From: Jeff Law <jeffreyalaw@gmail.com>
To: Kito Cheng <kito.cheng@gmail.com>, Die Li <lidie@eswincomputing.com>
Cc: "GCC Patches" <gcc-patches@gcc.gnu.org>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Christoph Müllner" <christoph.muellner@vrull.eu>,
"Philipp Tomsich" <philipp.tomsich@vrull.eu>
Subject: Re: [PATCH] RISC-V: Optimize TARGET_XTHEADCONDMOV
Date: Thu, 25 May 2023 22:01:07 -0600 [thread overview]
Message-ID: <d1d9da73-fd2e-4864-634b-b7b749b35160@gmail.com> (raw)
In-Reply-To: <CA+yXCZBSkOB-fUuLEGvBZiJg2RLb_Cx2mxi-8PSX5RNoV6nZHA@mail.gmail.com>
On 5/25/23 20:43, Kito Cheng wrote:
> I would defer this to vrull or t-head folks :)
Given the overlap between where this is going and how I think we should
be handling Zicondops, I'll take it. It overlaps with work I've had
Raphael doing recently.
jeff
next prev parent reply other threads:[~2023-05-26 4:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 0:52 Die Li
2023-05-26 2:43 ` Kito Cheng
2023-05-26 4:01 ` Jeff Law [this message]
2023-05-26 8:20 ` Philipp Tomsich
2023-05-29 17:14 ` Jeff Law
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=d1d9da73-fd2e-4864-634b-b7b749b35160@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=christoph.muellner@vrull.eu \
--cc=gcc-patches@gcc.gnu.org \
--cc=kito.cheng@gmail.com \
--cc=lidie@eswincomputing.com \
--cc=palmer@dabbelt.com \
--cc=philipp.tomsich@vrull.eu \
/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).