From: Jeff Garzik <jeff@garzik.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: make-bogus-warnings-go-away tree [was: 2.6.18-mm3]
Date: Thu, 05 Oct 2006 12:44:46 -0400 [thread overview]
Message-ID: <4525367E.7080101@garzik.org> (raw)
In-Reply-To: <20061005163721.GJ16812@stusta.de>
Adrian Bunk wrote:
> What we'd need would be some -Wno-may-be-used-uninitialized gcc option
> that turns off the "may be may be used uninitialized" warnings but not
> the "is used uninitialized" warnings.
>
> This would:
> - give us a way to silence these warnings
> - allow people to see the warnings if they want to
> - not increase the maintenance overhead
Some of those warnings do indicate real bugs.
Jeff
next prev parent reply other threads:[~2006-10-05 16:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-03 7:11 2.6.18-mm3 Andrew Morton
2006-10-03 14:33 ` 2.6.18-mm3 Michal Piotrowski
2006-10-03 17:37 ` 2.6.18-mm3 Badari Pulavarty
2006-10-03 18:01 ` 2.6.18-mm3 Andrew Morton
2006-10-03 18:16 ` 2.6.18-mm3 Badari Pulavarty
2006-10-03 18:05 ` 2.6.18-mm3 Badari Pulavarty
2006-10-04 13:44 ` [-mm PATCH] fixed PCMCIA au1000_generic.c Yoichi Yuasa
2006-10-06 6:18 ` Om Narasimhan
2006-10-06 7:31 ` Yoichi Yuasa
2006-10-07 22:31 ` Om Narasimhan
2006-10-04 15:14 ` 2.6.18-mm3 oops in xfrm_register_mode Steve Fox
2006-10-04 16:57 ` Andrew Morton
2006-10-04 21:02 ` Steve Fox
2006-10-05 15:06 ` Badari Pulavarty
2006-10-05 8:37 ` make-bogus-warnings-go-away tree [was: 2.6.18-mm3] Ingo Molnar
2006-10-05 10:05 ` Jeff Garzik
2006-10-05 16:21 ` make-bogus-warnings-go-away tree Roland Dreier
2006-10-05 20:52 ` make-bogus-warnings-go-away tree [was: 2.6.18-mm3] Kyle Moffett
2006-10-05 16:37 ` Adrian Bunk
2006-10-05 16:44 ` Jeff Garzik [this message]
2006-10-05 16:51 ` Adrian Bunk
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=4525367E.7080101@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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