From: Kito Cheng <kito.cheng@gmail.com>
To: Markku-Juhani Olavi Saarinen <mjos@iki.fi>
Cc: Liao Shihua <shihua@iscas.ac.cn>,
gcc-patches@gcc.gnu.org, jiawei@iscas.ac.cn, palmer@dabbelt.com,
shiyulong@iscas.ac.cn, ben.marshall@pqshield.com,
christoph.muellner@vrull.eu
Subject: Re: [PATCH V2 0/5] RISC-V: Implement Scalar Cryptography Extension
Date: Thu, 16 Feb 2023 22:00:14 +0800 [thread overview]
Message-ID: <CA+yXCZC89x01BnFy8CRWy9F02xMcw7HNnGN8M2ayOiXmEUStsw@mail.gmail.com> (raw)
In-Reply-To: <CA+iU_q=rCOYm8PYF89czNNPKdFMV6aYopOi2fOEwM5=6mcPtyw@mail.gmail.com>
Hi Markku-Juhani:
Scalar crypto is ratified I know, but the scalar crypto intrinsic part
isn't standardized - and even the APIs listed in riscv_scalar_crypto.h
are not documented anywhere yet.
So what I mean is I am happy to accept this patch except the
riscv_scalar_crypto.h header.
Once the API has documented and merged I am happy to accept that part too.
On Thu, Feb 16, 2023 at 9:52 PM Markku-Juhani Olavi Saarinen
<mjos@iki.fi> wrote:
>
> On Thu, Feb 16, 2023, 13:29 Kito Cheng <kito.cheng@gmail.com> wrote:
>
> > Hi Shihua:
> >
> > Thanks for your patches! This patch set is generally in good shape,
> > but I would prefer to remove riscv_scalar_crypto.h at this moment
> > since it's NOT standardized yet.
> >
>
> Hi Kito,
>
> I'm not sure if you're referring to the scalar crypto extensions (which
> were fully ratified in November 2021 by RVI, are included in several
> profiles, and available in commercial silicon IP), or this particular
> header file. Note that the single header is perhaps the most convenient way
> to access these subextensions that make up the scalar crypto extension 1.0.
>
> Cheers,
> Markku
>
> >
> > Do you mind sending a new version of this patch set which does not
> > include that and also update the testcases?
> >
> >
> >
> > On Thu, Feb 16, 2023 at 3:52 PM Liao Shihua <shihua@iscas.ac.cn> wrote:
> > >
> > > This series adds basic support for the Scalar Cryptography extensions:
> > > * Zbkb
> > > * Zbkc
> > > * Zbkx
> > > * Zknd
> > > * Zkne
> > > * Zknh
> > > * Zksed
> > > * Zksh
> > >
> > > The implementation follows the version Scalar Cryptography v1.0.0 of the
> > specification,
> > > and the intrinsic of Scalar Cryptography extensions follows riscv-c-api
> > > which can be found here:
> > > https://github.com/riscv/riscv-crypto/releases/tag/v1.0.0-scalar
> > > https://github.com/riscv-non-isa/riscv-c-api-doc/pull/31
> > >
> > > It works by Wu Siyu and Liao Shihua .
> > >
> > > Liao Shihua (5):
> > > Add prototypes for RISC-V Crypto built-in functions
> > > Implement ZBKB, ZBKC and ZBKX extensions
> > > Implement ZKND and ZKNE extensions
> > > Implement ZKNH extensions
> > > Implement ZKSH and ZKSED extensions
> > >
> > > gcc/config.gcc | 2 +-
> > > gcc/config/riscv/bitmanip.md | 20 +-
> > > gcc/config/riscv/constraints.md | 8 +
> > > gcc/config/riscv/crypto.md | 435 ++++++++++++++++++
> > > gcc/config/riscv/riscv-builtins.cc | 26 ++
> > > gcc/config/riscv/riscv-crypto.def | 94 ++++
> > > gcc/config/riscv/riscv-ftypes.def | 10 +
> > > gcc/config/riscv/riscv.md | 4 +-
> > > gcc/config/riscv/riscv_scalar_crypto.h | 218 +++++++++
> > > gcc/testsuite/gcc.target/riscv/zbkb32.c | 36 ++
> > > gcc/testsuite/gcc.target/riscv/zbkb64.c | 28 ++
> > > gcc/testsuite/gcc.target/riscv/zbkc32.c | 17 +
> > > gcc/testsuite/gcc.target/riscv/zbkc64.c | 17 +
> > > gcc/testsuite/gcc.target/riscv/zbkx32.c | 18 +
> > > gcc/testsuite/gcc.target/riscv/zbkx64.c | 18 +
> > > gcc/testsuite/gcc.target/riscv/zknd32.c | 18 +
> > > gcc/testsuite/gcc.target/riscv/zknd64.c | 36 ++
> > > gcc/testsuite/gcc.target/riscv/zkne32.c | 18 +
> > > gcc/testsuite/gcc.target/riscv/zkne64.c | 30 ++
> > > gcc/testsuite/gcc.target/riscv/zknh-sha256.c | 29 ++
> > > .../gcc.target/riscv/zknh-sha512-32.c | 43 ++
> > > .../gcc.target/riscv/zknh-sha512-64.c | 31 ++
> > > gcc/testsuite/gcc.target/riscv/zksed.c | 20 +
> > > gcc/testsuite/gcc.target/riscv/zksh.c | 19 +
> > > 24 files changed, 1183 insertions(+), 12 deletions(-)
> > > create mode 100644 gcc/config/riscv/crypto.md
> > > create mode 100644 gcc/config/riscv/riscv-crypto.def
> > > create mode 100644 gcc/config/riscv/riscv_scalar_crypto.h
> > > create mode 100644 gcc/testsuite/gcc.target/riscv/zbkb32.c
> > > create mode 100644 gcc/testsuite/gcc.target/riscv/zbkb64.c
> > > create mode 100644 gcc/testsuite/gcc.target/riscv/zbkc32.c
> > > create mode 100644 gcc/testsuite/gcc.target/riscv/zbkc64.c
> > > create mode 100644 gcc/testsuite/gcc.target/riscv/zbkx32.c
> > > create mode 100644 gcc/testsuite/gcc.target/riscv/zbkx64.c
> > > create mode 100644 gcc/testsuite/gcc.target/riscv/zknd32.c
> > > create mode 100644 gcc/testsuite/gcc.target/riscv/zknd64.c
> > > create mode 100644 gcc/testsuite/gcc.target/riscv/zkne32.c
> > > create mode 100644 gcc/testsuite/gcc.target/riscv/zkne64.c
> > > create mode 100644 gcc/testsuite/gcc.target/riscv/zknh-sha256.c
> > > create mode 100644 gcc/testsuite/gcc.target/riscv/zknh-sha512-32.c
> > > create mode 100644 gcc/testsuite/gcc.target/riscv/zknh-sha512-64.c
> > > create mode 100644 gcc/testsuite/gcc.target/riscv/zksed.c
> > > create mode 100644 gcc/testsuite/gcc.target/riscv/zksh.c
> > >
> > > --
> > > 2.38.1.windows.1
> > >
> >
next prev parent reply other threads:[~2023-02-16 14:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 7:50 Liao Shihua
2023-02-16 7:50 ` [PATCH V2 1/5] Add prototypes for RISC-V Crypto built-in functions Liao Shihua
2023-02-16 7:50 ` [PATCH V2 2/5] Implement ZBKB, ZBKC and ZBKX extensions Liao Shihua
2023-02-16 7:50 ` [PATCH V2 3/5] Implement ZKND and ZKNE extensions Liao Shihua
2023-02-16 7:50 ` [PATCH V2 4/5] Implement ZKNH extensions Liao Shihua
2023-02-16 7:50 ` [PATCH V2 5/5] Implement ZKSH and ZKSED extensions Liao Shihua
2023-02-16 13:28 ` [PATCH V2 0/5] RISC-V: Implement Scalar Cryptography Extension Kito Cheng
2023-02-16 13:52 ` Markku-Juhani Olavi Saarinen
2023-02-16 14:00 ` Kito Cheng [this message]
2023-02-17 3:29 ` shihua
-- strict thread matches above, loose matches on Subject: below --
2023-02-16 7:45 Liao Shihua
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=CA+yXCZC89x01BnFy8CRWy9F02xMcw7HNnGN8M2ayOiXmEUStsw@mail.gmail.com \
--to=kito.cheng@gmail.com \
--cc=ben.marshall@pqshield.com \
--cc=christoph.muellner@vrull.eu \
--cc=gcc-patches@gcc.gnu.org \
--cc=jiawei@iscas.ac.cn \
--cc=mjos@iki.fi \
--cc=palmer@dabbelt.com \
--cc=shihua@iscas.ac.cn \
--cc=shiyulong@iscas.ac.cn \
/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).