ARM Compiler toolchain Using the Linker - ARM Information Center

9.4 Specific restrictions for using ld scripts with armlink
9.4.1 See also
The following restrictions apply when using ld scripts with armlink:
GNU ld script support in armlink
PHDRS This command is not implemented. When using an ld script the linker always
generates program headers automatically.
MEMORY This command is not implemented. The linker assumes that it has a uniform
memory space from 0 to 0XFFFFFFFF.
OVERLAY This command is not implemented. Overlays are not permitted.
Other commands and built-in functions
The following commands and built-in functions are not supported:
• ASSERT
• FORCE_COMMON_ALLOCATION
• INHIBIT_COMMON_ALLOCATION
• INSERT AFTER
• INSERT BEFORE
• LENGTH
• NOCROSSREFS
• ORIGIN
• REGION_ALIAS
• TARGET
armlink linker-defined symbols
Each output section is defined internally as an execution region. The existing
armlink execution region symbols can be used, for example:
.text : { *(.text) }
The output section .text is represented by an execution region called .text. You
can use the symbol Image$$.text$$Base as if the execution region had been
defined by a scatter file.
Other restrictions
Other restrictions are:
• __AT sections are not supported when using ld scripts
• RW compression is not supported when using ld scripts.
Concepts
• About GNU ld script support and restrictions on page 9-2
• Important ld script commands that are implemented in armlink on page 9-4
• Image$$ execution region symbols on page 7-6.
Reference
Linker Reference:
• --linker_script=ld_script on page 2-100
• --symver_script=file on page 2-167.
ARM DUI 0474C Copyright © 2010-2011 ARM. All rights reserved. 9-6
ID080411 Non-Confidential