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 target/96127] New: ICE in extract_insn, at recog.c:2294
Date: Thu, 09 Jul 2020 07:50:42 +0000 [thread overview]
Message-ID: <bug-96127-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96127
Bug ID: 96127
Summary: ICE in extract_insn, at recog.c:2294
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
CC: krebbel at gcc dot gnu.org
Target Milestone: ---
Host: x86_64-linux-gnu
Target: s390x-linux-gnu
The following fails:
$ s390x-linux-gnu-gcc
/home/marxin/Programming/gcc/gcc/testsuite/gcc.dg/tree-ssa/pr92085-2.c -O1
-fno-tree-loop-im --param=sccvn-max-alias-queries-per-access=0
/home/marxin/Programming/gcc/gcc/testsuite/gcc.dg/tree-ssa/pr92085-2.c: In
function ‘c1’:
/home/marxin/Programming/gcc/gcc/testsuite/gcc.dg/tree-ssa/pr92085-2.c:10:18:
warning: initialization of ‘long int *’ from incompatible pointer type ‘int *’
[-Wincompatible-pointer-types]
10 | long int *th = &dk;
| ^
/home/marxin/Programming/gcc/gcc/testsuite/gcc.dg/tree-ssa/pr92085-2.c:20:22:
warning: initialization of ‘long int *’ from incompatible pointer type ‘int *’
[-Wincompatible-pointer-types]
20 | long int *lq = &oz;
| ^
/home/marxin/Programming/gcc/gcc/testsuite/gcc.dg/tree-ssa/pr92085-2.c:29:1:
error: unrecognizable insn:
29 | }
| ^
(insn 27 26 28 6 (parallel [
(set (strict_low_part (subreg:SI (reg/v:DI 64 [ oz+-4 ]) 4))
(subreg:SI (reg:DI 68) 4))
(clobber (reg:CC 33 %cc))
])
"/home/marxin/Programming/gcc/gcc/testsuite/gcc.dg/tree-ssa/pr92085-2.c":22:19
-1
(nil))
during RTL pass: vregs
/home/marxin/Programming/gcc/gcc/testsuite/gcc.dg/tree-ssa/pr92085-2.c:29:1:
internal compiler error: in extract_insn, at recog.c:2294
0x590f78 _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-s390x/build/gcc/rtl-error.c:108
0x590f94 _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-s390x/build/gcc/rtl-error.c:116
0x590408 extract_insn(rtx_insn*)
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-s390x/build/gcc/recog.c:2294
0x80800f instantiate_virtual_regs_in_insn
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-s390x/build/gcc/function.c:1607
0x80800f instantiate_virtual_regs
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-s390x/build/gcc/function.c:1977
0x80800f execute
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-s390x/build/gcc/function.c:2026
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
next reply other threads:[~2020-07-09 7:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 7:50 marxin at gcc dot gnu.org [this message]
2020-07-09 7:52 ` [Bug target/96127] " marxin at gcc dot gnu.org
2020-07-17 7:36 ` cvs-commit at gcc dot gnu.org
2020-08-30 5:01 ` asolokha at gmx dot com
2021-09-02 16:59 ` redi at gcc dot gnu.org
2021-09-06 9:23 ` krebbel at gcc dot gnu.org
2023-12-03 18:23 ` jakub at gcc dot gnu.org
2023-12-07 8:45 ` cvs-commit 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-96127-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).