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 Mark.Shannon
Recipients Mark.Shannon
Date 2022-03-17.16:23:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1647534190.7.0.0573728232462.issue47045@roundup.psfhosted.org>
In-reply-to
Content
The RESUME instruction was added to make resumption points explicit in the bytecode. This makes it easier to implement tracing, quickening, and interrupt checks as there is an explicit place to perform these checks.

Unfortunately, it also has considerable overhead. So we should remove it.
To do that, we need to:
1. Remove f_state from the InterpreterFrame so we don't need to update it.
2 .Quicken automatically in the adaptive instructions.
3. Check the evalbreaker when resuming a frame in the interpreter.
4. Add some metadata to the code object, so that we know when to fire "call" events when tracing.
History
Date User Action Args
2022-03-17 16:23:10Mark.Shannonsetrecipients: + Mark.Shannon
2022-03-17 16:23:10Mark.Shannonsetmessageid: <1647534190.7.0.0573728232462.issue47045@roundup.psfhosted.org>
2022-03-17 16:23:10Mark.Shannonlinkissue47045 messages
2022-03-17 16:23:10Mark.Shannoncreate