Re:Guido van Rossum's Performance tips for Python
by Peaker on Saturday October 13, 2012 @11:29AM
(#4648778)
Optimizing away getter/setter calls and function call overhead in general is well within the reach of current compilers.
[ Parent
| on HN ]
Re:Guido van Rossum's Performance tips for Python
by tjgq on Saturday October 13, 2012 @03:40PM
(#4649467)
In general, function calls cannot be inlined by the Python compiler because (almost) any function name may be re-bound to a different object at run time.
A very smart compiler could probably attempt to prove that no such modification can occur at run time throughout the whole program; but this is much harder than simply deciding whether inlining a given call is worth it or not.
Re:Guido van Rossum's Performance tips for Python
by cma on Saturday October 13, 2012 @05:51PM
(#4649850)
V8 handles them w minimal overhead in JavaScript.
Re:Guido van Rossum's Performance tips for Python
by pjscott on Sunday October 14, 2012 @12:37AM
(#4650656)
And more to the point, PyPy can do Python inlining with its tracing JIT. The method, in both cases, is similar: find some type assumptions that are useful and usually true, generate code under those assumptions, and fall back on more generic code if they're ever false.