Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Support __vectorcall in FunctionHook (.NET 9+) #36

Open
alexrp opened this issue Jul 21, 2022 · 0 comments
Open

Support __vectorcall in FunctionHook (.NET 9+) #36

alexrp opened this issue Jul 21, 2022 · 0 comments
Assignees
@alexrp
Labels
area: hooking Issues related to the function hooking APIs. state: blocked Issues that are blocked on some other issue or work.
Milestone
Future

Comments

@alexrp
Copy link
Member

alexrp commented Jul 21, 2022

ruptura/src/memory/Code/FunctionHook.cs

Line 183 in b2bd417

// TODO: Support vectorcall (X/YMM0 - X/YMM5 for arguments, X/YMM0 - X/YMM3 for results)?

Blocked on .NET runtime support: dotnet/runtime#8300

Calling convention details: https://docs.microsoft.com/en-us/cpp/cpp/vectorcall
@alexrp alexrp added state: blocked Issues that are blocked on some other issue or work. type: feature area: hooking Issues related to the function hooking APIs. labels Jul 21, 2022
@alexrp alexrp added this to the v2.0 milestone Jul 21, 2022
@alexrp alexrp self-assigned this Jul 21, 2022
@alexrp alexrp modified the milestones: v2.0, v3.0 Jul 23, 2022
@alexrp alexrp changed the title Support __vectorcall in FunctionHook (.NET 8+) Support __vectorcall in FunctionHook (.NET 9+) Aug 3, 2023
@alexrp alexrp modified the milestones: v3.0, Future Jan 1, 2024
@alexrp alexrp removed their assignment Jan 27, 2024
@alexrp alexrp self-assigned this Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alexrp alexrp

Labels
area: hooking Issues related to the function hooking APIs. state: blocked Issues that are blocked on some other issue or work.
Milestone
Future
Development

No branches or pull requests
1 participant
@alexrp