linux-kernel - Re: annoying new gcc 4.6.0 warnings.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4DB087EC.1010205@caviumnetworks.com>
Date:	Thu, 21 Apr 2011 12:39:24 -0700
From:	David Daney <ddaney@...iumnetworks.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
CC:	Dave Jones <davej@...hat.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: annoying new gcc 4.6.0 warnings.

On 04/21/2011 12:24 PM, Linus Torvalds wrote:
> On Thu, Apr 21, 2011 at 12:21 PM, Dave Jones<davej@...hat.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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/