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/104676] New: [12 Regression] ICE in verify_loop_structure, at cfgloop.cc:1748 (error: loop 3's number of iterations '(unsigned int) + 4294967295' references the released SSA name '<unknown>') Date: Thu, 24 Feb 2022 12:48:26 +0000 [thread overview] Message-ID: <bug-104676-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104676 Bug ID: 104676 Summary: [12 Regression] ICE in verify_loop_structure, at cfgloop.cc:1748 (error: loop 3's number of iterations '(unsigned int) + 4294967295' references the released SSA name '<unknown>') Product: gcc Version: 12.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 12.0.1 20220220 snapshot (g:e49508ac6b36adb8a2056c5a1fb6e0178de2439d) ICEs when compiling the following testcase w/ -O1 -ftree-loop-distribution -ftree-parallelize-loops=2: struct S { int f; }; int n; int foo (struct S *s) { int arr[3]; int v = 0; for (n = 0; n < 2; ++n) { int i; for (i = 0; i < 2; ++i) { int j; for (j = 0; j < s->f; ++j) ++v; } if (v) arr[0] = 0; arr[n + 1] = 0; } return arr[0]; } % gcc-12.0.1 -O1 -ftree-loop-distribution -ftree-parallelize-loops=2 -c opcatmkb.c opcatmkb.c: In function 'foo': opcatmkb.c:8:1: error: loop 3's number of iterations '(unsigned int) + 4294967295' references the released SSA name '<unknown>' 8 | foo (struct S *s) | ^~~ during GIMPLE pass: ldist opcatmkb.c:8:1: internal compiler error: in verify_loop_structure, at cfgloop.cc:1748 0x68eb89 verify_loop_structure() /var/tmp/portage/sys-devel/gcc-12.0.1_p20220220/work/gcc-12-20220220/gcc/cfgloop.cc:1748 0xf752ee checking_verify_loop_structure /var/tmp/portage/sys-devel/gcc-12.0.1_p20220220/work/gcc-12-20220220/gcc/cfgloop.h:646 0xf752ee loop_distribution::execute(function*) /var/tmp/portage/sys-devel/gcc-12.0.1_p20220220/work/gcc-12-20220220/gcc/tree-loop-distribution.cc:3861 0xf7551b execute /var/tmp/portage/sys-devel/gcc-12.0.1_p20220220/work/gcc-12-20220220/gcc/tree-loop-distribution.cc:3905
next reply other threads:[~2022-02-24 12:48 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-24 12:48 asolokha at gmx dot com [this message] 2022-02-24 13:24 ` [Bug tree-optimization/104676] " jakub at gcc dot gnu.org 2022-02-24 13:25 ` rguenth at gcc dot gnu.org 2022-02-24 13:33 ` rguenth at gcc dot gnu.org 2022-02-24 14:58 ` cvs-commit at gcc dot gnu.org 2022-02-24 14:58 ` rguenth at gcc dot gnu.org 2022-04-28 3:23 ` 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-104676-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).