On Wed, Jul 12, 2006 at 12:10:45AM +0200, Adrian Bunk wrote:
> I'm not a C expert myself, so I asked a gcc developer on irc.
>
> The problem is that C allows you to assign other values than the ones
> listed in the enum to the variable.
Its still a gcc bug in that case because you can show by static analysis
that no value is assigned into that array which isn't a member of the enum
and also that nobody takes the address of the object in question...
[Ok its a harder one]
I'd say that gcc warning in the case that all the enum values are enumerated
and have returns is a broken warning irrespective of that so I won't "fix" it
because it isn't broken. Its just like various other bogus gcc warnings
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
