From: Alistair Francis <alistair23@gmail.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 v6 0/8] target/riscv: support Zfh, Zfhmin extension v0.1
Date: Wed, 15 Dec 2021 09:05:05 +1000 [thread overview]
Message-ID: <CAKmqyKN5VFD9aaTTAQA15c-0yjKvk9-Ekpo9M8Fz_PWMv8WR2Q@mail.gmail.com> (raw)
In-Reply-To: <20211210074329.5775-1-frank.chang@sifive.com>
On Fri, Dec 10, 2021 at 5:44 PM <frank.chang@sifive.com> wrote:
>
> From: Frank Chang <frank.chang@sifive.com>
>
> Zfh - Half width floating point
> Zfhmin - Subset of half width floating point
>
> Zfh, Zfhmin v0.1 is now in public review period and is required by
> RVV extension:
> https://groups.google.com/a/groups.riscv.org/g/isa-dev/c/63gDCinXTwE/m/871Wm9XIBQAJ
>
> Zfh, Zfhmin can be enabled with -cpu option: Zfh=true and Zfhmin=true
> respectively.
>
> The port is available at:
> https://github.com/sifive/qemu/tree/zfh-upstream-v6
>
> Note: This patchset depends on another patchset listed in Based-on
> section below so it is not able to be built unless the patchset
> is applied.
>
> Changelog:
>
> v6:
> * Rebase on riscv-to-apply.next.
>
> v5:
> * Rebase on riscv-to-apply.next.
>
> v4:
> * Spilt Zfh, Zfhmin cpu properties related changes into individual
> patches.
>
> v3:
> * Use the renamed softfloat min/max APIs: *_minimum_number()
> and *_maximum_number().
> * Pick softfloat min/max APIs based on CPU privilege spec version.
> * Add braces for if statements in REQUIRE_ZFH() and
> REQUIRE_ZFH_OR_ZFHMIN().
> * Rearrange the positions of Zfh and Zfhmin cpu properties.
>
> v2:
> * Use {get,dest}_gpr APIs.
> * Add Zfhmin extension.
>
> Based-on: <20211021160847.2748577-1-frank.chang@sifive.com>
>
> Frank Chang (3):
> target/riscv: zfh: add Zfh cpu property
> target/riscv: zfh: implement zfhmin extension
> target/riscv: zfh: add Zfhmin cpu property
>
> Kito Cheng (5):
> target/riscv: zfh: half-precision load and store
> target/riscv: zfh: half-precision computational
> target/riscv: zfh: half-precision convert and move
> target/riscv: zfh: half-precision floating-point compare
> target/riscv: zfh: half-precision floating-point classify
>
> target/riscv/cpu.c | 2 +
> target/riscv/cpu.h | 2 +
> target/riscv/fpu_helper.c | 180 ++++++++
> target/riscv/helper.h | 29 ++
> target/riscv/insn32.decode | 38 ++
> target/riscv/insn_trans/trans_rvzfh.c.inc | 537 ++++++++++++++++++++++
> target/riscv/internals.h | 16 +
> target/riscv/translate.c | 20 +
> 8 files changed, 824 insertions(+)
> create mode 100644 target/riscv/insn_trans/trans_rvzfh.c.inc
Thanks!
Applied to riscv-to-apply.next
Alistair
>
> --
> 2.31.1
>
>
prev parent reply other threads:[~2021-12-14 23:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 7:43 [PATCH v6 0/8] target/riscv: support Zfh, Zfhmin extension v0.1 frank.chang
2021-12-10 7:43 ` [PATCH v6 1/8] target/riscv: zfh: half-precision load and store frank.chang
2021-12-10 7:43 ` [PATCH v6 2/8] target/riscv: zfh: half-precision computational frank.chang
2021-12-10 7:43 ` [PATCH v6 3/8] target/riscv: zfh: half-precision convert and move frank.chang
2021-12-10 7:43 ` [PATCH v6 4/8] target/riscv: zfh: half-precision floating-point compare frank.chang
2021-12-10 7:43 ` [PATCH v6 5/8] target/riscv: zfh: half-precision floating-point classify frank.chang
2021-12-10 7:43 ` [PATCH v6 6/8] target/riscv: zfh: add Zfh cpu property frank.chang
2021-12-10 7:43 ` [PATCH v6 7/8] target/riscv: zfh: implement zfhmin extension frank.chang
2021-12-10 7:43 ` [PATCH v6 8/8] target/riscv: zfh: add Zfhmin cpu property frank.chang
2021-12-14 23:05 ` Alistair Francis [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=CAKmqyKN5VFD9aaTTAQA15c-0yjKvk9-Ekpo9M8Fz_PWMv8WR2Q@mail.gmail.com \
--to=alistair23@gmail.com \
--cc=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).