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 hniksic
Recipients hniksic, jbradaric, mark.dickinson, skrah
Date 2014-04-07.11:40:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1396870831.17.0.534945654481.issue21167@psf.upfronthosting.co.za>
In-reply-to
Content
Mark:
> > If Python requires strict IEEE 754 floating-point,
> 
> It doesn't (at the moment).

Does this imply that my patch is a better fix than requiring the builder to specify -fp-model strict to icc?

For our use case either solution is valid. For administrators and users testing or using Python with icc, it might be more convenient for Py_NAN to do the right thing with the default icc flags.
History
Date User Action Args
2014-04-07 11:40:31hniksicsetrecipients: + hniksic, mark.dickinson, skrah, jbradaric
2014-04-07 11:40:31hniksicsetmessageid: <1396870831.17.0.534945654481.issue21167@psf.upfronthosting.co.za>
2014-04-07 11:40:31hniksiclinkissue21167 messages
2014-04-07 11:40:30hniksiccreate