-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
JIT: fix assert seen in some OSR cases #68048
Conversation
As a result of dotnet#67884, OSR compilations were looking at data in the `gsShadowVarInfo` array in cases where it was not initialized. Fix is to defer allocating the `gsShadowVarInfo` array until it's certain it will be initialized. Fixes dotnet#68003.
Tagging subscribers to this area: @JulieLeeMSFT Issue DetailsAs a result of #67884, OSR compilations were looking at data in the Fix is to defer allocating the Fixes #68003.
|
/azp run runtime-coreclr jitstress |
Azure Pipelines successfully started running 1 pipeline(s). |
Got an OSX repro, finally. The proposed fix above is not fixing the assert. |
/azp run runtime-coreclr jitstress |
Azure Pipelines successfully started running 1 pipeline(s). |
@BruceForstall PTAL |
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.
Looks like Compiler::optCopyPropPushDef()
was also potentially reading an uninitialized shadowCopy
field?
Yeah, I think it was... odd that that did not lead to any observable problem. |
As a result of #67884, OSR compilations were looking at data in the
gsShadowVarInfo
array in cases where it was not initialized.Fix is to null out
gsShadowVarInfo
array if there are no shadowed params.Fixes #68003.