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: <20110421201534.GA19128@redhat.com>
Date:	Thu, 21 Apr 2011 16:15:34 -0400
From:	Dave Jones <davej@...hat.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Joe Perches <joe@...ches.com>,
	David Daney <ddaney@...iumnetworks.com>,
	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 01:09:11PM -0700, Linus Torvalds wrote:
 > On Thu, Apr 21, 2011 at 12:58 PM, Dave Jones <davej@...hat.com> wrote:
 > > @@ -359,7 +359,8 @@ KBUILD_CFLAGS   := -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs \
 > >                   -fno-strict-aliasing -fno-common \
 > >                   -Werror-implicit-function-declaration \
 > >                   -Wno-format-security \
 > > -                  -fno-delete-null-pointer-checks
 > > +                  -fno-delete-null-pointer-checks \
 > > +                  -Wno-unused-but-set-variable
 > 
 > Does this work ok for older gcc's? Do they understand that
 > -Wno-unused-by-set-variable?
 > 
 > gcc-4.5.1 seems to understand it, but what about much older gccs?

aparently not. I'll poke at it some more.

	Dave


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