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/102850] New: [10/11/12 Regression] ICE in begin_move_insn, at sched-ebb.c:196
Date: Wed, 20 Oct 2021 03:03:54 +0000	[thread overview]
Message-ID: <bug-102850-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 102850
           Summary: [10/11/12 Regression] ICE in begin_move_insn, at
                    sched-ebb.c:196
           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: ---
            Target: x86_64-pc-linux-gnu, aarch64-linux-gnu

Probably a duplicate of PR91161.

gcc-12.0.0-alpha20211017 snapshot (g:5d4d64faa71a6389bfb76bfb3334b63360cf62c0)
ICEs when compiling the following testcase w/ -O2 -fsched2-use-superblocks:

volatile int x;
int y;

int
baz (void);

void
bar (void)
{
  for (;;)
    ++y;
}

void
foo (int a)
{
  int z;

  if (a && baz ())
    {
      z = x;
      bar ();
    }
}

% x86_64-pc-linux-gnu-gcc-12.0.0 -O2 -fsched2-use-superblocks -c sakxrhiw.c
during RTL pass: sched2
sakxrhiw.c: In function 'foo':
sakxrhiw.c:24:1: internal compiler error: in begin_move_insn, at
sched-ebb.c:196
   24 | }
      | ^
0x82e8f3 begin_move_insn
       
/var/tmp/portage/sys-devel/gcc-12.0.0_alpha20211017/work/gcc-12-20211017/gcc/sched-ebb.c:196
0x82e8f3 begin_move_insn
       
/var/tmp/portage/sys-devel/gcc-12.0.0_alpha20211017/work/gcc-12-20211017/gcc/sched-ebb.c:144
0x1bc30f2 commit_schedule
       
/var/tmp/portage/sys-devel/gcc-12.0.0_alpha20211017/work/gcc-12-20211017/gcc/haifa-sched.c:6245
0x1bc30f2 schedule_block(basic_block_def**, void*)
       
/var/tmp/portage/sys-devel/gcc-12.0.0_alpha20211017/work/gcc-12-20211017/gcc/haifa-sched.c:7083
0x1ca13be schedule_ebb(rtx_insn*, rtx_insn*, bool)
       
/var/tmp/portage/sys-devel/gcc-12.0.0_alpha20211017/work/gcc-12-20211017/gcc/sched-ebb.c:536
0x1ca19c9 schedule_ebbs()
       
/var/tmp/portage/sys-devel/gcc-12.0.0_alpha20211017/work/gcc-12-20211017/gcc/sched-ebb.c:655
0xe414bc rest_of_handle_sched2
       
/var/tmp/portage/sys-devel/gcc-12.0.0_alpha20211017/work/gcc-12-20211017/gcc/sched-rgn.c:3740
0xe414bc execute
       
/var/tmp/portage/sys-devel/gcc-12.0.0_alpha20211017/work/gcc-12-20211017/gcc/sched-rgn.c:3878

             reply	other threads:[~2021-10-20  3:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-20  3:03 asolokha at gmx dot com [this message]
2021-10-20  6:56 ` [Bug rtl-optimization/102850] [10/11/12 Regression] ICE in begin_move_insn, at sched-ebb.c:196 since r10-3502-g2e2c6df346ab70ed marxin at gcc dot gnu.org
2021-10-20  7:11 ` rguenth at gcc dot gnu.org
2022-06-28 10:46 ` [Bug rtl-optimization/102850] [10/11/12/13 " jakub at gcc dot gnu.org
2023-07-07 10:41 ` [Bug rtl-optimization/102850] [11/12/13/14 " 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-102850-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).