From: Sam Ravnborg <sam@ravnborg.org>
To: Dave Jones <davej@redhat.com>, Joe Perches <joe@perches.com>,
David Daney <ddaney@caviumnetworks.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
BorislavPetkov <bp@alien8.de>
Subject: Re: annoying new gcc 4.6.0 warnings.
Date: Thu, 21 Apr 2011 22:08:36 +0200 [thread overview]
Message-ID: <20110421200836.GA31709@merkur.ravnborg.org> (raw)
In-Reply-To: <20110421195801.GA15126@redhat.com>
On Thu, Apr 21, 2011 at 03:58:02PM -0400, Dave Jones wrote:
> On Thu, Apr 21, 2011 at 12:44:46PM -0700, Joe Perches wrote:
> > On Thu, 2011-04-21 at 12:39 -0700, David Daney wrote:
> > > Would it make any sense to add a config option to enable the spew for
> > > those that wanted to see it?
> >
> > Add it to make W=1 instead?
> > See commit 4a5838ad9d2d
>
> This patch does that. Though I question the usefulness of W=1.
> I just built powernow-k8.o with W=1, and got 4030 lines of output.
> That's just insane.
It was discussed to do:
W=1 - the most usefull warnings
W=2 - the less usefull warnings
W=3 - the noise
Or somthing like that.
But no-one stepped up doing the classification then.
Should be simple to do.
My gcc (4.3.2) barfed over -Wno-unused-but-set-variable.
So your patch needs to check if the option is supported.
Sam
next prev parent reply other threads:[~2011-04-21 20:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 19:21 Dave Jones
2011-04-21 19:24 ` Linus Torvalds
2011-04-21 19:39 ` David Daney
2011-04-21 19:44 ` Joe Perches
2011-04-21 19:58 ` Dave Jones
2011-04-21 20:08 ` Sam Ravnborg [this message]
2011-04-21 20:27 ` Dave Jones
2011-04-21 20:37 ` David Daney
2011-04-21 20:45 ` Dave Jones
2011-04-21 20:56 ` Sam Ravnborg
2011-04-21 21:28 ` Dave Jones
2011-04-21 21:42 ` Sam Ravnborg
2011-04-29 15:02 ` Michal Marek
2011-04-21 20:09 ` Linus Torvalds
2011-04-21 20:15 ` Dave Jones
2011-04-21 20:30 ` Stratos Psomadakis
2011-04-21 21:10 ` Sam Ravnborg
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=20110421200836.GA31709@merkur.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=davej@redhat.com \
--cc=ddaney@caviumnetworks.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®