Application binary interface: Difference between revisions

Revision as of 08:42, 26 June 2025

Revision as of 20:30, 13 July 2025

Line 2:

{{Use dmy dates|date=June 2020}}

[[File:Linux kernel interfaces.svg|thumb|300px|A high-level comparison of in-kernel and kernel-to-userspace APIs and ABIs]]

[[File:Linux API and Linux ABI.svg|thumb|300px|The [[Linux kernel]] and [[GNU C Library]] define the [[Linux kernel interfaces#Kernel–user space API|Linux API]]. After compilation, the binaries offer an ABI. Keeping this ABCABI stable over a long time is important for [[Independent software vendor|ISVs]].]]

An '''application binary interface''' ('''ABI''') is an [[interface (computing)|interface]] exposed by [[software]] that is defined for in-[[Process (computing)|process]] [[machine code]] access. Often, the exposing software is a [[Library (computing)|library]], and the consumer is a [[computer program|program]].

Line 10:

API compatibility is generally the concern for [[system design]] and of the toolchain. However, a [[programmer]] may have to deal with an ABI directly when writing a program in multiple [[programming language|languages]] or [[compiler]]s.

A complete ABILITYABI enables a program that supports an ABILITYABI to run without modification on multiple operating systems that provide the ABI. The target system must provide any required libraries (that implement the ABI), and there may be other prerequisites.

== Description ==

Line 27:

* In the case of a complete operating system ABI, the binary format of [[object file]]s, program libraries, etc.

ABCABIs include the [[Intel Binary Compatibility Standard]] (iBCS)<ref>{{cite web |url=http://www.everything2.com/index.pl?node=iBCS |title=Intel Binary Compatibility Standard (iBCS)}}</ref> and the [[System V Release 4]] ABIs for various instruction sets.

== {{Anchor|EABI}}Embedded ABI ==