TIS ELF规范：Linux可执行与链接格式详解

4星 · 超过85%的资源需积分: 40 69 浏览量更新于2024-07-25 收藏 337KB PDF 举报

"Linux的Tool Interface Standard (TIS)和Executable and Linking Format (ELF)英文原版技术说明书" Tool Interface Standard (TIS) Executable and Linking Format (ELF)是Linux系统中的一种二进制文件格式，用于编译器、链接器和其他工具之间的接口。这份规范详细定义了如何在操作系统中创建、执行和链接可执行文件以及库文件。TIS和ELF的结合旨在提供一个标准，使得不同工具之间能够协同工作，确保软件的兼容性和一致性。 ELF是一种通用的文件格式，广泛应用于多种类UNIX系统，包括Linux。它支持动态和静态链接，包含程序头和节区表等关键组件，这些组件提供了关于程序结构和依赖性的信息。ELF文件可以是可执行文件、共享库（动态链接库）或可重定位对象文件，它们都遵循相同的内部结构。以下是ELF文件格式的一些关键知识点： 1. **程序头**：程序头记录了如何加载和执行程序的信息，如内存映射、入口点地址等。 2. **节区（Section）**：节区是ELF文件的基本组织单元，包含了代码、数据、符号信息等。 3. **符号表（Symbol Table）**：符号表存储了程序中定义和引用的函数、变量和其他实体的信息。 4. **重定位表（Relocation Table）**：用于链接器调整程序中的地址，以适应不同的运行时环境。 5. **动态段（Dynamic Section）**：包含有关动态链接所需的信息，如共享库的引用、版本信息等。 6. **头文件（Header）**：每个ELF文件都以一个固定的头开始，包含关于文件类型、架构、大小等基本信息。 7. **目标架构**：ELF支持多种处理器架构，如x86、x86_64、ARM等，每种架构有其特定的字节序和机器指令集。 8. **版本控制**：ELF格式允许版本信息的嵌入，以支持不同版本的库和工具之间的兼容性。 9. **调试信息**：如 DWARF 调试信息，帮助调试器解析源代码与二进制代码之间的关系。 TIS则是规定了工具之间的接口标准，确保所有工具都能理解并正确处理ELF文件。例如，编译器必须生成符合TIS-ELF规范的输出，链接器则需要理解并处理这些输出，而加载器则负责在运行时正确地加载和执行ELF文件。虽然TIS委员会对这份规范的使用提供了非独占、无版税的许可，但明确声明不提供任何保证，也不承担因使用该规范可能引发的任何责任，包括但不限于间接损害赔偿。此外，他们保留随时修改此规范的权利，而无需提前通知。最后，提到了IBM和Intel的商标，表明TIS-ELF规范也可能考虑了与其他平台，如IBM的OS/2和Intel的x86架构的兼容性。这些处理器和操作系统间的兼容性是ELF作为跨平台二进制格式的一个重要特性。

Introduction

1-2 Book I: ELF (Executable and Linking Format)

An ELF header resides at the beginning and holds a "road map'' describing the file's

organization. Sections hold the bulk of object file information for the linking view: instructions,

data, symbol table, relocation information, and so on. Descriptions of special sections appear

later in this section. Chapter 2 also describes segments and the program execution view of the

file.

A program header table, if present, tells the system how to create a process image. Files used

to build a process image (execute a program) must have a program header table; relocatable

files do not need one. A section header table contains information describing the file's sections.

Every section has an entry in the table; each entry gives information such as the section name,

the section size, and so on. Files used during linking must have a section header table; other

object files may or may not have one.

NOTE. Although the figure shows the program header table immediately after the

ELF header, and the section header table following the sections, actual

files may differ. Moreover, sections and segments have no specified

order. Only the ELF header has a fixed position in the file.

Data Representation

As described here, the object file format supports various processors with 8-bit bytes and 32-bit

architectures. Nevertheless, it is intended to be extensible to larger (or smaller) architectures.

Object files therefore represent some control data with a machine-independent format, making

it possible to identify object files and interpret their contents in a common way. Remaining

data in an object file use the encoding of the target processor, regardless of the machine on

which the file was created.

All data structures that the object file format defines follow the "natural'' size and alignment

guidelines for the relevant class. If necessary, data structures contain explicit padding to ensure

4-byte alignment for 4-byte objects, to force structure sizes to a multiple of 4, and so on. Data

also have suitable alignment from the beginning of the file. Thus, for example, a structure

containing an

Elf32_Addr member will be aligned on a 4-byte boundary within the file.

For portability reasons, ELF uses no bit fields.

Figure 1-2. 32-Bit Data Types

Name Size Alignment Purpose

Elf32_Addr 4 4 Unsigned program address

Elf32_Half 2 2 Unsigned medium integer

Elf32_Off 4 4 Unsigned file offset

Elf32_Sword 4 4 Signed large integer

Elf32_Word 4 4 Unsigned large integer

unsigned char 1 1 Unsigned small integer

Introduction

OBJECT FILES 1-3

Character Representations

This section describes the default ELF character representation and defines the standard

character set used for external files that should be portable among systems. Several external

file formats represent control information with characters. These single-byte characters use the

7-bit ASCII character set. In other words, when the ELF interface document mentions character

constants, such as, ‘/’ or ‘\n’ their numerical values should follow the 7-bit ASCII guidelines.

For the previous character constants, the single-byte values would be 47 and 10, respectively.

Character values outside the range of 0 to 127 may occupy one or more bytes, according to the

character encoding. Applications can control their own character sets, using different character

set extensions for different languages as appropriate. Although TIS-conformance does not

restrict the character sets, they generally should follow some simple guidelines.

• Character values between 0 and 127 should correspond to the 7-bit ASCII code. That is,

character sets with encodings above 127 should include the 7-bit ASCII code as a subset.

• Multibyte character encodings with values above 127 should contain only bytes with values

outside the range of 0 to 127. That is, a character set that uses more than one byte per character

should not "embed'' a byte resembling a 7-bit ASCII character within a multibyte, non-ASCII

character.

• Multibyte characters should be self-identifying. That allows, for example, any multibyte

character to be inserted between any pair of multibyte characters, without changing the

characters' interpretations.

These cautions are particularly relevant for multilingual applications.

NOTE. There are naming conventions for ELF constants that have processor

ranges specified. Names such as DT_, PT_, for processor specific

extensions, incorporate the name of the processor: DT_M32_SPECIAL,

for example. However, pre-existing processor extensions not using this

convention will be supported.

Pre-existing Extensions

DT_JMP_REL

剩余105页未读，继续阅读

stone04192007

粉丝: 0
资源: 3

TIS ELF规范：Linux可执行与链接格式详解

ELF中文版手册.pdf

ELF文件格式规范1.2

ELF手册-英文原版.pdf

TIS.Imaging 怎么安装

射频 TIS/TIP指标

SDGSAT-1TIS

具有激活的tis模块可以防止下载到设备

微波暗室测试天线trp tis原理

NB-IoT TIS TRP取值

within_tis = unlist(lapply(within_tis,function(x) mean(x[upper.tri(x)])))

最新资源