public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vincent-gcc at vinc17 dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/99944] incorrect maybe-uninitialized warning on variable defined as an array
Date: Wed, 07 Apr 2021 07:41:18 +0000 [thread overview]
Message-ID: <bug-99944-4-FugbzdIAmy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99944-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99944
--- Comment #2 from Vincent Lefèvre <vincent-gcc at vinc17 dot net> ---
(In reply to Richard Biener from comment #1)
> What's not correct with the diagnostic? The obfuscated printing of f[0]?
Hmm... for the *(unsigned int *)(&f[0]) case, it is correct after all, though
it should just say f[0].
But in the case with -fsanitize=undefined, gcc says that f may be used
uninitialized. But f is automatically initialized; it is f[0] that may be used
uninitialized.
next prev parent reply other threads:[~2021-04-07 7:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 20:59 [Bug c/99944] New: " vincent-gcc at vinc17 dot net
2021-04-07 7:25 ` [Bug c/99944] " rguenth at gcc dot gnu.org
2021-04-07 7:41 ` vincent-gcc at vinc17 dot net [this message]
2021-04-14 16:38 ` [Bug c/99944] poor format of array reference in -Wuninitialized msebor at gcc dot gnu.org
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-99944-4-FugbzdIAmy@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).