JIT: Remove VisitLoopBlocksLexical utility - #110490
Merged
amanasifkhalid merged 1 commit intoDec 12, 2024
Merged
Conversation
This was referenced Dec 6, 2024
Contributor
Author
|
cc @dotnet/jit-contrib, @jakobbotsch PTAL. Small diffs from churn in the lexical order of cloned loop blocks. Thanks! |
hez2010
pushed a commit
to hez2010/runtime
that referenced
this pull request
Dec 14, 2024
Follow-up to dotnet#110227. In the few places where we still visit loop blocks in lexical order, just visit them in RPO instead.
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.
2 participants
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.
Follow-up to #110227. In the few places where we still visit loop blocks in lexical order, just visit them in RPO instead.