public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/97972] [9/10/11 Regression] ICE in moving_insn_creates_bookkeeping_block_p, at sel-sched.c:2031 since r9-2064-gc4c5ad1d6d1e1e1f
Date: Wed, 25 Nov 2020 21:03:53 +0000	[thread overview]
Message-ID: <bug-97972-4-3Cy5UDsw4Q@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97972-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Segher Boessenkool <segher at gcc dot gnu.org> ---
#0  moving_insn_creates_bookkeeping_block_p (through_insn=0x3fffb5b23138, 
    insn=0x3fffb5b736c0) at /home/segher/src/gcc/gcc/sel-sched.c:2031

It crashes here because the insn is not in any BB; which is correct
actually, because the insn has been deleted!

It is deleted in sel-sched, and it was created there as well.  I don't
see anything wrong in the earlier debug dump; afaics this was just
expose by the 2-2 combine thing.

  parent reply	other threads:[~2020-11-25 21:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-24 18:28 [Bug c/97972] New: [10/11 Regression] ICE in moving_insn_creates_bookkeeping_block_p, at sel-sched.c:2031 gscfq@t-online.de
2020-11-25  8:07 ` [Bug c/97972] [9/10/11 Regression] ICE in moving_insn_creates_bookkeeping_block_p, at sel-sched.c:2031 since r9-2064-gc4c5ad1d6d1e1e1f marxin at gcc dot gnu.org
2020-11-25  8:19 ` [Bug rtl-optimization/97972] " rguenth at gcc dot gnu.org
2020-11-25 20:09 ` segher at gcc dot gnu.org
2020-11-25 21:03 ` segher at gcc dot gnu.org [this message]
2021-01-14  9:46 ` rguenth at gcc dot gnu.org
2021-06-01  8:19 ` [Bug rtl-optimization/97972] [9/10/11/12 " rguenth at gcc dot gnu.org
2022-05-27  9:43 ` [Bug rtl-optimization/97972] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:42 ` jakub at gcc dot gnu.org
2023-02-14 19:33 ` gscfq@t-online.de
2023-07-07 10:38 ` [Bug rtl-optimization/97972] [11/12/13/14 " rguenth at gcc dot gnu.org
2024-03-10 23:12 ` law 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-97972-4-3Cy5UDsw4Q@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).