Summary: | [powerpc] math-float, math-double failing logb_downward test with negative/positive zero difference on ppc32 | ||
---|---|---|---|
Product: | glibc | Reporter: | Brooks Moses <brooks> |
Component: | math | Assignee: | Not yet assigned to anyone <unassigned> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | Flags: | fweimer:
security-
|
Priority: | P2 | ||
Version: | 2.19 | ||
Target Milestone: | 2.19 | ||
Host: | powerpc*-*-* | Target: | |
Build: | Last reconfirmed: |
Description
Brooks Moses
2014-01-09 19:08:17 UTC
FWIW, this is also failing in math-ldouble. ...and this is failing in the test-ifloat, test-idouble, test-ildoubl inline variants as well. It turns out that this is probably a duplicate of bug 887, though I'll let someone else confirm before closing it. 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. |