linux-kernel - Re: Announce: gcc bogus warning repository

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <452005E7.5030705@garzik.org>
Date:	Sun, 01 Oct 2006 14:16:07 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Andrew Morton <akpm@...l.org>
CC:	Daniel Walker <dwalker@...sta.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: Announce: gcc bogus warning repository

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 majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/