Faster _EXIT_TRACE via jump patching
Open
@Fidget-Spinner is already working on this.
Since Oct 21, 2025.
interpreter-core
topic-JIT
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 35.9k
- PR merge metrics
- PR metrics pending
Description
Feature or enhancement
Proposal:
When a trace ends in _EXIT_TRACE instead of JUMP_TO_TOP, it seems to cost a lot more to jump.
We should do like pypy and patch the trace exit to the actual machine code so it's a direct jump.
Has this already been discussed elsewhere?
No response given
Links to previous discussion of this feature:
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.