Bug ID: 34095
           Summary: [APFloat] Unit tests use integer overload with
                    floating-point literals.
           Product: libraries
           Version: trunk
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: Support Libraries

Constructor invocations such as `APFloat(APFloat::IEEEdouble(), 0.0)` have a
float literal (only `0.0`, `1.0` and `3.0` in all the unit tests) in the source
but the overload they reach is actually the `integerPart` one, *not* a `float`
or `double` overload (which only exists when `fltSemantics` *aren't* passed).

The values they're used with *happen* to be all integers and they do work, but
the unit tests are a bit misleading.

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

Reply via email to