From: Corinna Vinschen <vinschen@redhat.com>
To: Kito Cheng <kito.cheng@sifive.com>
Cc: newlib@sourceware.org
Subject: Re: RISC-V: Implement more machine-specific for libm
Date: Wed, 18 Nov 2020 09:39:35 +0100 [thread overview]
Message-ID: <20201118083935.GM41926@calimero.vinschen.de> (raw)
In-Reply-To: <20201118033543.74968-1-kito.cheng@sifive.com>
On Nov 18 11:35, Kito Cheng wrote:
> This patch set has implement more machine-specific for libm with F/D extension, most can be done with one instruction, verified on rv32im, rv32imaf, rv32imafd+ilp32, rv32imafd+ilp32d, rv64im, rv64imaf, rv64gc+lp64 rv64gc+lp64d.
>
Pushed.
Thanks,
Corinna
prev parent reply other threads:[~2020-11-18 8:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 3:35 Kito Cheng
2020-11-18 3:35 ` [PATCH 1/3] RISC-V: Add missing compile rule for s_finite.c, sf_finite.c, s_isinf.c and sf_isinf.c Kito Cheng
2020-11-18 3:35 ` [PATCH 2/3] RISC-V: Add machine-specific implementation for isnan[f] and copysign[f] Kito Cheng
2020-11-18 3:35 ` [PATCH 3/3] RISC-V: Add machine-specific implementation for lrint[f], lround[f], llrint[f] and llround[f] Kito Cheng
2020-11-18 8:39 ` Corinna Vinschen [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=20201118083935.GM41926@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=kito.cheng@sifive.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).