public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/27093] [4.2 Regression] verify_ssa failed: definition does not dominate use
Date: Tue, 02 May 2006 08:04:00 -0000 [thread overview]
Message-ID: <20060502080409.31527.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27093-5724@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from rguenth at gcc dot gnu dot org 2006-05-02 08:04 -------
VRP causes the definition for SMT.5_37 to vanish, but it doesn't update the
PHI node. After reassoc we have:
# SMT.5_26 = PHI <SMT.5_35(4), SMT.5_43(7), SMT.5_41(5)>;
# bytes_left_22 = PHI <bytes_left_34(4), bytes_left_42(7),
bytes_left_40(5)>;
# seen_numbers_1 = PHI <0B(4), seen_numbers_15(7), seen_numbers_15(5)>;
<L8>:;
# bytes_left_36 = V_MAY_DEF <bytes_left_22>;
# SMT.5_37 = V_MAY_DEF <SMT.5_26>;
t1 ();
if (seen_numbers_1 == 0B) goto <L0>; else goto <L1>;
Invalid sum of incoming frequencies 9051, should be 8714
# SMT.5_20 = PHI <SMT.5_37(8), SMT.5_31(2), SMT.5_35(3)>;
# bytes_left_16 = PHI <bytes_left_36(8), bytes_left_30(2),
bytes_left_34(3)>;
<L0>:;
# bytes_left_32 = V_MAY_DEF <bytes_left_16>;
# SMT.5_33 = V_MAY_DEF <SMT.5_20>;
t1 ();
while after VRP, the def for SMT.5_37 vanished:
# SMT.5_26 = PHI <SMT.5_35(4), SMT.5_43(7), SMT.5_41(5)>;
# bytes_left_22 = PHI <bytes_left_34(4), bytes_left_42(7),
bytes_left_40(5)>;
# seen_numbers_1 = PHI <0B(4), seen_numbers_15(7), seen_numbers_15(5)>;
<L8>:;
# bytes_left_36 = V_MAY_DEF <bytes_left_22>;
t1 ();
if (seen_numbers_1 == 0B) goto <L0>; else goto <L1>;
Invalid sum of incoming frequencies 9051, should be 8714
# SMT.5_20 = PHI <SMT.5_37(8), SMT.5_31(2), SMT.5_35(3)>;
# bytes_left_16 = PHI <bytes_left_36(8), bytes_left_30(2),
bytes_left_34(3)>;
<L0>:;
# bytes_left_32 = V_MAY_DEF <bytes_left_16>;
t1 ();
but we didn't update the PHI node.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27093
next prev parent reply other threads:[~2006-05-02 8:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-09 14:46 [Bug tree-optimization/27093] New: " debian-gcc at lists dot debian dot org
2006-04-09 17:50 ` [Bug tree-optimization/27093] [4.2 Regression] " pinskia at gcc dot gnu dot org
2006-05-02 7:57 ` pinskia at gcc dot gnu dot org
2006-05-02 8:04 ` rguenth at gcc dot gnu dot org [this message]
2006-05-02 8:37 ` rguenth at gcc dot gnu dot org
2006-05-02 23:04 ` janis at gcc dot gnu dot org
2006-05-04 16:52 ` dberlin at gcc dot gnu dot org
2006-05-04 16:57 ` dberlin at dberlin dot org
2006-05-07 18:18 ` dberlin at gcc dot gnu dot org
2006-05-09 1:29 ` dberlin at gcc dot gnu dot org
2006-05-09 2:08 ` dberlin at gcc dot gnu dot org
2006-05-09 8:51 ` reichelt 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=20060502080409.31527.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).