You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
JIT: ARM64 - Generate constructive forms of ExtractVector and Splice #103850
Regarding using a constructive variant. Not sure how to mark explicit op2 and op3 as needing consecutive registers. The current intrinsics with consecutive registers have a tuple in a single op. Here we have two separate args in the API.
I might have to spend some time in figuring out how to make sure that when op2 gets register Zn, force op3 to get Zn+1 given that they are 2 different operands. I think for simplicity, lets add just the destructive version of SPLICE and open an issue to add constructive version post .NET 9.
changed the title [-]JIT: ARM64 - SVE cover destructive forms of ExtractVector and Splice[/-][+]JIT: ARM64 - Generate constructive forms of ExtractVector and Splice[/+]on Jun 24, 2024
Similar to the CreateBreak APIs, we could explicitly support this via an API call. If the result of #117722 is positive, then we should raise an API issue for this too.
Activity
[-]JIT: ARM64 - SVE cover destructive forms of ExtractVector and Splice[/-][+]JIT: ARM64 - Generate constructive forms of ExtractVector and Splice[/+]dotnet-policy-service commentedon Jun 25, 2024
Tagging subscribers to this area: @dotnet/area-system-runtime-intrinsics
See info in area-owners.md if you want to be subscribed.
a74nh commentedon Jul 17, 2025
Similar to the CreateBreak APIs, we could explicitly support this via an API call. If the result of #117722 is positive, then we should raise an API issue for this too.