unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu via Libc-alpha" <libc-alpha@sourceware.org>
To: GNU C Library <libc-alpha@sourceware.org>
Subject: New math test failures on Fedora/33
Date: Mon, 11 Jan 2021 08:00:09 -0800	[thread overview]
Message-ID: <CAMe9rOqtJNEDp5wX4Wn5htrxm6cUa0y+9ZUcooeMoLEHPSP=+g@mail.gmail.com> (raw)

On Fedora 33, I got these new math test failures:

FAIL: math/test-double-cosh
FAIL: math/test-float32x-cosh
FAIL: math/test-float64-cosh

for i686 glibc like

Failure: cosh_upward (-0x2.c5d374p+12): Exception "Overflow" not set
Failure: cosh_upward (-0x2.c5d37700c6bb2p+12): Exception "Overflow" not set
Failure: cosh_upward (-0x2.c5d37700c6bbp+12): Exception "Overflow" not set
Failure: cosh_upward (-0x2.c5d378p+12): Exception "Overflow" not set
Failure: cosh_upward (-0x2.c679d1f73f0fcp+8): Exception "Overflow" not set
Failure: cosh_upward (-0x2.c679d4p+8): Exception "Overflow" not set
Failure: cosh_upward (-0xf.ffffffffffff8p+1020): Exception "Overflow" not set
Failure: cosh_upward (-0xf.fffffp+124): Exception "Overflow" not set
Failure: cosh_upward (0x2.c5d374p+12): Exception "Overflow" not set
Failure: cosh_upward (0x2.c5d37700c6bb2p+12): Exception "Overflow" not set
Failure: cosh_upward (0x2.c5d37700c6bbp+12): Exception "Overflow" not set
Failure: cosh_upward (0x2.c5d378p+12): Exception "Overflow" not set
Failure: cosh_upward (0x2.c679d1f73f0fcp+8): Exception "Overflow" not set
Failure: cosh_upward (0x2.c679d4p+8): Exception "Overflow" not set
Failure: cosh_upward (0xf.ffffffffffff8p+1020): Exception "Overflow" not set
Failure: cosh_upward (0xf.fffffp+124): Exception "Overflow" not set


-- 
H.J.

             reply	other threads:[~2021-01-11 16:00 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-11 16:00 H.J. Lu via Libc-alpha [this message]
2021-01-11 16:28 ` New math test failures on Fedora/33 Adhemerval Zanella via Libc-alpha
2021-01-11 18:37   ` H.J. Lu via Libc-alpha
2021-01-11 19:21     ` Adhemerval Zanella via Libc-alpha
2021-01-12  7:13       ` Paul Zimmermann
2021-01-12 17:29         ` Adhemerval Zanella via Libc-alpha
2021-01-12 17:39           ` Siddhesh Poyarekar
2021-01-12 19:14           ` Tulio Magno Quites Machado Filho via Libc-alpha
2021-01-13  6:34             ` Paul Zimmermann
2021-01-13 12:51               ` Adhemerval Zanella via Libc-alpha
2021-01-14 12:48                 ` Carlos O'Donell via Libc-alpha
2021-01-14 12:59             ` Carlos O'Donell via Libc-alpha
2021-01-14 13:19               ` Paul Zimmermann
2021-01-14 14:47                 ` Carlos O'Donell via Libc-alpha
2021-01-14 13:07 ` Carlos O'Donell via Libc-alpha
  -- strict thread matches above, loose matches on Subject: below --
2021-01-18 14:22 Wilco Dijkstra via Libc-alpha
2021-01-18 14:36 ` Paul Zimmermann
2021-01-18 14:36 ` Andreas Schwab
2021-01-18 15:18   ` Paul Zimmermann
2021-01-18 17:03     ` Andreas Schwab
2021-01-18 15:20   ` Wilco Dijkstra via Libc-alpha
2021-01-18 15:30     ` Carlos O'Donell via Libc-alpha
2021-01-18 15:38       ` Andreas Schwab
2021-01-18 16:58 ` Florian Weimer via Libc-alpha
2021-01-19 15:59 ` Patrick McGehearty via Libc-alpha

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='CAMe9rOqtJNEDp5wX4Wn5htrxm6cUa0y+9ZUcooeMoLEHPSP=+g@mail.gmail.com' \
    --to=libc-alpha@sourceware.org \
    --cc=hjl.tools@gmail.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).