Start tracing at `JUMP_BACKWARD_NO_INTERRUPT`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 35.9k
- PR merge metrics
- PR metrics pending
Description
Feature or enhancement
Proposal:
We have just added the ability to start tracing at the beginning of functions.
That still leaves yield from and await loops to be run in the interpreter without jitting.
By starting tracing at JUMP_BACKWARD_NO_INTERRUPT we fill that gap.
Before we can do that, there are two problems we need to fix:
Once those are fixed, this should give us good jit coverage without degrading the quality of the traces.
Has this already been discussed elsewhere?
This is a minor feature, which does not need previous discussion elsewhere
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.
Research direction
Read issues 145047 and 146073 first, since this proposal depends on both being fixed. Then inspect CPython's tracing and JIT handling for JUMP_BACKWARD_NO_INTERRUPT, including the existing function-start tracing behavior. Done means yield from and await loops can begin tracing there without degrading trace quality.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100