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++/105953] New: [12/13 Regression] ICE in extract_insn, at recog.cc:2791
Date: Mon, 13 Jun 2022 17:48:53 +0000	[thread overview]
Message-ID: <bug-105953-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 105953
           Summary: [12/13 Regression] ICE in extract_insn, at
                    recog.cc:2791
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gscfq@t-online.de
  Target Milestone: ---

Started between 20211212 and 20211219,
with file g++.target/i386/pr100738-1.C :


$ g++-13-20220612 -c pr100738-1.C -O2 -mavx512vl -mabi=ms
pr100738-1.C: In function 'v4si foo_1(v16qi, v4si, v4si, v4si)':
pr100738-1.C:13:1: error: unrecognizable insn:
   13 | }
      | ^
(insn 28 27 21 2 (set (subreg:V16QI (reg:V4SI 84 [ <retval> ]) 0)
        (unspec:V16QI [
                (reg:V16QI 101)
                (mem/c:V16QI (reg:DI 100) [1 d+0 S16 A128])
                (subreg:V16QI (lt:V4SI (mem/c:V4SI (reg:DI 98) [0 a+0 S16
A128])
                        (const_vector:V4SI [
                                (const_int 0 [0]) repeated x4
                            ])) 0)
            ] UNSPEC_BLENDV)) "pr100738-1.C":12:31 -1
     (expr_list:REG_DEAD (reg:V16QI 101)
        (expr_list:REG_DEAD (reg:DI 100)
            (expr_list:REG_DEAD (reg:DI 98)
                (nil)))))
during RTL pass: ira
pr100738-1.C:13:1: internal compiler error: in extract_insn, at recog.cc:2791
0x698229 _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
        ../../gcc/rtl-error.cc:108
0x698248 _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
        ../../gcc/rtl-error.cc:116
0xd24317 extract_insn(rtx_insn*)
        ../../gcc/recog.cc:2791
0xbe6c10 ira_remove_insn_scratches(rtx_insn*, bool, _IO_FILE*, rtx_def*
(*)(rtx_def*))
        ../../gcc/ira.cc:5356
0xbe78f5 remove_scratches
        ../../gcc/ira.cc:5400
0xbe78f5 ira
        ../../gcc/ira.cc:5724
0xbe78f5 execute
        ../../gcc/ira.cc:6083

             reply	other threads:[~2022-06-13 17:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13 17:48 gscfq@t-online.de [this message]
2022-06-14  6:49 ` [Bug target/105953] " ubizjak at gmail dot com
2022-06-14  8:19 ` rguenth at gcc dot gnu.org
2022-06-15  5:55 ` cvs-commit at gcc dot gnu.org
2022-06-15  5:57 ` cvs-commit at gcc dot gnu.org
2022-06-15  7:16 ` crazylht at gmail dot com
2023-03-23  0:16 ` 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-105953-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).