Application binary interface(应用二进制接口)

最新推荐文章于 2023-03-31 14:34:48 发布

simtwo

最新推荐文章于 2023-03-31 14:34:48 发布

阅读量2.8k

点赞数

文章标签： application interface system assembly object construction

本文介绍了应用程序二进制接口(ABI)的概念，包括其在软件与操作系统交互中的作用，如数据类型、调用约定等细节，并重点阐述了嵌入式应用二进制接口(EABI)的特点，例如允许使用特权指令、不强制动态链接以及更紧凑的堆栈帧组织。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

In computer software, an application binary interface ABI ) describes the low-level interface between an application (or any type of) program and the operating system or another application.

Description

ABIs cover details such as data type, size, and alignment; the calling convention, which controls how functions ' arguments are passed and return values retrieved; the system call numbers and how an application should make system calls to the operating system; and in the case of a complete operating system ABI, the binary format of object files, program libraries and so on. A complete ABI, such as the Intel Binary Compatibility Standard (iBCS),^[1] allows a program from one operating system supporting that ABI to run without modifications on any other such system, provided that necessary shared libraries are present, and similar prerequisites are fulfilled.

Other ABIs standardize details such as the C++ name mangling,^[2] exception propagation,^[3] and calling convention between compilers on the same platform, but do not require cross-platform compatibility.

An ABI should not be confused with an application programming interface (API) which defines a library of routines to call, data structures to manipulate, and/or object classes to use in the construction of an application using that particular (often language specific) API.

EABI

An embedded-application binary interface (EABI) specifies standard conventions for file formats, data types, register usage, stack frame organization, and function parameter passing of an embedded software program.

Compilers that support the EABI create object code that is compatible with code generated by other such compilers, thus allowing developers to link libraries generated with one compiler with object code generated with a different compiler. Developers writing their own assembly language code may also use the EABI to interface with assembly generated by a compliant compiler.

The main differences of an EABI with respect to an ABI for general purpose operating systems are that privileged instructions are allowed in application code, dynamic linking is not required (sometimes it is completely disallowed), and a more compact stack frame organization is used to save memory.

Widely used EABIs include PowerPC and ARM.