[Python-Dev] Wordcode: new regular bytecode using 16-bit units (original) (raw)
Ryan Gonzalez rymg19 at gmail.com
Wed Apr 13 18:11:14 EDT 2016
- Previous message (by thread): [Python-Dev] Wordcode: new regular bytecode using 16-bit units
- Next message (by thread): [Python-Dev] Wordcode: new regular bytecode using 16-bit units
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
So code that depends on iterating through bytecode via HAS_ARG is going to break...
Darn it. :/
-- Ryan [ERROR]: Your autotools build scripts are 200 lines longer than your program. Something’s wrong. http://kirbyfan64.github.io/ On Apr 13, 2016 4:44 PM, "Victor Stinner" <victor.stinner at gmail.com> wrote:
Le mercredi 13 avril 2016, Ryan Gonzalez <rymg19 at gmail.com> a écrit :
What is the value of HASARG going to be now?
I asked Demur to keep HASARG(). Not really for backward compatibility, but for the dis module: to keep a nice assembler. There are also debug traces in ceval.c which use it. For ceval.c, we might use HASARG() to micro-optimize oparg=0 (hardcode 0 rather than reading the bytecode) for operators with no argument. Or maybe it's completly useless :-) Victor -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20160413/f6051af4/attachment.html>
- Previous message (by thread): [Python-Dev] Wordcode: new regular bytecode using 16-bit units
- Next message (by thread): [Python-Dev] Wordcode: new regular bytecode using 16-bit units
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]