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 translation/107301] New: [13 Regression] ICE in duplicate_block, at cfghooks.cc:1114
Date: Tue, 18 Oct 2022 03:49:36 +0000	[thread overview]
Message-ID: <bug-107301-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 107301
           Summary: [13 Regression] ICE in duplicate_block, at
                    cfghooks.cc:1114
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: translation
          Assignee: unassigned at gcc dot gnu.org
          Reporter: asolokha at gmx dot com
  Target Milestone: ---

gcc 13.0.0 20221016 snapshot (g:6366e3e8847af98d4728d55951534769d034d02a) ICEs
when compiling the following testcase w/ -O2:

__attribute__ ((pure, returns_twice)) int
foo (int x)
{
  int a;

  a = x ? 3 : 0;
  x /= a;
  a = foo (x);
  if (x == a)
    __builtin_unreachable ();

  return 0;
}

% gcc-13 -O2 -c ybzomcfk.c
during GIMPLE pass: isolate-paths
ybzomcfk.c: In function 'foo':
ybzomcfk.c:2:1: internal compiler error: in duplicate_block, at
cfghooks.cc:1114
    2 | foo (int x)
      | ^~~
0x6a97c8 duplicate_block(basic_block_def*, edge_def*, basic_block_def*,
copy_bb_data*)
       
/var/tmp/portage/sys-devel/gcc-13.0.0_p20221016/work/gcc-13-20221016/gcc/cfghooks.cc:1114
0x1d679dc isolate_path(basic_block_def*, basic_block_def*, edge_def*, gimple*,
tree_node*, bool)
       
/var/tmp/portage/sys-devel/gcc-13.0.0_p20221016/work/gcc-13-20221016/gcc/gimple-ssa-isolate-paths.cc:157
0x1d6970b find_implicit_erroneous_behavior
       
/var/tmp/portage/sys-devel/gcc-13.0.0_p20221016/work/gcc-13-20221016/gcc/gimple-ssa-isolate-paths.cc:770
0x1d6970b gimple_ssa_isolate_erroneous_paths
       
/var/tmp/portage/sys-devel/gcc-13.0.0_p20221016/work/gcc-13-20221016/gcc/gimple-ssa-isolate-paths.cc:932
0x1d6970b execute
       
/var/tmp/portage/sys-devel/gcc-13.0.0_p20221016/work/gcc-13-20221016/gcc/gimple-ssa-isolate-paths.cc:987

             reply	other threads:[~2022-10-18  3:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18  3:49 asolokha at gmx dot com [this message]
2022-10-18  7:34 ` [Bug tree-optimization/107301] " rguenth at gcc dot gnu.org
2022-10-18  7:54 ` rguenth at gcc dot gnu.org
2022-10-18  7:58 ` marxin at gcc dot gnu.org
2022-10-18  8:31 ` cvs-commit at gcc dot gnu.org
2022-10-18  8:31 ` 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-107301-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).