Path: csiph.com!goblin3!goblin1!goblin.stu.neva.ru!news.mixmin.net!aioe.org!gothmog.csi.it!bofh.it!news.nic.it!robomod
From: Markus Trippelsdorf <markus@trippelsdorf.de>
Newsgroups: linux.kernel
Subject: Re: [PATCH] Kbuild: Move -Wmaybe-uninitialized to W=1
Date: Thu, 28 Jul 2016 20:10:01 +0200
Message-ID: <rZXUR-1l2-7@gated-at.bofh.it>
References: <ntF90-8cg-15@gated-at.bofh.it> <ntMtQ-2lY-35@gated-at.bofh.it> <nwGBA-4bA-25@gated-at.bofh.it> <nBeOl-7wr-1@gated-at.bofh.it> <rZL7k-14A-23@gated-at.bofh.it> <rZORz-3Ef-9@gated-at.bofh.it> <rZPaW-3LV-11@gated-at.bofh.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: robomod@news.nic.it
Approved: robomod@news.nic.it
Lines: 19
Organization: linux.* mail to news gateway
Xref: csiph.com linux.kernel:1452035

On 2016.07.28 at 10:46 +0200, Borislav Petkov wrote:
> On Thu, Jul 28, 2016 at 10:29:15AM +0200, Ingo Molnar wrote:
> > BUT, isn't this the natural state of things, that the 'final' warnings
> > that don't get fixed are the obnoxious, false positive ones - because
> > anyone who looks at them will say "oh crap, idiotic compiler!"?
> 
> Hmm, so my experience is like Linus' - that -Wmaybe thing generates too
> much noise and a lot of false positives. The thing is, as Micha (on CC)
> explained it to me, that warning simply says that GCC sometimes *cannot*
> know whether the variable will be used uninitialized or not and eagerly
> issues the warning message, just in case.

Another issue is that the number of warnings you get depend on the
optimization level. So -Os may be different from -O2 and once you use
-O3 (I know it is not officially supported) you will drown in false
positives...

-- 
Markus