JIT: Introduce LclVarDsc::lvIsMultiRegDest
#113294
Merged
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.
With recent work to expand returned promoted locals into
FIELD_LIST
the only "whole references" of promoted locals we should see is when stored from a multi-reg node. This is the only knowledge the backend should need for correctness purposes, so introduce a bit to track this property, and switch the backend to check this instead.The existing
lvIsMultiRegRet
is essentially this + whether the local is returned. We should be able to remove this, but it is currently used for some outdated correctness checks in old promotion, so keep it around for now.This makes the new bitwise combination of returns kick in much more often for multireg returns. For example on win-arm64:
(which still can be improved)