Message-ID: <452005E7.5030705@garzik.org>
Date: Sun, 01 Oct 2006 14:16:07 -0400
From: Jeff Garzik <jeff@garzik.org>
User-Agent: Thunderbird 1.5.0.7 (X11/20060913)
MIME-Version: 1.0
To: Andrew Morton <akpm@osdl.org>
CC: Daniel Walker <dwalker@mvista.com>,
       Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Announce: gcc bogus warning repository
References: <451FC657.6090603@garzik.org>	<1159717214.24767.3.camel@c-67-180-230-165.hsd1.ca.comcast.net> <20061001111226.3e14133f.akpm@osdl.org>
In-Reply-To: <20061001111226.3e14133f.akpm@osdl.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 937
Lines: 23

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