Andrew Morton wrote:
The downsides are that it muckies up the source a little and introduces a
very small risk that real use-uninitialised bugs will be hidden. But I
believe the benefit outweighs those disadvantages.
How about just marking the ones I've already done in #gccbug?
If I'm taking the time to audit the code, and separate out bogosities
from real bugs, it would be nice not to see that effort wasted.
#gccbug includes _only_ the bogosities. I didn't just blindly paper
over everything with a 'may be used uninitialized' warning. I'm well
over halfway through the 'make allmodconfig' build, and as LKML emails
can attest, have found several valid warnings.
Jeff
-
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]
