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 pitrou
Recipients benjamin.peterson, collinwinter, jyasskin, pitrou, rnk
Date 2010-07-14.12:08:09
SpamBayes Score 0.01885565
Marked as misclassified No
Message-id <1279109291.52.0.831360968706.issue6033@psf.upfronthosting.co.za>
In-reply-to
Content
First, are these benchmark results jitted or non-jitted? Right now, non-jitted results are a stronger motivation for inclusion in main CPython, IMHO. 

Second, 2.7 won't receive any features / performance improvements anymore. It would be nice to have 3.2 (non-jitted) benchmark results.

Third, if removing intermediate allocations is the kind of optimizations a JIT will do anyway, does it make sense or not to make these optimizations explicit at the bytecode level? (this is really an open question, not a rhetorical one)
History
Date User Action Args
2010-07-14 12:08:11pitrousetrecipients: + pitrou, collinwinter, jyasskin, benjamin.peterson, rnk
2010-07-14 12:08:11pitrousetmessageid: <1279109291.52.0.831360968706.issue6033@psf.upfronthosting.co.za>
2010-07-14 12:08:10pitroulinkissue6033 messages
2010-07-14 12:08:09pitroucreate