public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/104704] [12 Regression] ix86_gen_scratch_sse_rtx doesn't work with explicit XMM7/XMM15/XMM31 usage
Date: Thu, 03 Mar 2022 08:51:31 +0000 [thread overview]
Message-ID: <bug-104704-4-VhxdkZ7xMF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104704-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104704
--- Comment #13 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to H.J. Lu from comment #10)
> Created attachment 52553 [details]
> A patch to always return pseudo register in ix86_gen_scratch_sse_rtx
Please go ahead with this patch, i'll submit an incremental patch for #12
next prev parent reply other threads:[~2022-03-03 8:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-26 20:09 [Bug target/104704] New: [12 Regression] ix86_gen_scratch_sse_rtx doesn't work " hjl.tools at gmail dot com
2022-02-27 0:55 ` [Bug target/104704] [12 Regression] ix86_gen_scratch_sse_rtx doesn't work with " hjl.tools at gmail dot com
2022-02-28 1:36 ` crazylht at gmail dot com
2022-02-28 1:44 ` crazylht at gmail dot com
2022-02-28 1:59 ` hjl.tools at gmail dot com
2022-02-28 8:31 ` crazylht at gmail dot com
2022-02-28 9:27 ` crazylht at gmail dot com
2022-02-28 9:33 ` crazylht at gmail dot com
2022-03-01 7:37 ` rguenth at gcc dot gnu.org
2022-03-02 5:29 ` crazylht at gmail dot com
2022-03-02 14:49 ` hjl.tools at gmail dot com
2022-03-02 22:22 ` hjl.tools at gmail dot com
2022-03-03 1:14 ` crazylht at gmail dot com
2022-03-03 1:28 ` crazylht at gmail dot com
2022-03-03 8:51 ` crazylht at gmail dot com [this message]
2022-03-04 3:02 ` cvs-commit at gcc dot gnu.org
2022-03-04 3:03 ` hjl.tools 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-104704-4-VhxdkZ7xMF@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).