JIT: Skip LSRA inserted nodes in gcIsWriteBarrierCandidate#81423
Merged
jakobbotsch merged 1 commit intodotnet:mainfrom Jan 31, 2023
Merged
JIT: Skip LSRA inserted nodes in gcIsWriteBarrierCandidate#81423jakobbotsch merged 1 commit intodotnet:mainfrom
jakobbotsch merged 1 commit intodotnet:mainfrom
Conversation
gcIsWriteBarrierCandidate is expected to return the same results during LSRA and during codegen, so it needs to skip GT_COPY and GT_RELOAD inserted on top of the data node. Fix dotnet#77141 Fix dotnet#77143
|
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch, @kunalspathak |
Member
Author
|
cc @dotnet/jit-contrib PTAL @EgorBo |
EgorBo
approved these changes
Jan 31, 2023
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.
gcIsWriteBarrierCandidate is expected to return the same results during LSRA and during codegen, so it needs to skip GT_COPY and GT_RELOAD inserted on top of the data node.
Fix #77141
Fix #77143