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/103458] [12 Regression] ICE in verify_loop_structure, at cfgloop.c:1736 (error: loop with header 4 not in loop tree) Date: Mon, 29 Nov 2021 08:18:07 +0000 [thread overview] Message-ID: <bug-103458-4-Z2puzVQQmr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103458-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103458 --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- So the issue is that we have bb3:<-\ <--\ |\ / | | -- | | | bb4: | .ABNORMAL_DISPATCHER at the start of CDDCE and the abnormal predecessor makes us not consider BB3 a loop header. But then we have an opportunity to create a forwarder (we avoid creating them for loop headers but this isn't one ...) which shows the opportunity to represent this CFG as an outer loop with an inner cycle with abnormal edge. CFG cleanup doesn't undo this forwarder because there are virtual PHIs in it. ethread is the pass that introduces this problematic header while this is all inside an irreducible region. In principle handling the abnormal edge in this case would be OK but in general abnormal latches pose a problem since with several loop opts we are facing the need to split/redirect those so relaxing this condition doesn't look feasible (but it creates nicer CFG for this particular testcase).
next prev parent reply other threads:[~2021-11-29 8:18 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-28 20:11 [Bug tree-optimization/103458] New: " asolokha at gmx dot com 2021-11-28 23:55 ` [Bug tree-optimization/103458] " pinskia at gcc dot gnu.org 2021-11-29 0:00 ` pinskia at gcc dot gnu.org 2021-11-29 7:41 ` rguenth at gcc dot gnu.org 2021-11-29 8:18 ` rguenth at gcc dot gnu.org [this message] 2021-11-29 8:54 ` [Bug tree-optimization/103458] [12 Regression] ICE in verify_loop_structure, at cfgloop.c:1736 (error: loop with header 4 not in loop tree) since r12-5301-g045206450386bcd7 marxin at gcc dot gnu.org 2021-11-29 9:12 ` cvs-commit at gcc dot gnu.org 2021-11-29 9:12 ` 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-103458-4-Z2puzVQQmr@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).