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 steve.dower
Recipients christopher.hogan, paul.moore, r.david.murray, steve.dower, tim.golden, zach.ware
Date 2015-08-31.22:12:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1441059123.86.0.484726720235.issue24973@psf.upfronthosting.co.za>
In-reply-to
Content
I assume you're referring to #24974? The default (for MSVC) is /fp:precise, which should allow fenv_access, but maybe ICL uses /fp:fast by default for the extra speed?

It's not a safe 3.5 change now, but compiling with /fp:fast by default and using #pragma float_control(precise, push)/#pragma float_control(pop) around that section may be an option for 3.6, if the benchmarks show some value in it. Either way, the pragma is probably the better way to require particular behaviour for that section of code, rather than changing a global option.

I'm not totally opposed to allowing an extra option for setting flags when building, but there'll almost always be a better fix.
History
Date User Action Args
2015-08-31 22:12:03steve.dowersetrecipients: + steve.dower, paul.moore, tim.golden, r.david.murray, zach.ware, christopher.hogan
2015-08-31 22:12:03steve.dowersetmessageid: <1441059123.86.0.484726720235.issue24973@psf.upfronthosting.co.za>
2015-08-31 22:12:03steve.dowerlinkissue24973 messages
2015-08-31 22:12:03steve.dowercreate