calling convention

Architectures almost always have more than one possible calling convention.

A single calling convention is used for all procedural languages.

This article describes the calling conventions used on the x86 architecture.

These languages, at the time, used different calling conventions.

The register calling convention may be selected by command line switch.

Also, the number of incompatible calling conventions has been reduced, but unfortunately there are still two in common use.

Key language constructs like calling conventions could have been eligible for patent protection.

This is a list of x86 calling conventions.

With some calling conventions, however, it is the caller's responsibility to remove the arguments from the stack after the return.

It is known as the Pascal calling convention.

Depending on calling conventions and memory layout, this may result in stack smashing.

The x86 architecture features many different calling conventions.

This makes threaded code the most compact calling convention.

For example, the call by reference calling convention can be implemented with either explicit or implicit use of references.

The calling conventions adopted for the platform were those defined by the manufacturer's software implementation.

This calling convention is used for calling C++ non-static member functions.

Variadic functions fall back to the Watcom stack based calling convention.

This makes naive implementations slower than calling conventions that keep more values in registers.

Such functions can be compiled to use a more efficient calling convention without changing the meaning of the enclosing program.

Depending on the compiler and architecture, it also may be the case that calling conventions differ between the two languages.

The following table shows calling conventions of functions:

When done per function/procedure the calling convention may require insertion of save/restore around each call-site.

This allows subroutines written in those languages to call, or be called by, existing Windows libraries using a calling convention different from their default.

Calling conventions describe the interface of called code:

It provides access to host or native files, can be used for functional programming, and can call functions that use the C calling convention.