public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/108892] [13 Regression] ICE: in curr_insn_transform, at lra-constraints.cc:4168 (unable to generate reloads for: {*mvconst_internal}) at -Og on riscv64
Date: Thu, 23 Feb 2023 21:20:09 +0000 [thread overview]
Message-ID: <bug-108892-4-1ALfQVsBaq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108892-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108892
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |blocker
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
The backend is really broken:
(define_insn_and_split "*mvconst_internal"
[(set (match_operand:GPR 0 "register_operand" "=r")
(match_operand:GPR 1 "splittable_const_int_operand" "i"))]
"!(p2m1_shift_operand (operands[1], <MODE>mode)
|| high_mask_shift_operand (operands[1], <MODE>mode))"
"#"
"&& 1"
[(const_int 0)]
{
riscv_move_integer (operands[0], operands[0], INTVAL (operands[1]),
<MODE>mode, TRUE);
DONE;
})
There are multiple insn patterns which match and guess what it is just broken.
next prev parent reply other threads:[~2023-02-23 21:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 19:52 [Bug rtl-optimization/108892] New: " zsojka at seznam dot cz
2023-02-23 8:39 ` [Bug target/108892] " rguenth at gcc dot gnu.org
2023-02-23 21:20 ` pinskia at gcc dot gnu.org [this message]
2023-02-23 21:21 ` [Bug target/108892] [13 Regression] unable to generate reloads for at -Og on riscv64 since r13-4907 pinskia at gcc dot gnu.org
2023-03-10 12:29 ` law at gcc dot gnu.org
2023-03-27 10:59 ` [Bug middle-end/108892] " rguenth at gcc dot gnu.org
2023-03-27 13:16 ` law at gcc dot gnu.org
2023-04-05 15:19 ` cvs-commit at gcc dot gnu.org
2023-04-05 15:20 ` 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-108892-4-1ALfQVsBaq@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).