Author zach.ware
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-09.16:16:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1447085794.99.0.770086675877.issue24999@psf.upfronthosting.co.za>
In-reply-to
Content
Stefan Krah wrote:
> If anyone worries that "-fp-model strict" will slow
> things down:  In the Python context these settings have
> no measurable impact:  A while ago I tested setting/restoring
> the control word *for every operation*, and even that did
> not have any impact.

If that's the case, would anyone (in particular, Steve, Tim or Tim) mind if we just made the default (for MSVC as well as ICC) /fp:strict?  It would be much easier to just change the global default than to try to either make it settable or to change it just when ICC is used.

As far as the segfault that this issue is actually about, compiling _sre.c with /Os seems to clear it up.  I believe Intel is looking into it deeper to determine whether it's an ICC bug or if there's something we should change in _sre.c.
History
Date User Action Args
2015-11-09 16:16:35zach.waresetrecipients: + zach.ware, tim.peters, paul.moore, mark.dickinson, pitrou, vstinner, tim.golden, r.david.murray, skrah, python-dev, serhiy.storchaka, steve.dower
2015-11-09 16:16:34zach.waresetmessageid: <1447085794.99.0.770086675877.issue24999@psf.upfronthosting.co.za>
2015-11-09 16:16:34zach.warelinkissue24999 messages
2015-11-09 16:16:34zach.warecreate