From: Andrew Morton <akpm@linux-foundation.org>
To: Andrey Ryabinin <aryabinin@virtuozzo.com>
Cc: <fengguang.wu@intel.com>, <linux-kernel@vger.kernel.org>,
<kbuild-all@01.org>
Subject: Re: [PATCH] ubsan: fix tree-wide -Wmaybe-uninitialized false positives
Date: Mon, 25 Jan 2016 13:41:36 -0800 [thread overview]
Message-ID: <20160125134136.cee4919a8453c4753f177c3b@linux-foundation.org> (raw)
In-Reply-To: <1453737694-19138-1-git-send-email-aryabinin@virtuozzo.com>
On Mon, 25 Jan 2016 19:01:34 +0300 Andrey Ryabinin <aryabinin@virtuozzo.com> wrote:
> -fsanitize=* options makes GCC less smart than usual and increase number
> of 'maybe-uninitialized' false-positives. So this patch does two things:
> * Add -Wno-maybe-uninitialized to CFLAGS_UBSAN which will disable all
> such warnings for instrumented files.
> * Remove CONFIG_UBSAN_SANITIZE_ALL from all[yes|mod]config builds. So
> the all[yes|mod]config build goes without -fsanitize=* and still with
> -Wmaybe-uninitialized.
hm, that's a bit sad.
We have no means of working out whether we should re-enable
maybe-uninitialized for later gcc's, as they become smarter about this.
What do we do, just "remember" to try it later on?
Do you know if this issue is on the gcc developer' radar?
next prev parent reply other threads:[~2016-01-25 21:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 7:15 sound/soc/codecs/wm8962.c:2790:32: warning: 'fratio' may be used uninitialized in this function kbuild test robot
2016-01-25 16:01 ` [PATCH] ubsan: fix tree-wide -Wmaybe-uninitialized false positives Andrey Ryabinin
2016-01-25 21:41 ` Andrew Morton [this message]
2016-01-26 17:03 ` Andrey Ryabinin
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=20160125134136.cee4919a8453c4753f177c3b@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aryabinin@virtuozzo.com \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.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
all inboxes | Powered by JetHome®