JIT: Use binary search in FlowGraphNaturalLoops::GetLoopByHeader
#108739
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 #108086. Since loops are stored in reverse post-order in
FlowGraphNaturalLoops::m_loops
, loop headers' post-order numbers are stored in descending order. Thus, we can use binary search, and since we plan to use loop-aware RPOs in more places, we should probably take advantage of this.