[release/9.0] Ensure that Arm64 correctly handles multiplication of simd by a 64-bit scalar#106972
Merged
jeffschwMSFT merged 3 commits intorelease/9.0from Aug 27, 2024
Merged
Conversation
Contributor
|
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch |
EgorBo
approved these changes
Aug 26, 2024
Member
|
CC. @jeffschwMSFT, @JulieLeeMSFT for approval |
jeffschwMSFT
approved these changes
Aug 26, 2024
Member
jeffschwMSFT
left a comment
There was a problem hiding this comment.
approved. we can merge when ready
2 tasks
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.
3 participants
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 #106839 to release/9.0
/cc @tannergooding
Customer Impact
#106838
On Arm64 hardware, multiplication of a vector containing
Int64orUInt64elements by a scalar (such asvector128 * 5UL) could produce incorrect results.Regression
64-bit vector multiplication was not accelerated in .NET 8, but support was added in .NET 9. A refactoring then later caused the
fgMakeMultiUsecall to replace the wrong node leading the second multiplication to produce incorrect results.Testing
An explicit test was added to validate the codegen was correct. The test was authored so it also validates the scenarios for other platforms as well.
Risk
Low. This is a relatively simple fix and is simply ensuring the write node is being duplicated.