public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/107969] New: ICE in extract_insn, at recog.cc:2791 since r13-3292-gc2565a31c1622ab0
Date: Mon, 05 Dec 2022 08:47:28 +0000	[thread overview]
Message-ID: <bug-107969-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 107969
           Summary: ICE in extract_insn, at recog.cc:2791 since
                    r13-3292-gc2565a31c1622ab0
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: marxin at gcc dot gnu.org
                CC: jakub at gcc dot gnu.org
  Target Milestone: ---

The follow crashes:

$ cat prec.c
int i;
__bf16 f;

void
bar() { i *= 0 <= f; }

$ gcc prec.c -Ofast -fexcess-precision=16 -m32 -msoft-float -c
prec.c: In function ‘bar’:
prec.c:5:22: error: unrecognizable insn:
    5 | bar() { i *= 0 <= f; }
      |                      ^
(insn 10 9 12 2 (set (reg:CCFP 17 flags)
        (compare:CCFP (reg:SF 89)
            (reg:SF 90))) "prec.c":5:11 -1
     (nil))
during RTL pass: vregs
prec.c:5:22: internal compiler error: in extract_insn, at recog.cc:2791
0x75acd4 _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
        /home/marxin/Programming/gcc/gcc/rtl-error.cc:108
0x75acf0 _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
        /home/marxin/Programming/gcc/gcc/rtl-error.cc:116
0x7592b5 extract_insn(rtx_insn*)
        /home/marxin/Programming/gcc/gcc/recog.cc:2791
0xb88100 instantiate_virtual_regs_in_insn
        /home/marxin/Programming/gcc/gcc/function.cc:1611
0xb88100 instantiate_virtual_regs
        /home/marxin/Programming/gcc/gcc/function.cc:1985
0xb88100 execute
        /home/marxin/Programming/gcc/gcc/function.cc:2034
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.

             reply	other threads:[~2022-12-05  8:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-05  8:47 marxin at gcc dot gnu.org [this message]
2022-12-05  8:47 ` [Bug c/107969] " marxin at gcc dot gnu.org
2022-12-05  8:56 ` [Bug target/107969] " pinskia at gcc dot gnu.org
2022-12-05  9:19 ` marxin at gcc dot gnu.org
2022-12-05 16:30 ` jakub at gcc dot gnu.org
2022-12-05 16:30 ` jakub at gcc dot gnu.org
2022-12-06 11:17 ` cvs-commit at gcc dot gnu.org
2022-12-06 11:17 ` [Bug target/107969] [13 Regression] " 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-107969-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).