From: Ingo Molnar <mingo@elte.hu>
To: Pierre Ossman <drzeus@drzeus.cx>
Cc: Steven Noonan <steven@uplinklabs.net>,
Adrian Bunk <bunk@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sdhci: 'scratch' may be used uninitialized
Date: Mon, 6 Oct 2008 10:25:41 +0200 [thread overview]
Message-ID: <20081006082541.GA5001@elte.hu> (raw)
In-Reply-To: <20081006092722.414a7200@mjolnir.drzeus.cx>
* Pierre Ossman <drzeus@drzeus.cx> wrote:
> > Correct. Would you be interested in sending a patch for a
> > (default-off) debug feature that allows the disabling of all the gcc
> > annotations? That way we can do regular sweeps to determine whether
> > old annotations are still relevant on latest and greatest GCC.
>
> How would you find the ones that are no longer needed though?
ideally gcc should not emit _any_ bogus warning. Life is too short to
comb through crappy warnings and to keep in mind which ones are relevant
and which ones are not. compiler-intel.h does not make use of the
annotations for example.
> Perhaps we could make it so that uninitialized_var() itself emits a
> warning. That way you could turn that option on and check that you
> always have pairs of warnings.
ok - when CONFIG_CC_DEBUG_ALLOW_WARNINGS=y - and then the work flow
would be to go for single-occurance warnings and eliminate them (because
their annotation is moot).
Ingo
next prev parent reply other threads:[~2008-10-06 8:26 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 7:57 [PATCH -tip] pcm_native: label out defined but not used Steven Noonan
2008-10-01 7:57 ` [PATCH -tip] sdhci: 'scratch' may be used uninitialized Steven Noonan
2008-10-01 7:57 ` [PATCH -tip] drivers/serial/8250.c: 'i' " Steven Noonan
2008-10-01 8:01 ` Ingo Molnar
2008-10-01 8:16 ` Steven Noonan
2008-10-01 8:29 ` Ingo Molnar
2008-10-01 8:36 ` Steven Noonan
2008-10-01 8:47 ` [PATCH] " Steven Noonan
2008-10-01 21:36 ` Alan Cox
2008-10-02 9:02 ` Ingo Molnar
2008-10-01 8:48 ` [PATCH -tip] " Ingo Molnar
2008-10-01 10:34 ` Alan Cox
2008-10-01 10:33 ` Alan Cox
2008-10-01 10:57 ` Ingo Molnar
2008-10-01 15:41 ` Alan Cox
2008-10-02 9:00 ` Ingo Molnar
2008-10-01 8:00 ` [PATCH -tip] sdhci: 'scratch' " Ingo Molnar
2008-10-01 8:14 ` Steven Noonan
2008-10-01 8:33 ` Steven Noonan
2008-10-01 8:35 ` Ingo Molnar
2008-10-01 8:50 ` [PATCH] " Steven Noonan
2008-10-04 19:57 ` Pierre Ossman
2008-10-05 14:28 ` Adrian Bunk
2008-10-05 22:53 ` Steven Noonan
2008-10-05 23:16 ` Adrian Bunk
2008-10-05 23:48 ` Steven Noonan
2008-10-06 5:59 ` Adrian Bunk
2008-10-06 6:30 ` Ingo Molnar
2008-10-06 7:27 ` Pierre Ossman
2008-10-06 8:25 ` Ingo Molnar [this message]
2008-10-01 7:59 ` [PATCH -tip] pcm_native: label out defined but not used Ingo Molnar
2008-10-01 8:12 ` Steven Noonan
2008-10-01 8:13 ` Takashi Iwai
2008-10-01 8:32 ` Ingo Molnar
2008-10-01 8:56 ` Takashi Iwai
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=20081006082541.GA5001@elte.hu \
--to=mingo@elte.hu \
--cc=bunk@kernel.org \
--cc=drzeus@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=steven@uplinklabs.net \
/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