Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
markshannon opened this issue Mar 20, 2024 · 0 comments
Closed

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

markshannon opened this issue Mar 20, 2024 · 0 comments
Labels
3.13 bugs and security fixes interpreter-core (Objects, Python, Grammar, and Parser dirs) performance Performance or resource usage

Comments

@markshannon
Copy link
Member

markshannon commented 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

@markshannon markshannon added type-feature A feature request or enhancement performance Performance or resource usage 3.13 bugs and security fixes labels Mar 20, 2024
@gvanrossum gvanrossum added interpreter-core (Objects, Python, Grammar, and Parser dirs) and removed type-feature A feature request or enhancement labels Mar 20, 2024
noahbkim pushed a commit to hudson-trading/cpython that referenced this issue Jul 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3.13 bugs and security fixes interpreter-core (Objects, Python, Grammar, and Parser dirs) performance Performance or resource usage
Projects
None yet
Development

No branches or pull requests

3 participants