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 r.david.murray
Recipients mark.dickinson, paul.moore, pitrou, python-dev, r.david.murray, serhiy.storchaka, skrah, steve.dower, tim.golden, tim.peters, vstinner, zach.ware
Date 2015-11-08.01:31:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1446946280.79.0.0347787782649.issue24999@psf.upfronthosting.co.za>
In-reply-to
Content
FYI Intel provided us with a workaround that disables a compiler optimization for re and allows the test to not crash.  Zach, can you test no-ftz? Maybe we need to apply that to the entire python compile.  Also, can you make sure the appropriate person from Intel is nosy on this issue, assuming they have already registered?

Tim: any idea why would this only show up on Windows?  Also, if you want a copy of ICC to play with, we can arrange that.
 
I wonder if this issue has any effect on Intel's numpy support.
History
Date User Action Args
2015-11-08 01:31:21r.david.murraysetrecipients: + r.david.murray, tim.peters, paul.moore, mark.dickinson, pitrou, vstinner, tim.golden, skrah, python-dev, zach.ware, serhiy.storchaka, steve.dower
2015-11-08 01:31:20r.david.murraysetmessageid: <1446946280.79.0.0347787782649.issue24999@psf.upfronthosting.co.za>
2015-11-08 01:31:20r.david.murraylinkissue24999 messages
2015-11-08 01:31:19r.david.murraycreate