public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Andreas K. Huttel <dilfridge@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] i686: Regenerate ulps
Date: Fri, 14 Jun 2024 19:24:49 +0000 (GMT)	[thread overview]
Message-ID: <20240614192449.14F1E3882100@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=3953b5b88f674d33675662e2e8d3a5f3cfda720c

commit 3953b5b88f674d33675662e2e8d3a5f3cfda720c
Author: Andreas K. Hüttel <dilfridge@gentoo.org>
Date:   Fri Jun 14 21:23:10 2024 +0200

    i686: Regenerate ulps
    
    Linux pinacolada 6.6.32-gentoo #1 SMP PREEMPT Sun Jun  9 14:18:17 CEST 2024 x86_64 Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz GenuineIntel GNU/Linux
    32bit build for multilib environment
    
    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>

Diff:
---
 sysdeps/i386/i686/fpu/multiarch/libm-test-ulps | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/sysdeps/i386/i686/fpu/multiarch/libm-test-ulps b/sysdeps/i386/i686/fpu/multiarch/libm-test-ulps
index 9eb3088d7a..b892c43e59 100644
--- a/sysdeps/i386/i686/fpu/multiarch/libm-test-ulps
+++ b/sysdeps/i386/i686/fpu/multiarch/libm-test-ulps
@@ -1431,20 +1431,20 @@ float128: 3
 ldouble: 2
 
 Function: "log2p1_downward":
-double: 1
-float: 1
+double: 2
+float: 2
 float128: 3
 ldouble: 4
 
 Function: "log2p1_towardzero":
-double: 1
-float: 1
+double: 2
+float: 2
 float128: 2
 ldouble: 4
 
 Function: "log2p1_upward":
 double: 1
-float: 1
+float: 2
 float128: 2
 ldouble: 5

             reply	other threads:[~2024-06-14 19:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-14 19:24 Andreas K. Huttel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-01-02 18:49 Florian Weimer
2021-02-03 17:47 [glibc] i686: Regenerate ULPs Siddhesh Poyarekar

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=20240614192449.14F1E3882100@sourceware.org \
    --to=dilfridge@sourceware.org \
    --cc=glibc-cvs@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).