PUTARG_STK/x86: mark push [mem] candidates reg optional - #68641
Merged
Conversation
|
Tagging subscribers to this area: @JulieLeeMSFT Issue DetailsIn #67400 I enabled containment for
|
SingleAccretion
marked this pull request as ready for review
April 28, 2022 14:26
Contributor
Author
|
x86 SPMI diffs timed out, OSX failure is #68654. @dotnet/jit-contrib |
SingleAccretion
force-pushed
the
PutargStk-RegOptional
branch
from
May 2, 2022 13:12
b7ae267 to
e377a4f
Compare
SingleAccretion
force-pushed
the
PutargStk-RegOptional
branch
from
May 8, 2022 14:37
e377a4f to
28bb507
Compare
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.
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.
In #67400 I enabled containment for
PUTARG_STKsources coming from memory on x86. This change completes that change by also enabling the "reg optional" setting, for yet more CQ:(All regressions are due to different allocation)