[issue32477] Move jumps optimization from the peepholer to the compiler
Serhiy Storchaka
report at bugs.python.org
Mon Dec 3 05:39:42 EST 2018
Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:
Simplified PR 5077. It uses now NEXT_BLOCK() to guarantee that a new block is always used after jumps. NEXT_BLOCK() was defined, but not used before.
bpo-35193 and bpo-9566 demonstrate that the code of peephole.c is complex and error-prone. Moving it to the upper level makes it more error-proof and general.
----------
versions: +Python 3.8 -Python 3.7
_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32477>
_______________________________________
More information about the Python-bugs-list
mailing list