From: David Daney <ddaney@caviumnetworks.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: annoying new gcc 4.6.0 warnings.
Date: Thu, 21 Apr 2011 12:39:24 -0700 [thread overview]
Message-ID: <4DB087EC.1010205@caviumnetworks.com> (raw)
In-Reply-To: <BANLkTi=srdq69ZG8pWbzWOZLX5KX48DcbQ@mail.gmail.com>
On 04/21/2011 12:24 PM, Linus Torvalds wrote:
> On Thu, Apr 21, 2011 at 12:21 PM, Dave Jones<davej@redhat.com> wrote:
>>
>> There might be some valid bugs found (I think DaveM found a few already) from this new
>> warning, but it seems like everything I've looked at so far is just noise.
>>
>> Any thoughts ?
>
> Yeah, let's just disable the crazy warning. Maybe some of them are
> valid, but it's like the f*cking sign-compare warning: most of them
> are just inane noise, and as such the warning is not worth the pain.
>
> I assume (hope) that there is some -Wno-unused-but-set-variable thing
> we could do, the same way we do -Wno-trigraphs for another totally
> useless gcc warning.
>
This particular warning has helped to find quite a bit of dead code.
Would it make any sense to add a config option to enable the spew for
those that wanted to see it?
David Daney
next prev parent reply other threads:[~2011-04-21 19:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 19:21 annoying new gcc 4.6.0 warnings Dave Jones
2011-04-21 19:24 ` Linus Torvalds
2011-04-21 19:39 ` David Daney [this message]
2011-04-21 19:44 ` Joe Perches
2011-04-21 19:58 ` Dave Jones
2011-04-21 20:08 ` Sam Ravnborg
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=4DB087EC.1010205@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=akpm@linux-foundation.org \
--cc=davej@redhat.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