public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/108685] New: [13 Regression] ICE in verify_loop_structure, at cfgloop.cc:1748
Date: Mon, 06 Feb 2023 18:50:55 +0000 [thread overview]
Message-ID: <bug-108685-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108685
Bug ID: 108685
Summary: [13 Regression] ICE in verify_loop_structure, at
cfgloop.cc:1748
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: gscfq@t-online.de
Target Milestone: ---
Started between 20220828 and 20220904, at -O1+ :
$ cat z1.c
void f (int a)
{
for (;;)
#pragma omp for collapse(2) ordered(4)
for (int i = 0; i < 2; i++)
for (int j = 0; j < a; j++)
for (int k = 0; k < 2; k++)
for (int l = 0; l < a; l++)
{
#pragma omp ordered doacross (source:)
__builtin_abort ();
}
}
$ gcc-13-20230205 -c z1.c -fopenmp -O2
z1.c: In function 'f':
z1.c:4:13: error: size of loop 3 should be 9, not 10
4 | #pragma omp for collapse(2) ordered(4)
| ^~~
z1.c:4:13: error: bb 8 does not belong to loop 3
z1.c:4:13: error: bb 18 does not belong to loop 3
z1.c:4:13: error: bb 15 does not belong to loop 3
z1.c:4:13: error: bb 14 does not belong to loop 3
z1.c:4:13: error: bb 13 does not belong to loop 3
z1.c:4:13: error: bb 9 does not belong to loop 3
z1.c:4:13: error: bb 17 does not belong to loop 3
z1.c:4:13: error: bb 16 does not belong to loop 3
z1.c:4:13: error: bb 10 does not belong to loop 3
z1.c:4:13: error: loop 3's header does not belong directly to it
during GIMPLE pass: ompexp
z1.c:4:13: internal compiler error: in verify_loop_structure, at
cfgloop.cc:1748
0x9ae013 verify_loop_structure()
../../gcc/cfgloop.cc:1748
0xd21499 checking_verify_loop_structure
../../gcc/cfgloop.h:646
0xd21499 fix_loop_structure(bitmap_head*)
../../gcc/loop-init.cc:327
0xf8dd37 repair_loop_structures
../../gcc/tree-cfgcleanup.cc:1190
0xf8dd37 cleanup_tree_cfg(unsigned int)
../../gcc/tree-cfgcleanup.cc:1218
0xe1dc14 execute_function_todo
../../gcc/passes.cc:2057
0xe1e5a2 execute_todo
../../gcc/passes.cc:2145
next reply other threads:[~2023-02-06 18:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 18:50 gscfq@t-online.de [this message]
2023-02-06 20:20 ` [Bug middle-end/108685] " pinskia at gcc dot gnu.org
2023-02-07 14:06 ` rguenth at gcc dot gnu.org
2023-02-10 9:05 ` [Bug middle-end/108685] [13 Regression] ICE in verify_loop_structure, at cfgloop.cc:1748 since r13-2388-ga651e6d59188da marxin at gcc dot gnu.org
2023-02-15 13:41 ` [Bug middle-end/108685] [10/11/12/13 " jakub at gcc dot gnu.org
2023-02-15 15:15 ` jakub at gcc dot gnu.org
2023-02-15 16:14 ` jakub at gcc dot gnu.org
2023-02-21 12:50 ` rguenth at gcc dot gnu.org
2023-03-16 17:32 ` jakub at gcc dot gnu.org
2023-03-17 8:00 ` cvs-commit at gcc dot gnu.org
2023-03-17 8:29 ` [Bug middle-end/108685] [10/11/12 " jakub at gcc dot gnu.org
2023-03-19 5:31 ` cvs-commit at gcc dot gnu.org
2023-03-20 10:30 ` [Bug middle-end/108685] [10/11 " jakub at gcc dot gnu.org
2023-05-02 20:15 ` cvs-commit at gcc dot gnu.org
2023-05-03 10:37 ` [Bug middle-end/108685] [10 " jakub at gcc dot gnu.org
2023-05-03 15:22 ` cvs-commit at gcc dot gnu.org
2023-05-04 7:24 ` jakub 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-108685-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: link
Be 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).