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/94420] New: ICE error: insn does not satisfy its constraints
Date: Tue, 31 Mar 2020 05:45:30 +0000 [thread overview]
Message-ID: <bug-94420-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94420
Bug ID: 94420
Summary: ICE error: insn does not satisfy its constraints
Product: gcc
Version: 10.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, segher at gcc dot gnu.org
Target Milestone: ---
Host: powerpc64-linux-gnu
Target: powerpc64-linux-gnu
It's reduced from moonjit bug:
https://github.com/moonjit/moonjit/issues/74
$ cat /tmp/moonjit.i
register long int *a __asm__("r2");
long int b;
void fn1() {
long *p = &b;
for (;;)
*p++ = (long int)a;
}
$ ./xgcc -B. /tmp/moonjit.i -c
$ ./xgcc -B. /tmp/moonjit.i -c -O2
/tmp/moonjit.i: In function ‘fn1’:
/tmp/moonjit.i:8:1: error: insn does not satisfy its constraints:
8 | }
| ^
(insn 7 5 8 2 (set (reg/f:DI 121)
(unspec:DI [
(symbol_ref:DI ("*.LANCHOR0") [flags 0x182])
(reg/f:DI 118 [ a.2_2 ])
] UNSPEC_TOCREL)) 731 {*tocrefdi}
(expr_list:REG_EQUAL (symbol_ref:DI ("*.LANCHOR0") [flags 0x182])
(nil)))
during RTL pass: combine
/tmp/moonjit.i:8:1: internal compiler error: in extract_constrain_insn_cached,
at recog.c:2207
0x10f19513 _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
../../gcc/rtl-error.c:108
0x10f195a7 _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
../../gcc/rtl-error.c:119
0x10ea179f extract_constrain_insn_cached(rtx_insn*)
../../gcc/recog.c:2207
0x11b779b7 get_attr_prefixed(rtx_insn*)
../../gcc/config/rs6000/rs6000.md:647
0x116c09df rs6000_insn_cost
../../gcc/config/rs6000/rs6000.c:21141
0x10f30097 insn_cost(rtx_insn*, bool)
../../gcc/rtlanal.c:5440
0x11ef525b combine_instructions
../../gcc/combine.c:1236
0x11f2b06f rest_of_handle_combine
../../gcc/combine.c:15059
0x11f2b1e3 execute
../../gcc/combine.c:15104
next reply other threads:[~2020-03-31 5:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 5:45 marxin at gcc dot gnu.org [this message]
2020-03-31 11:08 ` [Bug target/94420] [8/9/10 Regression] " jakub at gcc dot gnu.org
2020-03-31 13:53 ` segher at gcc dot gnu.org
2020-03-31 14:07 ` jakub at gcc dot gnu.org
2020-03-31 14:35 ` segher at gcc dot gnu.org
2020-03-31 14:36 ` segher at gcc dot gnu.org
2020-03-31 14:38 ` jakub at gcc dot gnu.org
2020-03-31 14:45 ` segher at gcc dot gnu.org
2020-03-31 14:46 ` segher at gcc dot gnu.org
2020-03-31 14:48 ` segher at gcc dot gnu.org
2020-04-01 8:59 ` rguenth at gcc dot gnu.org
2020-04-01 17:01 ` cvs-commit at gcc dot gnu.org
2020-04-18 17:00 ` law at redhat dot com
2020-04-18 21:43 ` [Bug target/94420] [8/9 " segher at gcc dot gnu.org
2021-05-14 9:53 ` [Bug target/94420] [9 " jakub at gcc dot gnu.org
2021-06-01 8:17 ` rguenth at gcc dot gnu.org
2022-05-27 8:50 ` rguenth 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-94420-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).