public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/104543] [12 Regression] wrong code at -O3 on x86_64-linux-gnu
Date: Tue, 15 Feb 2022 07:14:50 +0000 [thread overview]
Message-ID: <bug-104543-4-QK3tkC5Juv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104543-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104543
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2022-02-15
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Confirmed.
>From what I could tell it is the unroll and jam pass which is messing up.
-fno-loop-unroll-and-jam
<bb 5> [local count: 542102826]:
# c.4_21 = PHI <0(7), _9(23)>
_7 = a[c.4_21];
_8 = _7 ^ 1;
a[c.4_21] = _8;
_9 = c.4_21 + 1;
_11 = b_lsm.13_13 + 1;
if (_11 <= 2)
goto <bb 22>; [83.33%]
else
goto <bb 8>; [16.67%]
<bb 22> [local count: 451752355]:
a[c.4_21] = _7;
next prev parent reply other threads:[~2022-02-15 7:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 6:56 [Bug tree-optimization/104543] New: " zhendong.su at inf dot ethz.ch
2022-02-15 6:57 ` [Bug tree-optimization/104543] " zhendong.su at inf dot ethz.ch
2022-02-15 7:06 ` [Bug tree-optimization/104543] [12 Regression] " pinskia at gcc dot gnu.org
2022-02-15 7:14 ` pinskia at gcc dot gnu.org [this message]
2022-02-15 8:28 ` rguenth at gcc dot gnu.org
2022-02-15 10:02 ` rguenth at gcc dot gnu.org
2022-02-15 11:26 ` rguenth at gcc dot gnu.org
2022-02-15 12:22 ` cvs-commit at gcc dot gnu.org
2022-02-15 12:22 ` rguenth at gcc dot gnu.org
2022-02-15 12:23 ` [Bug tree-optimization/104543] [9/10/11 " rguenth at gcc dot gnu.org
2022-02-15 12:53 ` rguenth at gcc dot gnu.org
2022-02-15 12:54 ` rguenth at gcc dot gnu.org
2022-02-15 14:47 ` matz at gcc dot gnu.org
2022-05-27 9:47 ` [Bug tree-optimization/104543] [10/11 " rguenth at gcc dot gnu.org
2022-06-28 10:48 ` jakub at gcc dot gnu.org
2022-07-15 10:51 ` marxin at gcc dot gnu.org
2023-07-07 10:42 ` [Bug tree-optimization/104543] [11 " rguenth at gcc dot gnu.org
2024-07-19 7:49 ` 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-104543-4-QK3tkC5Juv@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).