public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/32395] false positive warning about use of uninitialized variable.
Date: Fri, 01 Feb 2008 17:56:00 -0000	[thread overview]
Message-ID: <20080201175542.9528.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32395-7667@http.gcc.gnu.org/bugzilla/>



------- Comment #16 from manu at gcc dot gnu dot org  2008-02-01 17:55 -------
Somehow after SRA we end up creating a PHI node with an empty definition:



 # BLOCK 5 freq:2931, starting at line 7057
  # PRED: 276 [98.0%]  (true,exec) 3 [98.0%]  (true,exec)
  # inf$sideD.88720_393 = PHI <inf$sideD.88720_1256(276),
inf$sideD.88720_1476(D)(3)>

This node comes from the end of BB 3:

  # MPT.561D.88709_1630 = VDEF <MPT.561D.88709_1629> { MPT.561D.88709 }
  [pr32395-0.ii : 26871] thisD.73371_2(D)->node_countD.70698 = 0;
  # VUSE <MPT.561D.88709_1630> { MPT.561D.88709 }
  [pr32395-0.ii : 27027] hint$nodeD.85841_101 =
D.84656_69->D.70734.memberD.68890;
  [pr32395-0.ii : 26876] if (last$_M_currentD.85838_10 !=
first$_M_currentD.85837_463)
    goto <bb 5>;
  else
    goto <bb 285>;
  # SUCC: 5 [98.0%]  (true,exec) 285 [2.0%]  (false,exec)

I really cannot see in this huge testcase how we end up building this. However,
not even after all passes we remove the uninitialized use (and the edges going
to the block have a rather high probability). So, this is does not seem a bug,
just a case were GCC is not smart enough. More optimizations, more cases we
could catch. We will never catch them all. I would call it a Halting Problem
case and suspend it (probably add it with xfail to the testsuite).  ;-)

That it worked before just shows a possible optimisation regression with
respect to this code. But in such a huge testcase, it is hard to see what
regressed.


-- 


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


  parent reply	other threads:[~2008-02-01 17:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-18 17:24 [Bug c++/32395] New: " pluto at agmk dot net
2007-06-18 17:25 ` [Bug c++/32395] " pluto at agmk dot net
2007-06-19  8:10 ` [Bug middle-end/32395] " pinskia at gcc dot gnu dot org
2007-06-24 15:54 ` pluto at agmk dot net
2007-06-25 22:56 ` pluto at agmk dot net
2007-06-25 22:57 ` pluto at agmk dot net
2007-08-22 15:44 ` manu at gcc dot gnu dot org
2007-08-22 15:54 ` pluto at agmk dot net
2007-08-22 16:48 ` manu at gcc dot gnu dot org
2007-08-22 18:36 ` pluto at agmk dot net
2007-09-25 14:24 ` pluto at agmk dot net
2007-09-27  0:58 ` manu at gcc dot gnu dot org
2007-09-27  4:07 ` bangerth at dealii dot org
2008-01-08 20:00 ` pluto at agmk dot net
2008-01-23 21:25 ` pluto at agmk dot net
2008-01-23 23:20 ` manu at gcc dot gnu dot org
2008-02-01 17:56 ` manu at gcc dot gnu dot org [this message]
2010-03-15 10:32 ` [Bug middle-end/32395] false uninitialized warning (huge testcase) pluto at agmk dot net
2010-03-15 13:40 ` manu 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=20080201175542.9528.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).