From: Kito Cheng <kito.cheng@gmail.com>
To: 廖仕华 <shihua@iscas.ac.cn>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
ben.marshall@pqshield.com,
Christoph Muellner <cmuellner@ventanamicro.com>,
Andrew Waterman <andrew@sifive.com>, jiawei <jiawei@iscas.ac.cn>,
mjos@iki.fi, Kito Cheng <kito.cheng@sifive.com>
Subject: Re: [PATCH 4/5 V1] RISC-V:Implement testcases for Crypto extension
Date: Tue, 1 Mar 2022 21:49:06 +0800 [thread overview]
Message-ID: <CA+yXCZC_SuoNnqcD-dorKbP=0AfFvfzQGZeuBxZ_4HO7rberXw@mail.gmail.com> (raw)
In-Reply-To: <CA+yXCZBwTVt=5KB-L6fntpqw352RpJKvQjGLU+ija4UxxuTfnw@mail.gmail.com>
> > diff --git a/gcc/testsuite/gcc.target/riscv/zbkb64.c b/gcc/testsuite/gcc.target/riscv/zbkb64.c
> > new file mode 100644
> > index 00000000000..2cd76a29750
> > --- /dev/null
> > +++ b/gcc/testsuite/gcc.target/riscv/zbkb64.c
> > @@ -0,0 +1,21 @@
> > +/* { dg-do compile } */
> > +/* { dg-options "-O2 -march=rv64gc_zbkb -mabi=lp64" } */
> > +/* { dg-skip-if "" { *-*-* } { "-g" "-flto"} } */
> > +#include"riscv_crypto.h"
> > +int64_t foo1(int64_t rs1, int64_t rs2)
> > +{
> > + return _rv64_ror(rs1,rs2);
> > +}
> > +
> > +int64_t foo2(int64_t rs1, int64_t rs2)
> > +{
> > + return _rv64_rol(rs1,rs2);
> > +}
> > +
> > +int64_t foo3(int64_t rs1, int64_t rs2)
> > +{
> > + return _rv64_brev8(rs1);
> > +}
> > +/* { dg-final { scan-assembler-times "ror" 1 } } */
> > +/* { dg-final { scan-assembler-times "rol" 1 } } */
> > +/* { dg-final { scan-assembler-times "brev8" 1 } } */
> > \ No newline at end of file
Could you also add _rv32_variant test to zbkb64.c?
next prev parent reply other threads:[~2022-03-01 13:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 9:44 [PATCH 0/5 V1] RISC-V:Implement Crypto extension's instruction patterns and it's intrinsics shihua
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 [this message]
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='CA+yXCZC_SuoNnqcD-dorKbP=0AfFvfzQGZeuBxZ_4HO7rberXw@mail.gmail.com' \
--to=kito.cheng@gmail.com \
--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=mjos@iki.fi \
--cc=shihua@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).