Revision as of 21:24, 27 April 2025 edit Guy Harris (talk \| contribs) Extended confirmed users 79,938 edits →Description: The call stack layout may be determined by the instruction set to some degree, but it's usually not completely determined by the instruction set. ← Previous edit		Revision as of 21:27, 27 April 2025 edit undo Guy Harris (talk \| contribs) Extended confirmed users 79,938 edits Mention the iBCS in the Description section, along with the SVR4 ABIs. Next edit →
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 a multiple [[programming language\|languages]] or [[compiler]]s. A complete ABI~~, such as the [[Intel Binary Compatibility Standard]] (iBCS),<ref>[http://www.everything2.com/index.pl?node=iBCS Intel Binary Compatibility Standard (iBCS)]</ref>~~ enables a program that supports an ABI 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 26: * How an application should make [[system call]]s to the operating system, and if the ABI specifies direct system calls rather than procedure calls to system call [[Method stub\|stubs]], the system call numbers * In the case of a complete operating system ABI, the binary format of [[object file]]s, program libraries, etc. ABIs 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 ==

Application binary interface: Difference between revisions