public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/103226] [12 Regression] Recent change to copy-headers causes execution failure for gcc.dg/torture/pr80974
Date: Wed, 17 Nov 2021 11:32:17 +0000 [thread overview]
Message-ID: <bug-103226-4-YsVebraR4M@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103226-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103226
--- Comment #5 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
FWIW, the *.ch2 dump on both x86-64 and bfin-elf are identical.
This is unlikely to help, but...
In *.ivopts we start seeing differences in the IL:
<bb 5> [local count: 60236916]:
e = 1;
+ ivtmp.29_7 = (unsigned int) &g;
goto <bb 11>; [100.00%]
<bb 6> [local count: 60236916]:
@@ -593,7 +590,8 @@
goto <bb 9>; [50.00%]
<bb 8> [local count: 1625827684]:
- MEM[(int *)&g + ivtmp.26_25 * 4] = 4;
+ _8 = (void *) ivtmp.29_25;
+ MEM[(int *)_8] = 4;
<bb 9> [local count: 3251655368]:
ivtmp_15 = ivtmp_14 - 1;
@@ -603,8 +601,9 @@
goto <bb 10>; [14.29%]
<bb 10> [local count: 542132239]:
- ivtmp.26_10 = ivtmp.26_25 + 1;
- if (ivtmp.26_10 != 9)
+ h_11 = h_6 + 1;
+ ivtmp.29_10 = ivtmp.29_25 + 4;
+ if (h_11 != 9)
goto <bb 19>; [90.00%]
else
goto <bb 12>; [10.00%]
@@ -612,7 +611,8 @@
<bb 19> [local count: 487919014]:
<bb 11> [local count: 542132239]:
- # ivtmp.26_25 = PHI <ivtmp.26_10(19), 0(5)>
+ # h_6 = PHI <h_11(19), 0(5)>
+ # ivtmp.29_25 = PHI <ivtmp.29_10(19), ivtmp.29_7(5)>
goto <bb 7>; [100.00%]
next prev parent reply other threads:[~2021-11-17 11:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-13 20:39 [Bug tree-optimization/103226] New: " law at gcc dot gnu.org
2021-11-14 10:59 ` [Bug tree-optimization/103226] " aldyh at gcc dot gnu.org
2021-11-15 9:03 ` rguenth at gcc dot gnu.org
2021-11-16 2:30 ` law at gcc dot gnu.org
2021-11-17 11:14 ` aldyh at gcc dot gnu.org
2021-11-17 11:32 ` aldyh at gcc dot gnu.org [this message]
2021-11-17 15:00 ` tnfchris at gcc dot gnu.org
2021-11-17 15:02 ` tnfchris at gcc dot gnu.org
2021-11-17 15:53 ` aldyh at gcc dot gnu.org
2021-11-17 16:09 ` tnfchris at gcc dot gnu.org
2021-11-17 16:28 ` law at gcc dot gnu.org
2021-11-17 16:29 ` law at gcc dot gnu.org
2021-11-17 16:31 ` aldyh at gcc dot gnu.org
2021-11-17 17:18 ` aldyh at gcc dot gnu.org
2021-11-17 17:54 ` tnfchris at gcc dot gnu.org
2021-11-17 18:31 ` law at gcc dot gnu.org
2021-11-17 18:43 ` aldyh at gcc dot gnu.org
2021-11-17 19:26 ` aldyh at gcc dot gnu.org
2021-11-17 20:02 ` aldyh at gcc dot gnu.org
2021-11-18 13:28 ` aldyh at gcc dot gnu.org
2021-11-20 7:10 ` law at gcc dot gnu.org
2021-11-20 7:23 ` aldyh at gcc dot gnu.org
2021-11-20 16:30 ` cvs-commit at gcc dot gnu.org
2021-11-20 16:31 ` law at gcc dot gnu.org
2021-12-02 14:55 ` hp 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-103226-4-YsVebraR4M@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).