On Wed, 2016-12-14 at 11:50 +0100, Henri Verbeet wrote:
On 14 December 2016 at 11:34, Hans Leidekker hans@codeweavers.com wrote:
I didn't debug this (and I don't feel like it to be honest) but there
Ideally Austin would have, but fair enough.
are loops in the formatting code which terminate depending on the precision and rounding of long double operations. Valgrind can't match the precision of hardware because it uses 64-bit numbers internally to represent long doubles.
That makes some sense, although IIRC the FPU is by default in double precision mode as opposed to extended precision mode on Windows. (See also signal_init_thread() in ntdll.) Does that also imply a similar issue could happen if an application changed the FPU to single precision mode?
Yes. It would be interesting to see what webservices does on Windows in that case. We already set and restore the rounding mode.