For Debug, make sure we use right register selection heuristics to match with Release #97657
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.
If a method needs consecutive register, we do not use
*minimal()register allocation strategy added in #96386. The reason being that in some cases, the*minimalmight allocate registers that will sometime obstruct us from allocating consecutive registers. Also, to handle consecutive registers scenarios in*minimal()methods eats up the massive TP gain that we see in Arm64 for MinOpts because of the checks we need to add ifrefPositionneeds consecutive register or not. I forgot to add a condition for consecutive register while deciding the selection heuristics.Fixes: #97638