public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/58488] -Wuninitialized is useless for a variable whose address is later taken
Date: Mon, 23 Sep 2013 16:31:00 -0000	[thread overview]
Message-ID: <bug-58488-4-wNZT10wLsX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58488-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58488

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The warning machinery is only able to warn about vars in SSA form, vars which
must live in memory can't be warned on easily.  So, for such variables you only
get warnings if the compiler is able as part of some optimization make the var
non-addressable (e.g. inlining and propagation can help that, etc.), or scalar
replacement of aggregates is able to break appart larger aggregates and use SSA
form for those.  Thus, you get better warnings with optimizations.


  parent reply	other threads:[~2013-09-23 16:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-20 23:55 [Bug c/58488] New: " eblake at redhat dot com
2013-09-22 10:49 ` [Bug c/58488] " manu at gcc dot gnu.org
2013-09-23 16:16 ` eblake at redhat dot com
2013-09-23 16:31 ` jakub at gcc dot gnu.org [this message]
2013-10-30 20:47 ` law at redhat 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-58488-4-wNZT10wLsX@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).