This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug math/16423] math-float, math-double failing logb_downward test with negative/positive zero difference on ppc32
- From: "joseph at codesourcery dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Thu, 09 Jan 2014 21:02:32 +0000
- Subject: [Bug math/16423] math-float, math-double failing logb_downward test with negative/positive zero difference on ppc32
- Auto-submitted: auto-generated
- References: <bug-16423-131 at http dot sourceware dot org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=16423
--- Comment #4 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Thu, 9 Jan 2014, brooks at gcc dot gnu.org wrote:
> 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.
The reason for bug 887 being closed was spurious (and it should not have
been listed in NEWS as fixed for 2.16). There was a GCC fix only for more
recent Power processors. I think the bug should probably be kept open for
the point that glibc should work around the GCC bug (conditionally on a
configure test for whether the code generated needs it, i.e. that it uses
the problem arithmetic operations without modifying the rounding mode
temporarily). In addition, a GCC bug should be filed in GCC Bugzilla, if
not already open, for the bad code generation for these conversions with
-frounding-math.
--
You are receiving this mail because:
You are on the CC list for the bug.