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/107505] New: [13 Regression] ICE: verify_flow_info failed (error: returns_twice call is not first in basic block 2) Date: Wed, 02 Nov 2022 07:41:38 +0000 [thread overview] Message-ID: <bug-107505-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107505 Bug ID: 107505 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-checking, 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: --- An obligatory abnormal edge issue of the week. gcc 13.0.0 20221030 snapshot (g:f36bba013361d8d4f9c7237c3307630de0cc0416) ICEs when compiling the following testcase w/ -O2 -fno-guess-branch-probability: int n; void bar (void); __attribute__ ((noinline, returns_twice)) int zero (void) { return 0; } void foo (void) { int a = zero (); for (n = 0; n < 2; ++n) { } if (a) bar (); } % gcc-13 -O2 -fno-guess-branch-probability -c u9i2um01.c u9i2um01.c: In function 'foo': u9i2um01.c:13:1: error: returns_twice call is not first in basic block 2 13 | foo (void) | ^~~ _7 = zero (); during GIMPLE pass: cddce u9i2um01.c:13:1: internal compiler error: verify_flow_info failed 0xa10ebd verify_flow_info() /var/tmp/portage/sys-devel/gcc-13.0.0_p20221030/work/gcc-13-20221030/gcc/cfghooks.cc:284 0xf529c4 checking_verify_flow_info /var/tmp/portage/sys-devel/gcc-13.0.0_p20221030/work/gcc-13-20221030/gcc/cfghooks.h:214 0xf529c4 cleanup_tree_cfg_noloop /var/tmp/portage/sys-devel/gcc-13.0.0_p20221030/work/gcc-13-20221030/gcc/tree-cfgcleanup.cc:1161 0xf529c4 cleanup_tree_cfg(unsigned int) /var/tmp/portage/sys-devel/gcc-13.0.0_p20221030/work/gcc-13-20221030/gcc/tree-cfgcleanup.cc:1212 0xe0b79c execute_function_todo /var/tmp/portage/sys-devel/gcc-13.0.0_p20221030/work/gcc-13-20221030/gcc/passes.cc:2057 0xe0bbfe execute_todo /var/tmp/portage/sys-devel/gcc-13.0.0_p20221030/work/gcc-13-20221030/gcc/passes.cc:2145
next reply other threads:[~2022-11-02 7:41 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-02 7:41 asolokha at gmx dot com [this message] 2022-11-02 16:27 ` [Bug tree-optimization/107505] " pinskia at gcc dot gnu.org 2022-11-02 18:49 ` amonakov at gcc dot gnu.org 2022-11-05 10:49 ` rguenth at gcc dot gnu.org 2022-11-07 13:01 ` cvs-commit at gcc dot gnu.org 2022-11-07 13:03 ` amonakov 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-107505-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).