Repository navigation

Change `JUMP_TO_TOP` to a more general backwards jump for tier 2. #117062

Closed

Labels

3.13interpreter-coreperformance

opened

on Mar 20, 2024

Currently we have the _JUMP_TO_TOP uop which jumps to the second uop in the tier 2 trace, as the first is reserved for _START_EXECUTOR.
Since this is a bit of an odd special case, we might as well add a more general jump backward.
Doing so would have a few advantages:

It is less confusing
It would actually simplify the JIT a bit
It would allow loop invariant code motion for looping traces.

Linked PRs

GH-117062: Make _JUMP_TO_TOP a general absolute jump #120854

markshannon
added
type-featureA feature request or enhancement

performancePerformance or resource usage

3.13only security fixes
on Mar 20, 2024
gvanrossum
added
interpreter-core(Objects, Python, Grammar, and Parser dirs)
and removed
type-featureA feature request or enhancement
on Mar 20, 2024
brandtbucher
added a commit that references this issue on Jun 24, 2024
GH-117062: Make _JUMP_TO_TOP a general absolute jump (GH-120854)
a47abdb
brandtbucher
closed this as completed on Jun 24, 2024
mrahtz
added a commit that references this issue on Jun 30, 2024
pythonGH-117062: Make _JUMP_TO_TOP a general absolute jump (pythonGH-…
e8e94c2
noahbkim
added a commit that references this issue on Jul 11, 2024
pythonGH-117062: Make _JUMP_TO_TOP a general absolute jump (pythonGH-…
b562d88
estyxx
added a commit that references this issue on Jul 17, 2024
pythonGH-117062: Make _JUMP_TO_TOP a general absolute jump (pythonGH-…
684f2da

to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

Labels

3.13interpreter-coreperformance

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests