public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: shihua@iscas.ac.cn
To: gcc-patches@gcc.gnu.org
Cc: ben.marshall@pqshield.com, kito.cheng@sifive.com,
	cmuellner@ventanamicro.com, palmer@dabbelt.com,
	andrew@sifive.com, lazyparser@gmail.com, jiawei@iscas.ac.cn,
	mjos@iki.fi, LiaoShihua <shihua@iscas.ac.cn>
Subject: [PATCH 0/5 V1] RISC-V:Implement Crypto extension's instruction patterns and it's intrinsics
Date: Wed, 23 Feb 2022 17:44:13 +0800	[thread overview]
Message-ID: <20220223094418.3518-1-shihua@iscas.ac.cn> (raw)

From: LiaoShihua <shihua@iscas.ac.cn>

    This patch set is the implementation of Crypto extension, which includes zbkb, zbkc, zbkx,
    zknd, zknh, zkne,zksed and zksh extension.
    It includes instruction/md patterns, intrinsic functions, testcases for intrinsic functions, 
    and test macros.
    The definitions of intrinsic functions come from https://github.com/rvkrypto/rvkrypto-fips .
    This work is done by Liao Shihua and Wu Siyu.

LiaoShihua (5):
  RISC-V:Implement instruction patterns for Crypto extensions
  RISC-V:Implement built-in instructions for Crypto extensions
  RISC-V:Implement intrinsics for Crypto extensions
  RISC-V:Implement testcases for Crypto extensions
  RISC-V:Implement architecture extension test macros for Crypto extensions

 gcc/config.gcc                             |   1 +
 gcc/config/riscv/crypto.md                 | 383 +++++++++++++
 gcc/config/riscv/predicates.md             |   8 +
 gcc/config/riscv/riscv-builtins-crypto.def |  93 ++++
 gcc/config/riscv/riscv-builtins.cc         |  35 ++
 gcc/config/riscv/riscv-c.cc                |   9 +
 gcc/config/riscv/riscv-ftypes.def          |   7 +
 gcc/config/riscv/riscv.md                  |   1 +
 gcc/config/riscv/riscv_crypto.h            |  12 +
 gcc/config/riscv/riscv_crypto_scalar.h     | 247 +++++++++
 gcc/config/riscv/rvk_asm_intrin.h          | 187 +++++++
 gcc/config/riscv/rvk_emu_intrin.h          | 594 +++++++++++++++++++++
 gcc/testsuite/gcc.target/riscv/predef-17.c |  59 ++
 gcc/testsuite/gcc.target/riscv/zbkb32.c    |  34 ++
 gcc/testsuite/gcc.target/riscv/zbkb64.c    |  21 +
 gcc/testsuite/gcc.target/riscv/zbkc32.c    |  16 +
 gcc/testsuite/gcc.target/riscv/zbkc64.c    |  16 +
 gcc/testsuite/gcc.target/riscv/zbkx32.c    |  16 +
 gcc/testsuite/gcc.target/riscv/zbkx64.c    |  16 +
 gcc/testsuite/gcc.target/riscv/zknd32.c    |  18 +
 gcc/testsuite/gcc.target/riscv/zknd64.c    |  35 ++
 gcc/testsuite/gcc.target/riscv/zkne64.c    |  29 +
 gcc/testsuite/gcc.target/riscv/zknh.c      |  28 +
 gcc/testsuite/gcc.target/riscv/zknh32.c    |  40 ++
 gcc/testsuite/gcc.target/riscv/zknh64.c    |  29 +
 gcc/testsuite/gcc.target/riscv/zksed.c     |  20 +
 gcc/testsuite/gcc.target/riscv/zksh.c      |  17 +
 27 files changed, 1971 insertions(+)
 create mode 100644 gcc/config/riscv/crypto.md
 create mode 100644 gcc/config/riscv/riscv-builtins-crypto.def
 create mode 100644 gcc/config/riscv/riscv_crypto.h
 create mode 100644 gcc/config/riscv/riscv_crypto_scalar.h
 create mode 100644 gcc/config/riscv/rvk_asm_intrin.h
 create mode 100644 gcc/config/riscv/rvk_emu_intrin.h
 create mode 100644 gcc/testsuite/gcc.target/riscv/predef-17.c
 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/zkne64.c
 create mode 100644 gcc/testsuite/gcc.target/riscv/zknh.c
 create mode 100644 gcc/testsuite/gcc.target/riscv/zknh32.c
 create mode 100644 gcc/testsuite/gcc.target/riscv/zknh64.c
 create mode 100644 gcc/testsuite/gcc.target/riscv/zksed.c
 create mode 100644 gcc/testsuite/gcc.target/riscv/zksh.c

-- 
2.31.1.windows.1


             reply	other threads:[~2022-02-23  9:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-23  9:44 shihua [this message]
2022-02-23  9:44 ` [PATCH 1/5 V1] RISC-V:Implement instruction patterns for Crypto extension shihua
2022-02-28 16:04   ` Kito Cheng
2022-02-23  9:44 ` [PATCH 2/5 V1] RISC-V:Implement built-in instructions " shihua
2022-02-23  9:44 ` [PATCH 3/5 V1] RISC-V:Implement intrinsics " shihua
2022-02-28 15:34   ` Kito Cheng
2022-02-23  9:44 ` [PATCH 4/5 V1] RISC-V:Implement testcases " shihua
2022-03-01 13:00   ` Kito Cheng
2022-03-01 13:49     ` Kito Cheng
2022-02-23  9:44 ` [PATCH 5/5 V1] RISC-V:Implement architecture extension test macros " shihua
2022-02-24  9:55   ` Kito Cheng
2022-02-28 15:56     ` Kito Cheng

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=20220223094418.3518-1-shihua@iscas.ac.cn \
    --to=shihua@iscas.ac.cn \
    --cc=andrew@sifive.com \
    --cc=ben.marshall@pqshield.com \
    --cc=cmuellner@ventanamicro.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jiawei@iscas.ac.cn \
    --cc=kito.cheng@sifive.com \
    --cc=lazyparser@gmail.com \
    --cc=mjos@iki.fi \
    --cc=palmer@dabbelt.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).