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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20110421200836.GA31709@merkur.ravnborg.org>
Date:	Thu, 21 Apr 2011 22:08:36 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Dave Jones <davej@...hat.com>, Joe Perches <joe@...ches.com>,
	David Daney <ddaney@...iumnetworks.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	BorislavPetkov <bp@...en8.de>
Subject: Re: annoying new gcc 4.6.0 warnings.

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
--
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/