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/96424] New: ICE: verify_flow_info failed (error: wrong outgoing edge flags at end of bb 23); or ICE: Segmentation fault (in expand_omp_for_init_vars/contains_struct_check) Date: Mon, 03 Aug 2020 03:03:41 +0000 [thread overview] Message-ID: <bug-96424-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96424 Bug ID: 96424 Summary: ICE: verify_flow_info failed (error: wrong outgoing edge flags at end of bb 23); or ICE: Segmentation fault (in expand_omp_for_init_vars/contains_struct_check) Product: gcc Version: 11.0 Status: UNCONFIRMED Keywords: openmp Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: asolokha at gmx dot com Target Milestone: --- 1. g++-11.0.0-alpha20200726 snapshot (g:39ddfef9a5c24acf6412236f52f6716c8e0ebc9e) ICEs when compiling the following testcase, reduced from libgomp/testsuite/libgomp.c/loop-18.c, w/ -fbranch-probabilities -fnon-call-exceptions -fopenmp: int main () { int i, j; #pragma omp for collapse (2) for (i = 0; i < 1; ++i) for (j = 0; j <= i; ++j) { } return 0; } % g++-11.0.0 -fbranch-probabilities -fnon-call-exceptions -fopenmp -c qr6y7wzi.c qr6y7wzi.c: In function 'int main()': qr6y7wzi.c:13:1: error: wrong outgoing edge flags at end of bb 23 13 | } | ^ during IPA pass: profile qr6y7wzi.c:13:1: internal compiler error: verify_flow_info failed 0xb80b56 verify_flow_info() /var/tmp/portage/sys-devel/gcc-11.0.0_alpha20200726/work/gcc-11-20200726/gcc/cfghooks.c:269 0x105e7e7 checking_verify_flow_info /var/tmp/portage/sys-devel/gcc-11.0.0_alpha20200726/work/gcc-11-20200726/gcc/cfghooks.h:212 0x105e7e7 gimple_flow_call_edges_add /var/tmp/portage/sys-devel/gcc-11.0.0_alpha20200726/work/gcc-11-20200726/gcc/tree-cfg.c:8622 0xf81fdd branch_prob(bool) /var/tmp/portage/sys-devel/gcc-11.0.0_alpha20200726/work/gcc-11-20200726/gcc/profile.c:1099 0x10fe836 tree_profiling /var/tmp/portage/sys-devel/gcc-11.0.0_alpha20200726/work/gcc-11-20200726/gcc/tree-profile.c:779 0x10fe836 execute /var/tmp/portage/sys-devel/gcc-11.0.0_alpha20200726/work/gcc-11-20200726/gcc/tree-profile.c:885 2. Replacing <= w/ < yields the following instead: --- qr6y7wzi.c +++ #<buffer qr6y7wzi.c> @@ -5,7 +5,7 @@ main () #pragma omp for collapse (2) for (i = 0; i < 1; ++i) - for (j = 0; j <= i; ++j) + for (j = 0; j < i; ++j) { } % g++-11.0.0 -fbranch-probabilities -fnon-call-exceptions -fopenmp -c qr6y7wzi.c during GIMPLE pass: ompexp qr6y7wzi.c: In function 'int main()': qr6y7wzi.c:6:9: internal compiler error: Segmentation fault 6 | #pragma omp for collapse (2) | ^~~ 0x1028baf crash_signal /var/tmp/portage/sys-devel/gcc-11.0.0_alpha20200726/work/gcc-11-20200726/gcc/toplev.c:328 0xec69ae contains_struct_check(tree_node*, tree_node_structure_enum, char const*, int, char const*) /var/tmp/portage/sys-devel/gcc-11.0.0_alpha20200726/work/gcc-11-20200726/gcc/tree.h:3416 0xec69ae expand_omp_for_init_vars /var/tmp/portage/sys-devel/gcc-11.0.0_alpha20200726/work/gcc-11-20200726/gcc/omp-expand.c:2271 0xeccbe2 expand_omp_for_static_nochunk /var/tmp/portage/sys-devel/gcc-11.0.0_alpha20200726/work/gcc-11-20200726/gcc/omp-expand.c:4969 0xedc6b4 expand_omp_for /var/tmp/portage/sys-devel/gcc-11.0.0_alpha20200726/work/gcc-11-20200726/gcc/omp-expand.c:7421 0xedcb8a expand_omp /var/tmp/portage/sys-devel/gcc-11.0.0_alpha20200726/work/gcc-11-20200726/gcc/omp-expand.c:9691 0xede96c execute_expand_omp /var/tmp/portage/sys-devel/gcc-11.0.0_alpha20200726/work/gcc-11-20200726/gcc/omp-expand.c:9920
next reply other threads:[~2020-08-03 3:03 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-03 3:03 asolokha at gmx dot com [this message] 2020-08-07 10:08 ` [Bug tree-optimization/96424] " jakub at gcc dot gnu.org 2020-08-08 9:09 ` cvs-commit at gcc dot gnu.org 2020-08-08 11:36 ` 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-96424-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).