public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/105264] -Wanalyzer-use-of-uninitialized-value gets confused about var + i v.s. &var[i]
Date: Thu, 14 Apr 2022 13:46:03 +0000 [thread overview]
Message-ID: <bug-105264-4-puOm8wf9Dt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105264-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105264
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2022-04-14
--- Comment #5 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
(In reply to Ævar Arnfjörð Bjarmason from comment #2)
> I think I can do one better. Here's a stand-alone reproducible test case
> without any headers except standard headers, I've expanded the gcc -E
> version of that too, but presumably you won't need it.
Thanks - I'm poking at -fanalyzer on both attachments now.
FWIW, the -E version can sometimes be very helpful, for the case where we have
different headers (e.g. glibc sometimes adds attributes to decls, which can
affect things)
next prev parent reply other threads:[~2022-04-14 13:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 13:49 [Bug analyzer/105264] New: " avarab at gmail dot com
2022-04-13 16:25 ` [Bug analyzer/105264] " dmalcolm at gcc dot gnu.org
2022-04-14 8:03 ` avarab at gmail dot com
2022-04-14 8:04 ` avarab at gmail dot com
2022-04-14 8:05 ` avarab at gmail dot com
2022-04-14 13:46 ` dmalcolm at gcc dot gnu.org [this message]
2022-04-14 20:49 ` dmalcolm at gcc dot gnu.org
2022-04-14 22:43 ` cvs-commit at gcc dot gnu.org
2022-04-14 22:52 ` dmalcolm at gcc dot gnu.org
2022-04-15 10:08 ` avarab at gmail dot com
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=bug-105264-4-puOm8wf9Dt@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).