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 Kiriakos.Vlahos, brian.curtin, eric.smith, loewis, mark.dickinson, sjmachin, skrah
Date 2010-09-30.07:15:58
SpamBayes Score 6.476884e-08
Marked as misclassified No
Message-id <1285830960.35.0.687512912632.issue9980@psf.upfronthosting.co.za>
In-reply-to
Content
[Eric]
> There's no doubt a performance issue with doing so, although someone
> would have to measure that. It may well be swamped by the memory
> allocation, etc. that is going on at the same time and so won't matter.

Yes, I think changing the FPU state involves a pipeline flush, with potentially serious performance impact.  But as you say, that may well be insignificant compared with everything else that's going on.

> Mark will no doubt know this better than I do, but I also assume that
> there's an issue with thread safety when changing such global state.

I don't *think* there's an issue here:  wouldn't FPU state be thread-local?
History
Date User Action Args
2010-09-30 07:16:00mark.dickinsonsetrecipients: + mark.dickinson, loewis, sjmachin, eric.smith, brian.curtin, skrah, Kiriakos.Vlahos
2010-09-30 07:16:00mark.dickinsonsetmessageid: <1285830960.35.0.687512912632.issue9980@psf.upfronthosting.co.za>
2010-09-30 07:15:58mark.dickinsonlinkissue9980 messages
2010-09-30 07:15:58mark.dickinsoncreate