From: Stafford Horne <shorne@gmail.com>
To: GLIBC patches <libc-alpha@sourceware.org>
Cc: Linux OpenRISC <linux-openrisc@vger.kernel.org>,
Stafford Horne <shorne@gmail.com>
Subject: [PATCH] or1k: Update libm-test-ulps
Date: Thu, 12 Dec 2024 21:17:54 +0000 [thread overview]
Message-ID: <20241212211754.2139130-1-shorne@gmail.com> (raw)
Pick up new functions cospi, "Imaginary part of csin", exp10m1, exp2m1,
log10p1, log2p1, sinpi and tanpi.
---
I ran this on ron of a build from 2024-12-06. It looks like a few new functions
have been added upstream since. Posting, then will add new functions as needed
later.
sysdeps/or1k/nofpu/libm-test-ulps | 27 +++++++++++++++++++++++++++
1 file changed, 27 insertions(+)
diff --git a/sysdeps/or1k/nofpu/libm-test-ulps b/sysdeps/or1k/nofpu/libm-test-ulps
index e130fd8a1d..305b6cef70 100644
--- a/sysdeps/or1k/nofpu/libm-test-ulps
+++ b/sysdeps/or1k/nofpu/libm-test-ulps
@@ -535,6 +535,10 @@ Function: "cosh_upward":
double: 2
float: 2
+Function: "cospi":
+double: 1
+float: 1
+
Function: Real part of "cpow":
double: 2
float: 5
@@ -570,6 +574,9 @@ Function: Real part of "csin":
double: 1
float: 1
+Function: Imaginary part of "csin":
+float: 1
+
Function: Real part of "csin_downward":
double: 3
float: 3
@@ -763,6 +770,9 @@ Function: "exp10_upward":
double: 2
float: 1
+Function: "exp10m1":
+double: 3
+
Function: "exp2":
double: 1
@@ -776,6 +786,9 @@ Function: "exp2_upward":
double: 1
float: 1
+Function: "exp2m1":
+double: 2
+
Function: "exp_downward":
double: 1
float: 1
@@ -905,6 +918,9 @@ Function: "log10_upward":
double: 2
float: 2
+Function: "log10p1":
+double: 1
+
Function: "log1p":
double: 1
@@ -929,6 +945,9 @@ double: 1
Function: "log2_upward":
double: 1
+Function: "log2p1":
+double: 1
+
Function: "logp1":
double: 1
@@ -1003,6 +1022,10 @@ Function: "sinh_upward":
double: 3
float: 3
+Function: "sinpi":
+double: 1
+float: 1
+
Function: "tan_downward":
double: 1
@@ -1028,6 +1051,10 @@ Function: "tanh_upward":
double: 3
float: 3
+Function: "tanpi":
+double: 2
+float: 2
+
Function: "tgamma":
double: 9
--
2.47.0
reply other threads:[~2024-12-12 21:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20241212211754.2139130-1-shorne@gmail.com \
--to=shorne@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-openrisc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.