unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Alistair Francis <alistair23@gmail.com>
To: Jim Wilson <jimw@sifive.com>
Cc: Joseph Myers <joseph@codesourcery.com>,
	GNU C Library <libc-alpha@sourceware.org>
Subject: Re: Math errors
Date: Mon, 6 Jan 2020 17:32:44 -0800	[thread overview]
Message-ID: <CAKmqyKOfm8pcJYPkZyp89WL+t7WMnmRJL3rXALYokj1A3pdu8g@mail.gmail.com> (raw)
In-Reply-To: <CAFyWVaYqcvNuLM9oE2GYGN82CBGGHbYJz=cZQYGJNySzJzUbpA@mail.gmail.com>

On Mon, Jan 6, 2020 at 5:29 PM Jim Wilson <jimw@sifive.com> wrote:
>
> 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.

Thanks for that Jim.

I have the latest 5.4.x kernel, I'm not sure if that has it or not.

I see a lot of math failures, so I'm not sure if it's the same issue.

Right now I have all of these failing:

    FAIL: math/atest-exp
    FAIL: math/atest-exp2
    FAIL: math/atest-sincos
    FAIL: math/test-double-cacos
    FAIL: math/test-double-cosh
    FAIL: math/test-double-fromfpx
    FAIL: math/test-double-islessgreater
    FAIL: math/test-double-iszero
    FAIL: math/test-double-jn
    FAIL: math/test-double-llrint
    FAIL: math/test-double-log1p
    FAIL: math/test-double-ufromfp
    UNSUPPORTED: math/test-fesetexcept-traps
    UNSUPPORTED: math/test-fexcept-traps
    FAIL: math/test-float-cabs
    FAIL: math/test-float-ilogb
    FAIL: math/test-float-isnormal
    FAIL: math/test-float-ldouble-div
    FAIL: math/test-float128-fmod
    FAIL: math/test-float128-iseqsig
    FAIL: math/test-float128-ufromfpx
    FAIL: math/test-float32-catan
    FAIL: math/test-float32-csinh
    FAIL: math/test-float32-float64x-add
    FAIL: math/test-float32-iszero
    FAIL: math/test-float32-jn
    FAIL: math/test-float32-significand
    FAIL: math/test-float32-sincos
    FAIL: math/test-float32-tanh
    FAIL: math/test-float32-yn
    FAIL: math/test-float32x-asinh
    FAIL: math/test-float32x-exp
    FAIL: math/test-float32x-log10
    FAIL: math/test-float32x-yn
    FAIL: math/test-float64-asinh
    FAIL: math/test-float64-canonicalize
    FAIL: math/test-float64-getpayload
    FAIL: math/test-float64-j1
    FAIL: math/test-float64-jn
    FAIL: math/test-float64x-cexp
    FAIL: math/test-float64x-ctanh
    FAIL: math/test-idouble-acos
    FAIL: math/test-idouble-catanh
    FAIL: math/test-idouble-copysign
    FAIL: math/test-idouble-csinh
    FAIL: math/test-idouble-erf
    FAIL: math/test-idouble-fminmag
    FAIL: math/test-idouble-hypot
    FAIL: math/test-idouble-lgamma
    FAIL: math/test-idouble-log1p
    FAIL: math/test-idouble-setpayload
    FAIL: math/test-ifloat-cacos
    FAIL: math/test-ifloat-cacosh
    FAIL: math/test-ifloat-casin
    FAIL: math/test-ifloat-erf
    FAIL: math/test-ifloat-llround
    FAIL: math/test-ifloat-pow
    FAIL: math/test-ifloat-setpayload
    FAIL: math/test-ifloat-sincos
    FAIL: math/test-ifloat-tan
    FAIL: math/test-ifloat-tgamma
    FAIL: math/test-ifloat128-ctan
    FAIL: math/test-ifloat128-j0
    FAIL: math/test-ifloat32-clog10
    FAIL: math/test-ifloat32-issignaling
    FAIL: math/test-ifloat32x-cpow
    FAIL: math/test-ifloat32x-fmaxmag
    FAIL: math/test-ifloat32x-j0
    FAIL: math/test-ifloat32x-remainder
    FAIL: math/test-ifloat64-cexp
    FAIL: math/test-ifloat64-floor
    FAIL: math/test-ifloat64-fmod
    FAIL: math/test-ifloat64-lrint
    FAIL: math/test-ifloat64-sincos
    FAIL: math/test-ildouble-lgamma
    FAIL: math/test-ldouble-exp
    FAIL: math/test-ldouble-fmod
    FAIL: math/test-ldouble-ilogb
    UNSUPPORTED: math/test-matherr
    UNSUPPORTED: math/test-matherr-2
    UNSUPPORTED: math/test-nearbyint-except-2

Alistair

>
> Jim

  reply	other threads:[~2020-01-07  1:33 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
2020-01-07  1:32         ` Alistair Francis [this message]
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=CAKmqyKOfm8pcJYPkZyp89WL+t7WMnmRJL3rXALYokj1A3pdu8g@mail.gmail.com \
    --to=alistair23@gmail.com \
    --cc=jimw@sifive.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).