3 @c Copyright (C) 1991-2014 Free Software Foundation, Inc.
6 @include configdoc.texi
7 @c (configdoc.texi is generated by the Makefile)
13 @macro gcctabopt{body}
19 @c Configure for the generation of man pages
45 @dircategory Software development
47 * Ld: (ld). The GNU linker.
52 This file documents the @sc{gnu} linker LD
53 @ifset VERSION_PACKAGE
54 @value{VERSION_PACKAGE}
56 version @value{VERSION}.
58 Copyright @copyright{} 1991-2014 Free Software Foundation, Inc.
60 Permission is granted to copy, distribute and/or modify this document
61 under the terms of the GNU Free Documentation License, Version 1.3
62 or any later version published by the Free Software Foundation;
63 with no Invariant Sections, with no Front-Cover Texts, and with no
64 Back-Cover Texts. A copy of the license is included in the
65 section entitled ``GNU Free Documentation License''.
69 @setchapternewpage odd
70 @settitle The GNU linker
75 @ifset VERSION_PACKAGE
76 @subtitle @value{VERSION_PACKAGE}
78 @subtitle Version @value{VERSION}
79 @author Steve Chamberlain
80 @author Ian Lance Taylor
85 \hfill Red Hat Inc\par
86 \hfill nickc\@credhat.com, doc\@redhat.com\par
87 \hfill {\it The GNU linker}\par
88 \hfill Edited by Jeffrey Osier (jeffrey\@cygnus.com)\par
90 \global\parindent=0pt % Steve likes it this way.
93 @vskip 0pt plus 1filll
94 @c man begin COPYRIGHT
95 Copyright @copyright{} 1991-2014 Free Software Foundation, Inc.
97 Permission is granted to copy, distribute and/or modify this document
98 under the terms of the GNU Free Documentation License, Version 1.3
99 or any later version published by the Free Software Foundation;
100 with no Invariant Sections, with no Front-Cover Texts, and with no
101 Back-Cover Texts. A copy of the license is included in the
102 section entitled ``GNU Free Documentation License''.
108 @c FIXME: Talk about importance of *order* of args, cmds to linker!
113 This file documents the @sc{gnu} linker ld
114 @ifset VERSION_PACKAGE
115 @value{VERSION_PACKAGE}
117 version @value{VERSION}.
119 This document is distributed under the terms of the GNU Free
120 Documentation License version 1.3. A copy of the license is included
121 in the section entitled ``GNU Free Documentation License''.
124 * Overview:: Overview
125 * Invocation:: Invocation
126 * Scripts:: Linker Scripts
128 * Machine Dependent:: Machine Dependent Features
132 * H8/300:: ld and the H8/300
135 * Renesas:: ld and other Renesas micros
138 * i960:: ld and the Intel 960 family
141 * ARM:: ld and the ARM family
144 * M68HC11/68HC12:: ld and the Motorola 68HC11 and 68HC12 families
147 * HPPA ELF32:: ld and HPPA 32-bit ELF
150 * M68K:: ld and Motorola 68K family
153 * MIPS:: ld and MIPS family
156 * PowerPC ELF32:: ld and PowerPC 32-bit ELF Support
159 * PowerPC64 ELF64:: ld and PowerPC64 64-bit ELF Support
162 * SPU ELF:: ld and SPU ELF Support
165 * TI COFF:: ld and the TI COFF
168 * Win32:: ld and WIN32 (cygwin/mingw)
171 * Xtensa:: ld and Xtensa Processors
174 @ifclear SingleFormat
177 @c Following blank line required for remaining bug in makeinfo conds/menus
179 * Reporting Bugs:: Reporting Bugs
180 * MRI:: MRI Compatible Script Files
181 * GNU Free Documentation License:: GNU Free Documentation License
182 * LD Index:: LD Index
189 @cindex @sc{gnu} linker
190 @cindex what is this?
193 @c man begin SYNOPSIS
194 ld [@b{options}] @var{objfile} @dots{}
198 ar(1), nm(1), objcopy(1), objdump(1), readelf(1) and
199 the Info entries for @file{binutils} and
204 @c man begin DESCRIPTION
206 @command{ld} combines a number of object and archive files, relocates
207 their data and ties up symbol references. Usually the last step in
208 compiling a program is to run @command{ld}.
210 @command{ld} accepts Linker Command Language files written in
211 a superset of AT&T's Link Editor Command Language syntax,
212 to provide explicit and total control over the linking process.
216 This man page does not describe the command language; see the
217 @command{ld} entry in @code{info} for full details on the command
218 language and on other aspects of the GNU linker.
221 @ifclear SingleFormat
222 This version of @command{ld} uses the general purpose BFD libraries
223 to operate on object files. This allows @command{ld} to read, combine, and
224 write object files in many different formats---for example, COFF or
225 @code{a.out}. Different formats may be linked together to produce any
226 available kind of object file. @xref{BFD}, for more information.
229 Aside from its flexibility, the @sc{gnu} linker is more helpful than other
230 linkers in providing diagnostic information. Many linkers abandon
231 execution immediately upon encountering an error; whenever possible,
232 @command{ld} continues executing, allowing you to identify other errors
233 (or, in some cases, to get an output file in spite of the error).
240 @c man begin DESCRIPTION
242 The @sc{gnu} linker @command{ld} is meant to cover a broad range of situations,
243 and to be as compatible as possible with other linkers. As a result,
244 you have many choices to control its behavior.
250 * Options:: Command Line Options
251 * Environment:: Environment Variables
255 @section Command Line Options
263 The linker supports a plethora of command-line options, but in actual
264 practice few of them are used in any particular context.
265 @cindex standard Unix system
266 For instance, a frequent use of @command{ld} is to link standard Unix
267 object files on a standard, supported Unix system. On such a system, to
268 link a file @code{hello.o}:
271 ld -o @var{output} /lib/crt0.o hello.o -lc
274 This tells @command{ld} to produce a file called @var{output} as the
275 result of linking the file @code{/lib/crt0.o} with @code{hello.o} and
276 the library @code{libc.a}, which will come from the standard search
277 directories. (See the discussion of the @samp{-l} option below.)
279 Some of the command-line options to @command{ld} may be specified at any
280 point in the command line. However, options which refer to files, such
281 as @samp{-l} or @samp{-T}, cause the file to be read at the point at
282 which the option appears in the command line, relative to the object
283 files and other file options. Repeating non-file options with a
284 different argument will either have no further effect, or override prior
285 occurrences (those further to the left on the command line) of that
286 option. Options which may be meaningfully specified more than once are
287 noted in the descriptions below.
290 Non-option arguments are object files or archives which are to be linked
291 together. They may follow, precede, or be mixed in with command-line
292 options, except that an object file argument may not be placed between
293 an option and its argument.
295 Usually the linker is invoked with at least one object file, but you can
296 specify other forms of binary input files using @samp{-l}, @samp{-R},
297 and the script command language. If @emph{no} binary input files at all
298 are specified, the linker does not produce any output, and issues the
299 message @samp{No input files}.
301 If the linker cannot recognize the format of an object file, it will
302 assume that it is a linker script. A script specified in this way
303 augments the main linker script used for the link (either the default
304 linker script or the one specified by using @samp{-T}). This feature
305 permits the linker to link against a file which appears to be an object
306 or an archive, but actually merely defines some symbol values, or uses
307 @code{INPUT} or @code{GROUP} to load other objects. Specifying a
308 script in this way merely augments the main linker script, with the
309 extra commands placed after the main script; use the @samp{-T} option
310 to replace the default linker script entirely, but note the effect of
311 the @code{INSERT} command. @xref{Scripts}.
313 For options whose names are a single letter,
314 option arguments must either follow the option letter without intervening
315 whitespace, or be given as separate arguments immediately following the
316 option that requires them.
318 For options whose names are multiple letters, either one dash or two can
319 precede the option name; for example, @samp{-trace-symbol} and
320 @samp{--trace-symbol} are equivalent. Note---there is one exception to
321 this rule. Multiple letter options that start with a lower case 'o' can
322 only be preceded by two dashes. This is to reduce confusion with the
323 @samp{-o} option. So for example @samp{-omagic} sets the output file
324 name to @samp{magic} whereas @samp{--omagic} sets the NMAGIC flag on the
327 Arguments to multiple-letter options must either be separated from the
328 option name by an equals sign, or be given as separate arguments
329 immediately following the option that requires them. For example,
330 @samp{--trace-symbol foo} and @samp{--trace-symbol=foo} are equivalent.
331 Unique abbreviations of the names of multiple-letter options are
334 Note---if the linker is being invoked indirectly, via a compiler driver
335 (e.g. @samp{gcc}) then all the linker command line options should be
336 prefixed by @samp{-Wl,} (or whatever is appropriate for the particular
337 compiler driver) like this:
340 gcc -Wl,--start-group foo.o bar.o -Wl,--end-group
343 This is important, because otherwise the compiler driver program may
344 silently drop the linker options, resulting in a bad link. Confusion
345 may also arise when passing options that require values through a
346 driver, as the use of a space between option and argument acts as
347 a separator, and causes the driver to pass only the option to the linker
348 and the argument to the compiler. In this case, it is simplest to use
349 the joined forms of both single- and multiple-letter options, such as:
352 gcc foo.o bar.o -Wl,-eENTRY -Wl,-Map=a.map
355 Here is a table of the generic command line switches accepted by the GNU
359 @include at-file.texi
361 @kindex -a @var{keyword}
362 @item -a @var{keyword}
363 This option is supported for HP/UX compatibility. The @var{keyword}
364 argument must be one of the strings @samp{archive}, @samp{shared}, or
365 @samp{default}. @samp{-aarchive} is functionally equivalent to
366 @samp{-Bstatic}, and the other two keywords are functionally equivalent
367 to @samp{-Bdynamic}. This option may be used any number of times.
369 @kindex --audit @var{AUDITLIB}
370 @item --audit @var{AUDITLIB}
371 Adds @var{AUDITLIB} to the @code{DT_AUDIT} entry of the dynamic section.
372 @var{AUDITLIB} is not checked for existence, nor will it use the DT_SONAME
373 specified in the library. If specified multiple times @code{DT_AUDIT}
374 will contain a colon separated list of audit interfaces to use. If the linker
375 finds an object with an audit entry while searching for shared libraries,
376 it will add a corresponding @code{DT_DEPAUDIT} entry in the output file.
377 This option is only meaningful on ELF platforms supporting the rtld-audit
381 @cindex architectures
382 @kindex -A @var{arch}
383 @item -A @var{architecture}
384 @kindex --architecture=@var{arch}
385 @itemx --architecture=@var{architecture}
386 In the current release of @command{ld}, this option is useful only for the
387 Intel 960 family of architectures. In that @command{ld} configuration, the
388 @var{architecture} argument identifies the particular architecture in
389 the 960 family, enabling some safeguards and modifying the
390 archive-library search path. @xref{i960,,@command{ld} and the Intel 960
391 family}, for details.
393 Future releases of @command{ld} may support similar functionality for
394 other architecture families.
397 @ifclear SingleFormat
398 @cindex binary input format
399 @kindex -b @var{format}
400 @kindex --format=@var{format}
403 @item -b @var{input-format}
404 @itemx --format=@var{input-format}
405 @command{ld} may be configured to support more than one kind of object
406 file. If your @command{ld} is configured this way, you can use the
407 @samp{-b} option to specify the binary format for input object files
408 that follow this option on the command line. Even when @command{ld} is
409 configured to support alternative object formats, you don't usually need
410 to specify this, as @command{ld} should be configured to expect as a
411 default input format the most usual format on each machine.
412 @var{input-format} is a text string, the name of a particular format
413 supported by the BFD libraries. (You can list the available binary
414 formats with @samp{objdump -i}.)
417 You may want to use this option if you are linking files with an unusual
418 binary format. You can also use @samp{-b} to switch formats explicitly (when
419 linking object files of different formats), by including
420 @samp{-b @var{input-format}} before each group of object files in a
423 The default format is taken from the environment variable
428 You can also define the input format from a script, using the command
431 see @ref{Format Commands}.
435 @kindex -c @var{MRI-cmdfile}
436 @kindex --mri-script=@var{MRI-cmdfile}
437 @cindex compatibility, MRI
438 @item -c @var{MRI-commandfile}
439 @itemx --mri-script=@var{MRI-commandfile}
440 For compatibility with linkers produced by MRI, @command{ld} accepts script
441 files written in an alternate, restricted command language, described in
443 @ref{MRI,,MRI Compatible Script Files}.
446 the MRI Compatible Script Files section of GNU ld documentation.
448 Introduce MRI script files with
449 the option @samp{-c}; use the @samp{-T} option to run linker
450 scripts written in the general-purpose @command{ld} scripting language.
451 If @var{MRI-cmdfile} does not exist, @command{ld} looks for it in the directories
452 specified by any @samp{-L} options.
454 @cindex common allocation
461 These three options are equivalent; multiple forms are supported for
462 compatibility with other linkers. They assign space to common symbols
463 even if a relocatable output file is specified (with @samp{-r}). The
464 script command @code{FORCE_COMMON_ALLOCATION} has the same effect.
465 @xref{Miscellaneous Commands}.
467 @kindex --depaudit @var{AUDITLIB}
468 @kindex -P @var{AUDITLIB}
469 @item --depaudit @var{AUDITLIB}
470 @itemx -P @var{AUDITLIB}
471 Adds @var{AUDITLIB} to the @code{DT_DEPAUDIT} entry of the dynamic section.
472 @var{AUDITLIB} is not checked for existence, nor will it use the DT_SONAME
473 specified in the library. If specified multiple times @code{DT_DEPAUDIT}
474 will contain a colon separated list of audit interfaces to use. This
475 option is only meaningful on ELF platforms supporting the rtld-audit interface.
476 The -P option is provided for Solaris compatibility.
478 @cindex entry point, from command line
479 @kindex -e @var{entry}
480 @kindex --entry=@var{entry}
482 @itemx --entry=@var{entry}
483 Use @var{entry} as the explicit symbol for beginning execution of your
484 program, rather than the default entry point. If there is no symbol
485 named @var{entry}, the linker will try to parse @var{entry} as a number,
486 and use that as the entry address (the number will be interpreted in
487 base 10; you may use a leading @samp{0x} for base 16, or a leading
488 @samp{0} for base 8). @xref{Entry Point}, for a discussion of defaults
489 and other ways of specifying the entry point.
491 @kindex --exclude-libs
492 @item --exclude-libs @var{lib},@var{lib},...
493 Specifies a list of archive libraries from which symbols should not be automatically
494 exported. The library names may be delimited by commas or colons. Specifying
495 @code{--exclude-libs ALL} excludes symbols in all archive libraries from
496 automatic export. This option is available only for the i386 PE targeted
497 port of the linker and for ELF targeted ports. For i386 PE, symbols
498 explicitly listed in a .def file are still exported, regardless of this
499 option. For ELF targeted ports, symbols affected by this option will
500 be treated as hidden.
502 @kindex --exclude-modules-for-implib
503 @item --exclude-modules-for-implib @var{module},@var{module},...
504 Specifies a list of object files or archive members, from which symbols
505 should not be automatically exported, but which should be copied wholesale
506 into the import library being generated during the link. The module names
507 may be delimited by commas or colons, and must match exactly the filenames
508 used by @command{ld} to open the files; for archive members, this is simply
509 the member name, but for object files the name listed must include and
510 match precisely any path used to specify the input file on the linker's
511 command-line. This option is available only for the i386 PE targeted port
512 of the linker. Symbols explicitly listed in a .def file are still exported,
513 regardless of this option.
515 @cindex dynamic symbol table
517 @kindex --export-dynamic
518 @kindex --no-export-dynamic
520 @itemx --export-dynamic
521 @itemx --no-export-dynamic
522 When creating a dynamically linked executable, using the @option{-E}
523 option or the @option{--export-dynamic} option causes the linker to add
524 all symbols to the dynamic symbol table. The dynamic symbol table is the
525 set of symbols which are visible from dynamic objects at run time.
527 If you do not use either of these options (or use the
528 @option{--no-export-dynamic} option to restore the default behavior), the
529 dynamic symbol table will normally contain only those symbols which are
530 referenced by some dynamic object mentioned in the link.
532 If you use @code{dlopen} to load a dynamic object which needs to refer
533 back to the symbols defined by the program, rather than some other
534 dynamic object, then you will probably need to use this option when
535 linking the program itself.
537 You can also use the dynamic list to control what symbols should
538 be added to the dynamic symbol table if the output format supports it.
539 See the description of @samp{--dynamic-list}.
541 Note that this option is specific to ELF targeted ports. PE targets
542 support a similar function to export all symbols from a DLL or EXE; see
543 the description of @samp{--export-all-symbols} below.
545 @ifclear SingleFormat
546 @cindex big-endian objects
550 Link big-endian objects. This affects the default output format.
552 @cindex little-endian objects
555 Link little-endian objects. This affects the default output format.
558 @kindex -f @var{name}
559 @kindex --auxiliary=@var{name}
561 @itemx --auxiliary=@var{name}
562 When creating an ELF shared object, set the internal DT_AUXILIARY field
563 to the specified name. This tells the dynamic linker that the symbol
564 table of the shared object should be used as an auxiliary filter on the
565 symbol table of the shared object @var{name}.
567 If you later link a program against this filter object, then, when you
568 run the program, the dynamic linker will see the DT_AUXILIARY field. If
569 the dynamic linker resolves any symbols from the filter object, it will
570 first check whether there is a definition in the shared object
571 @var{name}. If there is one, it will be used instead of the definition
572 in the filter object. The shared object @var{name} need not exist.
573 Thus the shared object @var{name} may be used to provide an alternative
574 implementation of certain functions, perhaps for debugging or for
575 machine specific performance.
577 This option may be specified more than once. The DT_AUXILIARY entries
578 will be created in the order in which they appear on the command line.
580 @kindex -F @var{name}
581 @kindex --filter=@var{name}
583 @itemx --filter=@var{name}
584 When creating an ELF shared object, set the internal DT_FILTER field to
585 the specified name. This tells the dynamic linker that the symbol table
586 of the shared object which is being created should be used as a filter
587 on the symbol table of the shared object @var{name}.
589 If you later link a program against this filter object, then, when you
590 run the program, the dynamic linker will see the DT_FILTER field. The
591 dynamic linker will resolve symbols according to the symbol table of the
592 filter object as usual, but it will actually link to the definitions
593 found in the shared object @var{name}. Thus the filter object can be
594 used to select a subset of the symbols provided by the object
597 Some older linkers used the @option{-F} option throughout a compilation
598 toolchain for specifying object-file format for both input and output
600 @ifclear SingleFormat
601 The @sc{gnu} linker uses other mechanisms for this purpose: the
602 @option{-b}, @option{--format}, @option{--oformat} options, the
603 @code{TARGET} command in linker scripts, and the @code{GNUTARGET}
604 environment variable.
606 The @sc{gnu} linker will ignore the @option{-F} option when not
607 creating an ELF shared object.
609 @cindex finalization function
610 @kindex -fini=@var{name}
611 @item -fini=@var{name}
612 When creating an ELF executable or shared object, call NAME when the
613 executable or shared object is unloaded, by setting DT_FINI to the
614 address of the function. By default, the linker uses @code{_fini} as
615 the function to call.
619 Ignored. Provided for compatibility with other tools.
621 @kindex -G @var{value}
622 @kindex --gpsize=@var{value}
625 @itemx --gpsize=@var{value}
626 Set the maximum size of objects to be optimized using the GP register to
627 @var{size}. This is only meaningful for object file formats such as
628 MIPS ELF that support putting large and small objects into different
629 sections. This is ignored for other object file formats.
631 @cindex runtime library name
632 @kindex -h @var{name}
633 @kindex -soname=@var{name}
635 @itemx -soname=@var{name}
636 When creating an ELF shared object, set the internal DT_SONAME field to
637 the specified name. When an executable is linked with a shared object
638 which has a DT_SONAME field, then when the executable is run the dynamic
639 linker will attempt to load the shared object specified by the DT_SONAME
640 field rather than the using the file name given to the linker.
643 @cindex incremental link
645 Perform an incremental link (same as option @samp{-r}).
647 @cindex initialization function
648 @kindex -init=@var{name}
649 @item -init=@var{name}
650 When creating an ELF executable or shared object, call NAME when the
651 executable or shared object is loaded, by setting DT_INIT to the address
652 of the function. By default, the linker uses @code{_init} as the
655 @cindex archive files, from cmd line
656 @kindex -l @var{namespec}
657 @kindex --library=@var{namespec}
658 @item -l @var{namespec}
659 @itemx --library=@var{namespec}
660 Add the archive or object file specified by @var{namespec} to the
661 list of files to link. This option may be used any number of times.
662 If @var{namespec} is of the form @file{:@var{filename}}, @command{ld}
663 will search the library path for a file called @var{filename}, otherwise it
664 will search the library path for a file called @file{lib@var{namespec}.a}.
666 On systems which support shared libraries, @command{ld} may also search for
667 files other than @file{lib@var{namespec}.a}. Specifically, on ELF
668 and SunOS systems, @command{ld} will search a directory for a library
669 called @file{lib@var{namespec}.so} before searching for one called
670 @file{lib@var{namespec}.a}. (By convention, a @code{.so} extension
671 indicates a shared library.) Note that this behavior does not apply
672 to @file{:@var{filename}}, which always specifies a file called
675 The linker will search an archive only once, at the location where it is
676 specified on the command line. If the archive defines a symbol which
677 was undefined in some object which appeared before the archive on the
678 command line, the linker will include the appropriate file(s) from the
679 archive. However, an undefined symbol in an object appearing later on
680 the command line will not cause the linker to search the archive again.
682 See the @option{-(} option for a way to force the linker to search
683 archives multiple times.
685 You may list the same archive multiple times on the command line.
688 This type of archive searching is standard for Unix linkers. However,
689 if you are using @command{ld} on AIX, note that it is different from the
690 behaviour of the AIX linker.
693 @cindex search directory, from cmd line
695 @kindex --library-path=@var{dir}
696 @item -L @var{searchdir}
697 @itemx --library-path=@var{searchdir}
698 Add path @var{searchdir} to the list of paths that @command{ld} will search
699 for archive libraries and @command{ld} control scripts. You may use this
700 option any number of times. The directories are searched in the order
701 in which they are specified on the command line. Directories specified
702 on the command line are searched before the default directories. All
703 @option{-L} options apply to all @option{-l} options, regardless of the
704 order in which the options appear. @option{-L} options do not affect
705 how @command{ld} searches for a linker script unless @option{-T}
708 If @var{searchdir} begins with @code{=}, then the @code{=} will be replaced
709 by the @dfn{sysroot prefix}, a path specified when the linker is configured.
712 The default set of paths searched (without being specified with
713 @samp{-L}) depends on which emulation mode @command{ld} is using, and in
714 some cases also on how it was configured. @xref{Environment}.
717 The paths can also be specified in a link script with the
718 @code{SEARCH_DIR} command. Directories specified this way are searched
719 at the point in which the linker script appears in the command line.
722 @kindex -m @var{emulation}
723 @item -m @var{emulation}
724 Emulate the @var{emulation} linker. You can list the available
725 emulations with the @samp{--verbose} or @samp{-V} options.
727 If the @samp{-m} option is not used, the emulation is taken from the
728 @code{LDEMULATION} environment variable, if that is defined.
730 Otherwise, the default emulation depends upon how the linker was
738 Print a link map to the standard output. A link map provides
739 information about the link, including the following:
743 Where object files are mapped into memory.
745 How common symbols are allocated.
747 All archive members included in the link, with a mention of the symbol
748 which caused the archive member to be brought in.
750 The values assigned to symbols.
752 Note - symbols whose values are computed by an expression which
753 involves a reference to a previous value of the same symbol may not
754 have correct result displayed in the link map. This is because the
755 linker discards intermediate results and only retains the final value
756 of an expression. Under such circumstances the linker will display
757 the final value enclosed by square brackets. Thus for example a
758 linker script containing:
766 will produce the following output in the link map if the @option{-M}
771 [0x0000000c] foo = (foo * 0x4)
772 [0x0000000c] foo = (foo + 0x8)
775 See @ref{Expressions} for more information about expressions in linker
780 @cindex read-only text
785 Turn off page alignment of sections, and disable linking against shared
786 libraries. If the output format supports Unix style magic numbers,
787 mark the output as @code{NMAGIC}.
791 @cindex read/write from cmd line
795 Set the text and data sections to be readable and writable. Also, do
796 not page-align the data segment, and disable linking against shared
797 libraries. If the output format supports Unix style magic numbers,
798 mark the output as @code{OMAGIC}. Note: Although a writable text section
799 is allowed for PE-COFF targets, it does not conform to the format
800 specification published by Microsoft.
805 This option negates most of the effects of the @option{-N} option. It
806 sets the text section to be read-only, and forces the data segment to
807 be page-aligned. Note - this option does not enable linking against
808 shared libraries. Use @option{-Bdynamic} for this.
810 @kindex -o @var{output}
811 @kindex --output=@var{output}
812 @cindex naming the output file
813 @item -o @var{output}
814 @itemx --output=@var{output}
815 Use @var{output} as the name for the program produced by @command{ld}; if this
816 option is not specified, the name @file{a.out} is used by default. The
817 script command @code{OUTPUT} can also specify the output file name.
819 @kindex -O @var{level}
820 @cindex generating optimized output
822 If @var{level} is a numeric values greater than zero @command{ld} optimizes
823 the output. This might take significantly longer and therefore probably
824 should only be enabled for the final binary. At the moment this
825 option only affects ELF shared library generation. Future releases of
826 the linker may make more use of this option. Also currently there is
827 no difference in the linker's behaviour for different non-zero values
828 of this option. Again this may change with future releases.
831 @kindex --emit-relocs
832 @cindex retain relocations in final executable
835 Leave relocation sections and contents in fully linked executables.
836 Post link analysis and optimization tools may need this information in
837 order to perform correct modifications of executables. This results
838 in larger executables.
840 This option is currently only supported on ELF platforms.
842 @kindex --force-dynamic
843 @cindex forcing the creation of dynamic sections
844 @item --force-dynamic
845 Force the output file to have dynamic sections. This option is specific
849 @cindex relocatable output
851 @kindex --relocatable
854 Generate relocatable output---i.e., generate an output file that can in
855 turn serve as input to @command{ld}. This is often called @dfn{partial
856 linking}. As a side effect, in environments that support standard Unix
857 magic numbers, this option also sets the output file's magic number to
859 @c ; see @option{-N}.
860 If this option is not specified, an absolute file is produced. When
861 linking C++ programs, this option @emph{will not} resolve references to
862 constructors; to do that, use @samp{-Ur}.
864 When an input file does not have the same format as the output file,
865 partial linking is only supported if that input file does not contain any
866 relocations. Different output formats can have further restrictions; for
867 example some @code{a.out}-based formats do not support partial linking
868 with input files in other formats at all.
870 This option does the same thing as @samp{-i}.
872 @kindex -R @var{file}
873 @kindex --just-symbols=@var{file}
874 @cindex symbol-only input
875 @item -R @var{filename}
876 @itemx --just-symbols=@var{filename}
877 Read symbol names and their addresses from @var{filename}, but do not
878 relocate it or include it in the output. This allows your output file
879 to refer symbolically to absolute locations of memory defined in other
880 programs. You may use this option more than once.
882 For compatibility with other ELF linkers, if the @option{-R} option is
883 followed by a directory name, rather than a file name, it is treated as
884 the @option{-rpath} option.
888 @cindex strip all symbols
891 Omit all symbol information from the output file.
894 @kindex --strip-debug
895 @cindex strip debugger symbols
898 Omit debugger symbol information (but not all symbols) from the output file.
902 @cindex input files, displaying
905 Print the names of the input files as @command{ld} processes them.
907 @kindex -T @var{script}
908 @kindex --script=@var{script}
910 @item -T @var{scriptfile}
911 @itemx --script=@var{scriptfile}
912 Use @var{scriptfile} as the linker script. This script replaces
913 @command{ld}'s default linker script (rather than adding to it), so
914 @var{commandfile} must specify everything necessary to describe the
915 output file. @xref{Scripts}. If @var{scriptfile} does not exist in
916 the current directory, @code{ld} looks for it in the directories
917 specified by any preceding @samp{-L} options. Multiple @samp{-T}
920 @kindex -dT @var{script}
921 @kindex --default-script=@var{script}
923 @item -dT @var{scriptfile}
924 @itemx --default-script=@var{scriptfile}
925 Use @var{scriptfile} as the default linker script. @xref{Scripts}.
927 This option is similar to the @option{--script} option except that
928 processing of the script is delayed until after the rest of the
929 command line has been processed. This allows options placed after the
930 @option{--default-script} option on the command line to affect the
931 behaviour of the linker script, which can be important when the linker
932 command line cannot be directly controlled by the user. (eg because
933 the command line is being constructed by another tool, such as
936 @kindex -u @var{symbol}
937 @kindex --undefined=@var{symbol}
938 @cindex undefined symbol
939 @item -u @var{symbol}
940 @itemx --undefined=@var{symbol}
941 Force @var{symbol} to be entered in the output file as an undefined
942 symbol. Doing this may, for example, trigger linking of additional
943 modules from standard libraries. @samp{-u} may be repeated with
944 different option arguments to enter additional undefined symbols. This
945 option is equivalent to the @code{EXTERN} linker script command.
950 For anything other than C++ programs, this option is equivalent to
951 @samp{-r}: it generates relocatable output---i.e., an output file that can in
952 turn serve as input to @command{ld}. When linking C++ programs, @samp{-Ur}
953 @emph{does} resolve references to constructors, unlike @samp{-r}.
954 It does not work to use @samp{-Ur} on files that were themselves linked
955 with @samp{-Ur}; once the constructor table has been built, it cannot
956 be added to. Use @samp{-Ur} only for the last partial link, and
957 @samp{-r} for the others.
959 @kindex --unique[=@var{SECTION}]
960 @item --unique[=@var{SECTION}]
961 Creates a separate output section for every input section matching
962 @var{SECTION}, or if the optional wildcard @var{SECTION} argument is
963 missing, for every orphan input section. An orphan section is one not
964 specifically mentioned in a linker script. You may use this option
965 multiple times on the command line; It prevents the normal merging of
966 input sections with the same name, overriding output section assignments
976 Display the version number for @command{ld}. The @option{-V} option also
977 lists the supported emulations.
980 @kindex --discard-all
981 @cindex deleting local symbols
984 Delete all local symbols.
987 @kindex --discard-locals
988 @cindex local symbols, deleting
990 @itemx --discard-locals
991 Delete all temporary local symbols. (These symbols start with
992 system-specific local label prefixes, typically @samp{.L} for ELF systems
993 or @samp{L} for traditional a.out systems.)
995 @kindex -y @var{symbol}
996 @kindex --trace-symbol=@var{symbol}
997 @cindex symbol tracing
998 @item -y @var{symbol}
999 @itemx --trace-symbol=@var{symbol}
1000 Print the name of each linked file in which @var{symbol} appears. This
1001 option may be given any number of times. On many systems it is necessary
1002 to prepend an underscore.
1004 This option is useful when you have an undefined symbol in your link but
1005 don't know where the reference is coming from.
1007 @kindex -Y @var{path}
1009 Add @var{path} to the default library search path. This option exists
1010 for Solaris compatibility.
1012 @kindex -z @var{keyword}
1013 @item -z @var{keyword}
1014 The recognized keywords are:
1018 Combines multiple reloc sections and sorts them to make dynamic symbol
1019 lookup caching possible.
1022 Disallows undefined symbols in object files. Undefined symbols in
1023 shared libraries are still allowed.
1026 Marks the object as requiring executable stack.
1029 This option is only meaningful when building a shared object. It makes
1030 the symbols defined by this shared object available for symbol resolution
1031 of subsequently loaded libraries.
1034 This option is only meaningful when building a shared object.
1035 It marks the object so that its runtime initialization will occur
1036 before the runtime initialization of any other objects brought into
1037 the process at the same time. Similarly the runtime finalization of
1038 the object will occur after the runtime finalization of any other
1042 Marks the object that its symbol table interposes before all symbols
1043 but the primary executable.
1046 When generating an executable or shared library, mark it to tell the
1047 dynamic linker to defer function call resolution to the point when
1048 the function is called (lazy binding), rather than at load time.
1049 Lazy binding is the default.
1052 Marks the object that its filters be processed immediately at
1056 Allows multiple definitions.
1059 Disables multiple reloc sections combining.
1062 Disables production of copy relocs.
1065 Marks the object that the search for dependencies of this object will
1066 ignore any default library search paths.
1069 Marks the object shouldn't be unloaded at runtime.
1072 Marks the object not available to @code{dlopen}.
1075 Marks the object can not be dumped by @code{dldump}.
1078 Marks the object as not requiring executable stack.
1081 Don't create an ELF @code{PT_GNU_RELRO} segment header in the object.
1084 When generating an executable or shared library, mark it to tell the
1085 dynamic linker to resolve all symbols when the program is started, or
1086 when the shared library is linked to using dlopen, instead of
1087 deferring function call resolution to the point when the function is
1091 Marks the object may contain $ORIGIN.
1094 Create an ELF @code{PT_GNU_RELRO} segment header in the object.
1096 @item max-page-size=@var{value}
1097 Set the emulation maximum page size to @var{value}.
1099 @item common-page-size=@var{value}
1100 Set the emulation common page size to @var{value}.
1102 @item stack-size=@var{value}
1103 Specify a stack size for in an ELF @code{PT_GNU_STACK} segment.
1104 Specifying zero will override any default non-zero sized
1105 @code{PT_GNU_STACK} segment creation.
1109 Other keywords are ignored for Solaris compatibility.
1112 @cindex groups of archives
1113 @item -( @var{archives} -)
1114 @itemx --start-group @var{archives} --end-group
1115 The @var{archives} should be a list of archive files. They may be
1116 either explicit file names, or @samp{-l} options.
1118 The specified archives are searched repeatedly until no new undefined
1119 references are created. Normally, an archive is searched only once in
1120 the order that it is specified on the command line. If a symbol in that
1121 archive is needed to resolve an undefined symbol referred to by an
1122 object in an archive that appears later on the command line, the linker
1123 would not be able to resolve that reference. By grouping the archives,
1124 they all be searched repeatedly until all possible references are
1127 Using this option has a significant performance cost. It is best to use
1128 it only when there are unavoidable circular references between two or
1131 @kindex --accept-unknown-input-arch
1132 @kindex --no-accept-unknown-input-arch
1133 @item --accept-unknown-input-arch
1134 @itemx --no-accept-unknown-input-arch
1135 Tells the linker to accept input files whose architecture cannot be
1136 recognised. The assumption is that the user knows what they are doing
1137 and deliberately wants to link in these unknown input files. This was
1138 the default behaviour of the linker, before release 2.14. The default
1139 behaviour from release 2.14 onwards is to reject such input files, and
1140 so the @samp{--accept-unknown-input-arch} option has been added to
1141 restore the old behaviour.
1144 @kindex --no-as-needed
1146 @itemx --no-as-needed
1147 This option affects ELF DT_NEEDED tags for dynamic libraries mentioned
1148 on the command line after the @option{--as-needed} option. Normally
1149 the linker will add a DT_NEEDED tag for each dynamic library mentioned
1150 on the command line, regardless of whether the library is actually
1151 needed or not. @option{--as-needed} causes a DT_NEEDED tag to only be
1152 emitted for a library that @emph{at that point in the link} satisfies a
1153 non-weak undefined symbol reference from a regular object file or, if
1154 the library is not found in the DT_NEEDED lists of other libraries, a
1155 non-weak undefined symbol reference from another dynamic library.
1156 Object files or libraries appearing on the command line @emph{after}
1157 the library in question do not affect whether the library is seen as
1158 needed. This is similar to the rules for extraction of object files
1159 from archives. @option{--no-as-needed} restores the default behaviour.
1161 @kindex --add-needed
1162 @kindex --no-add-needed
1164 @itemx --no-add-needed
1165 These two options have been deprecated because of the similarity of
1166 their names to the @option{--as-needed} and @option{--no-as-needed}
1167 options. They have been replaced by @option{--copy-dt-needed-entries}
1168 and @option{--no-copy-dt-needed-entries}.
1170 @kindex -assert @var{keyword}
1171 @item -assert @var{keyword}
1172 This option is ignored for SunOS compatibility.
1176 @kindex -call_shared
1180 Link against dynamic libraries. This is only meaningful on platforms
1181 for which shared libraries are supported. This option is normally the
1182 default on such platforms. The different variants of this option are
1183 for compatibility with various systems. You may use this option
1184 multiple times on the command line: it affects library searching for
1185 @option{-l} options which follow it.
1189 Set the @code{DF_1_GROUP} flag in the @code{DT_FLAGS_1} entry in the dynamic
1190 section. This causes the runtime linker to handle lookups in this
1191 object and its dependencies to be performed only inside the group.
1192 @option{--unresolved-symbols=report-all} is implied. This option is
1193 only meaningful on ELF platforms which support shared libraries.
1203 Do not link against shared libraries. This is only meaningful on
1204 platforms for which shared libraries are supported. The different
1205 variants of this option are for compatibility with various systems. You
1206 may use this option multiple times on the command line: it affects
1207 library searching for @option{-l} options which follow it. This
1208 option also implies @option{--unresolved-symbols=report-all}. This
1209 option can be used with @option{-shared}. Doing so means that a
1210 shared library is being created but that all of the library's external
1211 references must be resolved by pulling in entries from static
1216 When creating a shared library, bind references to global symbols to the
1217 definition within the shared library, if any. Normally, it is possible
1218 for a program linked against a shared library to override the definition
1219 within the shared library. This option is only meaningful on ELF
1220 platforms which support shared libraries.
1222 @kindex -Bsymbolic-functions
1223 @item -Bsymbolic-functions
1224 When creating a shared library, bind references to global function
1225 symbols to the definition within the shared library, if any.
1226 This option is only meaningful on ELF platforms which support shared
1229 @kindex --dynamic-list=@var{dynamic-list-file}
1230 @item --dynamic-list=@var{dynamic-list-file}
1231 Specify the name of a dynamic list file to the linker. This is
1232 typically used when creating shared libraries to specify a list of
1233 global symbols whose references shouldn't be bound to the definition
1234 within the shared library, or creating dynamically linked executables
1235 to specify a list of symbols which should be added to the symbol table
1236 in the executable. This option is only meaningful on ELF platforms
1237 which support shared libraries.
1239 The format of the dynamic list is the same as the version node without
1240 scope and node name. See @ref{VERSION} for more information.
1242 @kindex --dynamic-list-data
1243 @item --dynamic-list-data
1244 Include all global data symbols to the dynamic list.
1246 @kindex --dynamic-list-cpp-new
1247 @item --dynamic-list-cpp-new
1248 Provide the builtin dynamic list for C++ operator new and delete. It
1249 is mainly useful for building shared libstdc++.
1251 @kindex --dynamic-list-cpp-typeinfo
1252 @item --dynamic-list-cpp-typeinfo
1253 Provide the builtin dynamic list for C++ runtime type identification.
1255 @kindex --check-sections
1256 @kindex --no-check-sections
1257 @item --check-sections
1258 @itemx --no-check-sections
1259 Asks the linker @emph{not} to check section addresses after they have
1260 been assigned to see if there are any overlaps. Normally the linker will
1261 perform this check, and if it finds any overlaps it will produce
1262 suitable error messages. The linker does know about, and does make
1263 allowances for sections in overlays. The default behaviour can be
1264 restored by using the command line switch @option{--check-sections}.
1265 Section overlap is not usually checked for relocatable links. You can
1266 force checking in that case by using the @option{--check-sections}
1269 @kindex --copy-dt-needed-entries
1270 @kindex --no-copy-dt-needed-entries
1271 @item --copy-dt-needed-entries
1272 @itemx --no-copy-dt-needed-entries
1273 This option affects the treatment of dynamic libraries referred to
1274 by DT_NEEDED tags @emph{inside} ELF dynamic libraries mentioned on the
1275 command line. Normally the linker won't add a DT_NEEDED tag to the
1276 output binary for each library mentioned in a DT_NEEDED tag in an
1277 input dynamic library. With @option{--copy-dt-needed-entries}
1278 specified on the command line however any dynamic libraries that
1279 follow it will have their DT_NEEDED entries added. The default
1280 behaviour can be restored with @option{--no-copy-dt-needed-entries}.
1282 This option also has an effect on the resolution of symbols in dynamic
1283 libraries. With @option{--copy-dt-needed-entries} dynamic libraries
1284 mentioned on the command line will be recursively searched, following
1285 their DT_NEEDED tags to other libraries, in order to resolve symbols
1286 required by the output binary. With the default setting however
1287 the searching of dynamic libraries that follow it will stop with the
1288 dynamic library itself. No DT_NEEDED links will be traversed to resolve
1291 @cindex cross reference table
1294 Output a cross reference table. If a linker map file is being
1295 generated, the cross reference table is printed to the map file.
1296 Otherwise, it is printed on the standard output.
1298 The format of the table is intentionally simple, so that it may be
1299 easily processed by a script if necessary. The symbols are printed out,
1300 sorted by name. For each symbol, a list of file names is given. If the
1301 symbol is defined, the first file listed is the location of the
1302 definition. If the symbol is defined as a common value then any files
1303 where this happens appear next. Finally any files that reference the
1306 @cindex common allocation
1307 @kindex --no-define-common
1308 @item --no-define-common
1309 This option inhibits the assignment of addresses to common symbols.
1310 The script command @code{INHIBIT_COMMON_ALLOCATION} has the same effect.
1311 @xref{Miscellaneous Commands}.
1313 The @samp{--no-define-common} option allows decoupling
1314 the decision to assign addresses to Common symbols from the choice
1315 of the output file type; otherwise a non-Relocatable output type
1316 forces assigning addresses to Common symbols.
1317 Using @samp{--no-define-common} allows Common symbols that are referenced
1318 from a shared library to be assigned addresses only in the main program.
1319 This eliminates the unused duplicate space in the shared library,
1320 and also prevents any possible confusion over resolving to the wrong
1321 duplicate when there are many dynamic modules with specialized search
1322 paths for runtime symbol resolution.
1324 @cindex symbols, from command line
1325 @kindex --defsym=@var{symbol}=@var{exp}
1326 @item --defsym=@var{symbol}=@var{expression}
1327 Create a global symbol in the output file, containing the absolute
1328 address given by @var{expression}. You may use this option as many
1329 times as necessary to define multiple symbols in the command line. A
1330 limited form of arithmetic is supported for the @var{expression} in this
1331 context: you may give a hexadecimal constant or the name of an existing
1332 symbol, or use @code{+} and @code{-} to add or subtract hexadecimal
1333 constants or symbols. If you need more elaborate expressions, consider
1334 using the linker command language from a script (@pxref{Assignments,,
1335 Assignment: Symbol Definitions}). @emph{Note:} there should be no white
1336 space between @var{symbol}, the equals sign (``@key{=}''), and
1339 @cindex demangling, from command line
1340 @kindex --demangle[=@var{style}]
1341 @kindex --no-demangle
1342 @item --demangle[=@var{style}]
1343 @itemx --no-demangle
1344 These options control whether to demangle symbol names in error messages
1345 and other output. When the linker is told to demangle, it tries to
1346 present symbol names in a readable fashion: it strips leading
1347 underscores if they are used by the object file format, and converts C++
1348 mangled symbol names into user readable names. Different compilers have
1349 different mangling styles. The optional demangling style argument can be used
1350 to choose an appropriate demangling style for your compiler. The linker will
1351 demangle by default unless the environment variable @samp{COLLECT_NO_DEMANGLE}
1352 is set. These options may be used to override the default.
1354 @cindex dynamic linker, from command line
1355 @kindex -I@var{file}
1356 @kindex --dynamic-linker=@var{file}
1358 @itemx --dynamic-linker=@var{file}
1359 Set the name of the dynamic linker. This is only meaningful when
1360 generating dynamically linked ELF executables. The default dynamic
1361 linker is normally correct; don't use this unless you know what you are
1364 @kindex --fatal-warnings
1365 @kindex --no-fatal-warnings
1366 @item --fatal-warnings
1367 @itemx --no-fatal-warnings
1368 Treat all warnings as errors. The default behaviour can be restored
1369 with the option @option{--no-fatal-warnings}.
1371 @kindex --force-exe-suffix
1372 @item --force-exe-suffix
1373 Make sure that an output file has a .exe suffix.
1375 If a successfully built fully linked output file does not have a
1376 @code{.exe} or @code{.dll} suffix, this option forces the linker to copy
1377 the output file to one of the same name with a @code{.exe} suffix. This
1378 option is useful when using unmodified Unix makefiles on a Microsoft
1379 Windows host, since some versions of Windows won't run an image unless
1380 it ends in a @code{.exe} suffix.
1382 @kindex --gc-sections
1383 @kindex --no-gc-sections
1384 @cindex garbage collection
1386 @itemx --no-gc-sections
1387 Enable garbage collection of unused input sections. It is ignored on
1388 targets that do not support this option. The default behaviour (of not
1389 performing this garbage collection) can be restored by specifying
1390 @samp{--no-gc-sections} on the command line.
1392 @samp{--gc-sections} decides which input sections are used by
1393 examining symbols and relocations. The section containing the entry
1394 symbol and all sections containing symbols undefined on the
1395 command-line will be kept, as will sections containing symbols
1396 referenced by dynamic objects. Note that when building shared
1397 libraries, the linker must assume that any visible symbol is
1398 referenced. Once this initial set of sections has been determined,
1399 the linker recursively marks as used any section referenced by their
1400 relocations. See @samp{--entry} and @samp{--undefined}.
1402 This option can be set when doing a partial link (enabled with option
1403 @samp{-r}). In this case the root of symbols kept must be explicitly
1404 specified either by an @samp{--entry} or @samp{--undefined} option or by
1405 a @code{ENTRY} command in the linker script.
1407 @kindex --print-gc-sections
1408 @kindex --no-print-gc-sections
1409 @cindex garbage collection
1410 @item --print-gc-sections
1411 @itemx --no-print-gc-sections
1412 List all sections removed by garbage collection. The listing is
1413 printed on stderr. This option is only effective if garbage
1414 collection has been enabled via the @samp{--gc-sections}) option. The
1415 default behaviour (of not listing the sections that are removed) can
1416 be restored by specifying @samp{--no-print-gc-sections} on the command
1419 @kindex --print-output-format
1420 @cindex output format
1421 @item --print-output-format
1422 Print the name of the default output format (perhaps influenced by
1423 other command-line options). This is the string that would appear
1424 in an @code{OUTPUT_FORMAT} linker script command (@pxref{File Commands}).
1430 Print a summary of the command-line options on the standard output and exit.
1432 @kindex --target-help
1434 Print a summary of all target specific options on the standard output and exit.
1436 @kindex -Map=@var{mapfile}
1437 @item -Map=@var{mapfile}
1438 Print a link map to the file @var{mapfile}. See the description of the
1439 @option{-M} option, above.
1441 @cindex memory usage
1442 @kindex --no-keep-memory
1443 @item --no-keep-memory
1444 @command{ld} normally optimizes for speed over memory usage by caching the
1445 symbol tables of input files in memory. This option tells @command{ld} to
1446 instead optimize for memory usage, by rereading the symbol tables as
1447 necessary. This may be required if @command{ld} runs out of memory space
1448 while linking a large executable.
1450 @kindex --no-undefined
1452 @item --no-undefined
1454 Report unresolved symbol references from regular object files. This
1455 is done even if the linker is creating a non-symbolic shared library.
1456 The switch @option{--[no-]allow-shlib-undefined} controls the
1457 behaviour for reporting unresolved references found in shared
1458 libraries being linked in.
1460 @kindex --allow-multiple-definition
1462 @item --allow-multiple-definition
1464 Normally when a symbol is defined multiple times, the linker will
1465 report a fatal error. These options allow multiple definitions and the
1466 first definition will be used.
1468 @kindex --allow-shlib-undefined
1469 @kindex --no-allow-shlib-undefined
1470 @item --allow-shlib-undefined
1471 @itemx --no-allow-shlib-undefined
1472 Allows or disallows undefined symbols in shared libraries.
1473 This switch is similar to @option{--no-undefined} except that it
1474 determines the behaviour when the undefined symbols are in a
1475 shared library rather than a regular object file. It does not affect
1476 how undefined symbols in regular object files are handled.
1478 The default behaviour is to report errors for any undefined symbols
1479 referenced in shared libraries if the linker is being used to create
1480 an executable, but to allow them if the linker is being used to create
1483 The reasons for allowing undefined symbol references in shared
1484 libraries specified at link time are that:
1488 A shared library specified at link time may not be the same as the one
1489 that is available at load time, so the symbol might actually be
1490 resolvable at load time.
1492 There are some operating systems, eg BeOS and HPPA, where undefined
1493 symbols in shared libraries are normal.
1495 The BeOS kernel for example patches shared libraries at load time to
1496 select whichever function is most appropriate for the current
1497 architecture. This is used, for example, to dynamically select an
1498 appropriate memset function.
1501 @kindex --no-undefined-version
1502 @item --no-undefined-version
1503 Normally when a symbol has an undefined version, the linker will ignore
1504 it. This option disallows symbols with undefined version and a fatal error
1505 will be issued instead.
1507 @kindex --default-symver
1508 @item --default-symver
1509 Create and use a default symbol version (the soname) for unversioned
1512 @kindex --default-imported-symver
1513 @item --default-imported-symver
1514 Create and use a default symbol version (the soname) for unversioned
1517 @kindex --no-warn-mismatch
1518 @item --no-warn-mismatch
1519 Normally @command{ld} will give an error if you try to link together input
1520 files that are mismatched for some reason, perhaps because they have
1521 been compiled for different processors or for different endiannesses.
1522 This option tells @command{ld} that it should silently permit such possible
1523 errors. This option should only be used with care, in cases when you
1524 have taken some special action that ensures that the linker errors are
1527 @kindex --no-warn-search-mismatch
1528 @item --no-warn-search-mismatch
1529 Normally @command{ld} will give a warning if it finds an incompatible
1530 library during a library search. This option silences the warning.
1532 @kindex --no-whole-archive
1533 @item --no-whole-archive
1534 Turn off the effect of the @option{--whole-archive} option for subsequent
1537 @cindex output file after errors
1538 @kindex --noinhibit-exec
1539 @item --noinhibit-exec
1540 Retain the executable output file whenever it is still usable.
1541 Normally, the linker will not produce an output file if it encounters
1542 errors during the link process; it exits without writing an output file
1543 when it issues any error whatsoever.
1547 Only search library directories explicitly specified on the
1548 command line. Library directories specified in linker scripts
1549 (including linker scripts specified on the command line) are ignored.
1551 @ifclear SingleFormat
1552 @kindex --oformat=@var{output-format}
1553 @item --oformat=@var{output-format}
1554 @command{ld} may be configured to support more than one kind of object
1555 file. If your @command{ld} is configured this way, you can use the
1556 @samp{--oformat} option to specify the binary format for the output
1557 object file. Even when @command{ld} is configured to support alternative
1558 object formats, you don't usually need to specify this, as @command{ld}
1559 should be configured to produce as a default output format the most
1560 usual format on each machine. @var{output-format} is a text string, the
1561 name of a particular format supported by the BFD libraries. (You can
1562 list the available binary formats with @samp{objdump -i}.) The script
1563 command @code{OUTPUT_FORMAT} can also specify the output format, but
1564 this option overrides it. @xref{BFD}.
1568 @kindex --pic-executable
1570 @itemx --pic-executable
1571 @cindex position independent executables
1572 Create a position independent executable. This is currently only supported on
1573 ELF platforms. Position independent executables are similar to shared
1574 libraries in that they are relocated by the dynamic linker to the virtual
1575 address the OS chooses for them (which can vary between invocations). Like
1576 normal dynamically linked executables they can be executed and symbols
1577 defined in the executable cannot be overridden by shared libraries.
1581 This option is ignored for Linux compatibility.
1585 This option is ignored for SVR4 compatibility.
1588 @cindex synthesizing linker
1589 @cindex relaxing addressing modes
1593 An option with machine dependent effects.
1595 This option is only supported on a few targets.
1598 @xref{H8/300,,@command{ld} and the H8/300}.
1601 @xref{i960,, @command{ld} and the Intel 960 family}.
1604 @xref{Xtensa,, @command{ld} and Xtensa Processors}.
1607 @xref{M68HC11/68HC12,,@command{ld} and the 68HC11 and 68HC12}.
1610 @xref{Nios II,,@command{ld} and the Altera Nios II}.
1613 @xref{PowerPC ELF32,,@command{ld} and PowerPC 32-bit ELF Support}.
1616 On some platforms the @samp{--relax} option performs target specific,
1617 global optimizations that become possible when the linker resolves
1618 addressing in the program, such as relaxing address modes,
1619 synthesizing new instructions, selecting shorter version of current
1620 instructions, and combining constant values.
1622 On some platforms these link time global optimizations may make symbolic
1623 debugging of the resulting executable impossible.
1625 This is known to be the case for the Matsushita MN10200 and MN10300
1626 family of processors.
1630 On platforms where this is not supported, @samp{--relax} is accepted,
1634 On platforms where @samp{--relax} is accepted the option
1635 @samp{--no-relax} can be used to disable the feature.
1637 @cindex retaining specified symbols
1638 @cindex stripping all but some symbols
1639 @cindex symbols, retaining selectively
1640 @kindex --retain-symbols-file=@var{filename}
1641 @item --retain-symbols-file=@var{filename}
1642 Retain @emph{only} the symbols listed in the file @var{filename},
1643 discarding all others. @var{filename} is simply a flat file, with one
1644 symbol name per line. This option is especially useful in environments
1648 where a large global symbol table is accumulated gradually, to conserve
1651 @samp{--retain-symbols-file} does @emph{not} discard undefined symbols,
1652 or symbols needed for relocations.
1654 You may only specify @samp{--retain-symbols-file} once in the command
1655 line. It overrides @samp{-s} and @samp{-S}.
1658 @item -rpath=@var{dir}
1659 @cindex runtime library search path
1660 @kindex -rpath=@var{dir}
1661 Add a directory to the runtime library search path. This is used when
1662 linking an ELF executable with shared objects. All @option{-rpath}
1663 arguments are concatenated and passed to the runtime linker, which uses
1664 them to locate shared objects at runtime. The @option{-rpath} option is
1665 also used when locating shared objects which are needed by shared
1666 objects explicitly included in the link; see the description of the
1667 @option{-rpath-link} option. If @option{-rpath} is not used when linking an
1668 ELF executable, the contents of the environment variable
1669 @code{LD_RUN_PATH} will be used if it is defined.
1671 The @option{-rpath} option may also be used on SunOS. By default, on
1672 SunOS, the linker will form a runtime search patch out of all the
1673 @option{-L} options it is given. If a @option{-rpath} option is used, the
1674 runtime search path will be formed exclusively using the @option{-rpath}
1675 options, ignoring the @option{-L} options. This can be useful when using
1676 gcc, which adds many @option{-L} options which may be on NFS mounted
1679 For compatibility with other ELF linkers, if the @option{-R} option is
1680 followed by a directory name, rather than a file name, it is treated as
1681 the @option{-rpath} option.
1685 @cindex link-time runtime library search path
1686 @kindex -rpath-link=@var{dir}
1687 @item -rpath-link=@var{dir}
1688 When using ELF or SunOS, one shared library may require another. This
1689 happens when an @code{ld -shared} link includes a shared library as one
1692 When the linker encounters such a dependency when doing a non-shared,
1693 non-relocatable link, it will automatically try to locate the required
1694 shared library and include it in the link, if it is not included
1695 explicitly. In such a case, the @option{-rpath-link} option
1696 specifies the first set of directories to search. The
1697 @option{-rpath-link} option may specify a sequence of directory names
1698 either by specifying a list of names separated by colons, or by
1699 appearing multiple times.
1701 This option should be used with caution as it overrides the search path
1702 that may have been hard compiled into a shared library. In such a case it
1703 is possible to use unintentionally a different search path than the
1704 runtime linker would do.
1706 The linker uses the following search paths to locate required shared
1710 Any directories specified by @option{-rpath-link} options.
1712 Any directories specified by @option{-rpath} options. The difference
1713 between @option{-rpath} and @option{-rpath-link} is that directories
1714 specified by @option{-rpath} options are included in the executable and
1715 used at runtime, whereas the @option{-rpath-link} option is only effective
1716 at link time. Searching @option{-rpath} in this way is only supported
1717 by native linkers and cross linkers which have been configured with
1718 the @option{--with-sysroot} option.
1720 On an ELF system, for native linkers, if the @option{-rpath} and
1721 @option{-rpath-link} options were not used, search the contents of the
1722 environment variable @code{LD_RUN_PATH}.
1724 On SunOS, if the @option{-rpath} option was not used, search any
1725 directories specified using @option{-L} options.
1727 For a native linker, search the contents of the environment
1728 variable @code{LD_LIBRARY_PATH}.
1730 For a native ELF linker, the directories in @code{DT_RUNPATH} or
1731 @code{DT_RPATH} of a shared library are searched for shared
1732 libraries needed by it. The @code{DT_RPATH} entries are ignored if
1733 @code{DT_RUNPATH} entries exist.
1735 The default directories, normally @file{/lib} and @file{/usr/lib}.
1737 For a native linker on an ELF system, if the file @file{/etc/ld.so.conf}
1738 exists, the list of directories found in that file.
1741 If the required shared library is not found, the linker will issue a
1742 warning and continue with the link.
1749 @cindex shared libraries
1750 Create a shared library. This is currently only supported on ELF, XCOFF
1751 and SunOS platforms. On SunOS, the linker will automatically create a
1752 shared library if the @option{-e} option is not used and there are
1753 undefined symbols in the link.
1755 @kindex --sort-common
1757 @itemx --sort-common=ascending
1758 @itemx --sort-common=descending
1759 This option tells @command{ld} to sort the common symbols by alignment in
1760 ascending or descending order when it places them in the appropriate output
1761 sections. The symbol alignments considered are sixteen-byte or larger,
1762 eight-byte, four-byte, two-byte, and one-byte. This is to prevent gaps
1763 between symbols due to alignment constraints. If no sorting order is
1764 specified, then descending order is assumed.
1766 @kindex --sort-section=name
1767 @item --sort-section=name
1768 This option will apply @code{SORT_BY_NAME} to all wildcard section
1769 patterns in the linker script.
1771 @kindex --sort-section=alignment
1772 @item --sort-section=alignment
1773 This option will apply @code{SORT_BY_ALIGNMENT} to all wildcard section
1774 patterns in the linker script.
1776 @kindex --split-by-file
1777 @item --split-by-file[=@var{size}]
1778 Similar to @option{--split-by-reloc} but creates a new output section for
1779 each input file when @var{size} is reached. @var{size} defaults to a
1780 size of 1 if not given.
1782 @kindex --split-by-reloc
1783 @item --split-by-reloc[=@var{count}]
1784 Tries to creates extra sections in the output file so that no single
1785 output section in the file contains more than @var{count} relocations.
1786 This is useful when generating huge relocatable files for downloading into
1787 certain real time kernels with the COFF object file format; since COFF
1788 cannot represent more than 65535 relocations in a single section. Note
1789 that this will fail to work with object file formats which do not
1790 support arbitrary sections. The linker will not split up individual
1791 input sections for redistribution, so if a single input section contains
1792 more than @var{count} relocations one output section will contain that
1793 many relocations. @var{count} defaults to a value of 32768.
1797 Compute and display statistics about the operation of the linker, such
1798 as execution time and memory usage.
1800 @kindex --sysroot=@var{directory}
1801 @item --sysroot=@var{directory}
1802 Use @var{directory} as the location of the sysroot, overriding the
1803 configure-time default. This option is only supported by linkers
1804 that were configured using @option{--with-sysroot}.
1806 @kindex --traditional-format
1807 @cindex traditional format
1808 @item --traditional-format
1809 For some targets, the output of @command{ld} is different in some ways from
1810 the output of some existing linker. This switch requests @command{ld} to
1811 use the traditional format instead.
1814 For example, on SunOS, @command{ld} combines duplicate entries in the
1815 symbol string table. This can reduce the size of an output file with
1816 full debugging information by over 30 percent. Unfortunately, the SunOS
1817 @code{dbx} program can not read the resulting program (@code{gdb} has no
1818 trouble). The @samp{--traditional-format} switch tells @command{ld} to not
1819 combine duplicate entries.
1821 @kindex --section-start=@var{sectionname}=@var{org}
1822 @item --section-start=@var{sectionname}=@var{org}
1823 Locate a section in the output file at the absolute
1824 address given by @var{org}. You may use this option as many
1825 times as necessary to locate multiple sections in the command
1827 @var{org} must be a single hexadecimal integer;
1828 for compatibility with other linkers, you may omit the leading
1829 @samp{0x} usually associated with hexadecimal values. @emph{Note:} there
1830 should be no white space between @var{sectionname}, the equals
1831 sign (``@key{=}''), and @var{org}.
1833 @kindex -Tbss=@var{org}
1834 @kindex -Tdata=@var{org}
1835 @kindex -Ttext=@var{org}
1836 @cindex segment origins, cmd line
1837 @item -Tbss=@var{org}
1838 @itemx -Tdata=@var{org}
1839 @itemx -Ttext=@var{org}
1840 Same as @option{--section-start}, with @code{.bss}, @code{.data} or
1841 @code{.text} as the @var{sectionname}.
1843 @kindex -Ttext-segment=@var{org}
1844 @item -Ttext-segment=@var{org}
1845 @cindex text segment origin, cmd line
1846 When creating an ELF executable, it will set the address of the first
1847 byte of the text segment.
1849 @kindex -Trodata-segment=@var{org}
1850 @item -Trodata-segment=@var{org}
1851 @cindex rodata segment origin, cmd line
1852 When creating an ELF executable or shared object for a target where
1853 the read-only data is in its own segment separate from the executable
1854 text, it will set the address of the first byte of the read-only data segment.
1856 @kindex -Tldata-segment=@var{org}
1857 @item -Tldata-segment=@var{org}
1858 @cindex ldata segment origin, cmd line
1859 When creating an ELF executable or shared object for x86-64 medium memory
1860 model, it will set the address of the first byte of the ldata segment.
1862 @kindex --unresolved-symbols
1863 @item --unresolved-symbols=@var{method}
1864 Determine how to handle unresolved symbols. There are four possible
1865 values for @samp{method}:
1869 Do not report any unresolved symbols.
1872 Report all unresolved symbols. This is the default.
1874 @item ignore-in-object-files
1875 Report unresolved symbols that are contained in shared libraries, but
1876 ignore them if they come from regular object files.
1878 @item ignore-in-shared-libs
1879 Report unresolved symbols that come from regular object files, but
1880 ignore them if they come from shared libraries. This can be useful
1881 when creating a dynamic binary and it is known that all the shared
1882 libraries that it should be referencing are included on the linker's
1886 The behaviour for shared libraries on their own can also be controlled
1887 by the @option{--[no-]allow-shlib-undefined} option.
1889 Normally the linker will generate an error message for each reported
1890 unresolved symbol but the option @option{--warn-unresolved-symbols}
1891 can change this to a warning.
1893 @kindex --verbose[=@var{NUMBER}]
1894 @cindex verbose[=@var{NUMBER}]
1896 @itemx --verbose[=@var{NUMBER}]
1897 Display the version number for @command{ld} and list the linker emulations
1898 supported. Display which input files can and cannot be opened. Display
1899 the linker script being used by the linker. If the optional @var{NUMBER}
1900 argument > 1, plugin symbol status will also be displayed.
1902 @kindex --version-script=@var{version-scriptfile}
1903 @cindex version script, symbol versions
1904 @item --version-script=@var{version-scriptfile}
1905 Specify the name of a version script to the linker. This is typically
1906 used when creating shared libraries to specify additional information
1907 about the version hierarchy for the library being created. This option
1908 is only fully supported on ELF platforms which support shared libraries;
1909 see @ref{VERSION}. It is partially supported on PE platforms, which can
1910 use version scripts to filter symbol visibility in auto-export mode: any
1911 symbols marked @samp{local} in the version script will not be exported.
1914 @kindex --warn-common
1915 @cindex warnings, on combining symbols
1916 @cindex combining symbols, warnings on
1918 Warn when a common symbol is combined with another common symbol or with
1919 a symbol definition. Unix linkers allow this somewhat sloppy practice,
1920 but linkers on some other operating systems do not. This option allows
1921 you to find potential problems from combining global symbols.
1922 Unfortunately, some C libraries use this practice, so you may get some
1923 warnings about symbols in the libraries as well as in your programs.
1925 There are three kinds of global symbols, illustrated here by C examples:
1929 A definition, which goes in the initialized data section of the output
1933 An undefined reference, which does not allocate space.
1934 There must be either a definition or a common symbol for the
1938 A common symbol. If there are only (one or more) common symbols for a
1939 variable, it goes in the uninitialized data area of the output file.
1940 The linker merges multiple common symbols for the same variable into a
1941 single symbol. If they are of different sizes, it picks the largest
1942 size. The linker turns a common symbol into a declaration, if there is
1943 a definition of the same variable.
1946 The @samp{--warn-common} option can produce five kinds of warnings.
1947 Each warning consists of a pair of lines: the first describes the symbol
1948 just encountered, and the second describes the previous symbol
1949 encountered with the same name. One or both of the two symbols will be
1954 Turning a common symbol into a reference, because there is already a
1955 definition for the symbol.
1957 @var{file}(@var{section}): warning: common of `@var{symbol}'
1958 overridden by definition
1959 @var{file}(@var{section}): warning: defined here
1963 Turning a common symbol into a reference, because a later definition for
1964 the symbol is encountered. This is the same as the previous case,
1965 except that the symbols are encountered in a different order.
1967 @var{file}(@var{section}): warning: definition of `@var{symbol}'
1969 @var{file}(@var{section}): warning: common is here
1973 Merging a common symbol with a previous same-sized common symbol.
1975 @var{file}(@var{section}): warning: multiple common
1977 @var{file}(@var{section}): warning: previous common is here
1981 Merging a common symbol with a previous larger common symbol.
1983 @var{file}(@var{section}): warning: common of `@var{symbol}'
1984 overridden by larger common
1985 @var{file}(@var{section}): warning: larger common is here
1989 Merging a common symbol with a previous smaller common symbol. This is
1990 the same as the previous case, except that the symbols are
1991 encountered in a different order.
1993 @var{file}(@var{section}): warning: common of `@var{symbol}'
1994 overriding smaller common
1995 @var{file}(@var{section}): warning: smaller common is here
1999 @kindex --warn-constructors
2000 @item --warn-constructors
2001 Warn if any global constructors are used. This is only useful for a few
2002 object file formats. For formats like COFF or ELF, the linker can not
2003 detect the use of global constructors.
2005 @kindex --warn-multiple-gp
2006 @item --warn-multiple-gp
2007 Warn if multiple global pointer values are required in the output file.
2008 This is only meaningful for certain processors, such as the Alpha.
2009 Specifically, some processors put large-valued constants in a special
2010 section. A special register (the global pointer) points into the middle
2011 of this section, so that constants can be loaded efficiently via a
2012 base-register relative addressing mode. Since the offset in
2013 base-register relative mode is fixed and relatively small (e.g., 16
2014 bits), this limits the maximum size of the constant pool. Thus, in
2015 large programs, it is often necessary to use multiple global pointer
2016 values in order to be able to address all possible constants. This
2017 option causes a warning to be issued whenever this case occurs.
2020 @cindex warnings, on undefined symbols
2021 @cindex undefined symbols, warnings on
2023 Only warn once for each undefined symbol, rather than once per module
2026 @kindex --warn-section-align
2027 @cindex warnings, on section alignment
2028 @cindex section alignment, warnings on
2029 @item --warn-section-align
2030 Warn if the address of an output section is changed because of
2031 alignment. Typically, the alignment will be set by an input section.
2032 The address will only be changed if it not explicitly specified; that
2033 is, if the @code{SECTIONS} command does not specify a start address for
2034 the section (@pxref{SECTIONS}).
2036 @kindex --warn-shared-textrel
2037 @item --warn-shared-textrel
2038 Warn if the linker adds a DT_TEXTREL to a shared object.
2040 @kindex --warn-alternate-em
2041 @item --warn-alternate-em
2042 Warn if an object has alternate ELF machine code.
2044 @kindex --warn-unresolved-symbols
2045 @item --warn-unresolved-symbols
2046 If the linker is going to report an unresolved symbol (see the option
2047 @option{--unresolved-symbols}) it will normally generate an error.
2048 This option makes it generate a warning instead.
2050 @kindex --error-unresolved-symbols
2051 @item --error-unresolved-symbols
2052 This restores the linker's default behaviour of generating errors when
2053 it is reporting unresolved symbols.
2055 @kindex --whole-archive
2056 @cindex including an entire archive
2057 @item --whole-archive
2058 For each archive mentioned on the command line after the
2059 @option{--whole-archive} option, include every object file in the archive
2060 in the link, rather than searching the archive for the required object
2061 files. This is normally used to turn an archive file into a shared
2062 library, forcing every object to be included in the resulting shared
2063 library. This option may be used more than once.
2065 Two notes when using this option from gcc: First, gcc doesn't know
2066 about this option, so you have to use @option{-Wl,-whole-archive}.
2067 Second, don't forget to use @option{-Wl,-no-whole-archive} after your
2068 list of archives, because gcc will add its own list of archives to
2069 your link and you may not want this flag to affect those as well.
2071 @kindex --wrap=@var{symbol}
2072 @item --wrap=@var{symbol}
2073 Use a wrapper function for @var{symbol}. Any undefined reference to
2074 @var{symbol} will be resolved to @code{__wrap_@var{symbol}}. Any
2075 undefined reference to @code{__real_@var{symbol}} will be resolved to
2078 This can be used to provide a wrapper for a system function. The
2079 wrapper function should be called @code{__wrap_@var{symbol}}. If it
2080 wishes to call the system function, it should call
2081 @code{__real_@var{symbol}}.
2083 Here is a trivial example:
2087 __wrap_malloc (size_t c)
2089 printf ("malloc called with %zu\n", c);
2090 return __real_malloc (c);
2094 If you link other code with this file using @option{--wrap malloc}, then
2095 all calls to @code{malloc} will call the function @code{__wrap_malloc}
2096 instead. The call to @code{__real_malloc} in @code{__wrap_malloc} will
2097 call the real @code{malloc} function.
2099 You may wish to provide a @code{__real_malloc} function as well, so that
2100 links without the @option{--wrap} option will succeed. If you do this,
2101 you should not put the definition of @code{__real_malloc} in the same
2102 file as @code{__wrap_malloc}; if you do, the assembler may resolve the
2103 call before the linker has a chance to wrap it to @code{malloc}.
2105 @kindex --eh-frame-hdr
2106 @item --eh-frame-hdr
2107 Request creation of @code{.eh_frame_hdr} section and ELF
2108 @code{PT_GNU_EH_FRAME} segment header.
2110 @kindex --ld-generated-unwind-info
2111 @item --no-ld-generated-unwind-info
2112 Request creation of @code{.eh_frame} unwind info for linker
2113 generated code sections like PLT. This option is on by default
2114 if linker generated unwind info is supported.
2116 @kindex --enable-new-dtags
2117 @kindex --disable-new-dtags
2118 @item --enable-new-dtags
2119 @itemx --disable-new-dtags
2120 This linker can create the new dynamic tags in ELF. But the older ELF
2121 systems may not understand them. If you specify
2122 @option{--enable-new-dtags}, the new dynamic tags will be created as needed
2123 and older dynamic tags will be omitted.
2124 If you specify @option{--disable-new-dtags}, no new dynamic tags will be
2125 created. By default, the new dynamic tags are not created. Note that
2126 those options are only available for ELF systems.
2128 @kindex --hash-size=@var{number}
2129 @item --hash-size=@var{number}
2130 Set the default size of the linker's hash tables to a prime number
2131 close to @var{number}. Increasing this value can reduce the length of
2132 time it takes the linker to perform its tasks, at the expense of
2133 increasing the linker's memory requirements. Similarly reducing this
2134 value can reduce the memory requirements at the expense of speed.
2136 @kindex --hash-style=@var{style}
2137 @item --hash-style=@var{style}
2138 Set the type of linker's hash table(s). @var{style} can be either
2139 @code{sysv} for classic ELF @code{.hash} section, @code{gnu} for
2140 new style GNU @code{.gnu.hash} section or @code{both} for both
2141 the classic ELF @code{.hash} and new style GNU @code{.gnu.hash}
2142 hash tables. The default is @code{sysv}.
2144 @kindex --reduce-memory-overheads
2145 @item --reduce-memory-overheads
2146 This option reduces memory requirements at ld runtime, at the expense of
2147 linking speed. This was introduced to select the old O(n^2) algorithm
2148 for link map file generation, rather than the new O(n) algorithm which uses
2149 about 40% more memory for symbol storage.
2151 Another effect of the switch is to set the default hash table size to
2152 1021, which again saves memory at the cost of lengthening the linker's
2153 run time. This is not done however if the @option{--hash-size} switch
2156 The @option{--reduce-memory-overheads} switch may be also be used to
2157 enable other tradeoffs in future versions of the linker.
2160 @kindex --build-id=@var{style}
2162 @itemx --build-id=@var{style}
2163 Request the creation of a @code{.note.gnu.build-id} ELF note section
2164 or a @code{.build-id} COFF section. The contents of the note are
2165 unique bits identifying this linked file. @var{style} can be
2166 @code{uuid} to use 128 random bits, @code{sha1} to use a 160-bit
2167 @sc{SHA1} hash on the normative parts of the output contents,
2168 @code{md5} to use a 128-bit @sc{MD5} hash on the normative parts of
2169 the output contents, or @code{0x@var{hexstring}} to use a chosen bit
2170 string specified as an even number of hexadecimal digits (@code{-} and
2171 @code{:} characters between digit pairs are ignored). If @var{style}
2172 is omitted, @code{sha1} is used.
2174 The @code{md5} and @code{sha1} styles produces an identifier
2175 that is always the same in an identical output file, but will be
2176 unique among all nonidentical output files. It is not intended
2177 to be compared as a checksum for the file's contents. A linked
2178 file may be changed later by other tools, but the build ID bit
2179 string identifying the original linked file does not change.
2181 Passing @code{none} for @var{style} disables the setting from any
2182 @code{--build-id} options earlier on the command line.
2187 @subsection Options Specific to i386 PE Targets
2189 @c man begin OPTIONS
2191 The i386 PE linker supports the @option{-shared} option, which causes
2192 the output to be a dynamically linked library (DLL) instead of a
2193 normal executable. You should name the output @code{*.dll} when you
2194 use this option. In addition, the linker fully supports the standard
2195 @code{*.def} files, which may be specified on the linker command line
2196 like an object file (in fact, it should precede archives it exports
2197 symbols from, to ensure that they get linked in, just like a normal
2200 In addition to the options common to all targets, the i386 PE linker
2201 support additional command line options that are specific to the i386
2202 PE target. Options that take values may be separated from their
2203 values by either a space or an equals sign.
2207 @kindex --add-stdcall-alias
2208 @item --add-stdcall-alias
2209 If given, symbols with a stdcall suffix (@@@var{nn}) will be exported
2210 as-is and also with the suffix stripped.
2211 [This option is specific to the i386 PE targeted port of the linker]
2214 @item --base-file @var{file}
2215 Use @var{file} as the name of a file in which to save the base
2216 addresses of all the relocations needed for generating DLLs with
2218 [This is an i386 PE specific option]
2222 Create a DLL instead of a regular executable. You may also use
2223 @option{-shared} or specify a @code{LIBRARY} in a given @code{.def}
2225 [This option is specific to the i386 PE targeted port of the linker]
2227 @kindex --enable-long-section-names
2228 @kindex --disable-long-section-names
2229 @item --enable-long-section-names
2230 @itemx --disable-long-section-names
2231 The PE variants of the Coff object format add an extension that permits
2232 the use of section names longer than eight characters, the normal limit
2233 for Coff. By default, these names are only allowed in object files, as
2234 fully-linked executable images do not carry the Coff string table required
2235 to support the longer names. As a GNU extension, it is possible to
2236 allow their use in executable images as well, or to (probably pointlessly!)
2237 disallow it in object files, by using these two options. Executable images
2238 generated with these long section names are slightly non-standard, carrying
2239 as they do a string table, and may generate confusing output when examined
2240 with non-GNU PE-aware tools, such as file viewers and dumpers. However,
2241 GDB relies on the use of PE long section names to find Dwarf-2 debug
2242 information sections in an executable image at runtime, and so if neither
2243 option is specified on the command-line, @command{ld} will enable long
2244 section names, overriding the default and technically correct behaviour,
2245 when it finds the presence of debug information while linking an executable
2246 image and not stripping symbols.
2247 [This option is valid for all PE targeted ports of the linker]
2249 @kindex --enable-stdcall-fixup
2250 @kindex --disable-stdcall-fixup
2251 @item --enable-stdcall-fixup
2252 @itemx --disable-stdcall-fixup
2253 If the link finds a symbol that it cannot resolve, it will attempt to
2254 do ``fuzzy linking'' by looking for another defined symbol that differs
2255 only in the format of the symbol name (cdecl vs stdcall) and will
2256 resolve that symbol by linking to the match. For example, the
2257 undefined symbol @code{_foo} might be linked to the function
2258 @code{_foo@@12}, or the undefined symbol @code{_bar@@16} might be linked
2259 to the function @code{_bar}. When the linker does this, it prints a
2260 warning, since it normally should have failed to link, but sometimes
2261 import libraries generated from third-party dlls may need this feature
2262 to be usable. If you specify @option{--enable-stdcall-fixup}, this
2263 feature is fully enabled and warnings are not printed. If you specify
2264 @option{--disable-stdcall-fixup}, this feature is disabled and such
2265 mismatches are considered to be errors.
2266 [This option is specific to the i386 PE targeted port of the linker]
2268 @kindex --leading-underscore
2269 @kindex --no-leading-underscore
2270 @item --leading-underscore
2271 @itemx --no-leading-underscore
2272 For most targets default symbol-prefix is an underscore and is defined
2273 in target's description. By this option it is possible to
2274 disable/enable the default underscore symbol-prefix.
2276 @cindex DLLs, creating
2277 @kindex --export-all-symbols
2278 @item --export-all-symbols
2279 If given, all global symbols in the objects used to build a DLL will
2280 be exported by the DLL. Note that this is the default if there
2281 otherwise wouldn't be any exported symbols. When symbols are
2282 explicitly exported via DEF files or implicitly exported via function
2283 attributes, the default is to not export anything else unless this
2284 option is given. Note that the symbols @code{DllMain@@12},
2285 @code{DllEntryPoint@@0}, @code{DllMainCRTStartup@@12}, and
2286 @code{impure_ptr} will not be automatically
2287 exported. Also, symbols imported from other DLLs will not be
2288 re-exported, nor will symbols specifying the DLL's internal layout
2289 such as those beginning with @code{_head_} or ending with
2290 @code{_iname}. In addition, no symbols from @code{libgcc},
2291 @code{libstd++}, @code{libmingw32}, or @code{crtX.o} will be exported.
2292 Symbols whose names begin with @code{__rtti_} or @code{__builtin_} will
2293 not be exported, to help with C++ DLLs. Finally, there is an
2294 extensive list of cygwin-private symbols that are not exported
2295 (obviously, this applies on when building DLLs for cygwin targets).
2296 These cygwin-excludes are: @code{_cygwin_dll_entry@@12},
2297 @code{_cygwin_crt0_common@@8}, @code{_cygwin_noncygwin_dll_entry@@12},
2298 @code{_fmode}, @code{_impure_ptr}, @code{cygwin_attach_dll},
2299 @code{cygwin_premain0}, @code{cygwin_premain1}, @code{cygwin_premain2},
2300 @code{cygwin_premain3}, and @code{environ}.
2301 [This option is specific to the i386 PE targeted port of the linker]
2303 @kindex --exclude-symbols
2304 @item --exclude-symbols @var{symbol},@var{symbol},...
2305 Specifies a list of symbols which should not be automatically
2306 exported. The symbol names may be delimited by commas or colons.
2307 [This option is specific to the i386 PE targeted port of the linker]
2309 @kindex --exclude-all-symbols
2310 @item --exclude-all-symbols
2311 Specifies no symbols should be automatically exported.
2312 [This option is specific to the i386 PE targeted port of the linker]
2314 @kindex --file-alignment
2315 @item --file-alignment
2316 Specify the file alignment. Sections in the file will always begin at
2317 file offsets which are multiples of this number. This defaults to
2319 [This option is specific to the i386 PE targeted port of the linker]
2323 @item --heap @var{reserve}
2324 @itemx --heap @var{reserve},@var{commit}
2325 Specify the number of bytes of memory to reserve (and optionally commit)
2326 to be used as heap for this program. The default is 1MB reserved, 4K
2328 [This option is specific to the i386 PE targeted port of the linker]
2331 @kindex --image-base
2332 @item --image-base @var{value}
2333 Use @var{value} as the base address of your program or dll. This is
2334 the lowest memory location that will be used when your program or dll
2335 is loaded. To reduce the need to relocate and improve performance of
2336 your dlls, each should have a unique base address and not overlap any
2337 other dlls. The default is 0x400000 for executables, and 0x10000000
2339 [This option is specific to the i386 PE targeted port of the linker]
2343 If given, the stdcall suffixes (@@@var{nn}) will be stripped from
2344 symbols before they are exported.
2345 [This option is specific to the i386 PE targeted port of the linker]
2347 @kindex --large-address-aware
2348 @item --large-address-aware
2349 If given, the appropriate bit in the ``Characteristics'' field of the COFF
2350 header is set to indicate that this executable supports virtual addresses
2351 greater than 2 gigabytes. This should be used in conjunction with the /3GB
2352 or /USERVA=@var{value} megabytes switch in the ``[operating systems]''
2353 section of the BOOT.INI. Otherwise, this bit has no effect.
2354 [This option is specific to PE targeted ports of the linker]
2356 @kindex --disable-large-address-aware
2357 @item --disable-large-address-aware
2358 Reverts the effect of a previous @samp{--large-address-aware} option.
2359 This is useful if @samp{--large-address-aware} is always set by the compiler
2360 driver (e.g. Cygwin gcc) and the executable does not support virtual
2361 addresses greater than 2 gigabytes.
2362 [This option is specific to PE targeted ports of the linker]
2364 @kindex --major-image-version
2365 @item --major-image-version @var{value}
2366 Sets the major number of the ``image version''. Defaults to 1.
2367 [This option is specific to the i386 PE targeted port of the linker]
2369 @kindex --major-os-version
2370 @item --major-os-version @var{value}
2371 Sets the major number of the ``os version''. Defaults to 4.
2372 [This option is specific to the i386 PE targeted port of the linker]
2374 @kindex --major-subsystem-version
2375 @item --major-subsystem-version @var{value}
2376 Sets the major number of the ``subsystem version''. Defaults to 4.
2377 [This option is specific to the i386 PE targeted port of the linker]
2379 @kindex --minor-image-version
2380 @item --minor-image-version @var{value}
2381 Sets the minor number of the ``image version''. Defaults to 0.
2382 [This option is specific to the i386 PE targeted port of the linker]
2384 @kindex --minor-os-version
2385 @item --minor-os-version @var{value}
2386 Sets the minor number of the ``os version''. Defaults to 0.
2387 [This option is specific to the i386 PE targeted port of the linker]
2389 @kindex --minor-subsystem-version
2390 @item --minor-subsystem-version @var{value}
2391 Sets the minor number of the ``subsystem version''. Defaults to 0.
2392 [This option is specific to the i386 PE targeted port of the linker]
2394 @cindex DEF files, creating
2395 @cindex DLLs, creating
2396 @kindex --output-def
2397 @item --output-def @var{file}
2398 The linker will create the file @var{file} which will contain a DEF
2399 file corresponding to the DLL the linker is generating. This DEF file
2400 (which should be called @code{*.def}) may be used to create an import
2401 library with @code{dlltool} or may be used as a reference to
2402 automatically or implicitly exported symbols.
2403 [This option is specific to the i386 PE targeted port of the linker]
2405 @cindex DLLs, creating
2406 @kindex --out-implib
2407 @item --out-implib @var{file}
2408 The linker will create the file @var{file} which will contain an
2409 import lib corresponding to the DLL the linker is generating. This
2410 import lib (which should be called @code{*.dll.a} or @code{*.a}
2411 may be used to link clients against the generated DLL; this behaviour
2412 makes it possible to skip a separate @code{dlltool} import library
2414 [This option is specific to the i386 PE targeted port of the linker]
2416 @kindex --enable-auto-image-base
2417 @item --enable-auto-image-base
2418 @itemx --enable-auto-image-base=@var{value}
2419 Automatically choose the image base for DLLs, optionally starting with base
2420 @var{value}, unless one is specified using the @code{--image-base} argument.
2421 By using a hash generated from the dllname to create unique image bases
2422 for each DLL, in-memory collisions and relocations which can delay program
2423 execution are avoided.
2424 [This option is specific to the i386 PE targeted port of the linker]
2426 @kindex --disable-auto-image-base
2427 @item --disable-auto-image-base
2428 Do not automatically generate a unique image base. If there is no
2429 user-specified image base (@code{--image-base}) then use the platform
2431 [This option is specific to the i386 PE targeted port of the linker]
2433 @cindex DLLs, linking to
2434 @kindex --dll-search-prefix
2435 @item --dll-search-prefix @var{string}
2436 When linking dynamically to a dll without an import library,
2437 search for @code{<string><basename>.dll} in preference to
2438 @code{lib<basename>.dll}. This behaviour allows easy distinction
2439 between DLLs built for the various "subplatforms": native, cygwin,
2440 uwin, pw, etc. For instance, cygwin DLLs typically use
2441 @code{--dll-search-prefix=cyg}.
2442 [This option is specific to the i386 PE targeted port of the linker]
2444 @kindex --enable-auto-import
2445 @item --enable-auto-import
2446 Do sophisticated linking of @code{_symbol} to @code{__imp__symbol} for
2447 DATA imports from DLLs, and create the necessary thunking symbols when
2448 building the import libraries with those DATA exports. Note: Use of the
2449 'auto-import' extension will cause the text section of the image file
2450 to be made writable. This does not conform to the PE-COFF format
2451 specification published by Microsoft.
2453 Note - use of the 'auto-import' extension will also cause read only
2454 data which would normally be placed into the .rdata section to be
2455 placed into the .data section instead. This is in order to work
2456 around a problem with consts that is described here:
2457 http://www.cygwin.com/ml/cygwin/2004-09/msg01101.html
2459 Using 'auto-import' generally will 'just work' -- but sometimes you may
2462 "variable '<var>' can't be auto-imported. Please read the
2463 documentation for ld's @code{--enable-auto-import} for details."
2465 This message occurs when some (sub)expression accesses an address
2466 ultimately given by the sum of two constants (Win32 import tables only
2467 allow one). Instances where this may occur include accesses to member
2468 fields of struct variables imported from a DLL, as well as using a
2469 constant index into an array variable imported from a DLL. Any
2470 multiword variable (arrays, structs, long long, etc) may trigger
2471 this error condition. However, regardless of the exact data type
2472 of the offending exported variable, ld will always detect it, issue
2473 the warning, and exit.
2475 There are several ways to address this difficulty, regardless of the
2476 data type of the exported variable:
2478 One way is to use --enable-runtime-pseudo-reloc switch. This leaves the task
2479 of adjusting references in your client code for runtime environment, so
2480 this method works only when runtime environment supports this feature.
2482 A second solution is to force one of the 'constants' to be a variable --
2483 that is, unknown and un-optimizable at compile time. For arrays,
2484 there are two possibilities: a) make the indexee (the array's address)
2485 a variable, or b) make the 'constant' index a variable. Thus:
2488 extern type extern_array[];
2490 @{ volatile type *t=extern_array; t[1] @}
2496 extern type extern_array[];
2498 @{ volatile int t=1; extern_array[t] @}
2501 For structs (and most other multiword data types) the only option
2502 is to make the struct itself (or the long long, or the ...) variable:
2505 extern struct s extern_struct;
2506 extern_struct.field -->
2507 @{ volatile struct s *t=&extern_struct; t->field @}
2513 extern long long extern_ll;
2515 @{ volatile long long * local_ll=&extern_ll; *local_ll @}
2518 A third method of dealing with this difficulty is to abandon
2519 'auto-import' for the offending symbol and mark it with
2520 @code{__declspec(dllimport)}. However, in practice that
2521 requires using compile-time #defines to indicate whether you are
2522 building a DLL, building client code that will link to the DLL, or
2523 merely building/linking to a static library. In making the choice
2524 between the various methods of resolving the 'direct address with
2525 constant offset' problem, you should consider typical real-world usage:
2533 void main(int argc, char **argv)@{
2534 printf("%d\n",arr[1]);
2544 void main(int argc, char **argv)@{
2545 /* This workaround is for win32 and cygwin; do not "optimize" */
2546 volatile int *parr = arr;
2547 printf("%d\n",parr[1]);
2554 /* Note: auto-export is assumed (no __declspec(dllexport)) */
2555 #if (defined(_WIN32) || defined(__CYGWIN__)) && \
2556 !(defined(FOO_BUILD_DLL) || defined(FOO_STATIC))
2557 #define FOO_IMPORT __declspec(dllimport)
2561 extern FOO_IMPORT int arr[];
2564 void main(int argc, char **argv)@{
2565 printf("%d\n",arr[1]);
2569 A fourth way to avoid this problem is to re-code your
2570 library to use a functional interface rather than a data interface
2571 for the offending variables (e.g. set_foo() and get_foo() accessor
2573 [This option is specific to the i386 PE targeted port of the linker]
2575 @kindex --disable-auto-import
2576 @item --disable-auto-import
2577 Do not attempt to do sophisticated linking of @code{_symbol} to
2578 @code{__imp__symbol} for DATA imports from DLLs.
2579 [This option is specific to the i386 PE targeted port of the linker]
2581 @kindex --enable-runtime-pseudo-reloc
2582 @item --enable-runtime-pseudo-reloc
2583 If your code contains expressions described in --enable-auto-import section,
2584 that is, DATA imports from DLL with non-zero offset, this switch will create
2585 a vector of 'runtime pseudo relocations' which can be used by runtime
2586 environment to adjust references to such data in your client code.
2587 [This option is specific to the i386 PE targeted port of the linker]
2589 @kindex --disable-runtime-pseudo-reloc
2590 @item --disable-runtime-pseudo-reloc
2591 Do not create pseudo relocations for non-zero offset DATA imports from
2593 [This option is specific to the i386 PE targeted port of the linker]
2595 @kindex --enable-extra-pe-debug
2596 @item --enable-extra-pe-debug
2597 Show additional debug info related to auto-import symbol thunking.
2598 [This option is specific to the i386 PE targeted port of the linker]
2600 @kindex --section-alignment
2601 @item --section-alignment
2602 Sets the section alignment. Sections in memory will always begin at
2603 addresses which are a multiple of this number. Defaults to 0x1000.
2604 [This option is specific to the i386 PE targeted port of the linker]
2608 @item --stack @var{reserve}
2609 @itemx --stack @var{reserve},@var{commit}
2610 Specify the number of bytes of memory to reserve (and optionally commit)
2611 to be used as stack for this program. The default is 2MB reserved, 4K
2613 [This option is specific to the i386 PE targeted port of the linker]
2616 @item --subsystem @var{which}
2617 @itemx --subsystem @var{which}:@var{major}
2618 @itemx --subsystem @var{which}:@var{major}.@var{minor}
2619 Specifies the subsystem under which your program will execute. The
2620 legal values for @var{which} are @code{native}, @code{windows},
2621 @code{console}, @code{posix}, and @code{xbox}. You may optionally set
2622 the subsystem version also. Numeric values are also accepted for
2624 [This option is specific to the i386 PE targeted port of the linker]
2626 The following options set flags in the @code{DllCharacteristics} field
2627 of the PE file header:
2628 [These options are specific to PE targeted ports of the linker]
2630 @kindex --dynamicbase
2632 The image base address may be relocated using address space layout
2633 randomization (ASLR). This feature was introduced with MS Windows
2634 Vista for i386 PE targets.
2636 @kindex --forceinteg
2638 Code integrity checks are enforced.
2642 The image is compatible with the Data Execution Prevention.
2643 This feature was introduced with MS Windows XP SP2 for i386 PE targets.
2645 @kindex --no-isolation
2646 @item --no-isolation
2647 Although the image understands isolation, do not isolate the image.
2651 The image does not use SEH. No SE handler may be called from
2656 Do not bind this image.
2660 The driver uses the MS Windows Driver Model.
2664 The image is Terminal Server aware.
2666 @kindex --insert-timestamp
2667 @item --insert-timestamp
2668 @itemx --no-insert-timestamp
2669 Insert a real timestamp into the image. This is the default behaviour
2670 as it matches legacy code and it means that the image will work with
2671 other, proprietary tools. The problem with this default is that it
2672 will result in slightly different images being produced each tiem the
2673 same sources are linked. The option @option{--no-insert-timestamp}
2674 can be used to insert a zero value for the timestamp, this ensuring
2675 that binaries produced from indentical sources will compare
2682 @subsection Options specific to C6X uClinux targets
2684 @c man begin OPTIONS
2686 The C6X uClinux target uses a binary format called DSBT to support shared
2687 libraries. Each shared library in the system needs to have a unique index;
2688 all executables use an index of 0.
2693 @item --dsbt-size @var{size}
2694 This option sets the number of entires in the DSBT of the current executable
2695 or shared library to @var{size}. The default is to create a table with 64
2698 @kindex --dsbt-index
2699 @item --dsbt-index @var{index}
2700 This option sets the DSBT index of the current executable or shared library
2701 to @var{index}. The default is 0, which is appropriate for generating
2702 executables. If a shared library is generated with a DSBT index of 0, the
2703 @code{R_C6000_DSBT_INDEX} relocs are copied into the output file.
2705 @kindex --no-merge-exidx-entries
2706 The @samp{--no-merge-exidx-entries} switch disables the merging of adjacent
2707 exidx entries in frame unwind info.
2715 @subsection Options specific to Motorola 68HC11 and 68HC12 targets
2717 @c man begin OPTIONS
2719 The 68HC11 and 68HC12 linkers support specific options to control the
2720 memory bank switching mapping and trampoline code generation.
2724 @kindex --no-trampoline
2725 @item --no-trampoline
2726 This option disables the generation of trampoline. By default a trampoline
2727 is generated for each far function which is called using a @code{jsr}
2728 instruction (this happens when a pointer to a far function is taken).
2730 @kindex --bank-window
2731 @item --bank-window @var{name}
2732 This option indicates to the linker the name of the memory region in
2733 the @samp{MEMORY} specification that describes the memory bank window.
2734 The definition of such region is then used by the linker to compute
2735 paging and addresses within the memory window.
2743 @subsection Options specific to Motorola 68K target
2745 @c man begin OPTIONS
2747 The following options are supported to control handling of GOT generation
2748 when linking for 68K targets.
2753 @item --got=@var{type}
2754 This option tells the linker which GOT generation scheme to use.
2755 @var{type} should be one of @samp{single}, @samp{negative},
2756 @samp{multigot} or @samp{target}. For more information refer to the
2757 Info entry for @file{ld}.
2765 @subsection Options specific to MIPS targets
2767 @c man begin OPTIONS
2769 The following options are supported to control microMIPS instruction
2770 generation when linking for MIPS targets.
2778 These options control the choice of microMIPS instructions used in code
2779 generated by the linker, such as that in the PLT or lazy binding stubs,
2780 or in relaxation. If @samp{--insn32} is used, then the linker only uses
2781 32-bit instruction encodings. By default or if @samp{--no-insn32} is
2782 used, all instruction encodings are used, including 16-bit ones where
2792 @section Environment Variables
2794 @c man begin ENVIRONMENT
2796 You can change the behaviour of @command{ld} with the environment variables
2797 @ifclear SingleFormat
2800 @code{LDEMULATION} and @code{COLLECT_NO_DEMANGLE}.
2802 @ifclear SingleFormat
2804 @cindex default input format
2805 @code{GNUTARGET} determines the input-file object format if you don't
2806 use @samp{-b} (or its synonym @samp{--format}). Its value should be one
2807 of the BFD names for an input format (@pxref{BFD}). If there is no
2808 @code{GNUTARGET} in the environment, @command{ld} uses the natural format
2809 of the target. If @code{GNUTARGET} is set to @code{default} then BFD
2810 attempts to discover the input format by examining binary input files;
2811 this method often succeeds, but there are potential ambiguities, since
2812 there is no method of ensuring that the magic number used to specify
2813 object-file formats is unique. However, the configuration procedure for
2814 BFD on each system places the conventional format for that system first
2815 in the search-list, so ambiguities are resolved in favor of convention.
2819 @cindex default emulation
2820 @cindex emulation, default
2821 @code{LDEMULATION} determines the default emulation if you don't use the
2822 @samp{-m} option. The emulation can affect various aspects of linker
2823 behaviour, particularly the default linker script. You can list the
2824 available emulations with the @samp{--verbose} or @samp{-V} options. If
2825 the @samp{-m} option is not used, and the @code{LDEMULATION} environment
2826 variable is not defined, the default emulation depends upon how the
2827 linker was configured.
2829 @kindex COLLECT_NO_DEMANGLE
2830 @cindex demangling, default
2831 Normally, the linker will default to demangling symbols. However, if
2832 @code{COLLECT_NO_DEMANGLE} is set in the environment, then it will
2833 default to not demangling symbols. This environment variable is used in
2834 a similar fashion by the @code{gcc} linker wrapper program. The default
2835 may be overridden by the @samp{--demangle} and @samp{--no-demangle}
2842 @chapter Linker Scripts
2845 @cindex linker scripts
2846 @cindex command files
2847 Every link is controlled by a @dfn{linker script}. This script is
2848 written in the linker command language.
2850 The main purpose of the linker script is to describe how the sections in
2851 the input files should be mapped into the output file, and to control
2852 the memory layout of the output file. Most linker scripts do nothing
2853 more than this. However, when necessary, the linker script can also
2854 direct the linker to perform many other operations, using the commands
2857 The linker always uses a linker script. If you do not supply one
2858 yourself, the linker will use a default script that is compiled into the
2859 linker executable. You can use the @samp{--verbose} command line option
2860 to display the default linker script. Certain command line options,
2861 such as @samp{-r} or @samp{-N}, will affect the default linker script.
2863 You may supply your own linker script by using the @samp{-T} command
2864 line option. When you do this, your linker script will replace the
2865 default linker script.
2867 You may also use linker scripts implicitly by naming them as input files
2868 to the linker, as though they were files to be linked. @xref{Implicit
2872 * Basic Script Concepts:: Basic Linker Script Concepts
2873 * Script Format:: Linker Script Format
2874 * Simple Example:: Simple Linker Script Example
2875 * Simple Commands:: Simple Linker Script Commands
2876 * Assignments:: Assigning Values to Symbols
2877 * SECTIONS:: SECTIONS Command
2878 * MEMORY:: MEMORY Command
2879 * PHDRS:: PHDRS Command
2880 * VERSION:: VERSION Command
2881 * Expressions:: Expressions in Linker Scripts
2882 * Implicit Linker Scripts:: Implicit Linker Scripts
2885 @node Basic Script Concepts
2886 @section Basic Linker Script Concepts
2887 @cindex linker script concepts
2888 We need to define some basic concepts and vocabulary in order to
2889 describe the linker script language.
2891 The linker combines input files into a single output file. The output
2892 file and each input file are in a special data format known as an
2893 @dfn{object file format}. Each file is called an @dfn{object file}.
2894 The output file is often called an @dfn{executable}, but for our
2895 purposes we will also call it an object file. Each object file has,
2896 among other things, a list of @dfn{sections}. We sometimes refer to a
2897 section in an input file as an @dfn{input section}; similarly, a section
2898 in the output file is an @dfn{output section}.
2900 Each section in an object file has a name and a size. Most sections
2901 also have an associated block of data, known as the @dfn{section
2902 contents}. A section may be marked as @dfn{loadable}, which means that
2903 the contents should be loaded into memory when the output file is run.
2904 A section with no contents may be @dfn{allocatable}, which means that an
2905 area in memory should be set aside, but nothing in particular should be
2906 loaded there (in some cases this memory must be zeroed out). A section
2907 which is neither loadable nor allocatable typically contains some sort
2908 of debugging information.
2910 Every loadable or allocatable output section has two addresses. The
2911 first is the @dfn{VMA}, or virtual memory address. This is the address
2912 the section will have when the output file is run. The second is the
2913 @dfn{LMA}, or load memory address. This is the address at which the
2914 section will be loaded. In most cases the two addresses will be the
2915 same. An example of when they might be different is when a data section
2916 is loaded into ROM, and then copied into RAM when the program starts up
2917 (this technique is often used to initialize global variables in a ROM
2918 based system). In this case the ROM address would be the LMA, and the
2919 RAM address would be the VMA.
2921 You can see the sections in an object file by using the @code{objdump}
2922 program with the @samp{-h} option.
2924 Every object file also has a list of @dfn{symbols}, known as the
2925 @dfn{symbol table}. A symbol may be defined or undefined. Each symbol
2926 has a name, and each defined symbol has an address, among other
2927 information. If you compile a C or C++ program into an object file, you
2928 will get a defined symbol for every defined function and global or
2929 static variable. Every undefined function or global variable which is
2930 referenced in the input file will become an undefined symbol.
2932 You can see the symbols in an object file by using the @code{nm}
2933 program, or by using the @code{objdump} program with the @samp{-t}
2937 @section Linker Script Format
2938 @cindex linker script format
2939 Linker scripts are text files.
2941 You write a linker script as a series of commands. Each command is
2942 either a keyword, possibly followed by arguments, or an assignment to a
2943 symbol. You may separate commands using semicolons. Whitespace is
2946 Strings such as file or format names can normally be entered directly.
2947 If the file name contains a character such as a comma which would
2948 otherwise serve to separate file names, you may put the file name in
2949 double quotes. There is no way to use a double quote character in a
2952 You may include comments in linker scripts just as in C, delimited by
2953 @samp{/*} and @samp{*/}. As in C, comments are syntactically equivalent
2956 @node Simple Example
2957 @section Simple Linker Script Example
2958 @cindex linker script example
2959 @cindex example of linker script
2960 Many linker scripts are fairly simple.
2962 The simplest possible linker script has just one command:
2963 @samp{SECTIONS}. You use the @samp{SECTIONS} command to describe the
2964 memory layout of the output file.
2966 The @samp{SECTIONS} command is a powerful command. Here we will
2967 describe a simple use of it. Let's assume your program consists only of
2968 code, initialized data, and uninitialized data. These will be in the
2969 @samp{.text}, @samp{.data}, and @samp{.bss} sections, respectively.
2970 Let's assume further that these are the only sections which appear in
2973 For this example, let's say that the code should be loaded at address
2974 0x10000, and that the data should start at address 0x8000000. Here is a
2975 linker script which will do that:
2980 .text : @{ *(.text) @}
2982 .data : @{ *(.data) @}
2983 .bss : @{ *(.bss) @}
2987 You write the @samp{SECTIONS} command as the keyword @samp{SECTIONS},
2988 followed by a series of symbol assignments and output section
2989 descriptions enclosed in curly braces.
2991 The first line inside the @samp{SECTIONS} command of the above example
2992 sets the value of the special symbol @samp{.}, which is the location
2993 counter. If you do not specify the address of an output section in some
2994 other way (other ways are described later), the address is set from the
2995 current value of the location counter. The location counter is then
2996 incremented by the size of the output section. At the start of the
2997 @samp{SECTIONS} command, the location counter has the value @samp{0}.
2999 The second line defines an output section, @samp{.text}. The colon is
3000 required syntax which may be ignored for now. Within the curly braces
3001 after the output section name, you list the names of the input sections
3002 which should be placed into this output section. The @samp{*} is a
3003 wildcard which matches any file name. The expression @samp{*(.text)}
3004 means all @samp{.text} input sections in all input files.
3006 Since the location counter is @samp{0x10000} when the output section
3007 @samp{.text} is defined, the linker will set the address of the
3008 @samp{.text} section in the output file to be @samp{0x10000}.
3010 The remaining lines define the @samp{.data} and @samp{.bss} sections in
3011 the output file. The linker will place the @samp{.data} output section
3012 at address @samp{0x8000000}. After the linker places the @samp{.data}
3013 output section, the value of the location counter will be
3014 @samp{0x8000000} plus the size of the @samp{.data} output section. The
3015 effect is that the linker will place the @samp{.bss} output section
3016 immediately after the @samp{.data} output section in memory.
3018 The linker will ensure that each output section has the required
3019 alignment, by increasing the location counter if necessary. In this
3020 example, the specified addresses for the @samp{.text} and @samp{.data}
3021 sections will probably satisfy any alignment constraints, but the linker
3022 may have to create a small gap between the @samp{.data} and @samp{.bss}
3025 That's it! That's a simple and complete linker script.
3027 @node Simple Commands
3028 @section Simple Linker Script Commands
3029 @cindex linker script simple commands
3030 In this section we describe the simple linker script commands.
3033 * Entry Point:: Setting the entry point
3034 * File Commands:: Commands dealing with files
3035 @ifclear SingleFormat
3036 * Format Commands:: Commands dealing with object file formats
3039 * REGION_ALIAS:: Assign alias names to memory regions
3040 * Miscellaneous Commands:: Other linker script commands
3044 @subsection Setting the Entry Point
3045 @kindex ENTRY(@var{symbol})
3046 @cindex start of execution
3047 @cindex first instruction
3049 The first instruction to execute in a program is called the @dfn{entry
3050 point}. You can use the @code{ENTRY} linker script command to set the
3051 entry point. The argument is a symbol name:
3056 There are several ways to set the entry point. The linker will set the
3057 entry point by trying each of the following methods in order, and
3058 stopping when one of them succeeds:
3061 the @samp{-e} @var{entry} command-line option;
3063 the @code{ENTRY(@var{symbol})} command in a linker script;
3065 the value of a target specific symbol, if it is defined; For many
3066 targets this is @code{start}, but PE and BeOS based systems for example
3067 check a list of possible entry symbols, matching the first one found.
3069 the address of the first byte of the @samp{.text} section, if present;
3071 The address @code{0}.
3075 @subsection Commands Dealing with Files
3076 @cindex linker script file commands
3077 Several linker script commands deal with files.
3080 @item INCLUDE @var{filename}
3081 @kindex INCLUDE @var{filename}
3082 @cindex including a linker script
3083 Include the linker script @var{filename} at this point. The file will
3084 be searched for in the current directory, and in any directory specified
3085 with the @option{-L} option. You can nest calls to @code{INCLUDE} up to
3088 You can place @code{INCLUDE} directives at the top level, in @code{MEMORY} or
3089 @code{SECTIONS} commands, or in output section descriptions.
3091 @item INPUT(@var{file}, @var{file}, @dots{})
3092 @itemx INPUT(@var{file} @var{file} @dots{})
3093 @kindex INPUT(@var{files})
3094 @cindex input files in linker scripts
3095 @cindex input object files in linker scripts
3096 @cindex linker script input object files
3097 The @code{INPUT} command directs the linker to include the named files
3098 in the link, as though they were named on the command line.
3100 For example, if you always want to include @file{subr.o} any time you do
3101 a link, but you can't be bothered to put it on every link command line,
3102 then you can put @samp{INPUT (subr.o)} in your linker script.
3104 In fact, if you like, you can list all of your input files in the linker
3105 script, and then invoke the linker with nothing but a @samp{-T} option.
3107 In case a @dfn{sysroot prefix} is configured, and the filename starts
3108 with the @samp{/} character, and the script being processed was
3109 located inside the @dfn{sysroot prefix}, the filename will be looked
3110 for in the @dfn{sysroot prefix}. Otherwise, the linker will try to
3111 open the file in the current directory. If it is not found, the
3112 linker will search through the archive library search path. See the
3113 description of @samp{-L} in @ref{Options,,Command Line Options}.
3115 If you use @samp{INPUT (-l@var{file})}, @command{ld} will transform the
3116 name to @code{lib@var{file}.a}, as with the command line argument
3119 When you use the @code{INPUT} command in an implicit linker script, the
3120 files will be included in the link at the point at which the linker
3121 script file is included. This can affect archive searching.
3123 @item GROUP(@var{file}, @var{file}, @dots{})
3124 @itemx GROUP(@var{file} @var{file} @dots{})
3125 @kindex GROUP(@var{files})
3126 @cindex grouping input files
3127 The @code{GROUP} command is like @code{INPUT}, except that the named
3128 files should all be archives, and they are searched repeatedly until no
3129 new undefined references are created. See the description of @samp{-(}
3130 in @ref{Options,,Command Line Options}.
3132 @item AS_NEEDED(@var{file}, @var{file}, @dots{})
3133 @itemx AS_NEEDED(@var{file} @var{file} @dots{})
3134 @kindex AS_NEEDED(@var{files})
3135 This construct can appear only inside of the @code{INPUT} or @code{GROUP}
3136 commands, among other filenames. The files listed will be handled
3137 as if they appear directly in the @code{INPUT} or @code{GROUP} commands,
3138 with the exception of ELF shared libraries, that will be added only
3139 when they are actually needed. This construct essentially enables
3140 @option{--as-needed} option for all the files listed inside of it
3141 and restores previous @option{--as-needed} resp. @option{--no-as-needed}
3144 @item OUTPUT(@var{filename})
3145 @kindex OUTPUT(@var{filename})
3146 @cindex output file name in linker script
3147 The @code{OUTPUT} command names the output file. Using
3148 @code{OUTPUT(@var{filename})} in the linker script is exactly like using
3149 @samp{-o @var{filename}} on the command line (@pxref{Options,,Command
3150 Line Options}). If both are used, the command line option takes
3153 You can use the @code{OUTPUT} command to define a default name for the
3154 output file other than the usual default of @file{a.out}.
3156 @item SEARCH_DIR(@var{path})
3157 @kindex SEARCH_DIR(@var{path})
3158 @cindex library search path in linker script
3159 @cindex archive search path in linker script
3160 @cindex search path in linker script
3161 The @code{SEARCH_DIR} command adds @var{path} to the list of paths where
3162 @command{ld} looks for archive libraries. Using
3163 @code{SEARCH_DIR(@var{path})} is exactly like using @samp{-L @var{path}}
3164 on the command line (@pxref{Options,,Command Line Options}). If both
3165 are used, then the linker will search both paths. Paths specified using
3166 the command line option are searched first.
3168 @item STARTUP(@var{filename})
3169 @kindex STARTUP(@var{filename})
3170 @cindex first input file
3171 The @code{STARTUP} command is just like the @code{INPUT} command, except
3172 that @var{filename} will become the first input file to be linked, as
3173 though it were specified first on the command line. This may be useful
3174 when using a system in which the entry point is always the start of the
3178 @ifclear SingleFormat
3179 @node Format Commands
3180 @subsection Commands Dealing with Object File Formats
3181 A couple of linker script commands deal with object file formats.
3184 @item OUTPUT_FORMAT(@var{bfdname})
3185 @itemx OUTPUT_FORMAT(@var{default}, @var{big}, @var{little})
3186 @kindex OUTPUT_FORMAT(@var{bfdname})
3187 @cindex output file format in linker script
3188 The @code{OUTPUT_FORMAT} command names the BFD format to use for the
3189 output file (@pxref{BFD}). Using @code{OUTPUT_FORMAT(@var{bfdname})} is
3190 exactly like using @samp{--oformat @var{bfdname}} on the command line
3191 (@pxref{Options,,Command Line Options}). If both are used, the command
3192 line option takes precedence.
3194 You can use @code{OUTPUT_FORMAT} with three arguments to use different
3195 formats based on the @samp{-EB} and @samp{-EL} command line options.
3196 This permits the linker script to set the output format based on the
3199 If neither @samp{-EB} nor @samp{-EL} are used, then the output format
3200 will be the first argument, @var{default}. If @samp{-EB} is used, the
3201 output format will be the second argument, @var{big}. If @samp{-EL} is
3202 used, the output format will be the third argument, @var{little}.
3204 For example, the default linker script for the MIPS ELF target uses this
3207 OUTPUT_FORMAT(elf32-bigmips, elf32-bigmips, elf32-littlemips)
3209 This says that the default format for the output file is
3210 @samp{elf32-bigmips}, but if the user uses the @samp{-EL} command line
3211 option, the output file will be created in the @samp{elf32-littlemips}
3214 @item TARGET(@var{bfdname})
3215 @kindex TARGET(@var{bfdname})
3216 @cindex input file format in linker script
3217 The @code{TARGET} command names the BFD format to use when reading input
3218 files. It affects subsequent @code{INPUT} and @code{GROUP} commands.
3219 This command is like using @samp{-b @var{bfdname}} on the command line
3220 (@pxref{Options,,Command Line Options}). If the @code{TARGET} command
3221 is used but @code{OUTPUT_FORMAT} is not, then the last @code{TARGET}
3222 command is also used to set the format for the output file. @xref{BFD}.
3227 @subsection Assign alias names to memory regions
3228 @kindex REGION_ALIAS(@var{alias}, @var{region})
3229 @cindex region alias
3230 @cindex region names
3232 Alias names can be added to existing memory regions created with the
3233 @ref{MEMORY} command. Each name corresponds to at most one memory region.
3236 REGION_ALIAS(@var{alias}, @var{region})
3239 The @code{REGION_ALIAS} function creates an alias name @var{alias} for the
3240 memory region @var{region}. This allows a flexible mapping of output sections
3241 to memory regions. An example follows.
3243 Suppose we have an application for embedded systems which come with various
3244 memory storage devices. All have a general purpose, volatile memory @code{RAM}
3245 that allows code execution or data storage. Some may have a read-only,
3246 non-volatile memory @code{ROM} that allows code execution and read-only data
3247 access. The last variant is a read-only, non-volatile memory @code{ROM2} with
3248 read-only data access and no code execution capability. We have four output
3253 @code{.text} program code;
3255 @code{.rodata} read-only data;
3257 @code{.data} read-write initialized data;
3259 @code{.bss} read-write zero initialized data.
3262 The goal is to provide a linker command file that contains a system independent
3263 part defining the output sections and a system dependent part mapping the
3264 output sections to the memory regions available on the system. Our embedded
3265 systems come with three different memory setups @code{A}, @code{B} and
3267 @multitable @columnfractions .25 .25 .25 .25
3268 @item Section @tab Variant A @tab Variant B @tab Variant C
3269 @item .text @tab RAM @tab ROM @tab ROM
3270 @item .rodata @tab RAM @tab ROM @tab ROM2
3271 @item .data @tab RAM @tab RAM/ROM @tab RAM/ROM2
3272 @item .bss @tab RAM @tab RAM @tab RAM
3274 The notation @code{RAM/ROM} or @code{RAM/ROM2} means that this section is
3275 loaded into region @code{ROM} or @code{ROM2} respectively. Please note that
3276 the load address of the @code{.data} section starts in all three variants at
3277 the end of the @code{.rodata} section.
3279 The base linker script that deals with the output sections follows. It
3280 includes the system dependent @code{linkcmds.memory} file that describes the
3283 INCLUDE linkcmds.memory
3296 .data : AT (rodata_end)
3301 data_size = SIZEOF(.data);
3302 data_load_start = LOADADDR(.data);
3310 Now we need three different @code{linkcmds.memory} files to define memory
3311 regions and alias names. The content of @code{linkcmds.memory} for the three
3312 variants @code{A}, @code{B} and @code{C}:
3315 Here everything goes into the @code{RAM}.
3319 RAM : ORIGIN = 0, LENGTH = 4M
3322 REGION_ALIAS("REGION_TEXT", RAM);
3323 REGION_ALIAS("REGION_RODATA", RAM);
3324 REGION_ALIAS("REGION_DATA", RAM);
3325 REGION_ALIAS("REGION_BSS", RAM);
3328 Program code and read-only data go into the @code{ROM}. Read-write data goes
3329 into the @code{RAM}. An image of the initialized data is loaded into the
3330 @code{ROM} and will be copied during system start into the @code{RAM}.
3334 ROM : ORIGIN = 0, LENGTH = 3M
3335 RAM : ORIGIN = 0x10000000, LENGTH = 1M
3338 REGION_ALIAS("REGION_TEXT", ROM);
3339 REGION_ALIAS("REGION_RODATA", ROM);
3340 REGION_ALIAS("REGION_DATA", RAM);
3341 REGION_ALIAS("REGION_BSS", RAM);
3344 Program code goes into the @code{ROM}. Read-only data goes into the
3345 @code{ROM2}. Read-write data goes into the @code{RAM}. An image of the
3346 initialized data is loaded into the @code{ROM2} and will be copied during
3347 system start into the @code{RAM}.
3351 ROM : ORIGIN = 0, LENGTH = 2M
3352 ROM2 : ORIGIN = 0x10000000, LENGTH = 1M
3353 RAM : ORIGIN = 0x20000000, LENGTH = 1M
3356 REGION_ALIAS("REGION_TEXT", ROM);
3357 REGION_ALIAS("REGION_RODATA", ROM2);
3358 REGION_ALIAS("REGION_DATA", RAM);
3359 REGION_ALIAS("REGION_BSS", RAM);
3363 It is possible to write a common system initialization routine to copy the
3364 @code{.data} section from @code{ROM} or @code{ROM2} into the @code{RAM} if
3369 extern char data_start [];
3370 extern char data_size [];
3371 extern char data_load_start [];
3373 void copy_data(void)
3375 if (data_start != data_load_start)
3377 memcpy(data_start, data_load_start, (size_t) data_size);
3382 @node Miscellaneous Commands
3383 @subsection Other Linker Script Commands
3384 There are a few other linker scripts commands.
3387 @item ASSERT(@var{exp}, @var{message})
3389 @cindex assertion in linker script
3390 Ensure that @var{exp} is non-zero. If it is zero, then exit the linker
3391 with an error code, and print @var{message}.
3393 @item EXTERN(@var{symbol} @var{symbol} @dots{})
3395 @cindex undefined symbol in linker script
3396 Force @var{symbol} to be entered in the output file as an undefined
3397 symbol. Doing this may, for example, trigger linking of additional
3398 modules from standard libraries. You may list several @var{symbol}s for
3399 each @code{EXTERN}, and you may use @code{EXTERN} multiple times. This
3400 command has the same effect as the @samp{-u} command-line option.
3402 @item FORCE_COMMON_ALLOCATION
3403 @kindex FORCE_COMMON_ALLOCATION
3404 @cindex common allocation in linker script
3405 This command has the same effect as the @samp{-d} command-line option:
3406 to make @command{ld} assign space to common symbols even if a relocatable
3407 output file is specified (@samp{-r}).
3409 @item INHIBIT_COMMON_ALLOCATION
3410 @kindex INHIBIT_COMMON_ALLOCATION
3411 @cindex common allocation in linker script
3412 This command has the same effect as the @samp{--no-define-common}
3413 command-line option: to make @code{ld} omit the assignment of addresses
3414 to common symbols even for a non-relocatable output file.
3416 @item INSERT [ AFTER | BEFORE ] @var{output_section}
3418 @cindex insert user script into default script
3419 This command is typically used in a script specified by @samp{-T} to
3420 augment the default @code{SECTIONS} with, for example, overlays. It
3421 inserts all prior linker script statements after (or before)
3422 @var{output_section}, and also causes @samp{-T} to not override the
3423 default linker script. The exact insertion point is as for orphan
3424 sections. @xref{Location Counter}. The insertion happens after the
3425 linker has mapped input sections to output sections. Prior to the
3426 insertion, since @samp{-T} scripts are parsed before the default
3427 linker script, statements in the @samp{-T} script occur before the
3428 default linker script statements in the internal linker representation
3429 of the script. In particular, input section assignments will be made
3430 to @samp{-T} output sections before those in the default script. Here
3431 is an example of how a @samp{-T} script using @code{INSERT} might look:
3438 .ov1 @{ ov1*(.text) @}
3439 .ov2 @{ ov2*(.text) @}
3445 @item NOCROSSREFS(@var{section} @var{section} @dots{})
3446 @kindex NOCROSSREFS(@var{sections})
3447 @cindex cross references
3448 This command may be used to tell @command{ld} to issue an error about any
3449 references among certain output sections.
3451 In certain types of programs, particularly on embedded systems when
3452 using overlays, when one section is loaded into memory, another section
3453 will not be. Any direct references between the two sections would be
3454 errors. For example, it would be an error if code in one section called
3455 a function defined in the other section.
3457 The @code{NOCROSSREFS} command takes a list of output section names. If
3458 @command{ld} detects any cross references between the sections, it reports
3459 an error and returns a non-zero exit status. Note that the
3460 @code{NOCROSSREFS} command uses output section names, not input section
3463 @ifclear SingleFormat
3464 @item OUTPUT_ARCH(@var{bfdarch})
3465 @kindex OUTPUT_ARCH(@var{bfdarch})
3466 @cindex machine architecture
3467 @cindex architecture
3468 Specify a particular output machine architecture. The argument is one
3469 of the names used by the BFD library (@pxref{BFD}). You can see the
3470 architecture of an object file by using the @code{objdump} program with
3471 the @samp{-f} option.
3474 @item LD_FEATURE(@var{string})
3475 @kindex LD_FEATURE(@var{string})
3476 This command may be used to modify @command{ld} behavior. If
3477 @var{string} is @code{"SANE_EXPR"} then absolute symbols and numbers
3478 in a script are simply treated as numbers everywhere.
3479 @xref{Expression Section}.
3483 @section Assigning Values to Symbols
3484 @cindex assignment in scripts
3485 @cindex symbol definition, scripts
3486 @cindex variables, defining
3487 You may assign a value to a symbol in a linker script. This will define
3488 the symbol and place it into the symbol table with a global scope.
3491 * Simple Assignments:: Simple Assignments
3494 * PROVIDE_HIDDEN:: PROVIDE_HIDDEN
3495 * Source Code Reference:: How to use a linker script defined symbol in source code
3498 @node Simple Assignments
3499 @subsection Simple Assignments
3501 You may assign to a symbol using any of the C assignment operators:
3504 @item @var{symbol} = @var{expression} ;
3505 @itemx @var{symbol} += @var{expression} ;
3506 @itemx @var{symbol} -= @var{expression} ;
3507 @itemx @var{symbol} *= @var{expression} ;
3508 @itemx @var{symbol} /= @var{expression} ;
3509 @itemx @var{symbol} <<= @var{expression} ;
3510 @itemx @var{symbol} >>= @var{expression} ;
3511 @itemx @var{symbol} &= @var{expression} ;
3512 @itemx @var{symbol} |= @var{expression} ;
3515 The first case will define @var{symbol} to the value of
3516 @var{expression}. In the other cases, @var{symbol} must already be
3517 defined, and the value will be adjusted accordingly.
3519 The special symbol name @samp{.} indicates the location counter. You
3520 may only use this within a @code{SECTIONS} command. @xref{Location Counter}.
3522 The semicolon after @var{expression} is required.
3524 Expressions are defined below; see @ref{Expressions}.
3526 You may write symbol assignments as commands in their own right, or as
3527 statements within a @code{SECTIONS} command, or as part of an output
3528 section description in a @code{SECTIONS} command.
3530 The section of the symbol will be set from the section of the
3531 expression; for more information, see @ref{Expression Section}.
3533 Here is an example showing the three different places that symbol
3534 assignments may be used:
3545 _bdata = (. + 3) & ~ 3;
3546 .data : @{ *(.data) @}
3550 In this example, the symbol @samp{floating_point} will be defined as
3551 zero. The symbol @samp{_etext} will be defined as the address following
3552 the last @samp{.text} input section. The symbol @samp{_bdata} will be
3553 defined as the address following the @samp{.text} output section aligned
3554 upward to a 4 byte boundary.
3559 For ELF targeted ports, define a symbol that will be hidden and won't be
3560 exported. The syntax is @code{HIDDEN(@var{symbol} = @var{expression})}.
3562 Here is the example from @ref{Simple Assignments}, rewritten to use
3566 HIDDEN(floating_point = 0);
3574 HIDDEN(_bdata = (. + 3) & ~ 3);
3575 .data : @{ *(.data) @}
3579 In this case none of the three symbols will be visible outside this module.
3584 In some cases, it is desirable for a linker script to define a symbol
3585 only if it is referenced and is not defined by any object included in
3586 the link. For example, traditional linkers defined the symbol
3587 @samp{etext}. However, ANSI C requires that the user be able to use
3588 @samp{etext} as a function name without encountering an error. The
3589 @code{PROVIDE} keyword may be used to define a symbol, such as
3590 @samp{etext}, only if it is referenced but not defined. The syntax is
3591 @code{PROVIDE(@var{symbol} = @var{expression})}.
3593 Here is an example of using @code{PROVIDE} to define @samp{etext}:
3606 In this example, if the program defines @samp{_etext} (with a leading
3607 underscore), the linker will give a multiple definition error. If, on
3608 the other hand, the program defines @samp{etext} (with no leading
3609 underscore), the linker will silently use the definition in the program.
3610 If the program references @samp{etext} but does not define it, the
3611 linker will use the definition in the linker script.
3613 @node PROVIDE_HIDDEN
3614 @subsection PROVIDE_HIDDEN
3615 @cindex PROVIDE_HIDDEN
3616 Similar to @code{PROVIDE}. For ELF targeted ports, the symbol will be
3617 hidden and won't be exported.
3619 @node Source Code Reference
3620 @subsection Source Code Reference
3622 Accessing a linker script defined variable from source code is not
3623 intuitive. In particular a linker script symbol is not equivalent to
3624 a variable declaration in a high level language, it is instead a
3625 symbol that does not have a value.
3627 Before going further, it is important to note that compilers often
3628 transform names in the source code into different names when they are
3629 stored in the symbol table. For example, Fortran compilers commonly
3630 prepend or append an underscore, and C++ performs extensive @samp{name
3631 mangling}. Therefore there might be a discrepancy between the name
3632 of a variable as it is used in source code and the name of the same
3633 variable as it is defined in a linker script. For example in C a
3634 linker script variable might be referred to as:
3640 But in the linker script it might be defined as:
3646 In the remaining examples however it is assumed that no name
3647 transformation has taken place.
3649 When a symbol is declared in a high level language such as C, two
3650 things happen. The first is that the compiler reserves enough space
3651 in the program's memory to hold the @emph{value} of the symbol. The
3652 second is that the compiler creates an entry in the program's symbol
3653 table which holds the symbol's @emph{address}. ie the symbol table
3654 contains the address of the block of memory holding the symbol's
3655 value. So for example the following C declaration, at file scope:
3661 creates an entry called @samp{foo} in the symbol table. This entry
3662 holds the address of an @samp{int} sized block of memory where the
3663 number 1000 is initially stored.
3665 When a program references a symbol the compiler generates code that
3666 first accesses the symbol table to find the address of the symbol's
3667 memory block and then code to read the value from that memory block.
3674 looks up the symbol @samp{foo} in the symbol table, gets the address
3675 associated with this symbol and then writes the value 1 into that
3682 looks up the symbol @samp{foo} in the symbol table, gets its address
3683 and then copies this address into the block of memory associated with
3684 the variable @samp{a}.
3686 Linker scripts symbol declarations, by contrast, create an entry in
3687 the symbol table but do not assign any memory to them. Thus they are
3688 an address without a value. So for example the linker script definition:
3694 creates an entry in the symbol table called @samp{foo} which holds
3695 the address of memory location 1000, but nothing special is stored at
3696 address 1000. This means that you cannot access the @emph{value} of a
3697 linker script defined symbol - it has no value - all you can do is
3698 access the @emph{address} of a linker script defined symbol.
3700 Hence when you are using a linker script defined symbol in source code
3701 you should always take the address of the symbol, and never attempt to
3702 use its value. For example suppose you want to copy the contents of a
3703 section of memory called .ROM into a section called .FLASH and the
3704 linker script contains these declarations:
3708 start_of_ROM = .ROM;
3709 end_of_ROM = .ROM + sizeof (.ROM) - 1;
3710 start_of_FLASH = .FLASH;
3714 Then the C source code to perform the copy would be:
3718 extern char start_of_ROM, end_of_ROM, start_of_FLASH;
3720 memcpy (& start_of_FLASH, & start_of_ROM, & end_of_ROM - & start_of_ROM);
3724 Note the use of the @samp{&} operators. These are correct.
3727 @section SECTIONS Command
3729 The @code{SECTIONS} command tells the linker how to map input sections
3730 into output sections, and how to place the output sections in memory.
3732 The format of the @code{SECTIONS} command is:
3736 @var{sections-command}
3737 @var{sections-command}
3742 Each @var{sections-command} may of be one of the following:
3746 an @code{ENTRY} command (@pxref{Entry Point,,Entry command})
3748 a symbol assignment (@pxref{Assignments})
3750 an output section description
3752 an overlay description
3755 The @code{ENTRY} command and symbol assignments are permitted inside the
3756 @code{SECTIONS} command for convenience in using the location counter in
3757 those commands. This can also make the linker script easier to
3758 understand because you can use those commands at meaningful points in
3759 the layout of the output file.
3761 Output section descriptions and overlay descriptions are described
3764 If you do not use a @code{SECTIONS} command in your linker script, the
3765 linker will place each input section into an identically named output
3766 section in the order that the sections are first encountered in the
3767 input files. If all input sections are present in the first file, for
3768 example, the order of sections in the output file will match the order
3769 in the first input file. The first section will be at address zero.
3772 * Output Section Description:: Output section description
3773 * Output Section Name:: Output section name
3774 * Output Section Address:: Output section address
3775 * Input Section:: Input section description
3776 * Output Section Data:: Output section data
3777 * Output Section Keywords:: Output section keywords
3778 * Output Section Discarding:: Output section discarding
3779 * Output Section Attributes:: Output section attributes
3780 * Overlay Description:: Overlay description
3783 @node Output Section Description
3784 @subsection Output Section Description
3785 The full description of an output section looks like this:
3788 @var{section} [@var{address}] [(@var{type})] :
3790 [ALIGN(@var{section_align}) | ALIGN_WITH_INPUT]
3791 [SUBALIGN(@var{subsection_align})]
3794 @var{output-section-command}
3795 @var{output-section-command}
3797 @} [>@var{region}] [AT>@var{lma_region}] [:@var{phdr} :@var{phdr} @dots{}] [=@var{fillexp}] [,]
3801 Most output sections do not use most of the optional section attributes.
3803 The whitespace around @var{section} is required, so that the section
3804 name is unambiguous. The colon and the curly braces are also required.
3805 The comma at the end may be required if a @var{fillexp} is used and
3806 the next @var{sections-command} looks like a continuation of the expression.
3807 The line breaks and other white space are optional.
3809 Each @var{output-section-command} may be one of the following:
3813 a symbol assignment (@pxref{Assignments})
3815 an input section description (@pxref{Input Section})
3817 data values to include directly (@pxref{Output Section Data})
3819 a special output section keyword (@pxref{Output Section Keywords})
3822 @node Output Section Name
3823 @subsection Output Section Name
3824 @cindex name, section
3825 @cindex section name
3826 The name of the output section is @var{section}. @var{section} must
3827 meet the constraints of your output format. In formats which only
3828 support a limited number of sections, such as @code{a.out}, the name
3829 must be one of the names supported by the format (@code{a.out}, for
3830 example, allows only @samp{.text}, @samp{.data} or @samp{.bss}). If the
3831 output format supports any number of sections, but with numbers and not
3832 names (as is the case for Oasys), the name should be supplied as a
3833 quoted numeric string. A section name may consist of any sequence of
3834 characters, but a name which contains any unusual characters such as
3835 commas must be quoted.
3837 The output section name @samp{/DISCARD/} is special; @ref{Output Section
3840 @node Output Section Address
3841 @subsection Output Section Address
3842 @cindex address, section
3843 @cindex section address
3844 The @var{address} is an expression for the VMA (the virtual memory
3845 address) of the output section. This address is optional, but if it
3846 is provided then the output address will be set exactly as specified.
3848 If the output address is not specified then one will be chosen for the
3849 section, based on the heuristic below. This address will be adjusted
3850 to fit the alignment requirement of the output section. The
3851 alignment requirement is the strictest alignment of any input section
3852 contained within the output section.
3854 The output section address heuristic is as follows:
3858 If an output memory @var{region} is set for the section then it
3859 is added to this region and its address will be the next free address
3863 If the MEMORY command has been used to create a list of memory
3864 regions then the first region which has attributes compatible with the
3865 section is selected to contain it. The section's output address will
3866 be the next free address in that region; @ref{MEMORY}.
3869 If no memory regions were specified, or none match the section then
3870 the output address will be based on the current value of the location
3878 .text . : @{ *(.text) @}
3885 .text : @{ *(.text) @}
3889 are subtly different. The first will set the address of the
3890 @samp{.text} output section to the current value of the location
3891 counter. The second will set it to the current value of the location
3892 counter aligned to the strictest alignment of any of the @samp{.text}
3895 The @var{address} may be an arbitrary expression; @ref{Expressions}.
3896 For example, if you want to align the section on a 0x10 byte boundary,
3897 so that the lowest four bits of the section address are zero, you could
3898 do something like this:
3900 .text ALIGN(0x10) : @{ *(.text) @}
3903 This works because @code{ALIGN} returns the current location counter
3904 aligned upward to the specified value.
3906 Specifying @var{address} for a section will change the value of the
3907 location counter, provided that the section is non-empty. (Empty
3908 sections are ignored).
3911 @subsection Input Section Description
3912 @cindex input sections
3913 @cindex mapping input sections to output sections
3914 The most common output section command is an input section description.
3916 The input section description is the most basic linker script operation.
3917 You use output sections to tell the linker how to lay out your program
3918 in memory. You use input section descriptions to tell the linker how to
3919 map the input files into your memory layout.
3922 * Input Section Basics:: Input section basics
3923 * Input Section Wildcards:: Input section wildcard patterns
3924 * Input Section Common:: Input section for common symbols
3925 * Input Section Keep:: Input section and garbage collection
3926 * Input Section Example:: Input section example
3929 @node Input Section Basics
3930 @subsubsection Input Section Basics
3931 @cindex input section basics
3932 An input section description consists of a file name optionally followed
3933 by a list of section names in parentheses.
3935 The file name and the section name may be wildcard patterns, which we
3936 describe further below (@pxref{Input Section Wildcards}).
3938 The most common input section description is to include all input
3939 sections with a particular name in the output section. For example, to
3940 include all input @samp{.text} sections, you would write:
3945 Here the @samp{*} is a wildcard which matches any file name. To exclude a list
3946 of files from matching the file name wildcard, EXCLUDE_FILE may be used to
3947 match all files except the ones specified in the EXCLUDE_FILE list. For
3950 *(EXCLUDE_FILE (*crtend.o *otherfile.o) .ctors)
3952 will cause all .ctors sections from all files except @file{crtend.o} and
3953 @file{otherfile.o} to be included.
3955 There are two ways to include more than one section:
3961 The difference between these is the order in which the @samp{.text} and
3962 @samp{.rdata} input sections will appear in the output section. In the
3963 first example, they will be intermingled, appearing in the same order as
3964 they are found in the linker input. In the second example, all
3965 @samp{.text} input sections will appear first, followed by all
3966 @samp{.rdata} input sections.
3968 You can specify a file name to include sections from a particular file.
3969 You would do this if one or more of your files contain special data that
3970 needs to be at a particular location in memory. For example:
3975 To refine the sections that are included based on the section flags
3976 of an input section, INPUT_SECTION_FLAGS may be used.
3978 Here is a simple example for using Section header flags for ELF sections:
3983 .text : @{ INPUT_SECTION_FLAGS (SHF_MERGE & SHF_STRINGS) *(.text) @}
3984 .text2 : @{ INPUT_SECTION_FLAGS (!SHF_WRITE) *(.text) @}
3989 In this example, the output section @samp{.text} will be comprised of any
3990 input section matching the name *(.text) whose section header flags
3991 @code{SHF_MERGE} and @code{SHF_STRINGS} are set. The output section
3992 @samp{.text2} will be comprised of any input section matching the name *(.text)
3993 whose section header flag @code{SHF_WRITE} is clear.
3995 You can also specify files within archives by writing a pattern
3996 matching the archive, a colon, then the pattern matching the file,
3997 with no whitespace around the colon.
4001 matches file within archive
4003 matches the whole archive
4005 matches file but not one in an archive
4008 Either one or both of @samp{archive} and @samp{file} can contain shell
4009 wildcards. On DOS based file systems, the linker will assume that a
4010 single letter followed by a colon is a drive specifier, so
4011 @samp{c:myfile.o} is a simple file specification, not @samp{myfile.o}
4012 within an archive called @samp{c}. @samp{archive:file} filespecs may
4013 also be used within an @code{EXCLUDE_FILE} list, but may not appear in
4014 other linker script contexts. For instance, you cannot extract a file
4015 from an archive by using @samp{archive:file} in an @code{INPUT}
4018 If you use a file name without a list of sections, then all sections in
4019 the input file will be included in the output section. This is not
4020 commonly done, but it may by useful on occasion. For example:
4025 When you use a file name which is not an @samp{archive:file} specifier
4026 and does not contain any wild card
4027 characters, the linker will first see if you also specified the file
4028 name on the linker command line or in an @code{INPUT} command. If you
4029 did not, the linker will attempt to open the file as an input file, as
4030 though it appeared on the command line. Note that this differs from an
4031 @code{INPUT} command, because the linker will not search for the file in
4032 the archive search path.
4034 @node Input Section Wildcards
4035 @subsubsection Input Section Wildcard Patterns
4036 @cindex input section wildcards
4037 @cindex wildcard file name patterns
4038 @cindex file name wildcard patterns
4039 @cindex section name wildcard patterns
4040 In an input section description, either the file name or the section
4041 name or both may be wildcard patterns.
4043 The file name of @samp{*} seen in many examples is a simple wildcard
4044 pattern for the file name.
4046 The wildcard patterns are like those used by the Unix shell.
4050 matches any number of characters
4052 matches any single character
4054 matches a single instance of any of the @var{chars}; the @samp{-}
4055 character may be used to specify a range of characters, as in
4056 @samp{[a-z]} to match any lower case letter
4058 quotes the following character
4061 When a file name is matched with a wildcard, the wildcard characters
4062 will not match a @samp{/} character (used to separate directory names on
4063 Unix). A pattern consisting of a single @samp{*} character is an
4064 exception; it will always match any file name, whether it contains a
4065 @samp{/} or not. In a section name, the wildcard characters will match
4066 a @samp{/} character.
4068 File name wildcard patterns only match files which are explicitly
4069 specified on the command line or in an @code{INPUT} command. The linker
4070 does not search directories to expand wildcards.
4072 If a file name matches more than one wildcard pattern, or if a file name
4073 appears explicitly and is also matched by a wildcard pattern, the linker
4074 will use the first match in the linker script. For example, this
4075 sequence of input section descriptions is probably in error, because the
4076 @file{data.o} rule will not be used:
4078 .data : @{ *(.data) @}
4079 .data1 : @{ data.o(.data) @}
4082 @cindex SORT_BY_NAME
4083 Normally, the linker will place files and sections matched by wildcards
4084 in the order in which they are seen during the link. You can change
4085 this by using the @code{SORT_BY_NAME} keyword, which appears before a wildcard
4086 pattern in parentheses (e.g., @code{SORT_BY_NAME(.text*)}). When the
4087 @code{SORT_BY_NAME} keyword is used, the linker will sort the files or sections
4088 into ascending order by name before placing them in the output file.
4090 @cindex SORT_BY_ALIGNMENT
4091 @code{SORT_BY_ALIGNMENT} is very similar to @code{SORT_BY_NAME}. The
4092 difference is @code{SORT_BY_ALIGNMENT} will sort sections into
4093 descending order by alignment before placing them in the output file.
4094 Larger alignments are placed before smaller alignments in order to
4095 reduce the amount of padding necessary.
4097 @cindex SORT_BY_INIT_PRIORITY
4098 @code{SORT_BY_INIT_PRIORITY} is very similar to @code{SORT_BY_NAME}. The
4099 difference is @code{SORT_BY_INIT_PRIORITY} will sort sections into
4100 ascending order by numerical value of the GCC init_priority attribute
4101 encoded in the section name before placing them in the output file.
4104 @code{SORT} is an alias for @code{SORT_BY_NAME}.
4106 When there are nested section sorting commands in linker script, there
4107 can be at most 1 level of nesting for section sorting commands.
4111 @code{SORT_BY_NAME} (@code{SORT_BY_ALIGNMENT} (wildcard section pattern)).
4112 It will sort the input sections by name first, then by alignment if two
4113 sections have the same name.
4115 @code{SORT_BY_ALIGNMENT} (@code{SORT_BY_NAME} (wildcard section pattern)).
4116 It will sort the input sections by alignment first, then by name if two
4117 sections have the same alignment.
4119 @code{SORT_BY_NAME} (@code{SORT_BY_NAME} (wildcard section pattern)) is
4120 treated the same as @code{SORT_BY_NAME} (wildcard section pattern).
4122 @code{SORT_BY_ALIGNMENT} (@code{SORT_BY_ALIGNMENT} (wildcard section pattern))
4123 is treated the same as @code{SORT_BY_ALIGNMENT} (wildcard section pattern).
4125 All other nested section sorting commands are invalid.
4128 When both command line section sorting option and linker script
4129 section sorting command are used, section sorting command always
4130 takes precedence over the command line option.
4132 If the section sorting command in linker script isn't nested, the
4133 command line option will make the section sorting command to be
4134 treated as nested sorting command.
4138 @code{SORT_BY_NAME} (wildcard section pattern ) with
4139 @option{--sort-sections alignment} is equivalent to
4140 @code{SORT_BY_NAME} (@code{SORT_BY_ALIGNMENT} (wildcard section pattern)).
4142 @code{SORT_BY_ALIGNMENT} (wildcard section pattern) with
4143 @option{--sort-section name} is equivalent to
4144 @code{SORT_BY_ALIGNMENT} (@code{SORT_BY_NAME} (wildcard section pattern)).
4147 If the section sorting command in linker script is nested, the
4148 command line option will be ignored.
4151 @code{SORT_NONE} disables section sorting by ignoring the command line
4152 section sorting option.
4154 If you ever get confused about where input sections are going, use the
4155 @samp{-M} linker option to generate a map file. The map file shows
4156 precisely how input sections are mapped to output sections.
4158 This example shows how wildcard patterns might be used to partition
4159 files. This linker script directs the linker to place all @samp{.text}
4160 sections in @samp{.text} and all @samp{.bss} sections in @samp{.bss}.
4161 The linker will place the @samp{.data} section from all files beginning
4162 with an upper case character in @samp{.DATA}; for all other files, the
4163 linker will place the @samp{.data} section in @samp{.data}.
4167 .text : @{ *(.text) @}
4168 .DATA : @{ [A-Z]*(.data) @}
4169 .data : @{ *(.data) @}
4170 .bss : @{ *(.bss) @}
4175 @node Input Section Common
4176 @subsubsection Input Section for Common Symbols
4177 @cindex common symbol placement
4178 @cindex uninitialized data placement
4179 A special notation is needed for common symbols, because in many object
4180 file formats common symbols do not have a particular input section. The
4181 linker treats common symbols as though they are in an input section
4182 named @samp{COMMON}.
4184 You may use file names with the @samp{COMMON} section just as with any
4185 other input sections. You can use this to place common symbols from a
4186 particular input file in one section while common symbols from other
4187 input files are placed in another section.
4189 In most cases, common symbols in input files will be placed in the
4190 @samp{.bss} section in the output file. For example:
4192 .bss @{ *(.bss) *(COMMON) @}
4195 @cindex scommon section
4196 @cindex small common symbols
4197 Some object file formats have more than one type of common symbol. For
4198 example, the MIPS ELF object file format distinguishes standard common
4199 symbols and small common symbols. In this case, the linker will use a
4200 different special section name for other types of common symbols. In
4201 the case of MIPS ELF, the linker uses @samp{COMMON} for standard common
4202 symbols and @samp{.scommon} for small common symbols. This permits you
4203 to map the different types of common symbols into memory at different
4207 You will sometimes see @samp{[COMMON]} in old linker scripts. This
4208 notation is now considered obsolete. It is equivalent to
4211 @node Input Section Keep
4212 @subsubsection Input Section and Garbage Collection
4214 @cindex garbage collection
4215 When link-time garbage collection is in use (@samp{--gc-sections}),
4216 it is often useful to mark sections that should not be eliminated.
4217 This is accomplished by surrounding an input section's wildcard entry
4218 with @code{KEEP()}, as in @code{KEEP(*(.init))} or
4219 @code{KEEP(SORT_BY_NAME(*)(.ctors))}.
4221 @node Input Section Example
4222 @subsubsection Input Section Example
4223 The following example is a complete linker script. It tells the linker
4224 to read all of the sections from file @file{all.o} and place them at the
4225 start of output section @samp{outputa} which starts at location
4226 @samp{0x10000}. All of section @samp{.input1} from file @file{foo.o}
4227 follows immediately, in the same output section. All of section
4228 @samp{.input2} from @file{foo.o} goes into output section
4229 @samp{outputb}, followed by section @samp{.input1} from @file{foo1.o}.
4230 All of the remaining @samp{.input1} and @samp{.input2} sections from any
4231 files are written to output section @samp{outputc}.
4259 @node Output Section Data
4260 @subsection Output Section Data
4262 @cindex section data
4263 @cindex output section data
4264 @kindex BYTE(@var{expression})
4265 @kindex SHORT(@var{expression})
4266 @kindex LONG(@var{expression})
4267 @kindex QUAD(@var{expression})
4268 @kindex SQUAD(@var{expression})
4269 You can include explicit bytes of data in an output section by using
4270 @code{BYTE}, @code{SHORT}, @code{LONG}, @code{QUAD}, or @code{SQUAD} as
4271 an output section command. Each keyword is followed by an expression in
4272 parentheses providing the value to store (@pxref{Expressions}). The
4273 value of the expression is stored at the current value of the location
4276 The @code{BYTE}, @code{SHORT}, @code{LONG}, and @code{QUAD} commands
4277 store one, two, four, and eight bytes (respectively). After storing the
4278 bytes, the location counter is incremented by the number of bytes
4281 For example, this will store the byte 1 followed by the four byte value
4282 of the symbol @samp{addr}:
4288 When using a 64 bit host or target, @code{QUAD} and @code{SQUAD} are the
4289 same; they both store an 8 byte, or 64 bit, value. When both host and
4290 target are 32 bits, an expression is computed as 32 bits. In this case
4291 @code{QUAD} stores a 32 bit value zero extended to 64 bits, and
4292 @code{SQUAD} stores a 32 bit value sign extended to 64 bits.
4294 If the object file format of the output file has an explicit endianness,
4295 which is the normal case, the value will be stored in that endianness.
4296 When the object file format does not have an explicit endianness, as is
4297 true of, for example, S-records, the value will be stored in the
4298 endianness of the first input object file.
4300 Note---these commands only work inside a section description and not
4301 between them, so the following will produce an error from the linker:
4303 SECTIONS @{@ .text : @{@ *(.text) @}@ LONG(1) .data : @{@ *(.data) @}@ @}@
4305 whereas this will work:
4307 SECTIONS @{@ .text : @{@ *(.text) ; LONG(1) @}@ .data : @{@ *(.data) @}@ @}@
4310 @kindex FILL(@var{expression})
4311 @cindex holes, filling
4312 @cindex unspecified memory
4313 You may use the @code{FILL} command to set the fill pattern for the
4314 current section. It is followed by an expression in parentheses. Any
4315 otherwise unspecified regions of memory within the section (for example,
4316 gaps left due to the required alignment of input sections) are filled
4317 with the value of the expression, repeated as
4318 necessary. A @code{FILL} statement covers memory locations after the
4319 point at which it occurs in the section definition; by including more
4320 than one @code{FILL} statement, you can have different fill patterns in
4321 different parts of an output section.
4323 This example shows how to fill unspecified regions of memory with the
4329 The @code{FILL} command is similar to the @samp{=@var{fillexp}} output
4330 section attribute, but it only affects the
4331 part of the section following the @code{FILL} command, rather than the
4332 entire section. If both are used, the @code{FILL} command takes
4333 precedence. @xref{Output Section Fill}, for details on the fill
4336 @node Output Section Keywords
4337 @subsection Output Section Keywords
4338 There are a couple of keywords which can appear as output section
4342 @kindex CREATE_OBJECT_SYMBOLS
4343 @cindex input filename symbols
4344 @cindex filename symbols
4345 @item CREATE_OBJECT_SYMBOLS
4346 The command tells the linker to create a symbol for each input file.
4347 The name of each symbol will be the name of the corresponding input
4348 file. The section of each symbol will be the output section in which
4349 the @code{CREATE_OBJECT_SYMBOLS} command appears.
4351 This is conventional for the a.out object file format. It is not
4352 normally used for any other object file format.
4354 @kindex CONSTRUCTORS
4355 @cindex C++ constructors, arranging in link
4356 @cindex constructors, arranging in link
4358 When linking using the a.out object file format, the linker uses an
4359 unusual set construct to support C++ global constructors and
4360 destructors. When linking object file formats which do not support
4361 arbitrary sections, such as ECOFF and XCOFF, the linker will
4362 automatically recognize C++ global constructors and destructors by name.
4363 For these object file formats, the @code{CONSTRUCTORS} command tells the
4364 linker to place constructor information in the output section where the
4365 @code{CONSTRUCTORS} command appears. The @code{CONSTRUCTORS} command is
4366 ignored for other object file formats.
4368 The symbol @w{@code{__CTOR_LIST__}} marks the start of the global
4369 constructors, and the symbol @w{@code{__CTOR_END__}} marks the end.
4370 Similarly, @w{@code{__DTOR_LIST__}} and @w{@code{__DTOR_END__}} mark
4371 the start and end of the global destructors. The
4372 first word in the list is the number of entries, followed by the address
4373 of each constructor or destructor, followed by a zero word. The
4374 compiler must arrange to actually run the code. For these object file
4375 formats @sc{gnu} C++ normally calls constructors from a subroutine
4376 @code{__main}; a call to @code{__main} is automatically inserted into
4377 the startup code for @code{main}. @sc{gnu} C++ normally runs
4378 destructors either by using @code{atexit}, or directly from the function
4381 For object file formats such as @code{COFF} or @code{ELF} which support
4382 arbitrary section names, @sc{gnu} C++ will normally arrange to put the
4383 addresses of global constructors and destructors into the @code{.ctors}
4384 and @code{.dtors} sections. Placing the following sequence into your
4385 linker script will build the sort of table which the @sc{gnu} C++
4386 runtime code expects to see.
4390 LONG((__CTOR_END__ - __CTOR_LIST__) / 4 - 2)
4395 LONG((__DTOR_END__ - __DTOR_LIST__) / 4 - 2)
4401 If you are using the @sc{gnu} C++ support for initialization priority,
4402 which provides some control over the order in which global constructors
4403 are run, you must sort the constructors at link time to ensure that they
4404 are executed in the correct order. When using the @code{CONSTRUCTORS}
4405 command, use @samp{SORT_BY_NAME(CONSTRUCTORS)} instead. When using the
4406 @code{.ctors} and @code{.dtors} sections, use @samp{*(SORT_BY_NAME(.ctors))} and
4407 @samp{*(SORT_BY_NAME(.dtors))} instead of just @samp{*(.ctors)} and
4410 Normally the compiler and linker will handle these issues automatically,
4411 and you will not need to concern yourself with them. However, you may
4412 need to consider this if you are using C++ and writing your own linker
4417 @node Output Section Discarding
4418 @subsection Output Section Discarding
4419 @cindex discarding sections
4420 @cindex sections, discarding
4421 @cindex removing sections
4422 The linker will not normally create output sections with no contents.
4423 This is for convenience when referring to input sections that may or
4424 may not be present in any of the input files. For example:
4426 .foo : @{ *(.foo) @}
4429 will only create a @samp{.foo} section in the output file if there is a
4430 @samp{.foo} section in at least one input file, and if the input
4431 sections are not all empty. Other link script directives that allocate
4432 space in an output section will also create the output section. So
4433 too will assignments to dot even if the assignment does not create
4434 space, except for @samp{. = 0}, @samp{. = . + 0}, @samp{. = sym},
4435 @samp{. = . + sym} and @samp{. = ALIGN (. != 0, expr, 1)} when
4436 @samp{sym} is an absolute symbol of value 0 defined in the script.
4437 This allows you to force output of an empty section with @samp{. = .}.
4439 The linker will ignore address assignments (@pxref{Output Section Address})
4440 on discarded output sections, except when the linker script defines
4441 symbols in the output section. In that case the linker will obey
4442 the address assignments, possibly advancing dot even though the
4443 section is discarded.
4446 The special output section name @samp{/DISCARD/} may be used to discard
4447 input sections. Any input sections which are assigned to an output
4448 section named @samp{/DISCARD/} are not included in the output file.
4450 @node Output Section Attributes
4451 @subsection Output Section Attributes
4452 @cindex output section attributes
4453 We showed above that the full description of an output section looked
4458 @var{section} [@var{address}] [(@var{type})] :
4460 [ALIGN(@var{section_align})]
4461 [SUBALIGN(@var{subsection_align})]
4464 @var{output-section-command}
4465 @var{output-section-command}
4467 @} [>@var{region}] [AT>@var{lma_region}] [:@var{phdr} :@var{phdr} @dots{}] [=@var{fillexp}]
4471 We've already described @var{section}, @var{address}, and
4472 @var{output-section-command}. In this section we will describe the
4473 remaining section attributes.
4476 * Output Section Type:: Output section type
4477 * Output Section LMA:: Output section LMA
4478 * Forced Output Alignment:: Forced Output Alignment
4479 * Forced Input Alignment:: Forced Input Alignment
4480 * Output Section Constraint:: Output section constraint
4481 * Output Section Region:: Output section region
4482 * Output Section Phdr:: Output section phdr
4483 * Output Section Fill:: Output section fill
4486 @node Output Section Type
4487 @subsubsection Output Section Type
4488 Each output section may have a type. The type is a keyword in
4489 parentheses. The following types are defined:
4493 The section should be marked as not loadable, so that it will not be
4494 loaded into memory when the program is run.
4499 These type names are supported for backward compatibility, and are
4500 rarely used. They all have the same effect: the section should be
4501 marked as not allocatable, so that no memory is allocated for the
4502 section when the program is run.
4506 @cindex prevent unnecessary loading
4507 @cindex loading, preventing
4508 The linker normally sets the attributes of an output section based on
4509 the input sections which map into it. You can override this by using
4510 the section type. For example, in the script sample below, the
4511 @samp{ROM} section is addressed at memory location @samp{0} and does not
4512 need to be loaded when the program is run.
4516 ROM 0 (NOLOAD) : @{ @dots{} @}
4522 @node Output Section LMA
4523 @subsubsection Output Section LMA
4524 @kindex AT>@var{lma_region}
4525 @kindex AT(@var{lma})
4526 @cindex load address
4527 @cindex section load address
4528 Every section has a virtual address (VMA) and a load address (LMA); see
4529 @ref{Basic Script Concepts}. The virtual address is specified by the
4530 @pxref{Output Section Address} described earlier. The load address is
4531 specified by the @code{AT} or @code{AT>} keywords. Specifying a load
4532 address is optional.
4534 The @code{AT} keyword takes an expression as an argument. This
4535 specifies the exact load address of the section. The @code{AT>} keyword
4536 takes the name of a memory region as an argument. @xref{MEMORY}. The
4537 load address of the section is set to the next free address in the
4538 region, aligned to the section's alignment requirements.
4540 If neither @code{AT} nor @code{AT>} is specified for an allocatable
4541 section, the linker will use the following heuristic to determine the
4546 If the section has a specific VMA address, then this is used as
4547 the LMA address as well.
4550 If the section is not allocatable then its LMA is set to its VMA.
4553 Otherwise if a memory region can be found that is compatible
4554 with the current section, and this region contains at least one
4555 section, then the LMA is set so the difference between the
4556 VMA and LMA is the same as the difference between the VMA and LMA of
4557 the last section in the located region.
4560 If no memory regions have been declared then a default region
4561 that covers the entire address space is used in the previous step.
4564 If no suitable region could be found, or there was no previous
4565 section then the LMA is set equal to the VMA.
4568 @cindex ROM initialized data
4569 @cindex initialized data in ROM
4570 This feature is designed to make it easy to build a ROM image. For
4571 example, the following linker script creates three output sections: one
4572 called @samp{.text}, which starts at @code{0x1000}, one called
4573 @samp{.mdata}, which is loaded at the end of the @samp{.text} section
4574 even though its VMA is @code{0x2000}, and one called @samp{.bss} to hold
4575 uninitialized data at address @code{0x3000}. The symbol @code{_data} is
4576 defined with the value @code{0x2000}, which shows that the location
4577 counter holds the VMA value, not the LMA value.
4583 .text 0x1000 : @{ *(.text) _etext = . ; @}
4585 AT ( ADDR (.text) + SIZEOF (.text) )
4586 @{ _data = . ; *(.data); _edata = . ; @}
4588 @{ _bstart = . ; *(.bss) *(COMMON) ; _bend = . ;@}
4593 The run-time initialization code for use with a program generated with
4594 this linker script would include something like the following, to copy
4595 the initialized data from the ROM image to its runtime address. Notice
4596 how this code takes advantage of the symbols defined by the linker
4601 extern char _etext, _data, _edata, _bstart, _bend;
4602 char *src = &_etext;
4605 /* ROM has data at end of text; copy it. */
4606 while (dst < &_edata)
4610 for (dst = &_bstart; dst< &_bend; dst++)
4615 @node Forced Output Alignment
4616 @subsubsection Forced Output Alignment
4617 @kindex ALIGN(@var{section_align})
4618 @cindex forcing output section alignment
4619 @cindex output section alignment
4620 You can increase an output section's alignment by using ALIGN. As an
4621 alternative you can enforce that the difference between the VMA and LMA remains
4622 intact throughout this output section with the ALIGN_WITH_INPUT attribute.
4624 @node Forced Input Alignment
4625 @subsubsection Forced Input Alignment
4626 @kindex SUBALIGN(@var{subsection_align})
4627 @cindex forcing input section alignment
4628 @cindex input section alignment
4629 You can force input section alignment within an output section by using
4630 SUBALIGN. The value specified overrides any alignment given by input
4631 sections, whether larger or smaller.
4633 @node Output Section Constraint
4634 @subsubsection Output Section Constraint
4637 @cindex constraints on output sections
4638 You can specify that an output section should only be created if all
4639 of its input sections are read-only or all of its input sections are
4640 read-write by using the keyword @code{ONLY_IF_RO} and
4641 @code{ONLY_IF_RW} respectively.
4643 @node Output Section Region
4644 @subsubsection Output Section Region
4645 @kindex >@var{region}
4646 @cindex section, assigning to memory region
4647 @cindex memory regions and sections
4648 You can assign a section to a previously defined region of memory by
4649 using @samp{>@var{region}}. @xref{MEMORY}.
4651 Here is a simple example:
4654 MEMORY @{ rom : ORIGIN = 0x1000, LENGTH = 0x1000 @}
4655 SECTIONS @{ ROM : @{ *(.text) @} >rom @}
4659 @node Output Section Phdr
4660 @subsubsection Output Section Phdr
4662 @cindex section, assigning to program header
4663 @cindex program headers and sections
4664 You can assign a section to a previously defined program segment by
4665 using @samp{:@var{phdr}}. @xref{PHDRS}. If a section is assigned to
4666 one or more segments, then all subsequent allocated sections will be
4667 assigned to those segments as well, unless they use an explicitly
4668 @code{:@var{phdr}} modifier. You can use @code{:NONE} to tell the
4669 linker to not put the section in any segment at all.
4671 Here is a simple example:
4674 PHDRS @{ text PT_LOAD ; @}
4675 SECTIONS @{ .text : @{ *(.text) @} :text @}
4679 @node Output Section Fill
4680 @subsubsection Output Section Fill
4681 @kindex =@var{fillexp}
4682 @cindex section fill pattern
4683 @cindex fill pattern, entire section
4684 You can set the fill pattern for an entire section by using
4685 @samp{=@var{fillexp}}. @var{fillexp} is an expression
4686 (@pxref{Expressions}). Any otherwise unspecified regions of memory
4687 within the output section (for example, gaps left due to the required
4688 alignment of input sections) will be filled with the value, repeated as
4689 necessary. If the fill expression is a simple hex number, ie. a string
4690 of hex digit starting with @samp{0x} and without a trailing @samp{k} or @samp{M}, then
4691 an arbitrarily long sequence of hex digits can be used to specify the
4692 fill pattern; Leading zeros become part of the pattern too. For all
4693 other cases, including extra parentheses or a unary @code{+}, the fill
4694 pattern is the four least significant bytes of the value of the
4695 expression. In all cases, the number is big-endian.
4697 You can also change the fill value with a @code{FILL} command in the
4698 output section commands; (@pxref{Output Section Data}).
4700 Here is a simple example:
4703 SECTIONS @{ .text : @{ *(.text) @} =0x90909090 @}
4707 @node Overlay Description
4708 @subsection Overlay Description
4711 An overlay description provides an easy way to describe sections which
4712 are to be loaded as part of a single memory image but are to be run at
4713 the same memory address. At run time, some sort of overlay manager will
4714 copy the overlaid sections in and out of the runtime memory address as
4715 required, perhaps by simply manipulating addressing bits. This approach
4716 can be useful, for example, when a certain region of memory is faster
4719 Overlays are described using the @code{OVERLAY} command. The
4720 @code{OVERLAY} command is used within a @code{SECTIONS} command, like an
4721 output section description. The full syntax of the @code{OVERLAY}
4722 command is as follows:
4725 OVERLAY [@var{start}] : [NOCROSSREFS] [AT ( @var{ldaddr} )]
4729 @var{output-section-command}
4730 @var{output-section-command}
4732 @} [:@var{phdr}@dots{}] [=@var{fill}]
4735 @var{output-section-command}
4736 @var{output-section-command}
4738 @} [:@var{phdr}@dots{}] [=@var{fill}]
4740 @} [>@var{region}] [:@var{phdr}@dots{}] [=@var{fill}] [,]
4744 Everything is optional except @code{OVERLAY} (a keyword), and each
4745 section must have a name (@var{secname1} and @var{secname2} above). The
4746 section definitions within the @code{OVERLAY} construct are identical to
4747 those within the general @code{SECTIONS} construct (@pxref{SECTIONS}),
4748 except that no addresses and no memory regions may be defined for
4749 sections within an @code{OVERLAY}.
4751 The comma at the end may be required if a @var{fill} is used and
4752 the next @var{sections-command} looks like a continuation of the expression.
4754 The sections are all defined with the same starting address. The load
4755 addresses of the sections are arranged such that they are consecutive in
4756 memory starting at the load address used for the @code{OVERLAY} as a
4757 whole (as with normal section definitions, the load address is optional,
4758 and defaults to the start address; the start address is also optional,
4759 and defaults to the current value of the location counter).
4761 If the @code{NOCROSSREFS} keyword is used, and there are any
4762 references among the sections, the linker will report an error. Since
4763 the sections all run at the same address, it normally does not make
4764 sense for one section to refer directly to another.
4765 @xref{Miscellaneous Commands, NOCROSSREFS}.
4767 For each section within the @code{OVERLAY}, the linker automatically
4768 provides two symbols. The symbol @code{__load_start_@var{secname}} is
4769 defined as the starting load address of the section. The symbol
4770 @code{__load_stop_@var{secname}} is defined as the final load address of
4771 the section. Any characters within @var{secname} which are not legal
4772 within C identifiers are removed. C (or assembler) code may use these
4773 symbols to move the overlaid sections around as necessary.
4775 At the end of the overlay, the value of the location counter is set to
4776 the start address of the overlay plus the size of the largest section.
4778 Here is an example. Remember that this would appear inside a
4779 @code{SECTIONS} construct.
4782 OVERLAY 0x1000 : AT (0x4000)
4784 .text0 @{ o1/*.o(.text) @}
4785 .text1 @{ o2/*.o(.text) @}
4790 This will define both @samp{.text0} and @samp{.text1} to start at
4791 address 0x1000. @samp{.text0} will be loaded at address 0x4000, and
4792 @samp{.text1} will be loaded immediately after @samp{.text0}. The
4793 following symbols will be defined if referenced: @code{__load_start_text0},
4794 @code{__load_stop_text0}, @code{__load_start_text1},
4795 @code{__load_stop_text1}.
4797 C code to copy overlay @code{.text1} into the overlay area might look
4802 extern char __load_start_text1, __load_stop_text1;
4803 memcpy ((char *) 0x1000, &__load_start_text1,
4804 &__load_stop_text1 - &__load_start_text1);
4808 Note that the @code{OVERLAY} command is just syntactic sugar, since
4809 everything it does can be done using the more basic commands. The above
4810 example could have been written identically as follows.
4814 .text0 0x1000 : AT (0x4000) @{ o1/*.o(.text) @}
4815 PROVIDE (__load_start_text0 = LOADADDR (.text0));
4816 PROVIDE (__load_stop_text0 = LOADADDR (.text0) + SIZEOF (.text0));
4817 .text1 0x1000 : AT (0x4000 + SIZEOF (.text0)) @{ o2/*.o(.text) @}
4818 PROVIDE (__load_start_text1 = LOADADDR (.text1));
4819 PROVIDE (__load_stop_text1 = LOADADDR (.text1) + SIZEOF (.text1));
4820 . = 0x1000 + MAX (SIZEOF (.text0), SIZEOF (.text1));
4825 @section MEMORY Command
4827 @cindex memory regions
4828 @cindex regions of memory
4829 @cindex allocating memory
4830 @cindex discontinuous memory
4831 The linker's default configuration permits allocation of all available
4832 memory. You can override this by using the @code{MEMORY} command.
4834 The @code{MEMORY} command describes the location and size of blocks of
4835 memory in the target. You can use it to describe which memory regions
4836 may be used by the linker, and which memory regions it must avoid. You
4837 can then assign sections to particular memory regions. The linker will
4838 set section addresses based on the memory regions, and will warn about
4839 regions that become too full. The linker will not shuffle sections
4840 around to fit into the available regions.
4842 A linker script may contain at most one use of the @code{MEMORY}
4843 command. However, you can define as many blocks of memory within it as
4844 you wish. The syntax is:
4849 @var{name} [(@var{attr})] : ORIGIN = @var{origin}, LENGTH = @var{len}
4855 The @var{name} is a name used in the linker script to refer to the
4856 region. The region name has no meaning outside of the linker script.
4857 Region names are stored in a separate name space, and will not conflict
4858 with symbol names, file names, or section names. Each memory region
4859 must have a distinct name within the @code{MEMORY} command. However you can
4860 add later alias names to existing memory regions with the @ref{REGION_ALIAS}
4863 @cindex memory region attributes
4864 The @var{attr} string is an optional list of attributes that specify
4865 whether to use a particular memory region for an input section which is
4866 not explicitly mapped in the linker script. As described in
4867 @ref{SECTIONS}, if you do not specify an output section for some input
4868 section, the linker will create an output section with the same name as
4869 the input section. If you define region attributes, the linker will use
4870 them to select the memory region for the output section that it creates.
4872 The @var{attr} string must consist only of the following characters:
4887 Invert the sense of any of the attributes that follow
4890 If a unmapped section matches any of the listed attributes other than
4891 @samp{!}, it will be placed in the memory region. The @samp{!}
4892 attribute reverses this test, so that an unmapped section will be placed
4893 in the memory region only if it does not match any of the listed
4899 The @var{origin} is an numerical expression for the start address of
4900 the memory region. The expression must evaluate to a constant and it
4901 cannot involve any symbols. The keyword @code{ORIGIN} may be
4902 abbreviated to @code{org} or @code{o} (but not, for example,
4908 The @var{len} is an expression for the size in bytes of the memory
4909 region. As with the @var{origin} expression, the expression must
4910 be numerical only and must evaluate to a constant. The keyword
4911 @code{LENGTH} may be abbreviated to @code{len} or @code{l}.
4913 In the following example, we specify that there are two memory regions
4914 available for allocation: one starting at @samp{0} for 256 kilobytes,
4915 and the other starting at @samp{0x40000000} for four megabytes. The
4916 linker will place into the @samp{rom} memory region every section which
4917 is not explicitly mapped into a memory region, and is either read-only
4918 or executable. The linker will place other sections which are not
4919 explicitly mapped into a memory region into the @samp{ram} memory
4926 rom (rx) : ORIGIN = 0, LENGTH = 256K
4927 ram (!rx) : org = 0x40000000, l = 4M
4932 Once you define a memory region, you can direct the linker to place
4933 specific output sections into that memory region by using the
4934 @samp{>@var{region}} output section attribute. For example, if you have
4935 a memory region named @samp{mem}, you would use @samp{>mem} in the
4936 output section definition. @xref{Output Section Region}. If no address
4937 was specified for the output section, the linker will set the address to
4938 the next available address within the memory region. If the combined
4939 output sections directed to a memory region are too large for the
4940 region, the linker will issue an error message.
4942 It is possible to access the origin and length of a memory in an
4943 expression via the @code{ORIGIN(@var{memory})} and
4944 @code{LENGTH(@var{memory})} functions:
4948 _fstack = ORIGIN(ram) + LENGTH(ram) - 4;
4953 @section PHDRS Command
4955 @cindex program headers
4956 @cindex ELF program headers
4957 @cindex program segments
4958 @cindex segments, ELF
4959 The ELF object file format uses @dfn{program headers}, also knows as
4960 @dfn{segments}. The program headers describe how the program should be
4961 loaded into memory. You can print them out by using the @code{objdump}
4962 program with the @samp{-p} option.
4964 When you run an ELF program on a native ELF system, the system loader
4965 reads the program headers in order to figure out how to load the
4966 program. This will only work if the program headers are set correctly.
4967 This manual does not describe the details of how the system loader
4968 interprets program headers; for more information, see the ELF ABI.
4970 The linker will create reasonable program headers by default. However,
4971 in some cases, you may need to specify the program headers more
4972 precisely. You may use the @code{PHDRS} command for this purpose. When
4973 the linker sees the @code{PHDRS} command in the linker script, it will
4974 not create any program headers other than the ones specified.
4976 The linker only pays attention to the @code{PHDRS} command when
4977 generating an ELF output file. In other cases, the linker will simply
4978 ignore @code{PHDRS}.
4980 This is the syntax of the @code{PHDRS} command. The words @code{PHDRS},
4981 @code{FILEHDR}, @code{AT}, and @code{FLAGS} are keywords.
4987 @var{name} @var{type} [ FILEHDR ] [ PHDRS ] [ AT ( @var{address} ) ]
4988 [ FLAGS ( @var{flags} ) ] ;
4993 The @var{name} is used only for reference in the @code{SECTIONS} command
4994 of the linker script. It is not put into the output file. Program
4995 header names are stored in a separate name space, and will not conflict
4996 with symbol names, file names, or section names. Each program header
4997 must have a distinct name. The headers are processed in order and it
4998 is usual for them to map to sections in ascending load address order.
5000 Certain program header types describe segments of memory which the
5001 system loader will load from the file. In the linker script, you
5002 specify the contents of these segments by placing allocatable output
5003 sections in the segments. You use the @samp{:@var{phdr}} output section
5004 attribute to place a section in a particular segment. @xref{Output
5007 It is normal to put certain sections in more than one segment. This
5008 merely implies that one segment of memory contains another. You may
5009 repeat @samp{:@var{phdr}}, using it once for each segment which should
5010 contain the section.
5012 If you place a section in one or more segments using @samp{:@var{phdr}},
5013 then the linker will place all subsequent allocatable sections which do
5014 not specify @samp{:@var{phdr}} in the same segments. This is for
5015 convenience, since generally a whole set of contiguous sections will be
5016 placed in a single segment. You can use @code{:NONE} to override the
5017 default segment and tell the linker to not put the section in any
5022 You may use the @code{FILEHDR} and @code{PHDRS} keywords after
5023 the program header type to further describe the contents of the segment.
5024 The @code{FILEHDR} keyword means that the segment should include the ELF
5025 file header. The @code{PHDRS} keyword means that the segment should
5026 include the ELF program headers themselves. If applied to a loadable
5027 segment (@code{PT_LOAD}), all prior loadable segments must have one of
5030 The @var{type} may be one of the following. The numbers indicate the
5031 value of the keyword.
5034 @item @code{PT_NULL} (0)
5035 Indicates an unused program header.
5037 @item @code{PT_LOAD} (1)
5038 Indicates that this program header describes a segment to be loaded from
5041 @item @code{PT_DYNAMIC} (2)
5042 Indicates a segment where dynamic linking information can be found.
5044 @item @code{PT_INTERP} (3)
5045 Indicates a segment where the name of the program interpreter may be
5048 @item @code{PT_NOTE} (4)
5049 Indicates a segment holding note information.
5051 @item @code{PT_SHLIB} (5)
5052 A reserved program header type, defined but not specified by the ELF
5055 @item @code{PT_PHDR} (6)
5056 Indicates a segment where the program headers may be found.
5058 @item @var{expression}
5059 An expression giving the numeric type of the program header. This may
5060 be used for types not defined above.
5063 You can specify that a segment should be loaded at a particular address
5064 in memory by using an @code{AT} expression. This is identical to the
5065 @code{AT} command used as an output section attribute (@pxref{Output
5066 Section LMA}). The @code{AT} command for a program header overrides the
5067 output section attribute.
5069 The linker will normally set the segment flags based on the sections
5070 which comprise the segment. You may use the @code{FLAGS} keyword to
5071 explicitly specify the segment flags. The value of @var{flags} must be
5072 an integer. It is used to set the @code{p_flags} field of the program
5075 Here is an example of @code{PHDRS}. This shows a typical set of program
5076 headers used on a native ELF system.
5082 headers PT_PHDR PHDRS ;
5084 text PT_LOAD FILEHDR PHDRS ;
5086 dynamic PT_DYNAMIC ;
5092 .interp : @{ *(.interp) @} :text :interp
5093 .text : @{ *(.text) @} :text
5094 .rodata : @{ *(.rodata) @} /* defaults to :text */
5096 . = . + 0x1000; /* move to a new page in memory */
5097 .data : @{ *(.data) @} :data
5098 .dynamic : @{ *(.dynamic) @} :data :dynamic
5105 @section VERSION Command
5106 @kindex VERSION @{script text@}
5107 @cindex symbol versions
5108 @cindex version script
5109 @cindex versions of symbols
5110 The linker supports symbol versions when using ELF. Symbol versions are
5111 only useful when using shared libraries. The dynamic linker can use
5112 symbol versions to select a specific version of a function when it runs
5113 a program that may have been linked against an earlier version of the
5116 You can include a version script directly in the main linker script, or
5117 you can supply the version script as an implicit linker script. You can
5118 also use the @samp{--version-script} linker option.
5120 The syntax of the @code{VERSION} command is simply
5122 VERSION @{ version-script-commands @}
5125 The format of the version script commands is identical to that used by
5126 Sun's linker in Solaris 2.5. The version script defines a tree of
5127 version nodes. You specify the node names and interdependencies in the
5128 version script. You can specify which symbols are bound to which
5129 version nodes, and you can reduce a specified set of symbols to local
5130 scope so that they are not globally visible outside of the shared
5133 The easiest way to demonstrate the version script language is with a few
5159 This example version script defines three version nodes. The first
5160 version node defined is @samp{VERS_1.1}; it has no other dependencies.
5161 The script binds the symbol @samp{foo1} to @samp{VERS_1.1}. It reduces
5162 a number of symbols to local scope so that they are not visible outside
5163 of the shared library; this is done using wildcard patterns, so that any
5164 symbol whose name begins with @samp{old}, @samp{original}, or @samp{new}
5165 is matched. The wildcard patterns available are the same as those used
5166 in the shell when matching filenames (also known as ``globbing'').
5167 However, if you specify the symbol name inside double quotes, then the
5168 name is treated as literal, rather than as a glob pattern.
5170 Next, the version script defines node @samp{VERS_1.2}. This node
5171 depends upon @samp{VERS_1.1}. The script binds the symbol @samp{foo2}
5172 to the version node @samp{VERS_1.2}.
5174 Finally, the version script defines node @samp{VERS_2.0}. This node
5175 depends upon @samp{VERS_1.2}. The scripts binds the symbols @samp{bar1}
5176 and @samp{bar2} are bound to the version node @samp{VERS_2.0}.
5178 When the linker finds a symbol defined in a library which is not
5179 specifically bound to a version node, it will effectively bind it to an
5180 unspecified base version of the library. You can bind all otherwise
5181 unspecified symbols to a given version node by using @samp{global: *;}
5182 somewhere in the version script. Note that it's slightly crazy to use
5183 wildcards in a global spec except on the last version node. Global
5184 wildcards elsewhere run the risk of accidentally adding symbols to the
5185 set exported for an old version. That's wrong since older versions
5186 ought to have a fixed set of symbols.
5188 The names of the version nodes have no specific meaning other than what
5189 they might suggest to the person reading them. The @samp{2.0} version
5190 could just as well have appeared in between @samp{1.1} and @samp{1.2}.
5191 However, this would be a confusing way to write a version script.
5193 Node name can be omitted, provided it is the only version node
5194 in the version script. Such version script doesn't assign any versions to
5195 symbols, only selects which symbols will be globally visible out and which
5199 @{ global: foo; bar; local: *; @};
5202 When you link an application against a shared library that has versioned
5203 symbols, the application itself knows which version of each symbol it
5204 requires, and it also knows which version nodes it needs from each
5205 shared library it is linked against. Thus at runtime, the dynamic
5206 loader can make a quick check to make sure that the libraries you have
5207 linked against do in fact supply all of the version nodes that the
5208 application will need to resolve all of the dynamic symbols. In this
5209 way it is possible for the dynamic linker to know with certainty that
5210 all external symbols that it needs will be resolvable without having to
5211 search for each symbol reference.
5213 The symbol versioning is in effect a much more sophisticated way of
5214 doing minor version checking that SunOS does. The fundamental problem
5215 that is being addressed here is that typically references to external
5216 functions are bound on an as-needed basis, and are not all bound when
5217 the application starts up. If a shared library is out of date, a
5218 required interface may be missing; when the application tries to use
5219 that interface, it may suddenly and unexpectedly fail. With symbol
5220 versioning, the user will get a warning when they start their program if
5221 the libraries being used with the application are too old.
5223 There are several GNU extensions to Sun's versioning approach. The
5224 first of these is the ability to bind a symbol to a version node in the
5225 source file where the symbol is defined instead of in the versioning
5226 script. This was done mainly to reduce the burden on the library
5227 maintainer. You can do this by putting something like:
5229 __asm__(".symver original_foo,foo@@VERS_1.1");
5232 in the C source file. This renames the function @samp{original_foo} to
5233 be an alias for @samp{foo} bound to the version node @samp{VERS_1.1}.
5234 The @samp{local:} directive can be used to prevent the symbol
5235 @samp{original_foo} from being exported. A @samp{.symver} directive
5236 takes precedence over a version script.
5238 The second GNU extension is to allow multiple versions of the same
5239 function to appear in a given shared library. In this way you can make
5240 an incompatible change to an interface without increasing the major
5241 version number of the shared library, while still allowing applications
5242 linked against the old interface to continue to function.
5244 To do this, you must use multiple @samp{.symver} directives in the
5245 source file. Here is an example:
5248 __asm__(".symver original_foo,foo@@");
5249 __asm__(".symver old_foo,foo@@VERS_1.1");
5250 __asm__(".symver old_foo1,foo@@VERS_1.2");
5251 __asm__(".symver new_foo,foo@@@@VERS_2.0");
5254 In this example, @samp{foo@@} represents the symbol @samp{foo} bound to the
5255 unspecified base version of the symbol. The source file that contains this
5256 example would define 4 C functions: @samp{original_foo}, @samp{old_foo},
5257 @samp{old_foo1}, and @samp{new_foo}.
5259 When you have multiple definitions of a given symbol, there needs to be
5260 some way to specify a default version to which external references to
5261 this symbol will be bound. You can do this with the
5262 @samp{foo@@@@VERS_2.0} type of @samp{.symver} directive. You can only
5263 declare one version of a symbol as the default in this manner; otherwise
5264 you would effectively have multiple definitions of the same symbol.
5266 If you wish to bind a reference to a specific version of the symbol
5267 within the shared library, you can use the aliases of convenience
5268 (i.e., @samp{old_foo}), or you can use the @samp{.symver} directive to
5269 specifically bind to an external version of the function in question.
5271 You can also specify the language in the version script:
5274 VERSION extern "lang" @{ version-script-commands @}
5277 The supported @samp{lang}s are @samp{C}, @samp{C++}, and @samp{Java}.
5278 The linker will iterate over the list of symbols at the link time and
5279 demangle them according to @samp{lang} before matching them to the
5280 patterns specified in @samp{version-script-commands}. The default
5281 @samp{lang} is @samp{C}.
5283 Demangled names may contains spaces and other special characters. As
5284 described above, you can use a glob pattern to match demangled names,
5285 or you can use a double-quoted string to match the string exactly. In
5286 the latter case, be aware that minor differences (such as differing
5287 whitespace) between the version script and the demangler output will
5288 cause a mismatch. As the exact string generated by the demangler
5289 might change in the future, even if the mangled name does not, you
5290 should check that all of your version directives are behaving as you
5291 expect when you upgrade.
5294 @section Expressions in Linker Scripts
5297 The syntax for expressions in the linker script language is identical to
5298 that of C expressions. All expressions are evaluated as integers. All
5299 expressions are evaluated in the same size, which is 32 bits if both the
5300 host and target are 32 bits, and is otherwise 64 bits.
5302 You can use and set symbol values in expressions.
5304 The linker defines several special purpose builtin functions for use in
5308 * Constants:: Constants
5309 * Symbolic Constants:: Symbolic constants
5310 * Symbols:: Symbol Names
5311 * Orphan Sections:: Orphan Sections
5312 * Location Counter:: The Location Counter
5313 * Operators:: Operators
5314 * Evaluation:: Evaluation
5315 * Expression Section:: The Section of an Expression
5316 * Builtin Functions:: Builtin Functions
5320 @subsection Constants
5321 @cindex integer notation
5322 @cindex constants in linker scripts
5323 All constants are integers.
5325 As in C, the linker considers an integer beginning with @samp{0} to be
5326 octal, and an integer beginning with @samp{0x} or @samp{0X} to be
5327 hexadecimal. Alternatively the linker accepts suffixes of @samp{h} or
5328 @samp{H} for hexadecimal, @samp{o} or @samp{O} for octal, @samp{b} or
5329 @samp{B} for binary and @samp{d} or @samp{D} for decimal. Any integer
5330 value without a prefix or a suffix is considered to be decimal.
5332 @cindex scaled integers
5333 @cindex K and M integer suffixes
5334 @cindex M and K integer suffixes
5335 @cindex suffixes for integers
5336 @cindex integer suffixes
5337 In addition, you can use the suffixes @code{K} and @code{M} to scale a
5341 @c END TEXI2ROFF-KILL
5342 @code{1024} or @code{1024*1024}
5346 ${\rm 1024}$ or ${\rm 1024}^2$
5348 @c END TEXI2ROFF-KILL
5349 respectively. For example, the following
5350 all refer to the same quantity:
5359 Note - the @code{K} and @code{M} suffixes cannot be used in
5360 conjunction with the base suffixes mentioned above.
5362 @node Symbolic Constants
5363 @subsection Symbolic Constants
5364 @cindex symbolic constants
5366 It is possible to refer to target specific constants via the use of
5367 the @code{CONSTANT(@var{name})} operator, where @var{name} is one of:
5372 The target's maximum page size.
5374 @item COMMONPAGESIZE
5375 @kindex COMMONPAGESIZE
5376 The target's default page size.
5382 .text ALIGN (CONSTANT (MAXPAGESIZE)) : @{ *(.text) @}
5385 will create a text section aligned to the largest page boundary
5386 supported by the target.
5389 @subsection Symbol Names
5390 @cindex symbol names
5392 @cindex quoted symbol names
5394 Unless quoted, symbol names start with a letter, underscore, or period
5395 and may include letters, digits, underscores, periods, and hyphens.
5396 Unquoted symbol names must not conflict with any keywords. You can
5397 specify a symbol which contains odd characters or has the same name as a
5398 keyword by surrounding the symbol name in double quotes:
5401 "with a space" = "also with a space" + 10;
5404 Since symbols can contain many non-alphabetic characters, it is safest
5405 to delimit symbols with spaces. For example, @samp{A-B} is one symbol,
5406 whereas @samp{A - B} is an expression involving subtraction.
5408 @node Orphan Sections
5409 @subsection Orphan Sections
5411 Orphan sections are sections present in the input files which
5412 are not explicitly placed into the output file by the linker
5413 script. The linker will still copy these sections into the
5414 output file, but it has to guess as to where they should be
5415 placed. The linker uses a simple heuristic to do this. It
5416 attempts to place orphan sections after non-orphan sections of the
5417 same attribute, such as code vs data, loadable vs non-loadable, etc.
5418 If there is not enough room to do this then it places
5419 at the end of the file.
5421 For ELF targets, the attribute of the section includes section type as
5422 well as section flag.
5424 If an orphaned section's name is representable as a C identifier then
5425 the linker will automatically @pxref{PROVIDE} two symbols:
5426 __start_SECNAME and __stop_SECNAME, where SECNAME is the name of the
5427 section. These indicate the start address and end address of the
5428 orphaned section respectively. Note: most section names are not
5429 representable as C identifiers because they contain a @samp{.}
5432 @node Location Counter
5433 @subsection The Location Counter
5436 @cindex location counter
5437 @cindex current output location
5438 The special linker variable @dfn{dot} @samp{.} always contains the
5439 current output location counter. Since the @code{.} always refers to a
5440 location in an output section, it may only appear in an expression
5441 within a @code{SECTIONS} command. The @code{.} symbol may appear
5442 anywhere that an ordinary symbol is allowed in an expression.
5445 Assigning a value to @code{.} will cause the location counter to be
5446 moved. This may be used to create holes in the output section. The
5447 location counter may not be moved backwards inside an output section,
5448 and may not be moved backwards outside of an output section if so
5449 doing creates areas with overlapping LMAs.
5465 In the previous example, the @samp{.text} section from @file{file1} is
5466 located at the beginning of the output section @samp{output}. It is
5467 followed by a 1000 byte gap. Then the @samp{.text} section from
5468 @file{file2} appears, also with a 1000 byte gap following before the
5469 @samp{.text} section from @file{file3}. The notation @samp{= 0x12345678}
5470 specifies what data to write in the gaps (@pxref{Output Section Fill}).
5472 @cindex dot inside sections
5473 Note: @code{.} actually refers to the byte offset from the start of the
5474 current containing object. Normally this is the @code{SECTIONS}
5475 statement, whose start address is 0, hence @code{.} can be used as an
5476 absolute address. If @code{.} is used inside a section description
5477 however, it refers to the byte offset from the start of that section,
5478 not an absolute address. Thus in a script like this:
5496 The @samp{.text} section will be assigned a starting address of 0x100
5497 and a size of exactly 0x200 bytes, even if there is not enough data in
5498 the @samp{.text} input sections to fill this area. (If there is too
5499 much data, an error will be produced because this would be an attempt to
5500 move @code{.} backwards). The @samp{.data} section will start at 0x500
5501 and it will have an extra 0x600 bytes worth of space after the end of
5502 the values from the @samp{.data} input sections and before the end of
5503 the @samp{.data} output section itself.
5505 @cindex dot outside sections
5506 Setting symbols to the value of the location counter outside of an
5507 output section statement can result in unexpected values if the linker
5508 needs to place orphan sections. For example, given the following:
5514 .text: @{ *(.text) @}
5518 .data: @{ *(.data) @}
5523 If the linker needs to place some input section, e.g. @code{.rodata},
5524 not mentioned in the script, it might choose to place that section
5525 between @code{.text} and @code{.data}. You might think the linker
5526 should place @code{.rodata} on the blank line in the above script, but
5527 blank lines are of no particular significance to the linker. As well,
5528 the linker doesn't associate the above symbol names with their
5529 sections. Instead, it assumes that all assignments or other
5530 statements belong to the previous output section, except for the
5531 special case of an assignment to @code{.}. I.e., the linker will
5532 place the orphan @code{.rodata} section as if the script was written
5539 .text: @{ *(.text) @}
5543 .rodata: @{ *(.rodata) @}
5544 .data: @{ *(.data) @}
5549 This may or may not be the script author's intention for the value of
5550 @code{start_of_data}. One way to influence the orphan section
5551 placement is to assign the location counter to itself, as the linker
5552 assumes that an assignment to @code{.} is setting the start address of
5553 a following output section and thus should be grouped with that
5554 section. So you could write:
5560 .text: @{ *(.text) @}
5565 .data: @{ *(.data) @}
5570 Now, the orphan @code{.rodata} section will be placed between
5571 @code{end_of_text} and @code{start_of_data}.
5575 @subsection Operators
5576 @cindex operators for arithmetic
5577 @cindex arithmetic operators
5578 @cindex precedence in expressions
5579 The linker recognizes the standard C set of arithmetic operators, with
5580 the standard bindings and precedence levels:
5583 @c END TEXI2ROFF-KILL
5585 precedence associativity Operators Notes
5591 5 left == != > < <= >=
5597 11 right &= += -= *= /= (2)
5601 (1) Prefix operators
5602 (2) @xref{Assignments}.
5606 \vskip \baselineskip
5607 %"lispnarrowing" is the extra indent used generally for smallexample
5608 \hskip\lispnarrowing\vbox{\offinterlineskip
5611 {\vrule#&\strut\hfil\ #\ \hfil&\vrule#&\strut\hfil\ #\ \hfil&\vrule#&\strut\hfil\ {\tt #}\ \hfil&\vrule#\cr
5612 height2pt&\omit&&\omit&&\omit&\cr
5613 &Precedence&& Associativity &&{\rm Operators}&\cr
5614 height2pt&\omit&&\omit&&\omit&\cr
5616 height2pt&\omit&&\omit&&\omit&\cr
5618 % '176 is tilde, '~' in tt font
5619 &1&&left&&\qquad- \char'176\ !\qquad\dag&\cr
5620 &2&&left&&* / \%&\cr
5623 &5&&left&&== != > < <= >=&\cr
5626 &8&&left&&{\&\&}&\cr
5629 &11&&right&&\qquad\&= += -= *= /=\qquad\ddag&\cr
5631 height2pt&\omit&&\omit&&\omit&\cr}
5636 @obeylines@parskip=0pt@parindent=0pt
5637 @dag@quad Prefix operators.
5638 @ddag@quad @xref{Assignments}.
5641 @c END TEXI2ROFF-KILL
5644 @subsection Evaluation
5645 @cindex lazy evaluation
5646 @cindex expression evaluation order
5647 The linker evaluates expressions lazily. It only computes the value of
5648 an expression when absolutely necessary.
5650 The linker needs some information, such as the value of the start
5651 address of the first section, and the origins and lengths of memory
5652 regions, in order to do any linking at all. These values are computed
5653 as soon as possible when the linker reads in the linker script.
5655 However, other values (such as symbol values) are not known or needed
5656 until after storage allocation. Such values are evaluated later, when
5657 other information (such as the sizes of output sections) is available
5658 for use in the symbol assignment expression.
5660 The sizes of sections cannot be known until after allocation, so
5661 assignments dependent upon these are not performed until after
5664 Some expressions, such as those depending upon the location counter
5665 @samp{.}, must be evaluated during section allocation.
5667 If the result of an expression is required, but the value is not
5668 available, then an error results. For example, a script like the
5674 .text 9+this_isnt_constant :
5680 will cause the error message @samp{non constant expression for initial
5683 @node Expression Section
5684 @subsection The Section of an Expression
5685 @cindex expression sections
5686 @cindex absolute expressions
5687 @cindex relative expressions
5688 @cindex absolute and relocatable symbols
5689 @cindex relocatable and absolute symbols
5690 @cindex symbols, relocatable and absolute
5691 Addresses and symbols may be section relative, or absolute. A section
5692 relative symbol is relocatable. If you request relocatable output
5693 using the @samp{-r} option, a further link operation may change the
5694 value of a section relative symbol. On the other hand, an absolute
5695 symbol will retain the same value throughout any further link
5698 Some terms in linker expressions are addresses. This is true of
5699 section relative symbols and for builtin functions that return an
5700 address, such as @code{ADDR}, @code{LOADADDR}, @code{ORIGIN} and
5701 @code{SEGMENT_START}. Other terms are simply numbers, or are builtin
5702 functions that return a non-address value, such as @code{LENGTH}.
5703 One complication is that unless you set @code{LD_FEATURE ("SANE_EXPR")}
5704 (@pxref{Miscellaneous Commands}), numbers and absolute symbols are treated
5705 differently depending on their location, for compatibility with older
5706 versions of @code{ld}. Expressions appearing outside an output
5707 section definition treat all numbers as absolute addresses.
5708 Expressions appearing inside an output section definition treat
5709 absolute symbols as numbers. If @code{LD_FEATURE ("SANE_EXPR")} is
5710 given, then absolute symbols and numbers are simply treated as numbers
5713 In the following simple example,
5720 __executable_start = 0x100;
5724 __data_start = 0x10;
5732 both @code{.} and @code{__executable_start} are set to the absolute
5733 address 0x100 in the first two assignments, then both @code{.} and
5734 @code{__data_start} are set to 0x10 relative to the @code{.data}
5735 section in the second two assignments.
5737 For expressions involving numbers, relative addresses and absolute
5738 addresses, ld follows these rules to evaluate terms:
5742 Unary operations on an absolute address or number, and binary
5743 operations on two absolute addresses or two numbers, or between one
5744 absolute address and a number, apply the operator to the value(s).
5746 Unary operations on a relative address, and binary operations on two
5747 relative addresses in the same section or between one relative address
5748 and a number, apply the operator to the offset part of the address(es).
5750 Other binary operations, that is, between two relative addresses not
5751 in the same section, or between a relative address and an absolute
5752 address, first convert any non-absolute term to an absolute address
5753 before applying the operator.
5756 The result section of each sub-expression is as follows:
5760 An operation involving only numbers results in a number.
5762 The result of comparisons, @samp{&&} and @samp{||} is also a number.
5764 The result of other binary arithmetic and logical operations on two
5765 relative addresses in the same section or two absolute addresses
5766 (after above conversions) is also a number.
5768 The result of other operations on relative addresses or one
5769 relative address and a number, is a relative address in the same
5770 section as the relative operand(s).
5772 The result of other operations on absolute addresses (after above
5773 conversions) is an absolute address.
5776 You can use the builtin function @code{ABSOLUTE} to force an expression
5777 to be absolute when it would otherwise be relative. For example, to
5778 create an absolute symbol set to the address of the end of the output
5779 section @samp{.data}:
5783 .data : @{ *(.data) _edata = ABSOLUTE(.); @}
5787 If @samp{ABSOLUTE} were not used, @samp{_edata} would be relative to the
5788 @samp{.data} section.
5790 Using @code{LOADADDR} also forces an expression absolute, since this
5791 particular builtin function returns an absolute address.
5793 @node Builtin Functions
5794 @subsection Builtin Functions
5795 @cindex functions in expressions
5796 The linker script language includes a number of builtin functions for
5797 use in linker script expressions.
5800 @item ABSOLUTE(@var{exp})
5801 @kindex ABSOLUTE(@var{exp})
5802 @cindex expression, absolute
5803 Return the absolute (non-relocatable, as opposed to non-negative) value
5804 of the expression @var{exp}. Primarily useful to assign an absolute
5805 value to a symbol within a section definition, where symbol values are
5806 normally section relative. @xref{Expression Section}.
5808 @item ADDR(@var{section})
5809 @kindex ADDR(@var{section})
5810 @cindex section address in expression
5811 Return the address (VMA) of the named @var{section}. Your
5812 script must previously have defined the location of that section. In
5813 the following example, @code{start_of_output_1}, @code{symbol_1} and
5814 @code{symbol_2} are assigned equivalent values, except that
5815 @code{symbol_1} will be relative to the @code{.output1} section while
5816 the other two will be absolute:
5822 start_of_output_1 = ABSOLUTE(.);
5827 symbol_1 = ADDR(.output1);
5828 symbol_2 = start_of_output_1;
5834 @item ALIGN(@var{align})
5835 @itemx ALIGN(@var{exp},@var{align})
5836 @kindex ALIGN(@var{align})
5837 @kindex ALIGN(@var{exp},@var{align})
5838 @cindex round up location counter
5839 @cindex align location counter
5840 @cindex round up expression
5841 @cindex align expression
5842 Return the location counter (@code{.}) or arbitrary expression aligned
5843 to the next @var{align} boundary. The single operand @code{ALIGN}
5844 doesn't change the value of the location counter---it just does
5845 arithmetic on it. The two operand @code{ALIGN} allows an arbitrary
5846 expression to be aligned upwards (@code{ALIGN(@var{align})} is
5847 equivalent to @code{ALIGN(., @var{align})}).
5849 Here is an example which aligns the output @code{.data} section to the
5850 next @code{0x2000} byte boundary after the preceding section and sets a
5851 variable within the section to the next @code{0x8000} boundary after the
5856 .data ALIGN(0x2000): @{
5858 variable = ALIGN(0x8000);
5864 The first use of @code{ALIGN} in this example specifies the location of
5865 a section because it is used as the optional @var{address} attribute of
5866 a section definition (@pxref{Output Section Address}). The second use
5867 of @code{ALIGN} is used to defines the value of a symbol.
5869 The builtin function @code{NEXT} is closely related to @code{ALIGN}.
5871 @item ALIGNOF(@var{section})
5872 @kindex ALIGNOF(@var{section})
5873 @cindex section alignment
5874 Return the alignment in bytes of the named @var{section}, if that section has
5875 been allocated. If the section has not been allocated when this is
5876 evaluated, the linker will report an error. In the following example,
5877 the alignment of the @code{.output} section is stored as the first
5878 value in that section.
5883 LONG (ALIGNOF (.output))
5890 @item BLOCK(@var{exp})
5891 @kindex BLOCK(@var{exp})
5892 This is a synonym for @code{ALIGN}, for compatibility with older linker
5893 scripts. It is most often seen when setting the address of an output
5896 @item DATA_SEGMENT_ALIGN(@var{maxpagesize}, @var{commonpagesize})
5897 @kindex DATA_SEGMENT_ALIGN(@var{maxpagesize}, @var{commonpagesize})
5898 This is equivalent to either
5900 (ALIGN(@var{maxpagesize}) + (. & (@var{maxpagesize} - 1)))
5904 (ALIGN(@var{maxpagesize}) + (. & (@var{maxpagesize} - @var{commonpagesize})))
5907 depending on whether the latter uses fewer @var{commonpagesize} sized pages
5908 for the data segment (area between the result of this expression and
5909 @code{DATA_SEGMENT_END}) than the former or not.
5910 If the latter form is used, it means @var{commonpagesize} bytes of runtime
5911 memory will be saved at the expense of up to @var{commonpagesize} wasted
5912 bytes in the on-disk file.
5914 This expression can only be used directly in @code{SECTIONS} commands, not in
5915 any output section descriptions and only once in the linker script.
5916 @var{commonpagesize} should be less or equal to @var{maxpagesize} and should
5917 be the system page size the object wants to be optimized for (while still
5918 working on system page sizes up to @var{maxpagesize}).
5923 . = DATA_SEGMENT_ALIGN(0x10000, 0x2000);
5926 @item DATA_SEGMENT_END(@var{exp})
5927 @kindex DATA_SEGMENT_END(@var{exp})
5928 This defines the end of data segment for @code{DATA_SEGMENT_ALIGN}
5929 evaluation purposes.
5932 . = DATA_SEGMENT_END(.);
5935 @item DATA_SEGMENT_RELRO_END(@var{offset}, @var{exp})
5936 @kindex DATA_SEGMENT_RELRO_END(@var{offset}, @var{exp})
5937 This defines the end of the @code{PT_GNU_RELRO} segment when
5938 @samp{-z relro} option is used.
5939 When @samp{-z relro} option is not present, @code{DATA_SEGMENT_RELRO_END}
5940 does nothing, otherwise @code{DATA_SEGMENT_ALIGN} is padded so that
5941 @var{exp} + @var{offset} is aligned to the most commonly used page
5942 boundary for particular target. If present in the linker script,
5943 it must always come in between @code{DATA_SEGMENT_ALIGN} and
5944 @code{DATA_SEGMENT_END}. Evaluates to the second argument plus any
5945 padding needed at the end of the @code{PT_GNU_RELRO} segment due to
5949 . = DATA_SEGMENT_RELRO_END(24, .);
5952 @item DEFINED(@var{symbol})
5953 @kindex DEFINED(@var{symbol})
5954 @cindex symbol defaults
5955 Return 1 if @var{symbol} is in the linker global symbol table and is
5956 defined before the statement using DEFINED in the script, otherwise
5957 return 0. You can use this function to provide
5958 default values for symbols. For example, the following script fragment
5959 shows how to set a global symbol @samp{begin} to the first location in
5960 the @samp{.text} section---but if a symbol called @samp{begin} already
5961 existed, its value is preserved:
5967 begin = DEFINED(begin) ? begin : . ;
5975 @item LENGTH(@var{memory})
5976 @kindex LENGTH(@var{memory})
5977 Return the length of the memory region named @var{memory}.
5979 @item LOADADDR(@var{section})
5980 @kindex LOADADDR(@var{section})
5981 @cindex section load address in expression
5982 Return the absolute LMA of the named @var{section}. (@pxref{Output
5985 @item LOG2CEIL(@var{exp})
5986 @kindex LOG2CEIL(@var{exp})
5987 Return the binary logarithm of @var{exp} rounded towards infinity.
5988 @code{LOG2CEIL(0)} returns 0.
5991 @item MAX(@var{exp1}, @var{exp2})
5992 Returns the maximum of @var{exp1} and @var{exp2}.
5995 @item MIN(@var{exp1}, @var{exp2})
5996 Returns the minimum of @var{exp1} and @var{exp2}.
5998 @item NEXT(@var{exp})
5999 @kindex NEXT(@var{exp})
6000 @cindex unallocated address, next
6001 Return the next unallocated address that is a multiple of @var{exp}.
6002 This function is closely related to @code{ALIGN(@var{exp})}; unless you
6003 use the @code{MEMORY} command to define discontinuous memory for the
6004 output file, the two functions are equivalent.
6006 @item ORIGIN(@var{memory})
6007 @kindex ORIGIN(@var{memory})
6008 Return the origin of the memory region named @var{memory}.
6010 @item SEGMENT_START(@var{segment}, @var{default})
6011 @kindex SEGMENT_START(@var{segment}, @var{default})
6012 Return the base address of the named @var{segment}. If an explicit
6013 value has already been given for this segment (with a command-line
6014 @samp{-T} option) then that value will be returned otherwise the value
6015 will be @var{default}. At present, the @samp{-T} command-line option
6016 can only be used to set the base address for the ``text'', ``data'', and
6017 ``bss'' sections, but you can use @code{SEGMENT_START} with any segment
6020 @item SIZEOF(@var{section})
6021 @kindex SIZEOF(@var{section})
6022 @cindex section size
6023 Return the size in bytes of the named @var{section}, if that section has
6024 been allocated. If the section has not been allocated when this is
6025 evaluated, the linker will report an error. In the following example,
6026 @code{symbol_1} and @code{symbol_2} are assigned identical values:
6035 symbol_1 = .end - .start ;
6036 symbol_2 = SIZEOF(.output);
6041 @item SIZEOF_HEADERS
6042 @itemx sizeof_headers
6043 @kindex SIZEOF_HEADERS
6045 Return the size in bytes of the output file's headers. This is
6046 information which appears at the start of the output file. You can use
6047 this number when setting the start address of the first section, if you
6048 choose, to facilitate paging.
6050 @cindex not enough room for program headers
6051 @cindex program headers, not enough room
6052 When producing an ELF output file, if the linker script uses the
6053 @code{SIZEOF_HEADERS} builtin function, the linker must compute the
6054 number of program headers before it has determined all the section
6055 addresses and sizes. If the linker later discovers that it needs
6056 additional program headers, it will report an error @samp{not enough
6057 room for program headers}. To avoid this error, you must avoid using
6058 the @code{SIZEOF_HEADERS} function, or you must rework your linker
6059 script to avoid forcing the linker to use additional program headers, or
6060 you must define the program headers yourself using the @code{PHDRS}
6061 command (@pxref{PHDRS}).
6064 @node Implicit Linker Scripts
6065 @section Implicit Linker Scripts
6066 @cindex implicit linker scripts
6067 If you specify a linker input file which the linker can not recognize as
6068 an object file or an archive file, it will try to read the file as a
6069 linker script. If the file can not be parsed as a linker script, the
6070 linker will report an error.
6072 An implicit linker script will not replace the default linker script.
6074 Typically an implicit linker script would contain only symbol
6075 assignments, or the @code{INPUT}, @code{GROUP}, or @code{VERSION}
6078 Any input files read because of an implicit linker script will be read
6079 at the position in the command line where the implicit linker script was
6080 read. This can affect archive searching.
6083 @node Machine Dependent
6084 @chapter Machine Dependent Features
6086 @cindex machine dependencies
6087 @command{ld} has additional features on some platforms; the following
6088 sections describe them. Machines where @command{ld} has no additional
6089 functionality are not listed.
6093 * H8/300:: @command{ld} and the H8/300
6096 * i960:: @command{ld} and the Intel 960 family
6099 * M68HC11/68HC12:: @code{ld} and the Motorola 68HC11 and 68HC12 families
6102 * ARM:: @command{ld} and the ARM family
6105 * HPPA ELF32:: @command{ld} and HPPA 32-bit ELF
6108 * M68K:: @command{ld} and the Motorola 68K family
6111 * MIPS:: @command{ld} and the MIPS family
6114 * MMIX:: @command{ld} and MMIX
6117 * MSP430:: @command{ld} and MSP430
6120 * NDS32:: @command{ld} and NDS32
6123 * Nios II:: @command{ld} and the Altera Nios II
6126 * PowerPC ELF32:: @command{ld} and PowerPC 32-bit ELF Support
6129 * PowerPC64 ELF64:: @command{ld} and PowerPC64 64-bit ELF Support
6132 * SPU ELF:: @command{ld} and SPU ELF Support
6135 * TI COFF:: @command{ld} and TI COFF
6138 * WIN32:: @command{ld} and WIN32 (cygwin/mingw)
6141 * Xtensa:: @command{ld} and Xtensa Processors
6152 @section @command{ld} and the H8/300
6154 @cindex H8/300 support
6155 For the H8/300, @command{ld} can perform these global optimizations when
6156 you specify the @samp{--relax} command-line option.
6159 @cindex relaxing on H8/300
6160 @item relaxing address modes
6161 @command{ld} finds all @code{jsr} and @code{jmp} instructions whose
6162 targets are within eight bits, and turns them into eight-bit
6163 program-counter relative @code{bsr} and @code{bra} instructions,
6166 @cindex synthesizing on H8/300
6167 @item synthesizing instructions
6168 @c FIXME: specifically mov.b, or any mov instructions really? -> mov.b only, at least on H8, H8H, H8S
6169 @command{ld} finds all @code{mov.b} instructions which use the
6170 sixteen-bit absolute address form, but refer to the top
6171 page of memory, and changes them to use the eight-bit address form.
6172 (That is: the linker turns @samp{mov.b @code{@@}@var{aa}:16} into
6173 @samp{mov.b @code{@@}@var{aa}:8} whenever the address @var{aa} is in the
6174 top page of memory).
6176 @command{ld} finds all @code{mov} instructions which use the register
6177 indirect with 32-bit displacement addressing mode, but use a small
6178 displacement inside 16-bit displacement range, and changes them to use
6179 the 16-bit displacement form. (That is: the linker turns @samp{mov.b
6180 @code{@@}@var{d}:32,ERx} into @samp{mov.b @code{@@}@var{d}:16,ERx}
6181 whenever the displacement @var{d} is in the 16 bit signed integer
6182 range. Only implemented in ELF-format ld).
6184 @item bit manipulation instructions
6185 @command{ld} finds all bit manipulation instructions like @code{band, bclr,
6186 biand, bild, bior, bist, bixor, bld, bnot, bor, bset, bst, btst, bxor}
6187 which use 32 bit and 16 bit absolute address form, but refer to the top
6188 page of memory, and changes them to use the 8 bit address form.
6189 (That is: the linker turns @samp{bset #xx:3,@code{@@}@var{aa}:32} into
6190 @samp{bset #xx:3,@code{@@}@var{aa}:8} whenever the address @var{aa} is in
6191 the top page of memory).
6193 @item system control instructions
6194 @command{ld} finds all @code{ldc.w, stc.w} instructions which use the
6195 32 bit absolute address form, but refer to the top page of memory, and
6196 changes them to use 16 bit address form.
6197 (That is: the linker turns @samp{ldc.w @code{@@}@var{aa}:32,ccr} into
6198 @samp{ldc.w @code{@@}@var{aa}:16,ccr} whenever the address @var{aa} is in
6199 the top page of memory).
6209 @c This stuff is pointless to say unless you're especially concerned
6210 @c with Renesas chips; don't enable it for generic case, please.
6212 @chapter @command{ld} and Other Renesas Chips
6214 @command{ld} also supports the Renesas (formerly Hitachi) H8/300H,
6215 H8/500, and SH chips. No special features, commands, or command-line
6216 options are required for these chips.
6226 @section @command{ld} and the Intel 960 Family
6228 @cindex i960 support
6230 You can use the @samp{-A@var{architecture}} command line option to
6231 specify one of the two-letter names identifying members of the 960
6232 family; the option specifies the desired output target, and warns of any
6233 incompatible instructions in the input files. It also modifies the
6234 linker's search strategy for archive libraries, to support the use of
6235 libraries specific to each particular architecture, by including in the
6236 search loop names suffixed with the string identifying the architecture.
6238 For example, if your @command{ld} command line included @w{@samp{-ACA}} as
6239 well as @w{@samp{-ltry}}, the linker would look (in its built-in search
6240 paths, and in any paths you specify with @samp{-L}) for a library with
6253 The first two possibilities would be considered in any event; the last
6254 two are due to the use of @w{@samp{-ACA}}.
6256 You can meaningfully use @samp{-A} more than once on a command line, since
6257 the 960 architecture family allows combination of target architectures; each
6258 use will add another pair of name variants to search for when @w{@samp{-l}}
6259 specifies a library.
6261 @cindex @option{--relax} on i960
6262 @cindex relaxing on i960
6263 @command{ld} supports the @samp{--relax} option for the i960 family. If
6264 you specify @samp{--relax}, @command{ld} finds all @code{balx} and
6265 @code{calx} instructions whose targets are within 24 bits, and turns
6266 them into 24-bit program-counter relative @code{bal} and @code{cal}
6267 instructions, respectively. @command{ld} also turns @code{cal}
6268 instructions into @code{bal} instructions when it determines that the
6269 target subroutine is a leaf routine (that is, the target subroutine does
6270 not itself call any subroutines).
6287 @node M68HC11/68HC12
6288 @section @command{ld} and the Motorola 68HC11 and 68HC12 families
6290 @cindex M68HC11 and 68HC12 support
6292 @subsection Linker Relaxation
6294 For the Motorola 68HC11, @command{ld} can perform these global
6295 optimizations when you specify the @samp{--relax} command-line option.
6298 @cindex relaxing on M68HC11
6299 @item relaxing address modes
6300 @command{ld} finds all @code{jsr} and @code{jmp} instructions whose
6301 targets are within eight bits, and turns them into eight-bit
6302 program-counter relative @code{bsr} and @code{bra} instructions,
6305 @command{ld} also looks at all 16-bit extended addressing modes and
6306 transforms them in a direct addressing mode when the address is in
6307 page 0 (between 0 and 0x0ff).
6309 @item relaxing gcc instruction group
6310 When @command{gcc} is called with @option{-mrelax}, it can emit group
6311 of instructions that the linker can optimize to use a 68HC11 direct
6312 addressing mode. These instructions consists of @code{bclr} or
6313 @code{bset} instructions.
6317 @subsection Trampoline Generation
6319 @cindex trampoline generation on M68HC11
6320 @cindex trampoline generation on M68HC12
6321 For 68HC11 and 68HC12, @command{ld} can generate trampoline code to
6322 call a far function using a normal @code{jsr} instruction. The linker
6323 will also change the relocation to some far function to use the
6324 trampoline address instead of the function address. This is typically the
6325 case when a pointer to a function is taken. The pointer will in fact
6326 point to the function trampoline.
6334 @section @command{ld} and the ARM family
6336 @cindex ARM interworking support
6337 @kindex --support-old-code
6338 For the ARM, @command{ld} will generate code stubs to allow functions calls
6339 between ARM and Thumb code. These stubs only work with code that has
6340 been compiled and assembled with the @samp{-mthumb-interwork} command
6341 line option. If it is necessary to link with old ARM object files or
6342 libraries, which have not been compiled with the -mthumb-interwork
6343 option then the @samp{--support-old-code} command line switch should be
6344 given to the linker. This will make it generate larger stub functions
6345 which will work with non-interworking aware ARM code. Note, however,
6346 the linker does not support generating stubs for function calls to
6347 non-interworking aware Thumb code.
6349 @cindex thumb entry point
6350 @cindex entry point, thumb
6351 @kindex --thumb-entry=@var{entry}
6352 The @samp{--thumb-entry} switch is a duplicate of the generic
6353 @samp{--entry} switch, in that it sets the program's starting address.
6354 But it also sets the bottom bit of the address, so that it can be
6355 branched to using a BX instruction, and the program will start
6356 executing in Thumb mode straight away.
6358 @cindex PE import table prefixing
6359 @kindex --use-nul-prefixed-import-tables
6360 The @samp{--use-nul-prefixed-import-tables} switch is specifying, that
6361 the import tables idata4 and idata5 have to be generated with a zero
6362 element prefix for import libraries. This is the old style to generate
6363 import tables. By default this option is turned off.
6367 The @samp{--be8} switch instructs @command{ld} to generate BE8 format
6368 executables. This option is only valid when linking big-endian objects.
6369 The resulting image will contain big-endian data and little-endian code.
6372 @kindex --target1-rel
6373 @kindex --target1-abs
6374 The @samp{R_ARM_TARGET1} relocation is typically used for entries in the
6375 @samp{.init_array} section. It is interpreted as either @samp{R_ARM_REL32}
6376 or @samp{R_ARM_ABS32}, depending on the target. The @samp{--target1-rel}
6377 and @samp{--target1-abs} switches override the default.
6380 @kindex --target2=@var{type}
6381 The @samp{--target2=type} switch overrides the default definition of the
6382 @samp{R_ARM_TARGET2} relocation. Valid values for @samp{type}, their
6383 meanings, and target defaults are as follows:
6386 @samp{R_ARM_REL32} (arm*-*-elf, arm*-*-eabi)
6388 @samp{R_ARM_ABS32} (arm*-*-symbianelf)
6390 @samp{R_ARM_GOT_PREL} (arm*-*-linux, arm*-*-*bsd)
6395 The @samp{R_ARM_V4BX} relocation (defined by the ARM AAELF
6396 specification) enables objects compiled for the ARMv4 architecture to be
6397 interworking-safe when linked with other objects compiled for ARMv4t, but
6398 also allows pure ARMv4 binaries to be built from the same ARMv4 objects.
6400 In the latter case, the switch @option{--fix-v4bx} must be passed to the
6401 linker, which causes v4t @code{BX rM} instructions to be rewritten as
6402 @code{MOV PC,rM}, since v4 processors do not have a @code{BX} instruction.
6404 In the former case, the switch should not be used, and @samp{R_ARM_V4BX}
6405 relocations are ignored.
6407 @cindex FIX_V4BX_INTERWORKING
6408 @kindex --fix-v4bx-interworking
6409 Replace @code{BX rM} instructions identified by @samp{R_ARM_V4BX}
6410 relocations with a branch to the following veneer:
6418 This allows generation of libraries/applications that work on ARMv4 cores
6419 and are still interworking safe. Note that the above veneer clobbers the
6420 condition flags, so may cause incorrect program behavior in rare cases.
6424 The @samp{--use-blx} switch enables the linker to use ARM/Thumb
6425 BLX instructions (available on ARMv5t and above) in various
6426 situations. Currently it is used to perform calls via the PLT from Thumb
6427 code using BLX rather than using BX and a mode-switching stub before
6428 each PLT entry. This should lead to such calls executing slightly faster.
6430 This option is enabled implicitly for SymbianOS, so there is no need to
6431 specify it if you are using that target.
6433 @cindex VFP11_DENORM_FIX
6434 @kindex --vfp11-denorm-fix
6435 The @samp{--vfp11-denorm-fix} switch enables a link-time workaround for a
6436 bug in certain VFP11 coprocessor hardware, which sometimes allows
6437 instructions with denorm operands (which must be handled by support code)
6438 to have those operands overwritten by subsequent instructions before
6439 the support code can read the intended values.
6441 The bug may be avoided in scalar mode if you allow at least one
6442 intervening instruction between a VFP11 instruction which uses a register
6443 and another instruction which writes to the same register, or at least two
6444 intervening instructions if vector mode is in use. The bug only affects
6445 full-compliance floating-point mode: you do not need this workaround if
6446 you are using "runfast" mode. Please contact ARM for further details.
6448 If you know you are using buggy VFP11 hardware, you can
6449 enable this workaround by specifying the linker option
6450 @samp{--vfp-denorm-fix=scalar} if you are using the VFP11 scalar
6451 mode only, or @samp{--vfp-denorm-fix=vector} if you are using
6452 vector mode (the latter also works for scalar code). The default is
6453 @samp{--vfp-denorm-fix=none}.
6455 If the workaround is enabled, instructions are scanned for
6456 potentially-troublesome sequences, and a veneer is created for each
6457 such sequence which may trigger the erratum. The veneer consists of the
6458 first instruction of the sequence and a branch back to the subsequent
6459 instruction. The original instruction is then replaced with a branch to
6460 the veneer. The extra cycles required to call and return from the veneer
6461 are sufficient to avoid the erratum in both the scalar and vector cases.
6463 @cindex ARM1176 erratum workaround
6464 @kindex --fix-arm1176
6465 @kindex --no-fix-arm1176
6466 The @samp{--fix-arm1176} switch enables a link-time workaround for an erratum
6467 in certain ARM1176 processors. The workaround is enabled by default if you
6468 are targeting ARM v6 (excluding ARM v6T2) or earlier. It can be disabled
6469 unconditionally by specifying @samp{--no-fix-arm1176}.
6471 Further information is available in the ``ARM1176JZ-S and ARM1176JZF-S
6472 Programmer Advice Notice'' available on the ARM documentation website at:
6473 http://infocenter.arm.com/.
6475 @cindex NO_ENUM_SIZE_WARNING
6476 @kindex --no-enum-size-warning
6477 The @option{--no-enum-size-warning} switch prevents the linker from
6478 warning when linking object files that specify incompatible EABI
6479 enumeration size attributes. For example, with this switch enabled,
6480 linking of an object file using 32-bit enumeration values with another
6481 using enumeration values fitted into the smallest possible space will
6484 @cindex NO_WCHAR_SIZE_WARNING
6485 @kindex --no-wchar-size-warning
6486 The @option{--no-wchar-size-warning} switch prevents the linker from
6487 warning when linking object files that specify incompatible EABI
6488 @code{wchar_t} size attributes. For example, with this switch enabled,
6489 linking of an object file using 32-bit @code{wchar_t} values with another
6490 using 16-bit @code{wchar_t} values will not be diagnosed.
6493 @kindex --pic-veneer
6494 The @samp{--pic-veneer} switch makes the linker use PIC sequences for
6495 ARM/Thumb interworking veneers, even if the rest of the binary
6496 is not PIC. This avoids problems on uClinux targets where
6497 @samp{--emit-relocs} is used to generate relocatable binaries.
6499 @cindex STUB_GROUP_SIZE
6500 @kindex --stub-group-size=@var{N}
6501 The linker will automatically generate and insert small sequences of
6502 code into a linked ARM ELF executable whenever an attempt is made to
6503 perform a function call to a symbol that is too far away. The
6504 placement of these sequences of instructions - called stubs - is
6505 controlled by the command line option @option{--stub-group-size=N}.
6506 The placement is important because a poor choice can create a need for
6507 duplicate stubs, increasing the code size. The linker will try to
6508 group stubs together in order to reduce interruptions to the flow of
6509 code, but it needs guidance as to how big these groups should be and
6510 where they should be placed.
6512 The value of @samp{N}, the parameter to the
6513 @option{--stub-group-size=} option controls where the stub groups are
6514 placed. If it is negative then all stubs are placed after the first
6515 branch that needs them. If it is positive then the stubs can be
6516 placed either before or after the branches that need them. If the
6517 value of @samp{N} is 1 (either +1 or -1) then the linker will choose
6518 exactly where to place groups of stubs, using its built in heuristics.
6519 A value of @samp{N} greater than 1 (or smaller than -1) tells the
6520 linker that a single group of stubs can service at most @samp{N} bytes
6521 from the input sections.
6523 The default, if @option{--stub-group-size=} is not specified, is
6526 Farcalls stubs insertion is fully supported for the ARM-EABI target
6527 only, because it relies on object files properties not present
6530 @cindex Cortex-A8 erratum workaround
6531 @kindex --fix-cortex-a8
6532 @kindex --no-fix-cortex-a8
6533 The @samp{--fix-cortex-a8} switch enables a link-time workaround for an erratum in certain Cortex-A8 processors. The workaround is enabled by default if you are targeting the ARM v7-A architecture profile. It can be enabled otherwise by specifying @samp{--fix-cortex-a8}, or disabled unconditionally by specifying @samp{--no-fix-cortex-a8}.
6535 The erratum only affects Thumb-2 code. Please contact ARM for further details.
6537 @kindex --merge-exidx-entries
6538 @kindex --no-merge-exidx-entries
6539 @cindex Merging exidx entries
6540 The @samp{--no-merge-exidx-entries} switch disables the merging of adjacent exidx entries in debuginfo.
6543 @cindex 32-bit PLT entries
6544 The @samp{--long-plt} option enables the use of 16 byte PLT entries
6545 which support up to 4Gb of code. The default is to use 12 byte PLT
6546 entries which only support 512Mb of code.
6559 @section @command{ld} and HPPA 32-bit ELF Support
6560 @cindex HPPA multiple sub-space stubs
6561 @kindex --multi-subspace
6562 When generating a shared library, @command{ld} will by default generate
6563 import stubs suitable for use with a single sub-space application.
6564 The @samp{--multi-subspace} switch causes @command{ld} to generate export
6565 stubs, and different (larger) import stubs suitable for use with
6566 multiple sub-spaces.
6568 @cindex HPPA stub grouping
6569 @kindex --stub-group-size=@var{N}
6570 Long branch stubs and import/export stubs are placed by @command{ld} in
6571 stub sections located between groups of input sections.
6572 @samp{--stub-group-size} specifies the maximum size of a group of input
6573 sections handled by one stub section. Since branch offsets are signed,
6574 a stub section may serve two groups of input sections, one group before
6575 the stub section, and one group after it. However, when using
6576 conditional branches that require stubs, it may be better (for branch
6577 prediction) that stub sections only serve one group of input sections.
6578 A negative value for @samp{N} chooses this scheme, ensuring that
6579 branches to stubs always use a negative offset. Two special values of
6580 @samp{N} are recognized, @samp{1} and @samp{-1}. These both instruct
6581 @command{ld} to automatically size input section groups for the branch types
6582 detected, with the same behaviour regarding stub placement as other
6583 positive or negative values of @samp{N} respectively.
6585 Note that @samp{--stub-group-size} does not split input sections. A
6586 single input section larger than the group size specified will of course
6587 create a larger group (of one section). If input sections are too
6588 large, it may not be possible for a branch to reach its stub.
6601 @section @command{ld} and the Motorola 68K family
6603 @cindex Motorola 68K GOT generation
6604 @kindex --got=@var{type}
6605 The @samp{--got=@var{type}} option lets you choose the GOT generation scheme.
6606 The choices are @samp{single}, @samp{negative}, @samp{multigot} and
6607 @samp{target}. When @samp{target} is selected the linker chooses
6608 the default GOT generation scheme for the current target.
6609 @samp{single} tells the linker to generate a single GOT with
6610 entries only at non-negative offsets.
6611 @samp{negative} instructs the linker to generate a single GOT with
6612 entries at both negative and positive offsets. Not all environments
6614 @samp{multigot} allows the linker to generate several GOTs in the
6615 output file. All GOT references from a single input object
6616 file access the same GOT, but references from different input object
6617 files might access different GOTs. Not all environments support such GOTs.
6630 @section @command{ld} and the MIPS family
6632 @cindex MIPS microMIPS instruction choice selection
6635 The @samp{--insn32} and @samp{--no-insn32} options control the choice of
6636 microMIPS instructions used in code generated by the linker, such as that
6637 in the PLT or lazy binding stubs, or in relaxation. If @samp{--insn32} is
6638 used, then the linker only uses 32-bit instruction encodings. By default
6639 or if @samp{--no-insn32} is used, all instruction encodings are used,
6640 including 16-bit ones where possible.
6653 @section @code{ld} and MMIX
6654 For MMIX, there is a choice of generating @code{ELF} object files or
6655 @code{mmo} object files when linking. The simulator @code{mmix}
6656 understands the @code{mmo} format. The binutils @code{objcopy} utility
6657 can translate between the two formats.
6659 There is one special section, the @samp{.MMIX.reg_contents} section.
6660 Contents in this section is assumed to correspond to that of global
6661 registers, and symbols referring to it are translated to special symbols,
6662 equal to registers. In a final link, the start address of the
6663 @samp{.MMIX.reg_contents} section corresponds to the first allocated
6664 global register multiplied by 8. Register @code{$255} is not included in
6665 this section; it is always set to the program entry, which is at the
6666 symbol @code{Main} for @code{mmo} files.
6668 Global symbols with the prefix @code{__.MMIX.start.}, for example
6669 @code{__.MMIX.start..text} and @code{__.MMIX.start..data} are special.
6670 The default linker script uses these to set the default start address
6673 Initial and trailing multiples of zero-valued 32-bit words in a section,
6674 are left out from an mmo file.
6687 @section @code{ld} and MSP430
6688 For the MSP430 it is possible to select the MPU architecture. The flag @samp{-m [mpu type]}
6689 will select an appropriate linker script for selected MPU type. (To get a list of known MPUs
6690 just pass @samp{-m help} option to the linker).
6692 @cindex MSP430 extra sections
6693 The linker will recognize some extra sections which are MSP430 specific:
6696 @item @samp{.vectors}
6697 Defines a portion of ROM where interrupt vectors located.
6699 @item @samp{.bootloader}
6700 Defines the bootloader portion of the ROM (if applicable). Any code
6701 in this section will be uploaded to the MPU.
6703 @item @samp{.infomem}
6704 Defines an information memory section (if applicable). Any code in
6705 this section will be uploaded to the MPU.
6707 @item @samp{.infomemnobits}
6708 This is the same as the @samp{.infomem} section except that any code
6709 in this section will not be uploaded to the MPU.
6711 @item @samp{.noinit}
6712 Denotes a portion of RAM located above @samp{.bss} section.
6714 The last two sections are used by gcc.
6728 @section @code{ld} and NDS32
6729 @kindex relaxing on NDS32
6730 For NDS32, there are some options to select relaxation behavior. The linker
6731 relaxes objects according to these options.
6734 @item @samp{--m[no-]fp-as-gp}
6735 Disable/enable fp-as-gp relaxation.
6737 @item @samp{--mexport-symbols=FILE}
6738 Exporting symbols and their address into FILE as linker script.
6740 @item @samp{--m[no-]ex9}
6741 Disable/enable link-time EX9 relaxation.
6743 @item @samp{--mexport-ex9=FILE}
6744 Export the EX9 table after linking.
6746 @item @samp{--mimport-ex9=FILE}
6747 Import the Ex9 table for EX9 relaxation.
6749 @item @samp{--mupdate-ex9}
6750 Update the existing EX9 table.
6752 @item @samp{--mex9-limit=NUM}
6753 Maximum number of entries in the ex9 table.
6755 @item @samp{--mex9-loop-aware}
6756 Avoid generating the EX9 instruction inside the loop.
6758 @item @samp{--m[no-]ifc}
6759 Disable/enable the link-time IFC optimization.
6761 @item @samp{--mifc-loop-aware}
6762 Avoid generating the IFC instruction inside the loop.
6776 @section @command{ld} and the Altera Nios II
6777 @cindex Nios II call relaxation
6778 @kindex --relax on Nios II
6780 Call and immediate jump instructions on Nios II processors are limited to
6781 transferring control to addresses in the same 256MB memory segment,
6782 which may result in @command{ld} giving
6783 @samp{relocation truncated to fit} errors with very large programs.
6784 The command-line option @option{--relax} enables the generation of
6785 trampolines that can access the entire 32-bit address space for calls
6786 outside the normal @code{call} and @code{jmpi} address range. These
6787 trampolines are inserted at section boundaries, so may not themselves
6788 be reachable if an input section and its associated call trampolines are
6791 The @option{--relax} option is enabled by default unless @option{-r}
6792 is also specified. You can disable trampoline generation by using the
6793 @option{--no-relax} linker option. You can also disable this optimization
6794 locally by using the @samp{set .noat} directive in assembly-language
6795 source files, as the linker-inserted trampolines use the @code{at}
6796 register as a temporary.
6798 Note that the linker @option{--relax} option is independent of assembler
6799 relaxation options, and that using the GNU assembler's @option{-relax-all}
6800 option interferes with the linker's more selective call instruction relaxation.
6813 @section @command{ld} and PowerPC 32-bit ELF Support
6814 @cindex PowerPC long branches
6815 @kindex --relax on PowerPC
6816 Branches on PowerPC processors are limited to a signed 26-bit
6817 displacement, which may result in @command{ld} giving
6818 @samp{relocation truncated to fit} errors with very large programs.
6819 @samp{--relax} enables the generation of trampolines that can access
6820 the entire 32-bit address space. These trampolines are inserted at
6821 section boundaries, so may not themselves be reachable if an input
6822 section exceeds 33M in size. You may combine @samp{-r} and
6823 @samp{--relax} to add trampolines in a partial link. In that case
6824 both branches to undefined symbols and inter-section branches are also
6825 considered potentially out of range, and trampolines inserted.
6827 @cindex PowerPC ELF32 options
6832 Current PowerPC GCC accepts a @samp{-msecure-plt} option that
6833 generates code capable of using a newer PLT and GOT layout that has
6834 the security advantage of no executable section ever needing to be
6835 writable and no writable section ever being executable. PowerPC
6836 @command{ld} will generate this layout, including stubs to access the
6837 PLT, if all input files (including startup and static libraries) were
6838 compiled with @samp{-msecure-plt}. @samp{--bss-plt} forces the old
6839 BSS PLT (and GOT layout) which can give slightly better performance.
6841 @kindex --secure-plt
6843 @command{ld} will use the new PLT and GOT layout if it is linking new
6844 @samp{-fpic} or @samp{-fPIC} code, but does not do so automatically
6845 when linking non-PIC code. This option requests the new PLT and GOT
6846 layout. A warning will be given if some object file requires the old
6852 The new secure PLT and GOT are placed differently relative to other
6853 sections compared to older BSS PLT and GOT placement. The location of
6854 @code{.plt} must change because the new secure PLT is an initialized
6855 section while the old PLT is uninitialized. The reason for the
6856 @code{.got} change is more subtle: The new placement allows
6857 @code{.got} to be read-only in applications linked with
6858 @samp{-z relro -z now}. However, this placement means that
6859 @code{.sdata} cannot always be used in shared libraries, because the
6860 PowerPC ABI accesses @code{.sdata} in shared libraries from the GOT
6861 pointer. @samp{--sdata-got} forces the old GOT placement. PowerPC
6862 GCC doesn't use @code{.sdata} in shared libraries, so this option is
6863 really only useful for other compilers that may do so.
6865 @cindex PowerPC stub symbols
6866 @kindex --emit-stub-syms
6867 @item --emit-stub-syms
6868 This option causes @command{ld} to label linker stubs with a local
6869 symbol that encodes the stub type and destination.
6871 @cindex PowerPC TLS optimization
6872 @kindex --no-tls-optimize
6873 @item --no-tls-optimize
6874 PowerPC @command{ld} normally performs some optimization of code
6875 sequences used to access Thread-Local Storage. Use this option to
6876 disable the optimization.
6889 @node PowerPC64 ELF64
6890 @section @command{ld} and PowerPC64 64-bit ELF Support
6892 @cindex PowerPC64 ELF64 options
6894 @cindex PowerPC64 stub grouping
6895 @kindex --stub-group-size
6896 @item --stub-group-size
6897 Long branch stubs, PLT call stubs and TOC adjusting stubs are placed
6898 by @command{ld} in stub sections located between groups of input sections.
6899 @samp{--stub-group-size} specifies the maximum size of a group of input
6900 sections handled by one stub section. Since branch offsets are signed,
6901 a stub section may serve two groups of input sections, one group before
6902 the stub section, and one group after it. However, when using
6903 conditional branches that require stubs, it may be better (for branch
6904 prediction) that stub sections only serve one group of input sections.
6905 A negative value for @samp{N} chooses this scheme, ensuring that
6906 branches to stubs always use a negative offset. Two special values of
6907 @samp{N} are recognized, @samp{1} and @samp{-1}. These both instruct
6908 @command{ld} to automatically size input section groups for the branch types
6909 detected, with the same behaviour regarding stub placement as other
6910 positive or negative values of @samp{N} respectively.
6912 Note that @samp{--stub-group-size} does not split input sections. A
6913 single input section larger than the group size specified will of course
6914 create a larger group (of one section). If input sections are too
6915 large, it may not be possible for a branch to reach its stub.
6917 @cindex PowerPC64 stub symbols
6918 @kindex --emit-stub-syms
6919 @item --emit-stub-syms
6920 This option causes @command{ld} to label linker stubs with a local
6921 symbol that encodes the stub type and destination.
6923 @cindex PowerPC64 dot symbols
6925 @kindex --no-dotsyms
6926 @item --dotsyms, --no-dotsyms
6927 These two options control how @command{ld} interprets version patterns
6928 in a version script. Older PowerPC64 compilers emitted both a
6929 function descriptor symbol with the same name as the function, and a
6930 code entry symbol with the name prefixed by a dot (@samp{.}). To
6931 properly version a function @samp{foo}, the version script thus needs
6932 to control both @samp{foo} and @samp{.foo}. The option
6933 @samp{--dotsyms}, on by default, automatically adds the required
6934 dot-prefixed patterns. Use @samp{--no-dotsyms} to disable this
6937 @cindex PowerPC64 TLS optimization
6938 @kindex --no-tls-optimize
6939 @item --no-tls-optimize
6940 PowerPC64 @command{ld} normally performs some optimization of code
6941 sequences used to access Thread-Local Storage. Use this option to
6942 disable the optimization.
6944 @cindex PowerPC64 OPD optimization
6945 @kindex --no-opd-optimize
6946 @item --no-opd-optimize
6947 PowerPC64 @command{ld} normally removes @code{.opd} section entries
6948 corresponding to deleted link-once functions, or functions removed by
6949 the action of @samp{--gc-sections} or linker script @code{/DISCARD/}.
6950 Use this option to disable @code{.opd} optimization.
6952 @cindex PowerPC64 OPD spacing
6953 @kindex --non-overlapping-opd
6954 @item --non-overlapping-opd
6955 Some PowerPC64 compilers have an option to generate compressed
6956 @code{.opd} entries spaced 16 bytes apart, overlapping the third word,
6957 the static chain pointer (unused in C) with the first word of the next
6958 entry. This option expands such entries to the full 24 bytes.
6960 @cindex PowerPC64 TOC optimization
6961 @kindex --no-toc-optimize
6962 @item --no-toc-optimize
6963 PowerPC64 @command{ld} normally removes unused @code{.toc} section
6964 entries. Such entries are detected by examining relocations that
6965 reference the TOC in code sections. A reloc in a deleted code section
6966 marks a TOC word as unneeded, while a reloc in a kept code section
6967 marks a TOC word as needed. Since the TOC may reference itself, TOC
6968 relocs are also examined. TOC words marked as both needed and
6969 unneeded will of course be kept. TOC words without any referencing
6970 reloc are assumed to be part of a multi-word entry, and are kept or
6971 discarded as per the nearest marked preceding word. This works
6972 reliably for compiler generated code, but may be incorrect if assembly
6973 code is used to insert TOC entries. Use this option to disable the
6976 @cindex PowerPC64 multi-TOC
6977 @kindex --no-multi-toc
6978 @item --no-multi-toc
6979 If given any toc option besides @code{-mcmodel=medium} or
6980 @code{-mcmodel=large}, PowerPC64 GCC generates code for a TOC model
6982 entries are accessed with a 16-bit offset from r2. This limits the
6983 total TOC size to 64K. PowerPC64 @command{ld} extends this limit by
6984 grouping code sections such that each group uses less than 64K for its
6985 TOC entries, then inserts r2 adjusting stubs between inter-group
6986 calls. @command{ld} does not split apart input sections, so cannot
6987 help if a single input file has a @code{.toc} section that exceeds
6988 64K, most likely from linking multiple files with @command{ld -r}.
6989 Use this option to turn off this feature.
6991 @cindex PowerPC64 TOC sorting
6992 @kindex --no-toc-sort
6994 By default, @command{ld} sorts TOC sections so that those whose file
6995 happens to have a section called @code{.init} or @code{.fini} are
6996 placed first, followed by TOC sections referenced by code generated
6997 with PowerPC64 gcc's @code{-mcmodel=small}, and lastly TOC sections
6998 referenced only by code generated with PowerPC64 gcc's
6999 @code{-mcmodel=medium} or @code{-mcmodel=large} options. Doing this
7000 results in better TOC grouping for multi-TOC. Use this option to turn
7003 @cindex PowerPC64 PLT stub alignment
7005 @kindex --no-plt-align
7007 @itemx --no-plt-align
7008 Use these options to control whether individual PLT call stubs are
7009 aligned to a 32-byte boundary, or to the specified power of two
7010 boundary when using @code{--plt-align=}. By default PLT call stubs
7013 @cindex PowerPC64 PLT call stub static chain
7014 @kindex --plt-static-chain
7015 @kindex --no-plt-static-chain
7016 @item --plt-static-chain
7017 @itemx --no-plt-static-chain
7018 Use these options to control whether PLT call stubs load the static
7019 chain pointer (r11). @code{ld} defaults to not loading the static
7020 chain since there is never any need to do so on a PLT call.
7022 @cindex PowerPC64 PLT call stub thread safety
7023 @kindex --plt-thread-safe
7024 @kindex --no-plt-thread-safe
7025 @item --plt-thread-safe
7026 @itemx --no-thread-safe
7027 With power7's weakly ordered memory model, it is possible when using
7028 lazy binding for ld.so to update a plt entry in one thread and have
7029 another thread see the individual plt entry words update in the wrong
7030 order, despite ld.so carefully writing in the correct order and using
7031 memory write barriers. To avoid this we need some sort of read
7032 barrier in the call stub, or use LD_BIND_NOW=1. By default, @code{ld}
7033 looks for calls to commonly used functions that create threads, and if
7034 seen, adds the necessary barriers. Use these options to change the
7049 @section @command{ld} and SPU ELF Support
7051 @cindex SPU ELF options
7057 This option marks an executable as a PIC plugin module.
7059 @cindex SPU overlays
7060 @kindex --no-overlays
7062 Normally, @command{ld} recognizes calls to functions within overlay
7063 regions, and redirects such calls to an overlay manager via a stub.
7064 @command{ld} also provides a built-in overlay manager. This option
7065 turns off all this special overlay handling.
7067 @cindex SPU overlay stub symbols
7068 @kindex --emit-stub-syms
7069 @item --emit-stub-syms
7070 This option causes @command{ld} to label overlay stubs with a local
7071 symbol that encodes the stub type and destination.
7073 @cindex SPU extra overlay stubs
7074 @kindex --extra-overlay-stubs
7075 @item --extra-overlay-stubs
7076 This option causes @command{ld} to add overlay call stubs on all
7077 function calls out of overlay regions. Normally stubs are not added
7078 on calls to non-overlay regions.
7080 @cindex SPU local store size
7081 @kindex --local-store=lo:hi
7082 @item --local-store=lo:hi
7083 @command{ld} usually checks that a final executable for SPU fits in
7084 the address range 0 to 256k. This option may be used to change the
7085 range. Disable the check entirely with @option{--local-store=0:0}.
7088 @kindex --stack-analysis
7089 @item --stack-analysis
7090 SPU local store space is limited. Over-allocation of stack space
7091 unnecessarily limits space available for code and data, while
7092 under-allocation results in runtime failures. If given this option,
7093 @command{ld} will provide an estimate of maximum stack usage.
7094 @command{ld} does this by examining symbols in code sections to
7095 determine the extents of functions, and looking at function prologues
7096 for stack adjusting instructions. A call-graph is created by looking
7097 for relocations on branch instructions. The graph is then searched
7098 for the maximum stack usage path. Note that this analysis does not
7099 find calls made via function pointers, and does not handle recursion
7100 and other cycles in the call graph. Stack usage may be
7101 under-estimated if your code makes such calls. Also, stack usage for
7102 dynamic allocation, e.g. alloca, will not be detected. If a link map
7103 is requested, detailed information about each function's stack usage
7104 and calls will be given.
7107 @kindex --emit-stack-syms
7108 @item --emit-stack-syms
7109 This option, if given along with @option{--stack-analysis} will result
7110 in @command{ld} emitting stack sizing symbols for each function.
7111 These take the form @code{__stack_<function_name>} for global
7112 functions, and @code{__stack_<number>_<function_name>} for static
7113 functions. @code{<number>} is the section id in hex. The value of
7114 such symbols is the stack requirement for the corresponding function.
7115 The symbol size will be zero, type @code{STT_NOTYPE}, binding
7116 @code{STB_LOCAL}, and section @code{SHN_ABS}.
7130 @section @command{ld}'s Support for Various TI COFF Versions
7131 @cindex TI COFF versions
7132 @kindex --format=@var{version}
7133 The @samp{--format} switch allows selection of one of the various
7134 TI COFF versions. The latest of this writing is 2; versions 0 and 1 are
7135 also supported. The TI COFF versions also vary in header byte-order
7136 format; @command{ld} will read any version or byte order, but the output
7137 header format depends on the default specified by the specific target.
7150 @section @command{ld} and WIN32 (cygwin/mingw)
7152 This section describes some of the win32 specific @command{ld} issues.
7153 See @ref{Options,,Command Line Options} for detailed description of the
7154 command line options mentioned here.
7157 @cindex import libraries
7158 @item import libraries
7159 The standard Windows linker creates and uses so-called import
7160 libraries, which contains information for linking to dll's. They are
7161 regular static archives and are handled as any other static
7162 archive. The cygwin and mingw ports of @command{ld} have specific
7163 support for creating such libraries provided with the
7164 @samp{--out-implib} command line option.
7166 @item exporting DLL symbols
7167 @cindex exporting DLL symbols
7168 The cygwin/mingw @command{ld} has several ways to export symbols for dll's.
7171 @item using auto-export functionality
7172 @cindex using auto-export functionality
7173 By default @command{ld} exports symbols with the auto-export functionality,
7174 which is controlled by the following command line options:
7177 @item --export-all-symbols [This is the default]
7178 @item --exclude-symbols
7179 @item --exclude-libs
7180 @item --exclude-modules-for-implib
7181 @item --version-script
7184 When auto-export is in operation, @command{ld} will export all the non-local
7185 (global and common) symbols it finds in a DLL, with the exception of a few
7186 symbols known to belong to the system's runtime and libraries. As it will
7187 often not be desirable to export all of a DLL's symbols, which may include
7188 private functions that are not part of any public interface, the command-line
7189 options listed above may be used to filter symbols out from the list for
7190 exporting. The @samp{--output-def} option can be used in order to see the
7191 final list of exported symbols with all exclusions taken into effect.
7193 If @samp{--export-all-symbols} is not given explicitly on the
7194 command line, then the default auto-export behavior will be @emph{disabled}
7195 if either of the following are true:
7198 @item A DEF file is used.
7199 @item Any symbol in any object file was marked with the __declspec(dllexport) attribute.
7202 @item using a DEF file
7203 @cindex using a DEF file
7204 Another way of exporting symbols is using a DEF file. A DEF file is
7205 an ASCII file containing definitions of symbols which should be
7206 exported when a dll is created. Usually it is named @samp{<dll
7207 name>.def} and is added as any other object file to the linker's
7208 command line. The file's name must end in @samp{.def} or @samp{.DEF}.
7211 gcc -o <output> <objectfiles> <dll name>.def
7214 Using a DEF file turns off the normal auto-export behavior, unless the
7215 @samp{--export-all-symbols} option is also used.
7217 Here is an example of a DEF file for a shared library called @samp{xyz.dll}:
7220 LIBRARY "xyz.dll" BASE=0x20000000
7226 another_foo = abc.dll.afoo
7232 This example defines a DLL with a non-default base address and seven
7233 symbols in the export table. The third exported symbol @code{_bar} is an
7234 alias for the second. The fourth symbol, @code{another_foo} is resolved
7235 by "forwarding" to another module and treating it as an alias for
7236 @code{afoo} exported from the DLL @samp{abc.dll}. The final symbol
7237 @code{var1} is declared to be a data object. The @samp{doo} symbol in
7238 export library is an alias of @samp{foo}, which gets the string name
7239 in export table @samp{foo2}. The @samp{eoo} symbol is an data export
7240 symbol, which gets in export table the name @samp{var1}.
7242 The optional @code{LIBRARY <name>} command indicates the @emph{internal}
7243 name of the output DLL. If @samp{<name>} does not include a suffix,
7244 the default library suffix, @samp{.DLL} is appended.
7246 When the .DEF file is used to build an application, rather than a
7247 library, the @code{NAME <name>} command should be used instead of
7248 @code{LIBRARY}. If @samp{<name>} does not include a suffix, the default
7249 executable suffix, @samp{.EXE} is appended.
7251 With either @code{LIBRARY <name>} or @code{NAME <name>} the optional
7252 specification @code{BASE = <number>} may be used to specify a
7253 non-default base address for the image.
7255 If neither @code{LIBRARY <name>} nor @code{NAME <name>} is specified,
7256 or they specify an empty string, the internal name is the same as the
7257 filename specified on the command line.
7259 The complete specification of an export symbol is:
7263 ( ( ( <name1> [ = <name2> ] )
7264 | ( <name1> = <module-name> . <external-name>))
7265 [ @@ <integer> ] [NONAME] [DATA] [CONSTANT] [PRIVATE] [== <name3>] ) *
7268 Declares @samp{<name1>} as an exported symbol from the DLL, or declares
7269 @samp{<name1>} as an exported alias for @samp{<name2>}; or declares
7270 @samp{<name1>} as a "forward" alias for the symbol
7271 @samp{<external-name>} in the DLL @samp{<module-name>}.
7272 Optionally, the symbol may be exported by the specified ordinal
7273 @samp{<integer>} alias. The optional @samp{<name3>} is the to be used
7274 string in import/export table for the symbol.
7276 The optional keywords that follow the declaration indicate:
7278 @code{NONAME}: Do not put the symbol name in the DLL's export table. It
7279 will still be exported by its ordinal alias (either the value specified
7280 by the .def specification or, otherwise, the value assigned by the
7281 linker). The symbol name, however, does remain visible in the import
7282 library (if any), unless @code{PRIVATE} is also specified.
7284 @code{DATA}: The symbol is a variable or object, rather than a function.
7285 The import lib will export only an indirect reference to @code{foo} as
7286 the symbol @code{_imp__foo} (ie, @code{foo} must be resolved as
7289 @code{CONSTANT}: Like @code{DATA}, but put the undecorated @code{foo} as
7290 well as @code{_imp__foo} into the import library. Both refer to the
7291 read-only import address table's pointer to the variable, not to the
7292 variable itself. This can be dangerous. If the user code fails to add
7293 the @code{dllimport} attribute and also fails to explicitly add the
7294 extra indirection that the use of the attribute enforces, the
7295 application will behave unexpectedly.
7297 @code{PRIVATE}: Put the symbol in the DLL's export table, but do not put
7298 it into the static import library used to resolve imports at link time. The
7299 symbol can still be imported using the @code{LoadLibrary/GetProcAddress}
7300 API at runtime or by by using the GNU ld extension of linking directly to
7301 the DLL without an import library.
7303 See ld/deffilep.y in the binutils sources for the full specification of
7304 other DEF file statements
7306 @cindex creating a DEF file
7307 While linking a shared dll, @command{ld} is able to create a DEF file
7308 with the @samp{--output-def <file>} command line option.
7310 @item Using decorations
7311 @cindex Using decorations
7312 Another way of marking symbols for export is to modify the source code
7313 itself, so that when building the DLL each symbol to be exported is
7317 __declspec(dllexport) int a_variable
7318 __declspec(dllexport) void a_function(int with_args)
7321 All such symbols will be exported from the DLL. If, however,
7322 any of the object files in the DLL contain symbols decorated in
7323 this way, then the normal auto-export behavior is disabled, unless
7324 the @samp{--export-all-symbols} option is also used.
7326 Note that object files that wish to access these symbols must @emph{not}
7327 decorate them with dllexport. Instead, they should use dllimport,
7331 __declspec(dllimport) int a_variable
7332 __declspec(dllimport) void a_function(int with_args)
7335 This complicates the structure of library header files, because
7336 when included by the library itself the header must declare the
7337 variables and functions as dllexport, but when included by client
7338 code the header must declare them as dllimport. There are a number
7339 of idioms that are typically used to do this; often client code can
7340 omit the __declspec() declaration completely. See
7341 @samp{--enable-auto-import} and @samp{automatic data imports} for more
7345 @cindex automatic data imports
7346 @item automatic data imports
7347 The standard Windows dll format supports data imports from dlls only
7348 by adding special decorations (dllimport/dllexport), which let the
7349 compiler produce specific assembler instructions to deal with this
7350 issue. This increases the effort necessary to port existing Un*x
7351 code to these platforms, especially for large
7352 c++ libraries and applications. The auto-import feature, which was
7353 initially provided by Paul Sokolovsky, allows one to omit the
7354 decorations to achieve a behavior that conforms to that on POSIX/Un*x
7355 platforms. This feature is enabled with the @samp{--enable-auto-import}
7356 command-line option, although it is enabled by default on cygwin/mingw.
7357 The @samp{--enable-auto-import} option itself now serves mainly to
7358 suppress any warnings that are ordinarily emitted when linked objects
7359 trigger the feature's use.
7361 auto-import of variables does not always work flawlessly without
7362 additional assistance. Sometimes, you will see this message
7364 "variable '<var>' can't be auto-imported. Please read the
7365 documentation for ld's @code{--enable-auto-import} for details."
7367 The @samp{--enable-auto-import} documentation explains why this error
7368 occurs, and several methods that can be used to overcome this difficulty.
7369 One of these methods is the @emph{runtime pseudo-relocs} feature, described
7372 @cindex runtime pseudo-relocation
7373 For complex variables imported from DLLs (such as structs or classes),
7374 object files typically contain a base address for the variable and an
7375 offset (@emph{addend}) within the variable--to specify a particular
7376 field or public member, for instance. Unfortunately, the runtime loader used
7377 in win32 environments is incapable of fixing these references at runtime
7378 without the additional information supplied by dllimport/dllexport decorations.
7379 The standard auto-import feature described above is unable to resolve these
7382 The @samp{--enable-runtime-pseudo-relocs} switch allows these references to
7383 be resolved without error, while leaving the task of adjusting the references
7384 themselves (with their non-zero addends) to specialized code provided by the
7385 runtime environment. Recent versions of the cygwin and mingw environments and
7386 compilers provide this runtime support; older versions do not. However, the
7387 support is only necessary on the developer's platform; the compiled result will
7388 run without error on an older system.
7390 @samp{--enable-runtime-pseudo-relocs} is not the default; it must be explicitly
7393 @cindex direct linking to a dll
7394 @item direct linking to a dll
7395 The cygwin/mingw ports of @command{ld} support the direct linking,
7396 including data symbols, to a dll without the usage of any import
7397 libraries. This is much faster and uses much less memory than does the
7398 traditional import library method, especially when linking large
7399 libraries or applications. When @command{ld} creates an import lib, each
7400 function or variable exported from the dll is stored in its own bfd, even
7401 though a single bfd could contain many exports. The overhead involved in
7402 storing, loading, and processing so many bfd's is quite large, and explains the
7403 tremendous time, memory, and storage needed to link against particularly
7404 large or complex libraries when using import libs.
7406 Linking directly to a dll uses no extra command-line switches other than
7407 @samp{-L} and @samp{-l}, because @command{ld} already searches for a number
7408 of names to match each library. All that is needed from the developer's
7409 perspective is an understanding of this search, in order to force ld to
7410 select the dll instead of an import library.
7413 For instance, when ld is called with the argument @samp{-lxxx} it will attempt
7414 to find, in the first directory of its search path,
7426 before moving on to the next directory in the search path.
7428 (*) Actually, this is not @samp{cygxxx.dll} but in fact is @samp{<prefix>xxx.dll},
7429 where @samp{<prefix>} is set by the @command{ld} option
7430 @samp{--dll-search-prefix=<prefix>}. In the case of cygwin, the standard gcc spec
7431 file includes @samp{--dll-search-prefix=cyg}, so in effect we actually search for
7434 Other win32-based unix environments, such as mingw or pw32, may use other
7435 @samp{<prefix>}es, although at present only cygwin makes use of this feature. It
7436 was originally intended to help avoid name conflicts among dll's built for the
7437 various win32/un*x environments, so that (for example) two versions of a zlib dll
7438 could coexist on the same machine.
7440 The generic cygwin/mingw path layout uses a @samp{bin} directory for
7441 applications and dll's and a @samp{lib} directory for the import
7442 libraries (using cygwin nomenclature):
7448 libxxx.dll.a (in case of dll's)
7449 libxxx.a (in case of static archive)
7452 Linking directly to a dll without using the import library can be
7455 1. Use the dll directly by adding the @samp{bin} path to the link line
7457 gcc -Wl,-verbose -o a.exe -L../bin/ -lxxx
7460 However, as the dll's often have version numbers appended to their names
7461 (@samp{cygncurses-5.dll}) this will often fail, unless one specifies
7462 @samp{-L../bin -lncurses-5} to include the version. Import libs are generally
7463 not versioned, and do not have this difficulty.
7465 2. Create a symbolic link from the dll to a file in the @samp{lib}
7466 directory according to the above mentioned search pattern. This
7467 should be used to avoid unwanted changes in the tools needed for
7471 ln -s bin/cygxxx.dll lib/[cyg|lib|]xxx.dll[.a]
7474 Then you can link without any make environment changes.
7477 gcc -Wl,-verbose -o a.exe -L../lib/ -lxxx
7480 This technique also avoids the version number problems, because the following is
7487 libxxx.dll.a -> ../bin/cygxxx-5.dll
7490 Linking directly to a dll without using an import lib will work
7491 even when auto-import features are exercised, and even when
7492 @samp{--enable-runtime-pseudo-relocs} is used.
7494 Given the improvements in speed and memory usage, one might justifiably
7495 wonder why import libraries are used at all. There are three reasons:
7497 1. Until recently, the link-directly-to-dll functionality did @emph{not}
7498 work with auto-imported data.
7500 2. Sometimes it is necessary to include pure static objects within the
7501 import library (which otherwise contains only bfd's for indirection
7502 symbols that point to the exports of a dll). Again, the import lib
7503 for the cygwin kernel makes use of this ability, and it is not
7504 possible to do this without an import lib.
7506 3. Symbol aliases can only be resolved using an import lib. This is
7507 critical when linking against OS-supplied dll's (eg, the win32 API)
7508 in which symbols are usually exported as undecorated aliases of their
7509 stdcall-decorated assembly names.
7511 So, import libs are not going away. But the ability to replace
7512 true import libs with a simple symbolic link to (or a copy of)
7513 a dll, in many cases, is a useful addition to the suite of tools
7514 binutils makes available to the win32 developer. Given the
7515 massive improvements in memory requirements during linking, storage
7516 requirements, and linking speed, we expect that many developers
7517 will soon begin to use this feature whenever possible.
7519 @item symbol aliasing
7521 @item adding additional names
7522 Sometimes, it is useful to export symbols with additional names.
7523 A symbol @samp{foo} will be exported as @samp{foo}, but it can also be
7524 exported as @samp{_foo} by using special directives in the DEF file
7525 when creating the dll. This will affect also the optional created
7526 import library. Consider the following DEF file:
7529 LIBRARY "xyz.dll" BASE=0x61000000
7536 The line @samp{_foo = foo} maps the symbol @samp{foo} to @samp{_foo}.
7538 Another method for creating a symbol alias is to create it in the
7539 source code using the "weak" attribute:
7542 void foo () @{ /* Do something. */; @}
7543 void _foo () __attribute__ ((weak, alias ("foo")));
7546 See the gcc manual for more information about attributes and weak
7549 @item renaming symbols
7550 Sometimes it is useful to rename exports. For instance, the cygwin
7551 kernel does this regularly. A symbol @samp{_foo} can be exported as
7552 @samp{foo} but not as @samp{_foo} by using special directives in the
7553 DEF file. (This will also affect the import library, if it is
7554 created). In the following example:
7557 LIBRARY "xyz.dll" BASE=0x61000000
7563 The line @samp{_foo = foo} maps the exported symbol @samp{foo} to
7567 Note: using a DEF file disables the default auto-export behavior,
7568 unless the @samp{--export-all-symbols} command line option is used.
7569 If, however, you are trying to rename symbols, then you should list
7570 @emph{all} desired exports in the DEF file, including the symbols
7571 that are not being renamed, and do @emph{not} use the
7572 @samp{--export-all-symbols} option. If you list only the
7573 renamed symbols in the DEF file, and use @samp{--export-all-symbols}
7574 to handle the other symbols, then the both the new names @emph{and}
7575 the original names for the renamed symbols will be exported.
7576 In effect, you'd be aliasing those symbols, not renaming them,
7577 which is probably not what you wanted.
7579 @cindex weak externals
7580 @item weak externals
7581 The Windows object format, PE, specifies a form of weak symbols called
7582 weak externals. When a weak symbol is linked and the symbol is not
7583 defined, the weak symbol becomes an alias for some other symbol. There
7584 are three variants of weak externals:
7586 @item Definition is searched for in objects and libraries, historically
7587 called lazy externals.
7588 @item Definition is searched for only in other objects, not in libraries.
7589 This form is not presently implemented.
7590 @item No search; the symbol is an alias. This form is not presently
7593 As a GNU extension, weak symbols that do not specify an alternate symbol
7594 are supported. If the symbol is undefined when linking, the symbol
7595 uses a default value.
7597 @cindex aligned common symbols
7598 @item aligned common symbols
7599 As a GNU extension to the PE file format, it is possible to specify the
7600 desired alignment for a common symbol. This information is conveyed from
7601 the assembler or compiler to the linker by means of GNU-specific commands
7602 carried in the object file's @samp{.drectve} section, which are recognized
7603 by @command{ld} and respected when laying out the common symbols. Native
7604 tools will be able to process object files employing this GNU extension,
7605 but will fail to respect the alignment instructions, and may issue noisy
7606 warnings about unknown linker directives.
7621 @section @code{ld} and Xtensa Processors
7623 @cindex Xtensa processors
7624 The default @command{ld} behavior for Xtensa processors is to interpret
7625 @code{SECTIONS} commands so that lists of explicitly named sections in a
7626 specification with a wildcard file will be interleaved when necessary to
7627 keep literal pools within the range of PC-relative load offsets. For
7628 example, with the command:
7640 @command{ld} may interleave some of the @code{.literal}
7641 and @code{.text} sections from different object files to ensure that the
7642 literal pools are within the range of PC-relative load offsets. A valid
7643 interleaving might place the @code{.literal} sections from an initial
7644 group of files followed by the @code{.text} sections of that group of
7645 files. Then, the @code{.literal} sections from the rest of the files
7646 and the @code{.text} sections from the rest of the files would follow.
7648 @cindex @option{--relax} on Xtensa
7649 @cindex relaxing on Xtensa
7650 Relaxation is enabled by default for the Xtensa version of @command{ld} and
7651 provides two important link-time optimizations. The first optimization
7652 is to combine identical literal values to reduce code size. A redundant
7653 literal will be removed and all the @code{L32R} instructions that use it
7654 will be changed to reference an identical literal, as long as the
7655 location of the replacement literal is within the offset range of all
7656 the @code{L32R} instructions. The second optimization is to remove
7657 unnecessary overhead from assembler-generated ``longcall'' sequences of
7658 @code{L32R}/@code{CALLX@var{n}} when the target functions are within
7659 range of direct @code{CALL@var{n}} instructions.
7661 For each of these cases where an indirect call sequence can be optimized
7662 to a direct call, the linker will change the @code{CALLX@var{n}}
7663 instruction to a @code{CALL@var{n}} instruction, remove the @code{L32R}
7664 instruction, and remove the literal referenced by the @code{L32R}
7665 instruction if it is not used for anything else. Removing the
7666 @code{L32R} instruction always reduces code size but can potentially
7667 hurt performance by changing the alignment of subsequent branch targets.
7668 By default, the linker will always preserve alignments, either by
7669 switching some instructions between 24-bit encodings and the equivalent
7670 density instructions or by inserting a no-op in place of the @code{L32R}
7671 instruction that was removed. If code size is more important than
7672 performance, the @option{--size-opt} option can be used to prevent the
7673 linker from widening density instructions or inserting no-ops, except in
7674 a few cases where no-ops are required for correctness.
7676 The following Xtensa-specific command-line options can be used to
7679 @cindex Xtensa options
7682 When optimizing indirect calls to direct calls, optimize for code size
7683 more than performance. With this option, the linker will not insert
7684 no-ops or widen density instructions to preserve branch target
7685 alignment. There may still be some cases where no-ops are required to
7686 preserve the correctness of the code.
7694 @ifclear SingleFormat
7699 @cindex object file management
7700 @cindex object formats available
7702 The linker accesses object and archive files using the BFD libraries.
7703 These libraries allow the linker to use the same routines to operate on
7704 object files whatever the object file format. A different object file
7705 format can be supported simply by creating a new BFD back end and adding
7706 it to the library. To conserve runtime memory, however, the linker and
7707 associated tools are usually configured to support only a subset of the
7708 object file formats available. You can use @code{objdump -i}
7709 (@pxref{objdump,,objdump,binutils.info,The GNU Binary Utilities}) to
7710 list all the formats available for your configuration.
7712 @cindex BFD requirements
7713 @cindex requirements for BFD
7714 As with most implementations, BFD is a compromise between
7715 several conflicting requirements. The major factor influencing
7716 BFD design was efficiency: any time used converting between
7717 formats is time which would not have been spent had BFD not
7718 been involved. This is partly offset by abstraction payback; since
7719 BFD simplifies applications and back ends, more time and care
7720 may be spent optimizing algorithms for a greater speed.
7722 One minor artifact of the BFD solution which you should bear in
7723 mind is the potential for information loss. There are two places where
7724 useful information can be lost using the BFD mechanism: during
7725 conversion and during output. @xref{BFD information loss}.
7728 * BFD outline:: How it works: an outline of BFD
7732 @section How It Works: An Outline of BFD
7733 @cindex opening object files
7734 @include bfdsumm.texi
7737 @node Reporting Bugs
7738 @chapter Reporting Bugs
7739 @cindex bugs in @command{ld}
7740 @cindex reporting bugs in @command{ld}
7742 Your bug reports play an essential role in making @command{ld} reliable.
7744 Reporting a bug may help you by bringing a solution to your problem, or
7745 it may not. But in any case the principal function of a bug report is
7746 to help the entire community by making the next version of @command{ld}
7747 work better. Bug reports are your contribution to the maintenance of
7750 In order for a bug report to serve its purpose, you must include the
7751 information that enables us to fix the bug.
7754 * Bug Criteria:: Have you found a bug?
7755 * Bug Reporting:: How to report bugs
7759 @section Have You Found a Bug?
7760 @cindex bug criteria
7762 If you are not sure whether you have found a bug, here are some guidelines:
7765 @cindex fatal signal
7766 @cindex linker crash
7767 @cindex crash of linker
7769 If the linker gets a fatal signal, for any input whatever, that is a
7770 @command{ld} bug. Reliable linkers never crash.
7772 @cindex error on valid input
7774 If @command{ld} produces an error message for valid input, that is a bug.
7776 @cindex invalid input
7778 If @command{ld} does not produce an error message for invalid input, that
7779 may be a bug. In the general case, the linker can not verify that
7780 object files are correct.
7783 If you are an experienced user of linkers, your suggestions for
7784 improvement of @command{ld} are welcome in any case.
7788 @section How to Report Bugs
7790 @cindex @command{ld} bugs, reporting
7792 A number of companies and individuals offer support for @sc{gnu}
7793 products. If you obtained @command{ld} from a support organization, we
7794 recommend you contact that organization first.
7796 You can find contact information for many support companies and
7797 individuals in the file @file{etc/SERVICE} in the @sc{gnu} Emacs
7801 Otherwise, send bug reports for @command{ld} to
7805 The fundamental principle of reporting bugs usefully is this:
7806 @strong{report all the facts}. If you are not sure whether to state a
7807 fact or leave it out, state it!
7809 Often people omit facts because they think they know what causes the
7810 problem and assume that some details do not matter. Thus, you might
7811 assume that the name of a symbol you use in an example does not
7812 matter. Well, probably it does not, but one cannot be sure. Perhaps
7813 the bug is a stray memory reference which happens to fetch from the
7814 location where that name is stored in memory; perhaps, if the name
7815 were different, the contents of that location would fool the linker
7816 into doing the right thing despite the bug. Play it safe and give a
7817 specific, complete example. That is the easiest thing for you to do,
7818 and the most helpful.
7820 Keep in mind that the purpose of a bug report is to enable us to fix
7821 the bug if it is new to us. Therefore, always write your bug reports
7822 on the assumption that the bug has not been reported previously.
7824 Sometimes people give a few sketchy facts and ask, ``Does this ring a
7825 bell?'' This cannot help us fix a bug, so it is basically useless. We
7826 respond by asking for enough details to enable us to investigate.
7827 You might as well expedite matters by sending them to begin with.
7829 To enable us to fix the bug, you should include all these things:
7833 The version of @command{ld}. @command{ld} announces it if you start it with
7834 the @samp{--version} argument.
7836 Without this, we will not know whether there is any point in looking for
7837 the bug in the current version of @command{ld}.
7840 Any patches you may have applied to the @command{ld} source, including any
7841 patches made to the @code{BFD} library.
7844 The type of machine you are using, and the operating system name and
7848 What compiler (and its version) was used to compile @command{ld}---e.g.
7852 The command arguments you gave the linker to link your example and
7853 observe the bug. To guarantee you will not omit something important,
7854 list them all. A copy of the Makefile (or the output from make) is
7857 If we were to try to guess the arguments, we would probably guess wrong
7858 and then we might not encounter the bug.
7861 A complete input file, or set of input files, that will reproduce the
7862 bug. It is generally most helpful to send the actual object files
7863 provided that they are reasonably small. Say no more than 10K. For
7864 bigger files you can either make them available by FTP or HTTP or else
7865 state that you are willing to send the object file(s) to whomever
7866 requests them. (Note - your email will be going to a mailing list, so
7867 we do not want to clog it up with large attachments). But small
7868 attachments are best.
7870 If the source files were assembled using @code{gas} or compiled using
7871 @code{gcc}, then it may be OK to send the source files rather than the
7872 object files. In this case, be sure to say exactly what version of
7873 @code{gas} or @code{gcc} was used to produce the object files. Also say
7874 how @code{gas} or @code{gcc} were configured.
7877 A description of what behavior you observe that you believe is
7878 incorrect. For example, ``It gets a fatal signal.''
7880 Of course, if the bug is that @command{ld} gets a fatal signal, then we
7881 will certainly notice it. But if the bug is incorrect output, we might
7882 not notice unless it is glaringly wrong. You might as well not give us
7883 a chance to make a mistake.
7885 Even if the problem you experience is a fatal signal, you should still
7886 say so explicitly. Suppose something strange is going on, such as, your
7887 copy of @command{ld} is out of sync, or you have encountered a bug in the
7888 C library on your system. (This has happened!) Your copy might crash
7889 and ours would not. If you told us to expect a crash, then when ours
7890 fails to crash, we would know that the bug was not happening for us. If
7891 you had not told us to expect a crash, then we would not be able to draw
7892 any conclusion from our observations.
7895 If you wish to suggest changes to the @command{ld} source, send us context
7896 diffs, as generated by @code{diff} with the @samp{-u}, @samp{-c}, or
7897 @samp{-p} option. Always send diffs from the old file to the new file.
7898 If you even discuss something in the @command{ld} source, refer to it by
7899 context, not by line number.
7901 The line numbers in our development sources will not match those in your
7902 sources. Your line numbers would convey no useful information to us.
7905 Here are some things that are not necessary:
7909 A description of the envelope of the bug.
7911 Often people who encounter a bug spend a lot of time investigating
7912 which changes to the input file will make the bug go away and which
7913 changes will not affect it.
7915 This is often time consuming and not very useful, because the way we
7916 will find the bug is by running a single example under the debugger
7917 with breakpoints, not by pure deduction from a series of examples.
7918 We recommend that you save your time for something else.
7920 Of course, if you can find a simpler example to report @emph{instead}
7921 of the original one, that is a convenience for us. Errors in the
7922 output will be easier to spot, running under the debugger will take
7923 less time, and so on.
7925 However, simplification is not vital; if you do not want to do this,
7926 report the bug anyway and send us the entire test case you used.
7929 A patch for the bug.
7931 A patch for the bug does help us if it is a good one. But do not omit
7932 the necessary information, such as the test case, on the assumption that
7933 a patch is all we need. We might see problems with your patch and decide
7934 to fix the problem another way, or we might not understand it at all.
7936 Sometimes with a program as complicated as @command{ld} it is very hard to
7937 construct an example that will make the program follow a certain path
7938 through the code. If you do not send us the example, we will not be
7939 able to construct one, so we will not be able to verify that the bug is
7942 And if we cannot understand what bug you are trying to fix, or why your
7943 patch should be an improvement, we will not install it. A test case will
7944 help us to understand.
7947 A guess about what the bug is or what it depends on.
7949 Such guesses are usually wrong. Even we cannot guess right about such
7950 things without first using the debugger to find the facts.
7954 @appendix MRI Compatible Script Files
7955 @cindex MRI compatibility
7956 To aid users making the transition to @sc{gnu} @command{ld} from the MRI
7957 linker, @command{ld} can use MRI compatible linker scripts as an
7958 alternative to the more general-purpose linker scripting language
7959 described in @ref{Scripts}. MRI compatible linker scripts have a much
7960 simpler command set than the scripting language otherwise used with
7961 @command{ld}. @sc{gnu} @command{ld} supports the most commonly used MRI
7962 linker commands; these commands are described here.
7964 In general, MRI scripts aren't of much use with the @code{a.out} object
7965 file format, since it only has three sections and MRI scripts lack some
7966 features to make use of them.
7968 You can specify a file containing an MRI-compatible script using the
7969 @samp{-c} command-line option.
7971 Each command in an MRI-compatible script occupies its own line; each
7972 command line starts with the keyword that identifies the command (though
7973 blank lines are also allowed for punctuation). If a line of an
7974 MRI-compatible script begins with an unrecognized keyword, @command{ld}
7975 issues a warning message, but continues processing the script.
7977 Lines beginning with @samp{*} are comments.
7979 You can write these commands using all upper-case letters, or all
7980 lower case; for example, @samp{chip} is the same as @samp{CHIP}.
7981 The following list shows only the upper-case form of each command.
7984 @cindex @code{ABSOLUTE} (MRI)
7985 @item ABSOLUTE @var{secname}
7986 @itemx ABSOLUTE @var{secname}, @var{secname}, @dots{} @var{secname}
7987 Normally, @command{ld} includes in the output file all sections from all
7988 the input files. However, in an MRI-compatible script, you can use the
7989 @code{ABSOLUTE} command to restrict the sections that will be present in
7990 your output program. If the @code{ABSOLUTE} command is used at all in a
7991 script, then only the sections named explicitly in @code{ABSOLUTE}
7992 commands will appear in the linker output. You can still use other
7993 input sections (whatever you select on the command line, or using
7994 @code{LOAD}) to resolve addresses in the output file.
7996 @cindex @code{ALIAS} (MRI)
7997 @item ALIAS @var{out-secname}, @var{in-secname}
7998 Use this command to place the data from input section @var{in-secname}
7999 in a section called @var{out-secname} in the linker output file.
8001 @var{in-secname} may be an integer.
8003 @cindex @code{ALIGN} (MRI)
8004 @item ALIGN @var{secname} = @var{expression}
8005 Align the section called @var{secname} to @var{expression}. The
8006 @var{expression} should be a power of two.
8008 @cindex @code{BASE} (MRI)
8009 @item BASE @var{expression}
8010 Use the value of @var{expression} as the lowest address (other than
8011 absolute addresses) in the output file.
8013 @cindex @code{CHIP} (MRI)
8014 @item CHIP @var{expression}
8015 @itemx CHIP @var{expression}, @var{expression}
8016 This command does nothing; it is accepted only for compatibility.
8018 @cindex @code{END} (MRI)
8020 This command does nothing whatever; it's only accepted for compatibility.
8022 @cindex @code{FORMAT} (MRI)
8023 @item FORMAT @var{output-format}
8024 Similar to the @code{OUTPUT_FORMAT} command in the more general linker
8025 language, but restricted to one of these output formats:
8029 S-records, if @var{output-format} is @samp{S}
8032 IEEE, if @var{output-format} is @samp{IEEE}
8035 COFF (the @samp{coff-m68k} variant in BFD), if @var{output-format} is
8039 @cindex @code{LIST} (MRI)
8040 @item LIST @var{anything}@dots{}
8041 Print (to the standard output file) a link map, as produced by the
8042 @command{ld} command-line option @samp{-M}.
8044 The keyword @code{LIST} may be followed by anything on the
8045 same line, with no change in its effect.
8047 @cindex @code{LOAD} (MRI)
8048 @item LOAD @var{filename}
8049 @itemx LOAD @var{filename}, @var{filename}, @dots{} @var{filename}
8050 Include one or more object file @var{filename} in the link; this has the
8051 same effect as specifying @var{filename} directly on the @command{ld}
8054 @cindex @code{NAME} (MRI)
8055 @item NAME @var{output-name}
8056 @var{output-name} is the name for the program produced by @command{ld}; the
8057 MRI-compatible command @code{NAME} is equivalent to the command-line
8058 option @samp{-o} or the general script language command @code{OUTPUT}.
8060 @cindex @code{ORDER} (MRI)
8061 @item ORDER @var{secname}, @var{secname}, @dots{} @var{secname}
8062 @itemx ORDER @var{secname} @var{secname} @var{secname}
8063 Normally, @command{ld} orders the sections in its output file in the
8064 order in which they first appear in the input files. In an MRI-compatible
8065 script, you can override this ordering with the @code{ORDER} command. The
8066 sections you list with @code{ORDER} will appear first in your output
8067 file, in the order specified.
8069 @cindex @code{PUBLIC} (MRI)
8070 @item PUBLIC @var{name}=@var{expression}
8071 @itemx PUBLIC @var{name},@var{expression}
8072 @itemx PUBLIC @var{name} @var{expression}
8073 Supply a value (@var{expression}) for external symbol
8074 @var{name} used in the linker input files.
8076 @cindex @code{SECT} (MRI)
8077 @item SECT @var{secname}, @var{expression}
8078 @itemx SECT @var{secname}=@var{expression}
8079 @itemx SECT @var{secname} @var{expression}
8080 You can use any of these three forms of the @code{SECT} command to
8081 specify the start address (@var{expression}) for section @var{secname}.
8082 If you have more than one @code{SECT} statement for the same
8083 @var{secname}, only the @emph{first} sets the start address.
8086 @node GNU Free Documentation License
8087 @appendix GNU Free Documentation License
8091 @unnumbered LD Index
8096 % I think something like @@colophon should be in texinfo. In the
8098 \long\def\colophon{\hbox to0pt{}\vfill
8099 \centerline{The body of this manual is set in}
8100 \centerline{\fontname\tenrm,}
8101 \centerline{with headings in {\bf\fontname\tenbf}}
8102 \centerline{and examples in {\tt\fontname\tentt}.}
8103 \centerline{{\it\fontname\tenit\/} and}
8104 \centerline{{\sl\fontname\tensl\/}}
8105 \centerline{are used for emphasis.}\vfill}
8107 % Blame: doc@@cygnus.com, 28mar91.