From: Jeff Law <jeffreyalaw@gmail.com>
To: Lin Sinan <mynameisxiaou@gmail.com>, gcc-patches@gcc.gnu.org
Cc: shihua@iscas.ac.cn, philipp.tomsich@vrull.eu,
kito.cheng@gmail.com, Sinan Lin <sinan.lin@linux.alibaba.com>
Subject: Re: [PATCH] RISC-V: add TARGET_ZBKB to the condition of bswapsi2, bswapdi2 and rotr<mode>3 patterns
Date: Tue, 18 Apr 2023 12:27:36 -0600 [thread overview]
Message-ID: <27da8be4-695c-428d-0f58-341d675b3618@gmail.com> (raw)
In-Reply-To: <20230410105640.6510-1-mynameisxiaou@gmail.com>
On 4/10/23 04:56, Lin Sinan wrote:
> From: Sinan Lin <sinan.lin@linux.alibaba.com>
>
> tell gcc that zbkb has these two spn to enable some optimizations. e.g.
> 1) the rrotate_expr could match to rotrm3 during expand; 2) hook up
> __builtin_bswap64 with `rev8` in zbkb64.
Thanks. I pushed this to the trunk.
jeff
prev parent reply other threads:[~2023-04-18 18:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 10:56 Lin Sinan
2023-04-10 14:55 ` Jeff Law
2023-04-18 18:27 ` Jeff Law [this message]
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=27da8be4-695c-428d-0f58-341d675b3618@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kito.cheng@gmail.com \
--cc=mynameisxiaou@gmail.com \
--cc=philipp.tomsich@vrull.eu \
--cc=shihua@iscas.ac.cn \
--cc=sinan.lin@linux.alibaba.com \
/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).