From: Kito Cheng <kito.cheng@sifive.com>
To: Jim Wilson <jimw@sifive.com>
Cc: Keith Packard <keithp@keithp.com>, Newlib <newlib@sourceware.org>
Subject: Re: [PATCH 2/2] RISC-V: Implment finite and fpclassify
Date: Thu, 29 Oct 2020 11:02:29 +0800 [thread overview]
Message-ID: <CALLt3Tgdsr8H5wbC4i2hV4K0JCXpk9sersQgQSbTxonLrdcrwA@mail.gmail.com> (raw)
In-Reply-To: <CAFyWVaaEOF28zc_Oren-gwd70k_-T9fg=U6P31uGsNKS07WUGg@mail.gmail.com>
Hi Jim:
Thanks for your inputs, next round I'll send fcvt* and fsgnj* related
functions :)
On Thu, Oct 29, 2020 at 4:45 AM Jim Wilson <jimw@sifive.com> wrote:
> A copysign hook would also be useful. That is a single instruction, just
> like abs.
>
> Jim
>
>
>>
>>
next prev parent reply other threads:[~2020-10-29 3:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 6:19 [PATCH 1/2] RISC-V: Add fabs[f], fmax[f] and fmin[f] Kito Cheng
2020-10-27 6:19 ` [PATCH 2/2] RISC-V: Implment finite and fpclassify Kito Cheng
2020-10-27 18:11 ` Keith Packard
2020-10-27 18:22 ` Keith Packard
2020-10-28 15:42 ` Kito Cheng
2020-10-28 20:45 ` Jim Wilson
2020-10-29 3:02 ` Kito Cheng [this message]
2020-10-27 7:59 ` [PATCH 1/2] RISC-V: Add fabs[f], fmax[f] and fmin[f] Corinna Vinschen
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=CALLt3Tgdsr8H5wbC4i2hV4K0JCXpk9sersQgQSbTxonLrdcrwA@mail.gmail.com \
--to=kito.cheng@sifive.com \
--cc=jimw@sifive.com \
--cc=keithp@keithp.com \
--cc=newlib@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).