public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@xry111.site>
To: "Andreas K. Huettel" <dilfridge@gentoo.org>,
	Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: state of the ports
Date: Fri, 23 Feb 2024 01:11:31 +0800	[thread overview]
Message-ID: <559c2241354364b2f61672140a956251ab3b747d.camel@xry111.site> (raw)
In-Reply-To: <3204286.Lt9SDvczpP@noumea>

On Fri, 2024-02-02 at 22:40 +0100, Andreas K. Huettel wrote:
> Am Freitag, 2. Februar 2024, 12:28:45 CET schrieb Florian Weimer:
> > * Xi Ruoyao:
> > 
> > > On Fri, 2024-02-02 at 15:51 +0800, Xi Ruoyao wrote:
> > > > On Fri, 2024-02-02 at 03:35 +0100, Andreas K. Huettel wrote:
> > > > > mips (n64)
> > > > >  - mostly math failures
> > > > 
> > > > They are some sort of 2 ulp vs expected 1 ulp things.  I'm not yet sure
> > > > if they are hardware issues or Glibc bugs.
> > > 
> > > Something like:
> > > 
> > >  is      : 3 ulp
> > >  accepted: 2 ulp
> [..]
> > > 
> > > I'm really not an expert in numerical analysis.  Any pointer to debug
> > > such a thing further?
> 
> That looks like it can be "fixed" by regenerate-ulps, not like a real bug.
> 
> So the real number of fails is likely smaller indeed. \o/

An update on this: most of the failures were caused by my hardware:the
mips64r2 specification says FP madd should be unfused but the Loongson
hardware implements it as fused.  Passing the correct -march option to
GCC can fix them.  I'll note this in the wiki...

OTOH some ulps indeed needs an update and the updated values seem same
as the other ports using the generic math implementation (RISC-V and
LoongArch) : 

--- ../sysdeps/mips/mips64/libm-test-ulps	2024-02-23 00:56:46.428819912 +0800
+++ /home/xry111/git-repos/glibc-build/math/NewUlps	2024-02-23 00:59:29.085565020 +0800
@@ -1066,17 +1066,17 @@
 ldouble: 1
 
 Function: "j0":
-double: 2
+double: 3
 float: 9
 ldouble: 2
 
 Function: "j0_downward":
-double: 5
+double: 6
 float: 9
 ldouble: 9
 
 Function: "j0_towardzero":
-double: 6
+double: 7
 float: 9
 ldouble: 9
 
@@ -1146,6 +1146,7 @@
 ldouble: 8
 
 Function: "log":
+double: 1
 float: 1
 ldouble: 1

-- 
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University

  reply	other threads:[~2024-02-22 17:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-02  2:35 Andreas K. Huettel
2024-02-02  7:51 ` Xi Ruoyao
2024-02-02  7:53   ` Xi Ruoyao
2024-02-02 11:28     ` Florian Weimer
2024-02-02 21:40       ` Andreas K. Huettel
2024-02-22 17:11         ` Xi Ruoyao [this message]
2024-02-22 20:30           ` Andreas K. Huettel
2024-02-04  7:37 ` Stafford Horne
2024-02-04 11:40   ` Andreas K. Huettel
2024-02-25 22:47 ` Mark Wielaard
2024-02-26 12:44   ` Adhemerval Zanella Netto

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=559c2241354364b2f61672140a956251ab3b747d.camel@xry111.site \
    --to=xry111@xry111.site \
    --cc=dilfridge@gentoo.org \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@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).