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/106781] New: [13 Regression] ICE: verify_flow_info failed (error: returns_twice call is not first in basic block 2) Date: Wed, 31 Aug 2022 07:11:50 +0000 [thread overview] Message-ID: <bug-106781-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106781 Bug ID: 106781 Summary: [13 Regression] ICE: verify_flow_info failed (error: returns_twice call is not first in basic block 2) 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 20220828 snapshot (g:1ae1325f24cea1698b56e4299d95446a1f7b90a2) ICEs when compiling the following testcase w/ -O2: int n; __attribute__ ((noinline, returns_twice)) static int bar (int) { n /= 0; return n; } int foo (int x) { return bar (x); } % gcc-13.0.0 -O2 -w -c dmkrwty8.c dmkrwty8.c: In function 'foo': dmkrwty8.c:12:1: error: returns_twice call is not first in basic block 2 12 | foo (int x) | ^~~ bar.constprop (); during IPA pass: inline dmkrwty8.c:12:1: internal compiler error: verify_flow_info failed 0x9fcb0d verify_flow_info() /var/tmp/portage/sys-devel/gcc-13.0.0_p20220828/work/gcc-13-20220828/gcc/cfghooks.cc:284 0xf44614 checking_verify_flow_info /var/tmp/portage/sys-devel/gcc-13.0.0_p20220828/work/gcc-13-20220828/gcc/cfghooks.h:214 0xf44614 cleanup_tree_cfg_noloop /var/tmp/portage/sys-devel/gcc-13.0.0_p20220828/work/gcc-13-20220828/gcc/tree-cfgcleanup.cc:1156 0xf44614 cleanup_tree_cfg(unsigned int) /var/tmp/portage/sys-devel/gcc-13.0.0_p20220828/work/gcc-13-20220828/gcc/tree-cfgcleanup.cc:1207 0xdfdaf4 execute_function_todo /var/tmp/portage/sys-devel/gcc-13.0.0_p20220828/work/gcc-13-20220828/gcc/passes.cc:2057 0xdfdf4c execute_todo /var/tmp/portage/sys-devel/gcc-13.0.0_p20220828/work/gcc-13-20220828/gcc/passes.cc:2145 0xe00970 execute_one_ipa_transform_pass /var/tmp/portage/sys-devel/gcc-13.0.0_p20220828/work/gcc-13-20220828/gcc/passes.cc:2339 0xe00970 execute_all_ipa_transforms(bool) /var/tmp/portage/sys-devel/gcc-13.0.0_p20220828/work/gcc-13-20220828/gcc/passes.cc:2399 0xa34d2d cgraph_node::expand() /var/tmp/portage/sys-devel/gcc-13.0.0_p20220828/work/gcc-13-20220828/gcc/cgraphunit.cc:1827 0xa34d2d cgraph_node::expand() /var/tmp/portage/sys-devel/gcc-13.0.0_p20220828/work/gcc-13-20220828/gcc/cgraphunit.cc:1787 0xa36304 expand_all_functions /var/tmp/portage/sys-devel/gcc-13.0.0_p20220828/work/gcc-13-20220828/gcc/cgraphunit.cc:1998 0xa36304 symbol_table::compile() /var/tmp/portage/sys-devel/gcc-13.0.0_p20220828/work/gcc-13-20220828/gcc/cgraphunit.cc:2348 0xa38e27 symbol_table::compile() /var/tmp/portage/sys-devel/gcc-13.0.0_p20220828/work/gcc-13-20220828/gcc/cgraphunit.cc:2261 0xa38e27 symbol_table::finalize_compilation_unit() /var/tmp/portage/sys-devel/gcc-13.0.0_p20220828/work/gcc-13-20220828/gcc/cgraphunit.cc:2529
next reply other threads:[~2022-08-31 7:11 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-31 7:11 asolokha at gmx dot com [this message] 2022-08-31 7:48 ` [Bug tree-optimization/106781] " amonakov at gcc dot gnu.org 2022-08-31 8:23 ` [Bug tree-optimization/106781] [13 Regression] ICE: verify_flow_info failed (error: returns_twice call is not first in basic block 2) since r13-1754-g7a158a5776f5ca95 marxin at gcc dot gnu.org 2022-08-31 8:24 ` marxin at gcc dot gnu.org 2022-08-31 8:59 ` amonakov at gcc dot gnu.org 2022-08-31 12:17 ` rguenth at gcc dot gnu.org 2022-08-31 13:37 ` amonakov at gcc dot gnu.org 2022-10-19 7:01 ` rguenth at gcc dot gnu.org 2022-10-19 8:56 ` cvs-commit at gcc dot gnu.org 2022-10-19 8:56 ` rguenth 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-106781-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).