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/109410] New: [13 Regression] ICE: verify_flow_info failed Date: Tue, 04 Apr 2023 16:10:58 +0000 [thread overview] Message-ID: <bug-109410-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109410 Bug ID: 109410 Summary: [13 Regression] ICE: verify_flow_info failed 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 between 20220717 and 20220724, at -O1+ : (testcase derived from pr108783.c) (gcc configured with --enable-checking=yes) $ cat z1.c __attribute__((returns_twice)) int baz (int, int); int bar (int x) { return x; } int foo (int x, int y) { int a; a = bar (x); baz (x, y); return y && a && a; } int qux (int x, int y) { int a; a = bar (x); baz (x, y); return y && a != 42 && a >= 42; } int corge (int x, int y) { int a; baz (x, y); a = bar (x); return y || a == 42 || a > 42; } $ gcc-13-20230402 -c z1.c -O2 z1.c: In function 'corge': z1.c:24:1: error: returns_twice call is not first in basic block 2 24 | corge (int x, int y) | ^~~~~ baz (x_7(D), y_8(D)); during GIMPLE pass: reassoc z1.c:24:1: internal compiler error: verify_flow_info failed 0x8eeb6f verify_flow_info() ../../gcc/cfghooks.cc:285 0xd58ce6 execute_function_todo ../../gcc/passes.cc:2110 0xd59742 execute_todo ../../gcc/passes.cc:2152
next reply other threads:[~2023-04-04 16:10 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-04 16:10 gscfq@t-online.de [this message] 2023-04-04 20:50 ` [Bug tree-optimization/109410] " pinskia at gcc dot gnu.org 2023-04-04 20:53 ` pinskia at gcc dot gnu.org 2023-04-04 20:58 ` pinskia at gcc dot gnu.org 2023-04-11 12:31 ` rguenth at gcc dot gnu.org 2023-04-11 14:33 ` jakub at gcc dot gnu.org 2023-04-12 5:00 ` sjames at gcc dot gnu.org 2023-04-12 14:55 ` cvs-commit at gcc dot gnu.org 2023-04-12 14:58 ` jakub at gcc dot gnu.org 2023-04-18 7:16 ` cvs-commit at gcc dot gnu.org 2023-04-22 12:41 ` dcb314 at hotmail dot com 2023-04-22 12:58 ` sjames at gcc dot gnu.org 2023-04-23 2:45 ` sjames at gcc dot gnu.org 2023-04-23 3:58 ` sjames at gcc dot gnu.org 2023-04-23 4:07 ` pinskia at gcc dot gnu.org 2023-04-23 4:11 ` pinskia at gcc dot gnu.org 2023-04-26 6:58 ` [Bug tree-optimization/109410] [13/14 " rguenth at gcc dot gnu.org 2023-05-02 20:16 ` cvs-commit at gcc dot gnu.org 2023-05-03 15:23 ` cvs-commit at gcc dot gnu.org 2023-07-27 9:25 ` rguenth at gcc dot gnu.org 2024-05-21 9:14 ` [Bug tree-optimization/109410] [13/14/15 " 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-109410-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).