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 skrah
Recipients Serge Anuchin, mark.dickinson, pitrou, r.david.murray, rhettinger, serhiy.storchaka, skrah, steven.daprano, tim.peters, vstinner
Date 2015-07-12.17:40:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1436722847.88.0.542820366685.issue24567@psf.upfronthosting.co.za>
In-reply-to
Content
The double rounding problem even occurs between different versions
of gcc. I think ultimately we should put our foot down and ship with
sse2 enabled (not possible for 2.7 though, unless an LTS-PEP emerges).

If distributions want to break that, it's their business. :)
The gcc manual is quite upfront about the issue and really
recommends sse2 for reproducible results.
History
Date User Action Args
2015-07-12 17:40:47skrahsetrecipients: + skrah, tim.peters, rhettinger, mark.dickinson, pitrou, vstinner, steven.daprano, r.david.murray, serhiy.storchaka, Serge Anuchin
2015-07-12 17:40:47skrahsetmessageid: <1436722847.88.0.542820366685.issue24567@psf.upfronthosting.co.za>
2015-07-12 17:40:47skrahlinkissue24567 messages
2015-07-12 17:40:47skrahcreate