From: Jim Wilson <jimw@sifive.com>
To: Alistair Francis <alistair23@gmail.com>
Cc: Joseph Myers <joseph@codesourcery.com>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: Math errors
Date: Mon, 6 Jan 2020 17:29:26 -0800 [thread overview]
Message-ID: <CAFyWVaYqcvNuLM9oE2GYGN82CBGGHbYJz=cZQYGJNySzJzUbpA@mail.gmail.com> (raw)
In-Reply-To: <CAKmqyKO6tkQjTkP85z3PoX13Y+Xgd1S6zZZo0HjZQsSMW=E=9A@mail.gmail.com>
On Thu, Jan 2, 2020 at 6:18 PM Alistair Francis <alistair23@gmail.com> wrote:
> There are a handful of math tests that seem to fail, but if I manually
> run the test a few times I will eventually get a pass. Any hints on
> what to do there?
There is a known bug in the RISC-V linux port where FP regs can leak
across fork and exec. This is normally not a fatal problem, except
for some tests that assume that the FP exception flags are clear on
program start. This can be false if they were set in the parent
process, which can cause some glibc math test failures. This can
result in failures that appear/disappear when run manually versus from
the testsuite driver. There are only about 5 tests that are affected.
The bug was finally fixed about a year and a half after I first
reported it. That happened only a few months ago. If you don't have
a recent enough version of the linux kernel you may not have the fix.
Jim
next prev parent reply other threads:[~2020-01-07 1:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 19:52 Math errors Alistair Francis
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 [this message]
2020-01-07 1:32 ` Alistair Francis
2020-01-07 18:29 ` Jim Wilson
2020-01-14 2:10 ` Alistair Francis
2020-01-14 2:28 ` 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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFyWVaYqcvNuLM9oE2GYGN82CBGGHbYJz=cZQYGJNySzJzUbpA@mail.gmail.com' \
--to=jimw@sifive.com \
--cc=alistair23@gmail.com \
--cc=joseph@codesourcery.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).