➜

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 loewis
Recipients brian.curtin, loewis, nadeem.vawda, skrah, steve.dower, vstinner
Date 2014-06-14.12:49:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1402750158.91.0.754215581083.issue15993@psf.upfronthosting.co.za>
In-reply-to
Content 
Please don't. If the compiler is demonstrated to generate bad code in one case, we should *not* exclude that code from optimization, but not use optimization at all. How many other places will there be which also cause bad code being generated that just happens not to be uncovered by the test suite?
History
Date User Action Args
2014-06-14 12:49:18loewissetrecipients: + loewis, vstinner, nadeem.vawda, brian.curtin, skrah, steve.dower
2014-06-14 12:49:18loewissetmessageid: <1402750158.91.0.754215581083.issue15993@psf.upfronthosting.co.za>
2014-06-14 12:49:18loewislinkissue15993 messages
2014-06-14 12:49:18loewiscreate