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/113373] [14 regression] ICE in verify_ssa since r14-6822 Date: Tue, 16 Jan 2024 13:57:37 +0000 [thread overview] Message-ID: <bug-113373-4-CjLjbiAr2T@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113373-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113373 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 #7 from Richard Biener <rguenth at gcc dot gnu.org> --- All good after vect_do_peeling. It's wrecked by vect_create_epilog_for_reduction here: scalar_result = scalar_results[k]; FOR_EACH_IMM_USE_STMT (use_stmt, imm_iter, orig_name) { FOR_EACH_IMM_USE_ON_STMT (use_p, imm_iter) SET_USE (use_p, scalar_result); update_stmt (use_stmt); we have two reduction epilogues, one for the early and one for the late exit but we mismatch the scalar use to replace. We're also picking up a reduction that's only live on one edge on the other (but that doesn't seem to result in a problem here). It also seems we're doing epilogue code generation before creating some exit PHIs required for that - vect_do_peeling fails to do that. We can try to hack around that a bit, but there's more issues with this testcase, like we generate useless epilogues - it seems we should identify the scalar exit PHI to transform when calling epilogue generation for a specific edge and skip if there isn't one.
next prev parent reply other threads:[~2024-01-16 13:57 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-13 9:43 [Bug c++/113373] New: ice in verify_ssa dcb314 at hotmail dot com 2024-01-13 14:47 ` [Bug tree-optimization/113373] [14 regression] ICE " dcb314 at hotmail dot com 2024-01-13 21:22 ` dcb314 at hotmail dot com 2024-01-13 21:27 ` pinskia at gcc dot gnu.org 2024-01-13 21:45 ` dcb314 at hotmail dot com 2024-01-13 22:56 ` pinskia at gcc dot gnu.org 2024-01-13 22:56 ` pinskia at gcc dot gnu.org 2024-01-15 8:32 ` rguenth at gcc dot gnu.org 2024-01-15 8:49 ` [Bug tree-optimization/113373] [14 regression] ICE in verify_ssa since r14-6822 jakub at gcc dot gnu.org 2024-01-16 13:57 ` rguenth at gcc dot gnu.org [this message] 2024-01-22 7:50 ` cvs-commit at gcc dot gnu.org 2024-01-22 7:50 ` 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-113373-4-CjLjbiAr2T@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).