-
-
Notifications
You must be signed in to change notification settings - Fork 33.3k
gh-139525: Don't specialize functions which have a modified vectorcall #139524
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
Conversation
da9f886 to
4e30d66
Compare
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.
LGTM. Should we test for this?
797814b to
9a4d5b0
Compare
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
…torcall (python#139524) Don't specialize functions which have a modified vectorcall
|
Thanks @DinoV for the PR 🌮🎉.. I'm working now to backport this PR to: 3.14. |
|
Sorry, @DinoV, I could not cleanly backport this to |
…torcall (python#139524) Don't specialize functions which have a modified vectorcall
|
GH-139709 is a backport of this pull request to the 3.14 branch. |
The specializer isn't checking to see if
vectorcallis overridden, but the interpreter loop does. This causes a call which goes through this to randomly go through the interpreter on the first specialization, and then it de-opts and goes through vectorcall.