-
-
Notifications
You must be signed in to change notification settings - Fork 30.9k
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
GH-98686: Get rid of BINARY_OP_GENERIC
and COMPARE_OP_GENERIC
#99399
Conversation
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.
Thanks for the merge conflict. :-/
Don't you need to change the magic number? All the opcodes are different.
I'll wait until after #99313 is merged to land this. Anything else in flight that I should wait for?
We don't need to bump the magic number when adding/removing/changing specialized instructions or superinstructions, since those never get included in pycs! It's a pretty nice design. |
In that case I welcome your review of #99313. |
You have the baton. Have fun fixing the merge conflicts. :-) |
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.
IIUC this means that un-specializable binary ops and comparisons will now be a teensy bit slower because they always have to check the counter. But it seems clear that happens rarely enough.
This optimization made more sense back before we had exponential backoff (and the unquickened versions of these instructions were just laying around waiting to be used). Nowadays this move just complicates things, and doesn't actually seem to improve performance: