-
Notifications
You must be signed in to change notification settings - Fork 50
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
break up JUMP_IF_NOT_EXC/EG_MATCH #348
Comments
The check opcodes don't have an arg, so we could merge them and use the oparg to distinguish between the except and except* versions. |
Actually these two versions have different stack_effects, so this may not be a good idea. |
This is done. |
Repository owner
moved this from In Review
to Done
in Fancy CPython Board
Apr 8, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
JUMP_IF_NOT_EXC_MATCH and JUMP_IF_NOT_EG_MATCH are not hot opcodes (they are part of exception handling).
If we break them up into
(1) check match
(2) POP_JUMP_IF_FALSE
then we will have fewer jump opcodes.
The text was updated successfully, but these errors were encountered: