From: Corinna Vinschen <vinschen@redhat.com>
To: Kito Cheng <kito.cheng@sifive.com>
Cc: newlib@sourceware.org, kito.cheng@gmail.com,
Jesse Huang <jesse.huang@sifive.com>
Subject: Re: [PATCH] RISC-V: Support Zfinx/Zdinx extension.
Date: Wed, 26 Jul 2023 15:27:32 +0200 [thread overview]
Message-ID: <ZMEfREofb0C4KfWg@calimero.vinschen.de> (raw)
In-Reply-To: <20230726100319.45915-1-kito.cheng@sifive.com>
On Jul 26 18:03, Kito Cheng via Newlib wrote:
> Zfinx/Zdinx are new extensions ratified in 2022, it similar to F/D extensions,
> support hard float operation for single/double precision, but the difference
> between Zfinx/Zdinx and F/D is Zfinx/Zdinx is operating under general purpose
> registers rather than dedicated floating-point registers.
>
> This patch improve the hard float support detection for RISC-V port, so
> that Zfinx/Zdinx can have better/right performance.
>
> Co-authored-by: Jesse Huang <jesse.huang@sifive.com>
> ---
> newlib/libc/include/machine/ieeefp.h | 4 ++--
> newlib/libc/machine/riscv/ieeefp.c | 10 +++++-----
> newlib/libc/machine/riscv/sys/fenv.h | 2 +-
> newlib/libm/common/math_config.h | 6 ++++--
> newlib/libm/machine/riscv/e_sqrt.c | 2 +-
> newlib/libm/machine/riscv/ef_sqrt.c | 2 +-
> newlib/libm/machine/riscv/feclearexcept.c | 3 ++-
> newlib/libm/machine/riscv/fegetenv.c | 3 ++-
> newlib/libm/machine/riscv/fegetexceptflag.c | 3 ++-
> newlib/libm/machine/riscv/fegetround.c | 3 ++-
> newlib/libm/machine/riscv/feholdexcept.c | 3 ++-
> newlib/libm/machine/riscv/feraiseexcept.c | 3 ++-
> newlib/libm/machine/riscv/fesetenv.c | 3 ++-
> newlib/libm/machine/riscv/fesetexceptflag.c | 3 ++-
> newlib/libm/machine/riscv/fesetround.c | 3 ++-
> newlib/libm/machine/riscv/fetestexcept.c | 3 ++-
> newlib/libm/machine/riscv/feupdateenv.c | 3 ++-
> newlib/libm/machine/riscv/riscv_math.h | 12 +++++++++---
> newlib/libm/machine/riscv/s_copysign.c | 3 ++-
> newlib/libm/machine/riscv/s_fabs.c | 3 ++-
> newlib/libm/machine/riscv/s_finite.c | 3 ++-
> newlib/libm/machine/riscv/s_fmax.c | 3 ++-
> newlib/libm/machine/riscv/s_fmin.c | 3 ++-
> newlib/libm/machine/riscv/s_fpclassify.c | 5 ++---
> newlib/libm/machine/riscv/s_isinf.c | 4 ++--
> newlib/libm/machine/riscv/s_isnan.c | 4 ++--
> newlib/libm/machine/riscv/s_llrint.c | 3 ++-
> newlib/libm/machine/riscv/s_llround.c | 3 ++-
> newlib/libm/machine/riscv/s_lrint.c | 3 ++-
> newlib/libm/machine/riscv/s_lround.c | 3 ++-
> newlib/libm/machine/riscv/sf_copysign.c | 3 ++-
> newlib/libm/machine/riscv/sf_fabs.c | 3 ++-
> newlib/libm/machine/riscv/sf_finite.c | 3 ++-
> newlib/libm/machine/riscv/sf_fmax.c | 3 ++-
> newlib/libm/machine/riscv/sf_fmin.c | 3 ++-
> newlib/libm/machine/riscv/sf_fpclassify.c | 3 ++-
> newlib/libm/machine/riscv/sf_isinf.c | 4 ++--
> newlib/libm/machine/riscv/sf_isnan.c | 4 ++--
> newlib/libm/machine/riscv/sf_llrint.c | 3 ++-
> newlib/libm/machine/riscv/sf_llround.c | 3 ++-
> newlib/libm/machine/riscv/sf_lrint.c | 3 ++-
> newlib/libm/machine/riscv/sf_lround.c | 3 ++-
> 42 files changed, 93 insertions(+), 56 deletions(-)
Pushed.
Thanks,
Corinna
next prev parent reply other threads:[~2023-07-26 13:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 10:03 Kito Cheng
2023-07-26 13:27 ` Corinna Vinschen [this message]
2023-10-10 5:26 ` Sebastian Huber
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=ZMEfREofb0C4KfWg@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=jesse.huang@sifive.com \
--cc=kito.cheng@gmail.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).