From: Tom Rix <trix@redhat.com>
To: Nathan Chancellor <nathan@kernel.org>,
Dan Carpenter <dan.carpenter@oracle.com>
Cc: ksummit-discuss@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org, kbuild@lists.01.org, lkp@intel.com,
llvm@lists.linux.dev, Nick Desaulniers <ndesaulniers@google.com>
Subject: Re: uninitialized variables bugs
Date: Sun, 8 May 2022 05:17:58 -0700 [thread overview]
Message-ID: <53237fa6-3d32-4f92-c7ea-9dd8bc12e028@redhat.com> (raw)
In-Reply-To: <YnWYHzQC4Y55sOsT@dev-arch.thelio-3990X>
On 5/6/22 2:50 PM, Nathan Chancellor wrote:
> Hi Dan,
>
> On Fri, May 06, 2022 at 12:13:38PM +0300, Dan Carpenter wrote:
>> Ever since commit 78a5255ffb6a ("Stop the ad-hoc games with
>> -Wno-maybe-initialized"), GCC's uninitialized variable warnings have
>> been disabled by default. Now, you have to turn on W=1 or W=2 to see
>> the warnings which nobody except Arnd does.
...
> Clang's static analyzer, which Tom regularly runs, will check variables
> across function boundaries. I am not sure what the false positive rate
> on that check is but it does turn up issues like smatch does.
Clang's static analyzer is pretty go wrt uninitialized variables.
But the issues do not turn up in the report, the show up as errors and
is why
I post a fix for a build break every couple of weeks.
Tom
next prev parent reply other threads:[~2022-05-08 12:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 9:13 uninitialized variables bugs Dan Carpenter
2022-05-06 9:53 ` [Ksummit-discuss] " Julia Lawall
2022-05-06 11:56 ` Arnd Bergmann
2022-05-06 16:23 ` Shuah Khan
2022-05-06 21:50 ` Nathan Chancellor
2022-05-08 12:17 ` Tom Rix [this message]
2022-05-22 9:07 ` [Ksummit-discuss] " Krzysztof Kozlowski
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=53237fa6-3d32-4f92-c7ea-9dd8bc12e028@redhat.com \
--to=trix@redhat.com \
--cc=dan.carpenter@oracle.com \
--cc=kbuild@lists.01.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.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