-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Fix incorrect codegen for SVE GatherVector*With*Offsets* #119853
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
Fix incorrect codegen for SVE GatherVector*With*Offsets* #119853
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.
The isLoadingBytes
is a little ugly. Alternative would be to split the switch cases. But, then it'd duplicate the code underneath isLoadingBytes
. So, I'm happy
This is similar enough to #119712 that I feel we need both in .NET11 if possible.
So, LGTM.
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.
@tannergooding could you please take a quick look if your feedback was addressed
Updated compares to use intrinsics only instead of the instructions and intrinsics for better clarity. |
@SwapnilGaikwad could you please file a manual backport to release/10.0 branch with changes from #119712 and this PR combined? |
Hey @EgorBo , not sure how to do that. Would that be a different PR with changes combined? |
Yes. Our backport bot doesn't know how to combine changes from two PRs and since the approval process for backports is not simple for RC2/GA, it's better to file just one PR with both |
I think you can just cherry-pick two commits or just extract them as patches and apply to your release/5.0 branch e.g. https://github.com/dotnet/runtime/pull/119712.patch |
Combined these changes with scatters in #119959. |
Equivalent to #119712 for gathers where offsets are incorrectly treated as indices which is leading to incorrect code being emitted.
Discussed here.
@dotnet/arm64-contrib @a74nh @tannergooding @EgorBo