There are a few other linker scripts commands.
ASSERT(
exp,
message)
Note that assertions are checked before the final stages of linking take place. This means that expressions involving symbols PROVIDEd inside section definitions will fail if the user has not set values for those symbols. The only exception to this rule is PROVIDEd symbols that just reference dot. Thus an assertion like this:
.stack : { PROVIDE (__stack = .); PROVIDE (__stack_size = 0x100); ASSERT ((__stack > (_end + __stack_size)), "Error: No room left for the stack"); }
will fail if __stack_size
is not defined elsewhere. Symbols
PROVIDEd outside of section definitions are evaluated earlier, so they
can be used inside ASSERTions. Thus:
PROVIDE (__stack_size = 0x100); .stack : { PROVIDE (__stack = .); ASSERT ((__stack > (_end + __stack_size)), "Error: No room left for the stack"); }
will work.
EXTERN(
symbol symbol ...)
EXTERN
, and you may use EXTERN
multiple times. This
command has the same effect as the ‘-u’ command-line option.
FORCE_COMMON_ALLOCATION
INHIBIT_COMMON_ALLOCATION
ld
omit the assignment of addresses
to common symbols even for a non-relocatable output file.
INSERT [ AFTER | BEFORE ]
output_sectionSECTIONS
with, for example, overlays. It
inserts all prior linker script statements after (or before)
output_section, and also causes ‘-T’ to not override the
default linker script. The exact insertion point is as for orphan
sections. See Location Counter. The insertion happens after the
linker has mapped input sections to output sections. Prior to the
insertion, since ‘-T’ scripts are parsed before the default
linker script, statements in the ‘-T’ script occur before the
default linker script statements in the internal linker representation
of the script. In particular, input section assignments will be made
to ‘-T’ output sections before those in the default script. Here
is an example of how a ‘-T’ script using INSERT
might look:
SECTIONS { OVERLAY : { .ov1 { ov1*(.text) } .ov2 { ov2*(.text) } } } INSERT AFTER .text;
NOCROSSREFS(
section section ...)
In certain types of programs, particularly on embedded systems when using overlays, when one section is loaded into memory, another section will not be. Any direct references between the two sections would be errors. For example, it would be an error if code in one section called a function defined in the other section.
The NOCROSSREFS
command takes a list of output section names. If
ld detects any cross references between the sections, it reports
an error and returns a non-zero exit status. Note that the
NOCROSSREFS
command uses output section names, not input section
names.
OUTPUT_ARCH(
bfdarch)
objdump
program with
the ‘-f’ option.
LD_FEATURE(
string)
"SANE_EXPR"
then absolute symbols and numbers
in a script are simply treated as numbers everywhere.
See Expression Section.