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/99347] New: [9/10/11 Regression] ICE in create_block_for_bookkeeping, at sel-sched.c:4549
Date: Tue, 02 Mar 2021 18:56:50 +0000	[thread overview]
Message-ID: <bug-99347-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 99347
           Summary: [9/10/11 Regression] ICE in
                    create_block_for_bookkeeping, at sel-sched.c:4549
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gscfq@t-online.de
  Target Milestone: ---

Using following options and testfile gcc.dg/tree-ssa/ifc-pr69489-2.c
This issue started with r9, between 20190331 and 20190414 :
(under the hood related to pr95636 ?)


$ gcc-11-20210228 -c ifc-pr69489-2.c -O1 -fvar-tracking-assignments
-fschedule-insns -fselective-scheduling
cc1: warning: var-tracking-assignments changes selective scheduling
during RTL pass: sched1
ifc-pr69489-2.c: In function 'foo':
ifc-pr69489-2.c:15:1: internal compiler error: in create_block_for_bookkeeping,
at sel-sched.c:4549
   15 | }
      | ^
0xb2c995 create_block_for_bookkeeping
        ../../gcc/sel-sched.c:4549
0xb2c995 find_place_for_bookkeeping
        ../../gcc/sel-sched.c:4686
0xb2c995 generate_bookkeeping_insn
        ../../gcc/sel-sched.c:4786
0xb2c995 move_op_at_first_insn
        ../../gcc/sel-sched.c:6063
0xb2d037 code_motion_path_driver
        ../../gcc/sel-sched.c:6657
0xb2d2ce code_motion_process_successors
        ../../gcc/sel-sched.c:6342
0xb2d2ce code_motion_path_driver
        ../../gcc/sel-sched.c:6608
0xb2d703 move_op
        ../../gcc/sel-sched.c:6702
0xb2d703 move_exprs_to_boundary
        ../../gcc/sel-sched.c:5223
0xb2d703 schedule_expr_on_boundary
        ../../gcc/sel-sched.c:5436
0xb30b94 fill_insns
        ../../gcc/sel-sched.c:5578
0xb32943 schedule_on_fences
        ../../gcc/sel-sched.c:7353
0xb32943 sel_sched_region_2
        ../../gcc/sel-sched.c:7491
0xb334dd sel_sched_region_1
        ../../gcc/sel-sched.c:7533
0xb33fab sel_sched_region(int)
        ../../gcc/sel-sched.c:7634
0xb349e9 run_selective_scheduling()
        ../../gcc/sel-sched.c:7720
0xb1642d rest_of_handle_sched
        ../../gcc/sched-rgn.c:3724
0xb1642d execute
        ../../gcc/sched-rgn.c:3834

             reply	other threads:[~2021-03-02 18:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-02 18:56 gscfq@t-online.de [this message]
2021-03-02 18:57 ` [Bug c/99347] " gscfq@t-online.de
2021-03-02 19:13 ` [Bug c/99347] [9/10/11 Regression] ICE in create_block_for_bookkeeping, at sel-sched.c:4549 since r9-6859-g25eafae67f186cfa marxin at gcc dot gnu.org
2021-03-02 19:15 ` marxin at gcc dot gnu.org
2021-03-03  8:28 ` [Bug rtl-optimization/99347] " rguenth at gcc dot gnu.org
2021-03-04 15:17 ` law at gcc dot gnu.org
2021-06-01  8:19 ` [Bug rtl-optimization/99347] [9/10/11/12 " rguenth at gcc dot gnu.org
2022-05-27  9:44 ` [Bug rtl-optimization/99347] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:43 ` jakub at gcc dot gnu.org
2022-11-09  5:58 ` 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-99347-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).