JIT: Remove fgMoveHotJumps
#112016
Open
JIT: Remove fgMoveHotJumps
#112016
+0
−206
Conversation
This file contains 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
dotnet-issue-labeler
bot
added
the
area-CodeGen-coreclr
|
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Part of #107749. Based on the plans outlined in #111989 (comment), we should rely on 3-opt to improve upon the baseline RPO layout;
fgMoveHotJumpsis a meek approximation of the former. RemovingfgMoveHotJumpschurns the initial layout into 3-opt, which seems to redirect it to a different local optimum with some frequency. The cases where the new local optimum is worse aren't a justification forfgMoveHotJumps's existence, but motivation for improving 3-opt's ability to find globally-optimal layouts.