public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/103300] [12 Regression] wrong code at -O3 on x86_64-linux-gnu
Date: Thu, 18 Nov 2021 10:37:19 +0000 [thread overview]
Message-ID: <bug-103300-4-raDJS7hMHr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103300-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103300
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |matz at gcc dot gnu.org
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #3)
> (In reply to hubicka from comment #2)
> > Needs -O2 -floop-unroll-and-jam --param early-inlining-insns=14
> > to fail, so I guess it may be issue with unrol-and-jam.
>
> The major difference I see between GCC 11 and GCC 12 is how tree-loop-im
> handles the load/store of a and c. In GCC 11, it was an unconditional move
> of the store of a and c while in GCC 12 we get some interesting branches:
> <bb 9> [local count: 35059055]:
> # a_lsm.21_25 = PHI <_20(D)(6), _15(8)>
> # a_lsm_flag.22_8 = PHI <0(6), 1(8)>
> # c_lsm.23_22 = PHI <0(6), _5(8)>
> if (c_lsm.23_22 <= 2)
> goto <bb 17>; [94.50%]
> else
> goto <bb 10>; [5.50%]
>
> <bb 10> [local count: 1928248]:
> # a_lsm_flag.22_14 = PHI <a_lsm_flag.22_8(9)>
> # a_lsm.21_28 = PHI <a_lsm.21_25(9)>
> c_lsm.23_27 = 3;
> if (a_lsm_flag.22_14 != 0)
> goto <bb 11>; [66.67%]
> else
> goto <bb 12>; [33.33%]
>
> <bb 11> [local count: 1285499]:
> c = c_lsm.23_27;
>
> <bb 12> [local count: 1285499]:
> if (a_lsm_flag.22_14 != 0)
> goto <bb 13>; [66.67%]
> else
> goto <bb 14>; [33.33%]
>
> <bb 13> [local count: 856999]:
> a = a_lsm.21_28;
>
> <bb 14> [local count: 1928248]:
That's likely a missed threading / header copying, the stores are conditional
now and thus need protecting against store data races.
What unroll-and-jam does is make the inner loop enter always, only considering
the loop header check for the second iteration and also fails to include the
increment. That's likely a latent issue, maybe because the latch of the
outer loop is not empty?
Testcase that fails with -O2 -floop-unroll-and-jam:
int a, b[2], c, d, e, f;
int g(int h, int i) { return !i || h && i == 1 ? 0 : h % i; }
static void j() {
while (1)
while (1) {
if (d)
L:
if (f)
break;
if (e)
goto L;
return;
}
}
int main() {
j();
for (c = 0; c < 3; c++)
for (a = 0; a < 2; a++)
if (g(0, b[a]++))
while (1)
;
if (b[1] != 3)
__builtin_abort();
return 0;
}
Micha?
next prev parent reply other threads:[~2021-11-18 10:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 10:17 [Bug tree-optimization/103300] New: " zhendong.su at inf dot ethz.ch
2021-11-17 10:24 ` [Bug tree-optimization/103300] [12 Regression] " pinskia at gcc dot gnu.org
2021-11-17 11:08 ` [Bug tree-optimization/103300] New: " Jan Hubicka
2021-11-17 11:08 ` [Bug tree-optimization/103300] [12 Regression] " hubicka at kam dot mff.cuni.cz
2021-11-17 22:32 ` pinskia at gcc dot gnu.org
2021-11-18 7:47 ` rguenth at gcc dot gnu.org
2021-11-18 10:37 ` rguenth at gcc dot gnu.org [this message]
2021-11-18 10:39 ` [Bug tree-optimization/103300] [12 Regression] wrong code at -O3 on x86_64-linux-gnu since r12-4526-gd8edfadfc7a9795b marxin at gcc dot gnu.org
2021-12-02 7:22 ` zhendong.su at inf dot ethz.ch
2021-12-02 9:14 ` marxin at gcc dot gnu.org
2022-02-15 12:53 ` rguenth 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-103300-4-raDJS7hMHr@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).