linux-kernel - Re: [PATCH -v5] kbuild: Add extra gcc checks

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:	Wed, 9 Mar 2011 15:45:04 +0100
From:	Michal Marek <mmarek@...e.cz>
To:	Borislav Petkov <bp@...en8.de>, Arnd Bergmann <arnd@...db.de>,
	Sam Ravnborg <sam@...nborg.org>, torvalds@...ux-foundation.org,
	x86@...nel.org, linux-kernel@...r.kernel.org,
	Ingo Molnar <mingo@...e.hu>, linux-kbuild@...r.kernel.org,
	bp@...64.org
Subject: Re: [PATCH -v5] kbuild: Add extra gcc checks

On Tue, Mar 01, 2011 at 09:35:29AM +0100, Borislav Petkov wrote:
> Add a 'W=1' Makefile switch which adds additional checking per build
> object.
> 
> The idea behind this option is targeted at developers who, in the
> process of writing their code, want to do the occasional
> 
> make W=1 [target.o]
> 
> and let gcc do more extensive code checking for them. Then, they
> could eyeball the output for valid gcc warnings about various
> bugs/discrepancies which are not reported during the normal build
> process.
> 
> For more background information and a use case, read through this
> thread: http://marc.info/?l=kernel-janitors&m=129802065918147&w=2
> 
> -v5: Document internal kbuild variable which is introduced by this.
> Simplify assignment.

Thanks, applied to kbuild-2.6.git#packaging. If someone comes up with a
good selection of warnings for W=1 and W=2, we can change it later.

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