public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/111010] [13/14 regression] error: unable to find a register to spill compiling GCDAProfiling.c since r13-5092-g4e0b504f26f78f
Date: Fri, 18 Aug 2023 12:12:06 +0000 [thread overview]
Message-ID: <bug-111010-4-rG4cpg0Pxb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111010-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111010
--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
diff --git a/gcc/config/i386/i386.md b/gcc/config/i386/i386.md
index f3a3305ac4f..d38b9d764d8 100644
--- a/gcc/config/i386/i386.md
+++ b/gcc/config/i386/i386.md
@@ -11511,7 +11511,7 @@
})
(define_insn_and_split "*concat<mode><dwi>3_3"
- [(set (match_operand:<DWI> 0 "nonimmediate_operand" "=ro,r,r,&r")
+ [(set (match_operand:<DWI> 0 "nonimmediate_operand" "=ro,r,r,!&r")
(any_or_plus:<DWI>
(ashift:<DWI>
(zero_extend:<DWI>
fixes the issue for me, this disparages the &r,m,m alternative since
that makes any reloading difficult(?) and the early-clobber output
makes register pressure even harder to deal with.
next prev parent reply other threads:[~2023-08-18 12:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 9:42 [Bug target/111010] New: [13 regression] error: unable to find a register to spill compiling GCDAProfiling.c ro at gcc dot gnu.org
2023-08-14 9:43 ` [Bug target/111010] " ro at gcc dot gnu.org
2023-08-14 9:44 ` ro at gcc dot gnu.org
2023-08-14 11:14 ` rguenth at gcc dot gnu.org
2023-08-14 14:38 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-08-14 14:54 ` ro at gcc dot gnu.org
2023-08-18 11:04 ` [Bug target/111010] [13/14 " ro at gcc dot gnu.org
2023-08-18 12:03 ` [Bug target/111010] [13/14 regression] error: unable to find a register to spill compiling GCDAProfiling.c since r13-5092-g4e0b504f26f78f rguenth at gcc dot gnu.org
2023-08-18 12:12 ` rguenth at gcc dot gnu.org [this message]
2023-08-21 11:46 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-08-21 11:53 ` ubizjak at gmail dot com
2023-08-21 12:47 ` ubizjak at gmail dot com
2023-08-21 12:48 ` ubizjak at gmail dot com
2023-08-21 14:59 ` ubizjak at gmail dot com
2023-08-22 7:08 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-08-22 7:09 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-08-22 7:59 ` ubizjak at gmail dot com
2023-08-22 8:01 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-08-22 8:03 ` ubizjak at gmail dot com
2023-08-23 14:42 ` cvs-commit at gcc dot gnu.org
2023-08-23 14:45 ` cvs-commit at gcc dot gnu.org
2023-08-23 14:46 ` ubizjak at gmail dot com
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-111010-4-rG4cpg0Pxb@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).