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/107153] [13 Regression] ICE in check_loop_closed_ssa_def, at tree-ssa-loop-manip.cc:645 Date: Fri, 07 Oct 2022 08:29:11 +0000 [thread overview] Message-ID: <bug-107153-4-4IetkcQ53c@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107153-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107153 --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- OK, so the main issue is that when we parallelize a loop without stores we insert stores and thus would require a loop PHI for the virtual operand plus LC SSA updates. We eventually end up in gen_parallel_loop at /* We assume that the loop usually iterates a lot. */ loop_version (loop, many_iterations_cond, NULL, profile_probability::likely (), profile_probability::unlikely (), profile_probability::likely (), profile_probability::unlikely (), true); update_ssa (TODO_update_ssa_no_phi); which performs the update but doesn't insert PHIs - the above assumed that we'd have no SSA update pending before the call to loop_version. separate_decls_in_region is what creates the stores (with no virtual operands, thus triggering renaming and the need for a LC PHI). I'm going to work around.
next prev parent reply other threads:[~2022-10-07 8:29 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-04 13:04 [Bug tree-optimization/107153] New: " asolokha at gmx dot com 2022-10-04 13:12 ` [Bug tree-optimization/107153] " marxin at gcc dot gnu.org 2022-10-06 10:13 ` rguenth at gcc dot gnu.org 2022-10-07 8:29 ` rguenth at gcc dot gnu.org [this message] 2022-10-07 12:27 ` cvs-commit at gcc dot gnu.org 2022-10-07 12:28 ` rguenth at gcc dot gnu.org 2022-10-10 10:05 ` cvs-commit 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-107153-4-4IetkcQ53c@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).