From: Ingo Molnar <mingo@elte.hu>
To: Borislav Petkov <bp@alien8.de>
Cc: Michal Marek <mmarek@suse.cz>,
torvalds@linux-foundation.org, x86@kernel.org,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] kbuild: Add extra gcc checks
Date: Sun, 20 Feb 2011 18:11:22 +0100 [thread overview]
Message-ID: <20110220171122.GA7050@elte.hu> (raw)
In-Reply-To: <1298219710-9846-1-git-send-email-bp@alien8.de>
* Borislav Petkov <bp@alien8.de> 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/?i=20110218091716.GA4384@bicker
>
> Cc: Ingo Molnar <mingo@elte.hu>
> Cc: Michal Marek <mmarek@suse.cz>
> Cc: linux-kbuild@vger.kernel.org
> Signed-off-by: Borislav Petkov <bp@alien8.de>
Nice.
Acked-by: Ingo Molnar <mingo@elte.hu>
We enable a lot of GCC warnings in tools/perf/ as well, and while there are false
positives occasionally, the general effect on code quality is positive. We combine
it with -Werror to make sure warnings do not accumulate.
Thanks,
Ingo
next prev parent reply other threads:[~2011-02-20 17:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-20 16:35 [PATCH] kbuild: Add extra gcc checks Borislav Petkov
2011-02-20 17:11 ` Ingo Molnar [this message]
2011-02-20 17:57 ` Sam Ravnborg
2011-02-20 19:39 ` Borislav Petkov
2011-02-20 19:52 ` Sam Ravnborg
2011-02-21 2:23 ` [PATCH -v3] " Borislav Petkov
2011-02-21 3:26 ` Arnaud Lacombe
2011-02-21 4:37 ` Borislav Petkov
2011-02-21 5:22 ` Arnaud Lacombe
2011-02-20 20:00 ` [PATCH] " Joe Perches
2011-02-21 2:27 ` Borislav Petkov
2011-02-21 3:34 ` Arnaud Lacombe
2011-02-21 4:54 ` Borislav Petkov
2011-02-21 5:32 ` Arnaud Lacombe
2011-02-20 20:20 ` Jesper Juhl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110220171122.GA7050@elte.hu \
--to=mingo@elte.hu \
--cc=bp@alien8.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox