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 rtl-optimization/105455] New: ICE: verify_flow_info failed (error: verify_flow_info: REG_BR_PROB does not match cfg) Date: Mon, 02 May 2022 16:29:30 +0000 [thread overview] Message-ID: <bug-105455-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105455 Bug ID: 105455 Summary: ICE: verify_flow_info failed (error: verify_flow_info: REG_BR_PROB does not match cfg) Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: rtl-optimization Assignee: unassigned at gcc dot gnu.org Reporter: asolokha at gmx dot com Target Milestone: --- gcc 12.0.1 20220424 snapshot (g:6b7441a46c771aa6ecdc0c8ed96197417d036b9a) ICEs when compiling the following testcase w/ -O1 -fharden-conditional-branches -funroll-loops --param max-loop-header-insns=1: __attribute__ ((cold)) void bar (void); void foo (int x) { if (x) { int i; for (i = 0; i < 101; ++i) bar (); } } % gcc-12.0.1 -O1 -fharden-conditional-branches -funroll-loops --param max-loop-header-insns=1 -c hkihrvjs.c hkihrvjs.c: In function 'foo': hkihrvjs.c:14:1: error: verify_flow_info: REG_BR_PROB does not match cfg 1073741831 7 14 | } | ^ during RTL pass: loop2_unroll hkihrvjs.c:14:1: internal compiler error: verify_flow_info failed 0x9df59e verify_flow_info() /var/tmp/portage/sys-devel/gcc-12.0.1_p20220424/work/gcc-12-20220424/gcc/cfghooks.cc:284 0xde0a8a execute_function_todo /var/tmp/portage/sys-devel/gcc-12.0.1_p20220424/work/gcc-12-20220424/gcc/passes.cc:2097 0xde0f9e execute_todo /var/tmp/portage/sys-devel/gcc-12.0.1_p20220424/work/gcc-12-20220424/gcc/passes.cc:2139
next reply other threads:[~2022-05-02 16:29 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-02 16:29 asolokha at gmx dot com [this message] 2022-05-03 8:42 ` [Bug rtl-optimization/105455] " marxin at gcc dot gnu.org 2022-05-03 8:42 ` marxin at gcc dot gnu.org 2022-05-11 7:34 ` aoliva at gcc dot gnu.org 2022-05-13 6:01 ` cvs-commit at gcc dot gnu.org 2022-05-13 6:06 ` cvs-commit at gcc dot gnu.org 2022-05-13 6:09 ` aoliva at gcc dot gnu.org 2022-11-07 4:51 ` pinskia 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-105455-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).