I’m not sure this is the best, but: function A{ Param([scriptblock]$FunctionToCall) Write-Host “I’m calling $($FunctionToCall.Invoke(4))” } function B($x){ Write-Output “Function B with $x” } Function C{ Param($x) Write-Output “Function C with $x” } PS C:\WINDOWS\system32> A -FunctionToCall $function:B I’m calling Function B with 4 PS C:\WINDOWS\system32> A -FunctionToCall $function:C I’m calling Function C with 4 … Read more
RCX, along with R11, is used by the syscall instruction, being immediately destroyed by it. Thus these registers are not only not saved after syscall, but they can’t even be used for parameter passing. Thus R10 was chosen to replace unusable RCX to pass fourth parameter. See also this answer for a bit more information … Read more
Your quote is from the “calling convention” part of the documentation. At the very least, you do not have to worry about this if you do not call other functions from your assembly code. If you do, then you must respect, among other things, “red zone” and stack alignment considerations, that the recommendation you quote … Read more
Cast it: WinApiFunc(static_cast<void(__stdcall *)()>(func)); Or store it into a local variable first: void (__stdcall *funcp)() = func; WinApiFunc(funcp);
If you remember C memcpy‘s arg order, and how rep movsb works, that’s most of the way to remembering x86-64 System V. The design makes memcpy(dst, src, size) cheap to implement with rep movsb, except leaving RCX unused in more functions because it’s needed for variable-count shifts more often than anything needs RDX. Then R8 … Read more
The purpose of that area is revealed by the following code int main(int argc, char** argv) { if (rand() == 42) return 1; printf(“Helo World!\n”); return 0; } At the start it does movl $0, -4(%rbp) then the early return looks as follows callq rand cmpl $42, %eax jne .LBB0_2 movl $1, -4(%rbp) jmp .LBB0_3 … Read more
In my experience, there is no standard way how C returns a structure. To be able to pass a struct, the compiler usually (invisibly to the user) passes a pointer to the struct, to which the function can copy the contents. How this pointer is passed (first or last on stack) is implementation dependent. Some … Read more
Not all registers make good candidates for preserving: no (e)ax — Implicitly used in some instructions; Return value no (e)dx — edx:eax is implicity used in cdq, div, mul and in return values (e)bx — generic register, usable in 16-bit addressing modes (base) (e)cx — shift-counts, used in loop, rep (e)si — movs operations, usable … Read more
As Graznarak’s answer correctly points out, the order in which arguments are evaluated is distinct from the order in which arguments are passed. An ABI typically applies only to the order in which arguments are passed, for example which registers are used and/or the order in which argument values are pushed onto the stack. What … Read more
This debug error means that the stack pointer register is not returned to its original value after the function call, i.e. that the number of pushes before the function call were not followed by the equal number of pops after the call. There are 2 reasons for this that I know (both with dynamically loaded … Read more