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 zach.ware
Recipients christopher.hogan, mark.dickinson, paul.moore, r.david.murray, rhettinger, skrah, steve.dower, tim.golden, zach.ware
Date 2015-09-01.16:34:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAKJDb-PKwNkO=i98x_CtA95+7=Xh5XLw1T4ujvNFGY-MwDXuPw@mail.gmail.com>
In-reply-to <1441124857.81.0.699016573765.issue24974@psf.upfronthosting.co.za>
Content
Steve Dower added the comment:
> fenv_access is not available when compiling with /fp:fast, which is apparently ICC's default.
>
> The proposed workaround here changes that default to /fp:strict, which is a very different model, for all of CPython. I proposed using #pragma float_control to force /fp:strict locally and enable fenv_access, rather than changing the entire build to use /fp:strict (even though fenv_access is not enabled everywhere by default).

Note that I'm not suggesting changing the default for everything to
/fp:strict.  The goal of the project building Python with ICC on
Windows is to change nothing for an MSVC build.  The default floating
point model should not change without a good reason, and this is not
it :)

I'll experiment with your suggestions, Steve and Stefan, discuss it
with Intel, and get back to you here.
History
Date User Action Args
2015-09-01 16:34:40zach.waresetrecipients: + zach.ware, rhettinger, paul.moore, mark.dickinson, tim.golden, r.david.murray, skrah, steve.dower, christopher.hogan
2015-09-01 16:34:40zach.warelinkissue24974 messages
2015-09-01 16:34:40zach.warecreate