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
bpo-47120: make POP_JUMP_IF_TRUE/FALSE/NONE/NOT_NONE relative #32400
Conversation
|
This branch includes the NONE/NOT_NONE commits, so look at the last commit to see the TRUE/FALSE part. |
|
Looks good to me. Want to run the buildbots on it before merging? There are more bit hacks we could do to streamline the jump computation and evalbreaker checks, but that's for another PR. |
|
If you want to schedule another build, you need to add the " |
|
As we predicted, this change eliminates 90% of the jumps with extended args: Static stats Before: After: |
|
If you want to schedule another build, you need to add the " |
|
If you want to schedule another build, you need to add the " |
|
The buildbots are happy. |
https://bugs.python.org/issue47120