This repository was archived by the owner on Jan 23, 2023. It is now read-only.
[release/3.1] Capture AVX context when redirecting threads for suspension#28131
Merged
aik-jahoda merged 1 commit intodotnet:release/3.1from Feb 10, 2021
Merged
[release/3.1] Capture AVX context when redirecting threads for suspension#28131aik-jahoda merged 1 commit intodotnet:release/3.1from
aik-jahoda merged 1 commit intodotnet:release/3.1from
Conversation
Member
Author
|
@mangod9 - this is a similar port as in dotnet/runtime#47447 . |
mangod9
approved these changes
Feb 1, 2021
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Re: dotnet/runtime#38974, dotnet/runtime#47016
These are the same changes as in dotnet/runtime#47212
Customer Impact
Once we move to the new toolset, managed code that employs AVX register set directly or indirectly (as in
Span<byte>helpers) may occasionally observe incorrect computation results.Testing
The fix was tested and merged in master. This is a port of the fix.
Risk
Master branch had this fix for some time now. Based on that the risk is low.