From: Jeff Garzik <jeff@garzik.org>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@osdl.org>
Subject: Announce: gcc bogus warning repository
Date: Sun, 01 Oct 2006 09:44:55 -0400 [thread overview]
Message-ID: <451FC657.6090603@garzik.org> (raw)
The level of warnings in a kernel build has lately increased to the
point where it is hiding bugs and otherwise making life difficult.
In particular, recent gcc versions throw warnings when it thinks a
variable "MAY be used uninitialized", which is not terribly helpful due
to the fact that most of these warnings are bogus.
For those that may find this valuable, I have started a git repo that
silences these bogus warnings, after careful auditing of code paths to
ensure that the warning truly is bogus.
The results may be found in the "gccbug" branch of
git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/misc-2.6.git
This repository will NEVER EVER be pushed upstream. It exists solely
for those who want to decrease their build noise, thereby exposing true
bugs.
The audit has already uncovered several minor bugs, lending credence to
my theory that too many warnings hides bugs.
next reply other threads:[~2006-10-01 13:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-01 13:44 Jeff Garzik [this message]
2006-10-01 13:56 ` Announce: gcc bogus warning repository Al Viro
2006-10-01 15:40 ` Daniel Walker
2006-10-01 18:12 ` Andrew Morton
2006-10-01 18:16 ` Jeff Garzik
2006-10-01 18:26 ` Daniel Walker
2006-10-01 18:45 ` Jeff Garzik
2006-10-01 18:58 ` Daniel Walker
2006-10-01 19:00 ` Al Viro
2006-10-01 19:03 ` Daniel Walker
2006-10-01 19:07 ` Al Viro
2006-10-01 19:13 ` Daniel Walker
2006-10-01 19:20 ` Al Viro
2006-10-01 19:25 ` Daniel Walker
2006-10-01 19:33 ` Al Viro
2006-10-01 21:45 ` Andrew Morton
2006-10-01 20:24 ` Roland Dreier
2006-10-02 11:39 ` linux-os (Dick Johnson)
2006-10-01 17:07 ` Randy Dunlap
2006-10-01 17:20 ` Jeff Garzik
2006-10-01 17:27 ` Alistair John Strachan
2006-10-01 17:45 ` Adrian Bunk
2006-10-01 18:16 ` Randy Dunlap
2006-10-04 16:19 ` Jörn Engel
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=451FC657.6090603@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.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