Your program (binary) can run on platforms who provide proper ABI. API restricts type definitions, function definitions, macros, sometimes global variables a library should expose. ABI restricts what a "platform" should provide for you program to run on. I like to consider it in 3 levels: processor level - the instruction set, the calling ...

从这个角度看来，ABI 只是 API 的底层实现，所以多数时候我们才不需要去关心这个问题。 那么当人们提到 ABI 的时候，到底在说什么？以我个人的经验来看，当人们提及 ABI 时，一般主要是在说 Binary-compatible 即二进制兼容性。 什么是二进制兼容性呢？

2010年1月31日 · ABI: "This is how to call a function." The ABI is set of rules that compilers and linkers adhere to in order to compile your program so that will work properly. ABIs cover multiple topics: Arguably the biggest and most important part of an ABI is the procedure call standard sometimes known as the "calling convention". Calling conventions ...

2011年11月9日 · ABI is basically how the function / procedures passes information to each other through registers (compiled form), where the return value stored (specify registers). In x86 or x86-x64 it is called ABI (Application binary interface). In ARM architecture, it is knows as EABI (extended application binary interface).

2011年4月17日 · The C and C++ ABI changed in GCC 4.7.0, which means in general you can't link together binaries compiled with this version of the compiler and with versions before GCC 4.7.0. In particular: The option -mms-bitfields is enabled by default, which means the bitfield layout follows the convention of the Microsoft compiler.

2011年1月27日 · ABI is the thing that handles these things for you like compiling, linking, byte ordering and so on. System programmers have had hard luck defining a uniform ABI for same operating systems running on different architectures and that is why every machine architecture has its own and you need to compile your programs in order to confirm to the ...

2022年5月11日 · 说白了 ABI 问题只有在 C++ 和 Rust 这类开发速度受编译速度制约极大的语言上才比较显著。 而哪怕是 Haskell 和 Rust，它们对于调整 ABI 相关参数和依赖关系的处理基本上都是工具链自带自动化的，只有 C++ 还在靠 CMake 之类的外部程序处理，导致这个问题更加显著。

2017年10月21日 · Related: C++ ABI. GCC and Clang (on all architectures) use the C++ ABI originally developed for Itanium. https://itanium-cxx-abi.github.io/cxx-abi/. This is relevant for example for what requirements a C++ struct/class need to be passed in registers (e.g. being an aggregate according to some definition), vs. when a struct/class always needs to ...

C defines no ABI. In fact, it bends over backwards to avoid defining an ABI. Those people, who like me, who have spent most of their programming lives programming in C on 16/32/64 bit architectures with 8 bit bytes, 2's complement arithmetic and flat address spaces, will usually be quite surprised on reading the convoluted language of the current C standard.

For some of the proposals which were brought forward, e.g., the idea of mandating a stack trace for std::exceptions which would break everybody's exception ABI, the ABI breakage is pretty much a killer argument. Although changes which mandate ABI breaking changes are sometimes introduced, the case has to be argued a lot stronger than changes ...