[RegisterCoalescer] Fix subrange update when rematerialization widens a def #151974
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.
Currently, when an instruction rematerialized by the register coalescer defines more subregs of the destination register
than the original COPY instruction did, we only add dead defs for the newly defined subregs if they were not defined anywhere
else. For example, consider something like this before rematerialization:
that would look like this after rematerializing
%0:A dead def would not be added for
%1.sub_lo64_hi32at the 2nd instruction because it's subrange wasn't empty beforehand.