Remove GTF_LATE_ARG - #68617
Merged
Merged
Conversation
This serves no purpose anymore after the call args refactoring and removing stores as call operands in LIR.
|
Tagging subscribers to this area: @JulieLeeMSFT Issue DetailsThis serves no purpose anymore after the call args refactoring and FWIW, what I plan to work on next in this area is to consistently include the signature type/class handle inside
|
Member
Author
|
cc @dotnet/jit-contrib |
BruceForstall
approved these changes
Apr 28, 2022
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 serves no purpose anymore after the call args refactoring and
removing stores as call operands in LIR.
FWIW, what I plan to work on next in this area is to consistently include the signature type/class handle inside
CallArgsomewhere.That should allow us to get rid of
GT_PUTARG_TYPEand also contributes to #51569 and #11057.