[issue6033] LOOKUP_METHOD and CALL_METHOD optimization

Antoine Pitrou report at bugs.python.org
Wed Jul 14 14:08:11 CEST 2010


Antoine Pitrou <pitrou at free.fr> added the comment:

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)

----------
nosy: +collinwinter, jyasskin

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue6033>
_______________________________________


More information about the Python-bugs-list mailing list