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
In the x86_64 ABI, if a function has variable arguments then AL (which is part of EAX) is expected to hold the number of vector registers used to hold arguments to that function. In your example: printf(“%d”, 1); has an integer argument so there’s no need for a vector register, hence AL is set to … 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
Here’s the complete table of registers and their use from the documentation [PDF Link]: r12, r13, r14, r15, rbx, rsp, rbp are the callee-saved registers – they have a “Yes” in the “Preserved across function calls” column.
It depends on the ABI for the platform you are compiling for. On Linux, there are two ARM ABIs; the old one and the new one. AFAIK, the new one (EABI) is in fact ARM’s AAPCS. The complete EABI definitions currently live here on ARM’s infocenter. From the AAPCS, §5.1.1: r0-r3 are the argument and … Read more
Caller-saved registers (AKA volatile registers, or call-clobbered) are used to hold temporary quantities that need not be preserved across calls. For that reason, it is the caller’s responsibility to push these registers onto the stack or copy them somewhere else if it wants to restore this value after a procedure call. It’s normal to let … Read more
In .NET 4.5 / C# 5, this is simple: public void PopularMethod([CallerMemberName] string caller = null) { // look at caller } The compiler adds the caller’s name automatically; so: void Foo() { PopularMethod(); } will pass in “Foo”.
The System V AMD64 psABI document is maintained as LaTeX sources on GitLab. Similarly the i386 psABI is a separate GitLab repo. (Formerly on github). Those pages have info on where revisions are discussed. The x32 ABI (32-bit pointers in long mode) is part of the x86-64 aka AMD64 ABI doc. See Chapter 10: ILP32 … Read more
This answer covers 32-bit mode. (Windows x64 only uses 2 conventions: the normal one (which is called __fastcall if it has a name at all) and __vectorcall, which is the same except for how SIMD vector args like __m128i are passed). Traditionally, C function calls are made with the caller pushing some parameters onto the … Read more
I just did some real-world testing (compiling DLLs and applications with MSVC++ and MinGW, then mixing them). As it appears, I had better results with the cdecl calling convention. More specifically: the problem with stdcall is that MSVC++ mangles names in the DLL export table, even when using extern “C”. For example foo becomes _foo@4. … Read more