➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author mark.dickinson
Recipients arhadthedev, mark.dickinson
Date 2021-11-03.14:34:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1635950060.97.0.560599124907.issue45702@roundup.psfhosted.org>
In-reply-to
Content 
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 arithmetic at 53-bit precision (not 56-bit), following IEEE 754. It's mainly the ancient x86/x87 hardware that's problematic. This code has been working well on many different x64 platforms for around a decade now.

Can you describe the issue that you're seeing in more detail?
History
Date User Action Args
2021-11-03 14:34:21mark.dickinsonsetrecipients: + mark.dickinson, arhadthedev
2021-11-03 14:34:20mark.dickinsonsetmessageid: <1635950060.97.0.560599124907.issue45702@roundup.psfhosted.org>
2021-11-03 14:34:20mark.dickinsonlinkissue45702 messages
2021-11-03 14:34:20mark.dickinsoncreate