Application binary interface

An application binary interface (ABI) specifies binary-level conventions that let compiled programs interact with operating systems, libraries, and processors, including rules for calls, data layout, and executable files.

Calling convention: Rules governing how functions pass arguments, return values, and preserve processor state. It defines the register and stack behavior at function boundaries.
Object file: A file containing compiled code and data, often with symbols and relocation information. Object files are the units whose symbols and layouts must fit an ABI.
System V AMD64 ABI: The ABI used by many Unix-like systems on x86-64 processors. Its register assignments and stack rules govern common Linux and BSD binaries.
Application programming interface: A source-level specification of functions, types, and services available to software developers. An API describes permitted source-level use; an ABI fixes binary-level interaction rules.
Shared library: A library loaded by multiple programs at runtime rather than copied into each executable. Its functions and data must retain compatible binary conventions for existing programs to keep working.
Application binary interface register: A processor register assigned a defined role by an ABI, such as carrying an argument or return value. ABIs specify which registers carry values across calls.
Linker: A program that combines object files and libraries into an executable or shared library. Linkers enforce symbol and relocation conventions established by an ABI.
Microsoft x64 calling convention: The standard 64-bit calling convention used by Microsoft Windows on x86-64. Its argument registers and shadow space differ from the System V AMD64 rules.
Instruction set architecture: The specification of a processor's instructions, registers, and programmer-visible behavior. An ISA defines processor behavior, while an ABI adds conventions for compiled software.
Application binary interface stability: The preservation of binary conventions across software releases so existing compiled clients remain usable. Stable conventions let applications survive library updates without recompilation.

Linked from 22 pages