report at bugs
Jun 12, 2008, 3:08 PM
Views: 72
Permalink
|
|
[issue2493] Remove unused constants from optimized code objects
|
|
Raymond Hettinger <rhettinger[at]users.sourceforge.net> added the comment:
The issue with unused constants is an artifact of the peepholer running
after the bytecode generation phase. When constant folding was
written, I intentionally left-out a step to remove unused constants
because of the code complexity, the fragility of the process, because
the benefits were inconsequential, and because it added to compilation
time.
It would be better to wait for the AST optimizer to replace the
peepholer. AST optimizations are upstream from bytecode generation, so
the unused constant issue simply disappears.
----------
resolution: -> rejected
status: open -> closed
_______________________________________
Python tracker <report[at]bugs.python.org>
<http://bugs.python.org/issue2493>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com
|
[issue2493] Remove unused constants from optimized code objects