From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Jeff Garzik <jeff@garzik.org>
Subject: Re: Announce: gcc bogus warning repository
Date: Sun, 1 Oct 2006 18:27:29 +0100
User-Agent: KMail/1.9.4
Cc: Randy Dunlap <rdunlap@xenotime.net>,
       Linux Kernel <linux-kernel@vger.kernel.org>,
       Andrew Morton <akpm@osdl.org>
References: <451FC657.6090603@garzik.org> <20061001100747.d1842273.rdunlap@xenotime.net> <451FF8ED.9080507@garzik.org>
In-Reply-To: <451FF8ED.9080507@garzik.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200610011827.29732.s0348365@sms.ed.ac.uk>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1453
Lines: 38

On Sunday 01 October 2006 18:20, Jeff Garzik wrote:
> Randy Dunlap wrote:
[snip]
> >> This repository will NEVER EVER be pushed upstream.  It exists solely
> >> for those who want to decrease their build noise, thereby exposing true
> >> bugs.
> >>
> >> The audit has already uncovered several minor bugs, lending credence to
> >> my theory that too many warnings hides bugs.
> >
> > I usually build with must_check etc. enabled then grep them
> > away if I want to look for other messages.  I think that the situation
> > is not so disastrous.
>
> I think it's both sad, and telling, that the high level of build noise
> has trained kernel hackers to tune out warnings, and/or build tools of
> ever-increasing sophistication just to pick out the useful messages from
> all the noise.
>
> If you have to grep useful stuff out of the noise, you've already lost.

The question is whether the GCC guys are actually doing anything about the 
problem. If they are, we should do nothing. If they aren't, maybe it's time 
for "x = x" hacks like Steven's.

Is GCC 4.2 any better with this class of warnings?

-- 
Cheers,
Alistair.

Final year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
-
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/