|
Bugzilla – Full Text Bug Listing |
| Summary: | gcc warning without reason | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Jan Engelhardt <jengelh> |
| Component: | Development | Assignee: | Michael Matz <matz> |
| Status: | VERIFIED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | meissner |
| Version: | RC 1 | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | testcase | ||
|
Description
Jan Engelhardt
2005-09-26 20:31:06 UTC
Created attachment 50861 [details]
testcase
gcc -c mx.c
No linking needed.
well, the whole struct is passed marked as const, so probably the field are considered const too. This warning indeed is invalid (Marcus: the field itself is indeed considered const, but that doesn't mean that the pointed-to memory is readonly, i.e. the type of c->var in this context is "char * const var", but not "const char *". ) This is meanwhile fixed in 4.1 which doesn't give the wrong warning anymore. There are no plans to backport this specifically to 4.0, so I'll close this as FIXED. |