-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Updating Vector128 to have its software fallback be 2x Vector64<T> ops #76592
Conversation
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
src/libraries/System.Private.CoreLib/src/System/Runtime/Intrinsics/Vector128.cs
Outdated
Show resolved
Hide resolved
Tagging subscribers to this area: @dotnet/area-system-runtime-intrinsics Issue DetailsSame general change as #76221. In this case, there is no theoretical perf benefit for any supported platforms. It just simplifies the implementation overall and makes it easier to update logic if that's ever desired. As with the Vector256 cleanup, I audited the doc comments at the same time and ensured they were consistent and correct.
|
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.
Looks good overall, added a few clarifications and suggestions.
Same general change as #76221.
In this case, there is no theoretical perf benefit for any supported platforms. It just simplifies the implementation overall and makes it easier to update logic if that's ever desired.
As with the Vector256 cleanup, I audited the doc comments at the same time and ensured they were consistent and correct.