From: David Sterba <dsterba@suse.cz>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>, Arnd Bergmann <arnd@arndb.de>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>,
Anand Jain <anand.jain@oracle.com>,
Filipe Manana <fdmanana@suse.com>, Qu Wenruo <wqu@suse.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] btrfs: avoid Wmaybe-uninitialized warnings
Date: Mon, 10 Jul 2023 18:55:06 +0200 [thread overview]
Message-ID: <20230710165506.GA30916@twin.jikos.cz> (raw)
In-Reply-To: <20230705140117.795478-1-arnd@kernel.org>
On Wed, Jul 05, 2023 at 04:01:08PM +0200, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> The -Wmaybe-uninitialized warning option in gcc produces tons of false
> positive warnings when KASAN is enabled, as that turns off some required
> optimizations.
Which version of gcc produces the warnings? I have KASAN enabled and
don't see any warnings, with gcc 13. Making the warning conditional
would effectively turn it off for me which means I can't catch the
warnings early. We do get reports from various build bots with
various arch/compiler combinations and fix the warnings.
If there's a know minimum compiler version where there are no reports
(or reasonably small nubmer to fix) then I'd rather make the condition
bassed on that, neither on KASAN nor any similar feature for that matter.
next prev parent reply other threads:[~2023-07-10 17:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 14:01 Arnd Bergmann
2023-07-05 14:01 ` [PATCH 2/2] btrfs: fix 64-bit division link failure Arnd Bergmann
2023-07-10 17:06 ` David Sterba
2023-07-10 16:55 ` David Sterba [this message]
2023-07-10 19:12 ` [PATCH 1/2] btrfs: avoid Wmaybe-uninitialized warnings Arnd Bergmann
2023-07-10 19:25 ` Arnd Bergmann
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=20230710165506.GA30916@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=anand.jain@oracle.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=fdmanana@suse.com \
--cc=johannes.thumshirn@wdc.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wqu@suse.com \
/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®