From: Chao Liu <lc00631@tecorigin.com>
To: bmeng.cn@gmail.com, liwei1518@gmail.com, palmer@dabbelt.com,
alistair.francis@wdc.com, dbarboza@ventanamicro.com,
zhiwei_liu@linux.alibaba.com, max.chou@sifive.com,
alistair23@gmail.com
Cc: qemu-riscv@nongnu.org, qemu-devel@nongnu.org,
zqz00548@tecorigin.com, Chao Liu <lc00631@tecorigin.com>
Subject: [PATCH v2 0/2] Enhanced VSTART and VL Checks for Vector Instructions
Date: Wed, 18 Dec 2024 15:15:29 +0800 [thread overview]
Message-ID: <cover.1734504907.git.lc00631@tecorigin.com> (raw)
Hi, all:
In the second version of this patch, I addressed the issue that other vector
instructions didn't check for vstart >= vl correctly.
I refactored the VSTART_CHECK_EARLY_EXIT() macro. This change is intended to:
Vector instructions with special vl values can also be checked with this macro,
such as vlm.v instruction (real vl = ceil(vl / 8)).
PATCH v1:
https://lore.kernel.org/qemu-riscv/cover.1734423785.git.lc00631@tecorigin.com/
Chao Liu (2):
target/riscv: refactor VSTART_CHECK_EARLY_EXIT() to accept vl as a
parameter
target/riscv: fix handling of nop for vstart >= vl in some vector
instruction
target/riscv/vcrypto_helper.c | 32 ++++++-------
target/riscv/vector_helper.c | 83 ++++++++++++++++++---------------
target/riscv/vector_internals.c | 4 +-
target/riscv/vector_internals.h | 12 ++---
4 files changed, 69 insertions(+), 62 deletions(-)
--
2.47.1
next reply other threads:[~2024-12-18 7:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 7:15 Chao Liu [this message]
2024-12-18 7:15 ` [PATCH v2 1/2] target/riscv: refactor VSTART_CHECK_EARLY_EXIT() to accept vl as a parameter Chao Liu
2024-12-26 13:16 ` Daniel Henrique Barboza
2024-12-18 7:15 ` [PATCH v2 2/2] target/riscv: fix handling of nop for vstart >= vl in some vector instruction Chao Liu
2024-12-26 13:48 ` 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=cover.1734504907.git.lc00631@tecorigin.com \
--to=lc00631@tecorigin.com \
--cc=alistair.francis@wdc.com \
--cc=alistair23@gmail.com \
--cc=bmeng.cn@gmail.com \
--cc=dbarboza@ventanamicro.com \
--cc=liwei1518@gmail.com \
--cc=max.chou@sifive.com \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=zhiwei_liu@linux.alibaba.com \
--cc=zqz00548@tecorigin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.