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/103721] [12 regression] wrong code generated for loop with conditional since r12-4790-g4b3a325f07acebf4 Date: Wed, 19 Jan 2022 16:40:28 +0000 [thread overview] Message-ID: <bug-103721-4-xjCiXbxhlj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103721-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103721 --- Comment #7 from Aldy Hernandez <aldyh at gcc dot gnu.org> --- After chatting with Andrew about this, it seems the problem is we are starting a path mid-loop and crossing a backedge. This causes us to use relations we had on one iteration in another iteration. <bb 8> [local count: 955630225]: # searchVolume_11 = PHI <1(4), 0(3)> # currentVolume_8 = PHI <searchVolume_5(4), searchVolume_5(3)> # **BACKEDGE** <bb 9> [local count: 1073741824]: # searchVolume_5 = PHI <searchVolume_11(8), world_7(D)(2)> # currentVolume_6 = PHI <currentVolume_8(8), 0(2)> _2 = searchVolume_5 != currentVolume_6; _3 = searchVolume_5 != 0; _4 = _2 & _3; if (_4 != 0) goto <bb 3>; [89.00%] else goto <bb 7>; [11.00%] ... ... <bb3> <bb4> <bb8> The _8 == _5 relation in BB8 is using _5 from a previous iteration (that came through BB9). Basically 8->9 has a use before def of _5. Once we hit a back edge, we should probably kill all current relations and disable looking outside the path altogether for relations. I will experiment.
next prev parent reply other threads:[~2022-01-19 16:40 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-14 22:19 [Bug tree-optimization/103721] New: [12 regression] wrong code generated for loop with conditional (jump threading?) sss@li-snyder.org 2021-12-14 22:21 ` [Bug tree-optimization/103721] " pinskia at gcc dot gnu.org 2021-12-14 23:03 ` pinskia at gcc dot gnu.org 2021-12-15 11:27 ` [Bug tree-optimization/103721] [12 regression] wrong code generated for loop with conditional since r12-4790-g4b3a325f07acebf4 marxin at gcc dot gnu.org 2022-01-04 11:16 ` rguenth at gcc dot gnu.org 2022-01-06 20:13 ` amacleod at redhat dot com 2022-01-18 4:02 ` law at gcc dot gnu.org 2022-01-18 18:49 ` amacleod at redhat dot com 2022-01-19 12:44 ` aldyh at gcc dot gnu.org 2022-01-19 16:40 ` aldyh at gcc dot gnu.org [this message] 2022-01-19 16:58 ` amacleod at redhat dot com 2022-01-19 22:51 ` law at gcc dot gnu.org 2022-01-20 0:10 ` amacleod at redhat dot com 2022-01-20 11:13 ` aldyh at gcc dot gnu.org 2022-01-20 11:14 ` aldyh at gcc dot gnu.org 2022-01-20 13:28 ` aldyh at gcc dot gnu.org 2022-01-20 14:12 ` amacleod at redhat dot com 2022-01-21 10:19 ` cvs-commit at gcc dot gnu.org 2022-01-21 10:30 ` aldyh 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-103721-4-xjCiXbxhlj@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).