-
Notifications
You must be signed in to change notification settings - Fork 5.1k
JIT: add missing xarch RMW case #92252
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Handle the case where we're indirectly updating a local with a value that is not a constant. Fixes dotnet#92218.
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue DetailsHandle the case where we're indirectly updating a local with a value that is not a constant. Fixes #92218.
|
@BruceForstall PTAL This is a regression from .NET 7, so we'll need to make the case for a backport. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Probably should run jitstress
/azp run runtime-coreclr jitstress |
Azure Pipelines successfully started running 1 pipeline(s). |
The issue looks like the same as #41073, where it seems we elected not to fix it in |
My fix is in jitstress failures also happening in main (#92202 ). |
Build analysis doesn't seem to be tracking known jitstress issues, so will have to "merge on red". |
/backport to release/8.0 |
Started backporting to release/8.0: https://github.com/dotnet/runtime/actions/runs/6239547972 |
The issues with the JSON blobs need to have the "Known Build Error" label to be included in the analysis. I've added it to #92202 |
Aha. Thanks! |
Handle the case where we're indirectly updating a local with a value that is not a constant.
Fixes #92218.