public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/106342] [12/13 Regression] internal compiler error: in extract_insn, at recog.cc:2791
Date: Tue, 19 Jul 2022 18:09:13 +0000	[thread overview]
Message-ID: <bug-106342-4-TmmabiNWEY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106342-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Ah, -march=z14 is needed:

$ ./cc1 -quiet -O2 pr104612.c -Iinclude -march=z14 -mtune=z15
pr104612.c: In function ‘foo’:
pr104612.c:15:1: error: unrecognizable insn:
   15 | }
      | ^
(insn 9 8 10 2 (set (reg:V2SF 61 [ vect__2.10 ])
        (ior:V2SF (and:V2SF (subreg:V2SF (reg/v:DI 63 [ v ]) 0)
                (reg:V2SF 65))
            (and:V2SF (not:V2SF (reg:V2SF 65))
                (reg:V2SF 64)))) "pr104612.c":12:11 -1
     (nil))
during RTL pass: vregs
pr104612.c:15:1: internal compiler error: in extract_insn, at recog.cc:2791
0x68616c _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
        /home/mpolacek/src/gcc/gcc/rtl-error.cc:108
0x686188 _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
        /home/mpolacek/src/gcc/gcc/rtl-error.cc:116
0x684bf1 extract_insn(rtx_insn*)
        /home/mpolacek/src/gcc/gcc/recog.cc:2791
0xaabc10 instantiate_virtual_regs_in_insn
        /home/mpolacek/src/gcc/gcc/function.cc:1611
0xaabc10 instantiate_virtual_regs
        /home/mpolacek/src/gcc/gcc/function.cc:1985
0xaabc10 execute
        /home/mpolacek/src/gcc/gcc/function.cc:2034

  parent reply	other threads:[~2022-07-19 18:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18 15:32 [Bug target/106342] New: " mpolacek at gcc dot gnu.org
2022-07-18 15:33 ` [Bug target/106342] " mpolacek at gcc dot gnu.org
2022-07-18 15:35 ` mpolacek at gcc dot gnu.org
2022-07-19  6:40 ` rguenth at gcc dot gnu.org
2022-07-19 10:34 ` marxin at gcc dot gnu.org
2022-07-19 18:09 ` mpolacek at gcc dot gnu.org [this message]
2022-07-20  8:13 ` [Bug target/106342] [12/13 Regression] internal compiler error: in extract_insn, at recog.cc:2791 since r12-4240-g2b8453c401b699 marxin at gcc dot gnu.org
2022-07-28 17:08 ` jakub at gcc dot gnu.org
2022-07-28 22:29 ` iii at linux dot ibm.com
2022-07-29  7:31 ` jakub at gcc dot gnu.org
2022-08-10 10:36 ` jakub at gcc dot gnu.org
2023-04-19 14:32 ` [Bug target/106342] [12/13/14 " iii at linux dot ibm.com
2023-05-08 12:25 ` rguenth at gcc dot gnu.org
2024-03-15  1:15 ` 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-106342-4-TmmabiNWEY@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).