x86 calling conventions

This article describes the <a href="/facts/Calling_convention/FtzN2BKj">calling conventions</a> used when programming <a href="/facts/X86/Kypq5fgu">x86</a> architecture <a href="/facts/Microprocessor/Fx9CaQht">microprocessors</a>.
Calling conventions describe the interface of called code:

<ul><li>The order in which atomic (scalar) parameters, or individual parts of a complex parameter, are allocated</li>
<li>How parameters are passed (pushed on the stack, placed in registers, or a mix of both)</li>
<li>Which registers the called function must preserve for the caller (also known as: callee-saved registers or non-volatile registers)</li>
<li>How the task of preparing the stack for, and restoring after, a function call is divided between the caller and the callee</li></ul>
This is intimately related with the assignment of sizes and formats to programming-language types.
Another closely related topic is <a href="/facts/Name_mangling/br0AH0zP">name mangling</a>, which determines how symbol names in the code are mapped to symbol names used by the linker. Calling conventions, type representations, and name mangling are all part of what is known as an <a href="/facts/Application_binary_interface/wc6pmKKb">application binary interface</a> (ABI).
There are subtle differences in how various compilers implement these conventions, so it is often difficult to interface code which is compiled by different compilers. On the other hand, conventions which are used as an API standard (such as stdcall) are very uniformly implemented.

x86 calling conventions open-in-new

x86 calling conventions