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/113374] [14 regression] ICE in find_uses_to_rename_use Date: Tue, 16 Jan 2024 14:49:25 +0000 [thread overview] Message-ID: <bug-113374-4-0R0oEV25qi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113374-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113374 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org Status|NEW |ASSIGNED --- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> --- The code populating alternative exit virtual PHIs simply doesn't handle more than one arg ... /* Now link the alternative exits. */ if (multiple_exits_p) { ... SET_PHI_ARG_DEF (l_phi, 0, exit_val); we're losing the original ones doing for (auto exit : loop_exits) { basic_block dest = main_loop_exit_block; if (exit != loop_exit) { if (!alt_loop_exit_block) { edge res = redirect_edge_and_branch ( exit, new_preheader); flush_pending_stmts (res); alt_loop_exit_block = split_edge (res); continue; } dest = alt_loop_exit_block; } edge e = redirect_edge_and_branch (exit, dest); flush_pending_stmts (e); } since that creates a new BB without any virtual PHI.
next prev parent reply other threads:[~2024-01-16 14:49 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-13 9:58 [Bug c++/113374] New: new breakage " dcb314 at hotmail dot com 2024-01-13 14:50 ` [Bug tree-optimization/113374] [14 regression] ICE " dcb314 at hotmail dot com 2024-01-13 16:14 ` pinskia at gcc dot gnu.org 2024-01-13 20:42 ` pinskia at gcc dot gnu.org 2024-01-13 22:50 ` pinskia at gcc dot gnu.org 2024-01-13 22:50 ` pinskia at gcc dot gnu.org 2024-01-15 8:33 ` rguenth at gcc dot gnu.org 2024-01-15 8:44 ` jakub at gcc dot gnu.org 2024-01-15 9:08 ` jakub at gcc dot gnu.org 2024-01-15 16:51 ` jakub at gcc dot gnu.org 2024-01-16 14:49 ` rguenth at gcc dot gnu.org [this message] 2024-01-18 7:37 ` cvs-commit at gcc dot gnu.org 2024-01-18 7:38 ` 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-113374-4-0R0oEV25qi@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).