From: Roland Dreier <rdreier@cisco.com>
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
Date: Sun, 01 Oct 2006 13:24:04 -0700 [thread overview]
Message-ID: <ada8xjzyecb.fsf@cisco.com> (raw)
In-Reply-To: <20061001111226.3e14133f.akpm@osdl.org> (Andrew Morton's message of "Sun, 1 Oct 2006 11:12:26 -0700")
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?)
next prev parent reply other threads:[~2006-10-01 20:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-01 13:44 Announce: gcc bogus warning repository Jeff Garzik
2006-10-01 13:56 ` Al Viro
2006-10-01 15:40 ` Daniel Walker
2006-10-01 18:12 ` Andrew Morton
2006-10-01 18:16 ` Jeff Garzik
2006-10-01 18:26 ` Daniel Walker
2006-10-01 18:45 ` Jeff Garzik
2006-10-01 18:58 ` Daniel Walker
2006-10-01 19:00 ` Al Viro
2006-10-01 19:03 ` Daniel Walker
2006-10-01 19:07 ` Al Viro
2006-10-01 19:13 ` Daniel Walker
2006-10-01 19:20 ` Al Viro
2006-10-01 19:25 ` Daniel Walker
2006-10-01 19:33 ` Al Viro
2006-10-01 21:45 ` Andrew Morton
2006-10-01 20:24 ` Roland Dreier [this message]
2006-10-02 11:39 ` linux-os (Dick Johnson)
2006-10-01 17:07 ` Randy Dunlap
2006-10-01 17:20 ` Jeff Garzik
2006-10-01 17:27 ` Alistair John Strachan
2006-10-01 17:45 ` Adrian Bunk
2006-10-01 18:16 ` Randy Dunlap
2006-10-04 16:19 ` Jörn Engel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ada8xjzyecb.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=akpm@osdl.org \
--cc=dwalker@mvista.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.