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/107369] New: [13 Regression] ICE: verify_flow_info failed (error: label 'l1' has incorrect context in bb 2)
Date: Mon, 24 Oct 2022 06:00:18 +0000	[thread overview]
Message-ID: <bug-107369-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107369

            Bug ID: 107369
           Summary: [13 Regression] ICE: verify_flow_info failed (error:
                    label 'l1' has incorrect context in bb 2)
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Keywords: ice-on-invalid-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 20221023 snapshot (g:0e37fd4dc74c1db99cdc7d71ef378e1221253c6f) ICEs
when compiling the following testcase, reduced from
gcc/testsuite/gcc.dg/attr-assume-3.c, w/ -O1:

void
foo (int x)
{
  if (x == 1)
    goto l1;

  [[gnu::assume (({ l1:; 1; }))]];
}

% aarch64-linux-gnu-gcc-13 -O1 -c bgoph4pp.c
bgoph4pp.c: In function 'foo':
bgoph4pp.c:5:5: error: jump into statement expression
    5 |     goto l1;
      |     ^~~~
bgoph4pp.c:7:21: note: label 'l1' defined here
    7 |   [[gnu::assume (({ l1:; 1; }))]];
      |                     ^~
bgoph4pp.c:2:1: error: label 'l1' has incorrect context in bb 2
    2 | foo (int x)
      | ^~~
during GIMPLE pass: cfg
bgoph4pp.c:2:1: internal compiler error: verify_flow_info failed
0xa39a8e verify_flow_info()
       
/var/tmp/portage/cross-aarch64-linux-gnu/gcc-13.0.0_p20221023/work/gcc-13-20221023/gcc/cfghooks.cc:284
0xf87e34 checking_verify_flow_info
       
/var/tmp/portage/cross-aarch64-linux-gnu/gcc-13.0.0_p20221023/work/gcc-13-20221023/gcc/cfghooks.h:214
0xf87e34 cleanup_tree_cfg_noloop
       
/var/tmp/portage/cross-aarch64-linux-gnu/gcc-13.0.0_p20221023/work/gcc-13-20221023/gcc/tree-cfgcleanup.cc:1161
0xf87e34 cleanup_tree_cfg(unsigned int)
       
/var/tmp/portage/cross-aarch64-linux-gnu/gcc-13.0.0_p20221023/work/gcc-13-20221023/gcc/tree-cfgcleanup.cc:1212
0xf7d534 execute_build_cfg
       
/var/tmp/portage/cross-aarch64-linux-gnu/gcc-13.0.0_p20221023/work/gcc-13-20221023/gcc/tree-cfg.cc:378
0xf7d534 execute
       
/var/tmp/portage/cross-aarch64-linux-gnu/gcc-13.0.0_p20221023/work/gcc-13-20221023/gcc/tree-cfg.cc:412

             reply	other threads:[~2022-10-24  6:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-24  6:00 asolokha at gmx dot com [this message]
2022-10-24  8:04 ` [Bug tree-optimization/107369] " marxin at gcc dot gnu.org
2022-10-24  8:50 ` jakub at gcc dot gnu.org
2022-10-24 13:17 ` rguenth at gcc dot gnu.org
2022-10-25  8:42 ` cvs-commit at gcc dot gnu.org
2022-10-25  8:51 ` 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-107369-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: link
Be 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).