JIT: Track visited blocks in LSRA with post-order number-based BitVec
#108932
+25
−29
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.
Since LSRA's block order computes a RPO traversal, we conveniently have post-order numbers on reachable blocks that can be used as keys in visited sets, and computing post-order numbers for unreached blocks is trivial. By using
bbPostorderNum
as the key instead ofbbNum
, we're one step closer to removingbbNum
andBasicBlockEpoch
.cc @dotnet/jit-contrib