From: Jeff Law <jeffreyalaw@gmail.com>
To: Kito Cheng <kito.cheng@gmail.com>,
Feng Wang <wangfeng@eswincomputing.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>
Subject: Re: [PATCH] RISC-V: Add crypto machine descriptions
Date: Thu, 28 Dec 2023 08:52:21 -0700 [thread overview]
Message-ID: <b1f4505c-6947-4489-9148-3a3e5f693dec@gmail.com> (raw)
In-Reply-To: <CA+yXCZDKF+JWZoT+_8e1NX9dwnQhnjtYc+gaS6==nRP17sFVpw@mail.gmail.com>
On 12/26/23 19:47, Kito Cheng wrote:
> Thanks Feng, the patch is LGTM from my side, I am happy to accept
> vector crypto stuffs for GCC 14, it's mostly intrinsic stuff, and the
> only few non-intrinsic stuff also low risk enough (e.g. vrol, vctz)
I won't object. I'm disappointed that we're in a similar situation as
last year, but at least the scope is smaller.
jeff
prev parent reply other threads:[~2023-12-28 15:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 1:59 Feng Wang
2023-12-22 2:03 ` juzhe.zhong
2023-12-22 2:04 ` Feng Wang
2023-12-27 2:47 ` Kito Cheng
2023-12-28 15:52 ` 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=b1f4505c-6947-4489-9148-3a3e5f693dec@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=wangfeng@eswincomputing.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).