Skip to content
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

Merged
merged 1 commit into from
Mar 3, 2022
Merged

Conversation

SingleAccretion
Copy link
Contributor

Now that we don't push any defs for shadowed parameters, we don't want to pop them as well.

Now that we don't push defs for shadowed parameters, we don't want to pop them as well.
@dotnet-issue-labeler dotnet-issue-labeler bot added the area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI label Mar 2, 2022
@ghost ghost added the community-contribution Indicates that the PR has been added by a community member label Mar 2, 2022
@ghost
Copy link

ghost commented Mar 2, 2022

Tagging subscribers to this area: @JulieLeeMSFT
See info in area-owners.md if you want to be subscribed.

Issue Details

Now that we don't push any defs for shadowed parameters, we don't want to pop them as well.

Author: SingleAccretion
Assignees: -
Labels:

area-CodeGen-coreclr, community-contribution

Milestone: -

@SingleAccretion SingleAccretion marked this pull request as ready for review March 2, 2022 14:07
@kunalspathak
Copy link
Member

/azp run runtime-coreclr jitstress, runtime-coreclr libraries-jitstress, runtime-coreclr libraries-jitstress2-jitstressregs, runtime-coreclr jitstress2-jitstressregs

@kunalspathak
Copy link
Member

@BruceForstall - if jitstress legs are clean with this PR, we won't need #66060

@azure-pipelines
Copy link

Azure Pipelines successfully started running 4 pipeline(s).

Copy link
Member

@kunalspathak kunalspathak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@BruceForstall
Copy link
Member

I'm willing to take this instead of the revert; unfortunately, the test build is broken :-( #66099

@BruceForstall
Copy link
Member

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:
https://dev.azure.com/dnceng/public/_build/results?buildId=1639743&view=ms.vss-test-web.build-test-results-tab
https://dev.azure.com/dnceng/public/_build/results?buildId=1639742&view=ms.vss-test-web.build-test-results-tab

And these jobs:
https://dev.azure.com/dnceng/public/_build/results?buildId=1640729&view=ms.vss-test-web.build-test-results-tab
https://dev.azure.com/dnceng/public/_build/results?buildId=1640726&view=ms.vss-test-web.build-test-results-tab

In particular, it looks like with this change, System.Reflection.Tests.NullabilityInfoContextTests.NullablePublicOnlyOtherTypesTest is failing everywhere with "System.ArgumentNullException : Value cannot be null. (Parameter 'fieldInfo')"

So, I'm inclined to take the revert change.

@SingleAccretion
Copy link
Contributor Author

SingleAccretion commented Mar 2, 2022

In particular, it looks like with this change, System.Reflection.Tests.NullabilityInfoContextTests.NullablePublicOnlyOtherTypesTest is failing everywhere with "System.ArgumentNullException : Value cannot be null. (Parameter 'fieldInfo')"

FWIW, looks like it's failing elsewhere too: #66100 (without stress).

(Also, being behind main somewhat, I could not reproduce it locally)

@BruceForstall
Copy link
Member

FWIW, looks like it's failing elsewhere too: #66100 (without stress).

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 :-(

@BruceForstall
Copy link
Member

/azp run runtime-coreclr jitstress, runtime-coreclr libraries-jitstress, runtime-coreclr libraries-jitstress2-jitstressregs, runtime-coreclr jitstress2-jitstressregs

@azure-pipelines
Copy link

Azure Pipelines successfully started running 4 pipeline(s).

@BruceForstall
Copy link
Member

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.

@SingleAccretion
Copy link
Contributor Author

:(

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.

@BruceForstall
Copy link
Member

I'm going to take a risk and merge this and hope for the best in the CI...

@BruceForstall BruceForstall merged commit 7f3ae69 into dotnet:main Mar 3, 2022
@SingleAccretion SingleAccretion deleted the Fix-Copy-Prop branch March 7, 2022 21:54
@ghost ghost locked as resolved and limited conversation to collaborators Apr 7, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI community-contribution Indicates that the PR has been added by a community member
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants