-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Fix copy propagation #66070
Fix copy propagation #66070
Conversation
Now that we don't push defs for shadowed parameters, we don't want to pop them as well.
Tagging subscribers to this area: @JulieLeeMSFT Issue DetailsNow that we don't push any defs for shadowed parameters, we don't want to pop them as well.
|
/azp run runtime-coreclr jitstress, runtime-coreclr libraries-jitstress, runtime-coreclr libraries-jitstress2-jitstressregs, runtime-coreclr jitstress2-jitstressregs |
@BruceForstall - if jitstress legs are clean with this PR, we won't need #66060 |
Azure Pipelines successfully started running 4 pipeline(s). |
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
I'm willing to take this instead of the revert; unfortunately, the test build is broken :-( #66099 |
Actually, the libraries jitstress jobs here have a lot more failures than the "revert" job had, so possibly there's still a bug in the code. E.g., the "revert" jobs: And these jobs: In particular, it looks like with this change, So, I'm inclined to take the revert change. |
FWIW, looks like it's failing elsewhere too: #66100 (without stress). (Also, being behind |
Thanks. Looks like I found the problem before an issue was opened, so I assumed (incorrectly) that it might be related to this. It's hard to keep up with all the issues causing test failures :-( |
/azp run runtime-coreclr jitstress, runtime-coreclr libraries-jitstress, runtime-coreclr libraries-jitstress2-jitstressregs, runtime-coreclr jitstress2-jitstressregs |
Azure Pipelines successfully started running 4 pipeline(s). |
I'm not sure what to do about this. I want to validate it with the extra CI jobs, but they keep massively failing due to, apparently, infrastructure related issues, but re-running and restarting the tests don't fix them. And I don't see (many?) cases of these failures elsewhere. |
:( I did see a similar CI-out on one of my other changes about 12 hours ago: https://dev.azure.com/dnceng/public/_build/results?buildId=1642520&view=results. Now it seems stress is failing on #66143, that has been fixed, but not picked up (?). FWIW, I do think this is a very safe change from the perspective of not "making things worse": if we didn't have a def to pop, we'd always crash, and if we did the current code is identical to what was there before. |
I'm going to take a risk and merge this and hope for the best in the CI... |
Now that we don't push any defs for shadowed parameters, we don't want to pop them as well.