-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Fix failure with reimportSpillClique=true.
#48152
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
|
There are other places that could be cleaned there, for example:
but as we discussed with @AndyAyersMS it should be done later when we have more reasons to touch this area. |
|
PTAL @dotnet/jit-contrib I don't think it meets the bar for 5.0 back-port, what do you think? |
|
/azp run runtime-coreclr crossgen2 outerloop |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@JulieLeeMSFT it is not an issue, it is a pr. Do we want to move PRs to the project and assigned authors to them? |
|
The failures are unrelated, opened #48204 |
AndyAyersMS
left a comment
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 don't think it does (if it were customer reported, then maybe). |
The optimization added in #31677 could cause a failure in tricky conditions.
The test reproduces the failure without crossgen2, it fails on 5.0.
We needed:
<DebugType>Full</DebugType>;reimportSpillClique = true, by creating blocks like:when all the conditions were met we were creating a tree like:
and failing with assert during local visitor phase, with a noway assert in codegen, then with invalid program exception (in 5.0 release).
The stack when we
bashToNop:so during reimportation, we will try to use the invalid reference during
impSpillStackEntry.Fixes #47308.