[issue26549] co_stacksize is calculated from unoptimized code
Brett Cannon
report at bugs.python.org
Sun Mar 13 13:36:44 EDT 2016
Brett Cannon added the comment:
I also suspect you're right, Antti, that the stack size is calculated prior to the bytecode being passed to through the peepholer which would have made the built tuple a value in the const array.
Off the top of my head I don't remember where the stack size calculation is made, but my suspicion is it's in the AT -> bytecode step, which would mean making it work from bytecode would mean re-implementing that calculation to work from the bytecode itself (assuming I'm right).
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26549>
_______________________________________
More information about the Python-bugs-list
mailing list