[release/6.0] Fix incorrect SIMD temp allocation for Vector256 with AVX2 disabled #58850
Conversation
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
The NI_Vector256_GetElement intrinsic, in some situations, requires a stack temporary. With AVX2 disabled, this temporary was getting allocated as a TYP_SIMD16 instead of a TYP_SIMD32, leading to overwriting the local variable. Add a type argument to the temp variable allocation, and allocate the temp as the largest sized type required by any use. Fixes #58295
ghost
added
the
area-CodeGen-coreclr
|
Tagging subscribers to this area: @JulieLeeMSFT Issue DetailsBackport of #58820 to release/6.0 /cc @BruceForstall Customer ImpactTestingRisk
|
Contributor
|
@tannergooding @dotnet/jit-contrib PTAL -- port of fix to release/6.0 |
Member
|
CC @jeffschwMSFT for 6.0 backport. |
Member
|
Please fill in the customer impact and request a code review. |
Contributor
|
@jeffschwMSFT This is ready now |
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.
Backport of #58820 to release/6.0
/cc @BruceForstall
Customer Impact
Using the
Vector256<T>GetElement API on a machine with AVX but without AVX2 could, in some instances, lead to a corrupt stack frame and data corruption.Testing
Manual testing of the fix on the repro case, as well as SuperPMI asm diffs to determine other impact of the change, as well as standard PR CI testing.
Risk
Low.