Message117728
| Author |
mark.dickinson |
| Recipients |
Kiriakos.Vlahos, brian.curtin, eric.smith, loewis, mark.dickinson, sjmachin, skrah |
| Date |
2010年09月30日.12:04:13 |
| SpamBayes Score |
1.2667306e-10 |
| Marked as misclassified |
No |
| Message-id |
<1285848255.44.0.518693216551.issue9980@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> I would feel more comfortable if the correct FPU state is guaranteed.
I agree, in principle. In practice there are some thorny issues to deal with, and things to think about:
(1) The method for getting and setting the FPU precision varies from platform to platform
(2) Most modern x86 processors have *two* FPUs that might be used (the SSE unit, and the x87), each with their own control words.
(3) Depending on the platform and compiler flags, a Python executable / shared library might be using the x87 instructions, the SSE2 instructions, or a mixture of both.
(4) We need to bear in mind that an executable created on a modern 32-bit Linux machine (with SSE2) might still need to run on older machines that don't have SSE2. |
|