This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients ajaksu2, alexandre.vassalotti, bboissin, blaisorblade, christian.heimes, collinwinter, djc, facundobatista, jyasskin, lemburg, pitrou, ralph.corderoy, rhettinger, skip.montanaro, theatrus
Date 2009-01-06.14:30:07
SpamBayes Score 0.199182
Marked as misclassified No
Message-id <>
FWIW, I have made a quick attempt at removing the f->f_lasti assignment
in the few places where it could be removed, but it didn't make a
difference on my machine. The problem being that there are very few
places where it is legitimate to remove the assignment (even a call to
Py_DECREF can invoke arbitrary external code through destructors, so
even a very simple opcode such as POP_TOP needs the f->f_lasti assignment).

Another approach would be to create agregate opcodes, e.g.
BINARY_ADD_FAST would combine LOAD_FAST and BINARY_ADD. That's
orthogonal to the current issue though.
Date User Action Args
2009-01-06 14:30:09pitrousetrecipients: + pitrou, lemburg, skip.montanaro, collinwinter, rhettinger, facundobatista, christian.heimes, ajaksu2, alexandre.vassalotti, jyasskin, djc, ralph.corderoy, bboissin, blaisorblade, theatrus
2009-01-06 14:30:08pitrousetmessageid: <>
2009-01-06 14:30:08pitroulinkissue4753 messages
2009-01-06 14:30:07pitroucreate