GNUPro® Toolkit GNUPro Development Tools

}
SECTIONS Command
In the previousexample, if the program defines _etext, the linker will give a multiple
definition error. If, on the other hand, the program defines etext, the linker will
silently use the definition in the program. If the program references etext but does not
define it, the linker will use the definition in the linker script.
SECTIONS Command
The SECTIONS command tells the linker how to map input sections into output
sections, and how to place the output sections in memory. The following
documentation describes more of the SECTIONS command.
■ “Output Section Description” on page 38
■ “Output Section Name” on page 38
■ “Output Section Address” on page 39
■ “Input Section Description” on page 39
■ “Input Section Basics” on page 39
■ “Input Section Wildcard Patterns” on page 40
■ “Input Section for Common Symbols” on page 41
■ “Input Section and Garbage Collection” on page 42
■ “Input Section Example” on page 42
■ “Output Section Data” on page 42
■ “Output Section Keywords” on page 43
■ “Output Section Discarding” on page 44
■ “Output Section Attributes” on page 45
■ “Output Section Type” on page 45
■ “Output Section LMA” on page 45
■ “Output Section Region” on page 46
■ “Output Section to Programs Previously Defined” on page 46
■ “Output Section Fill” on page 47
■ “Overlay Description” on page 47
The format of the SECTIONS command is:
SECTIONS
{
sections-command
sections-command
...
}
Red Hat GNUPro Toolkit Using ld / GNUPro Development Tools ■ 37