Bug ID: 34100
           Summary: [APFloat] DoubleAPFloat::changeSign results in unusual
           Product: libraries
           Version: trunk
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: Support Libraries

`DoubleAPFloat::make*` always uses positive zero `Floats[1]`, even if
`Floats[0]` becomes negative (for a `Neg=true` argument).
But `DoubleAPFloat::changeSign` changes *both* `Floats[0]` and `Floats[1]`,
even when the latter is zero.
That makes negating a positive zero or infinity that is *different* than the
ones created by `makeZero(true)` and `makeInf(true)`, respectively.

My fix would be to guard the `Floats[1].changeSign();` call by

You are receiving this mail because:
You are on the CC list for the bug.
llvm-bugs mailing list

Reply via email to