Bug ID: 34098
           Summary: [APFloat] DoubleAPFloat::isInteger would always
                    trigger an assert.
           Product: libraries
           Version: trunk
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: Support Libraries

`DoubleAPFloat::isInteger` creates a zero `semPPCDoubleDoubleLegacy` APFloat
and then tries to add `Floats[0]` and `Floats[1]` to it, both of which are
always `semIEEEdouble`.

Addition (like the other binary operations) has an assert that the semantics
are identical so calling this method would always assert (if they're enabled),
but it's not even tested.

Also, I'd expect the correct implementation to be `Floats[0].isInteger() &&

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

Reply via email to