From: Richard Henderson <richard.henderson@linaro.org>
To: frank.chang@sifive.com, qemu-devel@nongnu.org, qemu-riscv@nongnu.org
Subject: Re: [PATCH v3 0/6] target/riscv: support Zfh, Zfhmin extension v0.1
Date: Sat, 16 Oct 2021 11:03:47 -0700 [thread overview]
Message-ID: <e05ac0c9-3be7-7270-e46b-4da82466ad0e@linaro.org> (raw)
In-Reply-To: <20211016090742.3034669-1-frank.chang@sifive.com>
On 10/16/21 2:07 AM, frank.chang@sifive.com wrote:
> Changelog:
>
> v3:
> * Use the renamed softfloat min/max APIs: *_minimum_number()
> and *_maximum_number().
> * Pick softfloat min/max APIs based on CPU privilege spec version.
So... Given that Zfh 0.1 post-dates F 2.2, does that mean that Zfh should always use the
2019 functions?
r~
next prev parent reply other threads:[~2021-10-16 18:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-16 9:07 [PATCH v3 0/6] target/riscv: support Zfh, Zfhmin extension v0.1 frank.chang
2021-10-16 9:07 ` [PATCH v3 1/6] target/riscv: zfh: half-precision load and store frank.chang
2021-10-18 0:03 ` Alistair Francis
2021-10-18 2:15 ` Frank Chang
2021-10-18 4:28 ` Alistair Francis
2021-10-16 9:07 ` [PATCH v3 2/6] target/riscv: zfh: half-precision computational frank.chang
2021-10-17 23:50 ` Alistair Francis
2021-10-16 9:07 ` [PATCH v3 3/6] target/riscv: zfh: half-precision convert and move frank.chang
2021-10-17 23:59 ` Alistair Francis
2021-10-18 5:53 ` Richard Henderson
2021-10-18 6:11 ` Alistair Francis
2021-10-16 9:07 ` [PATCH v3 4/6] target/riscv: zfh: half-precision floating-point compare frank.chang
2021-10-18 0:00 ` Alistair Francis
2021-10-16 9:07 ` [PATCH v3 5/6] target/riscv: zfh: half-precision floating-point classify frank.chang
2021-10-18 0:01 ` Alistair Francis
2021-10-16 9:07 ` [PATCH v3 6/6] target/riscv: zfh: implement zfhmin extension frank.chang
2021-10-18 0:05 ` Alistair Francis
2021-10-16 18:03 ` Richard Henderson [this message]
2021-10-17 0:23 ` [PATCH v3 0/6] target/riscv: support Zfh, Zfhmin extension v0.1 Frank Chang
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=e05ac0c9-3be7-7270-e46b-4da82466ad0e@linaro.org \
--to=richard.henderson@linaro.org \
--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).