> But it doesn't need to store it *exactly*; it only tests that the > conversion reverses if PREC_OK (argument to TEST_I_F_VAL) is true, and > TEST_I_F sets PREC_OK to what should be an appropriate value (based on the > types involved, LDBL_MANT_DIG, etc.) in each case. The other tests are > applicable even when the conversion is inexact (and even if it overflows > to infinity): the compile-time conversions should agree with the runtime > ones since the results of converting integers to floating-point are > well-defined by IEEE.
Hmmm... in that case, the test is just failing, so I guess I'll debug it some more.
