public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/19430] taking address of a var causes missing uninitialized warning
Date: Thu, 21 Nov 2013 12:16:00 -0000 [thread overview]
Message-ID: <bug-19430-4-znFYTA0Bcj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-19430-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19430
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|V_MAY_DEF (taking address |taking address of a var
|of var) causes missing |causes missing
|uninitialized warning |uninitialized warning
Severity|minor |enhancement
--- Comment #24 from Richard Biener <rguenth at gcc dot gnu.org> ---
Well, fact is we still don't have the machinery that warns for the use of
uninitialized memory - and we never had. The cases that work by
accident are for loads that alias-analysis can prove we can move to
the function entry (well, a little less than that).
next prev parent reply other threads:[~2013-11-21 12:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-19430-4@http.gcc.gnu.org/bugzilla/>
2013-11-21 3:11 ` [Bug middle-end/19430] V_MAY_DEF (taking address of var) " vincent-gcc at vinc17 dot net
2013-11-21 12:16 ` rguenth at gcc dot gnu.org [this message]
2013-11-21 18:31 ` [Bug middle-end/19430] taking address of a var " manu at gcc dot gnu.org
2013-11-21 23:57 ` vincent-gcc at vinc17 dot net
2020-10-27 17:05 ` [Bug middle-end/19430] taking address of a var causes missing uninitialized warning (virtual PHI with MEM) msebor at gcc dot gnu.org
2021-04-01 0:23 ` msebor at gcc dot gnu.org
2022-08-29 13:08 ` rguenth at gcc dot gnu.org
2022-08-29 13:16 ` rguenth 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-19430-4-znFYTA0Bcj@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).