Oleg Iarygin added the comment:
When I first saw "default rounding precision of 64 bits", I've thought it's
about "64 bit precision", aka binary64, aka double. So I suggested that the
code expects some hardly known Intel FPU-specific binary56 instead. Now, after
a second paragraph of your re
Mark Dickinson added the comment:
I'm not sure I understand the problem that you're reporting - what issues are
you seeing in practice?
x64 should be fine here. In normal circumstances, the compiled version of
dtoa.c will be using SSE2 instructions and will already be doing floating-point
a
New submission from Oleg Iarygin :
File configure.ac:4617 states the following:
> # The short float repr introduced in Python 3.1 requires the
> # correctly-rounded string <-> double conversion functions from
> # Python/dtoa.c, which in turn require that the FPU uses 53-bit
> # rounding; this i
