Repository navigation
[GR-79953] Optimize vectorcall dispatch. - #1200
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This change improves GraalPy’s vectorcall support for native types, with Cython-generated extension code being the primary beneficiary.
It allows more calls involving native callables and method descriptors to remain on the vectorcall path, avoiding unnecessary argument adaptation and transitions between native and managed.
It also enables Cython’s fast calling conventions and improves method-call dispatch so Cython-to-Cython calls can stay in native code more often.
The optimized behavior is not Cython-specific: other native extensions using vectorcall, native method descriptors, or native
tp_callimplementations benefit from the same lower-overhead dispatch paths.