public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vsevolod.livinskiy at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/105587] New: [13 Regression] ICE in extract_insn, at recog.cc:2791 (error: unrecognizable insn)
Date: Thu, 12 May 2022 22:44:20 +0000	[thread overview]
Message-ID: <bug-105587-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 105587
           Summary: [13 Regression] ICE in extract_insn, at recog.cc:2791
                    (error: unrecognizable insn)
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: vsevolod.livinskiy at gmail dot com
  Target Milestone: ---

Link to the Compiler Explorer: https://godbolt.org/z/bboxEaWWx

Reproducer:
extern short arr_108[][4][2][24][12], arr_110[][4][2][24][12];
void test() {
  for (unsigned a = 0; a < 2; a += 2)
    for (unsigned b = 4; b < 22; b++)
      for (int c = 1; c < 11; c++)
        arr_110[0][0][a][b][c] = (unsigned char)arr_108[0][0][a][b][c];
}

Error:
>$ g++ -O3 -c func.cpp   
func.cpp: In function 'void test()':
func.cpp:7:1: error: unrecognizable insn:
    7 | }
      | ^
(insn 18 17 19 2 (set (reg:V1TI 202)
        (ashift:V1TI (subreg:V1TI (reg:V8HI 117 [ vect__15.12 ]) 0)
            (const_int 4294967264 [0xffffffe0]))) "func.cpp":6:70 -1
     (nil))
during RTL pass: vregs
func.cpp:7:1: internal compiler error: in extract_insn, at recog.cc:2791
0x85ea0e _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
        /testing/gcc/gcc_src_master/gcc/rtl-error.cc:108
0x85ea30 _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
        /testing/gcc/gcc_src_master/gcc/rtl-error.cc:116
0x85cf23 extract_insn(rtx_insn*)
        /testing/gcc/gcc_src_master/gcc/recog.cc:2791
0xecdac5 instantiate_virtual_regs_in_insn
        /testing/gcc/gcc_src_master/gcc/function.cc:1611
0xecdac5 instantiate_virtual_regs
        /testing/gcc/gcc_src_master/gcc/function.cc:1985
0xecdac5 execute
        /testing/gcc/gcc_src_master/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.

gcc version 13.0.0 20220512 (7f78783dbedca0183d193e475262ca3c489fd365)

             reply	other threads:[~2022-05-12 22:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-12 22:44 vsevolod.livinskiy at gmail dot com [this message]
2022-05-13  6:14 ` [Bug tree-optimization/105587] [13 Regression] ICE in extract_insn, at recog.cc:2791 (error: unrecognizable insn) since r13-210-gfcda0efccad41eba marxin at gcc dot gnu.org
2022-05-13  6:22 ` [Bug target/105587] " pinskia at gcc dot gnu.org
2022-05-13  7:55 ` rguenth at gcc dot gnu.org
2022-05-13  7:58 ` crazylht at gmail dot com
2022-05-16  0:30 ` cvs-commit at gcc dot gnu.org
2022-05-16  0:43 ` crazylht at gmail dot com
2022-05-18 16:35 ` slyfox at gcc dot gnu.org
2022-09-13 18:50 ` asolokha at gmx dot com
2022-09-13 19:20 ` marxin 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-105587-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).