ICallingConvention

The flag indicates that the calling convention uses an implicit pointer as first parameter when the function prototype specifies that a "complex" data type (some fundamental types, all aggregate types) is to be returned.

The first argument must be a pointer to the object. Typically, this flag is used by MSVC's __thiscall convention. Generally, it enforces the fact that the first parameter of a prototype must be a single-slot element (and more specifically, a pointer-type element.

The flag indicates that all float arguments must go on the stack, regardless of registers declared to be holding storage items, if any. (I.e., input registers will be used for integral types, at least, not FP types.)

This flag indicates that the return-address value is located after the input argument on the stack.

Example:

 | ...
 | return addr
 | argN
 | (...)
 v arg1
 +-----------   <---- SP at routine entry
 

The flag indicates that output values are located on the pre-allocated stack slots located after the input values (whose count may not be known).

Example, when calling a function (int,int)->(int)

 v ...
 +-----------  (SP1)
 | ? retval1 (slot)
 | arg2
 | arg1
 v return addr
 +-----------   <---- SP at routine entry
 

IMPORTANT: this flag requires that all calling convention elements (inputs, outputs, return address) be located on the stack.

This flag indicates that the return values are to be pushed on the stack after return. If it is combined with FLAG_STACK_CLEANED_BY_CALLEE, the input arguments are assumed to be cleaned before pushing the output.

Example, when calling a function (int,int)->(int):

 v ...
 +-----------  (SP1)
 | retaddr
 | arg2
 v arg1
 +-----------   <---- SP at routine entry
 

 v ...
 +-----------  (SP1)
 | retval
 +-----------   <---- SP at return PC
 

The indices in the lists of registers used to pass integral arguments and floating-point arguments grow together, in a parallel fashion.

Example when calling a method: void f(int a, float b, int c, float d)

With the standard x86_64 Windows calling convention, arguments...

 - a would go in rcx
 - b would go in xmm1 (FP reg at index 1)
 - c would go in r8 (GP reg at index 2)
 - d would go in xmm3 (GP reg at index 3)
 

Here is an example of what happens when the general and FP register stacks used for arguments passing grow separately, as is the case for Linux x64, with the standard amd64 System V convention:

 - a would go in rdi
 - b would go in xmm0 (NOT xmm1) 
 - c would go in rsi (NOT rdx) 
 - d would go in xmm1 (NOT xmm3)
 

The flag indicates that the stack is cleaned by the callee (which is not the norm; if the flag is not set, it should be assumed the stack is cleaned by the caller).

Note that a return-address value located on the stack is always pop'ed, regardless of the presence of this flag.

Determine the slotcount alignment requirement of a non-composite type.

Get a list of alternate names for this calling convention.

Create a storage-location generator for the inputs provided to a routine using this calling convention.

Get the list of compiler types this calling convention may work with.

Get an internally-generated identifier for this calling convention object. Two calling conventions using:
- the same names
- same flags
- same processor targets
- same subsystem targets
- same compiler targets
will have the same UUID.

Determine the storage item assigned to a method invocation parameter.

Return the number of slots that are reserved for parameters. Note that this is just a hint on how many parameters are used.

Get the common name of this calling convention.

Retrieve all names for this calling convention (principal and alternates).

Determine the storage item assigned to a method return value.

Determine the storage item assigned to a method return value.

Return the number of slots that are reserved for return values. Note that this is just a hint on how many return values are defined.

Get the list of processor types this calling convention may work with.

Get the list of registers that are spoiled by a callee, in the strictest sense, i.e. their value may or may not be modified, but it is meaningless and should not be interpreted by the caller upon return. That set would NOT include return registers.

Alignment specifications for non-composite types.

Get the list of all registers that may be modified and/or spoiled by a callee, in the most general sense. That set would include any type of return registers.

Get the list of subsystem types this calling convention may work with.

Determine whether routine parameters pushed on stack before a routine call are cleaned by the callee.

Determine whether routine parameters pushed on stack before a routine call are cleaned by the caller.