We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
List of various items related to vector length and Vector<T> handling in general for SVE:
Vector<T>
Vector256
getVectorTByteLength()
Sve
Vector<T> a+b
Sve.Add(a,b)
DOTNET_MaxVectorTBitWidth
The text was updated successfully, but these errors were encountered:
@dotnet/arm64-contrib
Sorry, something went wrong.
Tagging subscribers to this area: @dotnet/area-system-runtime-intrinsics See info in area-owners.md if you want to be subscribed.
@kunalspathak Is this list of items still in scope for 9.0.0, or should we move this into the 10.0.0 milestone?
No branches or pull requests
List of various items related to vector length and
Vector<T>
handling in general for SVE:Vector256
for SVE, when applicable. Details: https://github.com/dotnet/runtime/pull/101295/files#r1572607279getVectorTByteLength()
to give correct current vector length instead of hard-coded to return 128.Vector<T>
methods map toSve
intrinsics, whenever possible. SoVector<T> a+b
should map toSve.Add(a,b)
, etc.DOTNET_MaxVectorTBitWidth
for Sve. WIP: Add option to change SVE vector length for current and children processes #101295The text was updated successfully, but these errors were encountered: