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/104543] [12 Regression] wrong code at -O3 on x86_64-linux-gnu Date: Tue, 15 Feb 2022 11:26:34 +0000 [thread overview] Message-ID: <bug-104543-4-J8ZE9eLLxH@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 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matz at gcc dot gnu.org --- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> --- Hmm, no. The issue seems to be that the outer loop is head-controlled which means unrolling duplicates the exit check in the middle of the fused loop. I think we miss a check for an empty header of the outer loop, the perfect nest check is too simplistic here. We have b = 0; do { if (b > 2) break; c = 0; do { a[c] ^= 1; ++c } while (c <= 2); ++b; } while (1); and fusing ends up with something like b = 0; do { c = 0; do { a[c] ^= 1; if (b > 2) break; a[c] ^= 1; } while (c <= 2); b+=2; } while (1); in particular the comment in bb_prevents_fusion_p saying /* BB is duplicated by outer unrolling and then all N-1 first copies move into the body of the fused inner loop. If BB exits the outer loop the last copy still does so, and the first N-1 copies are cancelled by loop unrolling, so also after fusion it's the exit block. looks wrong. Yes, the first is cancelled but the remaining is not the exit block.
next prev parent reply other threads:[~2022-02-15 11:26 UTC|newest] Thread overview: 17+ 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 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 [this message] 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
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-J8ZE9eLLxH@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: linkBe 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).