Trace recording JIT
Open
@Fidget-Spinner is already working on this.
Since Sep 18, 2025.
interpreter-core
topic-JIT
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 35.9k
- PR merge metrics
- PR metrics pending
Description
This issue tracks progress of changing the JIT from one that projects traces to one that records them.
Follow-ups:
- Embed ENTER_EXECUTOR's executor in the bytecode and on trace graphs?
- Do not increase chain depth when side-exiting a branch, as that is just normal control-flow.
- Optimize through CALL_ALLOC_AND_ENTER_INIT
- Specialize: CALL_FUNCTION_EX,
__init__of slots, SEND foryield from - Loop peel.
Linked PRs
- gh-139111
- gh-140310
- gh-141573
- gh-141703
- gh-143033
- gh-144105
- gh-144394
- gh-146110
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.