From: Jan Beulich <jbeulich@suse.com>
To: jiawei@iscas.ac.cn
Cc: nelson@rivosinc.com, kito.cheng@sifive.com, palmer@dabbelt.com,
christoph.muellner@vrull.eu, jeremy.bennett@embecosm.com,
mary.bennett@embecosm.com, nandni.jamnadas@embecosm.com,
charlie.keaney@embecosm.com, simon.cook@embecosm.com,
tariq.kurd@codasip.com, ibrahim.abu.kharmeh1@huawei.com,
gaofei@eswincomputing.com, sinan.lin@linux.alibaba.com,
wuwei2016@iscas.ac.cn, shihua@iscas.ac.cn, shiyulong@iscas.ac.cn,
chenyixuan@iscas.ac.cn, binutils@sourceware.org
Subject: Re: [PATCH 2/2] RISC-V: Add Zcb extension testcases.
Date: Tue, 13 Jun 2023 16:59:30 +0200 [thread overview]
Message-ID: <7eacf14a-0de6-e1e9-42a6-1bec7e6f2c21@suse.com> (raw)
In-Reply-To: <52f715ca.88bf.188b540ca8b.Coremail.jiawei@iscas.ac.cn>
On 13.06.2023 16:55, jiawei@iscas.ac.cn wrote:
> > -----原始邮件-----
> > 发件人: "Jan Beulich" <jbeulich@suse.com>
> > 发送时间: 2023-06-13 22:28:38 (星期二)
> > 收件人: Jiawei <jiawei@iscas.ac.cn>
> > 抄送: nelson@rivosinc.com, kito.cheng@sifive.com, palmer@dabbelt.com, christoph.muellner@vrull.eu, jeremy.bennett@embecosm.com, mary.bennett@embecosm.com, nandni.jamnadas@embecosm.com, charlie.keaney@embecosm.com, simon.cook@embecosm.com, tariq.kurd@codasip.com, ibrahim.abu.kharmeh1@huawei.com, gaofei@eswincomputing.com, sinan.lin@linux.alibaba.com, wuwei2016@iscas.ac.cn, shihua@iscas.ac.cn, shiyulong@iscas.ac.cn, chenyixuan@iscas.ac.cn, binutils@sourceware.org
> > 主题: Re: [PATCH 2/2] RISC-V: Add Zcb extension testcases.
> >
> > On 13.06.2023 15:38, Jiawei wrote:
> > > Add all zcb instructions testcases. Fail testcases check missing depend
> > > extensions cases.
> > >
> > > Co-Authored by: Charlie Keaney <charlie.keaney@embecosm.com>
> > > Co-Authored by: Mary Bennett <mary.bennett@embecosm.com>
> > > Co-Authored by: Nandni Jamnadas <nandni.jamnadas@embecosm.com>
> > > Co-Authored by: Sinan Lin <sinan.lin@linux.alibaba.com>
> > > Co-Authored by: Simon Cook <simon.cook@embecosm.com>
> > > Co-Authored by: Shihua Liao <shihua@iscas.ac.cn>
> > > Co-Authored by: Yulong Shi <yulong@iscas.ac.cn>
> > >
> > > gas/ChangeLog:
> > >
> > > * testsuite/gas/riscv/zc-zcb-fail-arch-0.d: New test.
> > > * testsuite/gas/riscv/zc-zcb-fail-arch-0.l: New test.
> > > * testsuite/gas/riscv/zc-zcb-fail-arch-0.s: New test.
> > > * testsuite/gas/riscv/zc-zcb-fail-arch-1.d: New test.
> > > * testsuite/gas/riscv/zc-zcb-fail-arch-1.l: New test.
> > > * testsuite/gas/riscv/zc-zcb-fail-arch-1.s: New test.
> > > * testsuite/gas/riscv/zc-zcb-fail-operand-0.d: New test.
> > > * testsuite/gas/riscv/zc-zcb-fail-operand-0.l: New test.
> > > * testsuite/gas/riscv/zc-zcb-fail-operand-0.s: New test.
> > > * testsuite/gas/riscv/zc-zcb-fail-operand-1.d: New test.
> > > * testsuite/gas/riscv/zc-zcb-fail-operand-1.l: New test.
> > > * testsuite/gas/riscv/zc-zcb-fail-operand-1.s: New test.
> > > * testsuite/gas/riscv/zc-zcb-fail-xlen.d: New test.
> > > * testsuite/gas/riscv/zc-zcb-fail-xlen.l: New test.
> > > * testsuite/gas/riscv/zc-zcb-fail-xlen.s: New test.
> > > * testsuite/gas/riscv/zc-zcb-lbu.d: New test.
> > > * testsuite/gas/riscv/zc-zcb-lbu.s: New test.
> > > * testsuite/gas/riscv/zc-zcb-lh.d: New test.
> > > * testsuite/gas/riscv/zc-zcb-lh.s: New test.
> > > * testsuite/gas/riscv/zc-zcb-lhu.d: New test.
> > > * testsuite/gas/riscv/zc-zcb-lhu.s: New test.
> > > * testsuite/gas/riscv/zc-zcb-mul.d: New test.
> > > * testsuite/gas/riscv/zc-zcb-mul.s: New test.
> > > * testsuite/gas/riscv/zc-zcb-not.d: New test.
> > > * testsuite/gas/riscv/zc-zcb-not.s: New test.
> > > * testsuite/gas/riscv/zc-zcb-sb.d: New test.
> > > * testsuite/gas/riscv/zc-zcb-sb.s: New test.
> > > * testsuite/gas/riscv/zc-zcb-sext-b.s: New test.
> > > * testsuite/gas/riscv/zc-zcb-sext-h.s: New test.
> > > * testsuite/gas/riscv/zc-zcb-sextw.d: New test.
> > > * testsuite/gas/riscv/zc-zcb-sextw.s: New test.
> > > * testsuite/gas/riscv/zc-zcb-sh.d: New test.
> > > * testsuite/gas/riscv/zc-zcb-sh.s: New test.
> > > * testsuite/gas/riscv/zc-zcb-test-arch-gc.d: New test.
> > > * testsuite/gas/riscv/zc-zcb-test-arch-no-zcb.d: New test.
> > > * testsuite/gas/riscv/zc-zcb-test-arch.s: New test.
> > > * testsuite/gas/riscv/zc-zcb-test-operand-0.d: New test.
> > > * testsuite/gas/riscv/zc-zcb-test-operand-0.s: New test.
> > > * testsuite/gas/riscv/zc-zcb-test-operand-1.d: New test.
> > > * testsuite/gas/riscv/zc-zcb-test-operand-1.s: New test.
> > > * testsuite/gas/riscv/zc-zcb-test-operand-2.d: New test.
> > > * testsuite/gas/riscv/zc-zcb-test-operand-2.s: New test.
> > > * testsuite/gas/riscv/zc-zcb-zext-b.d: New test.
> > > * testsuite/gas/riscv/zc-zcb-zext-b.s: New test.
> > > * testsuite/gas/riscv/zc-zcb-zext-h.d: New test.
> > > * testsuite/gas/riscv/zc-zcb-zext-h.s: New test.
> > > * testsuite/gas/riscv/zc-zcb-zextw.d: New test.
> > > * testsuite/gas/riscv/zc-zcb-zextw.s: New test.
> >
> > While I'm not a RISC-V maintainer, I still wonder about the overhead
> > of having a single test per insn (rather than e.g. per feature or
> > relevant combination of features): In my experience many small tests
> > consume more time (and space) when running the testsuite than fewer
> > larger ones. (This remark would then also apply to the earlier series
> > consisting of just testsuite additions.)
> >
> > Jan
>
> We run these tests on dejagnu, they only do some regex matching, and
> used to ensure correct generation of instruction opcode, and to handle
> some wrong dependency cases error log.
>
> We not stats yet on their performance overhead yet, but they still run
> pretty fast with dejagnu currently. Do we need to stat it?
Not sure, but you want to keep the scalability aspect in mind: For the
handful of insns here this is likely fine, but what if every insn now
and in the future had its own testcase(s)?
Jan
prev parent reply other threads:[~2023-06-13 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 13:38 [PATCH 1/2] RISC-V: Add Zcb extension supports Jiawei
2023-06-13 13:38 ` [PATCH 2/2] RISC-V: Add Zcb extension testcases Jiawei
2023-06-13 14:28 ` Jan Beulich
2023-06-13 14:55 ` jiawei
2023-06-13 14:59 ` Jan Beulich [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=7eacf14a-0de6-e1e9-42a6-1bec7e6f2c21@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=charlie.keaney@embecosm.com \
--cc=chenyixuan@iscas.ac.cn \
--cc=christoph.muellner@vrull.eu \
--cc=gaofei@eswincomputing.com \
--cc=ibrahim.abu.kharmeh1@huawei.com \
--cc=jeremy.bennett@embecosm.com \
--cc=jiawei@iscas.ac.cn \
--cc=kito.cheng@sifive.com \
--cc=mary.bennett@embecosm.com \
--cc=nandni.jamnadas@embecosm.com \
--cc=nelson@rivosinc.com \
--cc=palmer@dabbelt.com \
--cc=shihua@iscas.ac.cn \
--cc=shiyulong@iscas.ac.cn \
--cc=simon.cook@embecosm.com \
--cc=sinan.lin@linux.alibaba.com \
--cc=tariq.kurd@codasip.com \
--cc=wuwei2016@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).