linux-kernel - Re: mainline build: 896 warnings 1 failures (mainline/v4.6-rc5-224-gda9373d)

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]

Date:	Mon, 2 May 2016 19:12:31 -0700
From:	Olof Johansson <olof@...om.net>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Kernel Build Reports Mailman List 
	<kernel-build-reports@...ts.linaro.org>,
	"Olof's autobuilder" <build@...om.net>,
	"linux-kbuild@...r.kernel.org" <linux-kbuild@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: mainline build: 896 warnings 1 failures (mainline/v4.6-rc5-224-gda9373d)

On Mon, May 2, 2016 at 12:24 AM, Arnd Bergmann <arnd@...db.de> wrote:
> On Sunday 01 May 2016 16:19:53 Olof Johansson wrote:
>> On Sun, May 1, 2016 at 2:26 PM, Olof's autobuilder <build@...om.net> wrote:
>> > Here are the build results from automated periodic testing.
>> >
>> > The tree being built was mainline, found at:
>> >
>> > http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git (master branch)
>> >
>> > Topmost commit:
>> >
>> > da9373d Merge branch 'fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal
>> >
>> > Build logs (stderr only) can be found at the following link (experimental):
>> >
>> > http://arm-soc.lixom.net/buildlogs/mainline/v4.6-rc5-224-gda9373d/
>> >
>> >
>> >         Runtime:                5m 0s
>> >
>> >         Passed:                 117
>> >         Failed:                 1
>> >
>> >         Warnings:               896
>> >
>> >         Section mismatches:     0
>>
>> So, yeah, I updated to GCC 6.1.0 and it looks noisy. If it doesn't get
>> whittled down pretty quickly I might switch to an older compiler
>> again.
>
> Oops, it looks like I never submitted a patch to shut up
> -Wunused-const-variable, though I've been building that way
> myself here and fixing all /other/ warnings.
>
> I think we want to have -Wunused-const-variable at the W=1 level, but
> not by default.

Agreed, at least as long as it is as noisy as it is today.

Care to send it in so we can see it in 4.6?

-Olof