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 0/2] Make vector whole-register move (vmv) depend on vtype register
Date: Thu, 30 Nov 2023 01:03:56 +0800 [thread overview]
Message-ID: <20231129170400.21251-1-max.chou@sifive.com> (raw)
The ratified v1.0 version of RISC-V V spec section 16.6 says that
`The instructions operate as if EEW=SEW.`.
So the whole vector register move instructions depend on the vtype
register that means the implementation needs to be fixed to raise an
illegal-instruction exception when vtype.vill=1, as is the case with
most other vector instructions.
Reference:
- https://github.com/riscv/riscv-v-spec/blob/v1.0/v-spec.adoc#whole-vector-register-move
- https://github.com/riscv/riscv-v-spec/commit/856fe5bd1cb135c39258e6ca941bf234ae63e1b1
Max Chou (2):
target/riscv: Add vill check for whole vector register move
instructions
target/riscv: The whole vector register move instructions depend on
vsew
target/riscv/insn_trans/trans_rvv.c.inc | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
--
2.34.1
next reply other threads:[~2023-11-29 17:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 17:03 Max Chou [this message]
2023-11-29 17:03 ` [PATCH 1/2] target/riscv: Add vill check for whole vector register move instructions Max Chou
2023-12-04 19:22 ` Daniel Henrique Barboza
2023-11-29 17:03 ` [PATCH 2/2] target/riscv: The whole vector register move instructions depend on vsew Max Chou
2023-11-29 17:27 ` Richard Henderson
2023-12-06 0:49 ` [PATCH 0/2] Make vector whole-register move (vmv) depend on vtype register Alistair Francis
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=20231129170400.21251-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).