From: Richard Henderson <richard.henderson@linaro.org>
To: Weiwei Li <liweiwei@iscas.ac.cn>,
qemu-riscv@nongnu.org, qemu-devel@nongnu.org
Cc: palmer@dabbelt.com, alistair.francis@wdc.com,
bin.meng@windriver.com, dbarboza@ventanamicro.com,
zhiwei_liu@linux.alibaba.com, wangjunqiang@iscas.ac.cn,
lazyparser@gmail.com
Subject: Re: [RFC 2/5] target/riscv: Add support for Zfbfmin extension
Date: Wed, 12 Apr 2023 12:20:32 +0200 [thread overview]
Message-ID: <650d7a14-5752-26d3-70a3-07d47e04fb14@linaro.org> (raw)
In-Reply-To: <20230412023320.50706-3-liweiwei@iscas.ac.cn>
On 4/12/23 04:33, Weiwei Li wrote:
> Add trans_* and helper function for Zfbfmin instructions.
>
> Signed-off-by: Weiwei Li<liweiwei@iscas.ac.cn>
> Signed-off-by: Junqiang Wang<wangjunqiang@iscas.ac.cn>
> ---
> target/riscv/fpu_helper.c | 12 +++++
> target/riscv/helper.h | 4 ++
> target/riscv/insn32.decode | 4 ++
> target/riscv/insn_trans/trans_rvbf16.c.inc | 53 ++++++++++++++++++++++
> target/riscv/insn_trans/trans_rvzfh.c.inc | 12 ++---
> target/riscv/translate.c | 1 +
> 6 files changed, 80 insertions(+), 6 deletions(-)
> create mode 100644 target/riscv/insn_trans/trans_rvbf16.c.inc
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
next prev parent reply other threads:[~2023-04-12 10:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 2:33 [RFC 0/5] target/riscv: Add support for BF16 extensions Weiwei Li
2023-04-12 2:33 ` [RFC 1/5] target/riscv: Add properties " Weiwei Li
2023-04-12 20:24 ` Daniel Henrique Barboza
2023-04-12 2:33 ` [RFC 2/5] target/riscv: Add support for Zfbfmin extension Weiwei Li
2023-04-12 10:20 ` Richard Henderson [this message]
2023-04-12 2:33 ` [RFC 3/5] target/riscv: Add support for Zvfbfmin extension Weiwei Li
2023-04-12 10:21 ` Richard Henderson
2023-04-12 2:33 ` [RFC 4/5] target/riscv: Add support for Zvfbfwma extension Weiwei Li
2023-04-12 10:22 ` Richard Henderson
2023-04-12 2:33 ` [RFC 5/5] target/riscv: Expose properties for BF16 extensions Weiwei Li
2023-04-12 20:24 ` Daniel Henrique Barboza
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=650d7a14-5752-26d3-70a3-07d47e04fb14@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alistair.francis@wdc.com \
--cc=bin.meng@windriver.com \
--cc=dbarboza@ventanamicro.com \
--cc=lazyparser@gmail.com \
--cc=liweiwei@iscas.ac.cn \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=wangjunqiang@iscas.ac.cn \
--cc=zhiwei_liu@linux.alibaba.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 NNTP newsgroup(s).