-
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
[release/7.0-preview5] Make gcunsafe for cpblk if it has gc pointers #70069
[release/7.0-preview5] Make gcunsafe for cpblk if it has gc pointers #70069
Conversation
Tagging subscribers to this area: @JulieLeeMSFT Issue DetailsBackport of #70053 to release/7.0-preview5 /cc @kunalspathak Customer ImpactTestingRiskIMPORTANT: If this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.
|
Failures are related to #68837 |
@dotnet/jit-contrib |
cc @jeffschwMSFT for servicing to PR5. |
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.
Approved. We should take for consideration in preview 5.
Approved by Tactics via email. |
Backport of #70053 to release/7.0-preview5
/cc @kunalspathak
Customer Impact
There was a bug where we would not mark a region as non-interruptible because it created references in registers that were not reported to GC. As such, if the GC kicks in, it will sporadically move non-GC pointers leading to crash or wrong behavior of the program.
Testing
Existing test coverage.
Risk
The bug was introduced with one of the refactoring changes and this PR just puts back those changes that were missed out.