From: Max Chou <max.chou@sifive.com>
To: qemu-devel@nongnu.org, qemu-riscv@nongnu.org
Cc: Max Chou <max.chou@sifive.com>
Subject: [PATCH] Fix fp16 checking in vector fp widen/narrow instructions
Date: Wed, 20 Mar 2024 15:25:01 +0800 [thread overview]
Message-ID: <20240320072709.1043227-1-max.chou@sifive.com> (raw)
When SEW is 16, we need to check whether the Zvfhmin is enabled for the
single width operator for vector floating point widen/narrow
instructions.
The commits in this patchset fix the single width operator checking and
remove the redudant SEW checking for vector floating point widen/narrow
instructions.
Max Chou (4):
target/riscv: rvv: Fix Zvfhmin checking for vfwcvt.f.f.v and
vfncvt.f.f.w instructions
target/riscv: rvv: Check single width operator for vector fp widen
instructions
target/riscv: rvv: Check single width operator for vfncvt.rod.f.f.w
target/riscv: rvv: Remove redudant SEW checking for vector fp
narrow/widen instructions
target/riscv/insn_trans/trans_rvv.c.inc | 42 ++++++++++++++++---------
1 file changed, 28 insertions(+), 14 deletions(-)
--
2.31.1
next reply other threads:[~2024-03-20 7:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 7:25 Max Chou [this message]
2024-03-20 7:25 ` [PATCH] target/riscv: rvv: Fix Zvfhmin checking for vfwcvt.f.f.v and vfncvt.f.f.w instructions Max Chou
2024-03-20 20:12 ` Daniel Henrique Barboza
2024-03-20 7:25 ` [PATCH] target/riscv: rvv: Check single width operator for vector fp widen instructions Max Chou
2024-03-20 20:13 ` Daniel Henrique Barboza
2024-03-20 7:25 ` [PATCH] target/riscv: rvv: Check single width operator for vfncvt.rod.f.f.w Max Chou
2024-03-20 20:13 ` Daniel Henrique Barboza
2024-03-20 7:25 ` [PATCH] target/riscv: rvv: Remove redudant SEW checking for vector fp narrow/widen instructions Max Chou
2024-03-20 20:14 ` Daniel Henrique Barboza
2024-03-22 4:12 ` [PATCH] Fix fp16 checking in vector fp widen/narrow instructions Alistair Francis
2024-03-22 8:59 ` Max Chou
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=20240320072709.1043227-1-max.chou@sifive.com \
--to=max.chou@sifive.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
/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).