-
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
Finish treating the Unsafe APIs as JIT intrinsics #69220
Comments
Tagging subscribers to this area: @JulieLeeMSFT Issue DetailsA majority of the APIs on The remaining unhandled ones are:
We should ensure these are likewise handled as JIT intrinsics to further improve code quality and JIT throughput where possible
|
Once this is done, we can switch these intrinsics onto the same plan as hardware intrinsics, implement them using self-recursive pattern in C# and delete the IL intrinsic expansion in VM/AOT ( |
Cc @dotnet/jit-contrib. |
Is this easy for JIT-newbies? |
Intrinsifies Copy, Read/ReadUnaligned, Write/WriteUnaligned. Contributes to dotnet#69220
|
A majority of the APIs on
System.Runtime.CompilerServices.Unsafe
were converted to be JIT intrinsics as part of #68739 and later more as part of #85562The remaining unhandled ones are:
NI_SRCS_UNSAFE_CopyBlock
NI_SRCS_UNSAFE_CopyBlockUnaligned
NI_SRCS_UNSAFE_InitBlock
NI_SRCS_UNSAFE_InitBlockUnaligned
NI_SRCS_UNSAFE_Unbox
We should ensure these are likewise handled as JIT intrinsics to further improve code quality and JIT throughput where possible
category:implementation
theme:intrinsics
skill-level:intermediate
cost:small
impact:small
The text was updated successfully, but these errors were encountered: