From: Andrew Morton <akpm@osdl.org>
To: Al Viro <viro@ftp.linux.org.uk>
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, 1 Oct 2006 14:45:09 -0700 [thread overview]
Message-ID: <20061001144509.e7950a16.akpm@osdl.org> (raw)
In-Reply-To: <20061001193330.GE29920@ftp.linux.org.uk>
On Sun, 1 Oct 2006 20:33:30 +0100
Al Viro <viro@ftp.linux.org.uk> wrote:
> On Sun, Oct 01, 2006 at 12:25:50PM -0700, Daniel Walker wrote:
> > > > > I bow to your incredible power of observation. Now that you've shared
> > > > > that revelation with the list, could you explain what does blanket silencing
> > > > > of these warnings buy you, oh wan^H^Hise one?
> > > >
> > > > Did you see me silencing anything (with your crystal ball?) ? Cause I'm
> > > > not.
> > >
> > > And what, in your opinion, does the patch in question achieve if not
> > > that?
> >
> > You mean the patch from Steven posted in May? Well it does appear to
> > silence the warning. You didn't like the approach it seems? Please tell
> > me why .
>
> Read the list archives...
There isn't much point in doing that if they're as useless as this thread.
Fact is, those bogus warnings are harmful and cause real problems to not be
noticed. There is value in finding some way of making real warnings
apparent to all developers and testers.
An external post-processor isn't very useful because few people will run
it. If we can integrate such a thing into the build system and make it
available to all developers and testers then OK.
next prev parent reply other threads:[~2006-10-01 21:45 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 [this message]
2006-10-01 20:24 ` Roland Dreier
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=20061001144509.e7950a16.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=dwalker@mvista.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ftp.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox