blocks|key|284152|text|在一定程度上，您对ABI的定义是正确的。典型的例子是Linux+(和其他UNIXes)中的syscall接口。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|284153|它们是代码请求操作系统执行某些任务的标准方式。|284154|因此，它们是由编写操作系统的人决定的，或者在后来添加syscalls的情况下，由添加它们的人决定(在操作系统允许的情况下)。例如，x86上的Linux+syscall接口声明您将syscall编号加载到eax中，并将其他参数放在ebx、ecx等中，这取决于您正在创建的syscall+(eax)。|284155|通常，做接口工作的不是编译器或链接器，而是为您正在使用的语言提供的库。|284156|回到Linux，GNU库包含用于fopen的代码(例如)，它最终调用相关的syscall来执行较低级别的任务(syscall+number+5，open)。可以在this+PDF+file中找到syscalls的列表。|284157|entityMap|0|LINK|mutability|MUTABLE|url|http://www.google.com.au/url?sa=t&source=web&cd=3&ved=0CCQQFjAC&url=http%253A%252F%252Fwww.digilife.be%252Fquickreferences%252FQRC%252FLINUX%252520System%252520Call%252520Quick%252520Reference.pdf&ei=hEVBTc-ZOcLMcL---IEO&usg=AFQjCNFc1oZljrSMCuBef1GQaeaeg42SBA^0|19|7|0|0|Q|8|24|7|2H|7|2T|3|36|3|3A|3|3Q|7|3Z|3|0|0|G|5|11|7|20|4|2P|8|29|D|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@$9|W|A|X|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Y|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|Z|8|@$9|10|A|11|B|C]|$9|12|A|13|B|C]|$9|14|A|15|B|C]|$9|16|A|17|B|C]|$9|18|A|19|B|C]|$9|1A|A|1B|B|C]|$9|1C|A|1D|B|C]|$9|1E|A|1F|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|1G|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|1H|8|@$9|1I|A|1J|B|C]|$9|1K|A|1L|B|C]|$9|1M|A|1N|B|C]|$9|1O|A|1P|B|C]]|D|@$9|1Q|A|1R|1|1S]]|E|$]]|$1|N|3|-4|5|6|7|1T|8|@]|D|@]|E|$]]]|O|$P|$5|Q|R|S|E|$T|U]]]]

You're correct about the definition of an ABI, up to a point. The classic example is the <code>syscall</code> interface in Linux (and other UNIXes).

They are a standard way for code to request the operating system to carry out certain duties.

As such, they're decided by the people that wrote the OS or, in the case where the <code>syscalls</code> have been added later, by whoever added them (in cases where the OS allows this). For example, the Linux <code>syscall</code> interface on x86 states that you load the <code>syscall</code> number into <code>eax</code>, with other parameters placed in <code>ebx</code>, <code>ecx</code> and so on, depending on the <code>syscall</code> you're making (<code>eax</code>).

Typically, it's not the compiler or linker which do the work of interfacing, rather it's the libraries provided for the language you're using.

Returning to Linux, the GNU C libraries contain code for <code>fopen</code> (for example) which eventually call the relevant <code>syscall</code> to perform the lower level tasks (syscall number 5, <code>open</code>). A list of the <code>syscalls</code> can be found in <a href="http://www.google.com.au/url?sa=t&amp;source=web&amp;cd=3&amp;ved=0CCQQFjAC&amp;url=http%3A%2F%2Fwww.digilife.be%2Fquickreferences%2FQRC%2FLINUX%2520System%2520Call%2520Quick%2520Reference.pdf&amp;ei=hEVBTc-ZOcLMcL---IEO&amp;usg=AFQjCNFc1oZljrSMCuBef1GQaeaeg42SBA" rel="noreferrer">this PDF file</a>.

blocks|key|282661|text|规范比约定更合适，因为约定是广泛接受的实践的松散术语，而规范是明确定义的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|282662|你是正确的。该规范由标准化组织制定。看看Windows支持的POSIX规范和编译/构建工具链，如gcc假设操作系统遵守它，甚至Linux内核也部分(几乎完全)遵守它。|282663|在ABIs之前？即使在今天，随着机顶盒和其他具有嵌入式系统的设备的新芯片的出现，固件仍然是手工制作的。|282664|文档是数据表中的数字逻辑内容，对于要用汇编语言编程的芯片和高级语言，交叉编译工具链文档给出了ABI中应该包含的假设。|282665|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Specification is more suitable term than convention, as convention is loose term for widely accepted practice whereas specification is well-defined.

You are right. The specification is made by standardization body. Take a look at POSIX specification which is supported by Windows and compiler/build tool-chains such as gcc assume OS's to adhere by it, and even Linux kernel partially (almost exactly) adheres to it.

Before ABIs? Even today, firmware is hand-crafted as new chips come along for set-top boxes and such other devices having embedded systems.

The documentation is digital logic content in the data-sheet for the chips to be programmed by assembly language and for higher-level language, the cross-compiler tool-chain documentation gives away the assumptions that should be part of ABI.

blocks|key|2994944|text|ABI的概念大概是为了支持您的程序在其他操作系统和机器架构上的二进制兼容性。因此，假设您在x86架构上运行的某个操作系统发行版上编写了一个程序。现在，对于程序员来说，最重要的事情是你在你的机器上编写的程序应该能够在运行在相同或不同架构上的任何其他机器上完全相同地运行，为了便于讨论，让我们假设另一台机器运行在i386架构上，这就是ABI或应用程序二进制接口概念的用武之地。由于每个机器体系结构定义了操作系统内核与外部世界(即用户空间程序)对话的方式，因此每个体系结构定义了一组不同的系统调用、机器寄存器、如何使用这些寄存器、内核如何处理软件中断等。ABI是为你处理这些事情的东西，比如编译、链接、字节排序等等。系统程序员很难为运行在不同体系结构上的相同操作系统定义一个统一的ABI，这就是为什么每个机器体系结构都有自己的体系结构，你需要编译你的程序以确认这些机器具有的格式。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2994945|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Well, the concept of ABI was presumably conceived to support the binary compatibility of your program on other operating systems and machine architectures. So, lets suppose that you wrote a program on some operating system distribution running on x86 architecture. Now, for a programmer the most important thing is that this program that you wrote on your machine should be able to run exactly the same on any other machine running on same or different architecture lets say for the sake of discussion that the other machine is running on i386 architecture and this is where the concept of ABI or Application Binary Interfaces comes in. As every machine architecture defines its own way in which the operating system kernal talks to the outside world i.e user-space programs, hence every architecture defines a different set of system calls, machine registers, how those registers are used, how are software interrupts handled by the kernal and so on. 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 format those machines have.

This is what wikipedia says:

<blockquote>
 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.
 
 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), 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.
</blockquote>

I guess that an ABI is a convention or standard, and compilers/linkers use this convention to produce object codes. Is that right? If so who made these conventions(companies or some organization)? What was it like when there was no ABIs? Is there documents about these ABIs that we can refer to?

What is ABI(Application Binary Interface)?

嵌入式系统

编译器

Windows

Linux

维基百科是这样说的：在计算机软件中，应用程序二进制接口(ABI)描述应用程序(或任何类型的)程序与操作系统或其他应用程序之间的低级接口。ABI介绍了一些细节，比如数据类型、大小和对齐方式；调用约定，它控制如何传递函数的参数以及如何检索返回值；系统调用号以及应用程序应该如何对操作系统进行系统调用；对于完整的操作系统ABI...

问什么是ABI(应用程序二进制接口)？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问什么是ABI(应用程序二进制接口)？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问什么是ABI(应用程序二进制接口)？
EN