public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "andress.barajas at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/112115] New: SH4 ICE: in extract_constrain_insn, at recog.cc:2692 with -mlra
Date: Sat, 28 Oct 2023 12:20:04 +0000 [thread overview]
Message-ID: <bug-112115-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112115
Bug ID: 112115
Summary: SH4 ICE: in extract_constrain_insn, at recog.cc:2692
with -mlra
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: andress.barajas at gmail dot com
Target Milestone: ---
Target: sh*-*-*
Created attachment 56322
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56322&action=edit
Temp file with ICE error
CFLAGS:
-std=c2x -O2 -ml -m4-single-only -ffast-math -mfsrra -mfsca
-matomic-model=soft-imask -ftls-model=local-exec -mlra -fomit-frame-pointer
-fno-builtin
ICE:
beep.c:200:1: error: insn does not satisfy its constraints:
200 | }
| ^
(insn 1726 1725 127 5 (parallel [
(set (reg:SF 65 fr1 [735])
(reg:SF 0 r0 [736]))
(use (reg:SI 154 fpscr0))
(clobber (scratch:SI))
]) "beep.c":78:17 214 {movsf_ie}
(expr_list:REG_DEAD (reg:SF 0 r0 [736])
(nil)))
during RTL pass: cprop_hardreg
beep.c:200:1: internal compiler error: in extract_constrain_insn, at
recog.cc:2692
next reply other threads:[~2023-10-28 12:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-28 12:20 andress.barajas at gmail dot com [this message]
2023-10-28 12:47 ` [Bug c/112115] SH4 ICE: in extract_constrain_insn, at recog.cc:2692 with -mlra (VMUBEEP) andress.barajas at gmail dot com
2023-10-28 17:49 ` [Bug target/112115] " pinskia at gcc dot gnu.org
2023-10-28 17:49 ` pinskia at gcc dot gnu.org
2023-10-28 17:50 ` pinskia at gcc dot gnu.org
2023-10-28 17:50 ` pinskia at gcc dot gnu.org
2023-10-28 17:50 ` pinskia at gcc dot gnu.org
2023-10-28 17:51 ` pinskia 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-112115-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).