public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/107153] New: [13 Regression] ICE in check_loop_closed_ssa_def, at tree-ssa-loop-manip.cc:645 Date: Tue, 04 Oct 2022 13:04:44 +0000 [thread overview] Message-ID: <bug-107153-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107153 Bug ID: 107153 Summary: [13 Regression] ICE in check_loop_closed_ssa_def, at tree-ssa-loop-manip.cc:645 Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: asolokha at gmx dot com Target Milestone: --- gcc 13.0.0 20220925 snapshot (g:77bbf69d2981dafc2ef3e59bfbefb645d88bab9d) ICEs when compiling the following testcase w/ -O1 -floop-parallelize-all -ftree-parallelize-loops=2 -fno-tree-dominator-opts: void foo (int x, int y) { int i; for (i = 0; i < 2; i++) { } while (x) if (!y) while (y) ++y; } % gcc-13.0.0 -O1 -floop-parallelize-all -ftree-parallelize-loops=2 -fno-tree-dominator-opts -c rssq9kpi.c during GIMPLE pass: ompexpssa rssq9kpi.c: In function 'foo': rssq9kpi.c:2:1: internal compiler error: in check_loop_closed_ssa_def, at tree-ssa-loop-manip.cc:645 2 | foo (int x, int y) | ^~~ 0x77e395 check_loop_closed_ssa_def /var/tmp/portage/sys-devel/gcc-13.0.0_p20220925/work/gcc-13-20220925/gcc/tree-ssa-loop-manip.cc:645 0x106f1a4 check_loop_closed_ssa_bb /var/tmp/portage/sys-devel/gcc-13.0.0_p20220925/work/gcc-13-20220925/gcc/tree-ssa-loop-manip.cc:659 0x1070566 verify_loop_closed_ssa(bool, loop*) /var/tmp/portage/sys-devel/gcc-13.0.0_p20220925/work/gcc-13-20220925/gcc/tree-ssa-loop-manip.cc:695 0x1070566 verify_loop_closed_ssa(bool, loop*) /var/tmp/portage/sys-devel/gcc-13.0.0_p20220925/work/gcc-13-20220925/gcc/tree-ssa-loop-manip.cc:679 0xdfcf64 execute_function_todo /var/tmp/portage/sys-devel/gcc-13.0.0_p20220925/work/gcc-13-20220925/gcc/passes.cc:2109 0xdfd33e execute_todo /var/tmp/portage/sys-devel/gcc-13.0.0_p20220925/work/gcc-13-20220925/gcc/passes.cc:2145
next reply other threads:[~2022-10-04 13:04 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-04 13:04 asolokha at gmx dot com [this message] 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 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@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).