public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109541] New: ICE in extract_constrain_insn on sparc64-unknown-linux-gnu when building rhash-1.4.3
Date: Tue, 18 Apr 2023 08:54:03 +0000 [thread overview]
Message-ID: <bug-109541-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109541
Bug ID: 109541
Summary: ICE in extract_constrain_insn on
sparc64-unknown-linux-gnu when building rhash-1.4.3
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: sjames at gcc dot gnu.org
Target Milestone: ---
Host: sparc64-unknown-linux-gnu
Target: sparc64-unknown-linux-gnu
Build: sparc64-unknown-linux-gnu
Created attachment 54880
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54880&action=edit
a-sha512.i
Hit this when building rhash-1.4.3
```
$ sparc64-unknown-linux-gnu-gcc -DUSE_OPENSSL -DNDEBUG -pipe
-ffunction-sections -fdata-sections -fomit-frame-pointer -Wall -W
-Wstrict-prototypes -Wnested-externs -Winline -Wpointer-arith
-Wbad-function-cast -Wmissing-prototypes -Wmissing-declarations
-Wdeclaration-after-statement -O2 -mcpu=niagara4 -pipe -fpic
-DRHASH_XVERSION=0x01040200 librhash/sha512.c
librhash/sha512.c: In function ‘rhash_sha512_process_block’:
librhash/sha512.c:179:1: error: insn does not satisfy its constraints:
179 | }
| ^
(insn 5 2048 675 2 (set (reg/f:DI 72 %f40 [2613])
(mem/u/c:DI (plus:DI (reg:DI 3 %g3 [109])
(symbol_ref:DI ("rhash_k512") [flags 0x2] <var_decl
0xfff800010eb1eea0 rhash_k512>)) [0 S8 A64])) "librhash/sha512.c":158:17 125
{*movdi_insn_sp64}
(expr_list:REG_EQUIV (symbol_ref:DI ("rhash_k512") [flags 0x2] <var_decl
0xfff800010eb1eea0 rhash_k512>)
(nil)))
during RTL pass: reload
librhash/sha512.c:179:1: internal compiler error: in extract_constrain_insn, at
recog.cc:2692
0x18521f7 internal_error(char const*, ...)
???:0
0x2cbd17 fancy_abort(char const*, int, char const*)
???:0
0x2b2b27 _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
???:0
0x2b2bdf _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
???:0
0xa3b7b7 extract_constrain_insn(rtx_insn*)
???:0
0x8c3687 lra(_IO_FILE*)
???:0
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <https://bugs.gentoo.org/> for instructions.
```
---
With the attached preprocessed source, this is enough:
```
$ sparc64-unknown-linux-gnu-gcc -O1 -mcpu=niagara4 -fpic -c a-sha512.i
librhash/sha512.c: In function ‘rhash_sha512_process_block’:
librhash/sha512.c:179:1: error: insn does not satisfy its constraints:
(insn 5 2048 675 2 (set (reg/f:DI 72 %f40 [2613])
(mem/u/c:DI (plus:DI (reg:DI 3 %g3 [109])
(symbol_ref:DI ("rhash_k512") [flags 0x2] <var_decl
0xfff800010ed1e900 rhash_k512>)) [0 S8 A64])) "librhash/sha512.c":158:17 125
{*movdi_insn_sp64}
(expr_list:REG_EQUIV (symbol_ref:DI ("rhash_k512") [flags 0x2] <var_decl
0xfff800010ed1e900 rhash_k512>)
(nil)))
during RTL pass: reload
librhash/sha512.c:179:1: internal compiler error: in extract_constrain_insn, at
recog.cc:2692
0x18521f7 internal_error(char const*, ...)
???:0
0x2cbd17 fancy_abort(char const*, int, char const*)
???:0
0x2b2b27 _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
???:0
0x2b2bdf _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
???:0
0xa3b7b7 extract_constrain_insn(rtx_insn*)
???:0
0x8c3687 lra(_IO_FILE*)
???:0
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <https://bugs.gentoo.org/> for instructions.
```
next reply other threads:[~2023-04-18 8:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 8:54 sjames at gcc dot gnu.org [this message]
2023-04-18 8:54 ` [Bug target/109541] " sjames at gcc dot gnu.org
2023-04-27 22:49 ` [Bug target/109541] [12 regression] " sjames at gcc dot gnu.org
2023-04-27 22:49 ` sjames at gcc dot gnu.org
2023-04-27 22:50 ` sjames at gcc dot gnu.org
2023-05-02 6:50 ` [Bug target/109541] [12/13/14 " rguenth at gcc dot gnu.org
2023-05-08 12:27 ` rguenth at gcc dot gnu.org
2023-05-12 8:03 ` [Bug target/109541] [12/13/14 regression] ICE in extract_constrain_insn on " ebotcazou at gcc dot gnu.org
2023-05-12 10:06 ` ebotcazou at gcc dot gnu.org
2023-05-12 10:07 ` ebotcazou at gcc dot gnu.org
2023-05-12 13:40 ` vmakarov at gcc dot gnu.org
2023-05-31 21:00 ` vmakarov at gcc dot gnu.org
2023-05-31 21:57 ` ebotcazou at gcc dot gnu.org
2023-05-31 21:58 ` ebotcazou at gcc dot gnu.org
2023-05-31 22:24 ` sjames at gcc dot gnu.org
2023-06-04 1:55 ` sjames at gcc dot gnu.org
2023-06-04 7:12 ` ebotcazou at gcc dot gnu.org
2023-06-04 7:24 ` sjames at gcc dot gnu.org
2023-06-05 19:57 ` vmakarov at gcc dot gnu.org
2023-06-06 4:12 ` sjames at gcc dot gnu.org
2023-06-07 15:35 ` cvs-commit at gcc dot gnu.org
2023-06-07 15:50 ` ebotcazou at gcc dot gnu.org
2023-06-16 19:52 ` [Bug target/109541] [12/13 " cvs-commit at gcc dot gnu.org
2023-06-20 8:08 ` [Bug target/109541] [12 " ebotcazou 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-109541-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).