-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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 CreateScalar to be intrinsic for Vector64/128/256 #77798
Conversation
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue DetailsThis ensures that vector constant nodes can be created and improves the codegen for inserts involving float. Handling for
|
CC. @dotnet/jit-contrib |
/azp run runtime-coreclr jitstress-isas-x86, runtime-coreclr jitstress-isas-arm, runtime-coreclr outerloop |
Azure Pipelines successfully started running 3 pipeline(s). |
|
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.
LGTM, assuming the test failures aren't related modulo the GT_CAST question.
Also, I assume it doesn't break mono since it converts a helper method into a "recursive" intrinsic
CI failures are currently dotnet/arcade#11554. However, there is no way to tell if its masking actual issues or not so I'll hold off on merging. |
This ensures that vector constant nodes can be created and improves the codegen for inserts involving float.
Handling for
Create(Vector128<T> lower, Vector128<T> upper)
also needs to be done, but will be a separate PR.