-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
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
base: main
Are you sure you want to change the base?
Conversation
Skip news because no version of JIT has released with this yet. |
There was a problem hiding this 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' |
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# For now.. until we constant propagte it away. | |
# For now... until we constant propagate it away. |
_BINARY_OP
evaluation produces UB (and incorrect results) #136183