-
Notifications
You must be signed in to change notification settings - Fork 5k
Don't emit unchecked write barrier for stack-allocated arrays #112711
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 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.
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
PTAL @AndyAyersMS @dotnet/jit-contrib 10 text diffs (basically, unchecked write barrier is replaced with the checked one, no size diff). |
Is CI is no longer running the full set of tests? |
Going to bounce this... |
I think it still is? I bet the new github UI confused you (it did it to me too) |
Preview 2 is missing an important fix for stack-allocated arrays of GC types: dotnet#112711. This can lead to unexpected crashes in jitted code. Disable array stack allocation to work around this.
* [10.0/preview-2] JIT: disable array stack allocation Preview 2 is missing an important fix for stack-allocated arrays of GC types: #112711. This can lead to unexpected crashes in jitted code. Disable array stack allocation to work around this. * adjust test case
Fixes #112709