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/107001] New: ICE in expand_gimple_stmt_1, at cfgexpand.cc:4017 Date: Wed, 21 Sep 2022 17:35:20 +0000 [thread overview] Message-ID: <bug-107001-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107001 Bug ID: 107001 Summary: ICE in expand_gimple_stmt_1, at cfgexpand.cc:4017 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: gscfq@t-online.de Target Milestone: --- Started with r9, at -O0 : $ cat z1.c void bar (int *q); void foo (int *p, int *q) { #pragma omp taskgroup task_reduction (*: p[0]) { #pragma omp taskgroup task_reduction (*: q[0]) bar (q); } } $ gcc-13-20220918 -c z1.c -O0 -fopenmp -fexceptions during RTL pass: expand z1.c: In function 'foo': z1.c:2:6: internal compiler error: in expand_gimple_stmt_1, at cfgexpand.cc:4017 2 | void foo (int *p, int *q) | ^~~ 0x9587db expand_gimple_stmt_1 ../../gcc/cfgexpand.cc:4017 0x9587db expand_gimple_stmt ../../gcc/cfgexpand.cc:4044 0x95febf expand_gimple_basic_block ../../gcc/cfgexpand.cc:6096 0x962516 execute ../../gcc/cfgexpand.cc:6822
next reply other threads:[~2022-09-21 17:35 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-21 17:35 gscfq@t-online.de [this message] 2022-09-22 19:11 ` [Bug c/107001] ICE in expand_gimple_stmt_1, at cfgexpand.cc:4017 since r9-3941-g28567c40e2c7c88e marxin at gcc dot gnu.org 2022-09-23 12:04 ` jakub at gcc dot gnu.org 2022-09-24 7:31 ` cvs-commit at gcc dot gnu.org 2022-11-03 0:23 ` cvs-commit at gcc dot gnu.org 2022-11-04 8:31 ` cvs-commit at gcc dot gnu.org 2023-05-03 15:19 ` cvs-commit at gcc dot gnu.org 2023-05-04 7:20 ` 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-107001-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).