To: Andrew Morton <akpm@osdl.org>
Cc: Daniel Walker <dwalker@mvista.com>, Jeff Garzik <jeff@garzik.org>,
       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>
From: Roland Dreier <rdreier@cisco.com>
Date: Sun, 01 Oct 2006 13:24:04 -0700
In-Reply-To: <20061001111226.3e14133f.akpm@osdl.org> (Andrew Morton's message of "Sun, 1 Oct 2006 11:12:26 -0700")
Message-ID: <ada8xjzyecb.fsf@cisco.com>
User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.18 (linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 889
Lines: 17

    Andrew> The downsides are that it muckies up the source a little
    Andrew> and introduces a very small risk that real
    Andrew> use-uninitialised bugs will be hidden.  But I believe the
    Andrew> benefit outweighs those disadvantages.

Not sure I agree -- it adds one more thing that must be maintained
when reorganizing code.  I think there is a pretty high risk of this
sort of warning silencing hiding a bug introduced later, which would
have triggered an "is used uninitialized" warning.

Perhaps asking for a gcc flag that turns off "may be used" warnings
but leaves "is used" warnings would be useful (or does it already exist?)
-
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/