text : $RELA ?A;
text : $REL ?A;
text : .IA_64.unwind_hdr;
text : $UNWIND ?A;
text : .IA_64.unwind_info;
text : .HP.opt_annot;
text : $PROGBITS ?A!X!W;
text : .IA_64.milli;
text : .text;
text : $PROGBITS ?AX!W;
text : $OVLBITS ?AX!W;
# data segment
data = LOAD ?RWmo V0x6000000000000000; data : .zeropage;
data : .hdata;
data : .data;
data : $PROGBITS ?AW!S;
data : .preinit_array;
data : .init_array;
data : .fini_array;
data : .opd;
data : .plt;
data : .dlt;
data : .sdata;
data : $PROGBITS ?AWS;
data : .sbss;
data : $NOBITS ?AWS;
data : .bss;
data : $NOBITS ?AW!S;data : .hbss;
#thread specific storage segment thread_specific = HP_TLS ?RW; thread_specific : .tbss; thread_specific : $NOBITS ?AWT;
#note segment
note = NOTE; note : $NOTE;
#
Defining Syntax for Mapfile Directives
A mapfile can have zero or more mapfile directives. There are two types of mapfile directives: segment declarations and section mapping directives. The directives can span across lines and are terminated by a semicolon. The following syntax conventions are used to describe the directives:
•[...]* means zero or more.
•[...]+ means one or more.
•[...] means optional.
•The section_names and segment_names are the same as a C identifier except that a period
(.)is treated as a letter.
•A number can be hexadecimal, following the same syntax as the C language.
Defining Syntax for Mapfile Directives 195