ARM µVision v5.06编译器链接器用户指南：功能与配置详解

需积分: 10 171 浏览量更新于2024-07-19 收藏 1.04MB PDF 举报

本资源是ARM Compiler for µVision® armlink 用户手册，专为Keil ARM开发环境设计。它提供了针对该链接器的详尽用户指南，涵盖了关键功能、目标映像结构、符号访问方法以及如何使用散列文件。手册适用于ARM Compiler v5.06版本，包括了对C和C++库的支持，以及对浮点运算的优化。该文档详细记录了从v3.1到v5.06的各个版本更新，每次更新都伴随着μVision平台的相应升级，如从RVCT v4.0到v5.06。在ARM Compiler v5.06中，用户可以利用强大的链接工具来构建高效、可移植的嵌入式应用程序。它强调了非保密性质，允许开发者自由实施文档中的信息，但需尊重版权。手册中不仅包含了基础的链接器操作指南，还可能包括链接器选项设置、内存管理策略以及如何处理链接错误和警告。通过阅读这份手册，开发者能够掌握以下核心知识点： 1. 链接器基础：理解链接器的工作原理，包括如何将源代码文件链接成可执行文件，以及链接过程中涉及的目标文件、对象文件和库文件的管理。 2. 目标映像结构：学习如何构建并优化程序的内存布局，包括代码段、数据段、栈和堆的分配，以及常量池和初始化块的组织。 3. 符号访问：了解如何查找和引用函数、变量、全局数据等符号，以及如何使用符号表进行调试和性能分析。 4. 散列文件（Scatter Files）：掌握如何编写和使用散列文件来控制代码和数据的存储位置，实现模块化和空间优化。 5. 版本兼容性与升级：理解不同版本之间的差异，以便在升级编译器或μVision时做出适应性调整。 6. C/C++库支持：了解内置的库函数特性，以及如何使用和扩展这些库以满足项目需求。 7. 浮点处理：对于需要高性能浮点计算的应用，这部分提供了关键信息，如编译选项设置和优化技巧。这份文档对于任何使用ARM Compiler with µVision进行嵌入式系统开发的工程师来说都是宝贵的参考资料，帮助他们提高开发效率，确保产品质量。无论是在编写代码、配置链接过程还是解决链接问题时，都能从中找到答案。

1.1 Mandatory linkage with the C library

If you write an application in C, you must link it with the C library, even if it makes no direct use of C

library functions.

This is because the compiler might implicitly generate calls to C library functions to improve your

application, even though calls to such functions might not exist in your source code.

Even if your application does not have a main() function, meaning that the C library is not initialized,

some C library functions are still legitimately available and the compiler might implicitly generate calls

to these functions.

Related concepts

1.2.1 Summary of the C and C++ runtime libraries on page 1-17.

1.6.4 Using the libraries in a nonsemihosting environment on page 1-35.

Related references

1.7.1 Building an application without the C library on page 1-40.

1 The ARM C and C++ Libraries

1.1 Mandatory linkage with the C library

reserved.

1-16

Non-Confidential

1.2 C and C++ runtime libraries

ARM provides the C standardlib, C microlib, and C++ runtime libraries to support compiled C and C++.

This section contains the following subsections:

• 1.2.1 Summary of the C and C++ runtime libraries on page 1-17.

• 1.2.2 Compliance with the Application Binary Interface (ABI) for the ARM architecture

on page 1-18.

• 1.2.3 Increasing portability of object files to other CLIBABI implementations on page 1-18.

• 1.2.4 ARM C and C++ library directory structure on page 1-18.

• 1.2.5 Selection of ARM C and C++ library variants based on build options on page 1-19.

• 1.2.6 Thumb C libraries on page 1-20.

1.2.1 Summary of the C and C++ runtime libraries

A summary of the C and C++ runtime libraries provided by ARM.

C standardlib

This is a C library consisting of:

• All functions defined by the ISO C99 library standard.

• Target-dependent functions that implement the C library functions in the semihosted

execution environment. You can redefine these functions in your own application.

• Functions called implicitly by the compiler.

• ARM extensions that are not defined by the ISO C library standard, but are included in the

library.

C microlib

This is a C library that can be used as an alternative to C standardlib. It is a micro-library that is

ideally suited for deeply embedded applications that have to fit within small-sized memory. The

C micro-library, microlib, consists of:

• Functions that are highly optimized to achieve the minimum code size.

• Functions that are not compliant with the ISO C library standard.

• Functions that are not compliant with the 1985 IEEE 754 standard for binary floating-point

arithmetic.

C++

This is a C++ library that can be used with C standardlib. It consists of:

• Functions defined by the ISO C++ library standard.

• The Rogue Wave Standard C++ library.

• Additional C++ functions not supported by the Rogue Wave library.

The C++ libraries depend on the C library for target-specific support. There are no target

dependencies in the C++ libraries.

Related concepts

1.1 Mandatory linkage with the C library on page 1-16.

Related references

1.7.1 Building an application without the C library on page 1-40.

Chapter 1 The ARM C and C++ Libraries on page 1-14.

Chapter 2 The ARM C Micro-library on page 2-96.

Related information

ISO C library standard.

IEEE Standard for Floating-Point Arithmetic (IEEE 754), 1985 version.

What is Semihosting?.

Rogue Wave Standard C++ Library Documentation.

1 The ARM C and C++ Libraries

1.2 C and C++ runtime libraries

reserved.

1-17

Non-Confidential

1.2.2 Compliance with the Application Binary Interface (ABI) for the ARM architecture

The ABI for the ARM Architecture is a family of specifications that describes the processor-specific

aspects of the translation of a source program into object files.

Object files produced by any toolchain that conforms to the relevant aspects of the ABI can be linked

together to produce a final executable image or library.

Each document in the specification covers a specific area of compatibility. For example, the C Library

ABI for the ARM

Architecture (CLIBABI) describes the parts of the C library that are expected to be

common to all conforming implementations.

The ABI documents contain several areas that are marked as platform specific. To define a complete

execution environment these platform-specific details have to be provided. This gives rise to a number of

supplemental specifications, for example the ARM GNU/Linux ABI supplement.

The Base Standard ABI for the ARM

Architecture (BSABI) enables you to use ARM and Thumb

objects and libraries from different producers that support the ABI for the ARM Architecture. The ARM

compilation tools fully support the BSABI, including support for Debug With Arbitrary Record Format

(DWARF) 3 debug tables (DWARF Debugging Standard Version 3).

The ARM C and C++ libraries conform to the standards described in the BSABI, the CLIBABI, and the

C++ ABI for the ARM Architecture (CPPABI).

Related tasks

1.2.3 Increasing portability of object files to other CLIBABI implementations on page 1-18.

Related information

Application Binary Interface (ABI) for the ARM Architecture.

DWARF Debugging Standard.

1.2.3 Increasing portability of object files to other CLIBABI implementations

You can request full CLIBABI portability to increase the portability of your object files to other

implementations of the CLIBABI.

Note

This reduces the performance of some library operations.

There are a number of methods you can use to request full CLIBABI portability.

Procedure

• Specify #define _AEABI_PORTABILITY_LEVEL 1 before you #include any library headers, such as

<stdlib.h>.

• Specify -D_AEABI_PORTABILITY_LEVEL=1 on the compiler command line.

Related concepts

1.2.2 Compliance with the Application Binary Interface (ABI) for the ARM architecture on page 1-18.

Related information

Application Binary Interface (ABI) for the ARM Architecture.

-Dname[(parm-list)][=def] compiler option.

1.2.4 ARM C and C++ library directory structure

The libraries are installed in the armlib and cpplib subdirectories within install_directory\lib.

armlib

Contains the variants of the ARM C library, the floating-point arithmetic library (fplib), and the

math library (mathlib).

1 The ARM C and C++ Libraries

1.2 C and C++ runtime libraries

reserved.

1-18

Non-Confidential

cpplib

Contains the variants of the Rogue Wave C++ library (cpp_*) and supporting ARM C++

functions (cpprt_*), referred to collectively as the ARM C++ Libraries.

The accompanying header files for these libraries are installed in:

install_directory\include

The environment variable ARMCC5LIB must be set to point to the lib directory, or if this variable is not

set, ARMLIB.

You must not identify the armlib and cpplib directories separately because this directory structure

might change in future releases. The linker finds them from the location of lib.

Note

• The ARM C libraries are supplied in binary form only.

• The ARM libraries must not be modified. If you want to create a new implementation of a library

function, place the new function in an object file, or your own library, and include it when you link

the application. Your version of the function is used instead of the standard library version.

• Normally, only a few functions in the ISO C library require re-implementation to create a target-

dependent application.

• The source for the Rogue Wave Standard C++ Library is not freely distributable. It can be obtained

from Rogue Wave Software Inc., or through ARM, for an additional license fee.

Related information

Rogue Wave Standard C++ Library Documentation.

1.2.5 Selection of ARM C and C++ library variants based on build options

When you build your application, you must make certain choices such as the target architecture,

instruction set, and byte order. You communicate these choices to the compiler using build options. The

linker then selects appropriate C and C++ library variants compatible with these build options.

Choices that influence the ARM C and C++ library variant include the following:

Target Architecture and instruction set

ARM or Thumb instruction sets.

Byte order

Big-endian or little-endian.

Floating-point support

• Software (SoftVFP).

• Hardware (VFP).

• Software or hardware with half-precision or double-precision extensions.

• No floating-point support.

1 The ARM C and C++ Libraries

1.2 C and C++ runtime libraries

reserved.

1-19

Non-Confidential

Position independence

Different ways to access your data are as follows:

• By absolute address.

• Relative to sb (read/write position-independent).

• Relative to pc (fpic).

Different ways to access your code are as follows:

• By absolute address when appropriate.

• Relative to pc (read-only position independent).

The standard C libraries provide variants to support all of these options.

Position-independent C++ code can only be achieved with --apcs=/fpic.

Note

Position independence is not supported in microlib.

When you link your assembler code, C or C++ code, the linker selects appropriate C and C++ library

variants compatible with the build options you specified. There is a variant of the ISO C library for each

combination of major build options.

Related information

Code compatibility between separately compiled and assembled modules.

--apcs=qualifier...qualifier compiler option.

--arm compiler option.

--bigend compiler option.

--fpu=name compiler option.

--littleend compiler option.

--thumb compiler option.

--fpu=name linker option.

--ropi linker option.

--rwpi linker option.

--arm assembler option.

--bigend assembler option.

--fpu assembler option.

--littleend assembler option.

--thumb assembler option.

1.2.6 Thumb C libraries

The linker automatically links in the Thumb C library if the objects to be linked contain Thumb

instructions.

Objects use Thumb instructions if they have been built for:

• Thumb code, either using the --thumb option or #pragma thumb.

• Interworking, using the --apcs /interwork option on architecture ARMv4T.

• An ARMv6-M architecture target or processor, for example, Cortex

-M1 or Cortex-M0.

• An ARMv7-M architecture target or processor, for example, Cortex-M3.

Despite its name, the Thumb C library might not contain exclusively Thumb code. If ARM instructions

are available, the Thumb library might use them to improve the performance of critical functions such as

memcpy(), memset(), and memclr(). The bulk of the Thumb C library, however, is coded in Thumb for

the best code density.

1 The ARM C and C++ Libraries

1.2 C and C++ runtime libraries

reserved.

1-20

Non-Confidential

剩余217页未读，继续阅读

yugenjushi

粉丝: 0
资源: 6

ARM µVision v5.06编译器链接器用户指南：功能与配置详解

keil arm编译器用户手册

keil for arm手册

keil uvision2使用手册

keil编译器的使用手册

Keil Software编译器用户手册

keil uvision5使用手册

keil arm-mdk开发参考资料

在keil中arm的 Stellaris Peripheral Driver Library 用户帮助手册

Keil v3 使用手册

KEIL中文使用手册

最新资源