Commit | Line | Data |
---|---|---|
252b5132 RH |
1 | \input texinfo |
2 | @setfilename ld.info | |
a2b64bed | 3 | @c Copyright 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, |
e7fc76dd | 4 | @c 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc. |
252b5132 | 5 | @syncodeindex ky cp |
dff70155 | 6 | @c man begin INCLUDE |
252b5132 RH |
7 | @include configdoc.texi |
8 | @c (configdoc.texi is generated by the Makefile) | |
c428fa83 | 9 | @include bfdver.texi |
dff70155 | 10 | @c man end |
252b5132 RH |
11 | |
12 | @c @smallbook | |
13 | ||
ff5dcc92 SC |
14 | @macro gcctabopt{body} |
15 | @code{\body\} | |
16 | @end macro | |
17 | ||
0285c67d NC |
18 | @c man begin NAME |
19 | @ifset man | |
20 | @c Configure for the generation of man pages | |
21 | @set UsesEnvVars | |
22 | @set GENERIC | |
0285c67d | 23 | @set ARM |
49fa1e15 | 24 | @set H8300 |
0285c67d | 25 | @set HPPA |
0285c67d | 26 | @set I960 |
0285c67d | 27 | @set M68HC11 |
7fb9f789 | 28 | @set M68K |
3c3bdf30 | 29 | @set MMIX |
2469cfa2 | 30 | @set MSP430 |
2a60a7a8 AM |
31 | @set POWERPC |
32 | @set POWERPC64 | |
49fa1e15 AM |
33 | @set Renesas |
34 | @set SPU | |
35 | @set TICOFF | |
2ca22b03 | 36 | @set WIN32 |
e0001a05 | 37 | @set XTENSA |
0285c67d NC |
38 | @end ifset |
39 | @c man end | |
40 | ||
252b5132 RH |
41 | @ifinfo |
42 | @format | |
43 | START-INFO-DIR-ENTRY | |
44 | * Ld: (ld). The GNU linker. | |
45 | END-INFO-DIR-ENTRY | |
46 | @end format | |
47 | @end ifinfo | |
48 | ||
0e9517a9 | 49 | @copying |
e49e529d JM |
50 | This file documents the @sc{gnu} linker LD |
51 | @ifset VERSION_PACKAGE | |
52 | @value{VERSION_PACKAGE} | |
53 | @end ifset | |
54 | version @value{VERSION}. | |
252b5132 | 55 | |
0e9517a9 | 56 | Copyright @copyright{} 1991, 92, 93, 94, 95, 96, 97, 98, 99, 2000, |
ad22bfe8 | 57 | 2001, 2002, 2003, 2004, 2005, 2006, 2007 Free Software Foundation, Inc. |
252b5132 | 58 | |
cf055d54 NC |
59 | Permission is granted to copy, distribute and/or modify this document |
60 | under the terms of the GNU Free Documentation License, Version 1.1 | |
61 | or any later version published by the Free Software Foundation; | |
62 | with no Invariant Sections, with no Front-Cover Texts, and with no | |
63 | Back-Cover Texts. A copy of the license is included in the | |
36f63dca | 64 | section entitled ``GNU Free Documentation License''. |
0e9517a9 | 65 | @end copying |
252b5132 RH |
66 | @iftex |
67 | @finalout | |
68 | @setchapternewpage odd | |
71ba23f6 | 69 | @settitle The GNU linker |
252b5132 | 70 | @titlepage |
71ba23f6 | 71 | @title The GNU linker |
252b5132 | 72 | @sp 1 |
e49e529d JM |
73 | @subtitle @code{ld} |
74 | @ifset VERSION_PACKAGE | |
75 | @subtitle @value{VERSION_PACKAGE} | |
76 | @end ifset | |
252b5132 RH |
77 | @subtitle Version @value{VERSION} |
78 | @author Steve Chamberlain | |
79 | @author Ian Lance Taylor | |
252b5132 RH |
80 | @page |
81 | ||
82 | @tex | |
83 | {\parskip=0pt | |
704c465c NC |
84 | \hfill Red Hat Inc\par |
85 | \hfill nickc\@credhat.com, doc\@redhat.com\par | |
71ba23f6 | 86 | \hfill {\it The GNU linker}\par |
252b5132 RH |
87 | \hfill Edited by Jeffrey Osier (jeffrey\@cygnus.com)\par |
88 | } | |
89 | \global\parindent=0pt % Steve likes it this way. | |
90 | @end tex | |
91 | ||
92 | @vskip 0pt plus 1filll | |
0285c67d | 93 | @c man begin COPYRIGHT |
9c8ebd6a | 94 | Copyright @copyright{} 1991, 92, 93, 94, 95, 96, 97, 98, 99, 2000, 2001, |
ad22bfe8 | 95 | 2002, 2003, 2004, 2005, 2006, 2007 Free Software Foundation, Inc. |
252b5132 | 96 | |
0285c67d NC |
97 | Permission is granted to copy, distribute and/or modify this document |
98 | under the terms of the GNU Free Documentation License, Version 1.1 | |
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 | |
36f63dca | 102 | section entitled ``GNU Free Documentation License''. |
0285c67d | 103 | @c man end |
252b5132 | 104 | |
252b5132 RH |
105 | @end titlepage |
106 | @end iftex | |
4ecceb71 | 107 | @contents |
252b5132 RH |
108 | @c FIXME: Talk about importance of *order* of args, cmds to linker! |
109 | ||
84ec0e6d | 110 | @ifnottex |
252b5132 | 111 | @node Top |
71ba23f6 | 112 | @top LD |
e49e529d JM |
113 | This file documents the @sc{gnu} linker ld |
114 | @ifset VERSION_PACKAGE | |
115 | @value{VERSION_PACKAGE} | |
116 | @end ifset | |
117 | version @value{VERSION}. | |
252b5132 | 118 | |
cf055d54 NC |
119 | This document is distributed under the terms of the GNU Free |
120 | Documentation License. A copy of the license is included in the | |
36f63dca | 121 | section entitled ``GNU Free Documentation License''. |
cf055d54 | 122 | |
252b5132 RH |
123 | @menu |
124 | * Overview:: Overview | |
125 | * Invocation:: Invocation | |
126 | * Scripts:: Linker Scripts | |
127 | @ifset GENERIC | |
128 | * Machine Dependent:: Machine Dependent Features | |
129 | @end ifset | |
130 | @ifclear GENERIC | |
131 | @ifset H8300 | |
132 | * H8/300:: ld and the H8/300 | |
133 | @end ifset | |
c2dcd04e NC |
134 | @ifset Renesas |
135 | * Renesas:: ld and other Renesas micros | |
252b5132 RH |
136 | @end ifset |
137 | @ifset I960 | |
138 | * i960:: ld and the Intel 960 family | |
139 | @end ifset | |
36f63dca NC |
140 | @ifset ARM |
141 | * ARM:: ld and the ARM family | |
142 | @end ifset | |
143 | @ifset HPPA | |
144 | * HPPA ELF32:: ld and HPPA 32-bit ELF | |
145 | @end ifset | |
93fd0973 SC |
146 | @ifset M68HC11 |
147 | * M68HC11/68HC12:: ld and the Motorola 68HC11 and 68HC12 families | |
148 | @end ifset | |
7fb9f789 NC |
149 | @ifset M68K |
150 | * M68K:: ld and Motorola 68K family | |
151 | @end ifset | |
2a60a7a8 AM |
152 | @ifset POWERPC |
153 | * PowerPC ELF32:: ld and PowerPC 32-bit ELF Support | |
154 | @end ifset | |
155 | @ifset POWERPC64 | |
156 | * PowerPC64 ELF64:: ld and PowerPC64 64-bit ELF Support | |
157 | @end ifset | |
49fa1e15 AM |
158 | @ifset SPU |
159 | * SPU ELF:: ld and SPU ELF Support | |
160 | @end ifset | |
74459f0e TW |
161 | @ifset TICOFF |
162 | * TI COFF:: ld and the TI COFF | |
163 | @end ifset | |
2ca22b03 NC |
164 | @ifset WIN32 |
165 | * Win32:: ld and WIN32 (cygwin/mingw) | |
166 | @end ifset | |
e0001a05 NC |
167 | @ifset XTENSA |
168 | * Xtensa:: ld and Xtensa Processors | |
169 | @end ifset | |
252b5132 RH |
170 | @end ifclear |
171 | @ifclear SingleFormat | |
172 | * BFD:: BFD | |
173 | @end ifclear | |
174 | @c Following blank line required for remaining bug in makeinfo conds/menus | |
175 | ||
176 | * Reporting Bugs:: Reporting Bugs | |
177 | * MRI:: MRI Compatible Script Files | |
704c465c | 178 | * GNU Free Documentation License:: GNU Free Documentation License |
370b66a1 | 179 | * LD Index:: LD Index |
252b5132 | 180 | @end menu |
84ec0e6d | 181 | @end ifnottex |
252b5132 RH |
182 | |
183 | @node Overview | |
184 | @chapter Overview | |
185 | ||
186 | @cindex @sc{gnu} linker | |
187 | @cindex what is this? | |
0285c67d | 188 | |
0879a67a | 189 | @ifset man |
0285c67d | 190 | @c man begin SYNOPSIS |
ff5dcc92 | 191 | ld [@b{options}] @var{objfile} @dots{} |
0285c67d NC |
192 | @c man end |
193 | ||
194 | @c man begin SEEALSO | |
195 | ar(1), nm(1), objcopy(1), objdump(1), readelf(1) and | |
196 | the Info entries for @file{binutils} and | |
197 | @file{ld}. | |
198 | @c man end | |
199 | @end ifset | |
200 | ||
201 | @c man begin DESCRIPTION | |
202 | ||
ff5dcc92 | 203 | @command{ld} combines a number of object and archive files, relocates |
252b5132 | 204 | their data and ties up symbol references. Usually the last step in |
ff5dcc92 | 205 | compiling a program is to run @command{ld}. |
252b5132 | 206 | |
ff5dcc92 | 207 | @command{ld} accepts Linker Command Language files written in |
252b5132 RH |
208 | a superset of AT&T's Link Editor Command Language syntax, |
209 | to provide explicit and total control over the linking process. | |
210 | ||
0285c67d NC |
211 | @ifset man |
212 | @c For the man only | |
ece2d90e | 213 | This man page does not describe the command language; see the |
71ba23f6 NC |
214 | @command{ld} entry in @code{info} for full details on the command |
215 | language and on other aspects of the GNU linker. | |
0285c67d NC |
216 | @end ifset |
217 | ||
252b5132 | 218 | @ifclear SingleFormat |
ff5dcc92 SC |
219 | This version of @command{ld} uses the general purpose BFD libraries |
220 | to operate on object files. This allows @command{ld} to read, combine, and | |
252b5132 RH |
221 | write object files in many different formats---for example, COFF or |
222 | @code{a.out}. Different formats may be linked together to produce any | |
223 | available kind of object file. @xref{BFD}, for more information. | |
224 | @end ifclear | |
225 | ||
226 | Aside from its flexibility, the @sc{gnu} linker is more helpful than other | |
227 | linkers in providing diagnostic information. Many linkers abandon | |
228 | execution immediately upon encountering an error; whenever possible, | |
ff5dcc92 | 229 | @command{ld} continues executing, allowing you to identify other errors |
252b5132 RH |
230 | (or, in some cases, to get an output file in spite of the error). |
231 | ||
0285c67d NC |
232 | @c man end |
233 | ||
252b5132 RH |
234 | @node Invocation |
235 | @chapter Invocation | |
236 | ||
0285c67d NC |
237 | @c man begin DESCRIPTION |
238 | ||
ff5dcc92 | 239 | The @sc{gnu} linker @command{ld} is meant to cover a broad range of situations, |
252b5132 RH |
240 | and to be as compatible as possible with other linkers. As a result, |
241 | you have many choices to control its behavior. | |
242 | ||
0285c67d NC |
243 | @c man end |
244 | ||
252b5132 RH |
245 | @ifset UsesEnvVars |
246 | @menu | |
247 | * Options:: Command Line Options | |
248 | * Environment:: Environment Variables | |
249 | @end menu | |
250 | ||
251 | @node Options | |
252 | @section Command Line Options | |
253 | @end ifset | |
254 | ||
255 | @cindex command line | |
256 | @cindex options | |
0285c67d NC |
257 | |
258 | @c man begin OPTIONS | |
259 | ||
252b5132 RH |
260 | The linker supports a plethora of command-line options, but in actual |
261 | practice few of them are used in any particular context. | |
262 | @cindex standard Unix system | |
ff5dcc92 | 263 | For instance, a frequent use of @command{ld} is to link standard Unix |
252b5132 RH |
264 | object files on a standard, supported Unix system. On such a system, to |
265 | link a file @code{hello.o}: | |
266 | ||
267 | @smallexample | |
268 | ld -o @var{output} /lib/crt0.o hello.o -lc | |
269 | @end smallexample | |
270 | ||
ff5dcc92 | 271 | This tells @command{ld} to produce a file called @var{output} as the |
252b5132 RH |
272 | result of linking the file @code{/lib/crt0.o} with @code{hello.o} and |
273 | the library @code{libc.a}, which will come from the standard search | |
274 | directories. (See the discussion of the @samp{-l} option below.) | |
275 | ||
ff5dcc92 | 276 | Some of the command-line options to @command{ld} may be specified at any |
511ab9e9 ILT |
277 | point in the command line. However, options which refer to files, such |
278 | as @samp{-l} or @samp{-T}, cause the file to be read at the point at | |
279 | which the option appears in the command line, relative to the object | |
280 | files and other file options. Repeating non-file options with a | |
281 | different argument will either have no further effect, or override prior | |
252b5132 RH |
282 | occurrences (those further to the left on the command line) of that |
283 | option. Options which may be meaningfully specified more than once are | |
284 | noted in the descriptions below. | |
285 | ||
286 | @cindex object files | |
511ab9e9 ILT |
287 | Non-option arguments are object files or archives which are to be linked |
288 | together. They may follow, precede, or be mixed in with command-line | |
289 | options, except that an object file argument may not be placed between | |
290 | an option and its argument. | |
252b5132 RH |
291 | |
292 | Usually the linker is invoked with at least one object file, but you can | |
293 | specify other forms of binary input files using @samp{-l}, @samp{-R}, | |
294 | and the script command language. If @emph{no} binary input files at all | |
295 | are specified, the linker does not produce any output, and issues the | |
296 | message @samp{No input files}. | |
297 | ||
36f63dca | 298 | If the linker cannot recognize the format of an object file, it will |
252b5132 RH |
299 | assume that it is a linker script. A script specified in this way |
300 | augments the main linker script used for the link (either the default | |
301 | linker script or the one specified by using @samp{-T}). This feature | |
302 | permits the linker to link against a file which appears to be an object | |
303 | or an archive, but actually merely defines some symbol values, or uses | |
53d25da6 AM |
304 | @code{INPUT} or @code{GROUP} to load other objects. Specifying a |
305 | script in this way merely augments the main linker script, with the | |
306 | extra commands placed after the main script; use the @samp{-T} option | |
307 | to replace the default linker script entirely, but note the effect of | |
308 | the @code{INSERT} command. @xref{Scripts}. | |
252b5132 RH |
309 | |
310 | For options whose names are a single letter, | |
311 | option arguments must either follow the option letter without intervening | |
312 | whitespace, or be given as separate arguments immediately following the | |
313 | option that requires them. | |
314 | ||
315 | For options whose names are multiple letters, either one dash or two can | |
e4897a32 | 316 | precede the option name; for example, @samp{-trace-symbol} and |
36f63dca | 317 | @samp{--trace-symbol} are equivalent. Note---there is one exception to |
e4897a32 | 318 | this rule. Multiple letter options that start with a lower case 'o' can |
ba1be17e | 319 | only be preceded by two dashes. This is to reduce confusion with the |
e4897a32 NC |
320 | @samp{-o} option. So for example @samp{-omagic} sets the output file |
321 | name to @samp{magic} whereas @samp{--omagic} sets the NMAGIC flag on the | |
322 | output. | |
323 | ||
324 | Arguments to multiple-letter options must either be separated from the | |
325 | option name by an equals sign, or be given as separate arguments | |
326 | immediately following the option that requires them. For example, | |
327 | @samp{--trace-symbol foo} and @samp{--trace-symbol=foo} are equivalent. | |
328 | Unique abbreviations of the names of multiple-letter options are | |
329 | accepted. | |
252b5132 | 330 | |
36f63dca NC |
331 | Note---if the linker is being invoked indirectly, via a compiler driver |
332 | (e.g. @samp{gcc}) then all the linker command line options should be | |
fa19fce0 NC |
333 | prefixed by @samp{-Wl,} (or whatever is appropriate for the particular |
334 | compiler driver) like this: | |
4e53152f NC |
335 | |
336 | @smallexample | |
337 | gcc -Wl,--startgroup foo.o bar.o -Wl,--endgroup | |
338 | @end smallexample | |
339 | ||
340 | This is important, because otherwise the compiler driver program may | |
341 | silently drop the linker options, resulting in a bad link. | |
342 | ||
343 | Here is a table of the generic command line switches accepted by the GNU | |
344 | linker: | |
345 | ||
ff5dcc92 | 346 | @table @gcctabopt |
38fc1cb1 | 347 | @include at-file.texi |
dff70155 | 348 | |
252b5132 RH |
349 | @kindex -a@var{keyword} |
350 | @item -a@var{keyword} | |
351 | This option is supported for HP/UX compatibility. The @var{keyword} | |
352 | argument must be one of the strings @samp{archive}, @samp{shared}, or | |
353 | @samp{default}. @samp{-aarchive} is functionally equivalent to | |
354 | @samp{-Bstatic}, and the other two keywords are functionally equivalent | |
355 | to @samp{-Bdynamic}. This option may be used any number of times. | |
356 | ||
357 | @ifset I960 | |
358 | @cindex architectures | |
359 | @kindex -A@var{arch} | |
360 | @item -A@var{architecture} | |
361 | @kindex --architecture=@var{arch} | |
362 | @itemx --architecture=@var{architecture} | |
ff5dcc92 SC |
363 | In the current release of @command{ld}, this option is useful only for the |
364 | Intel 960 family of architectures. In that @command{ld} configuration, the | |
252b5132 RH |
365 | @var{architecture} argument identifies the particular architecture in |
366 | the 960 family, enabling some safeguards and modifying the | |
ff5dcc92 | 367 | archive-library search path. @xref{i960,,@command{ld} and the Intel 960 |
252b5132 RH |
368 | family}, for details. |
369 | ||
ff5dcc92 | 370 | Future releases of @command{ld} may support similar functionality for |
252b5132 RH |
371 | other architecture families. |
372 | @end ifset | |
373 | ||
374 | @ifclear SingleFormat | |
375 | @cindex binary input format | |
376 | @kindex -b @var{format} | |
377 | @kindex --format=@var{format} | |
378 | @cindex input format | |
379 | @cindex input format | |
380 | @item -b @var{input-format} | |
381 | @itemx --format=@var{input-format} | |
ff5dcc92 SC |
382 | @command{ld} may be configured to support more than one kind of object |
383 | file. If your @command{ld} is configured this way, you can use the | |
252b5132 | 384 | @samp{-b} option to specify the binary format for input object files |
ff5dcc92 | 385 | that follow this option on the command line. Even when @command{ld} is |
252b5132 | 386 | configured to support alternative object formats, you don't usually need |
ff5dcc92 | 387 | to specify this, as @command{ld} should be configured to expect as a |
252b5132 RH |
388 | default input format the most usual format on each machine. |
389 | @var{input-format} is a text string, the name of a particular format | |
390 | supported by the BFD libraries. (You can list the available binary | |
391 | formats with @samp{objdump -i}.) | |
392 | @xref{BFD}. | |
393 | ||
394 | You may want to use this option if you are linking files with an unusual | |
395 | binary format. You can also use @samp{-b} to switch formats explicitly (when | |
396 | linking object files of different formats), by including | |
397 | @samp{-b @var{input-format}} before each group of object files in a | |
a1ab1d2a | 398 | particular format. |
252b5132 RH |
399 | |
400 | The default format is taken from the environment variable | |
401 | @code{GNUTARGET}. | |
402 | @ifset UsesEnvVars | |
403 | @xref{Environment}. | |
404 | @end ifset | |
405 | You can also define the input format from a script, using the command | |
0285c67d NC |
406 | @code{TARGET}; |
407 | @ifclear man | |
408 | see @ref{Format Commands}. | |
409 | @end ifclear | |
252b5132 RH |
410 | @end ifclear |
411 | ||
412 | @kindex -c @var{MRI-cmdfile} | |
413 | @kindex --mri-script=@var{MRI-cmdfile} | |
414 | @cindex compatibility, MRI | |
415 | @item -c @var{MRI-commandfile} | |
416 | @itemx --mri-script=@var{MRI-commandfile} | |
ff5dcc92 | 417 | For compatibility with linkers produced by MRI, @command{ld} accepts script |
252b5132 | 418 | files written in an alternate, restricted command language, described in |
0285c67d NC |
419 | @ifclear man |
420 | @ref{MRI,,MRI Compatible Script Files}. | |
421 | @end ifclear | |
422 | @ifset man | |
423 | the MRI Compatible Script Files section of GNU ld documentation. | |
424 | @end ifset | |
425 | Introduce MRI script files with | |
252b5132 | 426 | the option @samp{-c}; use the @samp{-T} option to run linker |
ff5dcc92 SC |
427 | scripts written in the general-purpose @command{ld} scripting language. |
428 | If @var{MRI-cmdfile} does not exist, @command{ld} looks for it in the directories | |
252b5132 RH |
429 | specified by any @samp{-L} options. |
430 | ||
431 | @cindex common allocation | |
432 | @kindex -d | |
433 | @kindex -dc | |
434 | @kindex -dp | |
a1ab1d2a | 435 | @item -d |
252b5132 RH |
436 | @itemx -dc |
437 | @itemx -dp | |
438 | These three options are equivalent; multiple forms are supported for | |
439 | compatibility with other linkers. They assign space to common symbols | |
440 | even if a relocatable output file is specified (with @samp{-r}). The | |
441 | script command @code{FORCE_COMMON_ALLOCATION} has the same effect. | |
442 | @xref{Miscellaneous Commands}. | |
443 | ||
444 | @cindex entry point, from command line | |
445 | @kindex -e @var{entry} | |
446 | @kindex --entry=@var{entry} | |
a1ab1d2a | 447 | @item -e @var{entry} |
252b5132 RH |
448 | @itemx --entry=@var{entry} |
449 | Use @var{entry} as the explicit symbol for beginning execution of your | |
450 | program, rather than the default entry point. If there is no symbol | |
451 | named @var{entry}, the linker will try to parse @var{entry} as a number, | |
452 | and use that as the entry address (the number will be interpreted in | |
453 | base 10; you may use a leading @samp{0x} for base 16, or a leading | |
454 | @samp{0} for base 8). @xref{Entry Point}, for a discussion of defaults | |
455 | and other ways of specifying the entry point. | |
456 | ||
b58f81ae DJ |
457 | @kindex --exclude-libs |
458 | @item --exclude-libs @var{lib},@var{lib},... | |
459 | Specifies a list of archive libraries from which symbols should not be automatically | |
460 | exported. The library names may be delimited by commas or colons. Specifying | |
461 | @code{--exclude-libs ALL} excludes symbols in all archive libraries from | |
462 | automatic export. This option is available only for the i386 PE targeted | |
463 | port of the linker and for ELF targeted ports. For i386 PE, symbols | |
464 | explicitly listed in a .def file are still exported, regardless of this | |
465 | option. For ELF targeted ports, symbols affected by this option will | |
466 | be treated as hidden. | |
467 | ||
252b5132 RH |
468 | @cindex dynamic symbol table |
469 | @kindex -E | |
470 | @kindex --export-dynamic | |
471 | @item -E | |
472 | @itemx --export-dynamic | |
473 | When creating a dynamically linked executable, add all symbols to the | |
474 | dynamic symbol table. The dynamic symbol table is the set of symbols | |
475 | which are visible from dynamic objects at run time. | |
476 | ||
477 | If you do not use this option, the dynamic symbol table will normally | |
478 | contain only those symbols which are referenced by some dynamic object | |
479 | mentioned in the link. | |
480 | ||
481 | If you use @code{dlopen} to load a dynamic object which needs to refer | |
482 | back to the symbols defined by the program, rather than some other | |
483 | dynamic object, then you will probably need to use this option when | |
484 | linking the program itself. | |
485 | ||
55255dae | 486 | You can also use the dynamic list to control what symbols should |
cb840a31 | 487 | be added to the dynamic symbol table if the output format supports it. |
55255dae | 488 | See the description of @samp{--dynamic-list}. |
cb840a31 | 489 | |
36f63dca | 490 | @ifclear SingleFormat |
252b5132 RH |
491 | @cindex big-endian objects |
492 | @cindex endianness | |
493 | @kindex -EB | |
494 | @item -EB | |
495 | Link big-endian objects. This affects the default output format. | |
496 | ||
497 | @cindex little-endian objects | |
498 | @kindex -EL | |
499 | @item -EL | |
500 | Link little-endian objects. This affects the default output format. | |
36f63dca | 501 | @end ifclear |
252b5132 RH |
502 | |
503 | @kindex -f | |
504 | @kindex --auxiliary | |
505 | @item -f | |
506 | @itemx --auxiliary @var{name} | |
507 | When creating an ELF shared object, set the internal DT_AUXILIARY field | |
508 | to the specified name. This tells the dynamic linker that the symbol | |
509 | table of the shared object should be used as an auxiliary filter on the | |
510 | symbol table of the shared object @var{name}. | |
511 | ||
512 | If you later link a program against this filter object, then, when you | |
513 | run the program, the dynamic linker will see the DT_AUXILIARY field. If | |
514 | the dynamic linker resolves any symbols from the filter object, it will | |
515 | first check whether there is a definition in the shared object | |
516 | @var{name}. If there is one, it will be used instead of the definition | |
517 | in the filter object. The shared object @var{name} need not exist. | |
518 | Thus the shared object @var{name} may be used to provide an alternative | |
519 | implementation of certain functions, perhaps for debugging or for | |
520 | machine specific performance. | |
521 | ||
522 | This option may be specified more than once. The DT_AUXILIARY entries | |
523 | will be created in the order in which they appear on the command line. | |
524 | ||
525 | @kindex -F | |
526 | @kindex --filter | |
527 | @item -F @var{name} | |
528 | @itemx --filter @var{name} | |
529 | When creating an ELF shared object, set the internal DT_FILTER field to | |
530 | the specified name. This tells the dynamic linker that the symbol table | |
531 | of the shared object which is being created should be used as a filter | |
532 | on the symbol table of the shared object @var{name}. | |
533 | ||
534 | If you later link a program against this filter object, then, when you | |
535 | run the program, the dynamic linker will see the DT_FILTER field. The | |
536 | dynamic linker will resolve symbols according to the symbol table of the | |
537 | filter object as usual, but it will actually link to the definitions | |
538 | found in the shared object @var{name}. Thus the filter object can be | |
539 | used to select a subset of the symbols provided by the object | |
540 | @var{name}. | |
541 | ||
ff5dcc92 | 542 | Some older linkers used the @option{-F} option throughout a compilation |
252b5132 | 543 | toolchain for specifying object-file format for both input and output |
36f63dca NC |
544 | object files. |
545 | @ifclear SingleFormat | |
546 | The @sc{gnu} linker uses other mechanisms for this purpose: the | |
ece2d90e | 547 | @option{-b}, @option{--format}, @option{--oformat} options, the |
252b5132 | 548 | @code{TARGET} command in linker scripts, and the @code{GNUTARGET} |
36f63dca NC |
549 | environment variable. |
550 | @end ifclear | |
551 | The @sc{gnu} linker will ignore the @option{-F} option when not | |
552 | creating an ELF shared object. | |
252b5132 | 553 | |
3dbf70a2 MM |
554 | @cindex finalization function |
555 | @kindex -fini | |
556 | @item -fini @var{name} | |
557 | When creating an ELF executable or shared object, call NAME when the | |
558 | executable or shared object is unloaded, by setting DT_FINI to the | |
559 | address of the function. By default, the linker uses @code{_fini} as | |
560 | the function to call. | |
561 | ||
252b5132 RH |
562 | @kindex -g |
563 | @item -g | |
564 | Ignored. Provided for compatibility with other tools. | |
565 | ||
566 | @kindex -G | |
567 | @kindex --gpsize | |
568 | @cindex object size | |
569 | @item -G@var{value} | |
570 | @itemx --gpsize=@var{value} | |
571 | Set the maximum size of objects to be optimized using the GP register to | |
572 | @var{size}. This is only meaningful for object file formats such as | |
573 | MIPS ECOFF which supports putting large and small objects into different | |
574 | sections. This is ignored for other object file formats. | |
575 | ||
576 | @cindex runtime library name | |
577 | @kindex -h@var{name} | |
578 | @kindex -soname=@var{name} | |
579 | @item -h@var{name} | |
580 | @itemx -soname=@var{name} | |
581 | When creating an ELF shared object, set the internal DT_SONAME field to | |
582 | the specified name. When an executable is linked with a shared object | |
583 | which has a DT_SONAME field, then when the executable is run the dynamic | |
584 | linker will attempt to load the shared object specified by the DT_SONAME | |
585 | field rather than the using the file name given to the linker. | |
586 | ||
587 | @kindex -i | |
588 | @cindex incremental link | |
589 | @item -i | |
590 | Perform an incremental link (same as option @samp{-r}). | |
591 | ||
3dbf70a2 MM |
592 | @cindex initialization function |
593 | @kindex -init | |
594 | @item -init @var{name} | |
595 | When creating an ELF executable or shared object, call NAME when the | |
596 | executable or shared object is loaded, by setting DT_INIT to the address | |
597 | of the function. By default, the linker uses @code{_init} as the | |
598 | function to call. | |
599 | ||
252b5132 | 600 | @cindex archive files, from cmd line |
bcb674cf RS |
601 | @kindex -l@var{namespec} |
602 | @kindex --library=@var{namespec} | |
603 | @item -l@var{namespec} | |
604 | @itemx --library=@var{namespec} | |
605 | Add the archive or object file specified by @var{namespec} to the | |
606 | list of files to link. This option may be used any number of times. | |
607 | If @var{namespec} is of the form @file{:@var{filename}}, @command{ld} | |
608 | will search the library path for a file called @var{filename}, otherise it | |
609 | will search the library path for a file called @file{lib@var{namespec}.a}. | |
252b5132 | 610 | |
ff5dcc92 | 611 | On systems which support shared libraries, @command{ld} may also search for |
bcb674cf RS |
612 | files other than @file{lib@var{namespec}.a}. Specifically, on ELF |
613 | and SunOS systems, @command{ld} will search a directory for a library | |
614 | called @file{lib@var{namespec}.so} before searching for one called | |
615 | @file{lib@var{namespec}.a}. (By convention, a @code{.so} extension | |
616 | indicates a shared library.) Note that this behavior does not apply | |
617 | to @file{:@var{filename}}, which always specifies a file called | |
618 | @var{filename}. | |
252b5132 RH |
619 | |
620 | The linker will search an archive only once, at the location where it is | |
621 | specified on the command line. If the archive defines a symbol which | |
622 | was undefined in some object which appeared before the archive on the | |
623 | command line, the linker will include the appropriate file(s) from the | |
624 | archive. However, an undefined symbol in an object appearing later on | |
625 | the command line will not cause the linker to search the archive again. | |
626 | ||
ff5dcc92 | 627 | See the @option{-(} option for a way to force the linker to search |
252b5132 RH |
628 | archives multiple times. |
629 | ||
630 | You may list the same archive multiple times on the command line. | |
631 | ||
632 | @ifset GENERIC | |
633 | This type of archive searching is standard for Unix linkers. However, | |
ff5dcc92 | 634 | if you are using @command{ld} on AIX, note that it is different from the |
252b5132 RH |
635 | behaviour of the AIX linker. |
636 | @end ifset | |
637 | ||
638 | @cindex search directory, from cmd line | |
639 | @kindex -L@var{dir} | |
640 | @kindex --library-path=@var{dir} | |
a1ab1d2a | 641 | @item -L@var{searchdir} |
252b5132 | 642 | @itemx --library-path=@var{searchdir} |
ff5dcc92 SC |
643 | Add path @var{searchdir} to the list of paths that @command{ld} will search |
644 | for archive libraries and @command{ld} control scripts. You may use this | |
252b5132 RH |
645 | option any number of times. The directories are searched in the order |
646 | in which they are specified on the command line. Directories specified | |
647 | on the command line are searched before the default directories. All | |
ff5dcc92 | 648 | @option{-L} options apply to all @option{-l} options, regardless of the |
252b5132 RH |
649 | order in which the options appear. |
650 | ||
9c8ebd6a DJ |
651 | If @var{searchdir} begins with @code{=}, then the @code{=} will be replaced |
652 | by the @dfn{sysroot prefix}, a path specified when the linker is configured. | |
653 | ||
252b5132 RH |
654 | @ifset UsesEnvVars |
655 | The default set of paths searched (without being specified with | |
ff5dcc92 | 656 | @samp{-L}) depends on which emulation mode @command{ld} is using, and in |
252b5132 RH |
657 | some cases also on how it was configured. @xref{Environment}. |
658 | @end ifset | |
659 | ||
660 | The paths can also be specified in a link script with the | |
661 | @code{SEARCH_DIR} command. Directories specified this way are searched | |
662 | at the point in which the linker script appears in the command line. | |
663 | ||
664 | @cindex emulation | |
665 | @kindex -m @var{emulation} | |
666 | @item -m@var{emulation} | |
667 | Emulate the @var{emulation} linker. You can list the available | |
668 | emulations with the @samp{--verbose} or @samp{-V} options. | |
669 | ||
670 | If the @samp{-m} option is not used, the emulation is taken from the | |
671 | @code{LDEMULATION} environment variable, if that is defined. | |
672 | ||
673 | Otherwise, the default emulation depends upon how the linker was | |
674 | configured. | |
675 | ||
676 | @cindex link map | |
677 | @kindex -M | |
678 | @kindex --print-map | |
679 | @item -M | |
680 | @itemx --print-map | |
681 | Print a link map to the standard output. A link map provides | |
682 | information about the link, including the following: | |
683 | ||
684 | @itemize @bullet | |
685 | @item | |
3b83e13a | 686 | Where object files are mapped into memory. |
252b5132 RH |
687 | @item |
688 | How common symbols are allocated. | |
689 | @item | |
690 | All archive members included in the link, with a mention of the symbol | |
691 | which caused the archive member to be brought in. | |
3b83e13a NC |
692 | @item |
693 | The values assigned to symbols. | |
694 | ||
695 | Note - symbols whose values are computed by an expression which | |
696 | involves a reference to a previous value of the same symbol may not | |
697 | have correct result displayed in the link map. This is because the | |
698 | linker discards intermediate results and only retains the final value | |
699 | of an expression. Under such circumstances the linker will display | |
700 | the final value enclosed by square brackets. Thus for example a | |
701 | linker script containing: | |
702 | ||
703 | @smallexample | |
704 | foo = 1 | |
705 | foo = foo * 4 | |
706 | foo = foo + 8 | |
707 | @end smallexample | |
708 | ||
709 | will produce the following output in the link map if the @option{-M} | |
710 | option is used: | |
711 | ||
712 | @smallexample | |
713 | 0x00000001 foo = 0x1 | |
714 | [0x0000000c] foo = (foo * 0x4) | |
715 | [0x0000000c] foo = (foo + 0x8) | |
716 | @end smallexample | |
717 | ||
718 | See @ref{Expressions} for more information about expressions in linker | |
719 | scripts. | |
252b5132 RH |
720 | @end itemize |
721 | ||
722 | @kindex -n | |
723 | @cindex read-only text | |
724 | @cindex NMAGIC | |
725 | @kindex --nmagic | |
726 | @item -n | |
727 | @itemx --nmagic | |
fa19fce0 | 728 | Turn off page alignment of sections, and mark the output as |
a1ab1d2a | 729 | @code{NMAGIC} if possible. |
252b5132 RH |
730 | |
731 | @kindex -N | |
732 | @kindex --omagic | |
733 | @cindex read/write from cmd line | |
734 | @cindex OMAGIC | |
a1ab1d2a | 735 | @item -N |
252b5132 RH |
736 | @itemx --omagic |
737 | Set the text and data sections to be readable and writable. Also, do | |
63fd3b82 NC |
738 | not page-align the data segment, and disable linking against shared |
739 | libraries. If the output format supports Unix style magic numbers, | |
4d8907ac DS |
740 | mark the output as @code{OMAGIC}. Note: Although a writable text section |
741 | is allowed for PE-COFF targets, it does not conform to the format | |
742 | specification published by Microsoft. | |
63fd3b82 NC |
743 | |
744 | @kindex --no-omagic | |
745 | @cindex OMAGIC | |
746 | @item --no-omagic | |
747 | This option negates most of the effects of the @option{-N} option. It | |
748 | sets the text section to be read-only, and forces the data segment to | |
749 | be page-aligned. Note - this option does not enable linking against | |
750 | shared libraries. Use @option{-Bdynamic} for this. | |
252b5132 RH |
751 | |
752 | @kindex -o @var{output} | |
753 | @kindex --output=@var{output} | |
754 | @cindex naming the output file | |
755 | @item -o @var{output} | |
756 | @itemx --output=@var{output} | |
ff5dcc92 | 757 | Use @var{output} as the name for the program produced by @command{ld}; if this |
252b5132 RH |
758 | option is not specified, the name @file{a.out} is used by default. The |
759 | script command @code{OUTPUT} can also specify the output file name. | |
760 | ||
761 | @kindex -O @var{level} | |
762 | @cindex generating optimized output | |
763 | @item -O @var{level} | |
ff5dcc92 | 764 | If @var{level} is a numeric values greater than zero @command{ld} optimizes |
252b5132 | 765 | the output. This might take significantly longer and therefore probably |
98c503ac NC |
766 | should only be enabled for the final binary. At the moment this |
767 | option only affects ELF shared library generation. Future releases of | |
768 | the linker may make more use of this option. Also currently there is | |
769 | no difference in the linker's behaviour for different non-zero values | |
770 | of this option. Again this may change with future releases. | |
252b5132 | 771 | |
a712da20 NC |
772 | @kindex -q |
773 | @kindex --emit-relocs | |
774 | @cindex retain relocations in final executable | |
775 | @item -q | |
776 | @itemx --emit-relocs | |
ba1be17e | 777 | Leave relocation sections and contents in fully linked executables. |
a712da20 NC |
778 | Post link analysis and optimization tools may need this information in |
779 | order to perform correct modifications of executables. This results | |
780 | in larger executables. | |
781 | ||
dbab7a7b NC |
782 | This option is currently only supported on ELF platforms. |
783 | ||
4f471f39 RS |
784 | @kindex --force-dynamic |
785 | @cindex forcing the creation of dynamic sections | |
786 | @item --force-dynamic | |
787 | Force the output file to have dynamic sections. This option is specific | |
788 | to VxWorks targets. | |
789 | ||
252b5132 RH |
790 | @cindex partial link |
791 | @cindex relocatable output | |
792 | @kindex -r | |
1049f94e | 793 | @kindex --relocatable |
252b5132 | 794 | @item -r |
1049f94e | 795 | @itemx --relocatable |
252b5132 | 796 | Generate relocatable output---i.e., generate an output file that can in |
ff5dcc92 | 797 | turn serve as input to @command{ld}. This is often called @dfn{partial |
252b5132 RH |
798 | linking}. As a side effect, in environments that support standard Unix |
799 | magic numbers, this option also sets the output file's magic number to | |
800 | @code{OMAGIC}. | |
ff5dcc92 | 801 | @c ; see @option{-N}. |
252b5132 RH |
802 | If this option is not specified, an absolute file is produced. When |
803 | linking C++ programs, this option @emph{will not} resolve references to | |
804 | constructors; to do that, use @samp{-Ur}. | |
805 | ||
62bf86b4 HPN |
806 | When an input file does not have the same format as the output file, |
807 | partial linking is only supported if that input file does not contain any | |
808 | relocations. Different output formats can have further restrictions; for | |
809 | example some @code{a.out}-based formats do not support partial linking | |
810 | with input files in other formats at all. | |
811 | ||
252b5132 RH |
812 | This option does the same thing as @samp{-i}. |
813 | ||
814 | @kindex -R @var{file} | |
815 | @kindex --just-symbols=@var{file} | |
816 | @cindex symbol-only input | |
817 | @item -R @var{filename} | |
818 | @itemx --just-symbols=@var{filename} | |
819 | Read symbol names and their addresses from @var{filename}, but do not | |
820 | relocate it or include it in the output. This allows your output file | |
821 | to refer symbolically to absolute locations of memory defined in other | |
822 | programs. You may use this option more than once. | |
823 | ||
ff5dcc92 | 824 | For compatibility with other ELF linkers, if the @option{-R} option is |
252b5132 | 825 | followed by a directory name, rather than a file name, it is treated as |
ff5dcc92 | 826 | the @option{-rpath} option. |
252b5132 RH |
827 | |
828 | @kindex -s | |
829 | @kindex --strip-all | |
830 | @cindex strip all symbols | |
a1ab1d2a | 831 | @item -s |
252b5132 RH |
832 | @itemx --strip-all |
833 | Omit all symbol information from the output file. | |
834 | ||
835 | @kindex -S | |
836 | @kindex --strip-debug | |
837 | @cindex strip debugger symbols | |
a1ab1d2a | 838 | @item -S |
252b5132 RH |
839 | @itemx --strip-debug |
840 | Omit debugger symbol information (but not all symbols) from the output file. | |
841 | ||
842 | @kindex -t | |
843 | @kindex --trace | |
844 | @cindex input files, displaying | |
a1ab1d2a | 845 | @item -t |
252b5132 | 846 | @itemx --trace |
ff5dcc92 | 847 | Print the names of the input files as @command{ld} processes them. |
252b5132 RH |
848 | |
849 | @kindex -T @var{script} | |
850 | @kindex --script=@var{script} | |
851 | @cindex script files | |
852 | @item -T @var{scriptfile} | |
853 | @itemx --script=@var{scriptfile} | |
854 | Use @var{scriptfile} as the linker script. This script replaces | |
ff5dcc92 | 855 | @command{ld}'s default linker script (rather than adding to it), so |
252b5132 | 856 | @var{commandfile} must specify everything necessary to describe the |
114283d8 NC |
857 | output file. @xref{Scripts}. If @var{scriptfile} does not exist in |
858 | the current directory, @code{ld} looks for it in the directories | |
859 | specified by any preceding @samp{-L} options. Multiple @samp{-T} | |
860 | options accumulate. | |
252b5132 | 861 | |
14be8564 L |
862 | @kindex -dT @var{script} |
863 | @kindex --default-script=@var{script} | |
864 | @cindex script files | |
865 | @item -dT @var{scriptfile} | |
866 | @itemx --default-script=@var{scriptfile} | |
867 | Use @var{scriptfile} as the default linker script. @xref{Scripts}. | |
868 | ||
869 | This option is similar to the @option{--script} option except that | |
870 | processing of the script is delayed until after the rest of the | |
871 | command line has been processed. This allows options placed after the | |
872 | @option{--default-script} option on the command line to affect the | |
873 | behaviour of the linker script, which can be important when the linker | |
874 | command line cannot be directly controlled by the user. (eg because | |
875 | the command line is being constructed by another tool, such as | |
876 | @samp{gcc}). | |
877 | ||
252b5132 RH |
878 | @kindex -u @var{symbol} |
879 | @kindex --undefined=@var{symbol} | |
880 | @cindex undefined symbol | |
881 | @item -u @var{symbol} | |
882 | @itemx --undefined=@var{symbol} | |
883 | Force @var{symbol} to be entered in the output file as an undefined | |
884 | symbol. Doing this may, for example, trigger linking of additional | |
885 | modules from standard libraries. @samp{-u} may be repeated with | |
886 | different option arguments to enter additional undefined symbols. This | |
887 | option is equivalent to the @code{EXTERN} linker script command. | |
888 | ||
889 | @kindex -Ur | |
890 | @cindex constructors | |
a1ab1d2a | 891 | @item -Ur |
252b5132 RH |
892 | For anything other than C++ programs, this option is equivalent to |
893 | @samp{-r}: it generates relocatable output---i.e., an output file that can in | |
ff5dcc92 | 894 | turn serve as input to @command{ld}. When linking C++ programs, @samp{-Ur} |
252b5132 RH |
895 | @emph{does} resolve references to constructors, unlike @samp{-r}. |
896 | It does not work to use @samp{-Ur} on files that were themselves linked | |
897 | with @samp{-Ur}; once the constructor table has been built, it cannot | |
898 | be added to. Use @samp{-Ur} only for the last partial link, and | |
899 | @samp{-r} for the others. | |
900 | ||
577a0623 AM |
901 | @kindex --unique[=@var{SECTION}] |
902 | @item --unique[=@var{SECTION}] | |
903 | Creates a separate output section for every input section matching | |
904 | @var{SECTION}, or if the optional wildcard @var{SECTION} argument is | |
905 | missing, for every orphan input section. An orphan section is one not | |
906 | specifically mentioned in a linker script. You may use this option | |
907 | multiple times on the command line; It prevents the normal merging of | |
908 | input sections with the same name, overriding output section assignments | |
909 | in a linker script. | |
a854a4a7 | 910 | |
252b5132 RH |
911 | @kindex -v |
912 | @kindex -V | |
913 | @kindex --version | |
914 | @cindex version | |
915 | @item -v | |
916 | @itemx --version | |
917 | @itemx -V | |
ff5dcc92 | 918 | Display the version number for @command{ld}. The @option{-V} option also |
252b5132 RH |
919 | lists the supported emulations. |
920 | ||
921 | @kindex -x | |
922 | @kindex --discard-all | |
923 | @cindex deleting local symbols | |
924 | @item -x | |
925 | @itemx --discard-all | |
926 | Delete all local symbols. | |
927 | ||
928 | @kindex -X | |
929 | @kindex --discard-locals | |
930 | @cindex local symbols, deleting | |
a1ab1d2a | 931 | @item -X |
252b5132 | 932 | @itemx --discard-locals |
3c68c38f BW |
933 | Delete all temporary local symbols. (These symbols start with |
934 | system-specific local label prefixes, typically @samp{.L} for ELF systems | |
935 | or @samp{L} for traditional a.out systems.) | |
252b5132 RH |
936 | |
937 | @kindex -y @var{symbol} | |
938 | @kindex --trace-symbol=@var{symbol} | |
939 | @cindex symbol tracing | |
940 | @item -y @var{symbol} | |
941 | @itemx --trace-symbol=@var{symbol} | |
942 | Print the name of each linked file in which @var{symbol} appears. This | |
943 | option may be given any number of times. On many systems it is necessary | |
944 | to prepend an underscore. | |
945 | ||
946 | This option is useful when you have an undefined symbol in your link but | |
947 | don't know where the reference is coming from. | |
948 | ||
949 | @kindex -Y @var{path} | |
950 | @item -Y @var{path} | |
951 | Add @var{path} to the default library search path. This option exists | |
952 | for Solaris compatibility. | |
953 | ||
954 | @kindex -z @var{keyword} | |
955 | @item -z @var{keyword} | |
cd6d6c15 NC |
956 | The recognized keywords are: |
957 | @table @samp | |
958 | ||
959 | @item combreloc | |
960 | Combines multiple reloc sections and sorts them to make dynamic symbol | |
961 | lookup caching possible. | |
962 | ||
963 | @item defs | |
560e09e9 | 964 | Disallows undefined symbols in object files. Undefined symbols in |
07f3b6ad | 965 | shared libraries are still allowed. |
cd6d6c15 | 966 | |
6aa29e7b JJ |
967 | @item execstack |
968 | Marks the object as requiring executable stack. | |
969 | ||
cd6d6c15 NC |
970 | @item initfirst |
971 | This option is only meaningful when building a shared object. | |
972 | It marks the object so that its runtime initialization will occur | |
973 | before the runtime initialization of any other objects brought into | |
974 | the process at the same time. Similarly the runtime finalization of | |
975 | the object will occur after the runtime finalization of any other | |
976 | objects. | |
977 | ||
978 | @item interpose | |
979 | Marks the object that its symbol table interposes before all symbols | |
980 | but the primary executable. | |
981 | ||
5fa222e4 AM |
982 | @item lazy |
983 | When generating an executable or shared library, mark it to tell the | |
984 | dynamic linker to defer function call resolution to the point when | |
985 | the function is called (lazy binding), rather than at load time. | |
986 | Lazy binding is the default. | |
987 | ||
cd6d6c15 NC |
988 | @item loadfltr |
989 | Marks the object that its filters be processed immediately at | |
990 | runtime. | |
991 | ||
992 | @item muldefs | |
993 | Allows multiple definitions. | |
994 | ||
995 | @item nocombreloc | |
996 | Disables multiple reloc sections combining. | |
997 | ||
998 | @item nocopyreloc | |
999 | Disables production of copy relocs. | |
1000 | ||
1001 | @item nodefaultlib | |
1002 | Marks the object that the search for dependencies of this object will | |
1003 | ignore any default library search paths. | |
1004 | ||
1005 | @item nodelete | |
1006 | Marks the object shouldn't be unloaded at runtime. | |
1007 | ||
1008 | @item nodlopen | |
1009 | Marks the object not available to @code{dlopen}. | |
1010 | ||
1011 | @item nodump | |
1012 | Marks the object can not be dumped by @code{dldump}. | |
1013 | ||
6aa29e7b JJ |
1014 | @item noexecstack |
1015 | Marks the object as not requiring executable stack. | |
1016 | ||
1017 | @item norelro | |
1018 | Don't create an ELF @code{PT_GNU_RELRO} segment header in the object. | |
1019 | ||
cd6d6c15 NC |
1020 | @item now |
1021 | When generating an executable or shared library, mark it to tell the | |
1022 | dynamic linker to resolve all symbols when the program is started, or | |
1023 | when the shared library is linked to using dlopen, instead of | |
1024 | deferring function call resolution to the point when the function is | |
1025 | first called. | |
1026 | ||
1027 | @item origin | |
1028 | Marks the object may contain $ORIGIN. | |
1029 | ||
6aa29e7b JJ |
1030 | @item relro |
1031 | Create an ELF @code{PT_GNU_RELRO} segment header in the object. | |
1032 | ||
24718e3b L |
1033 | @item max-page-size=@var{value} |
1034 | Set the emulation maximum page size to @var{value}. | |
1035 | ||
1036 | @item common-page-size=@var{value} | |
1037 | Set the emulation common page size to @var{value}. | |
1038 | ||
cd6d6c15 NC |
1039 | @end table |
1040 | ||
ece2d90e | 1041 | Other keywords are ignored for Solaris compatibility. |
252b5132 RH |
1042 | |
1043 | @kindex -( | |
1044 | @cindex groups of archives | |
1045 | @item -( @var{archives} -) | |
1046 | @itemx --start-group @var{archives} --end-group | |
1047 | The @var{archives} should be a list of archive files. They may be | |
1048 | either explicit file names, or @samp{-l} options. | |
1049 | ||
1050 | The specified archives are searched repeatedly until no new undefined | |
1051 | references are created. Normally, an archive is searched only once in | |
1052 | the order that it is specified on the command line. If a symbol in that | |
1053 | archive is needed to resolve an undefined symbol referred to by an | |
1054 | object in an archive that appears later on the command line, the linker | |
1055 | would not be able to resolve that reference. By grouping the archives, | |
1056 | they all be searched repeatedly until all possible references are | |
1057 | resolved. | |
1058 | ||
1059 | Using this option has a significant performance cost. It is best to use | |
1060 | it only when there are unavoidable circular references between two or | |
1061 | more archives. | |
1062 | ||
69da35b5 NC |
1063 | @kindex --accept-unknown-input-arch |
1064 | @kindex --no-accept-unknown-input-arch | |
1065 | @item --accept-unknown-input-arch | |
1066 | @itemx --no-accept-unknown-input-arch | |
1067 | Tells the linker to accept input files whose architecture cannot be | |
2ca22b03 | 1068 | recognised. The assumption is that the user knows what they are doing |
69da35b5 NC |
1069 | and deliberately wants to link in these unknown input files. This was |
1070 | the default behaviour of the linker, before release 2.14. The default | |
1071 | behaviour from release 2.14 onwards is to reject such input files, and | |
1072 | so the @samp{--accept-unknown-input-arch} option has been added to | |
1073 | restore the old behaviour. | |
2ca22b03 | 1074 | |
4a43e768 AM |
1075 | @kindex --as-needed |
1076 | @kindex --no-as-needed | |
1077 | @item --as-needed | |
1078 | @itemx --no-as-needed | |
1079 | This option affects ELF DT_NEEDED tags for dynamic libraries mentioned | |
1080 | on the command line after the @option{--as-needed} option. Normally, | |
1081 | the linker will add a DT_NEEDED tag for each dynamic library mentioned | |
1082 | on the command line, regardless of whether the library is actually | |
77cfaee6 AM |
1083 | needed. @option{--as-needed} causes DT_NEEDED tags to only be emitted |
1084 | for libraries that satisfy some symbol reference from regular objects | |
1085 | which is undefined at the point that the library was linked. | |
4a43e768 AM |
1086 | @option{--no-as-needed} restores the default behaviour. |
1087 | ||
e56f61be L |
1088 | @kindex --add-needed |
1089 | @kindex --no-add-needed | |
1090 | @item --add-needed | |
1091 | @itemx --no-add-needed | |
1092 | This option affects the treatment of dynamic libraries from ELF | |
1093 | DT_NEEDED tags in dynamic libraries mentioned on the command line after | |
1094 | the @option{--no-add-needed} option. Normally, the linker will add | |
1095 | a DT_NEEDED tag for each dynamic library from DT_NEEDED tags. | |
1096 | @option{--no-add-needed} causes DT_NEEDED tags will never be emitted | |
1097 | for those libraries from DT_NEEDED tags. @option{--add-needed} restores | |
1098 | the default behaviour. | |
1099 | ||
252b5132 RH |
1100 | @kindex -assert @var{keyword} |
1101 | @item -assert @var{keyword} | |
1102 | This option is ignored for SunOS compatibility. | |
1103 | ||
1104 | @kindex -Bdynamic | |
1105 | @kindex -dy | |
1106 | @kindex -call_shared | |
1107 | @item -Bdynamic | |
1108 | @itemx -dy | |
1109 | @itemx -call_shared | |
1110 | Link against dynamic libraries. This is only meaningful on platforms | |
1111 | for which shared libraries are supported. This option is normally the | |
1112 | default on such platforms. The different variants of this option are | |
1113 | for compatibility with various systems. You may use this option | |
1114 | multiple times on the command line: it affects library searching for | |
da8bce14 | 1115 | @option{-l} options which follow it. |
252b5132 | 1116 | |
a1ab1d2a UD |
1117 | @kindex -Bgroup |
1118 | @item -Bgroup | |
1119 | Set the @code{DF_1_GROUP} flag in the @code{DT_FLAGS_1} entry in the dynamic | |
1120 | section. This causes the runtime linker to handle lookups in this | |
1121 | object and its dependencies to be performed only inside the group. | |
560e09e9 NC |
1122 | @option{--unresolved-symbols=report-all} is implied. This option is |
1123 | only meaningful on ELF platforms which support shared libraries. | |
a1ab1d2a | 1124 | |
252b5132 RH |
1125 | @kindex -Bstatic |
1126 | @kindex -dn | |
1127 | @kindex -non_shared | |
1128 | @kindex -static | |
a1ab1d2a | 1129 | @item -Bstatic |
252b5132 RH |
1130 | @itemx -dn |
1131 | @itemx -non_shared | |
1132 | @itemx -static | |
1133 | Do not link against shared libraries. This is only meaningful on | |
1134 | platforms for which shared libraries are supported. The different | |
1135 | variants of this option are for compatibility with various systems. You | |
1136 | may use this option multiple times on the command line: it affects | |
560e09e9 | 1137 | library searching for @option{-l} options which follow it. This |
e9156f74 NC |
1138 | option also implies @option{--unresolved-symbols=report-all}. This |
1139 | option can be used with @option{-shared}. Doing so means that a | |
1140 | shared library is being created but that all of the library's external | |
1141 | references must be resolved by pulling in entries from static | |
ece2d90e | 1142 | libraries. |
252b5132 RH |
1143 | |
1144 | @kindex -Bsymbolic | |
1145 | @item -Bsymbolic | |
1146 | When creating a shared library, bind references to global symbols to the | |
1147 | definition within the shared library, if any. Normally, it is possible | |
1148 | for a program linked against a shared library to override the definition | |
1149 | within the shared library. This option is only meaningful on ELF | |
1150 | platforms which support shared libraries. | |
1151 | ||
40b36307 L |
1152 | @kindex -Bsymbolic-functions |
1153 | @item -Bsymbolic-functions | |
1154 | When creating a shared library, bind references to global function | |
c0065db7 | 1155 | symbols to the definition within the shared library, if any. |
40b36307 L |
1156 | This option is only meaningful on ELF platforms which support shared |
1157 | libraries. | |
1158 | ||
55255dae L |
1159 | @kindex --dynamic-list=@var{dynamic-list-file} |
1160 | @item --dynamic-list=@var{dynamic-list-file} | |
1161 | Specify the name of a dynamic list file to the linker. This is | |
1162 | typically used when creating shared libraries to specify a list of | |
1163 | global symbols whose references shouldn't be bound to the definition | |
1164 | within the shared library, or creating dynamically linked executables | |
1165 | to specify a list of symbols which should be added to the symbol table | |
1166 | in the executable. This option is only meaningful on ELF platforms | |
1167 | which support shared libraries. | |
1168 | ||
1169 | The format of the dynamic list is the same as the version node without | |
1170 | scope and node name. See @ref{VERSION} for more information. | |
1171 | ||
40b36307 L |
1172 | @kindex --dynamic-list-data |
1173 | @item --dynamic-list-data | |
1174 | Include all global data symbols to the dynamic list. | |
1175 | ||
1176 | @kindex --dynamic-list-cpp-new | |
1177 | @item --dynamic-list-cpp-new | |
1178 | Provide the builtin dynamic list for C++ operator new and delete. It | |
1179 | is mainly useful for building shared libstdc++. | |
1180 | ||
0b8a70d9 L |
1181 | @kindex --dynamic-list-cpp-typeinfo |
1182 | @item --dynamic-list-cpp-typeinfo | |
1183 | Provide the builtin dynamic list for C++ runtime type identification. | |
1184 | ||
252b5132 RH |
1185 | @kindex --check-sections |
1186 | @kindex --no-check-sections | |
1187 | @item --check-sections | |
308b1ffd | 1188 | @itemx --no-check-sections |
252b5132 | 1189 | Asks the linker @emph{not} to check section addresses after they have |
7d816a17 | 1190 | been assigned to see if there are any overlaps. Normally the linker will |
252b5132 RH |
1191 | perform this check, and if it finds any overlaps it will produce |
1192 | suitable error messages. The linker does know about, and does make | |
1193 | allowances for sections in overlays. The default behaviour can be | |
560e09e9 | 1194 | restored by using the command line switch @option{--check-sections}. |
252b5132 RH |
1195 | |
1196 | @cindex cross reference table | |
1197 | @kindex --cref | |
1198 | @item --cref | |
1199 | Output a cross reference table. If a linker map file is being | |
1200 | generated, the cross reference table is printed to the map file. | |
1201 | Otherwise, it is printed on the standard output. | |
1202 | ||
1203 | The format of the table is intentionally simple, so that it may be | |
1204 | easily processed by a script if necessary. The symbols are printed out, | |
1205 | sorted by name. For each symbol, a list of file names is given. If the | |
1206 | symbol is defined, the first file listed is the location of the | |
1207 | definition. The remaining files contain references to the symbol. | |
1208 | ||
4818e05f AM |
1209 | @cindex common allocation |
1210 | @kindex --no-define-common | |
1211 | @item --no-define-common | |
1212 | This option inhibits the assignment of addresses to common symbols. | |
1213 | The script command @code{INHIBIT_COMMON_ALLOCATION} has the same effect. | |
1214 | @xref{Miscellaneous Commands}. | |
1215 | ||
1216 | The @samp{--no-define-common} option allows decoupling | |
1217 | the decision to assign addresses to Common symbols from the choice | |
1218 | of the output file type; otherwise a non-Relocatable output type | |
1219 | forces assigning addresses to Common symbols. | |
1220 | Using @samp{--no-define-common} allows Common symbols that are referenced | |
1221 | from a shared library to be assigned addresses only in the main program. | |
1222 | This eliminates the unused duplicate space in the shared library, | |
1223 | and also prevents any possible confusion over resolving to the wrong | |
1224 | duplicate when there are many dynamic modules with specialized search | |
1225 | paths for runtime symbol resolution. | |
1226 | ||
252b5132 RH |
1227 | @cindex symbols, from command line |
1228 | @kindex --defsym @var{symbol}=@var{exp} | |
1229 | @item --defsym @var{symbol}=@var{expression} | |
1230 | Create a global symbol in the output file, containing the absolute | |
1231 | address given by @var{expression}. You may use this option as many | |
1232 | times as necessary to define multiple symbols in the command line. A | |
1233 | limited form of arithmetic is supported for the @var{expression} in this | |
1234 | context: you may give a hexadecimal constant or the name of an existing | |
1235 | symbol, or use @code{+} and @code{-} to add or subtract hexadecimal | |
1236 | constants or symbols. If you need more elaborate expressions, consider | |
1237 | using the linker command language from a script (@pxref{Assignments,, | |
1238 | Assignment: Symbol Definitions}). @emph{Note:} there should be no white | |
1239 | space between @var{symbol}, the equals sign (``@key{=}''), and | |
1240 | @var{expression}. | |
1241 | ||
1242 | @cindex demangling, from command line | |
28c309a2 | 1243 | @kindex --demangle[=@var{style}] |
252b5132 | 1244 | @kindex --no-demangle |
28c309a2 | 1245 | @item --demangle[=@var{style}] |
252b5132 RH |
1246 | @itemx --no-demangle |
1247 | These options control whether to demangle symbol names in error messages | |
1248 | and other output. When the linker is told to demangle, it tries to | |
1249 | present symbol names in a readable fashion: it strips leading | |
1250 | underscores if they are used by the object file format, and converts C++ | |
a1ab1d2a UD |
1251 | mangled symbol names into user readable names. Different compilers have |
1252 | different mangling styles. The optional demangling style argument can be used | |
1253 | to choose an appropriate demangling style for your compiler. The linker will | |
28c309a2 NC |
1254 | demangle by default unless the environment variable @samp{COLLECT_NO_DEMANGLE} |
1255 | is set. These options may be used to override the default. | |
252b5132 RH |
1256 | |
1257 | @cindex dynamic linker, from command line | |
506eee22 | 1258 | @kindex -I@var{file} |
252b5132 RH |
1259 | @kindex --dynamic-linker @var{file} |
1260 | @item --dynamic-linker @var{file} | |
1261 | Set the name of the dynamic linker. This is only meaningful when | |
1262 | generating dynamically linked ELF executables. The default dynamic | |
1263 | linker is normally correct; don't use this unless you know what you are | |
1264 | doing. | |
1265 | ||
7ce691ae | 1266 | @kindex --fatal-warnings |
0fe58ccd | 1267 | @kindex --no-fatal-warnings |
7ce691ae | 1268 | @item --fatal-warnings |
0fe58ccd NC |
1269 | @itemx --no-fatal-warnings |
1270 | Treat all warnings as errors. The default behaviour can be restored | |
1271 | with the option @option{--no-fatal-warnings}. | |
7ce691ae | 1272 | |
252b5132 RH |
1273 | @kindex --force-exe-suffix |
1274 | @item --force-exe-suffix | |
1275 | Make sure that an output file has a .exe suffix. | |
1276 | ||
1277 | If a successfully built fully linked output file does not have a | |
1278 | @code{.exe} or @code{.dll} suffix, this option forces the linker to copy | |
1279 | the output file to one of the same name with a @code{.exe} suffix. This | |
1280 | option is useful when using unmodified Unix makefiles on a Microsoft | |
1281 | Windows host, since some versions of Windows won't run an image unless | |
1282 | it ends in a @code{.exe} suffix. | |
1283 | ||
1284 | @kindex --gc-sections | |
1285 | @kindex --no-gc-sections | |
1286 | @cindex garbage collection | |
c17d87de NC |
1287 | @item --gc-sections |
1288 | @itemx --no-gc-sections | |
252b5132 | 1289 | Enable garbage collection of unused input sections. It is ignored on |
ac69cbc6 | 1290 | targets that do not support this option. The default behaviour (of not |
b3549761 NC |
1291 | performing this garbage collection) can be restored by specifying |
1292 | @samp{--no-gc-sections} on the command line. | |
252b5132 | 1293 | |
d5465ba2 AM |
1294 | @samp{--gc-sections} decides which input sections are used by |
1295 | examining symbols and relocations. The section containing the entry | |
1296 | symbol and all sections containing symbols undefined on the | |
1297 | command-line will be kept, as will sections containing symbols | |
1298 | referenced by dynamic objects. Note that when building shared | |
1299 | libraries, the linker must assume that any visible symbol is | |
1300 | referenced. Once this initial set of sections has been determined, | |
1301 | the linker recursively marks as used any section referenced by their | |
1302 | relocations. See @samp{--entry} and @samp{--undefined}. | |
1303 | ||
ac69cbc6 TG |
1304 | This option can be set when doing a partial link (enabled with option |
1305 | @samp{-r}). In this case the root of symbols kept must be explicitely | |
1306 | specified either by an @samp{--entry} or @samp{--undefined} option or by | |
1307 | a @code{ENTRY} command in the linker script. | |
1308 | ||
c17d87de NC |
1309 | @kindex --print-gc-sections |
1310 | @kindex --no-print-gc-sections | |
1311 | @cindex garbage collection | |
1312 | @item --print-gc-sections | |
1313 | @itemx --no-print-gc-sections | |
1314 | List all sections removed by garbage collection. The listing is | |
1315 | printed on stderr. This option is only effective if garbage | |
1316 | collection has been enabled via the @samp{--gc-sections}) option. The | |
1317 | default behaviour (of not listing the sections that are removed) can | |
1318 | be restored by specifying @samp{--no-print-gc-sections} on the command | |
1319 | line. | |
1320 | ||
252b5132 RH |
1321 | @cindex help |
1322 | @cindex usage | |
1323 | @kindex --help | |
1324 | @item --help | |
1325 | Print a summary of the command-line options on the standard output and exit. | |
1326 | ||
ea20a7da CC |
1327 | @kindex --target-help |
1328 | @item --target-help | |
1329 | Print a summary of all target specific options on the standard output and exit. | |
1330 | ||
252b5132 RH |
1331 | @kindex -Map |
1332 | @item -Map @var{mapfile} | |
1333 | Print a link map to the file @var{mapfile}. See the description of the | |
560e09e9 | 1334 | @option{-M} option, above. |
252b5132 RH |
1335 | |
1336 | @cindex memory usage | |
1337 | @kindex --no-keep-memory | |
1338 | @item --no-keep-memory | |
ff5dcc92 SC |
1339 | @command{ld} normally optimizes for speed over memory usage by caching the |
1340 | symbol tables of input files in memory. This option tells @command{ld} to | |
252b5132 | 1341 | instead optimize for memory usage, by rereading the symbol tables as |
ff5dcc92 | 1342 | necessary. This may be required if @command{ld} runs out of memory space |
252b5132 RH |
1343 | while linking a large executable. |
1344 | ||
1345 | @kindex --no-undefined | |
a1ab1d2a | 1346 | @kindex -z defs |
252b5132 | 1347 | @item --no-undefined |
a1ab1d2a | 1348 | @itemx -z defs |
560e09e9 NC |
1349 | Report unresolved symbol references from regular object files. This |
1350 | is done even if the linker is creating a non-symbolic shared library. | |
1351 | The switch @option{--[no-]allow-shlib-undefined} controls the | |
1352 | behaviour for reporting unresolved references found in shared | |
ece2d90e | 1353 | libraries being linked in. |
252b5132 | 1354 | |
aa713662 L |
1355 | @kindex --allow-multiple-definition |
1356 | @kindex -z muldefs | |
1357 | @item --allow-multiple-definition | |
1358 | @itemx -z muldefs | |
1359 | Normally when a symbol is defined multiple times, the linker will | |
1360 | report a fatal error. These options allow multiple definitions and the | |
1361 | first definition will be used. | |
1362 | ||
b79e8c78 | 1363 | @kindex --allow-shlib-undefined |
ae9a127f | 1364 | @kindex --no-allow-shlib-undefined |
b79e8c78 | 1365 | @item --allow-shlib-undefined |
ae9a127f | 1366 | @itemx --no-allow-shlib-undefined |
560e09e9 NC |
1367 | Allows (the default) or disallows undefined symbols in shared libraries. |
1368 | This switch is similar to @option{--no-undefined} except that it | |
1369 | determines the behaviour when the undefined symbols are in a | |
1370 | shared library rather than a regular object file. It does not affect | |
1371 | how undefined symbols in regular object files are handled. | |
1372 | ||
1373 | The reason that @option{--allow-shlib-undefined} is the default is that | |
1374 | the shared library being specified at link time may not be the same as | |
1375 | the one that is available at load time, so the symbols might actually be | |
ae9a127f | 1376 | resolvable at load time. Plus there are some systems, (eg BeOS) where |
560e09e9 | 1377 | undefined symbols in shared libraries is normal. (The kernel patches |
ece2d90e | 1378 | them at load time to select which function is most appropriate |
560e09e9 NC |
1379 | for the current architecture. This is used for example to dynamically |
1380 | select an appropriate memset function). Apparently it is also normal | |
1381 | for HPPA shared libraries to have undefined symbols. | |
b79e8c78 | 1382 | |
31941635 L |
1383 | @kindex --no-undefined-version |
1384 | @item --no-undefined-version | |
1385 | Normally when a symbol has an undefined version, the linker will ignore | |
1386 | it. This option disallows symbols with undefined version and a fatal error | |
1387 | will be issued instead. | |
1388 | ||
3e3b46e5 PB |
1389 | @kindex --default-symver |
1390 | @item --default-symver | |
1391 | Create and use a default symbol version (the soname) for unversioned | |
fc0e6df6 PB |
1392 | exported symbols. |
1393 | ||
1394 | @kindex --default-imported-symver | |
1395 | @item --default-imported-symver | |
1396 | Create and use a default symbol version (the soname) for unversioned | |
1397 | imported symbols. | |
3e3b46e5 | 1398 | |
252b5132 RH |
1399 | @kindex --no-warn-mismatch |
1400 | @item --no-warn-mismatch | |
ff5dcc92 | 1401 | Normally @command{ld} will give an error if you try to link together input |
252b5132 RH |
1402 | files that are mismatched for some reason, perhaps because they have |
1403 | been compiled for different processors or for different endiannesses. | |
ff5dcc92 | 1404 | This option tells @command{ld} that it should silently permit such possible |
252b5132 RH |
1405 | errors. This option should only be used with care, in cases when you |
1406 | have taken some special action that ensures that the linker errors are | |
1407 | inappropriate. | |
1408 | ||
fe7929ce AM |
1409 | @kindex --no-warn-search-mismatch |
1410 | @item --no-warn-search-mismatch | |
1411 | Normally @command{ld} will give a warning if it finds an incompatible | |
1412 | library during a library search. This option silences the warning. | |
1413 | ||
252b5132 RH |
1414 | @kindex --no-whole-archive |
1415 | @item --no-whole-archive | |
ff5dcc92 | 1416 | Turn off the effect of the @option{--whole-archive} option for subsequent |
252b5132 RH |
1417 | archive files. |
1418 | ||
1419 | @cindex output file after errors | |
1420 | @kindex --noinhibit-exec | |
1421 | @item --noinhibit-exec | |
1422 | Retain the executable output file whenever it is still usable. | |
1423 | Normally, the linker will not produce an output file if it encounters | |
1424 | errors during the link process; it exits without writing an output file | |
1425 | when it issues any error whatsoever. | |
1426 | ||
0a9c1c8e CD |
1427 | @kindex -nostdlib |
1428 | @item -nostdlib | |
1429 | Only search library directories explicitly specified on the | |
1430 | command line. Library directories specified in linker scripts | |
1431 | (including linker scripts specified on the command line) are ignored. | |
1432 | ||
252b5132 RH |
1433 | @ifclear SingleFormat |
1434 | @kindex --oformat | |
1435 | @item --oformat @var{output-format} | |
ff5dcc92 SC |
1436 | @command{ld} may be configured to support more than one kind of object |
1437 | file. If your @command{ld} is configured this way, you can use the | |
252b5132 | 1438 | @samp{--oformat} option to specify the binary format for the output |
ff5dcc92 SC |
1439 | object file. Even when @command{ld} is configured to support alternative |
1440 | object formats, you don't usually need to specify this, as @command{ld} | |
252b5132 RH |
1441 | should be configured to produce as a default output format the most |
1442 | usual format on each machine. @var{output-format} is a text string, the | |
1443 | name of a particular format supported by the BFD libraries. (You can | |
1444 | list the available binary formats with @samp{objdump -i}.) The script | |
1445 | command @code{OUTPUT_FORMAT} can also specify the output format, but | |
1446 | this option overrides it. @xref{BFD}. | |
1447 | @end ifclear | |
1448 | ||
36af4a4e JJ |
1449 | @kindex -pie |
1450 | @kindex --pic-executable | |
1451 | @item -pie | |
1452 | @itemx --pic-executable | |
1453 | @cindex position independent executables | |
1454 | Create a position independent executable. This is currently only supported on | |
1455 | ELF platforms. Position independent executables are similar to shared | |
1456 | libraries in that they are relocated by the dynamic linker to the virtual | |
7e7d5768 | 1457 | address the OS chooses for them (which can vary between invocations). Like |
36af4a4e JJ |
1458 | normal dynamically linked executables they can be executed and symbols |
1459 | defined in the executable cannot be overridden by shared libraries. | |
1460 | ||
252b5132 RH |
1461 | @kindex -qmagic |
1462 | @item -qmagic | |
1463 | This option is ignored for Linux compatibility. | |
1464 | ||
1465 | @kindex -Qy | |
1466 | @item -Qy | |
1467 | This option is ignored for SVR4 compatibility. | |
1468 | ||
1469 | @kindex --relax | |
1470 | @cindex synthesizing linker | |
1471 | @cindex relaxing addressing modes | |
1472 | @item --relax | |
a1ab1d2a | 1473 | An option with machine dependent effects. |
252b5132 RH |
1474 | @ifset GENERIC |
1475 | This option is only supported on a few targets. | |
1476 | @end ifset | |
1477 | @ifset H8300 | |
ff5dcc92 | 1478 | @xref{H8/300,,@command{ld} and the H8/300}. |
252b5132 RH |
1479 | @end ifset |
1480 | @ifset I960 | |
ff5dcc92 | 1481 | @xref{i960,, @command{ld} and the Intel 960 family}. |
252b5132 | 1482 | @end ifset |
e0001a05 NC |
1483 | @ifset XTENSA |
1484 | @xref{Xtensa,, @command{ld} and Xtensa Processors}. | |
1485 | @end ifset | |
93fd0973 SC |
1486 | @ifset M68HC11 |
1487 | @xref{M68HC11/68HC12,,@command{ld} and the 68HC11 and 68HC12}. | |
1488 | @end ifset | |
2a60a7a8 AM |
1489 | @ifset POWERPC |
1490 | @xref{PowerPC ELF32,,@command{ld} and PowerPC 32-bit ELF Support}. | |
1491 | @end ifset | |
252b5132 RH |
1492 | |
1493 | On some platforms, the @samp{--relax} option performs global | |
1494 | optimizations that become possible when the linker resolves addressing | |
1495 | in the program, such as relaxing address modes and synthesizing new | |
1496 | instructions in the output object file. | |
1497 | ||
1498 | On some platforms these link time global optimizations may make symbolic | |
1499 | debugging of the resulting executable impossible. | |
1500 | @ifset GENERIC | |
1501 | This is known to be | |
1502 | the case for the Matsushita MN10200 and MN10300 family of processors. | |
1503 | @end ifset | |
1504 | ||
1505 | @ifset GENERIC | |
1506 | On platforms where this is not supported, @samp{--relax} is accepted, | |
1507 | but ignored. | |
1508 | @end ifset | |
1509 | ||
1510 | @cindex retaining specified symbols | |
1511 | @cindex stripping all but some symbols | |
1512 | @cindex symbols, retaining selectively | |
1513 | @item --retain-symbols-file @var{filename} | |
1514 | Retain @emph{only} the symbols listed in the file @var{filename}, | |
1515 | discarding all others. @var{filename} is simply a flat file, with one | |
1516 | symbol name per line. This option is especially useful in environments | |
1517 | @ifset GENERIC | |
1518 | (such as VxWorks) | |
1519 | @end ifset | |
1520 | where a large global symbol table is accumulated gradually, to conserve | |
1521 | run-time memory. | |
1522 | ||
1523 | @samp{--retain-symbols-file} does @emph{not} discard undefined symbols, | |
1524 | or symbols needed for relocations. | |
1525 | ||
1526 | You may only specify @samp{--retain-symbols-file} once in the command | |
1527 | line. It overrides @samp{-s} and @samp{-S}. | |
1528 | ||
1529 | @ifset GENERIC | |
1530 | @item -rpath @var{dir} | |
1531 | @cindex runtime library search path | |
1532 | @kindex -rpath | |
1533 | Add a directory to the runtime library search path. This is used when | |
ff5dcc92 | 1534 | linking an ELF executable with shared objects. All @option{-rpath} |
252b5132 | 1535 | arguments are concatenated and passed to the runtime linker, which uses |
ff5dcc92 | 1536 | them to locate shared objects at runtime. The @option{-rpath} option is |
252b5132 RH |
1537 | also used when locating shared objects which are needed by shared |
1538 | objects explicitly included in the link; see the description of the | |
ff5dcc92 | 1539 | @option{-rpath-link} option. If @option{-rpath} is not used when linking an |
252b5132 RH |
1540 | ELF executable, the contents of the environment variable |
1541 | @code{LD_RUN_PATH} will be used if it is defined. | |
1542 | ||
ff5dcc92 | 1543 | The @option{-rpath} option may also be used on SunOS. By default, on |
252b5132 | 1544 | SunOS, the linker will form a runtime search patch out of all the |
ff5dcc92 SC |
1545 | @option{-L} options it is given. If a @option{-rpath} option is used, the |
1546 | runtime search path will be formed exclusively using the @option{-rpath} | |
1547 | options, ignoring the @option{-L} options. This can be useful when using | |
1548 | gcc, which adds many @option{-L} options which may be on NFS mounted | |
b45619c0 | 1549 | file systems. |
252b5132 | 1550 | |
ff5dcc92 | 1551 | For compatibility with other ELF linkers, if the @option{-R} option is |
252b5132 | 1552 | followed by a directory name, rather than a file name, it is treated as |
ff5dcc92 | 1553 | the @option{-rpath} option. |
252b5132 RH |
1554 | @end ifset |
1555 | ||
1556 | @ifset GENERIC | |
1557 | @cindex link-time runtime library search path | |
1558 | @kindex -rpath-link | |
1559 | @item -rpath-link @var{DIR} | |
1560 | When using ELF or SunOS, one shared library may require another. This | |
1561 | happens when an @code{ld -shared} link includes a shared library as one | |
1562 | of the input files. | |
1563 | ||
1564 | When the linker encounters such a dependency when doing a non-shared, | |
1565 | non-relocatable link, it will automatically try to locate the required | |
1566 | shared library and include it in the link, if it is not included | |
ff5dcc92 | 1567 | explicitly. In such a case, the @option{-rpath-link} option |
252b5132 | 1568 | specifies the first set of directories to search. The |
ff5dcc92 | 1569 | @option{-rpath-link} option may specify a sequence of directory names |
252b5132 RH |
1570 | either by specifying a list of names separated by colons, or by |
1571 | appearing multiple times. | |
1572 | ||
28c309a2 NC |
1573 | This option should be used with caution as it overrides the search path |
1574 | that may have been hard compiled into a shared library. In such a case it | |
1575 | is possible to use unintentionally a different search path than the | |
1576 | runtime linker would do. | |
1577 | ||
252b5132 | 1578 | The linker uses the following search paths to locate required shared |
ece2d90e | 1579 | libraries: |
252b5132 RH |
1580 | @enumerate |
1581 | @item | |
ff5dcc92 | 1582 | Any directories specified by @option{-rpath-link} options. |
252b5132 | 1583 | @item |
ff5dcc92 SC |
1584 | Any directories specified by @option{-rpath} options. The difference |
1585 | between @option{-rpath} and @option{-rpath-link} is that directories | |
1586 | specified by @option{-rpath} options are included in the executable and | |
1587 | used at runtime, whereas the @option{-rpath-link} option is only effective | |
ece2d90e NC |
1588 | at link time. Searching @option{-rpath} in this way is only supported |
1589 | by native linkers and cross linkers which have been configured with | |
1590 | the @option{--with-sysroot} option. | |
252b5132 | 1591 | @item |
e2a83dd0 NC |
1592 | On an ELF system, for native linkers, if the @option{-rpath} and |
1593 | @option{-rpath-link} options were not used, search the contents of the | |
1594 | environment variable @code{LD_RUN_PATH}. | |
252b5132 | 1595 | @item |
ff5dcc92 SC |
1596 | On SunOS, if the @option{-rpath} option was not used, search any |
1597 | directories specified using @option{-L} options. | |
252b5132 | 1598 | @item |
e2a83dd0 NC |
1599 | For a native linker, the search the contents of the environment |
1600 | variable @code{LD_LIBRARY_PATH}. | |
252b5132 | 1601 | @item |
ec4eb78a L |
1602 | For a native ELF linker, the directories in @code{DT_RUNPATH} or |
1603 | @code{DT_RPATH} of a shared library are searched for shared | |
1604 | libraries needed by it. The @code{DT_RPATH} entries are ignored if | |
1605 | @code{DT_RUNPATH} entries exist. | |
1606 | @item | |
252b5132 RH |
1607 | The default directories, normally @file{/lib} and @file{/usr/lib}. |
1608 | @item | |
1609 | For a native linker on an ELF system, if the file @file{/etc/ld.so.conf} | |
1610 | exists, the list of directories found in that file. | |
1611 | @end enumerate | |
1612 | ||
1613 | If the required shared library is not found, the linker will issue a | |
1614 | warning and continue with the link. | |
1615 | @end ifset | |
1616 | ||
1617 | @kindex -shared | |
1618 | @kindex -Bshareable | |
1619 | @item -shared | |
1620 | @itemx -Bshareable | |
1621 | @cindex shared libraries | |
1622 | Create a shared library. This is currently only supported on ELF, XCOFF | |
1623 | and SunOS platforms. On SunOS, the linker will automatically create a | |
ff5dcc92 | 1624 | shared library if the @option{-e} option is not used and there are |
252b5132 RH |
1625 | undefined symbols in the link. |
1626 | ||
de7dd2bd | 1627 | @item --sort-common [= ascending | descending] |
252b5132 | 1628 | @kindex --sort-common |
de7dd2bd NC |
1629 | This option tells @command{ld} to sort the common symbols by alignment in |
1630 | ascending or descending order when it places them in the appropriate output | |
1631 | sections. The symbol alignments considered are sixteen-byte or larger, | |
1632 | eight-byte, four-byte, two-byte, and one-byte. This is to prevent gaps | |
1633 | between symbols due to alignment constraints. If no sorting order is | |
1634 | specified, then descending order is assumed. | |
252b5132 | 1635 | |
bcaa7b3e L |
1636 | @kindex --sort-section name |
1637 | @item --sort-section name | |
1638 | This option will apply @code{SORT_BY_NAME} to all wildcard section | |
1639 | patterns in the linker script. | |
1640 | ||
1641 | @kindex --sort-section alignment | |
1642 | @item --sort-section alignment | |
1643 | This option will apply @code{SORT_BY_ALIGNMENT} to all wildcard section | |
1644 | patterns in the linker script. | |
1645 | ||
252b5132 | 1646 | @kindex --split-by-file |
a854a4a7 | 1647 | @item --split-by-file [@var{size}] |
ff5dcc92 | 1648 | Similar to @option{--split-by-reloc} but creates a new output section for |
a854a4a7 AM |
1649 | each input file when @var{size} is reached. @var{size} defaults to a |
1650 | size of 1 if not given. | |
252b5132 RH |
1651 | |
1652 | @kindex --split-by-reloc | |
a854a4a7 AM |
1653 | @item --split-by-reloc [@var{count}] |
1654 | Tries to creates extra sections in the output file so that no single | |
252b5132 | 1655 | output section in the file contains more than @var{count} relocations. |
a854a4a7 | 1656 | This is useful when generating huge relocatable files for downloading into |
252b5132 RH |
1657 | certain real time kernels with the COFF object file format; since COFF |
1658 | cannot represent more than 65535 relocations in a single section. Note | |
1659 | that this will fail to work with object file formats which do not | |
1660 | support arbitrary sections. The linker will not split up individual | |
1661 | input sections for redistribution, so if a single input section contains | |
1662 | more than @var{count} relocations one output section will contain that | |
a854a4a7 | 1663 | many relocations. @var{count} defaults to a value of 32768. |
252b5132 RH |
1664 | |
1665 | @kindex --stats | |
1666 | @item --stats | |
1667 | Compute and display statistics about the operation of the linker, such | |
1668 | as execution time and memory usage. | |
1669 | ||
e2243057 RS |
1670 | @kindex --sysroot |
1671 | @item --sysroot=@var{directory} | |
1672 | Use @var{directory} as the location of the sysroot, overriding the | |
1673 | configure-time default. This option is only supported by linkers | |
1674 | that were configured using @option{--with-sysroot}. | |
1675 | ||
252b5132 RH |
1676 | @kindex --traditional-format |
1677 | @cindex traditional format | |
1678 | @item --traditional-format | |
ff5dcc92 SC |
1679 | For some targets, the output of @command{ld} is different in some ways from |
1680 | the output of some existing linker. This switch requests @command{ld} to | |
252b5132 RH |
1681 | use the traditional format instead. |
1682 | ||
1683 | @cindex dbx | |
ff5dcc92 | 1684 | For example, on SunOS, @command{ld} combines duplicate entries in the |
252b5132 RH |
1685 | symbol string table. This can reduce the size of an output file with |
1686 | full debugging information by over 30 percent. Unfortunately, the SunOS | |
1687 | @code{dbx} program can not read the resulting program (@code{gdb} has no | |
ff5dcc92 | 1688 | trouble). The @samp{--traditional-format} switch tells @command{ld} to not |
252b5132 RH |
1689 | combine duplicate entries. |
1690 | ||
176355da NC |
1691 | @kindex --section-start @var{sectionname}=@var{org} |
1692 | @item --section-start @var{sectionname}=@var{org} | |
1693 | Locate a section in the output file at the absolute | |
1694 | address given by @var{org}. You may use this option as many | |
1695 | times as necessary to locate multiple sections in the command | |
1696 | line. | |
1697 | @var{org} must be a single hexadecimal integer; | |
1698 | for compatibility with other linkers, you may omit the leading | |
1699 | @samp{0x} usually associated with hexadecimal values. @emph{Note:} there | |
1700 | should be no white space between @var{sectionname}, the equals | |
1701 | sign (``@key{=}''), and @var{org}. | |
1702 | ||
252b5132 RH |
1703 | @kindex -Tbss @var{org} |
1704 | @kindex -Tdata @var{org} | |
1705 | @kindex -Ttext @var{org} | |
1706 | @cindex segment origins, cmd line | |
1707 | @item -Tbss @var{org} | |
1708 | @itemx -Tdata @var{org} | |
1709 | @itemx -Ttext @var{org} | |
a6e02871 AO |
1710 | Same as --section-start, with @code{.bss}, @code{.data} or |
1711 | @code{.text} as the @var{sectionname}. | |
252b5132 | 1712 | |
560e09e9 NC |
1713 | @kindex --unresolved-symbols |
1714 | @item --unresolved-symbols=@var{method} | |
1715 | Determine how to handle unresolved symbols. There are four possible | |
1716 | values for @samp{method}: | |
1717 | ||
1718 | @table @samp | |
1719 | @item ignore-all | |
da8bce14 | 1720 | Do not report any unresolved symbols. |
560e09e9 NC |
1721 | |
1722 | @item report-all | |
da8bce14 | 1723 | Report all unresolved symbols. This is the default. |
560e09e9 NC |
1724 | |
1725 | @item ignore-in-object-files | |
1726 | Report unresolved symbols that are contained in shared libraries, but | |
1727 | ignore them if they come from regular object files. | |
1728 | ||
1729 | @item ignore-in-shared-libs | |
1730 | Report unresolved symbols that come from regular object files, but | |
1731 | ignore them if they come from shared libraries. This can be useful | |
1732 | when creating a dynamic binary and it is known that all the shared | |
1733 | libraries that it should be referencing are included on the linker's | |
1734 | command line. | |
1735 | @end table | |
1736 | ||
1737 | The behaviour for shared libraries on their own can also be controlled | |
1738 | by the @option{--[no-]allow-shlib-undefined} option. | |
1739 | ||
1740 | Normally the linker will generate an error message for each reported | |
1741 | unresolved symbol but the option @option{--warn-unresolved-symbols} | |
1742 | can change this to a warning. | |
1743 | ||
252b5132 RH |
1744 | @kindex --verbose |
1745 | @cindex verbose | |
1746 | @item --dll-verbose | |
308b1ffd | 1747 | @itemx --verbose |
ff5dcc92 | 1748 | Display the version number for @command{ld} and list the linker emulations |
252b5132 | 1749 | supported. Display which input files can and cannot be opened. Display |
b9a8de1e | 1750 | the linker script being used by the linker. |
252b5132 RH |
1751 | |
1752 | @kindex --version-script=@var{version-scriptfile} | |
1753 | @cindex version script, symbol versions | |
1754 | @itemx --version-script=@var{version-scriptfile} | |
1755 | Specify the name of a version script to the linker. This is typically | |
1756 | used when creating shared libraries to specify additional information | |
36f63dca | 1757 | about the version hierarchy for the library being created. This option |
252b5132 RH |
1758 | is only meaningful on ELF platforms which support shared libraries. |
1759 | @xref{VERSION}. | |
1760 | ||
7ce691ae | 1761 | @kindex --warn-common |
252b5132 RH |
1762 | @cindex warnings, on combining symbols |
1763 | @cindex combining symbols, warnings on | |
1764 | @item --warn-common | |
1765 | Warn when a common symbol is combined with another common symbol or with | |
560e09e9 | 1766 | a symbol definition. Unix linkers allow this somewhat sloppy practise, |
252b5132 RH |
1767 | but linkers on some other operating systems do not. This option allows |
1768 | you to find potential problems from combining global symbols. | |
560e09e9 | 1769 | Unfortunately, some C libraries use this practise, so you may get some |
252b5132 RH |
1770 | warnings about symbols in the libraries as well as in your programs. |
1771 | ||
1772 | There are three kinds of global symbols, illustrated here by C examples: | |
1773 | ||
1774 | @table @samp | |
1775 | @item int i = 1; | |
1776 | A definition, which goes in the initialized data section of the output | |
1777 | file. | |
1778 | ||
1779 | @item extern int i; | |
1780 | An undefined reference, which does not allocate space. | |
1781 | There must be either a definition or a common symbol for the | |
1782 | variable somewhere. | |
1783 | ||
1784 | @item int i; | |
1785 | A common symbol. If there are only (one or more) common symbols for a | |
1786 | variable, it goes in the uninitialized data area of the output file. | |
1787 | The linker merges multiple common symbols for the same variable into a | |
1788 | single symbol. If they are of different sizes, it picks the largest | |
1789 | size. The linker turns a common symbol into a declaration, if there is | |
1790 | a definition of the same variable. | |
1791 | @end table | |
1792 | ||
1793 | The @samp{--warn-common} option can produce five kinds of warnings. | |
1794 | Each warning consists of a pair of lines: the first describes the symbol | |
1795 | just encountered, and the second describes the previous symbol | |
1796 | encountered with the same name. One or both of the two symbols will be | |
1797 | a common symbol. | |
1798 | ||
1799 | @enumerate | |
1800 | @item | |
1801 | Turning a common symbol into a reference, because there is already a | |
1802 | definition for the symbol. | |
1803 | @smallexample | |
1804 | @var{file}(@var{section}): warning: common of `@var{symbol}' | |
1805 | overridden by definition | |
1806 | @var{file}(@var{section}): warning: defined here | |
1807 | @end smallexample | |
1808 | ||
1809 | @item | |
1810 | Turning a common symbol into a reference, because a later definition for | |
1811 | the symbol is encountered. This is the same as the previous case, | |
1812 | except that the symbols are encountered in a different order. | |
1813 | @smallexample | |
1814 | @var{file}(@var{section}): warning: definition of `@var{symbol}' | |
1815 | overriding common | |
1816 | @var{file}(@var{section}): warning: common is here | |
1817 | @end smallexample | |
1818 | ||
1819 | @item | |
1820 | Merging a common symbol with a previous same-sized common symbol. | |
1821 | @smallexample | |
1822 | @var{file}(@var{section}): warning: multiple common | |
1823 | of `@var{symbol}' | |
1824 | @var{file}(@var{section}): warning: previous common is here | |
1825 | @end smallexample | |
1826 | ||
1827 | @item | |
1828 | Merging a common symbol with a previous larger common symbol. | |
1829 | @smallexample | |
1830 | @var{file}(@var{section}): warning: common of `@var{symbol}' | |
1831 | overridden by larger common | |
1832 | @var{file}(@var{section}): warning: larger common is here | |
1833 | @end smallexample | |
1834 | ||
1835 | @item | |
1836 | Merging a common symbol with a previous smaller common symbol. This is | |
1837 | the same as the previous case, except that the symbols are | |
1838 | encountered in a different order. | |
1839 | @smallexample | |
1840 | @var{file}(@var{section}): warning: common of `@var{symbol}' | |
1841 | overriding smaller common | |
1842 | @var{file}(@var{section}): warning: smaller common is here | |
1843 | @end smallexample | |
1844 | @end enumerate | |
1845 | ||
1846 | @kindex --warn-constructors | |
1847 | @item --warn-constructors | |
1848 | Warn if any global constructors are used. This is only useful for a few | |
1849 | object file formats. For formats like COFF or ELF, the linker can not | |
1850 | detect the use of global constructors. | |
1851 | ||
1852 | @kindex --warn-multiple-gp | |
1853 | @item --warn-multiple-gp | |
1854 | Warn if multiple global pointer values are required in the output file. | |
1855 | This is only meaningful for certain processors, such as the Alpha. | |
1856 | Specifically, some processors put large-valued constants in a special | |
1857 | section. A special register (the global pointer) points into the middle | |
1858 | of this section, so that constants can be loaded efficiently via a | |
1859 | base-register relative addressing mode. Since the offset in | |
1860 | base-register relative mode is fixed and relatively small (e.g., 16 | |
1861 | bits), this limits the maximum size of the constant pool. Thus, in | |
1862 | large programs, it is often necessary to use multiple global pointer | |
1863 | values in order to be able to address all possible constants. This | |
1864 | option causes a warning to be issued whenever this case occurs. | |
1865 | ||
1866 | @kindex --warn-once | |
1867 | @cindex warnings, on undefined symbols | |
1868 | @cindex undefined symbols, warnings on | |
1869 | @item --warn-once | |
1870 | Only warn once for each undefined symbol, rather than once per module | |
1871 | which refers to it. | |
1872 | ||
1873 | @kindex --warn-section-align | |
1874 | @cindex warnings, on section alignment | |
1875 | @cindex section alignment, warnings on | |
1876 | @item --warn-section-align | |
1877 | Warn if the address of an output section is changed because of | |
1878 | alignment. Typically, the alignment will be set by an input section. | |
1879 | The address will only be changed if it not explicitly specified; that | |
1880 | is, if the @code{SECTIONS} command does not specify a start address for | |
1881 | the section (@pxref{SECTIONS}). | |
1882 | ||
8fdd7217 NC |
1883 | @kindex --warn-shared-textrel |
1884 | @item --warn-shared-textrel | |
ece2d90e | 1885 | Warn if the linker adds a DT_TEXTREL to a shared object. |
8fdd7217 | 1886 | |
560e09e9 NC |
1887 | @kindex --warn-unresolved-symbols |
1888 | @item --warn-unresolved-symbols | |
1889 | If the linker is going to report an unresolved symbol (see the option | |
1890 | @option{--unresolved-symbols}) it will normally generate an error. | |
1891 | This option makes it generate a warning instead. | |
1892 | ||
1893 | @kindex --error-unresolved-symbols | |
1894 | @item --error-unresolved-symbols | |
1895 | This restores the linker's default behaviour of generating errors when | |
1896 | it is reporting unresolved symbols. | |
1897 | ||
252b5132 RH |
1898 | @kindex --whole-archive |
1899 | @cindex including an entire archive | |
1900 | @item --whole-archive | |
1901 | For each archive mentioned on the command line after the | |
ff5dcc92 | 1902 | @option{--whole-archive} option, include every object file in the archive |
252b5132 RH |
1903 | in the link, rather than searching the archive for the required object |
1904 | files. This is normally used to turn an archive file into a shared | |
1905 | library, forcing every object to be included in the resulting shared | |
1906 | library. This option may be used more than once. | |
1907 | ||
7ec229ce | 1908 | Two notes when using this option from gcc: First, gcc doesn't know |
ff5dcc92 SC |
1909 | about this option, so you have to use @option{-Wl,-whole-archive}. |
1910 | Second, don't forget to use @option{-Wl,-no-whole-archive} after your | |
7ec229ce DD |
1911 | list of archives, because gcc will add its own list of archives to |
1912 | your link and you may not want this flag to affect those as well. | |
1913 | ||
252b5132 RH |
1914 | @kindex --wrap |
1915 | @item --wrap @var{symbol} | |
1916 | Use a wrapper function for @var{symbol}. Any undefined reference to | |
1917 | @var{symbol} will be resolved to @code{__wrap_@var{symbol}}. Any | |
1918 | undefined reference to @code{__real_@var{symbol}} will be resolved to | |
1919 | @var{symbol}. | |
1920 | ||
1921 | This can be used to provide a wrapper for a system function. The | |
1922 | wrapper function should be called @code{__wrap_@var{symbol}}. If it | |
1923 | wishes to call the system function, it should call | |
1924 | @code{__real_@var{symbol}}. | |
1925 | ||
1926 | Here is a trivial example: | |
1927 | ||
1928 | @smallexample | |
1929 | void * | |
cc2f008e | 1930 | __wrap_malloc (size_t c) |
252b5132 | 1931 | @{ |
cc2f008e | 1932 | printf ("malloc called with %zu\n", c); |
252b5132 RH |
1933 | return __real_malloc (c); |
1934 | @} | |
1935 | @end smallexample | |
1936 | ||
ff5dcc92 | 1937 | If you link other code with this file using @option{--wrap malloc}, then |
252b5132 RH |
1938 | all calls to @code{malloc} will call the function @code{__wrap_malloc} |
1939 | instead. The call to @code{__real_malloc} in @code{__wrap_malloc} will | |
1940 | call the real @code{malloc} function. | |
1941 | ||
1942 | You may wish to provide a @code{__real_malloc} function as well, so that | |
ff5dcc92 | 1943 | links without the @option{--wrap} option will succeed. If you do this, |
252b5132 RH |
1944 | you should not put the definition of @code{__real_malloc} in the same |
1945 | file as @code{__wrap_malloc}; if you do, the assembler may resolve the | |
1946 | call before the linker has a chance to wrap it to @code{malloc}. | |
1947 | ||
6aa29e7b JJ |
1948 | @kindex --eh-frame-hdr |
1949 | @item --eh-frame-hdr | |
1950 | Request creation of @code{.eh_frame_hdr} section and ELF | |
1951 | @code{PT_GNU_EH_FRAME} segment header. | |
1952 | ||
6c1439be L |
1953 | @kindex --enable-new-dtags |
1954 | @kindex --disable-new-dtags | |
1955 | @item --enable-new-dtags | |
1956 | @itemx --disable-new-dtags | |
1957 | This linker can create the new dynamic tags in ELF. But the older ELF | |
1958 | systems may not understand them. If you specify | |
ff5dcc92 SC |
1959 | @option{--enable-new-dtags}, the dynamic tags will be created as needed. |
1960 | If you specify @option{--disable-new-dtags}, no new dynamic tags will be | |
6c1439be L |
1961 | created. By default, the new dynamic tags are not created. Note that |
1962 | those options are only available for ELF systems. | |
1963 | ||
2d643429 | 1964 | @kindex --hash-size=@var{number} |
e185dd51 | 1965 | @item --hash-size=@var{number} |
2d643429 NC |
1966 | Set the default size of the linker's hash tables to a prime number |
1967 | close to @var{number}. Increasing this value can reduce the length of | |
1968 | time it takes the linker to perform its tasks, at the expense of | |
1969 | increasing the linker's memory requirements. Similarly reducing this | |
1970 | value can reduce the memory requirements at the expense of speed. | |
1971 | ||
fdc90cb4 JJ |
1972 | @kindex --hash-style=@var{style} |
1973 | @item --hash-style=@var{style} | |
1974 | Set the type of linker's hash table(s). @var{style} can be either | |
1975 | @code{sysv} for classic ELF @code{.hash} section, @code{gnu} for | |
1976 | new style GNU @code{.gnu.hash} section or @code{both} for both | |
1977 | the classic ELF @code{.hash} and new style GNU @code{.gnu.hash} | |
1978 | hash tables. The default is @code{sysv}. | |
1979 | ||
35835446 JR |
1980 | @kindex --reduce-memory-overheads |
1981 | @item --reduce-memory-overheads | |
1982 | This option reduces memory requirements at ld runtime, at the expense of | |
f2a8f148 | 1983 | linking speed. This was introduced to select the old O(n^2) algorithm |
35835446 | 1984 | for link map file generation, rather than the new O(n) algorithm which uses |
2d643429 NC |
1985 | about 40% more memory for symbol storage. |
1986 | ||
4f9c04f7 | 1987 | Another effect of the switch is to set the default hash table size to |
2d643429 | 1988 | 1021, which again saves memory at the cost of lengthening the linker's |
a85785bc | 1989 | run time. This is not done however if the @option{--hash-size} switch |
2d643429 NC |
1990 | has been used. |
1991 | ||
1992 | The @option{--reduce-memory-overheads} switch may be also be used to | |
1993 | enable other tradeoffs in future versions of the linker. | |
35835446 | 1994 | |
c0065db7 RM |
1995 | @kindex --build-id |
1996 | @kindex --build-id=@var{style} | |
1997 | @item --build-id | |
1998 | @itemx --build-id=@var{style} | |
1999 | Request creation of @code{.note.gnu.build-id} ELF note section. | |
2000 | The contents of the note are unique bits identifying this linked | |
2001 | file. @var{style} can be @code{uuid} to use 128 random bits, | |
24382dca RM |
2002 | @code{sha1} to use a 160-bit @sc{SHA1} hash on the normative |
2003 | parts of the output contents, @code{md5} to use a 128-bit | |
2004 | @sc{MD5} hash on the normative parts of the output contents, or | |
2005 | @code{0x@var{hexstring}} to use a chosen bit string specified as | |
2006 | an even number of hexadecimal digits (@code{-} and @code{:} | |
2007 | characters between digit pairs are ignored). If @var{style} is | |
2008 | omitted, @code{sha1} is used. | |
2009 | ||
2010 | The @code{md5} and @code{sha1} styles produces an identifier | |
2011 | that is always the same in an identical output file, but will be | |
2012 | unique among all nonidentical output files. It is not intended | |
2013 | to be compared as a checksum for the file's contents. A linked | |
2014 | file may be changed later by other tools, but the build ID bit | |
2015 | string identifying the original linked file does not change. | |
c0065db7 RM |
2016 | |
2017 | Passing @code{none} for @var{style} disables the setting from any | |
2018 | @code{--build-id} options earlier on the command line. | |
252b5132 RH |
2019 | @end table |
2020 | ||
0285c67d NC |
2021 | @c man end |
2022 | ||
36f63dca | 2023 | @subsection Options Specific to i386 PE Targets |
252b5132 | 2024 | |
0285c67d NC |
2025 | @c man begin OPTIONS |
2026 | ||
ff5dcc92 | 2027 | The i386 PE linker supports the @option{-shared} option, which causes |
252b5132 RH |
2028 | the output to be a dynamically linked library (DLL) instead of a |
2029 | normal executable. You should name the output @code{*.dll} when you | |
2030 | use this option. In addition, the linker fully supports the standard | |
2031 | @code{*.def} files, which may be specified on the linker command line | |
2032 | like an object file (in fact, it should precede archives it exports | |
2033 | symbols from, to ensure that they get linked in, just like a normal | |
2034 | object file). | |
2035 | ||
2036 | In addition to the options common to all targets, the i386 PE linker | |
2037 | support additional command line options that are specific to the i386 | |
2038 | PE target. Options that take values may be separated from their | |
2039 | values by either a space or an equals sign. | |
2040 | ||
ff5dcc92 | 2041 | @table @gcctabopt |
252b5132 RH |
2042 | |
2043 | @kindex --add-stdcall-alias | |
2044 | @item --add-stdcall-alias | |
2045 | If given, symbols with a stdcall suffix (@@@var{nn}) will be exported | |
2046 | as-is and also with the suffix stripped. | |
bb10df36 | 2047 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 RH |
2048 | |
2049 | @kindex --base-file | |
2050 | @item --base-file @var{file} | |
2051 | Use @var{file} as the name of a file in which to save the base | |
2052 | addresses of all the relocations needed for generating DLLs with | |
2053 | @file{dlltool}. | |
bb10df36 | 2054 | [This is an i386 PE specific option] |
252b5132 RH |
2055 | |
2056 | @kindex --dll | |
2057 | @item --dll | |
2058 | Create a DLL instead of a regular executable. You may also use | |
ff5dcc92 | 2059 | @option{-shared} or specify a @code{LIBRARY} in a given @code{.def} |
252b5132 | 2060 | file. |
bb10df36 | 2061 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 RH |
2062 | |
2063 | @kindex --enable-stdcall-fixup | |
2064 | @kindex --disable-stdcall-fixup | |
2065 | @item --enable-stdcall-fixup | |
2066 | @itemx --disable-stdcall-fixup | |
2067 | If the link finds a symbol that it cannot resolve, it will attempt to | |
36f63dca | 2068 | do ``fuzzy linking'' by looking for another defined symbol that differs |
252b5132 RH |
2069 | only in the format of the symbol name (cdecl vs stdcall) and will |
2070 | resolve that symbol by linking to the match. For example, the | |
2071 | undefined symbol @code{_foo} might be linked to the function | |
2072 | @code{_foo@@12}, or the undefined symbol @code{_bar@@16} might be linked | |
2073 | to the function @code{_bar}. When the linker does this, it prints a | |
2074 | warning, since it normally should have failed to link, but sometimes | |
2075 | import libraries generated from third-party dlls may need this feature | |
ff5dcc92 | 2076 | to be usable. If you specify @option{--enable-stdcall-fixup}, this |
252b5132 | 2077 | feature is fully enabled and warnings are not printed. If you specify |
ff5dcc92 | 2078 | @option{--disable-stdcall-fixup}, this feature is disabled and such |
252b5132 | 2079 | mismatches are considered to be errors. |
bb10df36 | 2080 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 RH |
2081 | |
2082 | @cindex DLLs, creating | |
2083 | @kindex --export-all-symbols | |
2084 | @item --export-all-symbols | |
2085 | If given, all global symbols in the objects used to build a DLL will | |
2086 | be exported by the DLL. Note that this is the default if there | |
2087 | otherwise wouldn't be any exported symbols. When symbols are | |
2088 | explicitly exported via DEF files or implicitly exported via function | |
2089 | attributes, the default is to not export anything else unless this | |
2090 | option is given. Note that the symbols @code{DllMain@@12}, | |
ece2d90e | 2091 | @code{DllEntryPoint@@0}, @code{DllMainCRTStartup@@12}, and |
b044cda1 | 2092 | @code{impure_ptr} will not be automatically |
ece2d90e NC |
2093 | exported. Also, symbols imported from other DLLs will not be |
2094 | re-exported, nor will symbols specifying the DLL's internal layout | |
2095 | such as those beginning with @code{_head_} or ending with | |
2096 | @code{_iname}. In addition, no symbols from @code{libgcc}, | |
b044cda1 CW |
2097 | @code{libstd++}, @code{libmingw32}, or @code{crtX.o} will be exported. |
2098 | Symbols whose names begin with @code{__rtti_} or @code{__builtin_} will | |
2099 | not be exported, to help with C++ DLLs. Finally, there is an | |
ece2d90e | 2100 | extensive list of cygwin-private symbols that are not exported |
b044cda1 | 2101 | (obviously, this applies on when building DLLs for cygwin targets). |
ece2d90e | 2102 | These cygwin-excludes are: @code{_cygwin_dll_entry@@12}, |
b044cda1 | 2103 | @code{_cygwin_crt0_common@@8}, @code{_cygwin_noncygwin_dll_entry@@12}, |
ece2d90e | 2104 | @code{_fmode}, @code{_impure_ptr}, @code{cygwin_attach_dll}, |
b044cda1 | 2105 | @code{cygwin_premain0}, @code{cygwin_premain1}, @code{cygwin_premain2}, |
ece2d90e | 2106 | @code{cygwin_premain3}, and @code{environ}. |
bb10df36 | 2107 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 RH |
2108 | |
2109 | @kindex --exclude-symbols | |
1d0a3c9c | 2110 | @item --exclude-symbols @var{symbol},@var{symbol},... |
252b5132 RH |
2111 | Specifies a list of symbols which should not be automatically |
2112 | exported. The symbol names may be delimited by commas or colons. | |
bb10df36 | 2113 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 RH |
2114 | |
2115 | @kindex --file-alignment | |
2116 | @item --file-alignment | |
2117 | Specify the file alignment. Sections in the file will always begin at | |
2118 | file offsets which are multiples of this number. This defaults to | |
2119 | 512. | |
bb10df36 | 2120 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 RH |
2121 | |
2122 | @cindex heap size | |
2123 | @kindex --heap | |
2124 | @item --heap @var{reserve} | |
2125 | @itemx --heap @var{reserve},@var{commit} | |
a00b50c5 DS |
2126 | Specify the number of bytes of memory to reserve (and optionally commit) |
2127 | to be used as heap for this program. The default is 1Mb reserved, 4K | |
252b5132 | 2128 | committed. |
bb10df36 | 2129 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 RH |
2130 | |
2131 | @cindex image base | |
2132 | @kindex --image-base | |
2133 | @item --image-base @var{value} | |
2134 | Use @var{value} as the base address of your program or dll. This is | |
2135 | the lowest memory location that will be used when your program or dll | |
2136 | is loaded. To reduce the need to relocate and improve performance of | |
2137 | your dlls, each should have a unique base address and not overlap any | |
2138 | other dlls. The default is 0x400000 for executables, and 0x10000000 | |
2139 | for dlls. | |
bb10df36 | 2140 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 RH |
2141 | |
2142 | @kindex --kill-at | |
2143 | @item --kill-at | |
2144 | If given, the stdcall suffixes (@@@var{nn}) will be stripped from | |
2145 | symbols before they are exported. | |
bb10df36 | 2146 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 | 2147 | |
26d2d8a2 BF |
2148 | @kindex --large-address-aware |
2149 | @item --large-address-aware | |
b45619c0 | 2150 | If given, the appropriate bit in the ``Characteristics'' field of the COFF |
26d2d8a2 | 2151 | header is set to indicate that this executable supports virtual addresses |
b45619c0 | 2152 | greater than 2 gigabytes. This should be used in conjunction with the /3GB |
26d2d8a2 BF |
2153 | or /USERVA=@var{value} megabytes switch in the ``[operating systems]'' |
2154 | section of the BOOT.INI. Otherwise, this bit has no effect. | |
2155 | [This option is specific to PE targeted ports of the linker] | |
2156 | ||
252b5132 RH |
2157 | @kindex --major-image-version |
2158 | @item --major-image-version @var{value} | |
36f63dca | 2159 | Sets the major number of the ``image version''. Defaults to 1. |
bb10df36 | 2160 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 RH |
2161 | |
2162 | @kindex --major-os-version | |
2163 | @item --major-os-version @var{value} | |
36f63dca | 2164 | Sets the major number of the ``os version''. Defaults to 4. |
bb10df36 | 2165 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 RH |
2166 | |
2167 | @kindex --major-subsystem-version | |
2168 | @item --major-subsystem-version @var{value} | |
36f63dca | 2169 | Sets the major number of the ``subsystem version''. Defaults to 4. |
bb10df36 | 2170 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 RH |
2171 | |
2172 | @kindex --minor-image-version | |
2173 | @item --minor-image-version @var{value} | |
36f63dca | 2174 | Sets the minor number of the ``image version''. Defaults to 0. |
bb10df36 | 2175 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 RH |
2176 | |
2177 | @kindex --minor-os-version | |
2178 | @item --minor-os-version @var{value} | |
36f63dca | 2179 | Sets the minor number of the ``os version''. Defaults to 0. |
bb10df36 | 2180 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 RH |
2181 | |
2182 | @kindex --minor-subsystem-version | |
2183 | @item --minor-subsystem-version @var{value} | |
36f63dca | 2184 | Sets the minor number of the ``subsystem version''. Defaults to 0. |
bb10df36 | 2185 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 RH |
2186 | |
2187 | @cindex DEF files, creating | |
2188 | @cindex DLLs, creating | |
2189 | @kindex --output-def | |
2190 | @item --output-def @var{file} | |
2191 | The linker will create the file @var{file} which will contain a DEF | |
2192 | file corresponding to the DLL the linker is generating. This DEF file | |
2193 | (which should be called @code{*.def}) may be used to create an import | |
2194 | library with @code{dlltool} or may be used as a reference to | |
2195 | automatically or implicitly exported symbols. | |
bb10df36 | 2196 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 | 2197 | |
b044cda1 CW |
2198 | @cindex DLLs, creating |
2199 | @kindex --out-implib | |
2200 | @item --out-implib @var{file} | |
2201 | The linker will create the file @var{file} which will contain an | |
2202 | import lib corresponding to the DLL the linker is generating. This | |
2203 | import lib (which should be called @code{*.dll.a} or @code{*.a} | |
560e09e9 | 2204 | may be used to link clients against the generated DLL; this behaviour |
b044cda1 CW |
2205 | makes it possible to skip a separate @code{dlltool} import library |
2206 | creation step. | |
bb10df36 | 2207 | [This option is specific to the i386 PE targeted port of the linker] |
b044cda1 CW |
2208 | |
2209 | @kindex --enable-auto-image-base | |
2210 | @item --enable-auto-image-base | |
2211 | Automatically choose the image base for DLLs, unless one is specified | |
2212 | using the @code{--image-base} argument. By using a hash generated | |
2213 | from the dllname to create unique image bases for each DLL, in-memory | |
2214 | collisions and relocations which can delay program execution are | |
2215 | avoided. | |
bb10df36 | 2216 | [This option is specific to the i386 PE targeted port of the linker] |
b044cda1 CW |
2217 | |
2218 | @kindex --disable-auto-image-base | |
2219 | @item --disable-auto-image-base | |
2220 | Do not automatically generate a unique image base. If there is no | |
2221 | user-specified image base (@code{--image-base}) then use the platform | |
2222 | default. | |
bb10df36 | 2223 | [This option is specific to the i386 PE targeted port of the linker] |
b044cda1 CW |
2224 | |
2225 | @cindex DLLs, linking to | |
2226 | @kindex --dll-search-prefix | |
2227 | @item --dll-search-prefix @var{string} | |
489d0400 | 2228 | When linking dynamically to a dll without an import library, |
ece2d90e | 2229 | search for @code{<string><basename>.dll} in preference to |
560e09e9 | 2230 | @code{lib<basename>.dll}. This behaviour allows easy distinction |
b044cda1 CW |
2231 | between DLLs built for the various "subplatforms": native, cygwin, |
2232 | uwin, pw, etc. For instance, cygwin DLLs typically use | |
ece2d90e | 2233 | @code{--dll-search-prefix=cyg}. |
bb10df36 | 2234 | [This option is specific to the i386 PE targeted port of the linker] |
b044cda1 CW |
2235 | |
2236 | @kindex --enable-auto-import | |
2237 | @item --enable-auto-import | |
ece2d90e NC |
2238 | Do sophisticated linking of @code{_symbol} to @code{__imp__symbol} for |
2239 | DATA imports from DLLs, and create the necessary thunking symbols when | |
4d8907ac DS |
2240 | building the import libraries with those DATA exports. Note: Use of the |
2241 | 'auto-import' extension will cause the text section of the image file | |
2242 | to be made writable. This does not conform to the PE-COFF format | |
2243 | specification published by Microsoft. | |
2244 | ||
e2a83dd0 NC |
2245 | Note - use of the 'auto-import' extension will also cause read only |
2246 | data which would normally be placed into the .rdata section to be | |
2247 | placed into the .data section instead. This is in order to work | |
2248 | around a problem with consts that is described here: | |
2249 | http://www.cygwin.com/ml/cygwin/2004-09/msg01101.html | |
2250 | ||
4d8907ac DS |
2251 | Using 'auto-import' generally will 'just work' -- but sometimes you may |
2252 | see this message: | |
0d888aac | 2253 | |
ece2d90e | 2254 | "variable '<var>' can't be auto-imported. Please read the |
0d888aac CW |
2255 | documentation for ld's @code{--enable-auto-import} for details." |
2256 | ||
ece2d90e NC |
2257 | This message occurs when some (sub)expression accesses an address |
2258 | ultimately given by the sum of two constants (Win32 import tables only | |
c0065db7 RM |
2259 | allow one). Instances where this may occur include accesses to member |
2260 | fields of struct variables imported from a DLL, as well as using a | |
2261 | constant index into an array variable imported from a DLL. Any | |
2f8d8971 NC |
2262 | multiword variable (arrays, structs, long long, etc) may trigger |
2263 | this error condition. However, regardless of the exact data type | |
2264 | of the offending exported variable, ld will always detect it, issue | |
2265 | the warning, and exit. | |
2266 | ||
2267 | There are several ways to address this difficulty, regardless of the | |
2268 | data type of the exported variable: | |
0d888aac | 2269 | |
2fa9fc65 NC |
2270 | One way is to use --enable-runtime-pseudo-reloc switch. This leaves the task |
2271 | of adjusting references in your client code for runtime environment, so | |
560e09e9 | 2272 | this method works only when runtime environment supports this feature. |
2fa9fc65 | 2273 | |
c0065db7 RM |
2274 | A second solution is to force one of the 'constants' to be a variable -- |
2275 | that is, unknown and un-optimizable at compile time. For arrays, | |
2276 | there are two possibilities: a) make the indexee (the array's address) | |
0d888aac CW |
2277 | a variable, or b) make the 'constant' index a variable. Thus: |
2278 | ||
2279 | @example | |
2280 | extern type extern_array[]; | |
c0065db7 | 2281 | extern_array[1] --> |
0d888aac CW |
2282 | @{ volatile type *t=extern_array; t[1] @} |
2283 | @end example | |
2284 | ||
2285 | or | |
2286 | ||
2287 | @example | |
2288 | extern type extern_array[]; | |
c0065db7 | 2289 | extern_array[1] --> |
0d888aac CW |
2290 | @{ volatile int t=1; extern_array[t] @} |
2291 | @end example | |
2292 | ||
c0065db7 | 2293 | For structs (and most other multiword data types) the only option |
2f8d8971 | 2294 | is to make the struct itself (or the long long, or the ...) variable: |
0d888aac CW |
2295 | |
2296 | @example | |
2297 | extern struct s extern_struct; | |
c0065db7 | 2298 | extern_struct.field --> |
0d888aac CW |
2299 | @{ volatile struct s *t=&extern_struct; t->field @} |
2300 | @end example | |
2301 | ||
c406afaf NC |
2302 | or |
2303 | ||
2304 | @example | |
2305 | extern long long extern_ll; | |
2306 | extern_ll --> | |
2307 | @{ volatile long long * local_ll=&extern_ll; *local_ll @} | |
2308 | @end example | |
2309 | ||
2fa9fc65 | 2310 | A third method of dealing with this difficulty is to abandon |
c0065db7 | 2311 | 'auto-import' for the offending symbol and mark it with |
560e09e9 | 2312 | @code{__declspec(dllimport)}. However, in practise that |
0d888aac | 2313 | requires using compile-time #defines to indicate whether you are |
c0065db7 RM |
2314 | building a DLL, building client code that will link to the DLL, or |
2315 | merely building/linking to a static library. In making the choice | |
2316 | between the various methods of resolving the 'direct address with | |
0d888aac CW |
2317 | constant offset' problem, you should consider typical real-world usage: |
2318 | ||
2319 | Original: | |
2320 | @example | |
2321 | --foo.h | |
2322 | extern int arr[]; | |
2323 | --foo.c | |
2324 | #include "foo.h" | |
2325 | void main(int argc, char **argv)@{ | |
2326 | printf("%d\n",arr[1]); | |
2327 | @} | |
2328 | @end example | |
2329 | ||
2330 | Solution 1: | |
2331 | @example | |
2332 | --foo.h | |
2333 | extern int arr[]; | |
2334 | --foo.c | |
2335 | #include "foo.h" | |
2336 | void main(int argc, char **argv)@{ | |
2337 | /* This workaround is for win32 and cygwin; do not "optimize" */ | |
2338 | volatile int *parr = arr; | |
2339 | printf("%d\n",parr[1]); | |
2340 | @} | |
2341 | @end example | |
2342 | ||
2343 | Solution 2: | |
2344 | @example | |
2345 | --foo.h | |
2346 | /* Note: auto-export is assumed (no __declspec(dllexport)) */ | |
2347 | #if (defined(_WIN32) || defined(__CYGWIN__)) && \ | |
2348 | !(defined(FOO_BUILD_DLL) || defined(FOO_STATIC)) | |
2349 | #define FOO_IMPORT __declspec(dllimport) | |
2350 | #else | |
2351 | #define FOO_IMPORT | |
2352 | #endif | |
2353 | extern FOO_IMPORT int arr[]; | |
2354 | --foo.c | |
2355 | #include "foo.h" | |
2356 | void main(int argc, char **argv)@{ | |
2357 | printf("%d\n",arr[1]); | |
2358 | @} | |
2359 | @end example | |
2360 | ||
c0065db7 | 2361 | A fourth way to avoid this problem is to re-code your |
0d888aac CW |
2362 | library to use a functional interface rather than a data interface |
2363 | for the offending variables (e.g. set_foo() and get_foo() accessor | |
2364 | functions). | |
bb10df36 | 2365 | [This option is specific to the i386 PE targeted port of the linker] |
b044cda1 CW |
2366 | |
2367 | @kindex --disable-auto-import | |
2368 | @item --disable-auto-import | |
c0065db7 | 2369 | Do not attempt to do sophisticated linking of @code{_symbol} to |
b044cda1 | 2370 | @code{__imp__symbol} for DATA imports from DLLs. |
bb10df36 | 2371 | [This option is specific to the i386 PE targeted port of the linker] |
b044cda1 | 2372 | |
2fa9fc65 NC |
2373 | @kindex --enable-runtime-pseudo-reloc |
2374 | @item --enable-runtime-pseudo-reloc | |
2375 | If your code contains expressions described in --enable-auto-import section, | |
2376 | that is, DATA imports from DLL with non-zero offset, this switch will create | |
2377 | a vector of 'runtime pseudo relocations' which can be used by runtime | |
c0065db7 | 2378 | environment to adjust references to such data in your client code. |
bb10df36 | 2379 | [This option is specific to the i386 PE targeted port of the linker] |
2fa9fc65 NC |
2380 | |
2381 | @kindex --disable-runtime-pseudo-reloc | |
2382 | @item --disable-runtime-pseudo-reloc | |
2383 | Do not create pseudo relocations for non-zero offset DATA imports from | |
2384 | DLLs. This is the default. | |
bb10df36 | 2385 | [This option is specific to the i386 PE targeted port of the linker] |
2fa9fc65 | 2386 | |
b044cda1 CW |
2387 | @kindex --enable-extra-pe-debug |
2388 | @item --enable-extra-pe-debug | |
2389 | Show additional debug info related to auto-import symbol thunking. | |
bb10df36 | 2390 | [This option is specific to the i386 PE targeted port of the linker] |
b044cda1 | 2391 | |
252b5132 RH |
2392 | @kindex --section-alignment |
2393 | @item --section-alignment | |
2394 | Sets the section alignment. Sections in memory will always begin at | |
2395 | addresses which are a multiple of this number. Defaults to 0x1000. | |
bb10df36 | 2396 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 RH |
2397 | |
2398 | @cindex stack size | |
2399 | @kindex --stack | |
2400 | @item --stack @var{reserve} | |
2401 | @itemx --stack @var{reserve},@var{commit} | |
a00b50c5 DS |
2402 | Specify the number of bytes of memory to reserve (and optionally commit) |
2403 | to be used as stack for this program. The default is 2Mb reserved, 4K | |
252b5132 | 2404 | committed. |
bb10df36 | 2405 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 RH |
2406 | |
2407 | @kindex --subsystem | |
2408 | @item --subsystem @var{which} | |
2409 | @itemx --subsystem @var{which}:@var{major} | |
2410 | @itemx --subsystem @var{which}:@var{major}.@var{minor} | |
2411 | Specifies the subsystem under which your program will execute. The | |
2412 | legal values for @var{which} are @code{native}, @code{windows}, | |
33f362e1 NC |
2413 | @code{console}, @code{posix}, and @code{xbox}. You may optionally set |
2414 | the subsystem version also. Numeric values are also accepted for | |
2415 | @var{which}. | |
bb10df36 | 2416 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 RH |
2417 | |
2418 | @end table | |
2419 | ||
0285c67d NC |
2420 | @c man end |
2421 | ||
93fd0973 SC |
2422 | @ifset M68HC11 |
2423 | @subsection Options specific to Motorola 68HC11 and 68HC12 targets | |
2424 | ||
2425 | @c man begin OPTIONS | |
2426 | ||
2427 | The 68HC11 and 68HC12 linkers support specific options to control the | |
2428 | memory bank switching mapping and trampoline code generation. | |
2429 | ||
2430 | @table @gcctabopt | |
2431 | ||
2432 | @kindex --no-trampoline | |
2433 | @item --no-trampoline | |
2434 | This option disables the generation of trampoline. By default a trampoline | |
2435 | is generated for each far function which is called using a @code{jsr} | |
2436 | instruction (this happens when a pointer to a far function is taken). | |
2437 | ||
2438 | @kindex --bank-window | |
2439 | @item --bank-window @var{name} | |
2440 | This option indicates to the linker the name of the memory region in | |
2441 | the @samp{MEMORY} specification that describes the memory bank window. | |
2442 | The definition of such region is then used by the linker to compute | |
2443 | paging and addresses within the memory window. | |
2444 | ||
2445 | @end table | |
2446 | ||
2447 | @c man end | |
2448 | @end ifset | |
2449 | ||
7fb9f789 NC |
2450 | @ifset M68K |
2451 | @subsection Options specific to Motorola 68K target | |
2452 | ||
2453 | @c man begin OPTIONS | |
2454 | ||
2455 | The following options are supported to control handling of GOT generation | |
2456 | when linking for 68K targets. | |
2457 | ||
2458 | @table @gcctabopt | |
2459 | ||
2460 | @kindex --got | |
2461 | @item --got=@var{type} | |
2462 | This option tells the linker which GOT generation scheme to use. | |
2463 | @var{type} should be one of @samp{single}, @samp{negative}, | |
2464 | @samp{multigot} or @samp{target}. For more information refer to the | |
2465 | Info entry for @file{ld}. | |
2466 | ||
2467 | @end table | |
2468 | ||
2469 | @c man end | |
2470 | @end ifset | |
2471 | ||
252b5132 RH |
2472 | @ifset UsesEnvVars |
2473 | @node Environment | |
2474 | @section Environment Variables | |
2475 | ||
0285c67d NC |
2476 | @c man begin ENVIRONMENT |
2477 | ||
560e09e9 | 2478 | You can change the behaviour of @command{ld} with the environment variables |
36f63dca NC |
2479 | @ifclear SingleFormat |
2480 | @code{GNUTARGET}, | |
2481 | @end ifclear | |
2482 | @code{LDEMULATION} and @code{COLLECT_NO_DEMANGLE}. | |
252b5132 | 2483 | |
36f63dca | 2484 | @ifclear SingleFormat |
252b5132 RH |
2485 | @kindex GNUTARGET |
2486 | @cindex default input format | |
2487 | @code{GNUTARGET} determines the input-file object format if you don't | |
2488 | use @samp{-b} (or its synonym @samp{--format}). Its value should be one | |
2489 | of the BFD names for an input format (@pxref{BFD}). If there is no | |
ff5dcc92 | 2490 | @code{GNUTARGET} in the environment, @command{ld} uses the natural format |
252b5132 RH |
2491 | of the target. If @code{GNUTARGET} is set to @code{default} then BFD |
2492 | attempts to discover the input format by examining binary input files; | |
2493 | this method often succeeds, but there are potential ambiguities, since | |
2494 | there is no method of ensuring that the magic number used to specify | |
2495 | object-file formats is unique. However, the configuration procedure for | |
2496 | BFD on each system places the conventional format for that system first | |
2497 | in the search-list, so ambiguities are resolved in favor of convention. | |
36f63dca | 2498 | @end ifclear |
252b5132 RH |
2499 | |
2500 | @kindex LDEMULATION | |
2501 | @cindex default emulation | |
2502 | @cindex emulation, default | |
2503 | @code{LDEMULATION} determines the default emulation if you don't use the | |
2504 | @samp{-m} option. The emulation can affect various aspects of linker | |
2505 | behaviour, particularly the default linker script. You can list the | |
2506 | available emulations with the @samp{--verbose} or @samp{-V} options. If | |
2507 | the @samp{-m} option is not used, and the @code{LDEMULATION} environment | |
2508 | variable is not defined, the default emulation depends upon how the | |
2509 | linker was configured. | |
252b5132 RH |
2510 | |
2511 | @kindex COLLECT_NO_DEMANGLE | |
2512 | @cindex demangling, default | |
2513 | Normally, the linker will default to demangling symbols. However, if | |
2514 | @code{COLLECT_NO_DEMANGLE} is set in the environment, then it will | |
2515 | default to not demangling symbols. This environment variable is used in | |
2516 | a similar fashion by the @code{gcc} linker wrapper program. The default | |
2517 | may be overridden by the @samp{--demangle} and @samp{--no-demangle} | |
2518 | options. | |
2519 | ||
0285c67d NC |
2520 | @c man end |
2521 | @end ifset | |
2522 | ||
252b5132 RH |
2523 | @node Scripts |
2524 | @chapter Linker Scripts | |
2525 | ||
2526 | @cindex scripts | |
2527 | @cindex linker scripts | |
2528 | @cindex command files | |
2529 | Every link is controlled by a @dfn{linker script}. This script is | |
2530 | written in the linker command language. | |
2531 | ||
2532 | The main purpose of the linker script is to describe how the sections in | |
2533 | the input files should be mapped into the output file, and to control | |
2534 | the memory layout of the output file. Most linker scripts do nothing | |
2535 | more than this. However, when necessary, the linker script can also | |
2536 | direct the linker to perform many other operations, using the commands | |
2537 | described below. | |
2538 | ||
2539 | The linker always uses a linker script. If you do not supply one | |
2540 | yourself, the linker will use a default script that is compiled into the | |
2541 | linker executable. You can use the @samp{--verbose} command line option | |
2542 | to display the default linker script. Certain command line options, | |
2543 | such as @samp{-r} or @samp{-N}, will affect the default linker script. | |
2544 | ||
2545 | You may supply your own linker script by using the @samp{-T} command | |
2546 | line option. When you do this, your linker script will replace the | |
2547 | default linker script. | |
2548 | ||
2549 | You may also use linker scripts implicitly by naming them as input files | |
2550 | to the linker, as though they were files to be linked. @xref{Implicit | |
2551 | Linker Scripts}. | |
2552 | ||
2553 | @menu | |
2554 | * Basic Script Concepts:: Basic Linker Script Concepts | |
2555 | * Script Format:: Linker Script Format | |
2556 | * Simple Example:: Simple Linker Script Example | |
2557 | * Simple Commands:: Simple Linker Script Commands | |
2558 | * Assignments:: Assigning Values to Symbols | |
2559 | * SECTIONS:: SECTIONS Command | |
2560 | * MEMORY:: MEMORY Command | |
2561 | * PHDRS:: PHDRS Command | |
2562 | * VERSION:: VERSION Command | |
2563 | * Expressions:: Expressions in Linker Scripts | |
2564 | * Implicit Linker Scripts:: Implicit Linker Scripts | |
2565 | @end menu | |
2566 | ||
2567 | @node Basic Script Concepts | |
2568 | @section Basic Linker Script Concepts | |
2569 | @cindex linker script concepts | |
2570 | We need to define some basic concepts and vocabulary in order to | |
2571 | describe the linker script language. | |
2572 | ||
2573 | The linker combines input files into a single output file. The output | |
2574 | file and each input file are in a special data format known as an | |
2575 | @dfn{object file format}. Each file is called an @dfn{object file}. | |
2576 | The output file is often called an @dfn{executable}, but for our | |
2577 | purposes we will also call it an object file. Each object file has, | |
2578 | among other things, a list of @dfn{sections}. We sometimes refer to a | |
2579 | section in an input file as an @dfn{input section}; similarly, a section | |
2580 | in the output file is an @dfn{output section}. | |
2581 | ||
2582 | Each section in an object file has a name and a size. Most sections | |
2583 | also have an associated block of data, known as the @dfn{section | |
2584 | contents}. A section may be marked as @dfn{loadable}, which mean that | |
2585 | the contents should be loaded into memory when the output file is run. | |
2586 | A section with no contents may be @dfn{allocatable}, which means that an | |
2587 | area in memory should be set aside, but nothing in particular should be | |
2588 | loaded there (in some cases this memory must be zeroed out). A section | |
2589 | which is neither loadable nor allocatable typically contains some sort | |
2590 | of debugging information. | |
2591 | ||
2592 | Every loadable or allocatable output section has two addresses. The | |
2593 | first is the @dfn{VMA}, or virtual memory address. This is the address | |
2594 | the section will have when the output file is run. The second is the | |
2595 | @dfn{LMA}, or load memory address. This is the address at which the | |
2596 | section will be loaded. In most cases the two addresses will be the | |
2597 | same. An example of when they might be different is when a data section | |
2598 | is loaded into ROM, and then copied into RAM when the program starts up | |
2599 | (this technique is often used to initialize global variables in a ROM | |
2600 | based system). In this case the ROM address would be the LMA, and the | |
2601 | RAM address would be the VMA. | |
2602 | ||
2603 | You can see the sections in an object file by using the @code{objdump} | |
2604 | program with the @samp{-h} option. | |
2605 | ||
2606 | Every object file also has a list of @dfn{symbols}, known as the | |
2607 | @dfn{symbol table}. A symbol may be defined or undefined. Each symbol | |
2608 | has a name, and each defined symbol has an address, among other | |
2609 | information. If you compile a C or C++ program into an object file, you | |
2610 | will get a defined symbol for every defined function and global or | |
2611 | static variable. Every undefined function or global variable which is | |
2612 | referenced in the input file will become an undefined symbol. | |
2613 | ||
2614 | You can see the symbols in an object file by using the @code{nm} | |
2615 | program, or by using the @code{objdump} program with the @samp{-t} | |
2616 | option. | |
2617 | ||
2618 | @node Script Format | |
2619 | @section Linker Script Format | |
2620 | @cindex linker script format | |
2621 | Linker scripts are text files. | |
2622 | ||
2623 | You write a linker script as a series of commands. Each command is | |
2624 | either a keyword, possibly followed by arguments, or an assignment to a | |
2625 | symbol. You may separate commands using semicolons. Whitespace is | |
2626 | generally ignored. | |
2627 | ||
2628 | Strings such as file or format names can normally be entered directly. | |
2629 | If the file name contains a character such as a comma which would | |
2630 | otherwise serve to separate file names, you may put the file name in | |
2631 | double quotes. There is no way to use a double quote character in a | |
2632 | file name. | |
2633 | ||
2634 | You may include comments in linker scripts just as in C, delimited by | |
2635 | @samp{/*} and @samp{*/}. As in C, comments are syntactically equivalent | |
2636 | to whitespace. | |
2637 | ||
2638 | @node Simple Example | |
2639 | @section Simple Linker Script Example | |
2640 | @cindex linker script example | |
2641 | @cindex example of linker script | |
2642 | Many linker scripts are fairly simple. | |
2643 | ||
2644 | The simplest possible linker script has just one command: | |
2645 | @samp{SECTIONS}. You use the @samp{SECTIONS} command to describe the | |
2646 | memory layout of the output file. | |
2647 | ||
2648 | The @samp{SECTIONS} command is a powerful command. Here we will | |
2649 | describe a simple use of it. Let's assume your program consists only of | |
2650 | code, initialized data, and uninitialized data. These will be in the | |
2651 | @samp{.text}, @samp{.data}, and @samp{.bss} sections, respectively. | |
2652 | Let's assume further that these are the only sections which appear in | |
2653 | your input files. | |
2654 | ||
2655 | For this example, let's say that the code should be loaded at address | |
2656 | 0x10000, and that the data should start at address 0x8000000. Here is a | |
2657 | linker script which will do that: | |
2658 | @smallexample | |
2659 | SECTIONS | |
2660 | @{ | |
2661 | . = 0x10000; | |
2662 | .text : @{ *(.text) @} | |
2663 | . = 0x8000000; | |
2664 | .data : @{ *(.data) @} | |
2665 | .bss : @{ *(.bss) @} | |
2666 | @} | |
2667 | @end smallexample | |
2668 | ||
2669 | You write the @samp{SECTIONS} command as the keyword @samp{SECTIONS}, | |
2670 | followed by a series of symbol assignments and output section | |
2671 | descriptions enclosed in curly braces. | |
2672 | ||
252b5132 RH |
2673 | The first line inside the @samp{SECTIONS} command of the above example |
2674 | sets the value of the special symbol @samp{.}, which is the location | |
2675 | counter. If you do not specify the address of an output section in some | |
2676 | other way (other ways are described later), the address is set from the | |
2677 | current value of the location counter. The location counter is then | |
2678 | incremented by the size of the output section. At the start of the | |
2679 | @samp{SECTIONS} command, the location counter has the value @samp{0}. | |
2680 | ||
2681 | The second line defines an output section, @samp{.text}. The colon is | |
2682 | required syntax which may be ignored for now. Within the curly braces | |
2683 | after the output section name, you list the names of the input sections | |
2684 | which should be placed into this output section. The @samp{*} is a | |
2685 | wildcard which matches any file name. The expression @samp{*(.text)} | |
2686 | means all @samp{.text} input sections in all input files. | |
2687 | ||
2688 | Since the location counter is @samp{0x10000} when the output section | |
2689 | @samp{.text} is defined, the linker will set the address of the | |
2690 | @samp{.text} section in the output file to be @samp{0x10000}. | |
2691 | ||
2692 | The remaining lines define the @samp{.data} and @samp{.bss} sections in | |
2693 | the output file. The linker will place the @samp{.data} output section | |
2694 | at address @samp{0x8000000}. After the linker places the @samp{.data} | |
2695 | output section, the value of the location counter will be | |
2696 | @samp{0x8000000} plus the size of the @samp{.data} output section. The | |
2697 | effect is that the linker will place the @samp{.bss} output section | |
58434bc1 | 2698 | immediately after the @samp{.data} output section in memory. |
252b5132 RH |
2699 | |
2700 | The linker will ensure that each output section has the required | |
2701 | alignment, by increasing the location counter if necessary. In this | |
2702 | example, the specified addresses for the @samp{.text} and @samp{.data} | |
2703 | sections will probably satisfy any alignment constraints, but the linker | |
2704 | may have to create a small gap between the @samp{.data} and @samp{.bss} | |
2705 | sections. | |
2706 | ||
2707 | That's it! That's a simple and complete linker script. | |
2708 | ||
2709 | @node Simple Commands | |
2710 | @section Simple Linker Script Commands | |
2711 | @cindex linker script simple commands | |
2712 | In this section we describe the simple linker script commands. | |
2713 | ||
2714 | @menu | |
2715 | * Entry Point:: Setting the entry point | |
2716 | * File Commands:: Commands dealing with files | |
2717 | @ifclear SingleFormat | |
2718 | * Format Commands:: Commands dealing with object file formats | |
2719 | @end ifclear | |
2720 | ||
2721 | * Miscellaneous Commands:: Other linker script commands | |
2722 | @end menu | |
2723 | ||
2724 | @node Entry Point | |
36f63dca | 2725 | @subsection Setting the Entry Point |
252b5132 RH |
2726 | @kindex ENTRY(@var{symbol}) |
2727 | @cindex start of execution | |
2728 | @cindex first instruction | |
2729 | @cindex entry point | |
2730 | The first instruction to execute in a program is called the @dfn{entry | |
2731 | point}. You can use the @code{ENTRY} linker script command to set the | |
2732 | entry point. The argument is a symbol name: | |
2733 | @smallexample | |
2734 | ENTRY(@var{symbol}) | |
2735 | @end smallexample | |
2736 | ||
2737 | There are several ways to set the entry point. The linker will set the | |
2738 | entry point by trying each of the following methods in order, and | |
2739 | stopping when one of them succeeds: | |
2740 | @itemize @bullet | |
a1ab1d2a | 2741 | @item |
252b5132 | 2742 | the @samp{-e} @var{entry} command-line option; |
a1ab1d2a | 2743 | @item |
252b5132 | 2744 | the @code{ENTRY(@var{symbol})} command in a linker script; |
a1ab1d2a | 2745 | @item |
252b5132 | 2746 | the value of the symbol @code{start}, if defined; |
a1ab1d2a | 2747 | @item |
252b5132 | 2748 | the address of the first byte of the @samp{.text} section, if present; |
a1ab1d2a | 2749 | @item |
252b5132 RH |
2750 | The address @code{0}. |
2751 | @end itemize | |
2752 | ||
2753 | @node File Commands | |
36f63dca | 2754 | @subsection Commands Dealing with Files |
252b5132 RH |
2755 | @cindex linker script file commands |
2756 | Several linker script commands deal with files. | |
2757 | ||
2758 | @table @code | |
2759 | @item INCLUDE @var{filename} | |
2760 | @kindex INCLUDE @var{filename} | |
2761 | @cindex including a linker script | |
2762 | Include the linker script @var{filename} at this point. The file will | |
2763 | be searched for in the current directory, and in any directory specified | |
ff5dcc92 | 2764 | with the @option{-L} option. You can nest calls to @code{INCLUDE} up to |
252b5132 RH |
2765 | 10 levels deep. |
2766 | ||
2767 | @item INPUT(@var{file}, @var{file}, @dots{}) | |
2768 | @itemx INPUT(@var{file} @var{file} @dots{}) | |
2769 | @kindex INPUT(@var{files}) | |
2770 | @cindex input files in linker scripts | |
2771 | @cindex input object files in linker scripts | |
2772 | @cindex linker script input object files | |
2773 | The @code{INPUT} command directs the linker to include the named files | |
2774 | in the link, as though they were named on the command line. | |
2775 | ||
2776 | For example, if you always want to include @file{subr.o} any time you do | |
2777 | a link, but you can't be bothered to put it on every link command line, | |
2778 | then you can put @samp{INPUT (subr.o)} in your linker script. | |
2779 | ||
2780 | In fact, if you like, you can list all of your input files in the linker | |
2781 | script, and then invoke the linker with nothing but a @samp{-T} option. | |
2782 | ||
e3f2db7f AO |
2783 | In case a @dfn{sysroot prefix} is configured, and the filename starts |
2784 | with the @samp{/} character, and the script being processed was | |
2785 | located inside the @dfn{sysroot prefix}, the filename will be looked | |
2786 | for in the @dfn{sysroot prefix}. Otherwise, the linker will try to | |
2787 | open the file in the current directory. If it is not found, the | |
2788 | linker will search through the archive library search path. See the | |
2789 | description of @samp{-L} in @ref{Options,,Command Line Options}. | |
252b5132 | 2790 | |
ff5dcc92 | 2791 | If you use @samp{INPUT (-l@var{file})}, @command{ld} will transform the |
252b5132 RH |
2792 | name to @code{lib@var{file}.a}, as with the command line argument |
2793 | @samp{-l}. | |
2794 | ||
2795 | When you use the @code{INPUT} command in an implicit linker script, the | |
2796 | files will be included in the link at the point at which the linker | |
2797 | script file is included. This can affect archive searching. | |
2798 | ||
2799 | @item GROUP(@var{file}, @var{file}, @dots{}) | |
2800 | @itemx GROUP(@var{file} @var{file} @dots{}) | |
2801 | @kindex GROUP(@var{files}) | |
2802 | @cindex grouping input files | |
2803 | The @code{GROUP} command is like @code{INPUT}, except that the named | |
2804 | files should all be archives, and they are searched repeatedly until no | |
2805 | new undefined references are created. See the description of @samp{-(} | |
2806 | in @ref{Options,,Command Line Options}. | |
2807 | ||
b717d30e JJ |
2808 | @item AS_NEEDED(@var{file}, @var{file}, @dots{}) |
2809 | @itemx AS_NEEDED(@var{file} @var{file} @dots{}) | |
2810 | @kindex AS_NEEDED(@var{files}) | |
2811 | This construct can appear only inside of the @code{INPUT} or @code{GROUP} | |
2812 | commands, among other filenames. The files listed will be handled | |
2813 | as if they appear directly in the @code{INPUT} or @code{GROUP} commands, | |
2814 | with the exception of ELF shared libraries, that will be added only | |
2815 | when they are actually needed. This construct essentially enables | |
2816 | @option{--as-needed} option for all the files listed inside of it | |
2817 | and restores previous @option{--as-needed} resp. @option{--no-as-needed} | |
2818 | setting afterwards. | |
2819 | ||
252b5132 RH |
2820 | @item OUTPUT(@var{filename}) |
2821 | @kindex OUTPUT(@var{filename}) | |
b45619c0 | 2822 | @cindex output file name in linker script |
252b5132 RH |
2823 | The @code{OUTPUT} command names the output file. Using |
2824 | @code{OUTPUT(@var{filename})} in the linker script is exactly like using | |
2825 | @samp{-o @var{filename}} on the command line (@pxref{Options,,Command | |
2826 | Line Options}). If both are used, the command line option takes | |
2827 | precedence. | |
2828 | ||
2829 | You can use the @code{OUTPUT} command to define a default name for the | |
2830 | output file other than the usual default of @file{a.out}. | |
2831 | ||
2832 | @item SEARCH_DIR(@var{path}) | |
2833 | @kindex SEARCH_DIR(@var{path}) | |
2834 | @cindex library search path in linker script | |
2835 | @cindex archive search path in linker script | |
2836 | @cindex search path in linker script | |
2837 | The @code{SEARCH_DIR} command adds @var{path} to the list of paths where | |
ff5dcc92 | 2838 | @command{ld} looks for archive libraries. Using |
252b5132 RH |
2839 | @code{SEARCH_DIR(@var{path})} is exactly like using @samp{-L @var{path}} |
2840 | on the command line (@pxref{Options,,Command Line Options}). If both | |
2841 | are used, then the linker will search both paths. Paths specified using | |
2842 | the command line option are searched first. | |
2843 | ||
2844 | @item STARTUP(@var{filename}) | |
2845 | @kindex STARTUP(@var{filename}) | |
2846 | @cindex first input file | |
2847 | The @code{STARTUP} command is just like the @code{INPUT} command, except | |
2848 | that @var{filename} will become the first input file to be linked, as | |
2849 | though it were specified first on the command line. This may be useful | |
2850 | when using a system in which the entry point is always the start of the | |
2851 | first file. | |
2852 | @end table | |
2853 | ||
2854 | @ifclear SingleFormat | |
2855 | @node Format Commands | |
36f63dca | 2856 | @subsection Commands Dealing with Object File Formats |
252b5132 RH |
2857 | A couple of linker script commands deal with object file formats. |
2858 | ||
2859 | @table @code | |
2860 | @item OUTPUT_FORMAT(@var{bfdname}) | |
2861 | @itemx OUTPUT_FORMAT(@var{default}, @var{big}, @var{little}) | |
2862 | @kindex OUTPUT_FORMAT(@var{bfdname}) | |
2863 | @cindex output file format in linker script | |
2864 | The @code{OUTPUT_FORMAT} command names the BFD format to use for the | |
2865 | output file (@pxref{BFD}). Using @code{OUTPUT_FORMAT(@var{bfdname})} is | |
024531e2 | 2866 | exactly like using @samp{--oformat @var{bfdname}} on the command line |
252b5132 RH |
2867 | (@pxref{Options,,Command Line Options}). If both are used, the command |
2868 | line option takes precedence. | |
2869 | ||
2870 | You can use @code{OUTPUT_FORMAT} with three arguments to use different | |
2871 | formats based on the @samp{-EB} and @samp{-EL} command line options. | |
2872 | This permits the linker script to set the output format based on the | |
2873 | desired endianness. | |
2874 | ||
2875 | If neither @samp{-EB} nor @samp{-EL} are used, then the output format | |
2876 | will be the first argument, @var{default}. If @samp{-EB} is used, the | |
2877 | output format will be the second argument, @var{big}. If @samp{-EL} is | |
2878 | used, the output format will be the third argument, @var{little}. | |
2879 | ||
2880 | For example, the default linker script for the MIPS ELF target uses this | |
2881 | command: | |
2882 | @smallexample | |
2883 | OUTPUT_FORMAT(elf32-bigmips, elf32-bigmips, elf32-littlemips) | |
2884 | @end smallexample | |
2885 | This says that the default format for the output file is | |
2886 | @samp{elf32-bigmips}, but if the user uses the @samp{-EL} command line | |
2887 | option, the output file will be created in the @samp{elf32-littlemips} | |
2888 | format. | |
2889 | ||
2890 | @item TARGET(@var{bfdname}) | |
2891 | @kindex TARGET(@var{bfdname}) | |
2892 | @cindex input file format in linker script | |
2893 | The @code{TARGET} command names the BFD format to use when reading input | |
2894 | files. It affects subsequent @code{INPUT} and @code{GROUP} commands. | |
2895 | This command is like using @samp{-b @var{bfdname}} on the command line | |
2896 | (@pxref{Options,,Command Line Options}). If the @code{TARGET} command | |
2897 | is used but @code{OUTPUT_FORMAT} is not, then the last @code{TARGET} | |
2898 | command is also used to set the format for the output file. @xref{BFD}. | |
2899 | @end table | |
2900 | @end ifclear | |
2901 | ||
2902 | @node Miscellaneous Commands | |
36f63dca | 2903 | @subsection Other Linker Script Commands |
252b5132 RH |
2904 | There are a few other linker scripts commands. |
2905 | ||
2906 | @table @code | |
2907 | @item ASSERT(@var{exp}, @var{message}) | |
2908 | @kindex ASSERT | |
2909 | @cindex assertion in linker script | |
2910 | Ensure that @var{exp} is non-zero. If it is zero, then exit the linker | |
2911 | with an error code, and print @var{message}. | |
2912 | ||
2913 | @item EXTERN(@var{symbol} @var{symbol} @dots{}) | |
2914 | @kindex EXTERN | |
2915 | @cindex undefined symbol in linker script | |
2916 | Force @var{symbol} to be entered in the output file as an undefined | |
2917 | symbol. Doing this may, for example, trigger linking of additional | |
2918 | modules from standard libraries. You may list several @var{symbol}s for | |
2919 | each @code{EXTERN}, and you may use @code{EXTERN} multiple times. This | |
2920 | command has the same effect as the @samp{-u} command-line option. | |
2921 | ||
2922 | @item FORCE_COMMON_ALLOCATION | |
2923 | @kindex FORCE_COMMON_ALLOCATION | |
2924 | @cindex common allocation in linker script | |
2925 | This command has the same effect as the @samp{-d} command-line option: | |
ff5dcc92 | 2926 | to make @command{ld} assign space to common symbols even if a relocatable |
252b5132 RH |
2927 | output file is specified (@samp{-r}). |
2928 | ||
4818e05f AM |
2929 | @item INHIBIT_COMMON_ALLOCATION |
2930 | @kindex INHIBIT_COMMON_ALLOCATION | |
2931 | @cindex common allocation in linker script | |
2932 | This command has the same effect as the @samp{--no-define-common} | |
2933 | command-line option: to make @code{ld} omit the assignment of addresses | |
2934 | to common symbols even for a non-relocatable output file. | |
2935 | ||
53d25da6 AM |
2936 | @item INSERT [ AFTER | BEFORE ] @var{output_section} |
2937 | @kindex INSERT | |
2938 | @cindex insert user script into default script | |
2939 | This command is typically used in a script specified by @samp{-T} to | |
2940 | augment the default @code{SECTIONS} with, for example, overlays. It | |
2941 | inserts all prior linker script statements after (or before) | |
2942 | @var{output_section}, and also causes @samp{-T} to not override the | |
2943 | default linker script. The exact insertion point is as for orphan | |
2944 | sections. @xref{Location Counter}. The insertion happens after the | |
2945 | linker has mapped input sections to output sections. Prior to the | |
2946 | insertion, since @samp{-T} scripts are parsed before the default | |
2947 | linker script, statements in the @samp{-T} script occur before the | |
2948 | default linker script statements in the internal linker representation | |
2949 | of the script. In particular, input section assignments will be made | |
2950 | to @samp{-T} output sections before those in the default script. Here | |
2951 | is an example of how a @samp{-T} script using @code{INSERT} might look: | |
2952 | ||
2953 | @smallexample | |
2954 | SECTIONS | |
2955 | @{ | |
2956 | OVERLAY : | |
2957 | @{ | |
2958 | .ov1 @{ ov1*(.text) @} | |
2959 | .ov2 @{ ov2*(.text) @} | |
2960 | @} | |
2961 | @} | |
2962 | INSERT AFTER .text; | |
2963 | @end smallexample | |
2964 | ||
252b5132 RH |
2965 | @item NOCROSSREFS(@var{section} @var{section} @dots{}) |
2966 | @kindex NOCROSSREFS(@var{sections}) | |
2967 | @cindex cross references | |
ff5dcc92 | 2968 | This command may be used to tell @command{ld} to issue an error about any |
252b5132 RH |
2969 | references among certain output sections. |
2970 | ||
2971 | In certain types of programs, particularly on embedded systems when | |
2972 | using overlays, when one section is loaded into memory, another section | |
2973 | will not be. Any direct references between the two sections would be | |
2974 | errors. For example, it would be an error if code in one section called | |
2975 | a function defined in the other section. | |
2976 | ||
2977 | The @code{NOCROSSREFS} command takes a list of output section names. If | |
ff5dcc92 | 2978 | @command{ld} detects any cross references between the sections, it reports |
252b5132 RH |
2979 | an error and returns a non-zero exit status. Note that the |
2980 | @code{NOCROSSREFS} command uses output section names, not input section | |
2981 | names. | |
2982 | ||
2983 | @ifclear SingleFormat | |
2984 | @item OUTPUT_ARCH(@var{bfdarch}) | |
2985 | @kindex OUTPUT_ARCH(@var{bfdarch}) | |
2986 | @cindex machine architecture | |
2987 | @cindex architecture | |
2988 | Specify a particular output machine architecture. The argument is one | |
2989 | of the names used by the BFD library (@pxref{BFD}). You can see the | |
2990 | architecture of an object file by using the @code{objdump} program with | |
2991 | the @samp{-f} option. | |
2992 | @end ifclear | |
2993 | @end table | |
2994 | ||
2995 | @node Assignments | |
2996 | @section Assigning Values to Symbols | |
2997 | @cindex assignment in scripts | |
2998 | @cindex symbol definition, scripts | |
2999 | @cindex variables, defining | |
3000 | You may assign a value to a symbol in a linker script. This will define | |
73ae6183 | 3001 | the symbol and place it into the symbol table with a global scope. |
252b5132 RH |
3002 | |
3003 | @menu | |
3004 | * Simple Assignments:: Simple Assignments | |
3005 | * PROVIDE:: PROVIDE | |
7af8e998 | 3006 | * PROVIDE_HIDDEN:: PROVIDE_HIDDEN |
73ae6183 | 3007 | * Source Code Reference:: How to use a linker script defined symbol in source code |
252b5132 RH |
3008 | @end menu |
3009 | ||
3010 | @node Simple Assignments | |
3011 | @subsection Simple Assignments | |
3012 | ||
3013 | You may assign to a symbol using any of the C assignment operators: | |
3014 | ||
3015 | @table @code | |
3016 | @item @var{symbol} = @var{expression} ; | |
3017 | @itemx @var{symbol} += @var{expression} ; | |
3018 | @itemx @var{symbol} -= @var{expression} ; | |
3019 | @itemx @var{symbol} *= @var{expression} ; | |
3020 | @itemx @var{symbol} /= @var{expression} ; | |
3021 | @itemx @var{symbol} <<= @var{expression} ; | |
3022 | @itemx @var{symbol} >>= @var{expression} ; | |
3023 | @itemx @var{symbol} &= @var{expression} ; | |
3024 | @itemx @var{symbol} |= @var{expression} ; | |
3025 | @end table | |
3026 | ||
3027 | The first case will define @var{symbol} to the value of | |
3028 | @var{expression}. In the other cases, @var{symbol} must already be | |
3029 | defined, and the value will be adjusted accordingly. | |
3030 | ||
3031 | The special symbol name @samp{.} indicates the location counter. You | |
b5666f2f | 3032 | may only use this within a @code{SECTIONS} command. @xref{Location Counter}. |
252b5132 RH |
3033 | |
3034 | The semicolon after @var{expression} is required. | |
3035 | ||
3036 | Expressions are defined below; see @ref{Expressions}. | |
3037 | ||
3038 | You may write symbol assignments as commands in their own right, or as | |
3039 | statements within a @code{SECTIONS} command, or as part of an output | |
3040 | section description in a @code{SECTIONS} command. | |
3041 | ||
3042 | The section of the symbol will be set from the section of the | |
3043 | expression; for more information, see @ref{Expression Section}. | |
3044 | ||
3045 | Here is an example showing the three different places that symbol | |
3046 | assignments may be used: | |
3047 | ||
3048 | @smallexample | |
3049 | floating_point = 0; | |
3050 | SECTIONS | |
3051 | @{ | |
3052 | .text : | |
3053 | @{ | |
3054 | *(.text) | |
3055 | _etext = .; | |
3056 | @} | |
156e34dd | 3057 | _bdata = (. + 3) & ~ 3; |
252b5132 RH |
3058 | .data : @{ *(.data) @} |
3059 | @} | |
3060 | @end smallexample | |
3061 | @noindent | |
3062 | In this example, the symbol @samp{floating_point} will be defined as | |
3063 | zero. The symbol @samp{_etext} will be defined as the address following | |
3064 | the last @samp{.text} input section. The symbol @samp{_bdata} will be | |
3065 | defined as the address following the @samp{.text} output section aligned | |
3066 | upward to a 4 byte boundary. | |
3067 | ||
3068 | @node PROVIDE | |
3069 | @subsection PROVIDE | |
3070 | @cindex PROVIDE | |
3071 | In some cases, it is desirable for a linker script to define a symbol | |
3072 | only if it is referenced and is not defined by any object included in | |
3073 | the link. For example, traditional linkers defined the symbol | |
3074 | @samp{etext}. However, ANSI C requires that the user be able to use | |
3075 | @samp{etext} as a function name without encountering an error. The | |
3076 | @code{PROVIDE} keyword may be used to define a symbol, such as | |
3077 | @samp{etext}, only if it is referenced but not defined. The syntax is | |
3078 | @code{PROVIDE(@var{symbol} = @var{expression})}. | |
3079 | ||
3080 | Here is an example of using @code{PROVIDE} to define @samp{etext}: | |
3081 | @smallexample | |
3082 | SECTIONS | |
3083 | @{ | |
3084 | .text : | |
3085 | @{ | |
3086 | *(.text) | |
3087 | _etext = .; | |
3088 | PROVIDE(etext = .); | |
3089 | @} | |
3090 | @} | |
3091 | @end smallexample | |
3092 | ||
3093 | In this example, if the program defines @samp{_etext} (with a leading | |
3094 | underscore), the linker will give a multiple definition error. If, on | |
3095 | the other hand, the program defines @samp{etext} (with no leading | |
3096 | underscore), the linker will silently use the definition in the program. | |
3097 | If the program references @samp{etext} but does not define it, the | |
3098 | linker will use the definition in the linker script. | |
3099 | ||
7af8e998 L |
3100 | @node PROVIDE_HIDDEN |
3101 | @subsection PROVIDE_HIDDEN | |
3102 | @cindex PROVIDE_HIDDEN | |
3103 | Similar to @code{PROVIDE}. For ELF targeted ports, the symbol will be | |
3104 | hidden and won't be exported. | |
3105 | ||
73ae6183 NC |
3106 | @node Source Code Reference |
3107 | @subsection Source Code Reference | |
3108 | ||
3109 | Accessing a linker script defined variable from source code is not | |
3110 | intuitive. In particular a linker script symbol is not equivalent to | |
3111 | a variable declaration in a high level language, it is instead a | |
3112 | symbol that does not have a value. | |
3113 | ||
3114 | Before going further, it is important to note that compilers often | |
3115 | transform names in the source code into different names when they are | |
3116 | stored in the symbol table. For example, Fortran compilers commonly | |
3117 | prepend or append an underscore, and C++ performs extensive @samp{name | |
3118 | mangling}. Therefore there might be a discrepancy between the name | |
3119 | of a variable as it is used in source code and the name of the same | |
3120 | variable as it is defined in a linker script. For example in C a | |
3121 | linker script variable might be referred to as: | |
3122 | ||
3123 | @smallexample | |
3124 | extern int foo; | |
3125 | @end smallexample | |
3126 | ||
3127 | But in the linker script it might be defined as: | |
3128 | ||
3129 | @smallexample | |
3130 | _foo = 1000; | |
3131 | @end smallexample | |
3132 | ||
3133 | In the remaining examples however it is assumed that no name | |
3134 | transformation has taken place. | |
3135 | ||
3136 | When a symbol is declared in a high level language such as C, two | |
3137 | things happen. The first is that the compiler reserves enough space | |
3138 | in the program's memory to hold the @emph{value} of the symbol. The | |
3139 | second is that the compiler creates an entry in the program's symbol | |
3140 | table which holds the symbol's @emph{address}. ie the symbol table | |
3141 | contains the address of the block of memory holding the symbol's | |
3142 | value. So for example the following C declaration, at file scope: | |
3143 | ||
3144 | @smallexample | |
3145 | int foo = 1000; | |
3146 | @end smallexample | |
3147 | ||
3148 | creates a entry called @samp{foo} in the symbol table. This entry | |
3149 | holds the address of an @samp{int} sized block of memory where the | |
3150 | number 1000 is initially stored. | |
3151 | ||
3152 | When a program references a symbol the compiler generates code that | |
3153 | first accesses the symbol table to find the address of the symbol's | |
3154 | memory block and then code to read the value from that memory block. | |
3155 | So: | |
3156 | ||
3157 | @smallexample | |
3158 | foo = 1; | |
3159 | @end smallexample | |
3160 | ||
3161 | looks up the symbol @samp{foo} in the symbol table, gets the address | |
3162 | associated with this symbol and then writes the value 1 into that | |
3163 | address. Whereas: | |
3164 | ||
3165 | @smallexample | |
3166 | int * a = & foo; | |
3167 | @end smallexample | |
3168 | ||
3169 | looks up the symbol @samp{foo} in the symbol table, gets it address | |
3170 | and then copies this address into the block of memory associated with | |
3171 | the variable @samp{a}. | |
3172 | ||
3173 | Linker scripts symbol declarations, by contrast, create an entry in | |
3174 | the symbol table but do not assign any memory to them. Thus they are | |
3175 | an address without a value. So for example the linker script definition: | |
3176 | ||
3177 | @smallexample | |
3178 | foo = 1000; | |
3179 | @end smallexample | |
3180 | ||
3181 | creates an entry in the symbol table called @samp{foo} which holds | |
3182 | the address of memory location 1000, but nothing special is stored at | |
3183 | address 1000. This means that you cannot access the @emph{value} of a | |
3184 | linker script defined symbol - it has no value - all you can do is | |
3185 | access the @emph{address} of a linker script defined symbol. | |
3186 | ||
3187 | Hence when you are using a linker script defined symbol in source code | |
3188 | you should always take the address of the symbol, and never attempt to | |
3189 | use its value. For example suppose you want to copy the contents of a | |
3190 | section of memory called .ROM into a section called .FLASH and the | |
3191 | linker script contains these declarations: | |
3192 | ||
3193 | @smallexample | |
3194 | @group | |
3195 | start_of_ROM = .ROM; | |
3196 | end_of_ROM = .ROM + sizeof (.ROM) - 1; | |
3197 | start_of_FLASH = .FLASH; | |
3198 | @end group | |
3199 | @end smallexample | |
3200 | ||
3201 | Then the C source code to perform the copy would be: | |
3202 | ||
3203 | @smallexample | |
3204 | @group | |
3205 | extern char start_of_ROM, end_of_ROM, start_of_FLASH; | |
c0065db7 | 3206 | |
73ae6183 NC |
3207 | memcpy (& start_of_FLASH, & start_of_ROM, & end_of_ROM - & start_of_ROM); |
3208 | @end group | |
3209 | @end smallexample | |
3210 | ||
3211 | Note the use of the @samp{&} operators. These are correct. | |
3212 | ||
252b5132 | 3213 | @node SECTIONS |
36f63dca | 3214 | @section SECTIONS Command |
252b5132 RH |
3215 | @kindex SECTIONS |
3216 | The @code{SECTIONS} command tells the linker how to map input sections | |
3217 | into output sections, and how to place the output sections in memory. | |
3218 | ||
3219 | The format of the @code{SECTIONS} command is: | |
3220 | @smallexample | |
3221 | SECTIONS | |
3222 | @{ | |
3223 | @var{sections-command} | |
3224 | @var{sections-command} | |
3225 | @dots{} | |
3226 | @} | |
3227 | @end smallexample | |
3228 | ||
3229 | Each @var{sections-command} may of be one of the following: | |
3230 | ||
3231 | @itemize @bullet | |
3232 | @item | |
3233 | an @code{ENTRY} command (@pxref{Entry Point,,Entry command}) | |
3234 | @item | |
3235 | a symbol assignment (@pxref{Assignments}) | |
3236 | @item | |
3237 | an output section description | |
3238 | @item | |
3239 | an overlay description | |
3240 | @end itemize | |
3241 | ||
3242 | The @code{ENTRY} command and symbol assignments are permitted inside the | |
3243 | @code{SECTIONS} command for convenience in using the location counter in | |
3244 | those commands. This can also make the linker script easier to | |
3245 | understand because you can use those commands at meaningful points in | |
3246 | the layout of the output file. | |
3247 | ||
3248 | Output section descriptions and overlay descriptions are described | |
3249 | below. | |
3250 | ||
3251 | If you do not use a @code{SECTIONS} command in your linker script, the | |
3252 | linker will place each input section into an identically named output | |
3253 | section in the order that the sections are first encountered in the | |
3254 | input files. If all input sections are present in the first file, for | |
3255 | example, the order of sections in the output file will match the order | |
3256 | in the first input file. The first section will be at address zero. | |
3257 | ||
3258 | @menu | |
3259 | * Output Section Description:: Output section description | |
3260 | * Output Section Name:: Output section name | |
3261 | * Output Section Address:: Output section address | |
3262 | * Input Section:: Input section description | |
3263 | * Output Section Data:: Output section data | |
3264 | * Output Section Keywords:: Output section keywords | |
3265 | * Output Section Discarding:: Output section discarding | |
3266 | * Output Section Attributes:: Output section attributes | |
3267 | * Overlay Description:: Overlay description | |
3268 | @end menu | |
3269 | ||
3270 | @node Output Section Description | |
36f63dca | 3271 | @subsection Output Section Description |
252b5132 RH |
3272 | The full description of an output section looks like this: |
3273 | @smallexample | |
a1ab1d2a | 3274 | @group |
7e7d5768 | 3275 | @var{section} [@var{address}] [(@var{type})] : |
bbf115d3 | 3276 | [AT(@var{lma})] [ALIGN(@var{section_align})] [SUBALIGN(@var{subsection_align})] |
252b5132 RH |
3277 | @{ |
3278 | @var{output-section-command} | |
3279 | @var{output-section-command} | |
3280 | @dots{} | |
562d3460 | 3281 | @} [>@var{region}] [AT>@var{lma_region}] [:@var{phdr} :@var{phdr} @dots{}] [=@var{fillexp}] |
252b5132 RH |
3282 | @end group |
3283 | @end smallexample | |
3284 | ||
3285 | Most output sections do not use most of the optional section attributes. | |
3286 | ||
3287 | The whitespace around @var{section} is required, so that the section | |
3288 | name is unambiguous. The colon and the curly braces are also required. | |
3289 | The line breaks and other white space are optional. | |
3290 | ||
3291 | Each @var{output-section-command} may be one of the following: | |
3292 | ||
3293 | @itemize @bullet | |
3294 | @item | |
3295 | a symbol assignment (@pxref{Assignments}) | |
3296 | @item | |
3297 | an input section description (@pxref{Input Section}) | |
3298 | @item | |
3299 | data values to include directly (@pxref{Output Section Data}) | |
3300 | @item | |
3301 | a special output section keyword (@pxref{Output Section Keywords}) | |
3302 | @end itemize | |
3303 | ||
3304 | @node Output Section Name | |
36f63dca | 3305 | @subsection Output Section Name |
252b5132 RH |
3306 | @cindex name, section |
3307 | @cindex section name | |
3308 | The name of the output section is @var{section}. @var{section} must | |
3309 | meet the constraints of your output format. In formats which only | |
3310 | support a limited number of sections, such as @code{a.out}, the name | |
3311 | must be one of the names supported by the format (@code{a.out}, for | |
3312 | example, allows only @samp{.text}, @samp{.data} or @samp{.bss}). If the | |
3313 | output format supports any number of sections, but with numbers and not | |
3314 | names (as is the case for Oasys), the name should be supplied as a | |
3315 | quoted numeric string. A section name may consist of any sequence of | |
3316 | characters, but a name which contains any unusual characters such as | |
3317 | commas must be quoted. | |
3318 | ||
3319 | The output section name @samp{/DISCARD/} is special; @ref{Output Section | |
3320 | Discarding}. | |
3321 | ||
3322 | @node Output Section Address | |
2a16d82a | 3323 | @subsection Output Section Address |
252b5132 RH |
3324 | @cindex address, section |
3325 | @cindex section address | |
3326 | The @var{address} is an expression for the VMA (the virtual memory | |
3327 | address) of the output section. If you do not provide @var{address}, | |
3328 | the linker will set it based on @var{region} if present, or otherwise | |
3329 | based on the current value of the location counter. | |
3330 | ||
3331 | If you provide @var{address}, the address of the output section will be | |
3332 | set to precisely that. If you provide neither @var{address} nor | |
3333 | @var{region}, then the address of the output section will be set to the | |
3334 | current value of the location counter aligned to the alignment | |
3335 | requirements of the output section. The alignment requirement of the | |
3336 | output section is the strictest alignment of any input section contained | |
3337 | within the output section. | |
3338 | ||
3339 | For example, | |
3340 | @smallexample | |
3341 | .text . : @{ *(.text) @} | |
3342 | @end smallexample | |
3343 | @noindent | |
3344 | and | |
3345 | @smallexample | |
3346 | .text : @{ *(.text) @} | |
3347 | @end smallexample | |
3348 | @noindent | |
3349 | are subtly different. The first will set the address of the | |
3350 | @samp{.text} output section to the current value of the location | |
3351 | counter. The second will set it to the current value of the location | |
3352 | counter aligned to the strictest alignment of a @samp{.text} input | |
3353 | section. | |
3354 | ||
3355 | The @var{address} may be an arbitrary expression; @ref{Expressions}. | |
3356 | For example, if you want to align the section on a 0x10 byte boundary, | |
3357 | so that the lowest four bits of the section address are zero, you could | |
3358 | do something like this: | |
3359 | @smallexample | |
3360 | .text ALIGN(0x10) : @{ *(.text) @} | |
3361 | @end smallexample | |
3362 | @noindent | |
3363 | This works because @code{ALIGN} returns the current location counter | |
3364 | aligned upward to the specified value. | |
3365 | ||
3366 | Specifying @var{address} for a section will change the value of the | |
3367 | location counter. | |
3368 | ||
3369 | @node Input Section | |
36f63dca | 3370 | @subsection Input Section Description |
252b5132 RH |
3371 | @cindex input sections |
3372 | @cindex mapping input sections to output sections | |
3373 | The most common output section command is an input section description. | |
3374 | ||
3375 | The input section description is the most basic linker script operation. | |
3376 | You use output sections to tell the linker how to lay out your program | |
3377 | in memory. You use input section descriptions to tell the linker how to | |
3378 | map the input files into your memory layout. | |
3379 | ||
3380 | @menu | |
3381 | * Input Section Basics:: Input section basics | |
3382 | * Input Section Wildcards:: Input section wildcard patterns | |
3383 | * Input Section Common:: Input section for common symbols | |
3384 | * Input Section Keep:: Input section and garbage collection | |
3385 | * Input Section Example:: Input section example | |
3386 | @end menu | |
3387 | ||
3388 | @node Input Section Basics | |
36f63dca | 3389 | @subsubsection Input Section Basics |
252b5132 RH |
3390 | @cindex input section basics |
3391 | An input section description consists of a file name optionally followed | |
3392 | by a list of section names in parentheses. | |
3393 | ||
3394 | The file name and the section name may be wildcard patterns, which we | |
3395 | describe further below (@pxref{Input Section Wildcards}). | |
3396 | ||
3397 | The most common input section description is to include all input | |
3398 | sections with a particular name in the output section. For example, to | |
3399 | include all input @samp{.text} sections, you would write: | |
3400 | @smallexample | |
3401 | *(.text) | |
3402 | @end smallexample | |
3403 | @noindent | |
18625d54 CM |
3404 | Here the @samp{*} is a wildcard which matches any file name. To exclude a list |
3405 | of files from matching the file name wildcard, EXCLUDE_FILE may be used to | |
3406 | match all files except the ones specified in the EXCLUDE_FILE list. For | |
3407 | example: | |
252b5132 | 3408 | @smallexample |
b4346c09 | 3409 | *(EXCLUDE_FILE (*crtend.o *otherfile.o) .ctors) |
252b5132 | 3410 | @end smallexample |
765b7cbe JB |
3411 | will cause all .ctors sections from all files except @file{crtend.o} and |
3412 | @file{otherfile.o} to be included. | |
252b5132 RH |
3413 | |
3414 | There are two ways to include more than one section: | |
3415 | @smallexample | |
3416 | *(.text .rdata) | |
3417 | *(.text) *(.rdata) | |
3418 | @end smallexample | |
3419 | @noindent | |
3420 | The difference between these is the order in which the @samp{.text} and | |
3421 | @samp{.rdata} input sections will appear in the output section. In the | |
b6bf44ba AM |
3422 | first example, they will be intermingled, appearing in the same order as |
3423 | they are found in the linker input. In the second example, all | |
252b5132 RH |
3424 | @samp{.text} input sections will appear first, followed by all |
3425 | @samp{.rdata} input sections. | |
3426 | ||
3427 | You can specify a file name to include sections from a particular file. | |
3428 | You would do this if one or more of your files contain special data that | |
3429 | needs to be at a particular location in memory. For example: | |
3430 | @smallexample | |
3431 | data.o(.data) | |
3432 | @end smallexample | |
3433 | ||
967928e9 AM |
3434 | You can also specify files within archives by writing a pattern |
3435 | matching the archive, a colon, then the pattern matching the file, | |
3436 | with no whitespace around the colon. | |
3437 | ||
3438 | @table @samp | |
3439 | @item archive:file | |
3440 | matches file within archive | |
3441 | @item archive: | |
3442 | matches the whole archive | |
3443 | @item :file | |
3444 | matches file but not one in an archive | |
3445 | @end table | |
3446 | ||
3447 | Either one or both of @samp{archive} and @samp{file} can contain shell | |
3448 | wildcards. On DOS based file systems, the linker will assume that a | |
3449 | single letter followed by a colon is a drive specifier, so | |
3450 | @samp{c:myfile.o} is a simple file specification, not @samp{myfile.o} | |
3451 | within an archive called @samp{c}. @samp{archive:file} filespecs may | |
3452 | also be used within an @code{EXCLUDE_FILE} list, but may not appear in | |
3453 | other linker script contexts. For instance, you cannot extract a file | |
3454 | from an archive by using @samp{archive:file} in an @code{INPUT} | |
3455 | command. | |
3456 | ||
252b5132 RH |
3457 | If you use a file name without a list of sections, then all sections in |
3458 | the input file will be included in the output section. This is not | |
3459 | commonly done, but it may by useful on occasion. For example: | |
3460 | @smallexample | |
3461 | data.o | |
3462 | @end smallexample | |
3463 | ||
967928e9 AM |
3464 | When you use a file name which is not an @samp{archive:file} specifier |
3465 | and does not contain any wild card | |
252b5132 RH |
3466 | characters, the linker will first see if you also specified the file |
3467 | name on the linker command line or in an @code{INPUT} command. If you | |
3468 | did not, the linker will attempt to open the file as an input file, as | |
3469 | though it appeared on the command line. Note that this differs from an | |
3470 | @code{INPUT} command, because the linker will not search for the file in | |
3471 | the archive search path. | |
3472 | ||
3473 | @node Input Section Wildcards | |
36f63dca | 3474 | @subsubsection Input Section Wildcard Patterns |
252b5132 RH |
3475 | @cindex input section wildcards |
3476 | @cindex wildcard file name patterns | |
3477 | @cindex file name wildcard patterns | |
3478 | @cindex section name wildcard patterns | |
3479 | In an input section description, either the file name or the section | |
3480 | name or both may be wildcard patterns. | |
3481 | ||
3482 | The file name of @samp{*} seen in many examples is a simple wildcard | |
3483 | pattern for the file name. | |
3484 | ||
3485 | The wildcard patterns are like those used by the Unix shell. | |
3486 | ||
3487 | @table @samp | |
3488 | @item * | |
3489 | matches any number of characters | |
3490 | @item ? | |
3491 | matches any single character | |
3492 | @item [@var{chars}] | |
3493 | matches a single instance of any of the @var{chars}; the @samp{-} | |
3494 | character may be used to specify a range of characters, as in | |
3495 | @samp{[a-z]} to match any lower case letter | |
3496 | @item \ | |
3497 | quotes the following character | |
3498 | @end table | |
3499 | ||
3500 | When a file name is matched with a wildcard, the wildcard characters | |
3501 | will not match a @samp{/} character (used to separate directory names on | |
3502 | Unix). A pattern consisting of a single @samp{*} character is an | |
3503 | exception; it will always match any file name, whether it contains a | |
3504 | @samp{/} or not. In a section name, the wildcard characters will match | |
3505 | a @samp{/} character. | |
3506 | ||
3507 | File name wildcard patterns only match files which are explicitly | |
3508 | specified on the command line or in an @code{INPUT} command. The linker | |
3509 | does not search directories to expand wildcards. | |
3510 | ||
3511 | If a file name matches more than one wildcard pattern, or if a file name | |
3512 | appears explicitly and is also matched by a wildcard pattern, the linker | |
3513 | will use the first match in the linker script. For example, this | |
3514 | sequence of input section descriptions is probably in error, because the | |
3515 | @file{data.o} rule will not be used: | |
3516 | @smallexample | |
3517 | .data : @{ *(.data) @} | |
3518 | .data1 : @{ data.o(.data) @} | |
3519 | @end smallexample | |
3520 | ||
bcaa7b3e | 3521 | @cindex SORT_BY_NAME |
252b5132 RH |
3522 | Normally, the linker will place files and sections matched by wildcards |
3523 | in the order in which they are seen during the link. You can change | |
bcaa7b3e L |
3524 | this by using the @code{SORT_BY_NAME} keyword, which appears before a wildcard |
3525 | pattern in parentheses (e.g., @code{SORT_BY_NAME(.text*)}). When the | |
3526 | @code{SORT_BY_NAME} keyword is used, the linker will sort the files or sections | |
252b5132 RH |
3527 | into ascending order by name before placing them in the output file. |
3528 | ||
bcaa7b3e L |
3529 | @cindex SORT_BY_ALIGNMENT |
3530 | @code{SORT_BY_ALIGNMENT} is very similar to @code{SORT_BY_NAME}. The | |
3531 | difference is @code{SORT_BY_ALIGNMENT} will sort sections into | |
3532 | ascending order by alignment before placing them in the output file. | |
3533 | ||
3534 | @cindex SORT | |
3535 | @code{SORT} is an alias for @code{SORT_BY_NAME}. | |
3536 | ||
3537 | When there are nested section sorting commands in linker script, there | |
3538 | can be at most 1 level of nesting for section sorting commands. | |
3539 | ||
3540 | @enumerate | |
3541 | @item | |
3542 | @code{SORT_BY_NAME} (@code{SORT_BY_ALIGNMENT} (wildcard section pattern)). | |
3543 | It will sort the input sections by name first, then by alignment if 2 | |
3544 | sections have the same name. | |
3545 | @item | |
3546 | @code{SORT_BY_ALIGNMENT} (@code{SORT_BY_NAME} (wildcard section pattern)). | |
3547 | It will sort the input sections by alignment first, then by name if 2 | |
3548 | sections have the same alignment. | |
3549 | @item | |
c0065db7 | 3550 | @code{SORT_BY_NAME} (@code{SORT_BY_NAME} (wildcard section pattern)) is |
bcaa7b3e L |
3551 | treated the same as @code{SORT_BY_NAME} (wildcard section pattern). |
3552 | @item | |
3553 | @code{SORT_BY_ALIGNMENT} (@code{SORT_BY_ALIGNMENT} (wildcard section pattern)) | |
3554 | is treated the same as @code{SORT_BY_ALIGNMENT} (wildcard section pattern). | |
3555 | @item | |
3556 | All other nested section sorting commands are invalid. | |
3557 | @end enumerate | |
3558 | ||
3559 | When both command line section sorting option and linker script | |
3560 | section sorting command are used, section sorting command always | |
3561 | takes precedence over the command line option. | |
3562 | ||
3563 | If the section sorting command in linker script isn't nested, the | |
3564 | command line option will make the section sorting command to be | |
3565 | treated as nested sorting command. | |
3566 | ||
3567 | @enumerate | |
3568 | @item | |
3569 | @code{SORT_BY_NAME} (wildcard section pattern ) with | |
3570 | @option{--sort-sections alignment} is equivalent to | |
3571 | @code{SORT_BY_NAME} (@code{SORT_BY_ALIGNMENT} (wildcard section pattern)). | |
3572 | @item | |
3573 | @code{SORT_BY_ALIGNMENT} (wildcard section pattern) with | |
3574 | @option{--sort-section name} is equivalent to | |
3575 | @code{SORT_BY_ALIGNMENT} (@code{SORT_BY_NAME} (wildcard section pattern)). | |
3576 | @end enumerate | |
3577 | ||
3578 | If the section sorting command in linker script is nested, the | |
3579 | command line option will be ignored. | |
3580 | ||
252b5132 RH |
3581 | If you ever get confused about where input sections are going, use the |
3582 | @samp{-M} linker option to generate a map file. The map file shows | |
3583 | precisely how input sections are mapped to output sections. | |
3584 | ||
3585 | This example shows how wildcard patterns might be used to partition | |
3586 | files. This linker script directs the linker to place all @samp{.text} | |
3587 | sections in @samp{.text} and all @samp{.bss} sections in @samp{.bss}. | |
3588 | The linker will place the @samp{.data} section from all files beginning | |
3589 | with an upper case character in @samp{.DATA}; for all other files, the | |
3590 | linker will place the @samp{.data} section in @samp{.data}. | |
3591 | @smallexample | |
3592 | @group | |
3593 | SECTIONS @{ | |
3594 | .text : @{ *(.text) @} | |
3595 | .DATA : @{ [A-Z]*(.data) @} | |
3596 | .data : @{ *(.data) @} | |
3597 | .bss : @{ *(.bss) @} | |
3598 | @} | |
3599 | @end group | |
3600 | @end smallexample | |
3601 | ||
3602 | @node Input Section Common | |
36f63dca | 3603 | @subsubsection Input Section for Common Symbols |
252b5132 RH |
3604 | @cindex common symbol placement |
3605 | @cindex uninitialized data placement | |
3606 | A special notation is needed for common symbols, because in many object | |
3607 | file formats common symbols do not have a particular input section. The | |
3608 | linker treats common symbols as though they are in an input section | |
3609 | named @samp{COMMON}. | |
3610 | ||
3611 | You may use file names with the @samp{COMMON} section just as with any | |
3612 | other input sections. You can use this to place common symbols from a | |
3613 | particular input file in one section while common symbols from other | |
3614 | input files are placed in another section. | |
3615 | ||
3616 | In most cases, common symbols in input files will be placed in the | |
3617 | @samp{.bss} section in the output file. For example: | |
3618 | @smallexample | |
3619 | .bss @{ *(.bss) *(COMMON) @} | |
3620 | @end smallexample | |
3621 | ||
3622 | @cindex scommon section | |
3623 | @cindex small common symbols | |
3624 | Some object file formats have more than one type of common symbol. For | |
3625 | example, the MIPS ELF object file format distinguishes standard common | |
3626 | symbols and small common symbols. In this case, the linker will use a | |
3627 | different special section name for other types of common symbols. In | |
3628 | the case of MIPS ELF, the linker uses @samp{COMMON} for standard common | |
3629 | symbols and @samp{.scommon} for small common symbols. This permits you | |
3630 | to map the different types of common symbols into memory at different | |
3631 | locations. | |
3632 | ||
3633 | @cindex [COMMON] | |
3634 | You will sometimes see @samp{[COMMON]} in old linker scripts. This | |
3635 | notation is now considered obsolete. It is equivalent to | |
3636 | @samp{*(COMMON)}. | |
3637 | ||
3638 | @node Input Section Keep | |
36f63dca | 3639 | @subsubsection Input Section and Garbage Collection |
252b5132 RH |
3640 | @cindex KEEP |
3641 | @cindex garbage collection | |
3642 | When link-time garbage collection is in use (@samp{--gc-sections}), | |
a1ab1d2a | 3643 | it is often useful to mark sections that should not be eliminated. |
252b5132 RH |
3644 | This is accomplished by surrounding an input section's wildcard entry |
3645 | with @code{KEEP()}, as in @code{KEEP(*(.init))} or | |
bcaa7b3e | 3646 | @code{KEEP(SORT_BY_NAME(*)(.ctors))}. |
252b5132 RH |
3647 | |
3648 | @node Input Section Example | |
36f63dca | 3649 | @subsubsection Input Section Example |
252b5132 RH |
3650 | The following example is a complete linker script. It tells the linker |
3651 | to read all of the sections from file @file{all.o} and place them at the | |
3652 | start of output section @samp{outputa} which starts at location | |
3653 | @samp{0x10000}. All of section @samp{.input1} from file @file{foo.o} | |
3654 | follows immediately, in the same output section. All of section | |
3655 | @samp{.input2} from @file{foo.o} goes into output section | |
3656 | @samp{outputb}, followed by section @samp{.input1} from @file{foo1.o}. | |
3657 | All of the remaining @samp{.input1} and @samp{.input2} sections from any | |
3658 | files are written to output section @samp{outputc}. | |
3659 | ||
3660 | @smallexample | |
3661 | @group | |
3662 | SECTIONS @{ | |
3663 | outputa 0x10000 : | |
3664 | @{ | |
3665 | all.o | |
3666 | foo.o (.input1) | |
3667 | @} | |
36f63dca NC |
3668 | @end group |
3669 | @group | |
252b5132 RH |
3670 | outputb : |
3671 | @{ | |
3672 | foo.o (.input2) | |
3673 | foo1.o (.input1) | |
3674 | @} | |
36f63dca NC |
3675 | @end group |
3676 | @group | |
252b5132 RH |
3677 | outputc : |
3678 | @{ | |
3679 | *(.input1) | |
3680 | *(.input2) | |
3681 | @} | |
3682 | @} | |
3683 | @end group | |
a1ab1d2a | 3684 | @end smallexample |
252b5132 RH |
3685 | |
3686 | @node Output Section Data | |
36f63dca | 3687 | @subsection Output Section Data |
252b5132 RH |
3688 | @cindex data |
3689 | @cindex section data | |
3690 | @cindex output section data | |
3691 | @kindex BYTE(@var{expression}) | |
3692 | @kindex SHORT(@var{expression}) | |
3693 | @kindex LONG(@var{expression}) | |
3694 | @kindex QUAD(@var{expression}) | |
3695 | @kindex SQUAD(@var{expression}) | |
3696 | You can include explicit bytes of data in an output section by using | |
3697 | @code{BYTE}, @code{SHORT}, @code{LONG}, @code{QUAD}, or @code{SQUAD} as | |
3698 | an output section command. Each keyword is followed by an expression in | |
3699 | parentheses providing the value to store (@pxref{Expressions}). The | |
3700 | value of the expression is stored at the current value of the location | |
3701 | counter. | |
3702 | ||
3703 | The @code{BYTE}, @code{SHORT}, @code{LONG}, and @code{QUAD} commands | |
3704 | store one, two, four, and eight bytes (respectively). After storing the | |
3705 | bytes, the location counter is incremented by the number of bytes | |
3706 | stored. | |
3707 | ||
3708 | For example, this will store the byte 1 followed by the four byte value | |
3709 | of the symbol @samp{addr}: | |
3710 | @smallexample | |
3711 | BYTE(1) | |
3712 | LONG(addr) | |
3713 | @end smallexample | |
3714 | ||
3715 | When using a 64 bit host or target, @code{QUAD} and @code{SQUAD} are the | |
3716 | same; they both store an 8 byte, or 64 bit, value. When both host and | |
3717 | target are 32 bits, an expression is computed as 32 bits. In this case | |
3718 | @code{QUAD} stores a 32 bit value zero extended to 64 bits, and | |
3719 | @code{SQUAD} stores a 32 bit value sign extended to 64 bits. | |
3720 | ||
3721 | If the object file format of the output file has an explicit endianness, | |
3722 | which is the normal case, the value will be stored in that endianness. | |
3723 | When the object file format does not have an explicit endianness, as is | |
3724 | true of, for example, S-records, the value will be stored in the | |
3725 | endianness of the first input object file. | |
3726 | ||
36f63dca | 3727 | Note---these commands only work inside a section description and not |
2b5fc1f5 NC |
3728 | between them, so the following will produce an error from the linker: |
3729 | @smallexample | |
3730 | SECTIONS @{@ .text : @{@ *(.text) @}@ LONG(1) .data : @{@ *(.data) @}@ @}@ | |
3731 | @end smallexample | |
3732 | whereas this will work: | |
3733 | @smallexample | |
3734 | SECTIONS @{@ .text : @{@ *(.text) ; LONG(1) @}@ .data : @{@ *(.data) @}@ @}@ | |
3735 | @end smallexample | |
3736 | ||
252b5132 RH |
3737 | @kindex FILL(@var{expression}) |
3738 | @cindex holes, filling | |
3739 | @cindex unspecified memory | |
3740 | You may use the @code{FILL} command to set the fill pattern for the | |
3741 | current section. It is followed by an expression in parentheses. Any | |
3742 | otherwise unspecified regions of memory within the section (for example, | |
3743 | gaps left due to the required alignment of input sections) are filled | |
a139d329 | 3744 | with the value of the expression, repeated as |
252b5132 RH |
3745 | necessary. A @code{FILL} statement covers memory locations after the |
3746 | point at which it occurs in the section definition; by including more | |
3747 | than one @code{FILL} statement, you can have different fill patterns in | |
3748 | different parts of an output section. | |
3749 | ||
3750 | This example shows how to fill unspecified regions of memory with the | |
563e308f | 3751 | value @samp{0x90}: |
252b5132 | 3752 | @smallexample |
563e308f | 3753 | FILL(0x90909090) |
252b5132 RH |
3754 | @end smallexample |
3755 | ||
3756 | The @code{FILL} command is similar to the @samp{=@var{fillexp}} output | |
9673c93c | 3757 | section attribute, but it only affects the |
252b5132 RH |
3758 | part of the section following the @code{FILL} command, rather than the |
3759 | entire section. If both are used, the @code{FILL} command takes | |
9673c93c | 3760 | precedence. @xref{Output Section Fill}, for details on the fill |
a139d329 | 3761 | expression. |
252b5132 RH |
3762 | |
3763 | @node Output Section Keywords | |
36f63dca | 3764 | @subsection Output Section Keywords |
252b5132 RH |
3765 | There are a couple of keywords which can appear as output section |
3766 | commands. | |
3767 | ||
3768 | @table @code | |
3769 | @kindex CREATE_OBJECT_SYMBOLS | |
3770 | @cindex input filename symbols | |
3771 | @cindex filename symbols | |
3772 | @item CREATE_OBJECT_SYMBOLS | |
3773 | The command tells the linker to create a symbol for each input file. | |
3774 | The name of each symbol will be the name of the corresponding input | |
3775 | file. The section of each symbol will be the output section in which | |
3776 | the @code{CREATE_OBJECT_SYMBOLS} command appears. | |
3777 | ||
3778 | This is conventional for the a.out object file format. It is not | |
3779 | normally used for any other object file format. | |
3780 | ||
3781 | @kindex CONSTRUCTORS | |
3782 | @cindex C++ constructors, arranging in link | |
3783 | @cindex constructors, arranging in link | |
3784 | @item CONSTRUCTORS | |
3785 | When linking using the a.out object file format, the linker uses an | |
3786 | unusual set construct to support C++ global constructors and | |
3787 | destructors. When linking object file formats which do not support | |
3788 | arbitrary sections, such as ECOFF and XCOFF, the linker will | |
3789 | automatically recognize C++ global constructors and destructors by name. | |
3790 | For these object file formats, the @code{CONSTRUCTORS} command tells the | |
3791 | linker to place constructor information in the output section where the | |
3792 | @code{CONSTRUCTORS} command appears. The @code{CONSTRUCTORS} command is | |
3793 | ignored for other object file formats. | |
3794 | ||
3795 | The symbol @w{@code{__CTOR_LIST__}} marks the start of the global | |
7e69709c AM |
3796 | constructors, and the symbol @w{@code{__CTOR_END__}} marks the end. |
3797 | Similarly, @w{@code{__DTOR_LIST__}} and @w{@code{__DTOR_END__}} mark | |
3798 | the start and end of the global destructors. The | |
252b5132 RH |
3799 | first word in the list is the number of entries, followed by the address |
3800 | of each constructor or destructor, followed by a zero word. The | |
3801 | compiler must arrange to actually run the code. For these object file | |
3802 | formats @sc{gnu} C++ normally calls constructors from a subroutine | |
3803 | @code{__main}; a call to @code{__main} is automatically inserted into | |
3804 | the startup code for @code{main}. @sc{gnu} C++ normally runs | |
3805 | destructors either by using @code{atexit}, or directly from the function | |
3806 | @code{exit}. | |
3807 | ||
3808 | For object file formats such as @code{COFF} or @code{ELF} which support | |
3809 | arbitrary section names, @sc{gnu} C++ will normally arrange to put the | |
3810 | addresses of global constructors and destructors into the @code{.ctors} | |
3811 | and @code{.dtors} sections. Placing the following sequence into your | |
3812 | linker script will build the sort of table which the @sc{gnu} C++ | |
3813 | runtime code expects to see. | |
3814 | ||
3815 | @smallexample | |
3816 | __CTOR_LIST__ = .; | |
3817 | LONG((__CTOR_END__ - __CTOR_LIST__) / 4 - 2) | |
3818 | *(.ctors) | |
3819 | LONG(0) | |
3820 | __CTOR_END__ = .; | |
3821 | __DTOR_LIST__ = .; | |
3822 | LONG((__DTOR_END__ - __DTOR_LIST__) / 4 - 2) | |
3823 | *(.dtors) | |
3824 | LONG(0) | |
3825 | __DTOR_END__ = .; | |
3826 | @end smallexample | |
3827 | ||
3828 | If you are using the @sc{gnu} C++ support for initialization priority, | |
3829 | which provides some control over the order in which global constructors | |
3830 | are run, you must sort the constructors at link time to ensure that they | |
3831 | are executed in the correct order. When using the @code{CONSTRUCTORS} | |
bcaa7b3e L |
3832 | command, use @samp{SORT_BY_NAME(CONSTRUCTORS)} instead. When using the |
3833 | @code{.ctors} and @code{.dtors} sections, use @samp{*(SORT_BY_NAME(.ctors))} and | |
3834 | @samp{*(SORT_BY_NAME(.dtors))} instead of just @samp{*(.ctors)} and | |
252b5132 RH |
3835 | @samp{*(.dtors)}. |
3836 | ||
3837 | Normally the compiler and linker will handle these issues automatically, | |
3838 | and you will not need to concern yourself with them. However, you may | |
3839 | need to consider this if you are using C++ and writing your own linker | |
3840 | scripts. | |
3841 | ||
3842 | @end table | |
3843 | ||
3844 | @node Output Section Discarding | |
36f63dca | 3845 | @subsection Output Section Discarding |
252b5132 RH |
3846 | @cindex discarding sections |
3847 | @cindex sections, discarding | |
3848 | @cindex removing sections | |
74541ad4 AM |
3849 | The linker will not create output sections with no contents. This is |
3850 | for convenience when referring to input sections that may or may not | |
3851 | be present in any of the input files. For example: | |
252b5132 | 3852 | @smallexample |
49c13adb | 3853 | .foo : @{ *(.foo) @} |
252b5132 RH |
3854 | @end smallexample |
3855 | @noindent | |
3856 | will only create a @samp{.foo} section in the output file if there is a | |
74541ad4 AM |
3857 | @samp{.foo} section in at least one input file, and if the input |
3858 | sections are not all empty. Other link script directives that allocate | |
3859 | space in an output section will also create the output section. | |
3860 | ||
a0976ea4 | 3861 | The linker will ignore address assignments (@pxref{Output Section Address}) |
74541ad4 AM |
3862 | on discarded output sections, except when the linker script defines |
3863 | symbols in the output section. In that case the linker will obey | |
a0976ea4 AM |
3864 | the address assignments, possibly advancing dot even though the |
3865 | section is discarded. | |
252b5132 RH |
3866 | |
3867 | @cindex /DISCARD/ | |
3868 | The special output section name @samp{/DISCARD/} may be used to discard | |
3869 | input sections. Any input sections which are assigned to an output | |
3870 | section named @samp{/DISCARD/} are not included in the output file. | |
3871 | ||
3872 | @node Output Section Attributes | |
36f63dca | 3873 | @subsection Output Section Attributes |
252b5132 RH |
3874 | @cindex output section attributes |
3875 | We showed above that the full description of an output section looked | |
3876 | like this: | |
3877 | @smallexample | |
a1ab1d2a | 3878 | @group |
7e7d5768 | 3879 | @var{section} [@var{address}] [(@var{type})] : |
bbf115d3 | 3880 | [AT(@var{lma})] [ALIGN(@var{section_align})] [SUBALIGN(@var{subsection_align})] |
252b5132 RH |
3881 | @{ |
3882 | @var{output-section-command} | |
3883 | @var{output-section-command} | |
3884 | @dots{} | |
562d3460 | 3885 | @} [>@var{region}] [AT>@var{lma_region}] [:@var{phdr} :@var{phdr} @dots{}] [=@var{fillexp}] |
252b5132 RH |
3886 | @end group |
3887 | @end smallexample | |
3888 | We've already described @var{section}, @var{address}, and | |
3889 | @var{output-section-command}. In this section we will describe the | |
3890 | remaining section attributes. | |
3891 | ||
a1ab1d2a | 3892 | @menu |
252b5132 RH |
3893 | * Output Section Type:: Output section type |
3894 | * Output Section LMA:: Output section LMA | |
bbf115d3 | 3895 | * Forced Output Alignment:: Forced Output Alignment |
7e7d5768 | 3896 | * Forced Input Alignment:: Forced Input Alignment |
252b5132 RH |
3897 | * Output Section Region:: Output section region |
3898 | * Output Section Phdr:: Output section phdr | |
3899 | * Output Section Fill:: Output section fill | |
3900 | @end menu | |
3901 | ||
3902 | @node Output Section Type | |
36f63dca | 3903 | @subsubsection Output Section Type |
252b5132 RH |
3904 | Each output section may have a type. The type is a keyword in |
3905 | parentheses. The following types are defined: | |
3906 | ||
3907 | @table @code | |
3908 | @item NOLOAD | |
3909 | The section should be marked as not loadable, so that it will not be | |
3910 | loaded into memory when the program is run. | |
3911 | @item DSECT | |
3912 | @itemx COPY | |
3913 | @itemx INFO | |
3914 | @itemx OVERLAY | |
3915 | These type names are supported for backward compatibility, and are | |
3916 | rarely used. They all have the same effect: the section should be | |
3917 | marked as not allocatable, so that no memory is allocated for the | |
3918 | section when the program is run. | |
3919 | @end table | |
3920 | ||
3921 | @kindex NOLOAD | |
3922 | @cindex prevent unnecessary loading | |
3923 | @cindex loading, preventing | |
3924 | The linker normally sets the attributes of an output section based on | |
3925 | the input sections which map into it. You can override this by using | |
3926 | the section type. For example, in the script sample below, the | |
3927 | @samp{ROM} section is addressed at memory location @samp{0} and does not | |
3928 | need to be loaded when the program is run. The contents of the | |
3929 | @samp{ROM} section will appear in the linker output file as usual. | |
3930 | @smallexample | |
3931 | @group | |
3932 | SECTIONS @{ | |
3933 | ROM 0 (NOLOAD) : @{ @dots{} @} | |
3934 | @dots{} | |
3935 | @} | |
3936 | @end group | |
3937 | @end smallexample | |
3938 | ||
3939 | @node Output Section LMA | |
36f63dca | 3940 | @subsubsection Output Section LMA |
562d3460 | 3941 | @kindex AT>@var{lma_region} |
252b5132 RH |
3942 | @kindex AT(@var{lma}) |
3943 | @cindex load address | |
3944 | @cindex section load address | |
3945 | Every section has a virtual address (VMA) and a load address (LMA); see | |
3946 | @ref{Basic Script Concepts}. The address expression which may appear in | |
3947 | an output section description sets the VMA (@pxref{Output Section | |
3948 | Address}). | |
3949 | ||
dc0b6aa0 AM |
3950 | The expression @var{lma} that follows the @code{AT} keyword specifies |
3951 | the load address of the section. | |
6bdafbeb NC |
3952 | |
3953 | Alternatively, with @samp{AT>@var{lma_region}} expression, you may | |
3954 | specify a memory region for the section's load address. @xref{MEMORY}. | |
3955 | Note that if the section has not had a VMA assigned to it then the | |
3956 | linker will use the @var{lma_region} as the VMA region as well. | |
dc0b6aa0 AM |
3957 | |
3958 | If neither @code{AT} nor @code{AT>} is specified for an allocatable | |
3959 | section, the linker will set the LMA such that the difference between | |
3960 | VMA and LMA for the section is the same as the preceding output | |
3961 | section in the same region. If there is no preceding output section | |
3962 | or the section is not allocatable, the linker will set the LMA equal | |
3963 | to the VMA. | |
6bdafbeb | 3964 | @xref{Output Section Region}. |
252b5132 RH |
3965 | |
3966 | @cindex ROM initialized data | |
3967 | @cindex initialized data in ROM | |
3968 | This feature is designed to make it easy to build a ROM image. For | |
3969 | example, the following linker script creates three output sections: one | |
3970 | called @samp{.text}, which starts at @code{0x1000}, one called | |
3971 | @samp{.mdata}, which is loaded at the end of the @samp{.text} section | |
3972 | even though its VMA is @code{0x2000}, and one called @samp{.bss} to hold | |
3973 | uninitialized data at address @code{0x3000}. The symbol @code{_data} is | |
3974 | defined with the value @code{0x2000}, which shows that the location | |
3975 | counter holds the VMA value, not the LMA value. | |
3976 | ||
3977 | @smallexample | |
3978 | @group | |
3979 | SECTIONS | |
3980 | @{ | |
3981 | .text 0x1000 : @{ *(.text) _etext = . ; @} | |
a1ab1d2a | 3982 | .mdata 0x2000 : |
252b5132 RH |
3983 | AT ( ADDR (.text) + SIZEOF (.text) ) |
3984 | @{ _data = . ; *(.data); _edata = . ; @} | |
3985 | .bss 0x3000 : | |
3986 | @{ _bstart = . ; *(.bss) *(COMMON) ; _bend = . ;@} | |
3987 | @} | |
3988 | @end group | |
3989 | @end smallexample | |
3990 | ||
3991 | The run-time initialization code for use with a program generated with | |
3992 | this linker script would include something like the following, to copy | |
3993 | the initialized data from the ROM image to its runtime address. Notice | |
3994 | how this code takes advantage of the symbols defined by the linker | |
3995 | script. | |
3996 | ||
3997 | @smallexample | |
3998 | @group | |
3999 | extern char _etext, _data, _edata, _bstart, _bend; | |
4000 | char *src = &_etext; | |
4001 | char *dst = &_data; | |
4002 | ||
4003 | /* ROM has data at end of text; copy it. */ | |
4004 | while (dst < &_edata) @{ | |
4005 | *dst++ = *src++; | |
4006 | @} | |
4007 | ||
4008 | /* Zero bss */ | |
4009 | for (dst = &_bstart; dst< &_bend; dst++) | |
4010 | *dst = 0; | |
4011 | @end group | |
4012 | @end smallexample | |
4013 | ||
bbf115d3 L |
4014 | @node Forced Output Alignment |
4015 | @subsubsection Forced Output Alignment | |
4016 | @kindex ALIGN(@var{section_align}) | |
4017 | @cindex forcing output section alignment | |
4018 | @cindex output section alignment | |
7270c5ed | 4019 | You can increase an output section's alignment by using ALIGN. |
bbf115d3 | 4020 | |
7e7d5768 AM |
4021 | @node Forced Input Alignment |
4022 | @subsubsection Forced Input Alignment | |
4023 | @kindex SUBALIGN(@var{subsection_align}) | |
4024 | @cindex forcing input section alignment | |
4025 | @cindex input section alignment | |
4026 | You can force input section alignment within an output section by using | |
4027 | SUBALIGN. The value specified overrides any alignment given by input | |
4028 | sections, whether larger or smaller. | |
4029 | ||
252b5132 | 4030 | @node Output Section Region |
36f63dca | 4031 | @subsubsection Output Section Region |
252b5132 RH |
4032 | @kindex >@var{region} |
4033 | @cindex section, assigning to memory region | |
4034 | @cindex memory regions and sections | |
4035 | You can assign a section to a previously defined region of memory by | |
4036 | using @samp{>@var{region}}. @xref{MEMORY}. | |
4037 | ||
4038 | Here is a simple example: | |
4039 | @smallexample | |
4040 | @group | |
4041 | MEMORY @{ rom : ORIGIN = 0x1000, LENGTH = 0x1000 @} | |
4042 | SECTIONS @{ ROM : @{ *(.text) @} >rom @} | |
4043 | @end group | |
4044 | @end smallexample | |
4045 | ||
4046 | @node Output Section Phdr | |
36f63dca | 4047 | @subsubsection Output Section Phdr |
252b5132 RH |
4048 | @kindex :@var{phdr} |
4049 | @cindex section, assigning to program header | |
4050 | @cindex program headers and sections | |
4051 | You can assign a section to a previously defined program segment by | |
4052 | using @samp{:@var{phdr}}. @xref{PHDRS}. If a section is assigned to | |
4053 | one or more segments, then all subsequent allocated sections will be | |
4054 | assigned to those segments as well, unless they use an explicitly | |
4055 | @code{:@var{phdr}} modifier. You can use @code{:NONE} to tell the | |
4056 | linker to not put the section in any segment at all. | |
4057 | ||
4058 | Here is a simple example: | |
4059 | @smallexample | |
4060 | @group | |
4061 | PHDRS @{ text PT_LOAD ; @} | |
4062 | SECTIONS @{ .text : @{ *(.text) @} :text @} | |
4063 | @end group | |
4064 | @end smallexample | |
4065 | ||
4066 | @node Output Section Fill | |
36f63dca | 4067 | @subsubsection Output Section Fill |
252b5132 RH |
4068 | @kindex =@var{fillexp} |
4069 | @cindex section fill pattern | |
4070 | @cindex fill pattern, entire section | |
4071 | You can set the fill pattern for an entire section by using | |
4072 | @samp{=@var{fillexp}}. @var{fillexp} is an expression | |
4073 | (@pxref{Expressions}). Any otherwise unspecified regions of memory | |
4074 | within the output section (for example, gaps left due to the required | |
a139d329 AM |
4075 | alignment of input sections) will be filled with the value, repeated as |
4076 | necessary. If the fill expression is a simple hex number, ie. a string | |
9673c93c | 4077 | of hex digit starting with @samp{0x} and without a trailing @samp{k} or @samp{M}, then |
a139d329 AM |
4078 | an arbitrarily long sequence of hex digits can be used to specify the |
4079 | fill pattern; Leading zeros become part of the pattern too. For all | |
9673c93c | 4080 | other cases, including extra parentheses or a unary @code{+}, the fill |
a139d329 AM |
4081 | pattern is the four least significant bytes of the value of the |
4082 | expression. In all cases, the number is big-endian. | |
252b5132 RH |
4083 | |
4084 | You can also change the fill value with a @code{FILL} command in the | |
9673c93c | 4085 | output section commands; (@pxref{Output Section Data}). |
252b5132 RH |
4086 | |
4087 | Here is a simple example: | |
4088 | @smallexample | |
4089 | @group | |
563e308f | 4090 | SECTIONS @{ .text : @{ *(.text) @} =0x90909090 @} |
252b5132 RH |
4091 | @end group |
4092 | @end smallexample | |
4093 | ||
4094 | @node Overlay Description | |
36f63dca | 4095 | @subsection Overlay Description |
252b5132 RH |
4096 | @kindex OVERLAY |
4097 | @cindex overlays | |
4098 | An overlay description provides an easy way to describe sections which | |
4099 | are to be loaded as part of a single memory image but are to be run at | |
4100 | the same memory address. At run time, some sort of overlay manager will | |
4101 | copy the overlaid sections in and out of the runtime memory address as | |
4102 | required, perhaps by simply manipulating addressing bits. This approach | |
4103 | can be useful, for example, when a certain region of memory is faster | |
4104 | than another. | |
4105 | ||
4106 | Overlays are described using the @code{OVERLAY} command. The | |
4107 | @code{OVERLAY} command is used within a @code{SECTIONS} command, like an | |
4108 | output section description. The full syntax of the @code{OVERLAY} | |
4109 | command is as follows: | |
4110 | @smallexample | |
4111 | @group | |
4112 | OVERLAY [@var{start}] : [NOCROSSREFS] [AT ( @var{ldaddr} )] | |
4113 | @{ | |
4114 | @var{secname1} | |
4115 | @{ | |
4116 | @var{output-section-command} | |
4117 | @var{output-section-command} | |
4118 | @dots{} | |
4119 | @} [:@var{phdr}@dots{}] [=@var{fill}] | |
4120 | @var{secname2} | |
4121 | @{ | |
4122 | @var{output-section-command} | |
4123 | @var{output-section-command} | |
4124 | @dots{} | |
4125 | @} [:@var{phdr}@dots{}] [=@var{fill}] | |
4126 | @dots{} | |
4127 | @} [>@var{region}] [:@var{phdr}@dots{}] [=@var{fill}] | |
4128 | @end group | |
4129 | @end smallexample | |
4130 | ||
4131 | Everything is optional except @code{OVERLAY} (a keyword), and each | |
4132 | section must have a name (@var{secname1} and @var{secname2} above). The | |
4133 | section definitions within the @code{OVERLAY} construct are identical to | |
4134 | those within the general @code{SECTIONS} contruct (@pxref{SECTIONS}), | |
4135 | except that no addresses and no memory regions may be defined for | |
4136 | sections within an @code{OVERLAY}. | |
4137 | ||
4138 | The sections are all defined with the same starting address. The load | |
4139 | addresses of the sections are arranged such that they are consecutive in | |
4140 | memory starting at the load address used for the @code{OVERLAY} as a | |
4141 | whole (as with normal section definitions, the load address is optional, | |
4142 | and defaults to the start address; the start address is also optional, | |
4143 | and defaults to the current value of the location counter). | |
4144 | ||
4145 | If the @code{NOCROSSREFS} keyword is used, and there any references | |
4146 | among the sections, the linker will report an error. Since the sections | |
4147 | all run at the same address, it normally does not make sense for one | |
4148 | section to refer directly to another. @xref{Miscellaneous Commands, | |
4149 | NOCROSSREFS}. | |
4150 | ||
4151 | For each section within the @code{OVERLAY}, the linker automatically | |
34711ca3 | 4152 | provides two symbols. The symbol @code{__load_start_@var{secname}} is |
252b5132 RH |
4153 | defined as the starting load address of the section. The symbol |
4154 | @code{__load_stop_@var{secname}} is defined as the final load address of | |
4155 | the section. Any characters within @var{secname} which are not legal | |
4156 | within C identifiers are removed. C (or assembler) code may use these | |
4157 | symbols to move the overlaid sections around as necessary. | |
4158 | ||
4159 | At the end of the overlay, the value of the location counter is set to | |
4160 | the start address of the overlay plus the size of the largest section. | |
4161 | ||
4162 | Here is an example. Remember that this would appear inside a | |
4163 | @code{SECTIONS} construct. | |
4164 | @smallexample | |
4165 | @group | |
4166 | OVERLAY 0x1000 : AT (0x4000) | |
4167 | @{ | |
4168 | .text0 @{ o1/*.o(.text) @} | |
4169 | .text1 @{ o2/*.o(.text) @} | |
4170 | @} | |
4171 | @end group | |
4172 | @end smallexample | |
4173 | @noindent | |
4174 | This will define both @samp{.text0} and @samp{.text1} to start at | |
4175 | address 0x1000. @samp{.text0} will be loaded at address 0x4000, and | |
4176 | @samp{.text1} will be loaded immediately after @samp{.text0}. The | |
34711ca3 | 4177 | following symbols will be defined if referenced: @code{__load_start_text0}, |
252b5132 RH |
4178 | @code{__load_stop_text0}, @code{__load_start_text1}, |
4179 | @code{__load_stop_text1}. | |
4180 | ||
4181 | C code to copy overlay @code{.text1} into the overlay area might look | |
4182 | like the following. | |
4183 | ||
4184 | @smallexample | |
4185 | @group | |
4186 | extern char __load_start_text1, __load_stop_text1; | |
4187 | memcpy ((char *) 0x1000, &__load_start_text1, | |
4188 | &__load_stop_text1 - &__load_start_text1); | |
4189 | @end group | |
4190 | @end smallexample | |
4191 | ||
4192 | Note that the @code{OVERLAY} command is just syntactic sugar, since | |
4193 | everything it does can be done using the more basic commands. The above | |
4194 | example could have been written identically as follows. | |
4195 | ||
4196 | @smallexample | |
4197 | @group | |
4198 | .text0 0x1000 : AT (0x4000) @{ o1/*.o(.text) @} | |
34711ca3 AM |
4199 | PROVIDE (__load_start_text0 = LOADADDR (.text0)); |
4200 | PROVIDE (__load_stop_text0 = LOADADDR (.text0) + SIZEOF (.text0)); | |
252b5132 | 4201 | .text1 0x1000 : AT (0x4000 + SIZEOF (.text0)) @{ o2/*.o(.text) @} |
34711ca3 AM |
4202 | PROVIDE (__load_start_text1 = LOADADDR (.text1)); |
4203 | PROVIDE (__load_stop_text1 = LOADADDR (.text1) + SIZEOF (.text1)); | |
252b5132 RH |
4204 | . = 0x1000 + MAX (SIZEOF (.text0), SIZEOF (.text1)); |
4205 | @end group | |
4206 | @end smallexample | |
4207 | ||
4208 | @node MEMORY | |
36f63dca | 4209 | @section MEMORY Command |
252b5132 RH |
4210 | @kindex MEMORY |
4211 | @cindex memory regions | |
4212 | @cindex regions of memory | |
4213 | @cindex allocating memory | |
4214 | @cindex discontinuous memory | |
4215 | The linker's default configuration permits allocation of all available | |
4216 | memory. You can override this by using the @code{MEMORY} command. | |
4217 | ||
4218 | The @code{MEMORY} command describes the location and size of blocks of | |
4219 | memory in the target. You can use it to describe which memory regions | |
4220 | may be used by the linker, and which memory regions it must avoid. You | |
4221 | can then assign sections to particular memory regions. The linker will | |
4222 | set section addresses based on the memory regions, and will warn about | |
4223 | regions that become too full. The linker will not shuffle sections | |
4224 | around to fit into the available regions. | |
4225 | ||
4226 | A linker script may contain at most one use of the @code{MEMORY} | |
4227 | command. However, you can define as many blocks of memory within it as | |
4228 | you wish. The syntax is: | |
4229 | @smallexample | |
4230 | @group | |
a1ab1d2a | 4231 | MEMORY |
252b5132 RH |
4232 | @{ |
4233 | @var{name} [(@var{attr})] : ORIGIN = @var{origin}, LENGTH = @var{len} | |
4234 | @dots{} | |
4235 | @} | |
4236 | @end group | |
4237 | @end smallexample | |
4238 | ||
4239 | The @var{name} is a name used in the linker script to refer to the | |
4240 | region. The region name has no meaning outside of the linker script. | |
4241 | Region names are stored in a separate name space, and will not conflict | |
4242 | with symbol names, file names, or section names. Each memory region | |
4243 | must have a distinct name. | |
4244 | ||
4245 | @cindex memory region attributes | |
4246 | The @var{attr} string is an optional list of attributes that specify | |
4247 | whether to use a particular memory region for an input section which is | |
4248 | not explicitly mapped in the linker script. As described in | |
4249 | @ref{SECTIONS}, if you do not specify an output section for some input | |
4250 | section, the linker will create an output section with the same name as | |
4251 | the input section. If you define region attributes, the linker will use | |
4252 | them to select the memory region for the output section that it creates. | |
4253 | ||
4254 | The @var{attr} string must consist only of the following characters: | |
4255 | @table @samp | |
4256 | @item R | |
4257 | Read-only section | |
4258 | @item W | |
4259 | Read/write section | |
4260 | @item X | |
4261 | Executable section | |
4262 | @item A | |
4263 | Allocatable section | |
4264 | @item I | |
4265 | Initialized section | |
4266 | @item L | |
4267 | Same as @samp{I} | |
4268 | @item ! | |
4269 | Invert the sense of any of the preceding attributes | |
4270 | @end table | |
4271 | ||
4272 | If a unmapped section matches any of the listed attributes other than | |
4273 | @samp{!}, it will be placed in the memory region. The @samp{!} | |
4274 | attribute reverses this test, so that an unmapped section will be placed | |
4275 | in the memory region only if it does not match any of the listed | |
4276 | attributes. | |
4277 | ||
4278 | @kindex ORIGIN = | |
4279 | @kindex o = | |
4280 | @kindex org = | |
9cd6d51a NC |
4281 | The @var{origin} is an numerical expression for the start address of |
4282 | the memory region. The expression must evaluate to a constant and it | |
4283 | cannot involve any symbols. The keyword @code{ORIGIN} may be | |
4284 | abbreviated to @code{org} or @code{o} (but not, for example, | |
4285 | @code{ORG}). | |
252b5132 RH |
4286 | |
4287 | @kindex LENGTH = | |
4288 | @kindex len = | |
4289 | @kindex l = | |
4290 | The @var{len} is an expression for the size in bytes of the memory | |
4291 | region. As with the @var{origin} expression, the expression must | |
9cd6d51a NC |
4292 | be numerical only and must evaluate to a constant. The keyword |
4293 | @code{LENGTH} may be abbreviated to @code{len} or @code{l}. | |
252b5132 RH |
4294 | |
4295 | In the following example, we specify that there are two memory regions | |
4296 | available for allocation: one starting at @samp{0} for 256 kilobytes, | |
4297 | and the other starting at @samp{0x40000000} for four megabytes. The | |
4298 | linker will place into the @samp{rom} memory region every section which | |
4299 | is not explicitly mapped into a memory region, and is either read-only | |
4300 | or executable. The linker will place other sections which are not | |
4301 | explicitly mapped into a memory region into the @samp{ram} memory | |
4302 | region. | |
4303 | ||
4304 | @smallexample | |
4305 | @group | |
a1ab1d2a | 4306 | MEMORY |
252b5132 RH |
4307 | @{ |
4308 | rom (rx) : ORIGIN = 0, LENGTH = 256K | |
4309 | ram (!rx) : org = 0x40000000, l = 4M | |
4310 | @} | |
4311 | @end group | |
4312 | @end smallexample | |
4313 | ||
4314 | Once you define a memory region, you can direct the linker to place | |
4315 | specific output sections into that memory region by using the | |
4316 | @samp{>@var{region}} output section attribute. For example, if you have | |
4317 | a memory region named @samp{mem}, you would use @samp{>mem} in the | |
4318 | output section definition. @xref{Output Section Region}. If no address | |
4319 | was specified for the output section, the linker will set the address to | |
4320 | the next available address within the memory region. If the combined | |
4321 | output sections directed to a memory region are too large for the | |
4322 | region, the linker will issue an error message. | |
4323 | ||
3ec57632 | 4324 | It is possible to access the origin and length of a memory in an |
c0065db7 | 4325 | expression via the @code{ORIGIN(@var{memory})} and |
3ec57632 NC |
4326 | @code{LENGTH(@var{memory})} functions: |
4327 | ||
4328 | @smallexample | |
4329 | @group | |
c0065db7 | 4330 | _fstack = ORIGIN(ram) + LENGTH(ram) - 4; |
3ec57632 NC |
4331 | @end group |
4332 | @end smallexample | |
4333 | ||
252b5132 RH |
4334 | @node PHDRS |
4335 | @section PHDRS Command | |
4336 | @kindex PHDRS | |
4337 | @cindex program headers | |
4338 | @cindex ELF program headers | |
4339 | @cindex program segments | |
4340 | @cindex segments, ELF | |
4341 | The ELF object file format uses @dfn{program headers}, also knows as | |
4342 | @dfn{segments}. The program headers describe how the program should be | |
4343 | loaded into memory. You can print them out by using the @code{objdump} | |
4344 | program with the @samp{-p} option. | |
4345 | ||
4346 | When you run an ELF program on a native ELF system, the system loader | |
4347 | reads the program headers in order to figure out how to load the | |
4348 | program. This will only work if the program headers are set correctly. | |
4349 | This manual does not describe the details of how the system loader | |
4350 | interprets program headers; for more information, see the ELF ABI. | |
4351 | ||
4352 | The linker will create reasonable program headers by default. However, | |
4353 | in some cases, you may need to specify the program headers more | |
4354 | precisely. You may use the @code{PHDRS} command for this purpose. When | |
4355 | the linker sees the @code{PHDRS} command in the linker script, it will | |
4356 | not create any program headers other than the ones specified. | |
4357 | ||
4358 | The linker only pays attention to the @code{PHDRS} command when | |
4359 | generating an ELF output file. In other cases, the linker will simply | |
4360 | ignore @code{PHDRS}. | |
4361 | ||
4362 | This is the syntax of the @code{PHDRS} command. The words @code{PHDRS}, | |
4363 | @code{FILEHDR}, @code{AT}, and @code{FLAGS} are keywords. | |
4364 | ||
4365 | @smallexample | |
4366 | @group | |
4367 | PHDRS | |
4368 | @{ | |
4369 | @var{name} @var{type} [ FILEHDR ] [ PHDRS ] [ AT ( @var{address} ) ] | |
4370 | [ FLAGS ( @var{flags} ) ] ; | |
4371 | @} | |
4372 | @end group | |
4373 | @end smallexample | |
4374 | ||
4375 | The @var{name} is used only for reference in the @code{SECTIONS} command | |
4376 | of the linker script. It is not put into the output file. Program | |
4377 | header names are stored in a separate name space, and will not conflict | |
4378 | with symbol names, file names, or section names. Each program header | |
4379 | must have a distinct name. | |
4380 | ||
4381 | Certain program header types describe segments of memory which the | |
4382 | system loader will load from the file. In the linker script, you | |
4383 | specify the contents of these segments by placing allocatable output | |
4384 | sections in the segments. You use the @samp{:@var{phdr}} output section | |
4385 | attribute to place a section in a particular segment. @xref{Output | |
4386 | Section Phdr}. | |
4387 | ||
4388 | It is normal to put certain sections in more than one segment. This | |
4389 | merely implies that one segment of memory contains another. You may | |
4390 | repeat @samp{:@var{phdr}}, using it once for each segment which should | |
4391 | contain the section. | |
4392 | ||
4393 | If you place a section in one or more segments using @samp{:@var{phdr}}, | |
4394 | then the linker will place all subsequent allocatable sections which do | |
4395 | not specify @samp{:@var{phdr}} in the same segments. This is for | |
4396 | convenience, since generally a whole set of contiguous sections will be | |
4397 | placed in a single segment. You can use @code{:NONE} to override the | |
4398 | default segment and tell the linker to not put the section in any | |
4399 | segment at all. | |
4400 | ||
4401 | @kindex FILEHDR | |
4402 | @kindex PHDRS | |
4403 | You may use the @code{FILEHDR} and @code{PHDRS} keywords appear after | |
4404 | the program header type to further describe the contents of the segment. | |
4405 | The @code{FILEHDR} keyword means that the segment should include the ELF | |
4406 | file header. The @code{PHDRS} keyword means that the segment should | |
4407 | include the ELF program headers themselves. | |
4408 | ||
4409 | The @var{type} may be one of the following. The numbers indicate the | |
4410 | value of the keyword. | |
4411 | ||
4412 | @table @asis | |
4413 | @item @code{PT_NULL} (0) | |
4414 | Indicates an unused program header. | |
4415 | ||
4416 | @item @code{PT_LOAD} (1) | |
4417 | Indicates that this program header describes a segment to be loaded from | |
4418 | the file. | |
4419 | ||
4420 | @item @code{PT_DYNAMIC} (2) | |
4421 | Indicates a segment where dynamic linking information can be found. | |
4422 | ||
4423 | @item @code{PT_INTERP} (3) | |
4424 | Indicates a segment where the name of the program interpreter may be | |
4425 | found. | |
4426 | ||
4427 | @item @code{PT_NOTE} (4) | |
4428 | Indicates a segment holding note information. | |
4429 | ||
4430 | @item @code{PT_SHLIB} (5) | |
4431 | A reserved program header type, defined but not specified by the ELF | |
4432 | ABI. | |
4433 | ||
4434 | @item @code{PT_PHDR} (6) | |
4435 | Indicates a segment where the program headers may be found. | |
4436 | ||
4437 | @item @var{expression} | |
4438 | An expression giving the numeric type of the program header. This may | |
4439 | be used for types not defined above. | |
4440 | @end table | |
4441 | ||
4442 | You can specify that a segment should be loaded at a particular address | |
4443 | in memory by using an @code{AT} expression. This is identical to the | |
4444 | @code{AT} command used as an output section attribute (@pxref{Output | |
4445 | Section LMA}). The @code{AT} command for a program header overrides the | |
4446 | output section attribute. | |
4447 | ||
4448 | The linker will normally set the segment flags based on the sections | |
4449 | which comprise the segment. You may use the @code{FLAGS} keyword to | |
4450 | explicitly specify the segment flags. The value of @var{flags} must be | |
4451 | an integer. It is used to set the @code{p_flags} field of the program | |
4452 | header. | |
4453 | ||
4454 | Here is an example of @code{PHDRS}. This shows a typical set of program | |
4455 | headers used on a native ELF system. | |
4456 | ||
4457 | @example | |
4458 | @group | |
4459 | PHDRS | |
4460 | @{ | |
4461 | headers PT_PHDR PHDRS ; | |
4462 | interp PT_INTERP ; | |
4463 | text PT_LOAD FILEHDR PHDRS ; | |
4464 | data PT_LOAD ; | |
4465 | dynamic PT_DYNAMIC ; | |
4466 | @} | |
4467 | ||
4468 | SECTIONS | |
4469 | @{ | |
4470 | . = SIZEOF_HEADERS; | |
4471 | .interp : @{ *(.interp) @} :text :interp | |
4472 | .text : @{ *(.text) @} :text | |
4473 | .rodata : @{ *(.rodata) @} /* defaults to :text */ | |
4474 | @dots{} | |
4475 | . = . + 0x1000; /* move to a new page in memory */ | |
4476 | .data : @{ *(.data) @} :data | |
4477 | .dynamic : @{ *(.dynamic) @} :data :dynamic | |
4478 | @dots{} | |
4479 | @} | |
4480 | @end group | |
4481 | @end example | |
4482 | ||
4483 | @node VERSION | |
4484 | @section VERSION Command | |
4485 | @kindex VERSION @{script text@} | |
4486 | @cindex symbol versions | |
4487 | @cindex version script | |
4488 | @cindex versions of symbols | |
4489 | The linker supports symbol versions when using ELF. Symbol versions are | |
4490 | only useful when using shared libraries. The dynamic linker can use | |
4491 | symbol versions to select a specific version of a function when it runs | |
4492 | a program that may have been linked against an earlier version of the | |
4493 | shared library. | |
4494 | ||
4495 | You can include a version script directly in the main linker script, or | |
4496 | you can supply the version script as an implicit linker script. You can | |
4497 | also use the @samp{--version-script} linker option. | |
4498 | ||
4499 | The syntax of the @code{VERSION} command is simply | |
4500 | @smallexample | |
4501 | VERSION @{ version-script-commands @} | |
4502 | @end smallexample | |
4503 | ||
4504 | The format of the version script commands is identical to that used by | |
4505 | Sun's linker in Solaris 2.5. The version script defines a tree of | |
4506 | version nodes. You specify the node names and interdependencies in the | |
4507 | version script. You can specify which symbols are bound to which | |
4508 | version nodes, and you can reduce a specified set of symbols to local | |
4509 | scope so that they are not globally visible outside of the shared | |
4510 | library. | |
4511 | ||
4512 | The easiest way to demonstrate the version script language is with a few | |
4513 | examples. | |
4514 | ||
4515 | @smallexample | |
4516 | VERS_1.1 @{ | |
4517 | global: | |
4518 | foo1; | |
4519 | local: | |
a1ab1d2a UD |
4520 | old*; |
4521 | original*; | |
4522 | new*; | |
252b5132 RH |
4523 | @}; |
4524 | ||
4525 | VERS_1.2 @{ | |
4526 | foo2; | |
4527 | @} VERS_1.1; | |
4528 | ||
4529 | VERS_2.0 @{ | |
4530 | bar1; bar2; | |
c0065db7 | 4531 | extern "C++" @{ |
86043bbb MM |
4532 | ns::*; |
4533 | "int f(int, double)"; | |
c0065db7 | 4534 | @} |
252b5132 RH |
4535 | @} VERS_1.2; |
4536 | @end smallexample | |
4537 | ||
4538 | This example version script defines three version nodes. The first | |
4539 | version node defined is @samp{VERS_1.1}; it has no other dependencies. | |
4540 | The script binds the symbol @samp{foo1} to @samp{VERS_1.1}. It reduces | |
4541 | a number of symbols to local scope so that they are not visible outside | |
313e35ee AM |
4542 | of the shared library; this is done using wildcard patterns, so that any |
4543 | symbol whose name begins with @samp{old}, @samp{original}, or @samp{new} | |
4544 | is matched. The wildcard patterns available are the same as those used | |
4545 | in the shell when matching filenames (also known as ``globbing''). | |
86043bbb MM |
4546 | However, if you specify the symbol name inside double quotes, then the |
4547 | name is treated as literal, rather than as a glob pattern. | |
252b5132 RH |
4548 | |
4549 | Next, the version script defines node @samp{VERS_1.2}. This node | |
4550 | depends upon @samp{VERS_1.1}. The script binds the symbol @samp{foo2} | |
4551 | to the version node @samp{VERS_1.2}. | |
4552 | ||
4553 | Finally, the version script defines node @samp{VERS_2.0}. This node | |
4554 | depends upon @samp{VERS_1.2}. The scripts binds the symbols @samp{bar1} | |
4555 | and @samp{bar2} are bound to the version node @samp{VERS_2.0}. | |
4556 | ||
4557 | When the linker finds a symbol defined in a library which is not | |
4558 | specifically bound to a version node, it will effectively bind it to an | |
4559 | unspecified base version of the library. You can bind all otherwise | |
a981ed6f | 4560 | unspecified symbols to a given version node by using @samp{global: *;} |
252b5132 RH |
4561 | somewhere in the version script. |
4562 | ||
4563 | The names of the version nodes have no specific meaning other than what | |
4564 | they might suggest to the person reading them. The @samp{2.0} version | |
4565 | could just as well have appeared in between @samp{1.1} and @samp{1.2}. | |
4566 | However, this would be a confusing way to write a version script. | |
4567 | ||
0f6bf451 | 4568 | Node name can be omitted, provided it is the only version node |
6b9b879a JJ |
4569 | in the version script. Such version script doesn't assign any versions to |
4570 | symbols, only selects which symbols will be globally visible out and which | |
4571 | won't. | |
4572 | ||
4573 | @smallexample | |
7c9c73be | 4574 | @{ global: foo; bar; local: *; @}; |
9d201f2f | 4575 | @end smallexample |
6b9b879a | 4576 | |
252b5132 RH |
4577 | When you link an application against a shared library that has versioned |
4578 | symbols, the application itself knows which version of each symbol it | |
4579 | requires, and it also knows which version nodes it needs from each | |
4580 | shared library it is linked against. Thus at runtime, the dynamic | |
4581 | loader can make a quick check to make sure that the libraries you have | |
4582 | linked against do in fact supply all of the version nodes that the | |
4583 | application will need to resolve all of the dynamic symbols. In this | |
4584 | way it is possible for the dynamic linker to know with certainty that | |
4585 | all external symbols that it needs will be resolvable without having to | |
4586 | search for each symbol reference. | |
4587 | ||
4588 | The symbol versioning is in effect a much more sophisticated way of | |
4589 | doing minor version checking that SunOS does. The fundamental problem | |
4590 | that is being addressed here is that typically references to external | |
4591 | functions are bound on an as-needed basis, and are not all bound when | |
4592 | the application starts up. If a shared library is out of date, a | |
4593 | required interface may be missing; when the application tries to use | |
4594 | that interface, it may suddenly and unexpectedly fail. With symbol | |
4595 | versioning, the user will get a warning when they start their program if | |
4596 | the libraries being used with the application are too old. | |
4597 | ||
4598 | There are several GNU extensions to Sun's versioning approach. The | |
4599 | first of these is the ability to bind a symbol to a version node in the | |
4600 | source file where the symbol is defined instead of in the versioning | |
4601 | script. This was done mainly to reduce the burden on the library | |
4602 | maintainer. You can do this by putting something like: | |
4603 | @smallexample | |
4604 | __asm__(".symver original_foo,foo@@VERS_1.1"); | |
4605 | @end smallexample | |
4606 | @noindent | |
4607 | in the C source file. This renames the function @samp{original_foo} to | |
4608 | be an alias for @samp{foo} bound to the version node @samp{VERS_1.1}. | |
4609 | The @samp{local:} directive can be used to prevent the symbol | |
96a94295 L |
4610 | @samp{original_foo} from being exported. A @samp{.symver} directive |
4611 | takes precedence over a version script. | |
252b5132 RH |
4612 | |
4613 | The second GNU extension is to allow multiple versions of the same | |
4614 | function to appear in a given shared library. In this way you can make | |
4615 | an incompatible change to an interface without increasing the major | |
4616 | version number of the shared library, while still allowing applications | |
4617 | linked against the old interface to continue to function. | |
4618 | ||
4619 | To do this, you must use multiple @samp{.symver} directives in the | |
4620 | source file. Here is an example: | |
4621 | ||
4622 | @smallexample | |
4623 | __asm__(".symver original_foo,foo@@"); | |
4624 | __asm__(".symver old_foo,foo@@VERS_1.1"); | |
4625 | __asm__(".symver old_foo1,foo@@VERS_1.2"); | |
4626 | __asm__(".symver new_foo,foo@@@@VERS_2.0"); | |
4627 | @end smallexample | |
4628 | ||
4629 | In this example, @samp{foo@@} represents the symbol @samp{foo} bound to the | |
4630 | unspecified base version of the symbol. The source file that contains this | |
4631 | example would define 4 C functions: @samp{original_foo}, @samp{old_foo}, | |
4632 | @samp{old_foo1}, and @samp{new_foo}. | |
4633 | ||
4634 | When you have multiple definitions of a given symbol, there needs to be | |
4635 | some way to specify a default version to which external references to | |
4636 | this symbol will be bound. You can do this with the | |
4637 | @samp{foo@@@@VERS_2.0} type of @samp{.symver} directive. You can only | |
4638 | declare one version of a symbol as the default in this manner; otherwise | |
4639 | you would effectively have multiple definitions of the same symbol. | |
4640 | ||
4641 | If you wish to bind a reference to a specific version of the symbol | |
4642 | within the shared library, you can use the aliases of convenience | |
36f63dca | 4643 | (i.e., @samp{old_foo}), or you can use the @samp{.symver} directive to |
252b5132 RH |
4644 | specifically bind to an external version of the function in question. |
4645 | ||
cb840a31 L |
4646 | You can also specify the language in the version script: |
4647 | ||
4648 | @smallexample | |
4649 | VERSION extern "lang" @{ version-script-commands @} | |
4650 | @end smallexample | |
4651 | ||
c0065db7 | 4652 | The supported @samp{lang}s are @samp{C}, @samp{C++}, and @samp{Java}. |
cb840a31 L |
4653 | The linker will iterate over the list of symbols at the link time and |
4654 | demangle them according to @samp{lang} before matching them to the | |
4655 | patterns specified in @samp{version-script-commands}. | |
4656 | ||
86043bbb MM |
4657 | Demangled names may contains spaces and other special characters. As |
4658 | described above, you can use a glob pattern to match demangled names, | |
4659 | or you can use a double-quoted string to match the string exactly. In | |
4660 | the latter case, be aware that minor differences (such as differing | |
4661 | whitespace) between the version script and the demangler output will | |
4662 | cause a mismatch. As the exact string generated by the demangler | |
4663 | might change in the future, even if the mangled name does not, you | |
4664 | should check that all of your version directives are behaving as you | |
4665 | expect when you upgrade. | |
4666 | ||
252b5132 RH |
4667 | @node Expressions |
4668 | @section Expressions in Linker Scripts | |
4669 | @cindex expressions | |
4670 | @cindex arithmetic | |
4671 | The syntax for expressions in the linker script language is identical to | |
4672 | that of C expressions. All expressions are evaluated as integers. All | |
4673 | expressions are evaluated in the same size, which is 32 bits if both the | |
4674 | host and target are 32 bits, and is otherwise 64 bits. | |
4675 | ||
4676 | You can use and set symbol values in expressions. | |
4677 | ||
4678 | The linker defines several special purpose builtin functions for use in | |
4679 | expressions. | |
4680 | ||
4681 | @menu | |
4682 | * Constants:: Constants | |
4683 | * Symbols:: Symbol Names | |
ecca9871 | 4684 | * Orphan Sections:: Orphan Sections |
252b5132 RH |
4685 | * Location Counter:: The Location Counter |
4686 | * Operators:: Operators | |
4687 | * Evaluation:: Evaluation | |
4688 | * Expression Section:: The Section of an Expression | |
4689 | * Builtin Functions:: Builtin Functions | |
4690 | @end menu | |
4691 | ||
4692 | @node Constants | |
4693 | @subsection Constants | |
4694 | @cindex integer notation | |
4695 | @cindex constants in linker scripts | |
4696 | All constants are integers. | |
4697 | ||
4698 | As in C, the linker considers an integer beginning with @samp{0} to be | |
4699 | octal, and an integer beginning with @samp{0x} or @samp{0X} to be | |
4700 | hexadecimal. The linker considers other integers to be decimal. | |
4701 | ||
4702 | @cindex scaled integers | |
4703 | @cindex K and M integer suffixes | |
4704 | @cindex M and K integer suffixes | |
4705 | @cindex suffixes for integers | |
4706 | @cindex integer suffixes | |
4707 | In addition, you can use the suffixes @code{K} and @code{M} to scale a | |
4708 | constant by | |
4709 | @c TEXI2ROFF-KILL | |
36f63dca | 4710 | @ifnottex |
252b5132 RH |
4711 | @c END TEXI2ROFF-KILL |
4712 | @code{1024} or @code{1024*1024} | |
4713 | @c TEXI2ROFF-KILL | |
36f63dca | 4714 | @end ifnottex |
252b5132 RH |
4715 | @tex |
4716 | ${\rm 1024}$ or ${\rm 1024}^2$ | |
4717 | @end tex | |
4718 | @c END TEXI2ROFF-KILL | |
4719 | respectively. For example, the following all refer to the same quantity: | |
4720 | @smallexample | |
36f63dca NC |
4721 | _fourk_1 = 4K; |
4722 | _fourk_2 = 4096; | |
4723 | _fourk_3 = 0x1000; | |
252b5132 RH |
4724 | @end smallexample |
4725 | ||
4726 | @node Symbols | |
4727 | @subsection Symbol Names | |
4728 | @cindex symbol names | |
4729 | @cindex names | |
4730 | @cindex quoted symbol names | |
4731 | @kindex " | |
4732 | Unless quoted, symbol names start with a letter, underscore, or period | |
4733 | and may include letters, digits, underscores, periods, and hyphens. | |
4734 | Unquoted symbol names must not conflict with any keywords. You can | |
4735 | specify a symbol which contains odd characters or has the same name as a | |
4736 | keyword by surrounding the symbol name in double quotes: | |
4737 | @smallexample | |
36f63dca NC |
4738 | "SECTION" = 9; |
4739 | "with a space" = "also with a space" + 10; | |
252b5132 RH |
4740 | @end smallexample |
4741 | ||
4742 | Since symbols can contain many non-alphabetic characters, it is safest | |
4743 | to delimit symbols with spaces. For example, @samp{A-B} is one symbol, | |
4744 | whereas @samp{A - B} is an expression involving subtraction. | |
4745 | ||
ecca9871 L |
4746 | @node Orphan Sections |
4747 | @subsection Orphan Sections | |
4748 | @cindex orphan | |
4749 | Orphan sections are sections present in the input files which | |
4750 | are not explicitly placed into the output file by the linker | |
4751 | script. The linker will still copy these sections into the | |
4752 | output file, but it has to guess as to where they should be | |
4753 | placed. The linker uses a simple heuristic to do this. It | |
4754 | attempts to place orphan sections after non-orphan sections of the | |
4755 | same attribute, such as code vs data, loadable vs non-loadable, etc. | |
4756 | If there is not enough room to do this then it places | |
4757 | at the end of the file. | |
4758 | ||
4759 | For ELF targets, the attribute of the section includes section type as | |
4760 | well as section flag. | |
4761 | ||
41911f68 | 4762 | If an orphaned section's name is representable as a C identifier then |
a61ca861 | 4763 | the linker will automatically @pxref{PROVIDE} two symbols: |
41911f68 NC |
4764 | __start_SECNAME and __end_SECNAME, where SECNAME is the name of the |
4765 | section. These indicate the start address and end address of the | |
4766 | orphaned section respectively. Note: most section names are not | |
4767 | representable as C identifiers because they contain a @samp{.} | |
4768 | character. | |
4769 | ||
252b5132 RH |
4770 | @node Location Counter |
4771 | @subsection The Location Counter | |
4772 | @kindex . | |
4773 | @cindex dot | |
4774 | @cindex location counter | |
4775 | @cindex current output location | |
4776 | The special linker variable @dfn{dot} @samp{.} always contains the | |
4777 | current output location counter. Since the @code{.} always refers to a | |
4778 | location in an output section, it may only appear in an expression | |
4779 | within a @code{SECTIONS} command. The @code{.} symbol may appear | |
4780 | anywhere that an ordinary symbol is allowed in an expression. | |
4781 | ||
4782 | @cindex holes | |
4783 | Assigning a value to @code{.} will cause the location counter to be | |
4784 | moved. This may be used to create holes in the output section. The | |
dc0b6aa0 AM |
4785 | location counter may not be moved backwards inside an output section, |
4786 | and may not be moved backwards outside of an output section if so | |
4787 | doing creates areas with overlapping LMAs. | |
252b5132 RH |
4788 | |
4789 | @smallexample | |
4790 | SECTIONS | |
4791 | @{ | |
4792 | output : | |
4793 | @{ | |
4794 | file1(.text) | |
4795 | . = . + 1000; | |
4796 | file2(.text) | |
4797 | . += 1000; | |
4798 | file3(.text) | |
563e308f | 4799 | @} = 0x12345678; |
252b5132 RH |
4800 | @} |
4801 | @end smallexample | |
4802 | @noindent | |
4803 | In the previous example, the @samp{.text} section from @file{file1} is | |
4804 | located at the beginning of the output section @samp{output}. It is | |
4805 | followed by a 1000 byte gap. Then the @samp{.text} section from | |
4806 | @file{file2} appears, also with a 1000 byte gap following before the | |
563e308f | 4807 | @samp{.text} section from @file{file3}. The notation @samp{= 0x12345678} |
252b5132 RH |
4808 | specifies what data to write in the gaps (@pxref{Output Section Fill}). |
4809 | ||
5c6bbab8 NC |
4810 | @cindex dot inside sections |
4811 | Note: @code{.} actually refers to the byte offset from the start of the | |
4812 | current containing object. Normally this is the @code{SECTIONS} | |
69da35b5 | 4813 | statement, whose start address is 0, hence @code{.} can be used as an |
5c6bbab8 NC |
4814 | absolute address. If @code{.} is used inside a section description |
4815 | however, it refers to the byte offset from the start of that section, | |
4816 | not an absolute address. Thus in a script like this: | |
4817 | ||
4818 | @smallexample | |
4819 | SECTIONS | |
4820 | @{ | |
4821 | . = 0x100 | |
4822 | .text: @{ | |
4823 | *(.text) | |
4824 | . = 0x200 | |
4825 | @} | |
4826 | . = 0x500 | |
4827 | .data: @{ | |
4828 | *(.data) | |
4829 | . += 0x600 | |
4830 | @} | |
4831 | @} | |
4832 | @end smallexample | |
4833 | ||
4834 | The @samp{.text} section will be assigned a starting address of 0x100 | |
4835 | and a size of exactly 0x200 bytes, even if there is not enough data in | |
4836 | the @samp{.text} input sections to fill this area. (If there is too | |
4837 | much data, an error will be produced because this would be an attempt to | |
4838 | move @code{.} backwards). The @samp{.data} section will start at 0x500 | |
4839 | and it will have an extra 0x600 bytes worth of space after the end of | |
4840 | the values from the @samp{.data} input sections and before the end of | |
4841 | the @samp{.data} output section itself. | |
4842 | ||
b5666f2f AM |
4843 | @cindex dot outside sections |
4844 | Setting symbols to the value of the location counter outside of an | |
4845 | output section statement can result in unexpected values if the linker | |
4846 | needs to place orphan sections. For example, given the following: | |
4847 | ||
4848 | @smallexample | |
4849 | SECTIONS | |
4850 | @{ | |
4851 | start_of_text = . ; | |
4852 | .text: @{ *(.text) @} | |
4853 | end_of_text = . ; | |
4854 | ||
4855 | start_of_data = . ; | |
4856 | .data: @{ *(.data) @} | |
4857 | end_of_data = . ; | |
4858 | @} | |
4859 | @end smallexample | |
4860 | ||
4861 | If the linker needs to place some input section, e.g. @code{.rodata}, | |
4862 | not mentioned in the script, it might choose to place that section | |
4863 | between @code{.text} and @code{.data}. You might think the linker | |
4864 | should place @code{.rodata} on the blank line in the above script, but | |
4865 | blank lines are of no particular significance to the linker. As well, | |
4866 | the linker doesn't associate the above symbol names with their | |
4867 | sections. Instead, it assumes that all assignments or other | |
4868 | statements belong to the previous output section, except for the | |
4869 | special case of an assignment to @code{.}. I.e., the linker will | |
4870 | place the orphan @code{.rodata} section as if the script was written | |
4871 | as follows: | |
4872 | ||
4873 | @smallexample | |
4874 | SECTIONS | |
4875 | @{ | |
4876 | start_of_text = . ; | |
4877 | .text: @{ *(.text) @} | |
4878 | end_of_text = . ; | |
4879 | ||
4880 | start_of_data = . ; | |
4881 | .rodata: @{ *(.rodata) @} | |
4882 | .data: @{ *(.data) @} | |
4883 | end_of_data = . ; | |
4884 | @} | |
4885 | @end smallexample | |
4886 | ||
4887 | This may or may not be the script author's intention for the value of | |
4888 | @code{start_of_data}. One way to influence the orphan section | |
4889 | placement is to assign the location counter to itself, as the linker | |
4890 | assumes that an assignment to @code{.} is setting the start address of | |
4891 | a following output section and thus should be grouped with that | |
4892 | section. So you could write: | |
4893 | ||
4894 | @smallexample | |
4895 | SECTIONS | |
4896 | @{ | |
4897 | start_of_text = . ; | |
4898 | .text: @{ *(.text) @} | |
4899 | end_of_text = . ; | |
4900 | ||
4901 | . = . ; | |
4902 | start_of_data = . ; | |
4903 | .data: @{ *(.data) @} | |
4904 | end_of_data = . ; | |
4905 | @} | |
4906 | @end smallexample | |
4907 | ||
4908 | Now, the orphan @code{.rodata} section will be placed between | |
4909 | @code{end_of_text} and @code{start_of_data}. | |
4910 | ||
252b5132 RH |
4911 | @need 2000 |
4912 | @node Operators | |
4913 | @subsection Operators | |
4914 | @cindex operators for arithmetic | |
4915 | @cindex arithmetic operators | |
4916 | @cindex precedence in expressions | |
4917 | The linker recognizes the standard C set of arithmetic operators, with | |
4918 | the standard bindings and precedence levels: | |
4919 | @c TEXI2ROFF-KILL | |
36f63dca | 4920 | @ifnottex |
252b5132 RH |
4921 | @c END TEXI2ROFF-KILL |
4922 | @smallexample | |
4923 | precedence associativity Operators Notes | |
4924 | (highest) | |
4925 | 1 left ! - ~ (1) | |
4926 | 2 left * / % | |
4927 | 3 left + - | |
4928 | 4 left >> << | |
4929 | 5 left == != > < <= >= | |
4930 | 6 left & | |
4931 | 7 left | | |
4932 | 8 left && | |
4933 | 9 left || | |
4934 | 10 right ? : | |
4935 | 11 right &= += -= *= /= (2) | |
4936 | (lowest) | |
4937 | @end smallexample | |
4938 | Notes: | |
a1ab1d2a | 4939 | (1) Prefix operators |
252b5132 RH |
4940 | (2) @xref{Assignments}. |
4941 | @c TEXI2ROFF-KILL | |
36f63dca | 4942 | @end ifnottex |
252b5132 RH |
4943 | @tex |
4944 | \vskip \baselineskip | |
4945 | %"lispnarrowing" is the extra indent used generally for smallexample | |
4946 | \hskip\lispnarrowing\vbox{\offinterlineskip | |
4947 | \hrule | |
4948 | \halign | |
4949 | {\vrule#&\strut\hfil\ #\ \hfil&\vrule#&\strut\hfil\ #\ \hfil&\vrule#&\strut\hfil\ {\tt #}\ \hfil&\vrule#\cr | |
4950 | height2pt&\omit&&\omit&&\omit&\cr | |
4951 | &Precedence&& Associativity &&{\rm Operators}&\cr | |
4952 | height2pt&\omit&&\omit&&\omit&\cr | |
4953 | \noalign{\hrule} | |
4954 | height2pt&\omit&&\omit&&\omit&\cr | |
4955 | &highest&&&&&\cr | |
4956 | % '176 is tilde, '~' in tt font | |
a1ab1d2a | 4957 | &1&&left&&\qquad- \char'176\ !\qquad\dag&\cr |
252b5132 RH |
4958 | &2&&left&&* / \%&\cr |
4959 | &3&&left&&+ -&\cr | |
4960 | &4&&left&&>> <<&\cr | |
4961 | &5&&left&&== != > < <= >=&\cr | |
4962 | &6&&left&&\&&\cr | |
4963 | &7&&left&&|&\cr | |
4964 | &8&&left&&{\&\&}&\cr | |
4965 | &9&&left&&||&\cr | |
4966 | &10&&right&&? :&\cr | |
4967 | &11&&right&&\qquad\&= += -= *= /=\qquad\ddag&\cr | |
4968 | &lowest&&&&&\cr | |
4969 | height2pt&\omit&&\omit&&\omit&\cr} | |
4970 | \hrule} | |
4971 | @end tex | |
4972 | @iftex | |
4973 | { | |
4974 | @obeylines@parskip=0pt@parindent=0pt | |
4975 | @dag@quad Prefix operators. | |
4976 | @ddag@quad @xref{Assignments}. | |
4977 | } | |
4978 | @end iftex | |
4979 | @c END TEXI2ROFF-KILL | |
4980 | ||
4981 | @node Evaluation | |
4982 | @subsection Evaluation | |
4983 | @cindex lazy evaluation | |
4984 | @cindex expression evaluation order | |
4985 | The linker evaluates expressions lazily. It only computes the value of | |
4986 | an expression when absolutely necessary. | |
4987 | ||
4988 | The linker needs some information, such as the value of the start | |
4989 | address of the first section, and the origins and lengths of memory | |
4990 | regions, in order to do any linking at all. These values are computed | |
4991 | as soon as possible when the linker reads in the linker script. | |
4992 | ||
4993 | However, other values (such as symbol values) are not known or needed | |
4994 | until after storage allocation. Such values are evaluated later, when | |
4995 | other information (such as the sizes of output sections) is available | |
4996 | for use in the symbol assignment expression. | |
4997 | ||
4998 | The sizes of sections cannot be known until after allocation, so | |
4999 | assignments dependent upon these are not performed until after | |
5000 | allocation. | |
5001 | ||
5002 | Some expressions, such as those depending upon the location counter | |
5003 | @samp{.}, must be evaluated during section allocation. | |
5004 | ||
5005 | If the result of an expression is required, but the value is not | |
5006 | available, then an error results. For example, a script like the | |
5007 | following | |
5008 | @smallexample | |
5009 | @group | |
5010 | SECTIONS | |
5011 | @{ | |
a1ab1d2a | 5012 | .text 9+this_isnt_constant : |
252b5132 RH |
5013 | @{ *(.text) @} |
5014 | @} | |
5015 | @end group | |
5016 | @end smallexample | |
5017 | @noindent | |
5018 | will cause the error message @samp{non constant expression for initial | |
5019 | address}. | |
5020 | ||
5021 | @node Expression Section | |
5022 | @subsection The Section of an Expression | |
5023 | @cindex expression sections | |
5024 | @cindex absolute expressions | |
5025 | @cindex relative expressions | |
5026 | @cindex absolute and relocatable symbols | |
5027 | @cindex relocatable and absolute symbols | |
5028 | @cindex symbols, relocatable and absolute | |
5029 | When the linker evaluates an expression, the result is either absolute | |
5030 | or relative to some section. A relative expression is expressed as a | |
5031 | fixed offset from the base of a section. | |
5032 | ||
5033 | The position of the expression within the linker script determines | |
5034 | whether it is absolute or relative. An expression which appears within | |
5035 | an output section definition is relative to the base of the output | |
5036 | section. An expression which appears elsewhere will be absolute. | |
5037 | ||
5038 | A symbol set to a relative expression will be relocatable if you request | |
5039 | relocatable output using the @samp{-r} option. That means that a | |
5040 | further link operation may change the value of the symbol. The symbol's | |
5041 | section will be the section of the relative expression. | |
5042 | ||
5043 | A symbol set to an absolute expression will retain the same value | |
5044 | through any further link operation. The symbol will be absolute, and | |
5045 | will not have any particular associated section. | |
5046 | ||
5047 | You can use the builtin function @code{ABSOLUTE} to force an expression | |
5048 | to be absolute when it would otherwise be relative. For example, to | |
5049 | create an absolute symbol set to the address of the end of the output | |
5050 | section @samp{.data}: | |
5051 | @smallexample | |
5052 | SECTIONS | |
5053 | @{ | |
5054 | .data : @{ *(.data) _edata = ABSOLUTE(.); @} | |
5055 | @} | |
5056 | @end smallexample | |
5057 | @noindent | |
5058 | If @samp{ABSOLUTE} were not used, @samp{_edata} would be relative to the | |
5059 | @samp{.data} section. | |
5060 | ||
5061 | @node Builtin Functions | |
5062 | @subsection Builtin Functions | |
5063 | @cindex functions in expressions | |
5064 | The linker script language includes a number of builtin functions for | |
5065 | use in linker script expressions. | |
5066 | ||
5067 | @table @code | |
5068 | @item ABSOLUTE(@var{exp}) | |
5069 | @kindex ABSOLUTE(@var{exp}) | |
5070 | @cindex expression, absolute | |
5071 | Return the absolute (non-relocatable, as opposed to non-negative) value | |
5072 | of the expression @var{exp}. Primarily useful to assign an absolute | |
5073 | value to a symbol within a section definition, where symbol values are | |
5074 | normally section relative. @xref{Expression Section}. | |
5075 | ||
5076 | @item ADDR(@var{section}) | |
5077 | @kindex ADDR(@var{section}) | |
5078 | @cindex section address in expression | |
5079 | Return the absolute address (the VMA) of the named @var{section}. Your | |
5080 | script must previously have defined the location of that section. In | |
5081 | the following example, @code{symbol_1} and @code{symbol_2} are assigned | |
5082 | identical values: | |
5083 | @smallexample | |
5084 | @group | |
5085 | SECTIONS @{ @dots{} | |
5086 | .output1 : | |
a1ab1d2a | 5087 | @{ |
252b5132 RH |
5088 | start_of_output_1 = ABSOLUTE(.); |
5089 | @dots{} | |
5090 | @} | |
5091 | .output : | |
5092 | @{ | |
5093 | symbol_1 = ADDR(.output1); | |
5094 | symbol_2 = start_of_output_1; | |
5095 | @} | |
5096 | @dots{} @} | |
5097 | @end group | |
5098 | @end smallexample | |
5099 | ||
876f4090 NS |
5100 | @item ALIGN(@var{align}) |
5101 | @itemx ALIGN(@var{exp},@var{align}) | |
5102 | @kindex ALIGN(@var{align}) | |
5103 | @kindex ALIGN(@var{exp},@var{align}) | |
252b5132 RH |
5104 | @cindex round up location counter |
5105 | @cindex align location counter | |
876f4090 NS |
5106 | @cindex round up expression |
5107 | @cindex align expression | |
5108 | Return the location counter (@code{.}) or arbitrary expression aligned | |
5109 | to the next @var{align} boundary. The single operand @code{ALIGN} | |
5110 | doesn't change the value of the location counter---it just does | |
5111 | arithmetic on it. The two operand @code{ALIGN} allows an arbitrary | |
5112 | expression to be aligned upwards (@code{ALIGN(@var{align})} is | |
5113 | equivalent to @code{ALIGN(., @var{align})}). | |
5114 | ||
5115 | Here is an example which aligns the output @code{.data} section to the | |
5116 | next @code{0x2000} byte boundary after the preceding section and sets a | |
5117 | variable within the section to the next @code{0x8000} boundary after the | |
5118 | input sections: | |
252b5132 RH |
5119 | @smallexample |
5120 | @group | |
5121 | SECTIONS @{ @dots{} | |
5122 | .data ALIGN(0x2000): @{ | |
5123 | *(.data) | |
5124 | variable = ALIGN(0x8000); | |
5125 | @} | |
5126 | @dots{} @} | |
5127 | @end group | |
5128 | @end smallexample | |
5129 | @noindent | |
5130 | The first use of @code{ALIGN} in this example specifies the location of | |
5131 | a section because it is used as the optional @var{address} attribute of | |
5132 | a section definition (@pxref{Output Section Address}). The second use | |
5133 | of @code{ALIGN} is used to defines the value of a symbol. | |
5134 | ||
5135 | The builtin function @code{NEXT} is closely related to @code{ALIGN}. | |
5136 | ||
362c1d1a NS |
5137 | @item ALIGNOF(@var{section}) |
5138 | @kindex ALIGNOF(@var{section}) | |
5139 | @cindex section alignment | |
5140 | Return the alignment in bytes of the named @var{section}, if that section has | |
5141 | been allocated. If the section has not been allocated when this is | |
5142 | evaluated, the linker will report an error. In the following example, | |
5143 | the alignment of the @code{.output} section is stored as the first | |
5144 | value in that section. | |
5145 | @smallexample | |
5146 | @group | |
5147 | SECTIONS@{ @dots{} | |
5148 | .output @{ | |
5149 | LONG (ALIGNOF (.output)) | |
5150 | @dots{} | |
5151 | @} | |
5152 | @dots{} @} | |
5153 | @end group | |
5154 | @end smallexample | |
5155 | ||
252b5132 RH |
5156 | @item BLOCK(@var{exp}) |
5157 | @kindex BLOCK(@var{exp}) | |
5158 | This is a synonym for @code{ALIGN}, for compatibility with older linker | |
5159 | scripts. It is most often seen when setting the address of an output | |
5160 | section. | |
5161 | ||
2d20f7bf JJ |
5162 | @item DATA_SEGMENT_ALIGN(@var{maxpagesize}, @var{commonpagesize}) |
5163 | @kindex DATA_SEGMENT_ALIGN(@var{maxpagesize}, @var{commonpagesize}) | |
5164 | This is equivalent to either | |
5165 | @smallexample | |
5166 | (ALIGN(@var{maxpagesize}) + (. & (@var{maxpagesize} - 1))) | |
5167 | @end smallexample | |
5168 | or | |
5169 | @smallexample | |
5170 | (ALIGN(@var{maxpagesize}) + (. & (@var{maxpagesize} - @var{commonpagesize}))) | |
5171 | @end smallexample | |
5172 | @noindent | |
5173 | depending on whether the latter uses fewer @var{commonpagesize} sized pages | |
5174 | for the data segment (area between the result of this expression and | |
5175 | @code{DATA_SEGMENT_END}) than the former or not. | |
5176 | If the latter form is used, it means @var{commonpagesize} bytes of runtime | |
5177 | memory will be saved at the expense of up to @var{commonpagesize} wasted | |
5178 | bytes in the on-disk file. | |
5179 | ||
5180 | This expression can only be used directly in @code{SECTIONS} commands, not in | |
5181 | any output section descriptions and only once in the linker script. | |
5182 | @var{commonpagesize} should be less or equal to @var{maxpagesize} and should | |
5183 | be the system page size the object wants to be optimized for (while still | |
5184 | working on system page sizes up to @var{maxpagesize}). | |
5185 | ||
5186 | @noindent | |
5187 | Example: | |
5188 | @smallexample | |
5189 | . = DATA_SEGMENT_ALIGN(0x10000, 0x2000); | |
5190 | @end smallexample | |
5191 | ||
5192 | @item DATA_SEGMENT_END(@var{exp}) | |
5193 | @kindex DATA_SEGMENT_END(@var{exp}) | |
5194 | This defines the end of data segment for @code{DATA_SEGMENT_ALIGN} | |
5195 | evaluation purposes. | |
5196 | ||
5197 | @smallexample | |
5198 | . = DATA_SEGMENT_END(.); | |
5199 | @end smallexample | |
5200 | ||
a4f5ad88 JJ |
5201 | @item DATA_SEGMENT_RELRO_END(@var{offset}, @var{exp}) |
5202 | @kindex DATA_SEGMENT_RELRO_END(@var{offset}, @var{exp}) | |
5203 | This defines the end of the @code{PT_GNU_RELRO} segment when | |
5204 | @samp{-z relro} option is used. Second argument is returned. | |
5205 | When @samp{-z relro} option is not present, @code{DATA_SEGMENT_RELRO_END} | |
5206 | does nothing, otherwise @code{DATA_SEGMENT_ALIGN} is padded so that | |
5207 | @var{exp} + @var{offset} is aligned to the most commonly used page | |
5208 | boundary for particular target. If present in the linker script, | |
5209 | it must always come in between @code{DATA_SEGMENT_ALIGN} and | |
5210 | @code{DATA_SEGMENT_END}. | |
5211 | ||
5212 | @smallexample | |
5213 | . = DATA_SEGMENT_RELRO_END(24, .); | |
5214 | @end smallexample | |
5215 | ||
252b5132 RH |
5216 | @item DEFINED(@var{symbol}) |
5217 | @kindex DEFINED(@var{symbol}) | |
5218 | @cindex symbol defaults | |
5219 | Return 1 if @var{symbol} is in the linker global symbol table and is | |
420e579c HPN |
5220 | defined before the statement using DEFINED in the script, otherwise |
5221 | return 0. You can use this function to provide | |
252b5132 RH |
5222 | default values for symbols. For example, the following script fragment |
5223 | shows how to set a global symbol @samp{begin} to the first location in | |
5224 | the @samp{.text} section---but if a symbol called @samp{begin} already | |
5225 | existed, its value is preserved: | |
5226 | ||
5227 | @smallexample | |
5228 | @group | |
5229 | SECTIONS @{ @dots{} | |
5230 | .text : @{ | |
5231 | begin = DEFINED(begin) ? begin : . ; | |
5232 | @dots{} | |
5233 | @} | |
5234 | @dots{} | |
5235 | @} | |
5236 | @end group | |
5237 | @end smallexample | |
5238 | ||
3ec57632 NC |
5239 | @item LENGTH(@var{memory}) |
5240 | @kindex LENGTH(@var{memory}) | |
5241 | Return the length of the memory region named @var{memory}. | |
5242 | ||
252b5132 RH |
5243 | @item LOADADDR(@var{section}) |
5244 | @kindex LOADADDR(@var{section}) | |
5245 | @cindex section load address in expression | |
5246 | Return the absolute LMA of the named @var{section}. This is normally | |
5247 | the same as @code{ADDR}, but it may be different if the @code{AT} | |
5248 | attribute is used in the output section definition (@pxref{Output | |
5249 | Section LMA}). | |
5250 | ||
5251 | @kindex MAX | |
5252 | @item MAX(@var{exp1}, @var{exp2}) | |
5253 | Returns the maximum of @var{exp1} and @var{exp2}. | |
5254 | ||
5255 | @kindex MIN | |
5256 | @item MIN(@var{exp1}, @var{exp2}) | |
5257 | Returns the minimum of @var{exp1} and @var{exp2}. | |
5258 | ||
5259 | @item NEXT(@var{exp}) | |
5260 | @kindex NEXT(@var{exp}) | |
5261 | @cindex unallocated address, next | |
5262 | Return the next unallocated address that is a multiple of @var{exp}. | |
5263 | This function is closely related to @code{ALIGN(@var{exp})}; unless you | |
5264 | use the @code{MEMORY} command to define discontinuous memory for the | |
5265 | output file, the two functions are equivalent. | |
5266 | ||
3ec57632 NC |
5267 | @item ORIGIN(@var{memory}) |
5268 | @kindex ORIGIN(@var{memory}) | |
5269 | Return the origin of the memory region named @var{memory}. | |
5270 | ||
ba916c8a MM |
5271 | @item SEGMENT_START(@var{segment}, @var{default}) |
5272 | @kindex SEGMENT_START(@var{segment}, @var{default}) | |
5273 | Return the base address of the named @var{segment}. If an explicit | |
5274 | value has been given for this segment (with a command-line @samp{-T} | |
5275 | option) that value will be returned; otherwise the value will be | |
5276 | @var{default}. At present, the @samp{-T} command-line option can only | |
5277 | be used to set the base address for the ``text'', ``data'', and | |
5278 | ``bss'' sections, but you use @code{SEGMENT_START} with any segment | |
5279 | name. | |
5280 | ||
252b5132 RH |
5281 | @item SIZEOF(@var{section}) |
5282 | @kindex SIZEOF(@var{section}) | |
5283 | @cindex section size | |
5284 | Return the size in bytes of the named @var{section}, if that section has | |
5285 | been allocated. If the section has not been allocated when this is | |
5286 | evaluated, the linker will report an error. In the following example, | |
5287 | @code{symbol_1} and @code{symbol_2} are assigned identical values: | |
5288 | @smallexample | |
5289 | @group | |
5290 | SECTIONS@{ @dots{} | |
5291 | .output @{ | |
5292 | .start = . ; | |
5293 | @dots{} | |
5294 | .end = . ; | |
5295 | @} | |
5296 | symbol_1 = .end - .start ; | |
5297 | symbol_2 = SIZEOF(.output); | |
5298 | @dots{} @} | |
5299 | @end group | |
5300 | @end smallexample | |
5301 | ||
5302 | @item SIZEOF_HEADERS | |
5303 | @itemx sizeof_headers | |
5304 | @kindex SIZEOF_HEADERS | |
5305 | @cindex header size | |
5306 | Return the size in bytes of the output file's headers. This is | |
5307 | information which appears at the start of the output file. You can use | |
5308 | this number when setting the start address of the first section, if you | |
5309 | choose, to facilitate paging. | |
5310 | ||
5311 | @cindex not enough room for program headers | |
5312 | @cindex program headers, not enough room | |
5313 | When producing an ELF output file, if the linker script uses the | |
5314 | @code{SIZEOF_HEADERS} builtin function, the linker must compute the | |
5315 | number of program headers before it has determined all the section | |
5316 | addresses and sizes. If the linker later discovers that it needs | |
5317 | additional program headers, it will report an error @samp{not enough | |
5318 | room for program headers}. To avoid this error, you must avoid using | |
5319 | the @code{SIZEOF_HEADERS} function, or you must rework your linker | |
5320 | script to avoid forcing the linker to use additional program headers, or | |
5321 | you must define the program headers yourself using the @code{PHDRS} | |
5322 | command (@pxref{PHDRS}). | |
5323 | @end table | |
5324 | ||
5325 | @node Implicit Linker Scripts | |
5326 | @section Implicit Linker Scripts | |
5327 | @cindex implicit linker scripts | |
5328 | If you specify a linker input file which the linker can not recognize as | |
5329 | an object file or an archive file, it will try to read the file as a | |
5330 | linker script. If the file can not be parsed as a linker script, the | |
5331 | linker will report an error. | |
5332 | ||
5333 | An implicit linker script will not replace the default linker script. | |
5334 | ||
5335 | Typically an implicit linker script would contain only symbol | |
5336 | assignments, or the @code{INPUT}, @code{GROUP}, or @code{VERSION} | |
5337 | commands. | |
5338 | ||
5339 | Any input files read because of an implicit linker script will be read | |
5340 | at the position in the command line where the implicit linker script was | |
5341 | read. This can affect archive searching. | |
5342 | ||
5343 | @ifset GENERIC | |
5344 | @node Machine Dependent | |
5345 | @chapter Machine Dependent Features | |
5346 | ||
5347 | @cindex machine dependencies | |
ff5dcc92 SC |
5348 | @command{ld} has additional features on some platforms; the following |
5349 | sections describe them. Machines where @command{ld} has no additional | |
252b5132 RH |
5350 | functionality are not listed. |
5351 | ||
5352 | @menu | |
36f63dca NC |
5353 | @ifset H8300 |
5354 | * H8/300:: @command{ld} and the H8/300 | |
5355 | @end ifset | |
5356 | @ifset I960 | |
5357 | * i960:: @command{ld} and the Intel 960 family | |
5358 | @end ifset | |
5359 | @ifset ARM | |
5360 | * ARM:: @command{ld} and the ARM family | |
5361 | @end ifset | |
5362 | @ifset HPPA | |
5363 | * HPPA ELF32:: @command{ld} and HPPA 32-bit ELF | |
5364 | @end ifset | |
7fb9f789 NC |
5365 | @ifset M68K |
5366 | * M68K:: @command{ld} and the Motorola 68K family | |
5367 | @end ifset | |
3c3bdf30 | 5368 | @ifset MMIX |
36f63dca | 5369 | * MMIX:: @command{ld} and MMIX |
3c3bdf30 | 5370 | @end ifset |
2469cfa2 | 5371 | @ifset MSP430 |
36f63dca | 5372 | * MSP430:: @command{ld} and MSP430 |
2469cfa2 | 5373 | @end ifset |
93fd0973 SC |
5374 | @ifset M68HC11 |
5375 | * M68HC11/68HC12:: @code{ld} and the Motorola 68HC11 and 68HC12 families | |
5376 | @end ifset | |
2a60a7a8 AM |
5377 | @ifset POWERPC |
5378 | * PowerPC ELF32:: @command{ld} and PowerPC 32-bit ELF Support | |
5379 | @end ifset | |
5380 | @ifset POWERPC64 | |
5381 | * PowerPC64 ELF64:: @command{ld} and PowerPC64 64-bit ELF Support | |
5382 | @end ifset | |
49fa1e15 AM |
5383 | @ifset SPU |
5384 | * SPU ELF:: @command{ld} and SPU ELF Support | |
5385 | @end ifset | |
74459f0e | 5386 | @ifset TICOFF |
ff5dcc92 | 5387 | * TI COFF:: @command{ld} and TI COFF |
74459f0e | 5388 | @end ifset |
2ca22b03 NC |
5389 | @ifset WIN32 |
5390 | * WIN32:: @command{ld} and WIN32 (cygwin/mingw) | |
5391 | @end ifset | |
e0001a05 NC |
5392 | @ifset XTENSA |
5393 | * Xtensa:: @command{ld} and Xtensa Processors | |
5394 | @end ifset | |
252b5132 RH |
5395 | @end menu |
5396 | @end ifset | |
5397 | ||
252b5132 RH |
5398 | @ifset H8300 |
5399 | @ifclear GENERIC | |
5400 | @raisesections | |
5401 | @end ifclear | |
5402 | ||
5403 | @node H8/300 | |
ff5dcc92 | 5404 | @section @command{ld} and the H8/300 |
252b5132 RH |
5405 | |
5406 | @cindex H8/300 support | |
ff5dcc92 | 5407 | For the H8/300, @command{ld} can perform these global optimizations when |
252b5132 RH |
5408 | you specify the @samp{--relax} command-line option. |
5409 | ||
5410 | @table @emph | |
5411 | @cindex relaxing on H8/300 | |
5412 | @item relaxing address modes | |
ff5dcc92 | 5413 | @command{ld} finds all @code{jsr} and @code{jmp} instructions whose |
252b5132 RH |
5414 | targets are within eight bits, and turns them into eight-bit |
5415 | program-counter relative @code{bsr} and @code{bra} instructions, | |
5416 | respectively. | |
5417 | ||
5418 | @cindex synthesizing on H8/300 | |
5419 | @item synthesizing instructions | |
5420 | @c FIXME: specifically mov.b, or any mov instructions really? | |
ff5dcc92 | 5421 | @command{ld} finds all @code{mov.b} instructions which use the |
252b5132 RH |
5422 | sixteen-bit absolute address form, but refer to the top |
5423 | page of memory, and changes them to use the eight-bit address form. | |
5424 | (That is: the linker turns @samp{mov.b @code{@@}@var{aa}:16} into | |
5425 | @samp{mov.b @code{@@}@var{aa}:8} whenever the address @var{aa} is in the | |
5426 | top page of memory). | |
1502569c NC |
5427 | |
5428 | @item bit manipulation instructions | |
c0065db7 | 5429 | @command{ld} finds all bit manipulation instructions like @code{band, bclr, |
1502569c | 5430 | biand, bild, bior, bist, bixor, bld, bnot, bor, bset, bst, btst, bxor} |
c0065db7 | 5431 | which use 32 bit and 16 bit absolute address form, but refer to the top |
1502569c NC |
5432 | page of memory, and changes them to use the 8 bit address form. |
5433 | (That is: the linker turns @samp{bset #xx:3,@code{@@}@var{aa}:32} into | |
c0065db7 | 5434 | @samp{bset #xx:3,@code{@@}@var{aa}:8} whenever the address @var{aa} is in |
1502569c NC |
5435 | the top page of memory). |
5436 | ||
5437 | @item system control instructions | |
c0065db7 RM |
5438 | @command{ld} finds all @code{ldc.w, stc.w} instructions which use the |
5439 | 32 bit absolute address form, but refer to the top page of memory, and | |
1502569c NC |
5440 | changes them to use 16 bit address form. |
5441 | (That is: the linker turns @samp{ldc.w @code{@@}@var{aa}:32,ccr} into | |
c0065db7 | 5442 | @samp{ldc.w @code{@@}@var{aa}:16,ccr} whenever the address @var{aa} is in |
1502569c | 5443 | the top page of memory). |
252b5132 RH |
5444 | @end table |
5445 | ||
5446 | @ifclear GENERIC | |
5447 | @lowersections | |
5448 | @end ifclear | |
5449 | @end ifset | |
5450 | ||
36f63dca | 5451 | @ifclear GENERIC |
c2dcd04e | 5452 | @ifset Renesas |
36f63dca | 5453 | @c This stuff is pointless to say unless you're especially concerned |
c2dcd04e NC |
5454 | @c with Renesas chips; don't enable it for generic case, please. |
5455 | @node Renesas | |
5456 | @chapter @command{ld} and Other Renesas Chips | |
36f63dca | 5457 | |
c2dcd04e NC |
5458 | @command{ld} also supports the Renesas (formerly Hitachi) H8/300H, |
5459 | H8/500, and SH chips. No special features, commands, or command-line | |
5460 | options are required for these chips. | |
36f63dca NC |
5461 | @end ifset |
5462 | @end ifclear | |
5463 | ||
5464 | @ifset I960 | |
5465 | @ifclear GENERIC | |
5466 | @raisesections | |
5467 | @end ifclear | |
5468 | ||
5469 | @node i960 | |
5470 | @section @command{ld} and the Intel 960 Family | |
5471 | ||
5472 | @cindex i960 support | |
5473 | ||
5474 | You can use the @samp{-A@var{architecture}} command line option to | |
5475 | specify one of the two-letter names identifying members of the 960 | |
5476 | family; the option specifies the desired output target, and warns of any | |
5477 | incompatible instructions in the input files. It also modifies the | |
5478 | linker's search strategy for archive libraries, to support the use of | |
5479 | libraries specific to each particular architecture, by including in the | |
5480 | search loop names suffixed with the string identifying the architecture. | |
5481 | ||
5482 | For example, if your @command{ld} command line included @w{@samp{-ACA}} as | |
5483 | well as @w{@samp{-ltry}}, the linker would look (in its built-in search | |
5484 | paths, and in any paths you specify with @samp{-L}) for a library with | |
5485 | the names | |
5486 | ||
5487 | @smallexample | |
5488 | @group | |
5489 | try | |
5490 | libtry.a | |
5491 | tryca | |
5492 | libtryca.a | |
5493 | @end group | |
5494 | @end smallexample | |
5495 | ||
5496 | @noindent | |
5497 | The first two possibilities would be considered in any event; the last | |
5498 | two are due to the use of @w{@samp{-ACA}}. | |
5499 | ||
5500 | You can meaningfully use @samp{-A} more than once on a command line, since | |
5501 | the 960 architecture family allows combination of target architectures; each | |
5502 | use will add another pair of name variants to search for when @w{@samp{-l}} | |
5503 | specifies a library. | |
5504 | ||
5505 | @cindex @option{--relax} on i960 | |
5506 | @cindex relaxing on i960 | |
5507 | @command{ld} supports the @samp{--relax} option for the i960 family. If | |
5508 | you specify @samp{--relax}, @command{ld} finds all @code{balx} and | |
5509 | @code{calx} instructions whose targets are within 24 bits, and turns | |
5510 | them into 24-bit program-counter relative @code{bal} and @code{cal} | |
5511 | instructions, respectively. @command{ld} also turns @code{cal} | |
5512 | instructions into @code{bal} instructions when it determines that the | |
5513 | target subroutine is a leaf routine (that is, the target subroutine does | |
5514 | not itself call any subroutines). | |
5515 | ||
5516 | @ifclear GENERIC | |
5517 | @lowersections | |
5518 | @end ifclear | |
5519 | @end ifset | |
5520 | ||
5521 | @ifset ARM | |
5522 | @ifclear GENERIC | |
5523 | @raisesections | |
5524 | @end ifclear | |
5525 | ||
93fd0973 SC |
5526 | @ifset M68HC11 |
5527 | @ifclear GENERIC | |
5528 | @raisesections | |
5529 | @end ifclear | |
5530 | ||
5531 | @node M68HC11/68HC12 | |
5532 | @section @command{ld} and the Motorola 68HC11 and 68HC12 families | |
5533 | ||
5534 | @cindex M68HC11 and 68HC12 support | |
5535 | ||
5536 | @subsection Linker Relaxation | |
5537 | ||
5538 | For the Motorola 68HC11, @command{ld} can perform these global | |
5539 | optimizations when you specify the @samp{--relax} command-line option. | |
5540 | ||
5541 | @table @emph | |
5542 | @cindex relaxing on M68HC11 | |
5543 | @item relaxing address modes | |
5544 | @command{ld} finds all @code{jsr} and @code{jmp} instructions whose | |
5545 | targets are within eight bits, and turns them into eight-bit | |
5546 | program-counter relative @code{bsr} and @code{bra} instructions, | |
5547 | respectively. | |
5548 | ||
5549 | @command{ld} also looks at all 16-bit extended addressing modes and | |
5550 | transforms them in a direct addressing mode when the address is in | |
5551 | page 0 (between 0 and 0x0ff). | |
5552 | ||
5553 | @item relaxing gcc instruction group | |
5554 | When @command{gcc} is called with @option{-mrelax}, it can emit group | |
5555 | of instructions that the linker can optimize to use a 68HC11 direct | |
5556 | addressing mode. These instructions consists of @code{bclr} or | |
5557 | @code{bset} instructions. | |
5558 | ||
5559 | @end table | |
5560 | ||
5561 | @subsection Trampoline Generation | |
5562 | ||
5563 | @cindex trampoline generation on M68HC11 | |
5564 | @cindex trampoline generation on M68HC12 | |
5565 | For 68HC11 and 68HC12, @command{ld} can generate trampoline code to | |
5566 | call a far function using a normal @code{jsr} instruction. The linker | |
c0065db7 | 5567 | will also change the relocation to some far function to use the |
93fd0973 SC |
5568 | trampoline address instead of the function address. This is typically the |
5569 | case when a pointer to a function is taken. The pointer will in fact | |
5570 | point to the function trampoline. | |
5571 | ||
5572 | @ifclear GENERIC | |
5573 | @lowersections | |
5574 | @end ifclear | |
5575 | @end ifset | |
5576 | ||
36f63dca | 5577 | @node ARM |
3674e28a | 5578 | @section @command{ld} and the ARM family |
36f63dca NC |
5579 | |
5580 | @cindex ARM interworking support | |
5581 | @kindex --support-old-code | |
5582 | For the ARM, @command{ld} will generate code stubs to allow functions calls | |
b45619c0 | 5583 | between ARM and Thumb code. These stubs only work with code that has |
36f63dca NC |
5584 | been compiled and assembled with the @samp{-mthumb-interwork} command |
5585 | line option. If it is necessary to link with old ARM object files or | |
5586 | libraries, which have not been compiled with the -mthumb-interwork | |
5587 | option then the @samp{--support-old-code} command line switch should be | |
5588 | given to the linker. This will make it generate larger stub functions | |
5589 | which will work with non-interworking aware ARM code. Note, however, | |
5590 | the linker does not support generating stubs for function calls to | |
5591 | non-interworking aware Thumb code. | |
5592 | ||
5593 | @cindex thumb entry point | |
5594 | @cindex entry point, thumb | |
5595 | @kindex --thumb-entry=@var{entry} | |
5596 | The @samp{--thumb-entry} switch is a duplicate of the generic | |
5597 | @samp{--entry} switch, in that it sets the program's starting address. | |
5598 | But it also sets the bottom bit of the address, so that it can be | |
5599 | branched to using a BX instruction, and the program will start | |
5600 | executing in Thumb mode straight away. | |
5601 | ||
e489d0ae PB |
5602 | @cindex BE8 |
5603 | @kindex --be8 | |
5604 | The @samp{--be8} switch instructs @command{ld} to generate BE8 format | |
5605 | executables. This option is only valid when linking big-endian objects. | |
5606 | The resulting image will contain big-endian data and little-endian code. | |
5607 | ||
3674e28a PB |
5608 | @cindex TARGET1 |
5609 | @kindex --target1-rel | |
5610 | @kindex --target1-abs | |
5611 | The @samp{R_ARM_TARGET1} relocation is typically used for entries in the | |
5612 | @samp{.init_array} section. It is interpreted as either @samp{R_ARM_REL32} | |
5613 | or @samp{R_ARM_ABS32}, depending on the target. The @samp{--target1-rel} | |
5614 | and @samp{--target1-abs} switches override the default. | |
5615 | ||
5616 | @cindex TARGET2 | |
5617 | @kindex --target2=@var{type} | |
5618 | The @samp{--target2=type} switch overrides the default definition of the | |
5619 | @samp{R_ARM_TARGET2} relocation. Valid values for @samp{type}, their | |
5620 | meanings, and target defaults are as follows: | |
5621 | @table @samp | |
5622 | @item rel | |
eeac373a PB |
5623 | @samp{R_ARM_REL32} (arm*-*-elf, arm*-*-eabi) |
5624 | @item abs | |
5625 | @samp{R_ARM_ABS32} (arm*-*-symbianelf) | |
3674e28a PB |
5626 | @item got-rel |
5627 | @samp{R_ARM_GOT_PREL} (arm*-*-linux, arm*-*-*bsd) | |
5628 | @end table | |
5629 | ||
319850b4 JB |
5630 | @cindex FIX_V4BX |
5631 | @kindex --fix-v4bx | |
5632 | The @samp{R_ARM_V4BX} relocation (defined by the ARM AAELF | |
5633 | specification) enables objects compiled for the ARMv4 architecture to be | |
5634 | interworking-safe when linked with other objects compiled for ARMv4t, but | |
5635 | also allows pure ARMv4 binaries to be built from the same ARMv4 objects. | |
5636 | ||
5637 | In the latter case, the switch @option{--fix-v4bx} must be passed to the | |
5638 | linker, which causes v4t @code{BX rM} instructions to be rewritten as | |
5639 | @code{MOV PC,rM}, since v4 processors do not have a @code{BX} instruction. | |
5640 | ||
5641 | In the former case, the switch should not be used, and @samp{R_ARM_V4BX} | |
5642 | relocations are ignored. | |
5643 | ||
845b51d6 PB |
5644 | @cindex FIX_V4BX_INTERWORKING |
5645 | @kindex --fix-v4bx-interworking | |
5646 | Replace @code{BX rM} instructions identified by @samp{R_ARM_V4BX} | |
5647 | relocations with a branch to the following veneer: | |
5648 | ||
5649 | @smallexample | |
5650 | TST rM, #1 | |
5651 | MOVEQ PC, rM | |
5652 | BX Rn | |
5653 | @end smallexample | |
5654 | ||
5655 | This allows generation of libraries/applications that work on ARMv4 cores | |
5656 | and are still interworking safe. Note that the above veneer clobbers the | |
5657 | condition flags, so may cause incorrect progrm behavior in rare cases. | |
5658 | ||
33bfe774 JB |
5659 | @cindex USE_BLX |
5660 | @kindex --use-blx | |
5661 | The @samp{--use-blx} switch enables the linker to use ARM/Thumb | |
5662 | BLX instructions (available on ARMv5t and above) in various | |
5663 | situations. Currently it is used to perform calls via the PLT from Thumb | |
5664 | code using BLX rather than using BX and a mode-switching stub before | |
5665 | each PLT entry. This should lead to such calls executing slightly faster. | |
5666 | ||
5667 | This option is enabled implicitly for SymbianOS, so there is no need to | |
5668 | specify it if you are using that target. | |
5669 | ||
c6dd86c6 JB |
5670 | @cindex VFP11_DENORM_FIX |
5671 | @kindex --vfp11-denorm-fix | |
5672 | The @samp{--vfp11-denorm-fix} switch enables a link-time workaround for a | |
5673 | bug in certain VFP11 coprocessor hardware, which sometimes allows | |
5674 | instructions with denorm operands (which must be handled by support code) | |
5675 | to have those operands overwritten by subsequent instructions before | |
5676 | the support code can read the intended values. | |
5677 | ||
5678 | The bug may be avoided in scalar mode if you allow at least one | |
5679 | intervening instruction between a VFP11 instruction which uses a register | |
5680 | and another instruction which writes to the same register, or at least two | |
5681 | intervening instructions if vector mode is in use. The bug only affects | |
5682 | full-compliance floating-point mode: you do not need this workaround if | |
5683 | you are using "runfast" mode. Please contact ARM for further details. | |
5684 | ||
5685 | If you know you are using buggy VFP11 hardware, you can | |
5686 | enable this workaround by specifying the linker option | |
5687 | @samp{--vfp-denorm-fix=scalar} if you are using the VFP11 scalar | |
5688 | mode only, or @samp{--vfp-denorm-fix=vector} if you are using | |
5689 | vector mode (the latter also works for scalar code). The default is | |
5690 | @samp{--vfp-denorm-fix=none}. | |
5691 | ||
5692 | If the workaround is enabled, instructions are scanned for | |
5693 | potentially-troublesome sequences, and a veneer is created for each | |
5694 | such sequence which may trigger the erratum. The veneer consists of the | |
5695 | first instruction of the sequence and a branch back to the subsequent | |
5696 | instruction. The original instruction is then replaced with a branch to | |
5697 | the veneer. The extra cycles required to call and return from the veneer | |
5698 | are sufficient to avoid the erratum in both the scalar and vector cases. | |
5699 | ||
bf21ed78 MS |
5700 | @cindex NO_ENUM_SIZE_WARNING |
5701 | @kindex --no-enum-size-warning | |
726150b7 | 5702 | The @option{--no-enum-size-warning} switch prevents the linker from |
bf21ed78 MS |
5703 | warning when linking object files that specify incompatible EABI |
5704 | enumeration size attributes. For example, with this switch enabled, | |
5705 | linking of an object file using 32-bit enumeration values with another | |
5706 | using enumeration values fitted into the smallest possible space will | |
5707 | not be diagnosed. | |
5708 | ||
726150b7 NC |
5709 | @cindex PIC_VENEER |
5710 | @kindex --pic-veneer | |
5711 | The @samp{--pic-veneer} switch makes the linker use PIC sequences for | |
5712 | ARM/Thumb interworking veneers, even if the rest of the binary | |
5713 | is not PIC. This avoids problems on uClinux targets where | |
5714 | @samp{--emit-relocs} is used to generate relocatable binaries. | |
5715 | ||
5716 | @cindex STUB_GROUP_SIZE | |
5717 | @kindex --stub-group-size=@var{N} | |
5718 | The linker will automatically generate and insert small sequences of | |
5719 | code into a linked ARM ELF executable whenever an attempt is made to | |
5720 | perform a function call to a symbol that is too far away. The | |
5721 | placement of these sequences of instructions - called stubs - is | |
5722 | controlled by the command line option @option{--stub-group-size=N}. | |
5723 | The placement is important because a poor choice can create a need for | |
5724 | duplicate stubs, increasing the code sizw. The linker will try to | |
5725 | group stubs together in order to reduce interruptions to the flow of | |
5726 | code, but it needs guidance as to how big these groups should be and | |
5727 | where they should be placed. | |
5728 | ||
5729 | The value of @samp{N}, the parameter to the | |
5730 | @option{--stub-group-size=} option controls where the stub groups are | |
5731 | placed. If it is negative then all stubs are placed before the first | |
5732 | branch that needs them. If it is positive then the stubs can be | |
5733 | placed either before or after the branches that need them. If the | |
5734 | value of @samp{N} is 1 (either +1 or -1) then the linker will choose | |
5735 | exactly where to place groups of stubs, using its built in heuristics. | |
5736 | A value of @samp{N} greater than 1 (or smaller than -1) tells the | |
5737 | linker that a single group of stubs can service at most @samp{N} bytes | |
5738 | from the input sections. | |
5739 | ||
5740 | The default, if @option{--stub-group-size=} is not specified, is | |
5741 | @samp{N = +1}. | |
5742 | ||
1a51c1a4 NC |
5743 | Farcalls stubs insertion is fully supported for the ARM-EABI target |
5744 | only, because it relies on object files properties not present | |
5745 | otherwise. | |
5746 | ||
36f63dca NC |
5747 | @ifclear GENERIC |
5748 | @lowersections | |
5749 | @end ifclear | |
5750 | @end ifset | |
5751 | ||
5752 | @ifset HPPA | |
5753 | @ifclear GENERIC | |
5754 | @raisesections | |
5755 | @end ifclear | |
5756 | ||
5757 | @node HPPA ELF32 | |
5758 | @section @command{ld} and HPPA 32-bit ELF Support | |
5759 | @cindex HPPA multiple sub-space stubs | |
5760 | @kindex --multi-subspace | |
5761 | When generating a shared library, @command{ld} will by default generate | |
5762 | import stubs suitable for use with a single sub-space application. | |
5763 | The @samp{--multi-subspace} switch causes @command{ld} to generate export | |
5764 | stubs, and different (larger) import stubs suitable for use with | |
5765 | multiple sub-spaces. | |
5766 | ||
5767 | @cindex HPPA stub grouping | |
5768 | @kindex --stub-group-size=@var{N} | |
5769 | Long branch stubs and import/export stubs are placed by @command{ld} in | |
5770 | stub sections located between groups of input sections. | |
5771 | @samp{--stub-group-size} specifies the maximum size of a group of input | |
5772 | sections handled by one stub section. Since branch offsets are signed, | |
5773 | a stub section may serve two groups of input sections, one group before | |
5774 | the stub section, and one group after it. However, when using | |
5775 | conditional branches that require stubs, it may be better (for branch | |
5776 | prediction) that stub sections only serve one group of input sections. | |
5777 | A negative value for @samp{N} chooses this scheme, ensuring that | |
5778 | branches to stubs always use a negative offset. Two special values of | |
5779 | @samp{N} are recognized, @samp{1} and @samp{-1}. These both instruct | |
5780 | @command{ld} to automatically size input section groups for the branch types | |
5781 | detected, with the same behaviour regarding stub placement as other | |
5782 | positive or negative values of @samp{N} respectively. | |
5783 | ||
5784 | Note that @samp{--stub-group-size} does not split input sections. A | |
5785 | single input section larger than the group size specified will of course | |
5786 | create a larger group (of one section). If input sections are too | |
5787 | large, it may not be possible for a branch to reach its stub. | |
5788 | ||
5789 | @ifclear GENERIC | |
5790 | @lowersections | |
5791 | @end ifclear | |
5792 | @end ifset | |
5793 | ||
7fb9f789 NC |
5794 | @ifset M68K |
5795 | @ifclear GENERIC | |
5796 | @raisesections | |
5797 | @end ifclear | |
5798 | ||
5799 | @node M68K | |
5800 | @section @command{ld} and the Motorola 68K family | |
5801 | ||
5802 | @cindex Motorola 68K GOT generation | |
5803 | @kindex --got=@var{type} | |
5804 | The @samp{--got=@var{type}} option lets you choose the GOT generation scheme. | |
5805 | The choices are @samp{single}, @samp{negative}, @samp{multigot} and | |
5806 | @samp{target}. When @samp{target} is selected the linker chooses | |
5807 | the default GOT generation scheme for the current target. | |
5808 | @samp{single} tells the linker to generate a single GOT with | |
5809 | entries only at non-negative offsets. | |
5810 | @samp{negative} instructs the linker to generate a single GOT with | |
5811 | entries at both negative and positive offsets. Not all environments | |
5812 | support such GOTs. | |
5813 | @samp{multigot} allows the linker to generate several GOTs in the | |
5814 | output file. All GOT references from a single input object | |
5815 | file access the same GOT, but references from different input object | |
5816 | files might access different GOTs. Not all environments support such GOTs. | |
5817 | ||
5818 | @ifclear GENERIC | |
5819 | @lowersections | |
5820 | @end ifclear | |
5821 | @end ifset | |
5822 | ||
36f63dca NC |
5823 | @ifset MMIX |
5824 | @ifclear GENERIC | |
5825 | @raisesections | |
5826 | @end ifclear | |
5827 | ||
5828 | @node MMIX | |
5829 | @section @code{ld} and MMIX | |
5830 | For MMIX, there is a choice of generating @code{ELF} object files or | |
5831 | @code{mmo} object files when linking. The simulator @code{mmix} | |
5832 | understands the @code{mmo} format. The binutils @code{objcopy} utility | |
5833 | can translate between the two formats. | |
5834 | ||
5835 | There is one special section, the @samp{.MMIX.reg_contents} section. | |
5836 | Contents in this section is assumed to correspond to that of global | |
5837 | registers, and symbols referring to it are translated to special symbols, | |
5838 | equal to registers. In a final link, the start address of the | |
5839 | @samp{.MMIX.reg_contents} section corresponds to the first allocated | |
5840 | global register multiplied by 8. Register @code{$255} is not included in | |
5841 | this section; it is always set to the program entry, which is at the | |
5842 | symbol @code{Main} for @code{mmo} files. | |
5843 | ||
5844 | Symbols with the prefix @code{__.MMIX.start.}, for example | |
5845 | @code{__.MMIX.start..text} and @code{__.MMIX.start..data} are special; | |
5846 | there must be only one each, even if they are local. The default linker | |
5847 | script uses these to set the default start address of a section. | |
5848 | ||
5849 | Initial and trailing multiples of zero-valued 32-bit words in a section, | |
5850 | are left out from an mmo file. | |
5851 | ||
5852 | @ifclear GENERIC | |
5853 | @lowersections | |
5854 | @end ifclear | |
5855 | @end ifset | |
5856 | ||
5857 | @ifset MSP430 | |
5858 | @ifclear GENERIC | |
5859 | @raisesections | |
5860 | @end ifclear | |
5861 | ||
5862 | @node MSP430 | |
5863 | @section @code{ld} and MSP430 | |
5864 | For the MSP430 it is possible to select the MPU architecture. The flag @samp{-m [mpu type]} | |
5865 | will select an appropriate linker script for selected MPU type. (To get a list of known MPUs | |
5866 | just pass @samp{-m help} option to the linker). | |
5867 | ||
5868 | @cindex MSP430 extra sections | |
5869 | The linker will recognize some extra sections which are MSP430 specific: | |
5870 | ||
5871 | @table @code | |
5872 | @item @samp{.vectors} | |
5873 | Defines a portion of ROM where interrupt vectors located. | |
5874 | ||
5875 | @item @samp{.bootloader} | |
5876 | Defines the bootloader portion of the ROM (if applicable). Any code | |
5877 | in this section will be uploaded to the MPU. | |
5878 | ||
5879 | @item @samp{.infomem} | |
5880 | Defines an information memory section (if applicable). Any code in | |
5881 | this section will be uploaded to the MPU. | |
5882 | ||
c0065db7 | 5883 | @item @samp{.infomemnobits} |
36f63dca NC |
5884 | This is the same as the @samp{.infomem} section except that any code |
5885 | in this section will not be uploaded to the MPU. | |
5886 | ||
5887 | @item @samp{.noinit} | |
5888 | Denotes a portion of RAM located above @samp{.bss} section. | |
5889 | ||
c0065db7 | 5890 | The last two sections are used by gcc. |
36f63dca NC |
5891 | @end table |
5892 | ||
5893 | @ifclear GENERIC | |
5894 | @lowersections | |
5895 | @end ifclear | |
5896 | @end ifset | |
5897 | ||
2a60a7a8 AM |
5898 | @ifset POWERPC |
5899 | @ifclear GENERIC | |
5900 | @raisesections | |
5901 | @end ifclear | |
5902 | ||
5903 | @node PowerPC ELF32 | |
5904 | @section @command{ld} and PowerPC 32-bit ELF Support | |
5905 | @cindex PowerPC long branches | |
5906 | @kindex --relax on PowerPC | |
5907 | Branches on PowerPC processors are limited to a signed 26-bit | |
5908 | displacement, which may result in @command{ld} giving | |
5909 | @samp{relocation truncated to fit} errors with very large programs. | |
5910 | @samp{--relax} enables the generation of trampolines that can access | |
5911 | the entire 32-bit address space. These trampolines are inserted at | |
5912 | section boundaries, so may not themselves be reachable if an input | |
5913 | section exceeds 33M in size. | |
5914 | ||
5915 | @cindex PowerPC ELF32 options | |
5916 | @table @option | |
5917 | @cindex PowerPC PLT | |
5918 | @kindex --bss-plt | |
5919 | @item --bss-plt | |
5920 | Current PowerPC GCC accepts a @samp{-msecure-plt} option that | |
5921 | generates code capable of using a newer PLT and GOT layout that has | |
5922 | the security advantage of no executable section ever needing to be | |
5923 | writable and no writable section ever being executable. PowerPC | |
5924 | @command{ld} will generate this layout, including stubs to access the | |
5925 | PLT, if all input files (including startup and static libraries) were | |
5926 | compiled with @samp{-msecure-plt}. @samp{--bss-plt} forces the old | |
5927 | BSS PLT (and GOT layout) which can give slightly better performance. | |
5928 | ||
016687f8 AM |
5929 | @kindex --secure-plt |
5930 | @item --secure-plt | |
5931 | @command{ld} will use the new PLT and GOT layout if it is linking new | |
5932 | @samp{-fpic} or @samp{-fPIC} code, but does not do so automatically | |
5933 | when linking non-PIC code. This option requests the new PLT and GOT | |
5934 | layout. A warning will be given if some object file requires the old | |
5935 | style BSS PLT. | |
5936 | ||
2a60a7a8 AM |
5937 | @cindex PowerPC GOT |
5938 | @kindex --sdata-got | |
5939 | @item --sdata-got | |
5940 | The new secure PLT and GOT are placed differently relative to other | |
5941 | sections compared to older BSS PLT and GOT placement. The location of | |
5942 | @code{.plt} must change because the new secure PLT is an initialized | |
5943 | section while the old PLT is uninitialized. The reason for the | |
5944 | @code{.got} change is more subtle: The new placement allows | |
5945 | @code{.got} to be read-only in applications linked with | |
5946 | @samp{-z relro -z now}. However, this placement means that | |
5947 | @code{.sdata} cannot always be used in shared libraries, because the | |
5948 | PowerPC ABI accesses @code{.sdata} in shared libraries from the GOT | |
5949 | pointer. @samp{--sdata-got} forces the old GOT placement. PowerPC | |
5950 | GCC doesn't use @code{.sdata} in shared libraries, so this option is | |
5951 | really only useful for other compilers that may do so. | |
5952 | ||
5953 | @cindex PowerPC stub symbols | |
5954 | @kindex --emit-stub-syms | |
5955 | @item --emit-stub-syms | |
5956 | This option causes @command{ld} to label linker stubs with a local | |
5957 | symbol that encodes the stub type and destination. | |
5958 | ||
5959 | @cindex PowerPC TLS optimization | |
5960 | @kindex --no-tls-optimize | |
5961 | @item --no-tls-optimize | |
5962 | PowerPC @command{ld} normally performs some optimization of code | |
5963 | sequences used to access Thread-Local Storage. Use this option to | |
5964 | disable the optimization. | |
5965 | @end table | |
5966 | ||
5967 | @ifclear GENERIC | |
5968 | @lowersections | |
5969 | @end ifclear | |
5970 | @end ifset | |
5971 | ||
5972 | @ifset POWERPC64 | |
5973 | @ifclear GENERIC | |
5974 | @raisesections | |
5975 | @end ifclear | |
5976 | ||
5977 | @node PowerPC64 ELF64 | |
5978 | @section @command{ld} and PowerPC64 64-bit ELF Support | |
5979 | ||
5980 | @cindex PowerPC64 ELF64 options | |
5981 | @table @option | |
5982 | @cindex PowerPC64 stub grouping | |
5983 | @kindex --stub-group-size | |
5984 | @item --stub-group-size | |
5985 | Long branch stubs, PLT call stubs and TOC adjusting stubs are placed | |
5986 | by @command{ld} in stub sections located between groups of input sections. | |
5987 | @samp{--stub-group-size} specifies the maximum size of a group of input | |
5988 | sections handled by one stub section. Since branch offsets are signed, | |
5989 | a stub section may serve two groups of input sections, one group before | |
5990 | the stub section, and one group after it. However, when using | |
5991 | conditional branches that require stubs, it may be better (for branch | |
5992 | prediction) that stub sections only serve one group of input sections. | |
5993 | A negative value for @samp{N} chooses this scheme, ensuring that | |
5994 | branches to stubs always use a negative offset. Two special values of | |
5995 | @samp{N} are recognized, @samp{1} and @samp{-1}. These both instruct | |
5996 | @command{ld} to automatically size input section groups for the branch types | |
5997 | detected, with the same behaviour regarding stub placement as other | |
5998 | positive or negative values of @samp{N} respectively. | |
5999 | ||
6000 | Note that @samp{--stub-group-size} does not split input sections. A | |
6001 | single input section larger than the group size specified will of course | |
6002 | create a larger group (of one section). If input sections are too | |
6003 | large, it may not be possible for a branch to reach its stub. | |
6004 | ||
6005 | @cindex PowerPC64 stub symbols | |
6006 | @kindex --emit-stub-syms | |
6007 | @item --emit-stub-syms | |
6008 | This option causes @command{ld} to label linker stubs with a local | |
6009 | symbol that encodes the stub type and destination. | |
6010 | ||
6011 | @cindex PowerPC64 dot symbols | |
6012 | @kindex --dotsyms | |
6013 | @kindex --no-dotsyms | |
6014 | @item --dotsyms, --no-dotsyms | |
6015 | These two options control how @command{ld} interprets version patterns | |
6016 | in a version script. Older PowerPC64 compilers emitted both a | |
6017 | function descriptor symbol with the same name as the function, and a | |
6018 | code entry symbol with the name prefixed by a dot (@samp{.}). To | |
6019 | properly version a function @samp{foo}, the version script thus needs | |
6020 | to control both @samp{foo} and @samp{.foo}. The option | |
6021 | @samp{--dotsyms}, on by default, automatically adds the required | |
6022 | dot-prefixed patterns. Use @samp{--no-dotsyms} to disable this | |
6023 | feature. | |
6024 | ||
6025 | @cindex PowerPC64 TLS optimization | |
6026 | @kindex --no-tls-optimize | |
6027 | @item --no-tls-optimize | |
6028 | PowerPC64 @command{ld} normally performs some optimization of code | |
6029 | sequences used to access Thread-Local Storage. Use this option to | |
6030 | disable the optimization. | |
6031 | ||
6032 | @cindex PowerPC64 OPD optimization | |
6033 | @kindex --no-opd-optimize | |
6034 | @item --no-opd-optimize | |
6035 | PowerPC64 @command{ld} normally removes @code{.opd} section entries | |
6036 | corresponding to deleted link-once functions, or functions removed by | |
e7fc76dd | 6037 | the action of @samp{--gc-sections} or linker script @code{/DISCARD/}. |
2a60a7a8 AM |
6038 | Use this option to disable @code{.opd} optimization. |
6039 | ||
6040 | @cindex PowerPC64 OPD spacing | |
6041 | @kindex --non-overlapping-opd | |
6042 | @item --non-overlapping-opd | |
6043 | Some PowerPC64 compilers have an option to generate compressed | |
6044 | @code{.opd} entries spaced 16 bytes apart, overlapping the third word, | |
6045 | the static chain pointer (unused in C) with the first word of the next | |
6046 | entry. This option expands such entries to the full 24 bytes. | |
6047 | ||
6048 | @cindex PowerPC64 TOC optimization | |
6049 | @kindex --no-toc-optimize | |
6050 | @item --no-toc-optimize | |
6051 | PowerPC64 @command{ld} normally removes unused @code{.toc} section | |
6052 | entries. Such entries are detected by examining relocations that | |
6053 | reference the TOC in code sections. A reloc in a deleted code section | |
6054 | marks a TOC word as unneeded, while a reloc in a kept code section | |
6055 | marks a TOC word as needed. Since the TOC may reference itself, TOC | |
6056 | relocs are also examined. TOC words marked as both needed and | |
6057 | unneeded will of course be kept. TOC words without any referencing | |
6058 | reloc are assumed to be part of a multi-word entry, and are kept or | |
6059 | discarded as per the nearest marked preceding word. This works | |
6060 | reliably for compiler generated code, but may be incorrect if assembly | |
6061 | code is used to insert TOC entries. Use this option to disable the | |
6062 | optimization. | |
6063 | ||
6064 | @cindex PowerPC64 multi-TOC | |
6065 | @kindex --no-multi-toc | |
6066 | @item --no-multi-toc | |
6067 | By default, PowerPC64 GCC generates code for a TOC model where TOC | |
6068 | entries are accessed with a 16-bit offset from r2. This limits the | |
6069 | total TOC size to 64K. PowerPC64 @command{ld} extends this limit by | |
6070 | grouping code sections such that each group uses less than 64K for its | |
6071 | TOC entries, then inserts r2 adjusting stubs between inter-group | |
6072 | calls. @command{ld} does not split apart input sections, so cannot | |
6073 | help if a single input file has a @code{.toc} section that exceeds | |
6074 | 64K, most likely from linking multiple files with @command{ld -r}. | |
6075 | Use this option to turn off this feature. | |
6076 | @end table | |
6077 | ||
6078 | @ifclear GENERIC | |
6079 | @lowersections | |
6080 | @end ifclear | |
6081 | @end ifset | |
6082 | ||
49fa1e15 AM |
6083 | @ifset SPU |
6084 | @ifclear GENERIC | |
6085 | @raisesections | |
6086 | @end ifclear | |
6087 | ||
6088 | @node SPU ELF | |
6089 | @section @command{ld} and SPU ELF Support | |
6090 | ||
6091 | @cindex SPU ELF options | |
6092 | @table @option | |
6093 | ||
6094 | @cindex SPU plugins | |
6095 | @kindex --plugin | |
6096 | @item --plugin | |
6097 | This option marks an executable as a PIC plugin module. | |
6098 | ||
6099 | @cindex SPU overlays | |
6100 | @kindex --no-overlays | |
6101 | @item --no-overlays | |
6102 | Normally, @command{ld} recognizes calls to functions within overlay | |
6103 | regions, and redirects such calls to an overlay manager via a stub. | |
6104 | @command{ld} also provides a built-in overlay manager. This option | |
6105 | turns off all this special overlay handling. | |
6106 | ||
6107 | @cindex SPU overlay stub symbols | |
6108 | @kindex --emit-stub-syms | |
6109 | @item --emit-stub-syms | |
6110 | This option causes @command{ld} to label overlay stubs with a local | |
6111 | symbol that encodes the stub type and destination. | |
6112 | ||
6113 | @cindex SPU extra overlay stubs | |
6114 | @kindex --extra-overlay-stubs | |
6115 | @item --extra-overlay-stubs | |
6116 | This option causes @command{ld} to add overlay call stubs on all | |
6117 | function calls out of overlay regions. Normally stubs are not added | |
6118 | on calls to non-overlay regions. | |
6119 | ||
6120 | @cindex SPU local store size | |
6121 | @kindex --local-store=lo:hi | |
6122 | @item --local-store=lo:hi | |
6123 | @command{ld} usually checks that a final executable for SPU fits in | |
6124 | the address range 0 to 256k. This option may be used to change the | |
6125 | range. Disable the check entirely with @option{--local-store=0:0}. | |
6126 | ||
c0065db7 | 6127 | @cindex SPU |
49fa1e15 AM |
6128 | @kindex --stack-analysis |
6129 | @item --stack-analysis | |
6130 | SPU local store space is limited. Over-allocation of stack space | |
6131 | unnecessarily limits space available for code and data, while | |
6132 | under-allocation results in runtime failures. If given this option, | |
6133 | @command{ld} will provide an estimate of maximum stack usage. | |
6134 | @command{ld} does this by examining symbols in code sections to | |
6135 | determine the extents of functions, and looking at function prologues | |
6136 | for stack adjusting instructions. A call-graph is created by looking | |
6137 | for relocations on branch instructions. The graph is then searched | |
6138 | for the maximum stack usage path. Note that this analysis does not | |
6139 | find calls made via function pointers, and does not handle recursion | |
6140 | and other cycles in the call graph. Stack usage may be | |
6141 | under-estimated if your code makes such calls. Also, stack usage for | |
6142 | dynamic allocation, e.g. alloca, will not be detected. If a link map | |
6143 | is requested, detailed information about each function's stack usage | |
6144 | and calls will be given. | |
6145 | ||
c0065db7 | 6146 | @cindex SPU |
49fa1e15 AM |
6147 | @kindex --emit-stack-syms |
6148 | @item --emit-stack-syms | |
6149 | This option, if given along with @option{--stack-analysis} will result | |
6150 | in @command{ld} emitting stack sizing symbols for each function. | |
6151 | These take the form @code{__stack_<function_name>} for global | |
6152 | functions, and @code{__stack_<number>_<function_name>} for static | |
6153 | functions. @code{<number>} is the section id in hex. The value of | |
6154 | such symbols is the stack requirement for the corresponding function. | |
6155 | The symbol size will be zero, type @code{STT_NOTYPE}, binding | |
c0065db7 | 6156 | @code{STB_LOCAL}, and section @code{SHN_ABS}. |
49fa1e15 AM |
6157 | @end table |
6158 | ||
6159 | @ifclear GENERIC | |
6160 | @lowersections | |
6161 | @end ifclear | |
6162 | @end ifset | |
6163 | ||
36f63dca NC |
6164 | @ifset TICOFF |
6165 | @ifclear GENERIC | |
6166 | @raisesections | |
6167 | @end ifclear | |
6168 | ||
6169 | @node TI COFF | |
6170 | @section @command{ld}'s Support for Various TI COFF Versions | |
6171 | @cindex TI COFF versions | |
6172 | @kindex --format=@var{version} | |
6173 | The @samp{--format} switch allows selection of one of the various | |
6174 | TI COFF versions. The latest of this writing is 2; versions 0 and 1 are | |
6175 | also supported. The TI COFF versions also vary in header byte-order | |
6176 | format; @command{ld} will read any version or byte order, but the output | |
6177 | header format depends on the default specified by the specific target. | |
6178 | ||
6179 | @ifclear GENERIC | |
6180 | @lowersections | |
6181 | @end ifclear | |
6182 | @end ifset | |
6183 | ||
2ca22b03 NC |
6184 | @ifset WIN32 |
6185 | @ifclear GENERIC | |
6186 | @raisesections | |
6187 | @end ifclear | |
6188 | ||
6189 | @node WIN32 | |
6190 | @section @command{ld} and WIN32 (cygwin/mingw) | |
6191 | ||
c0065db7 | 6192 | This section describes some of the win32 specific @command{ld} issues. |
b45619c0 | 6193 | See @ref{Options,,Command Line Options} for detailed description of the |
dc8465bf | 6194 | command line options mentioned here. |
2ca22b03 NC |
6195 | |
6196 | @table @emph | |
c0065db7 RM |
6197 | @cindex import libraries |
6198 | @item import libraries | |
69da35b5 | 6199 | The standard Windows linker creates and uses so-called import |
2ca22b03 | 6200 | libraries, which contains information for linking to dll's. They are |
69da35b5 NC |
6201 | regular static archives and are handled as any other static |
6202 | archive. The cygwin and mingw ports of @command{ld} have specific | |
2ca22b03 NC |
6203 | support for creating such libraries provided with the |
6204 | @samp{--out-implib} command line option. | |
6205 | ||
c0065db7 RM |
6206 | @item exporting DLL symbols |
6207 | @cindex exporting DLL symbols | |
dc8465bf NC |
6208 | The cygwin/mingw @command{ld} has several ways to export symbols for dll's. |
6209 | ||
6210 | @table @emph | |
6211 | @item using auto-export functionality | |
6212 | @cindex using auto-export functionality | |
6213 | By default @command{ld} exports symbols with the auto-export functionality, | |
6214 | which is controlled by the following command line options: | |
6215 | ||
0a5d968e NC |
6216 | @itemize |
6217 | @item --export-all-symbols [This is the default] | |
6218 | @item --exclude-symbols | |
6219 | @item --exclude-libs | |
6220 | @end itemize | |
6221 | ||
c0065db7 | 6222 | If, however, @samp{--export-all-symbols} is not given explicitly on the |
0a5d968e NC |
6223 | command line, then the default auto-export behavior will be @emph{disabled} |
6224 | if either of the following are true: | |
6225 | ||
6226 | @itemize | |
6227 | @item A DEF file is used. | |
6228 | @item Any symbol in any object file was marked with the __declspec(dllexport) attribute. | |
6229 | @end itemize | |
dc8465bf | 6230 | |
c0065db7 RM |
6231 | @item using a DEF file |
6232 | @cindex using a DEF file | |
dc8465bf NC |
6233 | Another way of exporting symbols is using a DEF file. A DEF file is |
6234 | an ASCII file containing definitions of symbols which should be | |
6235 | exported when a dll is created. Usually it is named @samp{<dll | |
6236 | name>.def} and is added as any other object file to the linker's | |
0a5d968e | 6237 | command line. The file's name must end in @samp{.def} or @samp{.DEF}. |
dc8465bf NC |
6238 | |
6239 | @example | |
6240 | gcc -o <output> <objectfiles> <dll name>.def | |
6241 | @end example | |
6242 | ||
0a5d968e NC |
6243 | Using a DEF file turns off the normal auto-export behavior, unless the |
6244 | @samp{--export-all-symbols} option is also used. | |
6245 | ||
dc8465bf NC |
6246 | Here is an example of a DEF file for a shared library called @samp{xyz.dll}: |
6247 | ||
6248 | @example | |
4b5bd4e7 | 6249 | LIBRARY "xyz.dll" BASE=0x20000000 |
dc8465bf NC |
6250 | |
6251 | EXPORTS | |
6252 | foo | |
6253 | bar | |
6254 | _bar = bar | |
4b5bd4e7 DS |
6255 | another_foo = abc.dll.afoo |
6256 | var1 DATA | |
c0065db7 | 6257 | @end example |
dc8465bf | 6258 | |
4b5bd4e7 DS |
6259 | This example defines a DLL with a non-default base address and five |
6260 | symbols in the export table. The third exported symbol @code{_bar} is an | |
6261 | alias for the second. The fourth symbol, @code{another_foo} is resolved | |
6262 | by "forwarding" to another module and treating it as an alias for | |
6263 | @code{afoo} exported from the DLL @samp{abc.dll}. The final symbol | |
6264 | @code{var1} is declared to be a data object. | |
6265 | ||
6b31ad16 DS |
6266 | The optional @code{LIBRARY <name>} command indicates the @emph{internal} |
6267 | name of the output DLL. If @samp{<name>} does not include a suffix, | |
6268 | the default library suffix, @samp{.DLL} is appended. | |
6269 | ||
b45619c0 NC |
6270 | When the .DEF file is used to build an application, rather than a |
6271 | library, the @code{NAME <name>} command should be used instead of | |
6b31ad16 | 6272 | @code{LIBRARY}. If @samp{<name>} does not include a suffix, the default |
c0065db7 | 6273 | executable suffix, @samp{.EXE} is appended. |
6b31ad16 DS |
6274 | |
6275 | With either @code{LIBRARY <name>} or @code{NAME <name>} the optional | |
6276 | specification @code{BASE = <number>} may be used to specify a | |
c0065db7 | 6277 | non-default base address for the image. |
6b31ad16 DS |
6278 | |
6279 | If neither @code{LIBRARY <name>} nor @code{NAME <name>} is specified, | |
a2877985 DS |
6280 | or they specify an empty string, the internal name is the same as the |
6281 | filename specified on the command line. | |
6b31ad16 | 6282 | |
4b5bd4e7 DS |
6283 | The complete specification of an export symbol is: |
6284 | ||
6285 | @example | |
6286 | EXPORTS | |
6287 | ( ( ( <name1> [ = <name2> ] ) | |
6288 | | ( <name1> = <module-name> . <external-name>)) | |
6289 | [ @@ <integer> ] [NONAME] [DATA] [CONSTANT] [PRIVATE] ) * | |
c0065db7 | 6290 | @end example |
4b5bd4e7 DS |
6291 | |
6292 | Declares @samp{<name1>} as an exported symbol from the DLL, or declares | |
6293 | @samp{<name1>} as an exported alias for @samp{<name2>}; or declares | |
6294 | @samp{<name1>} as a "forward" alias for the symbol | |
6295 | @samp{<external-name>} in the DLL @samp{<module-name>}. | |
6296 | Optionally, the symbol may be exported by the specified ordinal | |
6297 | @samp{<integer>} alias. | |
6298 | ||
6299 | The optional keywords that follow the declaration indicate: | |
6300 | ||
6301 | @code{NONAME}: Do not put the symbol name in the DLL's export table. It | |
6302 | will still be exported by its ordinal alias (either the value specified | |
6303 | by the .def specification or, otherwise, the value assigned by the | |
6304 | linker). The symbol name, however, does remain visible in the import | |
6305 | library (if any), unless @code{PRIVATE} is also specified. | |
6306 | ||
6307 | @code{DATA}: The symbol is a variable or object, rather than a function. | |
6308 | The import lib will export only an indirect reference to @code{foo} as | |
6309 | the symbol @code{_imp__foo} (ie, @code{foo} must be resolved as | |
6310 | @code{*_imp__foo}). | |
6311 | ||
6312 | @code{CONSTANT}: Like @code{DATA}, but put the undecorated @code{foo} as | |
6313 | well as @code{_imp__foo} into the import library. Both refer to the | |
6314 | read-only import address table's pointer to the variable, not to the | |
6315 | variable itself. This can be dangerous. If the user code fails to add | |
6316 | the @code{dllimport} attribute and also fails to explicitly add the | |
6317 | extra indirection that the use of the attribute enforces, the | |
6318 | application will behave unexpectedly. | |
6319 | ||
6320 | @code{PRIVATE}: Put the symbol in the DLL's export table, but do not put | |
6321 | it into the static import library used to resolve imports at link time. The | |
6322 | symbol can still be imported using the @code{LoadLibrary/GetProcAddress} | |
6323 | API at runtime or by by using the GNU ld extension of linking directly to | |
6324 | the DLL without an import library. | |
c0065db7 | 6325 | |
4b5bd4e7 DS |
6326 | See ld/deffilep.y in the binutils sources for the full specification of |
6327 | other DEF file statements | |
dc8465bf NC |
6328 | |
6329 | @cindex creating a DEF file | |
6330 | While linking a shared dll, @command{ld} is able to create a DEF file | |
6331 | with the @samp{--output-def <file>} command line option. | |
0a5d968e NC |
6332 | |
6333 | @item Using decorations | |
6334 | @cindex Using decorations | |
6335 | Another way of marking symbols for export is to modify the source code | |
6336 | itself, so that when building the DLL each symbol to be exported is | |
6337 | declared as: | |
6338 | ||
6339 | @example | |
6340 | __declspec(dllexport) int a_variable | |
6341 | __declspec(dllexport) void a_function(int with_args) | |
6342 | @end example | |
6343 | ||
6344 | All such symbols will be exported from the DLL. If, however, | |
6345 | any of the object files in the DLL contain symbols decorated in | |
6346 | this way, then the normal auto-export behavior is disabled, unless | |
6347 | the @samp{--export-all-symbols} option is also used. | |
6348 | ||
6349 | Note that object files that wish to access these symbols must @emph{not} | |
c0065db7 | 6350 | decorate them with dllexport. Instead, they should use dllimport, |
0a5d968e NC |
6351 | instead: |
6352 | ||
6353 | @example | |
6354 | __declspec(dllimport) int a_variable | |
6355 | __declspec(dllimport) void a_function(int with_args) | |
6356 | @end example | |
6357 | ||
c0065db7 RM |
6358 | This complicates the structure of library header files, because |
6359 | when included by the library itself the header must declare the | |
0a5d968e NC |
6360 | variables and functions as dllexport, but when included by client |
6361 | code the header must declare them as dllimport. There are a number | |
c0065db7 | 6362 | of idioms that are typically used to do this; often client code can |
0a5d968e NC |
6363 | omit the __declspec() declaration completely. See |
6364 | @samp{--enable-auto-import} and @samp{automatic data imports} for more | |
b45619c0 | 6365 | information. |
c0065db7 | 6366 | @end table |
dc8465bf | 6367 | |
2ca22b03 NC |
6368 | @cindex automatic data imports |
6369 | @item automatic data imports | |
6370 | The standard Windows dll format supports data imports from dlls only | |
69da35b5 | 6371 | by adding special decorations (dllimport/dllexport), which let the |
2ca22b03 | 6372 | compiler produce specific assembler instructions to deal with this |
c0065db7 | 6373 | issue. This increases the effort necessary to port existing Un*x |
69da35b5 | 6374 | code to these platforms, especially for large |
2ca22b03 | 6375 | c++ libraries and applications. The auto-import feature, which was |
c0065db7 | 6376 | initially provided by Paul Sokolovsky, allows one to omit the |
b45619c0 | 6377 | decorations to achieve a behavior that conforms to that on POSIX/Un*x |
c0065db7 | 6378 | platforms. This feature is enabled with the @samp{--enable-auto-import} |
69da35b5 NC |
6379 | command-line option, although it is enabled by default on cygwin/mingw. |
6380 | The @samp{--enable-auto-import} option itself now serves mainly to | |
6381 | suppress any warnings that are ordinarily emitted when linked objects | |
6382 | trigger the feature's use. | |
6383 | ||
c0065db7 | 6384 | auto-import of variables does not always work flawlessly without |
69da35b5 NC |
6385 | additional assistance. Sometimes, you will see this message |
6386 | ||
c0065db7 | 6387 | "variable '<var>' can't be auto-imported. Please read the |
69da35b5 NC |
6388 | documentation for ld's @code{--enable-auto-import} for details." |
6389 | ||
c0065db7 RM |
6390 | The @samp{--enable-auto-import} documentation explains why this error |
6391 | occurs, and several methods that can be used to overcome this difficulty. | |
6392 | One of these methods is the @emph{runtime pseudo-relocs} feature, described | |
69da35b5 NC |
6393 | below. |
6394 | ||
6395 | @cindex runtime pseudo-relocation | |
c0065db7 RM |
6396 | For complex variables imported from DLLs (such as structs or classes), |
6397 | object files typically contain a base address for the variable and an | |
6398 | offset (@emph{addend}) within the variable--to specify a particular | |
6399 | field or public member, for instance. Unfortunately, the runtime loader used | |
6400 | in win32 environments is incapable of fixing these references at runtime | |
69da35b5 | 6401 | without the additional information supplied by dllimport/dllexport decorations. |
c0065db7 | 6402 | The standard auto-import feature described above is unable to resolve these |
69da35b5 NC |
6403 | references. |
6404 | ||
c0065db7 RM |
6405 | The @samp{--enable-runtime-pseudo-relocs} switch allows these references to |
6406 | be resolved without error, while leaving the task of adjusting the references | |
6407 | themselves (with their non-zero addends) to specialized code provided by the | |
6408 | runtime environment. Recent versions of the cygwin and mingw environments and | |
6409 | compilers provide this runtime support; older versions do not. However, the | |
6410 | support is only necessary on the developer's platform; the compiled result will | |
69da35b5 NC |
6411 | run without error on an older system. |
6412 | ||
c0065db7 RM |
6413 | @samp{--enable-runtime-pseudo-relocs} is not the default; it must be explicitly |
6414 | enabled as needed. | |
2ca22b03 NC |
6415 | |
6416 | @cindex direct linking to a dll | |
6417 | @item direct linking to a dll | |
6418 | The cygwin/mingw ports of @command{ld} support the direct linking, | |
6419 | including data symbols, to a dll without the usage of any import | |
69da35b5 | 6420 | libraries. This is much faster and uses much less memory than does the |
b45619c0 | 6421 | traditional import library method, especially when linking large |
c0065db7 RM |
6422 | libraries or applications. When @command{ld} creates an import lib, each |
6423 | function or variable exported from the dll is stored in its own bfd, even | |
6424 | though a single bfd could contain many exports. The overhead involved in | |
69da35b5 | 6425 | storing, loading, and processing so many bfd's is quite large, and explains the |
c0065db7 | 6426 | tremendous time, memory, and storage needed to link against particularly |
69da35b5 NC |
6427 | large or complex libraries when using import libs. |
6428 | ||
c0065db7 | 6429 | Linking directly to a dll uses no extra command-line switches other than |
69da35b5 | 6430 | @samp{-L} and @samp{-l}, because @command{ld} already searches for a number |
c0065db7 | 6431 | of names to match each library. All that is needed from the developer's |
69da35b5 NC |
6432 | perspective is an understanding of this search, in order to force ld to |
6433 | select the dll instead of an import library. | |
6434 | ||
2ca22b03 | 6435 | |
69da35b5 NC |
6436 | For instance, when ld is called with the argument @samp{-lxxx} it will attempt |
6437 | to find, in the first directory of its search path, | |
2ca22b03 NC |
6438 | |
6439 | @example | |
45e948fe NC |
6440 | libxxx.dll.a |
6441 | xxx.dll.a | |
6442 | libxxx.a | |
6443 | xxx.lib | |
69da35b5 | 6444 | cygxxx.dll (*) |
45e948fe NC |
6445 | libxxx.dll |
6446 | xxx.dll | |
2ca22b03 NC |
6447 | @end example |
6448 | ||
69da35b5 NC |
6449 | before moving on to the next directory in the search path. |
6450 | ||
c0065db7 RM |
6451 | (*) Actually, this is not @samp{cygxxx.dll} but in fact is @samp{<prefix>xxx.dll}, |
6452 | where @samp{<prefix>} is set by the @command{ld} option | |
6453 | @samp{--dll-search-prefix=<prefix>}. In the case of cygwin, the standard gcc spec | |
6454 | file includes @samp{--dll-search-prefix=cyg}, so in effect we actually search for | |
69da35b5 NC |
6455 | @samp{cygxxx.dll}. |
6456 | ||
c0065db7 RM |
6457 | Other win32-based unix environments, such as mingw or pw32, may use other |
6458 | @samp{<prefix>}es, although at present only cygwin makes use of this feature. It | |
69da35b5 NC |
6459 | was originally intended to help avoid name conflicts among dll's built for the |
6460 | various win32/un*x environments, so that (for example) two versions of a zlib dll | |
6461 | could coexist on the same machine. | |
6462 | ||
2ca22b03 NC |
6463 | The generic cygwin/mingw path layout uses a @samp{bin} directory for |
6464 | applications and dll's and a @samp{lib} directory for the import | |
69da35b5 | 6465 | libraries (using cygwin nomenclature): |
2ca22b03 NC |
6466 | |
6467 | @example | |
6468 | bin/ | |
6469 | cygxxx.dll | |
6470 | lib/ | |
6471 | libxxx.dll.a (in case of dll's) | |
c0065db7 | 6472 | libxxx.a (in case of static archive) |
2ca22b03 NC |
6473 | @end example |
6474 | ||
c0065db7 RM |
6475 | Linking directly to a dll without using the import library can be |
6476 | done two ways: | |
2ca22b03 NC |
6477 | |
6478 | 1. Use the dll directly by adding the @samp{bin} path to the link line | |
6479 | @example | |
6480 | gcc -Wl,-verbose -o a.exe -L../bin/ -lxxx | |
c0065db7 | 6481 | @end example |
2ca22b03 | 6482 | |
69da35b5 NC |
6483 | However, as the dll's often have version numbers appended to their names |
6484 | (@samp{cygncurses-5.dll}) this will often fail, unless one specifies | |
6485 | @samp{-L../bin -lncurses-5} to include the version. Import libs are generally | |
6486 | not versioned, and do not have this difficulty. | |
6487 | ||
2ca22b03 NC |
6488 | 2. Create a symbolic link from the dll to a file in the @samp{lib} |
6489 | directory according to the above mentioned search pattern. This | |
6490 | should be used to avoid unwanted changes in the tools needed for | |
6491 | making the app/dll. | |
6492 | ||
6493 | @example | |
6494 | ln -s bin/cygxxx.dll lib/[cyg|lib|]xxx.dll[.a] | |
c0065db7 | 6495 | @end example |
2ca22b03 NC |
6496 | |
6497 | Then you can link without any make environment changes. | |
6498 | ||
6499 | @example | |
6500 | gcc -Wl,-verbose -o a.exe -L../lib/ -lxxx | |
c0065db7 | 6501 | @end example |
69da35b5 NC |
6502 | |
6503 | This technique also avoids the version number problems, because the following is | |
6504 | perfectly legal | |
6505 | ||
6506 | @example | |
6507 | bin/ | |
6508 | cygxxx-5.dll | |
6509 | lib/ | |
c0065db7 | 6510 | libxxx.dll.a -> ../bin/cygxxx-5.dll |
69da35b5 NC |
6511 | @end example |
6512 | ||
dc8465bf | 6513 | Linking directly to a dll without using an import lib will work |
69da35b5 NC |
6514 | even when auto-import features are exercised, and even when |
6515 | @samp{--enable-runtime-pseudo-relocs} is used. | |
6516 | ||
6517 | Given the improvements in speed and memory usage, one might justifiably | |
45e948fe | 6518 | wonder why import libraries are used at all. There are three reasons: |
69da35b5 NC |
6519 | |
6520 | 1. Until recently, the link-directly-to-dll functionality did @emph{not} | |
6521 | work with auto-imported data. | |
6522 | ||
dc8465bf NC |
6523 | 2. Sometimes it is necessary to include pure static objects within the |
6524 | import library (which otherwise contains only bfd's for indirection | |
6525 | symbols that point to the exports of a dll). Again, the import lib | |
6526 | for the cygwin kernel makes use of this ability, and it is not | |
6527 | possible to do this without an import lib. | |
69da35b5 | 6528 | |
45e948fe NC |
6529 | 3. Symbol aliases can only be resolved using an import lib. This is |
6530 | critical when linking against OS-supplied dll's (eg, the win32 API) | |
6531 | in which symbols are usually exported as undecorated aliases of their | |
6532 | stdcall-decorated assembly names. | |
6533 | ||
69da35b5 | 6534 | So, import libs are not going away. But the ability to replace |
c0065db7 RM |
6535 | true import libs with a simple symbolic link to (or a copy of) |
6536 | a dll, in many cases, is a useful addition to the suite of tools | |
6537 | binutils makes available to the win32 developer. Given the | |
69da35b5 NC |
6538 | massive improvements in memory requirements during linking, storage |
6539 | requirements, and linking speed, we expect that many developers | |
6540 | will soon begin to use this feature whenever possible. | |
dc8465bf | 6541 | |
c0065db7 | 6542 | @item symbol aliasing |
dc8465bf | 6543 | @table @emph |
c0065db7 RM |
6544 | @item adding additional names |
6545 | Sometimes, it is useful to export symbols with additional names. | |
dc8465bf NC |
6546 | A symbol @samp{foo} will be exported as @samp{foo}, but it can also be |
6547 | exported as @samp{_foo} by using special directives in the DEF file | |
6548 | when creating the dll. This will affect also the optional created | |
c0065db7 | 6549 | import library. Consider the following DEF file: |
dc8465bf | 6550 | |
c0065db7 | 6551 | @example |
dc8465bf NC |
6552 | LIBRARY "xyz.dll" BASE=0x61000000 |
6553 | ||
6554 | EXPORTS | |
c0065db7 | 6555 | foo |
dc8465bf | 6556 | _foo = foo |
c0065db7 | 6557 | @end example |
dc8465bf NC |
6558 | |
6559 | The line @samp{_foo = foo} maps the symbol @samp{foo} to @samp{_foo}. | |
6560 | ||
6561 | Another method for creating a symbol alias is to create it in the | |
6562 | source code using the "weak" attribute: | |
6563 | ||
c0065db7 RM |
6564 | @example |
6565 | void foo () @{ /* Do something. */; @} | |
dc8465bf | 6566 | void _foo () __attribute__ ((weak, alias ("foo"))); |
c0065db7 | 6567 | @end example |
dc8465bf NC |
6568 | |
6569 | See the gcc manual for more information about attributes and weak | |
6570 | symbols. | |
6571 | ||
6572 | @item renaming symbols | |
6573 | Sometimes it is useful to rename exports. For instance, the cygwin | |
c0065db7 | 6574 | kernel does this regularly. A symbol @samp{_foo} can be exported as |
dc8465bf NC |
6575 | @samp{foo} but not as @samp{_foo} by using special directives in the |
6576 | DEF file. (This will also affect the import library, if it is | |
c0065db7 | 6577 | created). In the following example: |
dc8465bf | 6578 | |
c0065db7 | 6579 | @example |
dc8465bf NC |
6580 | LIBRARY "xyz.dll" BASE=0x61000000 |
6581 | ||
6582 | EXPORTS | |
6583 | _foo = foo | |
c0065db7 | 6584 | @end example |
dc8465bf NC |
6585 | |
6586 | The line @samp{_foo = foo} maps the exported symbol @samp{foo} to | |
6587 | @samp{_foo}. | |
c0065db7 | 6588 | @end table |
dc8465bf | 6589 | |
0a5d968e | 6590 | Note: using a DEF file disables the default auto-export behavior, |
c0065db7 | 6591 | unless the @samp{--export-all-symbols} command line option is used. |
0a5d968e | 6592 | If, however, you are trying to rename symbols, then you should list |
c0065db7 RM |
6593 | @emph{all} desired exports in the DEF file, including the symbols |
6594 | that are not being renamed, and do @emph{not} use the | |
6595 | @samp{--export-all-symbols} option. If you list only the | |
6596 | renamed symbols in the DEF file, and use @samp{--export-all-symbols} | |
6597 | to handle the other symbols, then the both the new names @emph{and} | |
6598 | the original names for the renamed symbols will be exported. | |
6599 | In effect, you'd be aliasing those symbols, not renaming them, | |
0a5d968e | 6600 | which is probably not what you wanted. |
c87db184 CF |
6601 | |
6602 | @cindex weak externals | |
6603 | @item weak externals | |
6604 | The Windows object format, PE, specifies a form of weak symbols called | |
6605 | weak externals. When a weak symbol is linked and the symbol is not | |
6606 | defined, the weak symbol becomes an alias for some other symbol. There | |
6607 | are three variants of weak externals: | |
6608 | @itemize | |
6609 | @item Definition is searched for in objects and libraries, historically | |
6610 | called lazy externals. | |
6611 | @item Definition is searched for only in other objects, not in libraries. | |
6612 | This form is not presently implemented. | |
6613 | @item No search; the symbol is an alias. This form is not presently | |
6614 | implemented. | |
6615 | @end itemize | |
6616 | As a GNU extension, weak symbols that do not specify an alternate symbol | |
6617 | are supported. If the symbol is undefined when linking, the symbol | |
6618 | uses a default value. | |
2ca22b03 NC |
6619 | @end table |
6620 | ||
6621 | @ifclear GENERIC | |
6622 | @lowersections | |
6623 | @end ifclear | |
6624 | @end ifset | |
6625 | ||
e0001a05 NC |
6626 | @ifset XTENSA |
6627 | @ifclear GENERIC | |
6628 | @raisesections | |
6629 | @end ifclear | |
6630 | ||
6631 | @node Xtensa | |
6632 | @section @code{ld} and Xtensa Processors | |
6633 | ||
6634 | @cindex Xtensa processors | |
6635 | The default @command{ld} behavior for Xtensa processors is to interpret | |
6636 | @code{SECTIONS} commands so that lists of explicitly named sections in a | |
6637 | specification with a wildcard file will be interleaved when necessary to | |
6638 | keep literal pools within the range of PC-relative load offsets. For | |
6639 | example, with the command: | |
6640 | ||
6641 | @smallexample | |
6642 | SECTIONS | |
6643 | @{ | |
6644 | .text : @{ | |
6645 | *(.literal .text) | |
6646 | @} | |
6647 | @} | |
6648 | @end smallexample | |
6649 | ||
6650 | @noindent | |
6651 | @command{ld} may interleave some of the @code{.literal} | |
6652 | and @code{.text} sections from different object files to ensure that the | |
6653 | literal pools are within the range of PC-relative load offsets. A valid | |
6654 | interleaving might place the @code{.literal} sections from an initial | |
6655 | group of files followed by the @code{.text} sections of that group of | |
6656 | files. Then, the @code{.literal} sections from the rest of the files | |
6657 | and the @code{.text} sections from the rest of the files would follow. | |
e0001a05 | 6658 | |
43cd72b9 | 6659 | @cindex @option{--relax} on Xtensa |
e0001a05 | 6660 | @cindex relaxing on Xtensa |
43cd72b9 BW |
6661 | Relaxation is enabled by default for the Xtensa version of @command{ld} and |
6662 | provides two important link-time optimizations. The first optimization | |
6663 | is to combine identical literal values to reduce code size. A redundant | |
6664 | literal will be removed and all the @code{L32R} instructions that use it | |
6665 | will be changed to reference an identical literal, as long as the | |
6666 | location of the replacement literal is within the offset range of all | |
6667 | the @code{L32R} instructions. The second optimization is to remove | |
6668 | unnecessary overhead from assembler-generated ``longcall'' sequences of | |
6669 | @code{L32R}/@code{CALLX@var{n}} when the target functions are within | |
6670 | range of direct @code{CALL@var{n}} instructions. | |
6671 | ||
6672 | For each of these cases where an indirect call sequence can be optimized | |
6673 | to a direct call, the linker will change the @code{CALLX@var{n}} | |
6674 | instruction to a @code{CALL@var{n}} instruction, remove the @code{L32R} | |
6675 | instruction, and remove the literal referenced by the @code{L32R} | |
6676 | instruction if it is not used for anything else. Removing the | |
6677 | @code{L32R} instruction always reduces code size but can potentially | |
6678 | hurt performance by changing the alignment of subsequent branch targets. | |
6679 | By default, the linker will always preserve alignments, either by | |
6680 | switching some instructions between 24-bit encodings and the equivalent | |
6681 | density instructions or by inserting a no-op in place of the @code{L32R} | |
6682 | instruction that was removed. If code size is more important than | |
6683 | performance, the @option{--size-opt} option can be used to prevent the | |
6684 | linker from widening density instructions or inserting no-ops, except in | |
6685 | a few cases where no-ops are required for correctness. | |
6686 | ||
6687 | The following Xtensa-specific command-line options can be used to | |
6688 | control the linker: | |
6689 | ||
6690 | @cindex Xtensa options | |
6691 | @table @option | |
e0001a05 | 6692 | @kindex --no-relax |
43cd72b9 BW |
6693 | @item --no-relax |
6694 | Since the Xtensa version of @code{ld} enables the @option{--relax} option | |
6695 | by default, the @option{--no-relax} option is provided to disable | |
6696 | relaxation. | |
6697 | ||
6698 | @item --size-opt | |
6699 | When optimizing indirect calls to direct calls, optimize for code size | |
6700 | more than performance. With this option, the linker will not insert | |
6701 | no-ops or widen density instructions to preserve branch target | |
6702 | alignment. There may still be some cases where no-ops are required to | |
6703 | preserve the correctness of the code. | |
6704 | @end table | |
e0001a05 NC |
6705 | |
6706 | @ifclear GENERIC | |
6707 | @lowersections | |
6708 | @end ifclear | |
6709 | @end ifset | |
6710 | ||
252b5132 RH |
6711 | @ifclear SingleFormat |
6712 | @node BFD | |
6713 | @chapter BFD | |
6714 | ||
6715 | @cindex back end | |
6716 | @cindex object file management | |
6717 | @cindex object formats available | |
6718 | @kindex objdump -i | |
6719 | The linker accesses object and archive files using the BFD libraries. | |
6720 | These libraries allow the linker to use the same routines to operate on | |
6721 | object files whatever the object file format. A different object file | |
6722 | format can be supported simply by creating a new BFD back end and adding | |
6723 | it to the library. To conserve runtime memory, however, the linker and | |
6724 | associated tools are usually configured to support only a subset of the | |
6725 | object file formats available. You can use @code{objdump -i} | |
6726 | (@pxref{objdump,,objdump,binutils.info,The GNU Binary Utilities}) to | |
6727 | list all the formats available for your configuration. | |
6728 | ||
6729 | @cindex BFD requirements | |
6730 | @cindex requirements for BFD | |
6731 | As with most implementations, BFD is a compromise between | |
6732 | several conflicting requirements. The major factor influencing | |
6733 | BFD design was efficiency: any time used converting between | |
6734 | formats is time which would not have been spent had BFD not | |
6735 | been involved. This is partly offset by abstraction payback; since | |
6736 | BFD simplifies applications and back ends, more time and care | |
6737 | may be spent optimizing algorithms for a greater speed. | |
6738 | ||
6739 | One minor artifact of the BFD solution which you should bear in | |
6740 | mind is the potential for information loss. There are two places where | |
6741 | useful information can be lost using the BFD mechanism: during | |
6742 | conversion and during output. @xref{BFD information loss}. | |
6743 | ||
6744 | @menu | |
6745 | * BFD outline:: How it works: an outline of BFD | |
6746 | @end menu | |
6747 | ||
6748 | @node BFD outline | |
36f63dca | 6749 | @section How It Works: An Outline of BFD |
252b5132 RH |
6750 | @cindex opening object files |
6751 | @include bfdsumm.texi | |
6752 | @end ifclear | |
6753 | ||
6754 | @node Reporting Bugs | |
6755 | @chapter Reporting Bugs | |
ff5dcc92 SC |
6756 | @cindex bugs in @command{ld} |
6757 | @cindex reporting bugs in @command{ld} | |
252b5132 | 6758 | |
ff5dcc92 | 6759 | Your bug reports play an essential role in making @command{ld} reliable. |
252b5132 RH |
6760 | |
6761 | Reporting a bug may help you by bringing a solution to your problem, or | |
6762 | it may not. But in any case the principal function of a bug report is | |
ff5dcc92 | 6763 | to help the entire community by making the next version of @command{ld} |
252b5132 | 6764 | work better. Bug reports are your contribution to the maintenance of |
ff5dcc92 | 6765 | @command{ld}. |
252b5132 RH |
6766 | |
6767 | In order for a bug report to serve its purpose, you must include the | |
6768 | information that enables us to fix the bug. | |
6769 | ||
6770 | @menu | |
6771 | * Bug Criteria:: Have you found a bug? | |
6772 | * Bug Reporting:: How to report bugs | |
6773 | @end menu | |
6774 | ||
6775 | @node Bug Criteria | |
36f63dca | 6776 | @section Have You Found a Bug? |
252b5132 RH |
6777 | @cindex bug criteria |
6778 | ||
6779 | If you are not sure whether you have found a bug, here are some guidelines: | |
6780 | ||
6781 | @itemize @bullet | |
6782 | @cindex fatal signal | |
6783 | @cindex linker crash | |
6784 | @cindex crash of linker | |
6785 | @item | |
6786 | If the linker gets a fatal signal, for any input whatever, that is a | |
ff5dcc92 | 6787 | @command{ld} bug. Reliable linkers never crash. |
252b5132 RH |
6788 | |
6789 | @cindex error on valid input | |
6790 | @item | |
ff5dcc92 | 6791 | If @command{ld} produces an error message for valid input, that is a bug. |
252b5132 RH |
6792 | |
6793 | @cindex invalid input | |
6794 | @item | |
ff5dcc92 | 6795 | If @command{ld} does not produce an error message for invalid input, that |
252b5132 RH |
6796 | may be a bug. In the general case, the linker can not verify that |
6797 | object files are correct. | |
6798 | ||
6799 | @item | |
6800 | If you are an experienced user of linkers, your suggestions for | |
ff5dcc92 | 6801 | improvement of @command{ld} are welcome in any case. |
252b5132 RH |
6802 | @end itemize |
6803 | ||
6804 | @node Bug Reporting | |
36f63dca | 6805 | @section How to Report Bugs |
252b5132 | 6806 | @cindex bug reports |
ff5dcc92 | 6807 | @cindex @command{ld} bugs, reporting |
252b5132 RH |
6808 | |
6809 | A number of companies and individuals offer support for @sc{gnu} | |
ff5dcc92 | 6810 | products. If you obtained @command{ld} from a support organization, we |
252b5132 RH |
6811 | recommend you contact that organization first. |
6812 | ||
6813 | You can find contact information for many support companies and | |
6814 | individuals in the file @file{etc/SERVICE} in the @sc{gnu} Emacs | |
6815 | distribution. | |
6816 | ||
ad22bfe8 | 6817 | @ifset BUGURL |
ff5dcc92 | 6818 | Otherwise, send bug reports for @command{ld} to |
ad22bfe8 JM |
6819 | @value{BUGURL}. |
6820 | @end ifset | |
252b5132 RH |
6821 | |
6822 | The fundamental principle of reporting bugs usefully is this: | |
6823 | @strong{report all the facts}. If you are not sure whether to state a | |
6824 | fact or leave it out, state it! | |
6825 | ||
6826 | Often people omit facts because they think they know what causes the | |
6827 | problem and assume that some details do not matter. Thus, you might | |
b553b183 NC |
6828 | assume that the name of a symbol you use in an example does not |
6829 | matter. Well, probably it does not, but one cannot be sure. Perhaps | |
6830 | the bug is a stray memory reference which happens to fetch from the | |
6831 | location where that name is stored in memory; perhaps, if the name | |
6832 | were different, the contents of that location would fool the linker | |
6833 | into doing the right thing despite the bug. Play it safe and give a | |
6834 | specific, complete example. That is the easiest thing for you to do, | |
c0065db7 | 6835 | and the most helpful. |
b553b183 NC |
6836 | |
6837 | Keep in mind that the purpose of a bug report is to enable us to fix | |
6838 | the bug if it is new to us. Therefore, always write your bug reports | |
6839 | on the assumption that the bug has not been reported previously. | |
252b5132 RH |
6840 | |
6841 | Sometimes people give a few sketchy facts and ask, ``Does this ring a | |
36f63dca NC |
6842 | bell?'' This cannot help us fix a bug, so it is basically useless. We |
6843 | respond by asking for enough details to enable us to investigate. | |
6844 | You might as well expedite matters by sending them to begin with. | |
252b5132 RH |
6845 | |
6846 | To enable us to fix the bug, you should include all these things: | |
6847 | ||
6848 | @itemize @bullet | |
6849 | @item | |
ff5dcc92 | 6850 | The version of @command{ld}. @command{ld} announces it if you start it with |
252b5132 RH |
6851 | the @samp{--version} argument. |
6852 | ||
6853 | Without this, we will not know whether there is any point in looking for | |
ff5dcc92 | 6854 | the bug in the current version of @command{ld}. |
252b5132 RH |
6855 | |
6856 | @item | |
ff5dcc92 | 6857 | Any patches you may have applied to the @command{ld} source, including any |
252b5132 RH |
6858 | patches made to the @code{BFD} library. |
6859 | ||
6860 | @item | |
6861 | The type of machine you are using, and the operating system name and | |
6862 | version number. | |
6863 | ||
6864 | @item | |
ff5dcc92 | 6865 | What compiler (and its version) was used to compile @command{ld}---e.g. |
252b5132 RH |
6866 | ``@code{gcc-2.7}''. |
6867 | ||
6868 | @item | |
6869 | The command arguments you gave the linker to link your example and | |
6870 | observe the bug. To guarantee you will not omit something important, | |
6871 | list them all. A copy of the Makefile (or the output from make) is | |
6872 | sufficient. | |
6873 | ||
6874 | If we were to try to guess the arguments, we would probably guess wrong | |
6875 | and then we might not encounter the bug. | |
6876 | ||
6877 | @item | |
6878 | A complete input file, or set of input files, that will reproduce the | |
b553b183 NC |
6879 | bug. It is generally most helpful to send the actual object files |
6880 | provided that they are reasonably small. Say no more than 10K. For | |
6881 | bigger files you can either make them available by FTP or HTTP or else | |
6882 | state that you are willing to send the object file(s) to whomever | |
6883 | requests them. (Note - your email will be going to a mailing list, so | |
6884 | we do not want to clog it up with large attachments). But small | |
6885 | attachments are best. | |
252b5132 RH |
6886 | |
6887 | If the source files were assembled using @code{gas} or compiled using | |
6888 | @code{gcc}, then it may be OK to send the source files rather than the | |
6889 | object files. In this case, be sure to say exactly what version of | |
6890 | @code{gas} or @code{gcc} was used to produce the object files. Also say | |
6891 | how @code{gas} or @code{gcc} were configured. | |
6892 | ||
6893 | @item | |
6894 | A description of what behavior you observe that you believe is | |
6895 | incorrect. For example, ``It gets a fatal signal.'' | |
6896 | ||
ff5dcc92 | 6897 | Of course, if the bug is that @command{ld} gets a fatal signal, then we |
252b5132 RH |
6898 | will certainly notice it. But if the bug is incorrect output, we might |
6899 | not notice unless it is glaringly wrong. You might as well not give us | |
6900 | a chance to make a mistake. | |
6901 | ||
6902 | Even if the problem you experience is a fatal signal, you should still | |
6903 | say so explicitly. Suppose something strange is going on, such as, your | |
b45619c0 | 6904 | copy of @command{ld} is out of sync, or you have encountered a bug in the |
252b5132 RH |
6905 | C library on your system. (This has happened!) Your copy might crash |
6906 | and ours would not. If you told us to expect a crash, then when ours | |
6907 | fails to crash, we would know that the bug was not happening for us. If | |
6908 | you had not told us to expect a crash, then we would not be able to draw | |
6909 | any conclusion from our observations. | |
6910 | ||
6911 | @item | |
ff5dcc92 | 6912 | If you wish to suggest changes to the @command{ld} source, send us context |
252b5132 RH |
6913 | diffs, as generated by @code{diff} with the @samp{-u}, @samp{-c}, or |
6914 | @samp{-p} option. Always send diffs from the old file to the new file. | |
ff5dcc92 | 6915 | If you even discuss something in the @command{ld} source, refer to it by |
252b5132 RH |
6916 | context, not by line number. |
6917 | ||
6918 | The line numbers in our development sources will not match those in your | |
6919 | sources. Your line numbers would convey no useful information to us. | |
6920 | @end itemize | |
6921 | ||
6922 | Here are some things that are not necessary: | |
6923 | ||
6924 | @itemize @bullet | |
6925 | @item | |
6926 | A description of the envelope of the bug. | |
6927 | ||
6928 | Often people who encounter a bug spend a lot of time investigating | |
6929 | which changes to the input file will make the bug go away and which | |
6930 | changes will not affect it. | |
6931 | ||
6932 | This is often time consuming and not very useful, because the way we | |
6933 | will find the bug is by running a single example under the debugger | |
6934 | with breakpoints, not by pure deduction from a series of examples. | |
6935 | We recommend that you save your time for something else. | |
6936 | ||
6937 | Of course, if you can find a simpler example to report @emph{instead} | |
6938 | of the original one, that is a convenience for us. Errors in the | |
6939 | output will be easier to spot, running under the debugger will take | |
6940 | less time, and so on. | |
6941 | ||
6942 | However, simplification is not vital; if you do not want to do this, | |
6943 | report the bug anyway and send us the entire test case you used. | |
6944 | ||
6945 | @item | |
6946 | A patch for the bug. | |
6947 | ||
6948 | A patch for the bug does help us if it is a good one. But do not omit | |
6949 | the necessary information, such as the test case, on the assumption that | |
6950 | a patch is all we need. We might see problems with your patch and decide | |
6951 | to fix the problem another way, or we might not understand it at all. | |
6952 | ||
ff5dcc92 | 6953 | Sometimes with a program as complicated as @command{ld} it is very hard to |
252b5132 RH |
6954 | construct an example that will make the program follow a certain path |
6955 | through the code. If you do not send us the example, we will not be | |
6956 | able to construct one, so we will not be able to verify that the bug is | |
6957 | fixed. | |
6958 | ||
6959 | And if we cannot understand what bug you are trying to fix, or why your | |
6960 | patch should be an improvement, we will not install it. A test case will | |
6961 | help us to understand. | |
6962 | ||
6963 | @item | |
6964 | A guess about what the bug is or what it depends on. | |
6965 | ||
6966 | Such guesses are usually wrong. Even we cannot guess right about such | |
6967 | things without first using the debugger to find the facts. | |
6968 | @end itemize | |
6969 | ||
6970 | @node MRI | |
6971 | @appendix MRI Compatible Script Files | |
6972 | @cindex MRI compatibility | |
ff5dcc92 SC |
6973 | To aid users making the transition to @sc{gnu} @command{ld} from the MRI |
6974 | linker, @command{ld} can use MRI compatible linker scripts as an | |
252b5132 RH |
6975 | alternative to the more general-purpose linker scripting language |
6976 | described in @ref{Scripts}. MRI compatible linker scripts have a much | |
6977 | simpler command set than the scripting language otherwise used with | |
ff5dcc92 | 6978 | @command{ld}. @sc{gnu} @command{ld} supports the most commonly used MRI |
252b5132 RH |
6979 | linker commands; these commands are described here. |
6980 | ||
6981 | In general, MRI scripts aren't of much use with the @code{a.out} object | |
6982 | file format, since it only has three sections and MRI scripts lack some | |
6983 | features to make use of them. | |
6984 | ||
6985 | You can specify a file containing an MRI-compatible script using the | |
6986 | @samp{-c} command-line option. | |
6987 | ||
6988 | Each command in an MRI-compatible script occupies its own line; each | |
6989 | command line starts with the keyword that identifies the command (though | |
6990 | blank lines are also allowed for punctuation). If a line of an | |
ff5dcc92 | 6991 | MRI-compatible script begins with an unrecognized keyword, @command{ld} |
252b5132 RH |
6992 | issues a warning message, but continues processing the script. |
6993 | ||
6994 | Lines beginning with @samp{*} are comments. | |
6995 | ||
6996 | You can write these commands using all upper-case letters, or all | |
6997 | lower case; for example, @samp{chip} is the same as @samp{CHIP}. | |
6998 | The following list shows only the upper-case form of each command. | |
6999 | ||
7000 | @table @code | |
7001 | @cindex @code{ABSOLUTE} (MRI) | |
7002 | @item ABSOLUTE @var{secname} | |
7003 | @itemx ABSOLUTE @var{secname}, @var{secname}, @dots{} @var{secname} | |
ff5dcc92 | 7004 | Normally, @command{ld} includes in the output file all sections from all |
252b5132 RH |
7005 | the input files. However, in an MRI-compatible script, you can use the |
7006 | @code{ABSOLUTE} command to restrict the sections that will be present in | |
7007 | your output program. If the @code{ABSOLUTE} command is used at all in a | |
7008 | script, then only the sections named explicitly in @code{ABSOLUTE} | |
7009 | commands will appear in the linker output. You can still use other | |
7010 | input sections (whatever you select on the command line, or using | |
7011 | @code{LOAD}) to resolve addresses in the output file. | |
7012 | ||
7013 | @cindex @code{ALIAS} (MRI) | |
7014 | @item ALIAS @var{out-secname}, @var{in-secname} | |
7015 | Use this command to place the data from input section @var{in-secname} | |
7016 | in a section called @var{out-secname} in the linker output file. | |
7017 | ||
7018 | @var{in-secname} may be an integer. | |
7019 | ||
7020 | @cindex @code{ALIGN} (MRI) | |
7021 | @item ALIGN @var{secname} = @var{expression} | |
7022 | Align the section called @var{secname} to @var{expression}. The | |
7023 | @var{expression} should be a power of two. | |
7024 | ||
7025 | @cindex @code{BASE} (MRI) | |
7026 | @item BASE @var{expression} | |
7027 | Use the value of @var{expression} as the lowest address (other than | |
7028 | absolute addresses) in the output file. | |
7029 | ||
7030 | @cindex @code{CHIP} (MRI) | |
7031 | @item CHIP @var{expression} | |
7032 | @itemx CHIP @var{expression}, @var{expression} | |
7033 | This command does nothing; it is accepted only for compatibility. | |
7034 | ||
7035 | @cindex @code{END} (MRI) | |
7036 | @item END | |
7037 | This command does nothing whatever; it's only accepted for compatibility. | |
7038 | ||
7039 | @cindex @code{FORMAT} (MRI) | |
7040 | @item FORMAT @var{output-format} | |
7041 | Similar to the @code{OUTPUT_FORMAT} command in the more general linker | |
a1ab1d2a | 7042 | language, but restricted to one of these output formats: |
252b5132 RH |
7043 | |
7044 | @enumerate | |
a1ab1d2a | 7045 | @item |
252b5132 RH |
7046 | S-records, if @var{output-format} is @samp{S} |
7047 | ||
7048 | @item | |
7049 | IEEE, if @var{output-format} is @samp{IEEE} | |
7050 | ||
7051 | @item | |
7052 | COFF (the @samp{coff-m68k} variant in BFD), if @var{output-format} is | |
7053 | @samp{COFF} | |
7054 | @end enumerate | |
7055 | ||
7056 | @cindex @code{LIST} (MRI) | |
7057 | @item LIST @var{anything}@dots{} | |
7058 | Print (to the standard output file) a link map, as produced by the | |
ff5dcc92 | 7059 | @command{ld} command-line option @samp{-M}. |
252b5132 RH |
7060 | |
7061 | The keyword @code{LIST} may be followed by anything on the | |
7062 | same line, with no change in its effect. | |
7063 | ||
7064 | @cindex @code{LOAD} (MRI) | |
7065 | @item LOAD @var{filename} | |
7066 | @itemx LOAD @var{filename}, @var{filename}, @dots{} @var{filename} | |
7067 | Include one or more object file @var{filename} in the link; this has the | |
ff5dcc92 | 7068 | same effect as specifying @var{filename} directly on the @command{ld} |
252b5132 RH |
7069 | command line. |
7070 | ||
7071 | @cindex @code{NAME} (MRI) | |
7072 | @item NAME @var{output-name} | |
ff5dcc92 | 7073 | @var{output-name} is the name for the program produced by @command{ld}; the |
252b5132 RH |
7074 | MRI-compatible command @code{NAME} is equivalent to the command-line |
7075 | option @samp{-o} or the general script language command @code{OUTPUT}. | |
7076 | ||
7077 | @cindex @code{ORDER} (MRI) | |
7078 | @item ORDER @var{secname}, @var{secname}, @dots{} @var{secname} | |
7079 | @itemx ORDER @var{secname} @var{secname} @var{secname} | |
ff5dcc92 | 7080 | Normally, @command{ld} orders the sections in its output file in the |
252b5132 RH |
7081 | order in which they first appear in the input files. In an MRI-compatible |
7082 | script, you can override this ordering with the @code{ORDER} command. The | |
7083 | sections you list with @code{ORDER} will appear first in your output | |
7084 | file, in the order specified. | |
7085 | ||
7086 | @cindex @code{PUBLIC} (MRI) | |
7087 | @item PUBLIC @var{name}=@var{expression} | |
7088 | @itemx PUBLIC @var{name},@var{expression} | |
7089 | @itemx PUBLIC @var{name} @var{expression} | |
7090 | Supply a value (@var{expression}) for external symbol | |
7091 | @var{name} used in the linker input files. | |
7092 | ||
7093 | @cindex @code{SECT} (MRI) | |
7094 | @item SECT @var{secname}, @var{expression} | |
7095 | @itemx SECT @var{secname}=@var{expression} | |
7096 | @itemx SECT @var{secname} @var{expression} | |
7097 | You can use any of these three forms of the @code{SECT} command to | |
7098 | specify the start address (@var{expression}) for section @var{secname}. | |
7099 | If you have more than one @code{SECT} statement for the same | |
7100 | @var{secname}, only the @emph{first} sets the start address. | |
7101 | @end table | |
7102 | ||
36f63dca | 7103 | @include fdl.texi |
704c465c | 7104 | |
370b66a1 CD |
7105 | @node LD Index |
7106 | @unnumbered LD Index | |
252b5132 RH |
7107 | |
7108 | @printindex cp | |
7109 | ||
7110 | @tex | |
7111 | % I think something like @colophon should be in texinfo. In the | |
7112 | % meantime: | |
7113 | \long\def\colophon{\hbox to0pt{}\vfill | |
7114 | \centerline{The body of this manual is set in} | |
7115 | \centerline{\fontname\tenrm,} | |
7116 | \centerline{with headings in {\bf\fontname\tenbf}} | |
7117 | \centerline{and examples in {\tt\fontname\tentt}.} | |
7118 | \centerline{{\it\fontname\tenit\/} and} | |
7119 | \centerline{{\sl\fontname\tensl\/}} | |
7120 | \centerline{are used for emphasis.}\vfill} | |
7121 | \page\colophon | |
7122 | % Blame: doc@cygnus.com, 28mar91. | |
7123 | @end tex | |
7124 | ||
252b5132 | 7125 | @bye |