public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/45085] incorrect -Wuninitialized warning
Date: Tue, 27 Jul 2010 12:58:00 -0000	[thread overview]
Message-ID: <20100727125801.6840.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45085-360@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from jakub at gcc dot gnu dot org  2010-07-27 12:58 -------
Seems to be caused by partial inlining.
fnsplit splits off the:
  q.0D.2030_3 = qD.1248;
  fn7 (q.0D.2030_3);
part of fn9 into fn9.part.0:
fn9.part.0 ()
{
  intD.0 D.2054;
  voidD.32 * q.0D.2053;
  struct T tD.2052;
  struct T xD.2050;
  intD.0 yD.2051;

<bb 4>:

<bb 2>:
  q.0D.2053_1 = qD.1248;
  fn7 (q.0D.2053_1);

<bb 3>:
  <retval> = tD.2052;
  return <retval>;

}

and uses:
  tD.1261 = fn9.part.0 (); [return slot optimization]
in fn9 instead.  tD.2052 isn't initialized anywhere though (and, it is unclear
why it did that at all, as that hunk doesn't modify t).  Perhaps with -m32 and
aggregate return (where in the end t will be returned via hidden reference) t
is addressable?  In any case, this is fnsplit bug.


-- 

jakub at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hubicka at gcc dot gnu dot
                   |                            |org


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


  parent reply	other threads:[~2010-07-27 12:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-26 16:11 [Bug tree-optimization/45085] New: " tromey at gcc dot gnu dot org
2010-07-26 16:13 ` [Bug tree-optimization/45085] " tromey at gcc dot gnu dot org
2010-07-27 12:42 ` jakub at gcc dot gnu dot org
2010-07-27 12:58 ` jakub at gcc dot gnu dot org [this message]
2010-07-27 13:25 ` [Bug tree-optimization/45085] [4.6 Regression] " jakub at gcc dot gnu dot org
2010-07-27 14:13 ` hubicka at gcc dot gnu dot org
2010-08-03 12:09 ` hubicka at gcc dot gnu dot org
2010-09-02 11:11 ` rguenth at gcc dot gnu dot org
2010-09-02 22:59 ` manu at gcc dot gnu dot org
2010-09-03  9:11 ` jakub at gcc dot gnu dot 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=20100727125801.6840.qmail@sourceware.org \
    --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).