public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "brooks at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug math/16423] New: math-float, math-double failing logb_downward test with negative/positive zero difference on ppc32
Date: Thu, 09 Jan 2014 19:08:00 -0000 [thread overview]
Message-ID: <bug-16423-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=16423
Bug ID: 16423
Summary: math-float, math-double failing logb_downward test
with negative/positive zero difference on ppc32
Product: glibc
Version: 2.19
Status: NEW
Severity: normal
Priority: P2
Component: math
Assignee: unassigned at sourceware dot org
Reporter: brooks at gcc dot gnu.org
This is failing with GLIBC trunk as of 10am PST on 2014-01-09.
Configure with "../glibc/configure --prefix=/usr CC='gcc -m32' CXX='g++ -m32'
--target=powerpc32-unknown-linux-gnu --build=powerpc32-unknown-linux-gnu
--host=powerpc32-unknown-linux-gnu" on an IBM Power7; run "make" and "make
check".
I'm seeing failures in both math/test-float and math/test-double, with
essentially identical test-*.out outputs. The contents of test-float.out are
included below. This bug report is for the logb_downward failure (which is
that it's producing a negative zero where it should be producing a positive
zero); I've filed the llrint failure separately.
----
testing float (without inline functions)
Failure: Test: logb_downward (1.000e+0)
Result:
is: -0.00000000000000000000e+00 -0x0.00000000000000000000p+0
should be: 0.00000000000000000000e+00 0x0.00000000000000000000p+0
difference: 0.00000000000000000000e+00 0x0.00000000000000000000p+0
ulp : 0.0000
max.ulp : 0.0000
Failure: llrint (2097151.0): Exception "Inexact" set
Failure: llrint (8388608.0): Exception "Inexact" set
Failure: llrint (16777216.0): Exception "Inexact" set
Failure: llrint (4503601774854144.0): Exception "Inexact" set
Failure: llrint_tonearest (2097151.0): Exception "Inexact" set
Failure: llrint_tonearest (8388608.0): Exception "Inexact" set
Failure: llrint_tonearest (16777216.0): Exception "Inexact" set
Failure: llrint_tonearest (4503601774854144.0): Exception "Inexact" set
Failure: llrint_towardzero (2097151.0): Exception "Inexact" set
Failure: llrint_towardzero (8388608.0): Exception "Inexact" set
Failure: llrint_towardzero (16777216.0): Exception "Inexact" set
Failure: llrint_towardzero (4503601774854144.0): Exception "Inexact" set
Failure: llrint_downward (2097151.0): Exception "Inexact" set
Failure: llrint_downward (8388608.0): Exception "Inexact" set
Failure: llrint_downward (16777216.0): Exception "Inexact" set
Failure: llrint_downward (4503601774854144.0): Exception "Inexact" set
Failure: llrint_upward (2097151.0): Exception "Inexact" set
Failure: llrint_upward (8388608.0): Exception "Inexact" set
Failure: llrint_upward (16777216.0): Exception "Inexact" set
Failure: llrint_upward (4503601774854144.0): Exception "Inexact" set
Failure: nexttoward (qNaN, 1.1): Exception "Inexact" set
Test suite completed:
10843 test cases plus 10244 tests for exception flags and
10244 tests for errno executed.
22 errors occurred.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2014-01-09 19:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 19:08 brooks at gcc dot gnu.org [this message]
2014-01-09 19:25 ` [Bug math/16423] " brooks at gcc dot gnu.org
2014-01-09 19:31 ` brooks at gcc dot gnu.org
2014-01-09 20:09 ` brooks at gcc dot gnu.org
2014-01-09 20:14 ` brooks at gcc dot gnu.org
2014-01-09 21:03 ` joseph at codesourcery dot com
2014-02-06 18:39 ` [Bug math/16423] [powerpc] " jsm28 at gcc dot gnu.org
2014-06-13 9:05 ` fweimer at redhat dot com
2015-10-01 21:51 ` jsm28 at gcc dot gnu.org
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=bug-16423-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).