From: Frank Chang <frank.chang@sifive.com>
To: Frank Chang <frank.chang@sifive.com>
Cc: "open list:RISC-V" <qemu-riscv@nongnu.org>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [PATCH 00/17] Add RISC-V RVV Zve32f and Zve64f extensions
Date: Mon, 17 Jan 2022 20:55:57 +0800 [thread overview]
Message-ID: <CANzO1D2MjL+d9Rconz4F9vtwzY9n2LOGChTZk_UW6F32TTMbuA@mail.gmail.com> (raw)
In-Reply-To: <20211229023348.12606-1-frank.chang@sifive.com>
[-- Attachment #1: Type: text/plain, Size: 2897 bytes --]
<frank.chang@sifive.com> 於 2021年12月29日 週三 上午10:35寫道:
> From: Frank Chang <frank.chang@sifive.com>
>
> In RVV v1.0 spec, several Zve* vector extensions for embedded processors
> are defined in Chapter 18.2:
>
> https://github.com/riscv/riscv-v-spec/blob/v1.0/v-spec.adoc#zve-vector-extensions-for-embedded-processors
>
> This patchset implements Zve32f and Zve64f extensions.
>
> The port is available at:
> https://github.com/sifive/qemu/tree/rvv-zve32f-zve64f-upstream
>
> Zve32f can be enabled with -cpu option: Zve32f=true and
> Zve64f can be enabled with -cpu option: Zve64f=true.
> V is not required to be enabled explicitly.
>
> Quote from the inclusion diagram for the six standard vector extensions
> from Nick Knight <nick.knight@sifive.com>:
>
> V
> |
> Zve64d
> |
> Zve64f
> / \
> Zve64x Zve32f
> \ /
> Zve32x
>
> Note: This patchset depends on other patchsets listed in Based-on
> section below so it is not able to be built unless those patchsets
> are applied.
>
> Based-on: <20211229021250.29804-1-frank.chang@sifive.com>
>
> Frank Chang (17):
> target/riscv: rvv-1.0: Add Zve64f extension into RISC-V
> target/riscv: rvv-1.0: Add Zve64f support for configuration insns
> target/riscv: rvv-1.0: Add Zve64f support for load and store insns
> target/riscv: rvv-1.0: Add Zve64f support for vmulh variant insns
> target/riscv: rvv-1.0: Add Zve64f support for vsmul.vv and vsmul.vx
> insns
> target/riscv: rvv-1.0: Add Zve64f support for scalar fp insns
> target/riscv: rvv-1.0: Add Zve64f support for single-width fp
> reduction insns
> target/riscv: rvv-1.0: Add Zve64f support for widening type-convert
> insns
> target/riscv: rvv-1.0: Add Zve64f support for narrowing type-convert
> insns
> target/riscv: rvv-1.0: Allow Zve64f extension to be turned on
> target/riscv: rvv-1.0: Add Zve32f extension into RISC-V
> target/riscv: rvv-1.0: Add Zve32f support for configuration insns
> target/riscv: rvv-1.0: Add Zve32f support for scalar fp insns
> target/riscv: rvv-1.0: Add Zve32f support for single-width fp
> reduction insns
> target/riscv: rvv-1.0: Add Zve32f support for widening type-convert
> insns
> target/riscv: rvv-1.0: Add Zve32f support for narrowing type-convert
> insns
> target/riscv: rvv-1.0: Allow Zve32f extension to be turned on
>
> target/riscv/cpu.c | 6 +
> target/riscv/cpu.h | 2 +
> target/riscv/cpu_helper.c | 5 +-
> target/riscv/csr.c | 6 +-
> target/riscv/insn_trans/trans_rvv.c.inc | 217 ++++++++++++++++++++----
> target/riscv/translate.c | 4 +
> 6 files changed, 203 insertions(+), 37 deletions(-)
>
> --
> 2.31.1
>
>
>
ping
[-- Attachment #2: Type: text/html, Size: 3945 bytes --]
prev parent reply other threads:[~2022-01-17 13:30 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 2:33 [PATCH 00/17] Add RISC-V RVV Zve32f and Zve64f extensions frank.chang
2021-12-29 2:33 ` [PATCH 01/17] target/riscv: rvv-1.0: Add Zve64f extension into RISC-V frank.chang
2022-01-17 22:23 ` Alistair Francis
2021-12-29 2:33 ` [PATCH 02/17] target/riscv: rvv-1.0: Add Zve64f support for configuration insns frank.chang
2022-01-17 22:21 ` Alistair Francis
2021-12-29 2:33 ` [PATCH 03/17] target/riscv: rvv-1.0: Add Zve64f support for load and store insns frank.chang
2022-01-17 22:27 ` Alistair Francis
2022-01-18 1:37 ` Frank Chang
2021-12-29 2:33 ` [PATCH 04/17] target/riscv: rvv-1.0: Add Zve64f support for vmulh variant insns frank.chang
2022-01-17 22:30 ` Alistair Francis
2021-12-29 2:33 ` [PATCH 05/17] target/riscv: rvv-1.0: Add Zve64f support for vsmul.vv and vsmul.vx insns frank.chang
2022-01-17 22:31 ` Alistair Francis
2021-12-29 2:33 ` [PATCH 06/17] target/riscv: rvv-1.0: Add Zve64f support for scalar fp insns frank.chang
2022-01-17 22:39 ` Alistair Francis
2021-12-29 2:33 ` [PATCH 07/17] target/riscv: rvv-1.0: Add Zve64f support for single-width fp reduction insns frank.chang
2022-01-17 22:50 ` Alistair Francis
2021-12-29 2:33 ` [PATCH 08/17] target/riscv: rvv-1.0: Add Zve64f support for widening type-convert insns frank.chang
2022-01-17 22:51 ` Alistair Francis
2021-12-29 2:33 ` [PATCH 09/17] target/riscv: rvv-1.0: Add Zve64f support for narrowing " frank.chang
2022-01-17 22:53 ` Alistair Francis
2021-12-29 2:33 ` [PATCH 10/17] target/riscv: rvv-1.0: Allow Zve64f extension to be turned on frank.chang
2022-01-17 22:53 ` Alistair Francis
2021-12-29 2:33 ` [PATCH 11/17] target/riscv: rvv-1.0: Add Zve32f extension into RISC-V frank.chang
2022-01-17 22:54 ` Alistair Francis
2021-12-29 2:33 ` [PATCH 12/17] target/riscv: rvv-1.0: Add Zve32f support for configuration insns frank.chang
2022-01-17 22:54 ` Alistair Francis
2021-12-29 2:33 ` [PATCH 13/17] target/riscv: rvv-1.0: Add Zve32f support for scalar fp insns frank.chang
2022-01-17 22:55 ` Alistair Francis
2021-12-29 2:33 ` [PATCH 14/17] target/riscv: rvv-1.0: Add Zve32f support for single-width fp reduction insns frank.chang
2022-01-17 22:56 ` Alistair Francis
2021-12-29 2:33 ` [PATCH 15/17] target/riscv: rvv-1.0: Add Zve32f support for widening type-convert insns frank.chang
2022-01-17 22:56 ` Alistair Francis
2021-12-29 2:33 ` [PATCH 16/17] target/riscv: rvv-1.0: Add Zve32f support for narrowing " frank.chang
2022-01-17 22:57 ` Alistair Francis
2021-12-29 2:33 ` [PATCH 17/17] target/riscv: rvv-1.0: Allow Zve32f extension to be turned on frank.chang
2022-01-17 22:57 ` Alistair Francis
2022-01-17 12:55 ` Frank Chang [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=CANzO1D2MjL+d9Rconz4F9vtwzY9n2LOGChTZk_UW6F32TTMbuA@mail.gmail.com \
--to=frank.chang@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).