From: Alistair Francis <alistair23@gmail.com>
To: GNU C Library <libc-alpha@sourceware.org>
Subject: Math errors
Date: Mon, 30 Dec 2019 19:59:00 -0000 [thread overview]
Message-ID: <CAKmqyKNQXGVriszbWvfyAys-8aoe-ShWDqXr9H7fMs9M8Htm5A@mail.gmail.com> (raw)
Hey,
I'm running the `make check` tests on RV32 inside QEMU and about 800
math tests are failing with errors along these lines:
$ cat math/test-double-erf.out
Failure: Test: erf (0x1.4p+0)
Result:
is: 9.2290012825645817e-01 0x1.d8865d98abe00p-1
should be: 9.2290012825645829e-01 0x1.d8865d98abe01p-1
difference: 1.1102230246251565e-16 0x1.0000000000000p-53
ulp : 1.0000
max.ulp : 0.0000
Maximal error of `erf'
is : 1 ulp
accepted: 0 ulp
Failure: Test: erf_downward (-0x1.4d32f4p-12)
Result:
is: -3.5855754629430663e-04 -0x1.77f98ef609eb3p-12
should be: -3.5855754629430669e-04 -0x1.77f98ef609eb4p-12
difference: 5.4210108624275221e-20 0x1.0000000000000p-64
ulp : 1.0000
max.ulp : 0.0000
Failure: Test: erf_downward (0x1.44e722p+0)
Result:
is: 9.2732266856644440e-01 0x1.daca096caa26ap-1
should be: 9.2732266856644429e-01 0x1.daca096caa269p-1
difference: 1.1102230246251565e-16 0x1.0000000000000p-53
It seems the tests are failing due to small differences in the
floating point values.
Has anyone seen this before? I don't see how this can be related
specifically to the RV32 port, but I didn't see these errors when
running the ARM 32-bit testing. It's possible we are loosing
information in the QEMU floating point implementation for RV32.
Alistair
next reply other threads:[~2019-12-30 19:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 19:59 Alistair Francis [this message]
2019-12-30 22:28 ` Joseph Myers
2019-12-30 22:29 ` Joseph Myers
2020-01-03 2:18 ` Alistair Francis
2020-01-03 9:30 ` Szabolcs Nagy
2020-01-04 18:09 ` Alistair Francis
2020-01-07 1:29 ` Jim Wilson
2020-01-07 1:33 ` Alistair Francis
2020-01-07 18:29 ` Jim Wilson
2020-01-14 2:11 ` Alistair Francis
2020-01-14 2:29 ` Jonathan Nieder
2020-01-14 4:57 ` Alistair Francis
2020-01-14 7:28 ` Alistair Francis
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=CAKmqyKNQXGVriszbWvfyAys-8aoe-ShWDqXr9H7fMs9M8Htm5A@mail.gmail.com \
--to=alistair23@gmail.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).