-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Ensure that AdvSimd.Insert doesn't zero out the upper bits #106981
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
Conversation
| assert(intrin.op2->isContainedIntOrIImmed()); | ||
| assert(intrin.op2->AsIntCon()->gtIconVal == 0); | ||
| // fmov (scalar) zeros the upper bits and is not safe to use | ||
| assert(!intrin.op3->isContainedFltOrDblImmed()); |
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.
GitHub is displaying the diff a bit weirdly. This is just removing the if and fixing the indentation of the else block now that its the only code path.
e744d96 to
7e49c28
Compare
|
CC. @dotnet/jit-contrib for review, this resolves #106079 and needs backport to .NET 9. It should also be considered for backport to .NET 8 |
|
/backport to release/9.0 |
|
Started backporting to release/9.0: https://github.com/dotnet/runtime/actions/runs/10599434161 |
|
/backport to release/8.0-staging |
|
Started backporting to release/8.0-staging: https://github.com/dotnet/runtime/actions/runs/10599481780 |
This resolves #106079
This bug was introduced in the first Arm64 support was added back in .NET 5: #35030