From: Richard Henderson <richard.henderson@linaro.org>
To: Frank Chang <frank.chang@sifive.com>
Cc: "open list:RISC-V" <qemu-riscv@nongnu.org>,
Bin Meng <bin.meng@windriver.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
Chih-Min Chao <chihmin.chao@sifive.com>,
Alistair Francis <alistair.francis@wdc.com>,
Palmer Dabbelt <palmer@dabbelt.com>
Subject: Re: [PATCH v3 2/2] target/riscv: change the api for single/double fmin/fmax
Date: Sat, 16 Oct 2021 10:56:33 -0700 [thread overview]
Message-ID: <2ac1b2bd-efa9-2005-5c0a-cace9346cbd7@linaro.org> (raw)
In-Reply-To: <CAE_xrPibc4W9FqoXUvLQ=pnW7h85ZYnYYwjLR-Rs+0NbifXc-A@mail.gmail.com>
On 10/16/21 1:52 AM, Frank Chang wrote:
> On Sat, Oct 16, 2021 at 1:05 AM Richard Henderson <richard.henderson@linaro.org
> <mailto:richard.henderson@linaro.org>> wrote:
>
> On 10/14/21 11:54 PM, frank.chang@sifive.com <mailto:frank.chang@sifive.com> wrote:
> > From: Chih-Min Chao<chihmin.chao@sifive.com <mailto:chihmin.chao@sifive.com>>
> >
> > The sNaN propagation behavior has been changed since
> > cd20cee7 inhttps://github.com/riscv/riscv-isa-manual
> <http://github.com/riscv/riscv-isa-manual>
> >
> > Signed-off-by: Chih-Min Chao<chihmin.chao@sifive.com <mailto:chihmin.chao@sifive.com>>
> > ---
> > target/riscv/fpu_helper.c | 8 ++++----
> > 1 file changed, 4 insertions(+), 4 deletions(-)
> >
> > diff --git a/target/riscv/fpu_helper.c b/target/riscv/fpu_helper.c
> > index 8700516a14c..1472ead2528 100644
> > --- a/target/riscv/fpu_helper.c
> > +++ b/target/riscv/fpu_helper.c
> > @@ -174,14 +174,14 @@ uint64_t helper_fmin_s(CPURISCVState *env, uint64_t rs1,
> uint64_t rs2)
> > {
> > float32 frs1 = check_nanbox_s(rs1);
> > float32 frs2 = check_nanbox_s(rs2);
> > - return nanbox_s(float32_minnum(frs1, frs2, &env->fp_status));
> > + return nanbox_s(float32_minnum_noprop(frs1, frs2, &env->fp_status));
> > }
>
> Don't you need to conditionalize behaviour on the isa revision?
>
>
> I will pick the right API based on CPU privilege spec version.
There's a separate F-extension revision number: 2.2.
But I'll leave it up to those more knowledgeable about the revision combinations actually
present in the field to decide.
r~
next prev parent reply other threads:[~2021-10-16 17:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 6:54 [PATCH RESEND v3 0/2] add APIs to handle alternative sNaN propagation for fmax/fmin frank.chang
2021-10-15 6:54 ` [PATCH v3 1/2] softfloat: " frank.chang
2021-10-15 17:00 ` Richard Henderson
2021-10-16 8:51 ` Frank Chang
2021-10-15 6:54 ` [PATCH v3 2/2] target/riscv: change the api for single/double fmin/fmax frank.chang
2021-10-15 17:05 ` Richard Henderson
2021-10-16 8:52 ` Frank Chang
2021-10-16 17:56 ` Richard Henderson [this message]
2021-10-17 0:55 ` Frank Chang
2021-10-17 6:57 ` Frank Chang
2021-10-18 0:18 ` Alistair Francis
2021-10-18 3:51 ` Frank Chang
-- strict thread matches above, loose matches on Subject: below --
2021-10-15 6:11 [PATCH v3 1/2] softfloat: add APIs to handle alternative sNaN propagation for fmax/fmin frank.chang
2021-10-15 6:11 ` [PATCH v3 2/2] target/riscv: change the api for single/double fmin/fmax frank.chang
2021-10-15 6:52 ` 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=2ac1b2bd-efa9-2005-5c0a-cace9346cbd7@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alistair.francis@wdc.com \
--cc=bin.meng@windriver.com \
--cc=chihmin.chao@sifive.com \
--cc=frank.chang@sifive.com \
--cc=palmer@dabbelt.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).