public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Xi Ruoyao <xry111@xry111.site>
Cc: "Andreas K. Huettel" <dilfridge@gentoo.org>,  libc-alpha@sourceware.org
Subject: Re: state of the ports
Date: Fri, 02 Feb 2024 12:28:45 +0100	[thread overview]
Message-ID: <87il37t89e.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <b1c011b7284ed3718fd6a0a2641f1b058df7585d.camel@xry111.site> (Xi Ruoyao's message of "Fri, 02 Feb 2024 15:53:51 +0800")

* 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:
>
> testing double (without inline functions)
> Failure: Test: j0 (0x4.130e7p+4)
> Result:
>  is:         -1.0474906594151864e-04  -0x1.b759740016860p-14
>  should be:  -1.0474906594151868e-04  -0x1.b759740016863p-14
>  difference:  4.0657581468206416e-20   0x1.8000000000000p-65
>  ulp       :  3.0000
>  max.ulp   :  2.0000
> Maximal error of `j0'
>  is      : 3 ulp
>  accepted: 2 ulp
> Failure: Test: j0_downward (0xa.5b833p+4)
> Result:
>  is:          1.4785400727226293e-05   0x1.f01da00ab51d1p-17
>  should be:   1.4785400727226283e-05   0x1.f01da00ab51cbp-17
>  difference:  1.0164395367051604e-20   0x1.8000000000000p-67
>  ulp       :  6.0000
>  max.ulp   :  5.0000
> Maximal error of `j0_downward'
>  is      : 6 ulp
>  accepted: 5 ulp
> Failure: Test: j0_towardzero (0xa.5b833p+4)
> Result:
>  is:          1.4785400727226271e-05   0x1.f01da00ab51c4p-17
>  should be:   1.4785400727226283e-05   0x1.f01da00ab51cbp-17
>  difference:  1.1858461261560204e-20   0x1.c000000000000p-67
>  ulp       :  7.0000
>  max.ulp   :  6.0000
> Maximal error of `j0_towardzero'
>  is      : 7 ulp
>  accepted: 6 ulp
>
> Test suite completed:
>   212 test cases plus 208 tests for exception flags and
>     208 tests for errno executed.
>   6 errors occurred.
>
> I'm really not an expert in numerical analysis.  Any pointer to debug
> such a thing further?

I think these are well within the bounds that other ports accept.  If
there are genuine bugs, the results are off by thousands or millions of
ulps.

Thanks,
Florian


  reply	other threads:[~2024-02-02 11:28 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 [this message]
2024-02-02 21:40       ` Andreas K. Huettel
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=87il37t89e.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=dilfridge@gentoo.org \
    --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).