public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112445] [14 Regression] ICE: in lra_split_hard_reg_for, at lra-assigns.cc:1861 unable to find a register to spill: {*umulditi3_1} with -O -march=cascadelake -fwrapv since r14-4968-g89e5d902fc55ad
Date: Wed, 22 Nov 2023 20:03:41 +0000 [thread overview]
Message-ID: <bug-112445-4-BCfJ6nTqOP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112445-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112445
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Just changing
--- i386.md.xx 2023-11-22 09:47:22.746637132 +0100
+++ i386.md 2023-11-22 20:38:07.216218697 +0100
@@ -9984,7 +9984,7 @@
[(set (match_operand:<DWI> 0 "register_operand" "=r,A")
(mult:<DWI>
(zero_extend:<DWI>
- (match_operand:DWIH 1 "register_operand" "%d,a"))
+ (match_operand:DWIH 1 "register_operand" "%d,0"))
(zero_extend:<DWI>
(match_operand:DWIH 2 "nonimmediate_operand" "rm,rm"))))
(clobber (reg:CC FLAGS_REG))]
makes the testcase pass. A question is how RA treats 0 constraint when the two
operands have different modes, if it is basically the same as a in that case,
meaning that the first input operand will never be in %rdx even when the A
constraint contains %rax and %rdx registers (but the double-word mode implies
it must be low part in %rax high part in $rdx).
next prev parent reply other threads:[~2023-11-22 20:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 16:06 [Bug target/112445] New: [14 Regression] ICE: in lra_split_hard_reg_for, at lra-assigns.cc:1861 unable to find a register to spill: {*umulditi3_1} with -O -march=cascadelake -fwrapv zsojka at seznam dot cz
2023-11-09 3:06 ` [Bug target/112445] " pinskia at gcc dot gnu.org
2023-11-09 3:16 ` pinskia at gcc dot gnu.org
2023-11-09 5:59 ` zsojka at seznam dot cz
2023-11-15 10:13 ` [Bug target/112445] [14 Regression] ICE: in lra_split_hard_reg_for, at lra-assigns.cc:1861 unable to find a register to spill: {*umulditi3_1} with -O -march=cascadelake -fwrapv since r14-4968-g89e5d902fc55ad sjames at gcc dot gnu.org
2023-11-22 19:25 ` jakub at gcc dot gnu.org
2023-11-22 20:03 ` jakub at gcc dot gnu.org [this message]
2023-11-22 20:34 ` ubizjak at gmail dot com
2023-11-22 20:46 ` vmakarov at gcc dot gnu.org
2023-12-01 16:54 ` cvs-commit at gcc dot gnu.org
2023-12-06 16:50 ` jakub 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-112445-4-BCfJ6nTqOP@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).