Skip to content

gh-136183: Deal with escapes in JIT optimizer's constant evaluator #136184

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

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

Fidget-Spinner
Copy link
Member

@Fidget-Spinner Fidget-Spinner commented Jul 1, 2025

@Fidget-Spinner
Copy link
Member Author

Skip news because no version of JIT has released with this yet.

@Fidget-Spinner Fidget-Spinner changed the title gh-136183: Deal with escapes gh-136183: Deal with escapes in JIT optimizer's constant evaluator Jul 1, 2025
Copy link
Member

@brandtbucher brandtbucher left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Confirmed that this fixes the issues we've been seeing.

@@ -5,6 +5,7 @@ on:
- '**jit**'
- 'Python/bytecodes.c'
- 'Python/optimizer*.c'
- 'Python/executor_cases.c.h'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we add optimizer_cases.c.h too?

self.assertIsNotNone(ex)
uops = get_opnames(ex)

# For now.. until we constant propagte it away.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
# For now.. until we constant propagte it away.
# For now... until we constant propagate it away.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants