| |||
| Home > The ARM C and C++ libraries | |||
The following topics describe the ARM C and C++ libraries:
Library heap usage requirements of the ARM C and C++ libraries
Compliance with the Application Binary Interface (ABI) for the ARM architecture
Increasing portability of object files to other CLIBABI implementations
Selection of ARM C and C++ library variants based on build options
Use of the __user_libspace static data area by the C libraries
C library functions to access subsections of the __user_libspace static data area
Re-implementation of legacy function __user_libspace() in the C library
The floating-point status word in a multithreaded environment
Using the C and C++ libraries with an application in a semihosting environment
Using $Sub$$ to mix semihosted and nonsemihosted I/O functionality
C library API definitions for targeting a different environment
Creating an application as bare machine C without the C library
Integer and floating-point compiler functions and building an application without the C library
Customized C library startup code and access to C library functions
Initialization of the execution environment and execution of the application
Assembler macros that tailor locale functions in the C library
Link time selection of the locale subsystem in the C library
Modification of C library functions for error signaling, error handling, and program exit
Modification of memory management functions in the C library
Avoiding the heap and heap-using library functions supplied by ARM
Target dependencies on low-level functions in the C and C++ libraries
Redefining low-level library functions to enable direct use of high-level library functions
How the ARM C library fulfills ISO C specification requirements
Persistence of C and C++ library names across releases of the ARM compilation tools
Managing projects that have explicit C or C++ library names in makefiles
Using macro__ARM_WCHAR_NO_IO to disable FILE declaration and wide I/O function prototypes.