From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: Xi Ruoyao <xry111@xry111.site>, Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: state of the ports
Date: Fri, 02 Feb 2024 22:40:41 +0100 [thread overview]
Message-ID: <3204286.Lt9SDvczpP@noumea> (raw)
In-Reply-To: <87il37t89e.fsf@oldenburg.str.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 901 bytes --]
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/
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, comrel, toolchain, base-system, perl, libreoffice)
https://wiki.gentoo.org/wiki/User:Dilfridge
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-02-02 21:40 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 [this message]
2024-02-22 17:11 ` Xi Ruoyao
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=3204286.Lt9SDvczpP@noumea \
--to=dilfridge@gentoo.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=xry111@xry111.site \
/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).