From: Carlos O'Donell <carlos@redhat.com>
To: sellcey@cavium.com, libc-alpha@sourceware.org
Subject: Re: long double test failures due to underflow exception getting set?
Date: Thu, 20 Jul 2017 00:58:00 -0000 [thread overview]
Message-ID: <041f2faf-c501-c70d-0c59-627fd8972543@redhat.com> (raw)
In-Reply-To: <201707192134.v6JLYQXo004521@sellcey-dt.caveonetworks.com>
On 07/19/2017 05:34 PM, Steve Ellcey wrote:
> Is anyone else seeing these failures with the latest glibc sources?
> I am getting them on aarch64 (standard ToT sources) and was wondering
> if this is an aarch64 specific problem or a more generic bug. Since
> all the failures involve long double I don't think they are using
> aarch64 specific code, but I could be wrong.
>
> FAIL: math/test-ldouble-cexp
> FAIL: math/test-ldouble-exp
> FAIL: math/test-ldouble-finite-cexp
> FAIL: math/test-ldouble-finite-exp
>
> I think these failures are new and all of the failures listed are
> about the Underflow exception being set:
>
> I.e.
>
> testing long double (without inline functions)
> Failure: exp (-0x1p-10000): Exception "Underflow" set
> Failure: exp (-0x2p-16384): Exception "Underflow" set
> Failure: exp (-0x4p-16384): Exception "Underflow" set
> Failure: exp (-0x4p-16448): Exception "Underflow" set
> Failure: exp (-0x4p-16496): Exception "Underflow" set
> Failure: exp (-0x8p-16448): Exception "Underflow" set
Neither DJ nor Szabolcs's glibc 2.26 builds showed those failures:
https://sourceware.org/glibc/wiki/Release/2.26
--
Cheers,
Carlos.
next prev parent reply other threads:[~2017-07-20 0:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 21:34 Steve Ellcey
2017-07-20 0:58 ` Carlos O'Donell [this message]
2017-07-20 16:28 ` Steve Ellcey
2017-07-20 17:32 Wilco Dijkstra
2017-07-20 17:40 ` Steve Ellcey
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=041f2faf-c501-c70d-0c59-627fd8972543@redhat.com \
--to=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=sellcey@cavium.com \
/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).