]>
Commit | Line | Data |
---|---|---|
252b5132 RH |
1 | \input texinfo |
2 | @setfilename ld.info | |
b90efa5b | 3 | @c Copyright (C) 1991-2015 Free Software Foundation, Inc. |
252b5132 | 4 | @syncodeindex ky cp |
dff70155 | 5 | @c man begin INCLUDE |
252b5132 RH |
6 | @include configdoc.texi |
7 | @c (configdoc.texi is generated by the Makefile) | |
c428fa83 | 8 | @include bfdver.texi |
dff70155 | 9 | @c man end |
252b5132 RH |
10 | |
11 | @c @smallbook | |
12 | ||
ff5dcc92 SC |
13 | @macro gcctabopt{body} |
14 | @code{\body\} | |
15 | @end macro | |
16 | ||
0285c67d NC |
17 | @c man begin NAME |
18 | @ifset man | |
19 | @c Configure for the generation of man pages | |
20 | @set UsesEnvVars | |
21 | @set GENERIC | |
0285c67d | 22 | @set ARM |
ac145307 | 23 | @set C6X |
49fa1e15 | 24 | @set H8300 |
0285c67d | 25 | @set HPPA |
0285c67d | 26 | @set I960 |
0285c67d | 27 | @set M68HC11 |
7fb9f789 | 28 | @set M68K |
833794fc | 29 | @set MIPS |
3c3bdf30 | 30 | @set MMIX |
2469cfa2 | 31 | @set MSP430 |
35c08157 | 32 | @set NDS32 |
78058a5e | 33 | @set NIOSII |
2a60a7a8 AM |
34 | @set POWERPC |
35 | @set POWERPC64 | |
49fa1e15 AM |
36 | @set Renesas |
37 | @set SPU | |
38 | @set TICOFF | |
2ca22b03 | 39 | @set WIN32 |
e0001a05 | 40 | @set XTENSA |
0285c67d NC |
41 | @end ifset |
42 | @c man end | |
43 | ||
9160ea82 AM |
44 | @ifnottex |
45 | @dircategory Software development | |
46 | @direntry | |
252b5132 | 47 | * Ld: (ld). The GNU linker. |
9160ea82 AM |
48 | @end direntry |
49 | @end ifnottex | |
252b5132 | 50 | |
0e9517a9 | 51 | @copying |
e49e529d JM |
52 | This file documents the @sc{gnu} linker LD |
53 | @ifset VERSION_PACKAGE | |
54 | @value{VERSION_PACKAGE} | |
55 | @end ifset | |
56 | version @value{VERSION}. | |
252b5132 | 57 | |
b90efa5b | 58 | Copyright @copyright{} 1991-2015 Free Software Foundation, Inc. |
252b5132 | 59 | |
cf055d54 | 60 | Permission is granted to copy, distribute and/or modify this document |
793c5807 | 61 | under the terms of the GNU Free Documentation License, Version 1.3 |
cf055d54 NC |
62 | or any later version published by the Free Software Foundation; |
63 | with no Invariant Sections, with no Front-Cover Texts, and with no | |
64 | Back-Cover Texts. A copy of the license is included in the | |
36f63dca | 65 | section entitled ``GNU Free Documentation License''. |
0e9517a9 | 66 | @end copying |
252b5132 RH |
67 | @iftex |
68 | @finalout | |
69 | @setchapternewpage odd | |
71ba23f6 | 70 | @settitle The GNU linker |
252b5132 | 71 | @titlepage |
71ba23f6 | 72 | @title The GNU linker |
252b5132 | 73 | @sp 1 |
e49e529d JM |
74 | @subtitle @code{ld} |
75 | @ifset VERSION_PACKAGE | |
76 | @subtitle @value{VERSION_PACKAGE} | |
77 | @end ifset | |
252b5132 RH |
78 | @subtitle Version @value{VERSION} |
79 | @author Steve Chamberlain | |
80 | @author Ian Lance Taylor | |
252b5132 RH |
81 | @page |
82 | ||
83 | @tex | |
84 | {\parskip=0pt | |
704c465c NC |
85 | \hfill Red Hat Inc\par |
86 | \hfill nickc\@credhat.com, doc\@redhat.com\par | |
71ba23f6 | 87 | \hfill {\it The GNU linker}\par |
252b5132 RH |
88 | \hfill Edited by Jeffrey Osier (jeffrey\@cygnus.com)\par |
89 | } | |
90 | \global\parindent=0pt % Steve likes it this way. | |
91 | @end tex | |
92 | ||
93 | @vskip 0pt plus 1filll | |
0285c67d | 94 | @c man begin COPYRIGHT |
b90efa5b | 95 | Copyright @copyright{} 1991-2015 Free Software Foundation, Inc. |
252b5132 | 96 | |
0285c67d | 97 | Permission is granted to copy, distribute and/or modify this document |
793c5807 | 98 | under the terms of the GNU Free Documentation License, Version 1.3 |
0285c67d NC |
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 | 119 | This document is distributed under the terms of the GNU Free |
793c5807 NC |
120 | Documentation License version 1.3. A copy of the license is included |
121 | in the 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 | |
93fd0973 SC |
143 | @ifset M68HC11 |
144 | * M68HC11/68HC12:: ld and the Motorola 68HC11 and 68HC12 families | |
145 | @end ifset | |
7ca01ed9 NC |
146 | @ifset HPPA |
147 | * HPPA ELF32:: ld and HPPA 32-bit ELF | |
148 | @end ifset | |
7fb9f789 NC |
149 | @ifset M68K |
150 | * M68K:: ld and Motorola 68K family | |
151 | @end ifset | |
833794fc MR |
152 | @ifset MIPS |
153 | * MIPS:: ld and MIPS family | |
154 | @end ifset | |
2a60a7a8 AM |
155 | @ifset POWERPC |
156 | * PowerPC ELF32:: ld and PowerPC 32-bit ELF Support | |
157 | @end ifset | |
158 | @ifset POWERPC64 | |
159 | * PowerPC64 ELF64:: ld and PowerPC64 64-bit ELF Support | |
160 | @end ifset | |
49fa1e15 AM |
161 | @ifset SPU |
162 | * SPU ELF:: ld and SPU ELF Support | |
163 | @end ifset | |
74459f0e TW |
164 | @ifset TICOFF |
165 | * TI COFF:: ld and the TI COFF | |
166 | @end ifset | |
2ca22b03 NC |
167 | @ifset WIN32 |
168 | * Win32:: ld and WIN32 (cygwin/mingw) | |
169 | @end ifset | |
e0001a05 NC |
170 | @ifset XTENSA |
171 | * Xtensa:: ld and Xtensa Processors | |
172 | @end ifset | |
252b5132 RH |
173 | @end ifclear |
174 | @ifclear SingleFormat | |
175 | * BFD:: BFD | |
176 | @end ifclear | |
177 | @c Following blank line required for remaining bug in makeinfo conds/menus | |
178 | ||
179 | * Reporting Bugs:: Reporting Bugs | |
180 | * MRI:: MRI Compatible Script Files | |
704c465c | 181 | * GNU Free Documentation License:: GNU Free Documentation License |
370b66a1 | 182 | * LD Index:: LD Index |
252b5132 | 183 | @end menu |
84ec0e6d | 184 | @end ifnottex |
252b5132 RH |
185 | |
186 | @node Overview | |
187 | @chapter Overview | |
188 | ||
189 | @cindex @sc{gnu} linker | |
190 | @cindex what is this? | |
0285c67d | 191 | |
0879a67a | 192 | @ifset man |
0285c67d | 193 | @c man begin SYNOPSIS |
ff5dcc92 | 194 | ld [@b{options}] @var{objfile} @dots{} |
0285c67d NC |
195 | @c man end |
196 | ||
197 | @c man begin SEEALSO | |
198 | ar(1), nm(1), objcopy(1), objdump(1), readelf(1) and | |
199 | the Info entries for @file{binutils} and | |
200 | @file{ld}. | |
201 | @c man end | |
202 | @end ifset | |
203 | ||
204 | @c man begin DESCRIPTION | |
205 | ||
ff5dcc92 | 206 | @command{ld} combines a number of object and archive files, relocates |
252b5132 | 207 | their data and ties up symbol references. Usually the last step in |
ff5dcc92 | 208 | compiling a program is to run @command{ld}. |
252b5132 | 209 | |
ff5dcc92 | 210 | @command{ld} accepts Linker Command Language files written in |
252b5132 RH |
211 | a superset of AT&T's Link Editor Command Language syntax, |
212 | to provide explicit and total control over the linking process. | |
213 | ||
0285c67d NC |
214 | @ifset man |
215 | @c For the man only | |
ece2d90e | 216 | This man page does not describe the command language; see the |
71ba23f6 NC |
217 | @command{ld} entry in @code{info} for full details on the command |
218 | language and on other aspects of the GNU linker. | |
0285c67d NC |
219 | @end ifset |
220 | ||
252b5132 | 221 | @ifclear SingleFormat |
ff5dcc92 SC |
222 | This version of @command{ld} uses the general purpose BFD libraries |
223 | to operate on object files. This allows @command{ld} to read, combine, and | |
252b5132 RH |
224 | write object files in many different formats---for example, COFF or |
225 | @code{a.out}. Different formats may be linked together to produce any | |
226 | available kind of object file. @xref{BFD}, for more information. | |
227 | @end ifclear | |
228 | ||
229 | Aside from its flexibility, the @sc{gnu} linker is more helpful than other | |
230 | linkers in providing diagnostic information. Many linkers abandon | |
231 | execution immediately upon encountering an error; whenever possible, | |
ff5dcc92 | 232 | @command{ld} continues executing, allowing you to identify other errors |
252b5132 RH |
233 | (or, in some cases, to get an output file in spite of the error). |
234 | ||
0285c67d NC |
235 | @c man end |
236 | ||
252b5132 RH |
237 | @node Invocation |
238 | @chapter Invocation | |
239 | ||
0285c67d NC |
240 | @c man begin DESCRIPTION |
241 | ||
ff5dcc92 | 242 | The @sc{gnu} linker @command{ld} is meant to cover a broad range of situations, |
252b5132 RH |
243 | and to be as compatible as possible with other linkers. As a result, |
244 | you have many choices to control its behavior. | |
245 | ||
0285c67d NC |
246 | @c man end |
247 | ||
252b5132 RH |
248 | @ifset UsesEnvVars |
249 | @menu | |
250 | * Options:: Command Line Options | |
251 | * Environment:: Environment Variables | |
252 | @end menu | |
253 | ||
254 | @node Options | |
255 | @section Command Line Options | |
256 | @end ifset | |
257 | ||
258 | @cindex command line | |
259 | @cindex options | |
0285c67d NC |
260 | |
261 | @c man begin OPTIONS | |
262 | ||
252b5132 RH |
263 | The linker supports a plethora of command-line options, but in actual |
264 | practice few of them are used in any particular context. | |
265 | @cindex standard Unix system | |
ff5dcc92 | 266 | For instance, a frequent use of @command{ld} is to link standard Unix |
252b5132 RH |
267 | object files on a standard, supported Unix system. On such a system, to |
268 | link a file @code{hello.o}: | |
269 | ||
270 | @smallexample | |
271 | ld -o @var{output} /lib/crt0.o hello.o -lc | |
272 | @end smallexample | |
273 | ||
ff5dcc92 | 274 | This tells @command{ld} to produce a file called @var{output} as the |
252b5132 RH |
275 | result of linking the file @code{/lib/crt0.o} with @code{hello.o} and |
276 | the library @code{libc.a}, which will come from the standard search | |
277 | directories. (See the discussion of the @samp{-l} option below.) | |
278 | ||
ff5dcc92 | 279 | Some of the command-line options to @command{ld} may be specified at any |
511ab9e9 ILT |
280 | point in the command line. However, options which refer to files, such |
281 | as @samp{-l} or @samp{-T}, cause the file to be read at the point at | |
282 | which the option appears in the command line, relative to the object | |
283 | files and other file options. Repeating non-file options with a | |
284 | different argument will either have no further effect, or override prior | |
252b5132 RH |
285 | occurrences (those further to the left on the command line) of that |
286 | option. Options which may be meaningfully specified more than once are | |
287 | noted in the descriptions below. | |
288 | ||
289 | @cindex object files | |
511ab9e9 ILT |
290 | Non-option arguments are object files or archives which are to be linked |
291 | together. They may follow, precede, or be mixed in with command-line | |
292 | options, except that an object file argument may not be placed between | |
293 | an option and its argument. | |
252b5132 RH |
294 | |
295 | Usually the linker is invoked with at least one object file, but you can | |
296 | specify other forms of binary input files using @samp{-l}, @samp{-R}, | |
297 | and the script command language. If @emph{no} binary input files at all | |
298 | are specified, the linker does not produce any output, and issues the | |
299 | message @samp{No input files}. | |
300 | ||
36f63dca | 301 | If the linker cannot recognize the format of an object file, it will |
252b5132 RH |
302 | assume that it is a linker script. A script specified in this way |
303 | augments the main linker script used for the link (either the default | |
304 | linker script or the one specified by using @samp{-T}). This feature | |
305 | permits the linker to link against a file which appears to be an object | |
306 | or an archive, but actually merely defines some symbol values, or uses | |
53d25da6 AM |
307 | @code{INPUT} or @code{GROUP} to load other objects. Specifying a |
308 | script in this way merely augments the main linker script, with the | |
309 | extra commands placed after the main script; use the @samp{-T} option | |
310 | to replace the default linker script entirely, but note the effect of | |
311 | the @code{INSERT} command. @xref{Scripts}. | |
252b5132 RH |
312 | |
313 | For options whose names are a single letter, | |
314 | option arguments must either follow the option letter without intervening | |
315 | whitespace, or be given as separate arguments immediately following the | |
316 | option that requires them. | |
317 | ||
318 | For options whose names are multiple letters, either one dash or two can | |
e4897a32 | 319 | precede the option name; for example, @samp{-trace-symbol} and |
36f63dca | 320 | @samp{--trace-symbol} are equivalent. Note---there is one exception to |
e4897a32 | 321 | this rule. Multiple letter options that start with a lower case 'o' can |
ba1be17e | 322 | only be preceded by two dashes. This is to reduce confusion with the |
e4897a32 NC |
323 | @samp{-o} option. So for example @samp{-omagic} sets the output file |
324 | name to @samp{magic} whereas @samp{--omagic} sets the NMAGIC flag on the | |
325 | output. | |
326 | ||
327 | Arguments to multiple-letter options must either be separated from the | |
328 | option name by an equals sign, or be given as separate arguments | |
329 | immediately following the option that requires them. For example, | |
330 | @samp{--trace-symbol foo} and @samp{--trace-symbol=foo} are equivalent. | |
331 | Unique abbreviations of the names of multiple-letter options are | |
332 | accepted. | |
252b5132 | 333 | |
36f63dca NC |
334 | Note---if the linker is being invoked indirectly, via a compiler driver |
335 | (e.g. @samp{gcc}) then all the linker command line options should be | |
fa19fce0 NC |
336 | prefixed by @samp{-Wl,} (or whatever is appropriate for the particular |
337 | compiler driver) like this: | |
4e53152f NC |
338 | |
339 | @smallexample | |
2509a395 | 340 | gcc -Wl,--start-group foo.o bar.o -Wl,--end-group |
4e53152f NC |
341 | @end smallexample |
342 | ||
343 | This is important, because otherwise the compiler driver program may | |
2509a395 SL |
344 | silently drop the linker options, resulting in a bad link. Confusion |
345 | may also arise when passing options that require values through a | |
346 | driver, as the use of a space between option and argument acts as | |
347 | a separator, and causes the driver to pass only the option to the linker | |
348 | and the argument to the compiler. In this case, it is simplest to use | |
349 | the joined forms of both single- and multiple-letter options, such as: | |
350 | ||
351 | @smallexample | |
352 | gcc foo.o bar.o -Wl,-eENTRY -Wl,-Map=a.map | |
353 | @end smallexample | |
4e53152f NC |
354 | |
355 | Here is a table of the generic command line switches accepted by the GNU | |
356 | linker: | |
357 | ||
ff5dcc92 | 358 | @table @gcctabopt |
38fc1cb1 | 359 | @include at-file.texi |
dff70155 | 360 | |
2509a395 SL |
361 | @kindex -a @var{keyword} |
362 | @item -a @var{keyword} | |
252b5132 RH |
363 | This option is supported for HP/UX compatibility. The @var{keyword} |
364 | argument must be one of the strings @samp{archive}, @samp{shared}, or | |
365 | @samp{default}. @samp{-aarchive} is functionally equivalent to | |
366 | @samp{-Bstatic}, and the other two keywords are functionally equivalent | |
367 | to @samp{-Bdynamic}. This option may be used any number of times. | |
368 | ||
7ee314fa AM |
369 | @kindex --audit @var{AUDITLIB} |
370 | @item --audit @var{AUDITLIB} | |
371 | Adds @var{AUDITLIB} to the @code{DT_AUDIT} entry of the dynamic section. | |
372 | @var{AUDITLIB} is not checked for existence, nor will it use the DT_SONAME | |
373 | specified in the library. If specified multiple times @code{DT_AUDIT} | |
374 | will contain a colon separated list of audit interfaces to use. If the linker | |
375 | finds an object with an audit entry while searching for shared libraries, | |
9d5777a3 | 376 | it will add a corresponding @code{DT_DEPAUDIT} entry in the output file. |
7ee314fa | 377 | This option is only meaningful on ELF platforms supporting the rtld-audit |
9d5777a3 | 378 | interface. |
7ee314fa | 379 | |
252b5132 RH |
380 | @ifset I960 |
381 | @cindex architectures | |
2509a395 SL |
382 | @kindex -A @var{arch} |
383 | @item -A @var{architecture} | |
252b5132 RH |
384 | @kindex --architecture=@var{arch} |
385 | @itemx --architecture=@var{architecture} | |
ff5dcc92 SC |
386 | In the current release of @command{ld}, this option is useful only for the |
387 | Intel 960 family of architectures. In that @command{ld} configuration, the | |
252b5132 RH |
388 | @var{architecture} argument identifies the particular architecture in |
389 | the 960 family, enabling some safeguards and modifying the | |
ff5dcc92 | 390 | archive-library search path. @xref{i960,,@command{ld} and the Intel 960 |
252b5132 RH |
391 | family}, for details. |
392 | ||
ff5dcc92 | 393 | Future releases of @command{ld} may support similar functionality for |
252b5132 RH |
394 | other architecture families. |
395 | @end ifset | |
396 | ||
397 | @ifclear SingleFormat | |
398 | @cindex binary input format | |
399 | @kindex -b @var{format} | |
400 | @kindex --format=@var{format} | |
401 | @cindex input format | |
402 | @cindex input format | |
403 | @item -b @var{input-format} | |
404 | @itemx --format=@var{input-format} | |
ff5dcc92 SC |
405 | @command{ld} may be configured to support more than one kind of object |
406 | file. If your @command{ld} is configured this way, you can use the | |
252b5132 | 407 | @samp{-b} option to specify the binary format for input object files |
ff5dcc92 | 408 | that follow this option on the command line. Even when @command{ld} is |
252b5132 | 409 | configured to support alternative object formats, you don't usually need |
ff5dcc92 | 410 | to specify this, as @command{ld} should be configured to expect as a |
252b5132 RH |
411 | default input format the most usual format on each machine. |
412 | @var{input-format} is a text string, the name of a particular format | |
413 | supported by the BFD libraries. (You can list the available binary | |
414 | formats with @samp{objdump -i}.) | |
415 | @xref{BFD}. | |
416 | ||
417 | You may want to use this option if you are linking files with an unusual | |
418 | binary format. You can also use @samp{-b} to switch formats explicitly (when | |
419 | linking object files of different formats), by including | |
420 | @samp{-b @var{input-format}} before each group of object files in a | |
a1ab1d2a | 421 | particular format. |
252b5132 RH |
422 | |
423 | The default format is taken from the environment variable | |
424 | @code{GNUTARGET}. | |
425 | @ifset UsesEnvVars | |
426 | @xref{Environment}. | |
427 | @end ifset | |
428 | You can also define the input format from a script, using the command | |
0285c67d NC |
429 | @code{TARGET}; |
430 | @ifclear man | |
431 | see @ref{Format Commands}. | |
432 | @end ifclear | |
252b5132 RH |
433 | @end ifclear |
434 | ||
435 | @kindex -c @var{MRI-cmdfile} | |
436 | @kindex --mri-script=@var{MRI-cmdfile} | |
437 | @cindex compatibility, MRI | |
438 | @item -c @var{MRI-commandfile} | |
439 | @itemx --mri-script=@var{MRI-commandfile} | |
ff5dcc92 | 440 | For compatibility with linkers produced by MRI, @command{ld} accepts script |
252b5132 | 441 | files written in an alternate, restricted command language, described in |
0285c67d NC |
442 | @ifclear man |
443 | @ref{MRI,,MRI Compatible Script Files}. | |
444 | @end ifclear | |
445 | @ifset man | |
446 | the MRI Compatible Script Files section of GNU ld documentation. | |
447 | @end ifset | |
448 | Introduce MRI script files with | |
252b5132 | 449 | the option @samp{-c}; use the @samp{-T} option to run linker |
ff5dcc92 SC |
450 | scripts written in the general-purpose @command{ld} scripting language. |
451 | If @var{MRI-cmdfile} does not exist, @command{ld} looks for it in the directories | |
252b5132 RH |
452 | specified by any @samp{-L} options. |
453 | ||
454 | @cindex common allocation | |
455 | @kindex -d | |
456 | @kindex -dc | |
457 | @kindex -dp | |
a1ab1d2a | 458 | @item -d |
252b5132 RH |
459 | @itemx -dc |
460 | @itemx -dp | |
461 | These three options are equivalent; multiple forms are supported for | |
462 | compatibility with other linkers. They assign space to common symbols | |
463 | even if a relocatable output file is specified (with @samp{-r}). The | |
464 | script command @code{FORCE_COMMON_ALLOCATION} has the same effect. | |
465 | @xref{Miscellaneous Commands}. | |
466 | ||
7ee314fa AM |
467 | @kindex --depaudit @var{AUDITLIB} |
468 | @kindex -P @var{AUDITLIB} | |
469 | @item --depaudit @var{AUDITLIB} | |
470 | @itemx -P @var{AUDITLIB} | |
471 | Adds @var{AUDITLIB} to the @code{DT_DEPAUDIT} entry of the dynamic section. | |
472 | @var{AUDITLIB} is not checked for existence, nor will it use the DT_SONAME | |
473 | specified in the library. If specified multiple times @code{DT_DEPAUDIT} | |
474 | will contain a colon separated list of audit interfaces to use. This | |
475 | option is only meaningful on ELF platforms supporting the rtld-audit interface. | |
9d5777a3 | 476 | The -P option is provided for Solaris compatibility. |
7ee314fa | 477 | |
252b5132 RH |
478 | @cindex entry point, from command line |
479 | @kindex -e @var{entry} | |
480 | @kindex --entry=@var{entry} | |
a1ab1d2a | 481 | @item -e @var{entry} |
252b5132 RH |
482 | @itemx --entry=@var{entry} |
483 | Use @var{entry} as the explicit symbol for beginning execution of your | |
484 | program, rather than the default entry point. If there is no symbol | |
485 | named @var{entry}, the linker will try to parse @var{entry} as a number, | |
486 | and use that as the entry address (the number will be interpreted in | |
487 | base 10; you may use a leading @samp{0x} for base 16, or a leading | |
488 | @samp{0} for base 8). @xref{Entry Point}, for a discussion of defaults | |
489 | and other ways of specifying the entry point. | |
490 | ||
b58f81ae DJ |
491 | @kindex --exclude-libs |
492 | @item --exclude-libs @var{lib},@var{lib},... | |
493 | Specifies a list of archive libraries from which symbols should not be automatically | |
e1c37eb5 | 494 | exported. The library names may be delimited by commas or colons. Specifying |
b58f81ae DJ |
495 | @code{--exclude-libs ALL} excludes symbols in all archive libraries from |
496 | automatic export. This option is available only for the i386 PE targeted | |
497 | port of the linker and for ELF targeted ports. For i386 PE, symbols | |
498 | explicitly listed in a .def file are still exported, regardless of this | |
499 | option. For ELF targeted ports, symbols affected by this option will | |
500 | be treated as hidden. | |
501 | ||
e1c37eb5 DK |
502 | @kindex --exclude-modules-for-implib |
503 | @item --exclude-modules-for-implib @var{module},@var{module},... | |
504 | Specifies a list of object files or archive members, from which symbols | |
505 | should not be automatically exported, but which should be copied wholesale | |
506 | into the import library being generated during the link. The module names | |
507 | may be delimited by commas or colons, and must match exactly the filenames | |
508 | used by @command{ld} to open the files; for archive members, this is simply | |
509 | the member name, but for object files the name listed must include and | |
510 | match precisely any path used to specify the input file on the linker's | |
511 | command-line. This option is available only for the i386 PE targeted port | |
512 | of the linker. Symbols explicitly listed in a .def file are still exported, | |
513 | regardless of this option. | |
514 | ||
252b5132 RH |
515 | @cindex dynamic symbol table |
516 | @kindex -E | |
517 | @kindex --export-dynamic | |
267e2722 | 518 | @kindex --no-export-dynamic |
252b5132 RH |
519 | @item -E |
520 | @itemx --export-dynamic | |
267e2722 CD |
521 | @itemx --no-export-dynamic |
522 | When creating a dynamically linked executable, using the @option{-E} | |
523 | option or the @option{--export-dynamic} option causes the linker to add | |
524 | all symbols to the dynamic symbol table. The dynamic symbol table is the | |
525 | set of symbols which are visible from dynamic objects at run time. | |
526 | ||
527 | If you do not use either of these options (or use the | |
528 | @option{--no-export-dynamic} option to restore the default behavior), the | |
529 | dynamic symbol table will normally contain only those symbols which are | |
530 | referenced by some dynamic object mentioned in the link. | |
252b5132 RH |
531 | |
532 | If you use @code{dlopen} to load a dynamic object which needs to refer | |
533 | back to the symbols defined by the program, rather than some other | |
534 | dynamic object, then you will probably need to use this option when | |
535 | linking the program itself. | |
536 | ||
55255dae | 537 | You can also use the dynamic list to control what symbols should |
cb840a31 | 538 | be added to the dynamic symbol table if the output format supports it. |
55255dae | 539 | See the description of @samp{--dynamic-list}. |
cb840a31 | 540 | |
8b747e1a DK |
541 | Note that this option is specific to ELF targeted ports. PE targets |
542 | support a similar function to export all symbols from a DLL or EXE; see | |
543 | the description of @samp{--export-all-symbols} below. | |
544 | ||
36f63dca | 545 | @ifclear SingleFormat |
252b5132 RH |
546 | @cindex big-endian objects |
547 | @cindex endianness | |
548 | @kindex -EB | |
549 | @item -EB | |
550 | Link big-endian objects. This affects the default output format. | |
551 | ||
552 | @cindex little-endian objects | |
553 | @kindex -EL | |
554 | @item -EL | |
555 | Link little-endian objects. This affects the default output format. | |
36f63dca | 556 | @end ifclear |
252b5132 | 557 | |
2509a395 SL |
558 | @kindex -f @var{name} |
559 | @kindex --auxiliary=@var{name} | |
560 | @item -f @var{name} | |
561 | @itemx --auxiliary=@var{name} | |
252b5132 RH |
562 | When creating an ELF shared object, set the internal DT_AUXILIARY field |
563 | to the specified name. This tells the dynamic linker that the symbol | |
564 | table of the shared object should be used as an auxiliary filter on the | |
565 | symbol table of the shared object @var{name}. | |
566 | ||
567 | If you later link a program against this filter object, then, when you | |
568 | run the program, the dynamic linker will see the DT_AUXILIARY field. If | |
569 | the dynamic linker resolves any symbols from the filter object, it will | |
570 | first check whether there is a definition in the shared object | |
571 | @var{name}. If there is one, it will be used instead of the definition | |
572 | in the filter object. The shared object @var{name} need not exist. | |
573 | Thus the shared object @var{name} may be used to provide an alternative | |
574 | implementation of certain functions, perhaps for debugging or for | |
575 | machine specific performance. | |
576 | ||
577 | This option may be specified more than once. The DT_AUXILIARY entries | |
578 | will be created in the order in which they appear on the command line. | |
579 | ||
2509a395 SL |
580 | @kindex -F @var{name} |
581 | @kindex --filter=@var{name} | |
252b5132 | 582 | @item -F @var{name} |
2509a395 | 583 | @itemx --filter=@var{name} |
252b5132 RH |
584 | When creating an ELF shared object, set the internal DT_FILTER field to |
585 | the specified name. This tells the dynamic linker that the symbol table | |
586 | of the shared object which is being created should be used as a filter | |
587 | on the symbol table of the shared object @var{name}. | |
588 | ||
589 | If you later link a program against this filter object, then, when you | |
590 | run the program, the dynamic linker will see the DT_FILTER field. The | |
591 | dynamic linker will resolve symbols according to the symbol table of the | |
592 | filter object as usual, but it will actually link to the definitions | |
593 | found in the shared object @var{name}. Thus the filter object can be | |
594 | used to select a subset of the symbols provided by the object | |
595 | @var{name}. | |
596 | ||
ff5dcc92 | 597 | Some older linkers used the @option{-F} option throughout a compilation |
252b5132 | 598 | toolchain for specifying object-file format for both input and output |
36f63dca NC |
599 | object files. |
600 | @ifclear SingleFormat | |
601 | The @sc{gnu} linker uses other mechanisms for this purpose: the | |
ece2d90e | 602 | @option{-b}, @option{--format}, @option{--oformat} options, the |
252b5132 | 603 | @code{TARGET} command in linker scripts, and the @code{GNUTARGET} |
36f63dca NC |
604 | environment variable. |
605 | @end ifclear | |
606 | The @sc{gnu} linker will ignore the @option{-F} option when not | |
607 | creating an ELF shared object. | |
252b5132 | 608 | |
3dbf70a2 | 609 | @cindex finalization function |
2509a395 SL |
610 | @kindex -fini=@var{name} |
611 | @item -fini=@var{name} | |
3dbf70a2 MM |
612 | When creating an ELF executable or shared object, call NAME when the |
613 | executable or shared object is unloaded, by setting DT_FINI to the | |
614 | address of the function. By default, the linker uses @code{_fini} as | |
615 | the function to call. | |
616 | ||
252b5132 RH |
617 | @kindex -g |
618 | @item -g | |
619 | Ignored. Provided for compatibility with other tools. | |
620 | ||
2509a395 SL |
621 | @kindex -G @var{value} |
622 | @kindex --gpsize=@var{value} | |
252b5132 | 623 | @cindex object size |
2509a395 | 624 | @item -G @var{value} |
252b5132 RH |
625 | @itemx --gpsize=@var{value} |
626 | Set the maximum size of objects to be optimized using the GP register to | |
627 | @var{size}. This is only meaningful for object file formats such as | |
e8044f35 | 628 | MIPS ELF that support putting large and small objects into different |
252b5132 RH |
629 | sections. This is ignored for other object file formats. |
630 | ||
631 | @cindex runtime library name | |
2509a395 | 632 | @kindex -h @var{name} |
252b5132 | 633 | @kindex -soname=@var{name} |
2509a395 | 634 | @item -h @var{name} |
252b5132 RH |
635 | @itemx -soname=@var{name} |
636 | When creating an ELF shared object, set the internal DT_SONAME field to | |
637 | the specified name. When an executable is linked with a shared object | |
638 | which has a DT_SONAME field, then when the executable is run the dynamic | |
639 | linker will attempt to load the shared object specified by the DT_SONAME | |
640 | field rather than the using the file name given to the linker. | |
641 | ||
642 | @kindex -i | |
643 | @cindex incremental link | |
644 | @item -i | |
645 | Perform an incremental link (same as option @samp{-r}). | |
646 | ||
3dbf70a2 | 647 | @cindex initialization function |
2509a395 SL |
648 | @kindex -init=@var{name} |
649 | @item -init=@var{name} | |
3dbf70a2 MM |
650 | When creating an ELF executable or shared object, call NAME when the |
651 | executable or shared object is loaded, by setting DT_INIT to the address | |
652 | of the function. By default, the linker uses @code{_init} as the | |
653 | function to call. | |
654 | ||
252b5132 | 655 | @cindex archive files, from cmd line |
2509a395 | 656 | @kindex -l @var{namespec} |
bcb674cf | 657 | @kindex --library=@var{namespec} |
2509a395 | 658 | @item -l @var{namespec} |
bcb674cf RS |
659 | @itemx --library=@var{namespec} |
660 | Add the archive or object file specified by @var{namespec} to the | |
661 | list of files to link. This option may be used any number of times. | |
662 | If @var{namespec} is of the form @file{:@var{filename}}, @command{ld} | |
07d8eb55 | 663 | will search the library path for a file called @var{filename}, otherwise it |
bcb674cf | 664 | will search the library path for a file called @file{lib@var{namespec}.a}. |
252b5132 | 665 | |
ff5dcc92 | 666 | On systems which support shared libraries, @command{ld} may also search for |
bcb674cf RS |
667 | files other than @file{lib@var{namespec}.a}. Specifically, on ELF |
668 | and SunOS systems, @command{ld} will search a directory for a library | |
669 | called @file{lib@var{namespec}.so} before searching for one called | |
670 | @file{lib@var{namespec}.a}. (By convention, a @code{.so} extension | |
671 | indicates a shared library.) Note that this behavior does not apply | |
672 | to @file{:@var{filename}}, which always specifies a file called | |
673 | @var{filename}. | |
252b5132 RH |
674 | |
675 | The linker will search an archive only once, at the location where it is | |
676 | specified on the command line. If the archive defines a symbol which | |
677 | was undefined in some object which appeared before the archive on the | |
678 | command line, the linker will include the appropriate file(s) from the | |
679 | archive. However, an undefined symbol in an object appearing later on | |
680 | the command line will not cause the linker to search the archive again. | |
681 | ||
ff5dcc92 | 682 | See the @option{-(} option for a way to force the linker to search |
252b5132 RH |
683 | archives multiple times. |
684 | ||
685 | You may list the same archive multiple times on the command line. | |
686 | ||
687 | @ifset GENERIC | |
688 | This type of archive searching is standard for Unix linkers. However, | |
ff5dcc92 | 689 | if you are using @command{ld} on AIX, note that it is different from the |
252b5132 RH |
690 | behaviour of the AIX linker. |
691 | @end ifset | |
692 | ||
693 | @cindex search directory, from cmd line | |
2509a395 | 694 | @kindex -L @var{dir} |
252b5132 | 695 | @kindex --library-path=@var{dir} |
2509a395 | 696 | @item -L @var{searchdir} |
252b5132 | 697 | @itemx --library-path=@var{searchdir} |
ff5dcc92 SC |
698 | Add path @var{searchdir} to the list of paths that @command{ld} will search |
699 | for archive libraries and @command{ld} control scripts. You may use this | |
252b5132 RH |
700 | option any number of times. The directories are searched in the order |
701 | in which they are specified on the command line. Directories specified | |
702 | on the command line are searched before the default directories. All | |
ff5dcc92 | 703 | @option{-L} options apply to all @option{-l} options, regardless of the |
7d24f02c KH |
704 | order in which the options appear. @option{-L} options do not affect |
705 | how @command{ld} searches for a linker script unless @option{-T} | |
706 | option is specified. | |
252b5132 | 707 | |
9c8ebd6a | 708 | If @var{searchdir} begins with @code{=}, then the @code{=} will be replaced |
b3b9c41d HPN |
709 | by the @dfn{sysroot prefix}, controlled by the @samp{--sysroot} option, or |
710 | specified when the linker is configured. | |
9c8ebd6a | 711 | |
252b5132 RH |
712 | @ifset UsesEnvVars |
713 | The default set of paths searched (without being specified with | |
ff5dcc92 | 714 | @samp{-L}) depends on which emulation mode @command{ld} is using, and in |
252b5132 RH |
715 | some cases also on how it was configured. @xref{Environment}. |
716 | @end ifset | |
717 | ||
718 | The paths can also be specified in a link script with the | |
719 | @code{SEARCH_DIR} command. Directories specified this way are searched | |
720 | at the point in which the linker script appears in the command line. | |
721 | ||
722 | @cindex emulation | |
723 | @kindex -m @var{emulation} | |
2509a395 | 724 | @item -m @var{emulation} |
252b5132 RH |
725 | Emulate the @var{emulation} linker. You can list the available |
726 | emulations with the @samp{--verbose} or @samp{-V} options. | |
727 | ||
728 | If the @samp{-m} option is not used, the emulation is taken from the | |
729 | @code{LDEMULATION} environment variable, if that is defined. | |
730 | ||
731 | Otherwise, the default emulation depends upon how the linker was | |
732 | configured. | |
733 | ||
734 | @cindex link map | |
735 | @kindex -M | |
736 | @kindex --print-map | |
737 | @item -M | |
738 | @itemx --print-map | |
739 | Print a link map to the standard output. A link map provides | |
740 | information about the link, including the following: | |
741 | ||
742 | @itemize @bullet | |
743 | @item | |
3b83e13a | 744 | Where object files are mapped into memory. |
252b5132 RH |
745 | @item |
746 | How common symbols are allocated. | |
747 | @item | |
748 | All archive members included in the link, with a mention of the symbol | |
749 | which caused the archive member to be brought in. | |
3b83e13a NC |
750 | @item |
751 | The values assigned to symbols. | |
752 | ||
753 | Note - symbols whose values are computed by an expression which | |
754 | involves a reference to a previous value of the same symbol may not | |
755 | have correct result displayed in the link map. This is because the | |
756 | linker discards intermediate results and only retains the final value | |
757 | of an expression. Under such circumstances the linker will display | |
758 | the final value enclosed by square brackets. Thus for example a | |
759 | linker script containing: | |
760 | ||
761 | @smallexample | |
762 | foo = 1 | |
763 | foo = foo * 4 | |
764 | foo = foo + 8 | |
765 | @end smallexample | |
766 | ||
767 | will produce the following output in the link map if the @option{-M} | |
768 | option is used: | |
769 | ||
770 | @smallexample | |
771 | 0x00000001 foo = 0x1 | |
772 | [0x0000000c] foo = (foo * 0x4) | |
773 | [0x0000000c] foo = (foo + 0x8) | |
774 | @end smallexample | |
775 | ||
776 | See @ref{Expressions} for more information about expressions in linker | |
777 | scripts. | |
252b5132 RH |
778 | @end itemize |
779 | ||
780 | @kindex -n | |
781 | @cindex read-only text | |
782 | @cindex NMAGIC | |
783 | @kindex --nmagic | |
784 | @item -n | |
785 | @itemx --nmagic | |
90f5d9d9 JZ |
786 | Turn off page alignment of sections, and disable linking against shared |
787 | libraries. If the output format supports Unix style magic numbers, | |
788 | mark the output as @code{NMAGIC}. | |
252b5132 RH |
789 | |
790 | @kindex -N | |
791 | @kindex --omagic | |
792 | @cindex read/write from cmd line | |
793 | @cindex OMAGIC | |
a1ab1d2a | 794 | @item -N |
252b5132 RH |
795 | @itemx --omagic |
796 | Set the text and data sections to be readable and writable. Also, do | |
63fd3b82 NC |
797 | not page-align the data segment, and disable linking against shared |
798 | libraries. If the output format supports Unix style magic numbers, | |
4d8907ac DS |
799 | mark the output as @code{OMAGIC}. Note: Although a writable text section |
800 | is allowed for PE-COFF targets, it does not conform to the format | |
801 | specification published by Microsoft. | |
63fd3b82 NC |
802 | |
803 | @kindex --no-omagic | |
804 | @cindex OMAGIC | |
805 | @item --no-omagic | |
806 | This option negates most of the effects of the @option{-N} option. It | |
807 | sets the text section to be read-only, and forces the data segment to | |
808 | be page-aligned. Note - this option does not enable linking against | |
809 | shared libraries. Use @option{-Bdynamic} for this. | |
252b5132 RH |
810 | |
811 | @kindex -o @var{output} | |
812 | @kindex --output=@var{output} | |
813 | @cindex naming the output file | |
814 | @item -o @var{output} | |
815 | @itemx --output=@var{output} | |
ff5dcc92 | 816 | Use @var{output} as the name for the program produced by @command{ld}; if this |
252b5132 RH |
817 | option is not specified, the name @file{a.out} is used by default. The |
818 | script command @code{OUTPUT} can also specify the output file name. | |
819 | ||
820 | @kindex -O @var{level} | |
821 | @cindex generating optimized output | |
822 | @item -O @var{level} | |
ff5dcc92 | 823 | If @var{level} is a numeric values greater than zero @command{ld} optimizes |
252b5132 | 824 | the output. This might take significantly longer and therefore probably |
98c503ac NC |
825 | should only be enabled for the final binary. At the moment this |
826 | option only affects ELF shared library generation. Future releases of | |
827 | the linker may make more use of this option. Also currently there is | |
828 | no difference in the linker's behaviour for different non-zero values | |
829 | of this option. Again this may change with future releases. | |
252b5132 | 830 | |
26278bb8 UD |
831 | @kindex --push-state |
832 | @cindex push state governing input file handling | |
833 | @item --push-state | |
834 | The @option{--push-state} allows to preserve the current state of the | |
835 | flags which govern the input file handling so that they can all be | |
836 | restored with one corresponding @option{--pop-state} option. | |
837 | ||
838 | The option which are covered are: @option{-Bdynamic}, @option{-Bstatic}, | |
839 | @option{-dn}, @option{-dy}, @option{-call_shared}, @option{-non_shared}, | |
840 | @option{-static}, @option{-N}, @option{-n}, @option{--whole-archive}, | |
841 | @option{--no-whole-archive}, @option{-r}, @option{-Ur}, | |
842 | @option{--copy-dt-needed-entries}, @option{--no-copy-dt-needed-entries}, | |
843 | @option{--as-needed}, @option{--no-as-needed}, and @option{-a}. | |
844 | ||
845 | One target for this option are specifications for @file{pkg-config}. When | |
846 | used with the @option{--libs} option all possibly needed libraries are | |
847 | listed and then possibly linked with all the time. It is better to return | |
848 | something as follows: | |
849 | ||
850 | @smallexample | |
851 | -Wl,--push-state,--as-needed -libone -libtwo -Wl,--pop-state | |
852 | @end smallexample | |
853 | ||
854 | @kindex --pop-state | |
855 | @cindex pop state governing input file handling | |
856 | Undoes the effect of --push-state, restores the previous values of the | |
857 | flags governing input file handling. | |
858 | ||
a712da20 NC |
859 | @kindex -q |
860 | @kindex --emit-relocs | |
861 | @cindex retain relocations in final executable | |
862 | @item -q | |
863 | @itemx --emit-relocs | |
ba1be17e | 864 | Leave relocation sections and contents in fully linked executables. |
a712da20 NC |
865 | Post link analysis and optimization tools may need this information in |
866 | order to perform correct modifications of executables. This results | |
867 | in larger executables. | |
868 | ||
dbab7a7b NC |
869 | This option is currently only supported on ELF platforms. |
870 | ||
4f471f39 RS |
871 | @kindex --force-dynamic |
872 | @cindex forcing the creation of dynamic sections | |
873 | @item --force-dynamic | |
874 | Force the output file to have dynamic sections. This option is specific | |
875 | to VxWorks targets. | |
876 | ||
252b5132 RH |
877 | @cindex partial link |
878 | @cindex relocatable output | |
879 | @kindex -r | |
1049f94e | 880 | @kindex --relocatable |
252b5132 | 881 | @item -r |
1049f94e | 882 | @itemx --relocatable |
252b5132 | 883 | Generate relocatable output---i.e., generate an output file that can in |
ff5dcc92 | 884 | turn serve as input to @command{ld}. This is often called @dfn{partial |
252b5132 RH |
885 | linking}. As a side effect, in environments that support standard Unix |
886 | magic numbers, this option also sets the output file's magic number to | |
887 | @code{OMAGIC}. | |
ff5dcc92 | 888 | @c ; see @option{-N}. |
252b5132 RH |
889 | If this option is not specified, an absolute file is produced. When |
890 | linking C++ programs, this option @emph{will not} resolve references to | |
891 | constructors; to do that, use @samp{-Ur}. | |
892 | ||
62bf86b4 HPN |
893 | When an input file does not have the same format as the output file, |
894 | partial linking is only supported if that input file does not contain any | |
895 | relocations. Different output formats can have further restrictions; for | |
896 | example some @code{a.out}-based formats do not support partial linking | |
897 | with input files in other formats at all. | |
898 | ||
252b5132 RH |
899 | This option does the same thing as @samp{-i}. |
900 | ||
901 | @kindex -R @var{file} | |
902 | @kindex --just-symbols=@var{file} | |
903 | @cindex symbol-only input | |
904 | @item -R @var{filename} | |
905 | @itemx --just-symbols=@var{filename} | |
906 | Read symbol names and their addresses from @var{filename}, but do not | |
907 | relocate it or include it in the output. This allows your output file | |
908 | to refer symbolically to absolute locations of memory defined in other | |
909 | programs. You may use this option more than once. | |
910 | ||
ff5dcc92 | 911 | For compatibility with other ELF linkers, if the @option{-R} option is |
252b5132 | 912 | followed by a directory name, rather than a file name, it is treated as |
ff5dcc92 | 913 | the @option{-rpath} option. |
252b5132 RH |
914 | |
915 | @kindex -s | |
916 | @kindex --strip-all | |
917 | @cindex strip all symbols | |
a1ab1d2a | 918 | @item -s |
252b5132 RH |
919 | @itemx --strip-all |
920 | Omit all symbol information from the output file. | |
921 | ||
922 | @kindex -S | |
923 | @kindex --strip-debug | |
924 | @cindex strip debugger symbols | |
a1ab1d2a | 925 | @item -S |
252b5132 RH |
926 | @itemx --strip-debug |
927 | Omit debugger symbol information (but not all symbols) from the output file. | |
928 | ||
929 | @kindex -t | |
930 | @kindex --trace | |
931 | @cindex input files, displaying | |
a1ab1d2a | 932 | @item -t |
252b5132 | 933 | @itemx --trace |
ff5dcc92 | 934 | Print the names of the input files as @command{ld} processes them. |
252b5132 RH |
935 | |
936 | @kindex -T @var{script} | |
937 | @kindex --script=@var{script} | |
938 | @cindex script files | |
939 | @item -T @var{scriptfile} | |
940 | @itemx --script=@var{scriptfile} | |
941 | Use @var{scriptfile} as the linker script. This script replaces | |
ff5dcc92 | 942 | @command{ld}'s default linker script (rather than adding to it), so |
252b5132 | 943 | @var{commandfile} must specify everything necessary to describe the |
114283d8 NC |
944 | output file. @xref{Scripts}. If @var{scriptfile} does not exist in |
945 | the current directory, @code{ld} looks for it in the directories | |
946 | specified by any preceding @samp{-L} options. Multiple @samp{-T} | |
947 | options accumulate. | |
252b5132 | 948 | |
14be8564 L |
949 | @kindex -dT @var{script} |
950 | @kindex --default-script=@var{script} | |
951 | @cindex script files | |
952 | @item -dT @var{scriptfile} | |
953 | @itemx --default-script=@var{scriptfile} | |
954 | Use @var{scriptfile} as the default linker script. @xref{Scripts}. | |
955 | ||
956 | This option is similar to the @option{--script} option except that | |
957 | processing of the script is delayed until after the rest of the | |
958 | command line has been processed. This allows options placed after the | |
959 | @option{--default-script} option on the command line to affect the | |
960 | behaviour of the linker script, which can be important when the linker | |
961 | command line cannot be directly controlled by the user. (eg because | |
962 | the command line is being constructed by another tool, such as | |
963 | @samp{gcc}). | |
964 | ||
252b5132 RH |
965 | @kindex -u @var{symbol} |
966 | @kindex --undefined=@var{symbol} | |
967 | @cindex undefined symbol | |
968 | @item -u @var{symbol} | |
969 | @itemx --undefined=@var{symbol} | |
970 | Force @var{symbol} to be entered in the output file as an undefined | |
971 | symbol. Doing this may, for example, trigger linking of additional | |
972 | modules from standard libraries. @samp{-u} may be repeated with | |
973 | different option arguments to enter additional undefined symbols. This | |
974 | option is equivalent to the @code{EXTERN} linker script command. | |
975 | ||
976 | @kindex -Ur | |
977 | @cindex constructors | |
a1ab1d2a | 978 | @item -Ur |
252b5132 RH |
979 | For anything other than C++ programs, this option is equivalent to |
980 | @samp{-r}: it generates relocatable output---i.e., an output file that can in | |
ff5dcc92 | 981 | turn serve as input to @command{ld}. When linking C++ programs, @samp{-Ur} |
252b5132 RH |
982 | @emph{does} resolve references to constructors, unlike @samp{-r}. |
983 | It does not work to use @samp{-Ur} on files that were themselves linked | |
984 | with @samp{-Ur}; once the constructor table has been built, it cannot | |
985 | be added to. Use @samp{-Ur} only for the last partial link, and | |
986 | @samp{-r} for the others. | |
987 | ||
577a0623 AM |
988 | @kindex --unique[=@var{SECTION}] |
989 | @item --unique[=@var{SECTION}] | |
990 | Creates a separate output section for every input section matching | |
991 | @var{SECTION}, or if the optional wildcard @var{SECTION} argument is | |
992 | missing, for every orphan input section. An orphan section is one not | |
993 | specifically mentioned in a linker script. You may use this option | |
994 | multiple times on the command line; It prevents the normal merging of | |
995 | input sections with the same name, overriding output section assignments | |
996 | in a linker script. | |
a854a4a7 | 997 | |
252b5132 RH |
998 | @kindex -v |
999 | @kindex -V | |
1000 | @kindex --version | |
1001 | @cindex version | |
1002 | @item -v | |
1003 | @itemx --version | |
1004 | @itemx -V | |
ff5dcc92 | 1005 | Display the version number for @command{ld}. The @option{-V} option also |
252b5132 RH |
1006 | lists the supported emulations. |
1007 | ||
1008 | @kindex -x | |
1009 | @kindex --discard-all | |
1010 | @cindex deleting local symbols | |
1011 | @item -x | |
1012 | @itemx --discard-all | |
1013 | Delete all local symbols. | |
1014 | ||
1015 | @kindex -X | |
1016 | @kindex --discard-locals | |
1017 | @cindex local symbols, deleting | |
a1ab1d2a | 1018 | @item -X |
252b5132 | 1019 | @itemx --discard-locals |
3c68c38f BW |
1020 | Delete all temporary local symbols. (These symbols start with |
1021 | system-specific local label prefixes, typically @samp{.L} for ELF systems | |
1022 | or @samp{L} for traditional a.out systems.) | |
252b5132 RH |
1023 | |
1024 | @kindex -y @var{symbol} | |
1025 | @kindex --trace-symbol=@var{symbol} | |
1026 | @cindex symbol tracing | |
1027 | @item -y @var{symbol} | |
1028 | @itemx --trace-symbol=@var{symbol} | |
1029 | Print the name of each linked file in which @var{symbol} appears. This | |
1030 | option may be given any number of times. On many systems it is necessary | |
1031 | to prepend an underscore. | |
1032 | ||
1033 | This option is useful when you have an undefined symbol in your link but | |
1034 | don't know where the reference is coming from. | |
1035 | ||
1036 | @kindex -Y @var{path} | |
1037 | @item -Y @var{path} | |
1038 | Add @var{path} to the default library search path. This option exists | |
1039 | for Solaris compatibility. | |
1040 | ||
1041 | @kindex -z @var{keyword} | |
1042 | @item -z @var{keyword} | |
cd6d6c15 NC |
1043 | The recognized keywords are: |
1044 | @table @samp | |
1045 | ||
1046 | @item combreloc | |
1047 | Combines multiple reloc sections and sorts them to make dynamic symbol | |
1048 | lookup caching possible. | |
1049 | ||
1050 | @item defs | |
560e09e9 | 1051 | Disallows undefined symbols in object files. Undefined symbols in |
07f3b6ad | 1052 | shared libraries are still allowed. |
cd6d6c15 | 1053 | |
6aa29e7b JJ |
1054 | @item execstack |
1055 | Marks the object as requiring executable stack. | |
1056 | ||
b039ef04 L |
1057 | @item global |
1058 | This option is only meaningful when building a shared object. It makes | |
1059 | the symbols defined by this shared object available for symbol resolution | |
1060 | of subsequently loaded libraries. | |
1061 | ||
cd6d6c15 NC |
1062 | @item initfirst |
1063 | This option is only meaningful when building a shared object. | |
1064 | It marks the object so that its runtime initialization will occur | |
1065 | before the runtime initialization of any other objects brought into | |
1066 | the process at the same time. Similarly the runtime finalization of | |
1067 | the object will occur after the runtime finalization of any other | |
1068 | objects. | |
1069 | ||
1070 | @item interpose | |
1071 | Marks the object that its symbol table interposes before all symbols | |
1072 | but the primary executable. | |
1073 | ||
5fa222e4 AM |
1074 | @item lazy |
1075 | When generating an executable or shared library, mark it to tell the | |
1076 | dynamic linker to defer function call resolution to the point when | |
1077 | the function is called (lazy binding), rather than at load time. | |
1078 | Lazy binding is the default. | |
1079 | ||
cd6d6c15 NC |
1080 | @item loadfltr |
1081 | Marks the object that its filters be processed immediately at | |
1082 | runtime. | |
1083 | ||
1084 | @item muldefs | |
1085 | Allows multiple definitions. | |
1086 | ||
1087 | @item nocombreloc | |
1088 | Disables multiple reloc sections combining. | |
1089 | ||
1090 | @item nocopyreloc | |
daf220f0 AM |
1091 | Disable linker generated .dynbss variables used in place of variables |
1092 | defined in shared libraries. May result in dynamic text relocations. | |
cd6d6c15 NC |
1093 | |
1094 | @item nodefaultlib | |
1095 | Marks the object that the search for dependencies of this object will | |
1096 | ignore any default library search paths. | |
1097 | ||
1098 | @item nodelete | |
1099 | Marks the object shouldn't be unloaded at runtime. | |
1100 | ||
1101 | @item nodlopen | |
1102 | Marks the object not available to @code{dlopen}. | |
1103 | ||
1104 | @item nodump | |
1105 | Marks the object can not be dumped by @code{dldump}. | |
1106 | ||
6aa29e7b JJ |
1107 | @item noexecstack |
1108 | Marks the object as not requiring executable stack. | |
1109 | ||
8dfef1bd L |
1110 | @item text |
1111 | Treat DT_TEXTREL in shared object as error. | |
1112 | ||
1113 | @item notext | |
1114 | Don't treat DT_TEXTREL in shared object as error. | |
1115 | ||
1116 | @item textoff | |
1117 | Don't treat DT_TEXTREL in shared object as error. | |
1118 | ||
6aa29e7b JJ |
1119 | @item norelro |
1120 | Don't create an ELF @code{PT_GNU_RELRO} segment header in the object. | |
1121 | ||
cd6d6c15 NC |
1122 | @item now |
1123 | When generating an executable or shared library, mark it to tell the | |
1124 | dynamic linker to resolve all symbols when the program is started, or | |
1125 | when the shared library is linked to using dlopen, instead of | |
1126 | deferring function call resolution to the point when the function is | |
1127 | first called. | |
1128 | ||
1129 | @item origin | |
1130 | Marks the object may contain $ORIGIN. | |
1131 | ||
6aa29e7b JJ |
1132 | @item relro |
1133 | Create an ELF @code{PT_GNU_RELRO} segment header in the object. | |
1134 | ||
24718e3b L |
1135 | @item max-page-size=@var{value} |
1136 | Set the emulation maximum page size to @var{value}. | |
1137 | ||
1138 | @item common-page-size=@var{value} | |
1139 | Set the emulation common page size to @var{value}. | |
1140 | ||
04c3a755 NS |
1141 | @item stack-size=@var{value} |
1142 | Specify a stack size for in an ELF @code{PT_GNU_STACK} segment. | |
1143 | Specifying zero will override any default non-zero sized | |
1144 | @code{PT_GNU_STACK} segment creation. | |
1145 | ||
d258b828 IZ |
1146 | @item bndplt |
1147 | Always generate BND prefix in PLT entries. Supported for Linux/x86_64. | |
1148 | ||
cd6d6c15 NC |
1149 | @end table |
1150 | ||
ece2d90e | 1151 | Other keywords are ignored for Solaris compatibility. |
252b5132 RH |
1152 | |
1153 | @kindex -( | |
1154 | @cindex groups of archives | |
1155 | @item -( @var{archives} -) | |
1156 | @itemx --start-group @var{archives} --end-group | |
1157 | The @var{archives} should be a list of archive files. They may be | |
1158 | either explicit file names, or @samp{-l} options. | |
1159 | ||
1160 | The specified archives are searched repeatedly until no new undefined | |
1161 | references are created. Normally, an archive is searched only once in | |
1162 | the order that it is specified on the command line. If a symbol in that | |
1163 | archive is needed to resolve an undefined symbol referred to by an | |
1164 | object in an archive that appears later on the command line, the linker | |
1165 | would not be able to resolve that reference. By grouping the archives, | |
1166 | they all be searched repeatedly until all possible references are | |
1167 | resolved. | |
1168 | ||
1169 | Using this option has a significant performance cost. It is best to use | |
1170 | it only when there are unavoidable circular references between two or | |
1171 | more archives. | |
1172 | ||
69da35b5 NC |
1173 | @kindex --accept-unknown-input-arch |
1174 | @kindex --no-accept-unknown-input-arch | |
1175 | @item --accept-unknown-input-arch | |
1176 | @itemx --no-accept-unknown-input-arch | |
1177 | Tells the linker to accept input files whose architecture cannot be | |
2ca22b03 | 1178 | recognised. The assumption is that the user knows what they are doing |
69da35b5 NC |
1179 | and deliberately wants to link in these unknown input files. This was |
1180 | the default behaviour of the linker, before release 2.14. The default | |
1181 | behaviour from release 2.14 onwards is to reject such input files, and | |
1182 | so the @samp{--accept-unknown-input-arch} option has been added to | |
1183 | restore the old behaviour. | |
2ca22b03 | 1184 | |
4a43e768 AM |
1185 | @kindex --as-needed |
1186 | @kindex --no-as-needed | |
1187 | @item --as-needed | |
1188 | @itemx --no-as-needed | |
1189 | This option affects ELF DT_NEEDED tags for dynamic libraries mentioned | |
ddbb8a31 | 1190 | on the command line after the @option{--as-needed} option. Normally |
4a43e768 AM |
1191 | the linker will add a DT_NEEDED tag for each dynamic library mentioned |
1192 | on the command line, regardless of whether the library is actually | |
ddbb8a31 | 1193 | needed or not. @option{--as-needed} causes a DT_NEEDED tag to only be |
ffa9430d AM |
1194 | emitted for a library that @emph{at that point in the link} satisfies a |
1195 | non-weak undefined symbol reference from a regular object file or, if | |
1240be6b AM |
1196 | the library is not found in the DT_NEEDED lists of other needed libraries, a |
1197 | non-weak undefined symbol reference from another needed dynamic library. | |
ffa9430d AM |
1198 | Object files or libraries appearing on the command line @emph{after} |
1199 | the library in question do not affect whether the library is seen as | |
1200 | needed. This is similar to the rules for extraction of object files | |
1201 | from archives. @option{--no-as-needed} restores the default behaviour. | |
4a43e768 | 1202 | |
e56f61be L |
1203 | @kindex --add-needed |
1204 | @kindex --no-add-needed | |
1205 | @item --add-needed | |
1206 | @itemx --no-add-needed | |
ddbb8a31 NC |
1207 | These two options have been deprecated because of the similarity of |
1208 | their names to the @option{--as-needed} and @option{--no-as-needed} | |
1209 | options. They have been replaced by @option{--copy-dt-needed-entries} | |
1210 | and @option{--no-copy-dt-needed-entries}. | |
e56f61be | 1211 | |
252b5132 RH |
1212 | @kindex -assert @var{keyword} |
1213 | @item -assert @var{keyword} | |
1214 | This option is ignored for SunOS compatibility. | |
1215 | ||
1216 | @kindex -Bdynamic | |
1217 | @kindex -dy | |
1218 | @kindex -call_shared | |
1219 | @item -Bdynamic | |
1220 | @itemx -dy | |
1221 | @itemx -call_shared | |
1222 | Link against dynamic libraries. This is only meaningful on platforms | |
1223 | for which shared libraries are supported. This option is normally the | |
1224 | default on such platforms. The different variants of this option are | |
1225 | for compatibility with various systems. You may use this option | |
1226 | multiple times on the command line: it affects library searching for | |
da8bce14 | 1227 | @option{-l} options which follow it. |
252b5132 | 1228 | |
a1ab1d2a UD |
1229 | @kindex -Bgroup |
1230 | @item -Bgroup | |
1231 | Set the @code{DF_1_GROUP} flag in the @code{DT_FLAGS_1} entry in the dynamic | |
1232 | section. This causes the runtime linker to handle lookups in this | |
1233 | object and its dependencies to be performed only inside the group. | |
560e09e9 NC |
1234 | @option{--unresolved-symbols=report-all} is implied. This option is |
1235 | only meaningful on ELF platforms which support shared libraries. | |
a1ab1d2a | 1236 | |
252b5132 RH |
1237 | @kindex -Bstatic |
1238 | @kindex -dn | |
1239 | @kindex -non_shared | |
1240 | @kindex -static | |
a1ab1d2a | 1241 | @item -Bstatic |
252b5132 RH |
1242 | @itemx -dn |
1243 | @itemx -non_shared | |
1244 | @itemx -static | |
1245 | Do not link against shared libraries. This is only meaningful on | |
1246 | platforms for which shared libraries are supported. The different | |
1247 | variants of this option are for compatibility with various systems. You | |
1248 | may use this option multiple times on the command line: it affects | |
560e09e9 | 1249 | library searching for @option{-l} options which follow it. This |
e9156f74 NC |
1250 | option also implies @option{--unresolved-symbols=report-all}. This |
1251 | option can be used with @option{-shared}. Doing so means that a | |
1252 | shared library is being created but that all of the library's external | |
1253 | references must be resolved by pulling in entries from static | |
ece2d90e | 1254 | libraries. |
252b5132 RH |
1255 | |
1256 | @kindex -Bsymbolic | |
1257 | @item -Bsymbolic | |
1258 | When creating a shared library, bind references to global symbols to the | |
1259 | definition within the shared library, if any. Normally, it is possible | |
1260 | for a program linked against a shared library to override the definition | |
1261 | within the shared library. This option is only meaningful on ELF | |
1262 | platforms which support shared libraries. | |
1263 | ||
40b36307 L |
1264 | @kindex -Bsymbolic-functions |
1265 | @item -Bsymbolic-functions | |
1266 | When creating a shared library, bind references to global function | |
c0065db7 | 1267 | symbols to the definition within the shared library, if any. |
40b36307 L |
1268 | This option is only meaningful on ELF platforms which support shared |
1269 | libraries. | |
1270 | ||
55255dae L |
1271 | @kindex --dynamic-list=@var{dynamic-list-file} |
1272 | @item --dynamic-list=@var{dynamic-list-file} | |
1273 | Specify the name of a dynamic list file to the linker. This is | |
1274 | typically used when creating shared libraries to specify a list of | |
1275 | global symbols whose references shouldn't be bound to the definition | |
1276 | within the shared library, or creating dynamically linked executables | |
1277 | to specify a list of symbols which should be added to the symbol table | |
1278 | in the executable. This option is only meaningful on ELF platforms | |
1279 | which support shared libraries. | |
1280 | ||
1281 | The format of the dynamic list is the same as the version node without | |
1282 | scope and node name. See @ref{VERSION} for more information. | |
1283 | ||
40b36307 L |
1284 | @kindex --dynamic-list-data |
1285 | @item --dynamic-list-data | |
1286 | Include all global data symbols to the dynamic list. | |
1287 | ||
1288 | @kindex --dynamic-list-cpp-new | |
1289 | @item --dynamic-list-cpp-new | |
1290 | Provide the builtin dynamic list for C++ operator new and delete. It | |
1291 | is mainly useful for building shared libstdc++. | |
1292 | ||
0b8a70d9 L |
1293 | @kindex --dynamic-list-cpp-typeinfo |
1294 | @item --dynamic-list-cpp-typeinfo | |
1295 | Provide the builtin dynamic list for C++ runtime type identification. | |
1296 | ||
252b5132 RH |
1297 | @kindex --check-sections |
1298 | @kindex --no-check-sections | |
1299 | @item --check-sections | |
308b1ffd | 1300 | @itemx --no-check-sections |
252b5132 | 1301 | Asks the linker @emph{not} to check section addresses after they have |
7d816a17 | 1302 | been assigned to see if there are any overlaps. Normally the linker will |
252b5132 RH |
1303 | perform this check, and if it finds any overlaps it will produce |
1304 | suitable error messages. The linker does know about, and does make | |
1305 | allowances for sections in overlays. The default behaviour can be | |
560e09e9 | 1306 | restored by using the command line switch @option{--check-sections}. |
02b0b1aa NS |
1307 | Section overlap is not usually checked for relocatable links. You can |
1308 | force checking in that case by using the @option{--check-sections} | |
1309 | option. | |
252b5132 | 1310 | |
ddbb8a31 NC |
1311 | @kindex --copy-dt-needed-entries |
1312 | @kindex --no-copy-dt-needed-entries | |
1313 | @item --copy-dt-needed-entries | |
1314 | @itemx --no-copy-dt-needed-entries | |
9d5777a3 | 1315 | This option affects the treatment of dynamic libraries referred to |
ddbb8a31 | 1316 | by DT_NEEDED tags @emph{inside} ELF dynamic libraries mentioned on the |
08efffb8 | 1317 | command line. Normally the linker won't add a DT_NEEDED tag to the |
ddbb8a31 | 1318 | output binary for each library mentioned in a DT_NEEDED tag in an |
08efffb8 | 1319 | input dynamic library. With @option{--copy-dt-needed-entries} |
ddbb8a31 | 1320 | specified on the command line however any dynamic libraries that |
08efffb8 MM |
1321 | follow it will have their DT_NEEDED entries added. The default |
1322 | behaviour can be restored with @option{--no-copy-dt-needed-entries}. | |
ddbb8a31 NC |
1323 | |
1324 | This option also has an effect on the resolution of symbols in dynamic | |
08efffb8 MM |
1325 | libraries. With @option{--copy-dt-needed-entries} dynamic libraries |
1326 | mentioned on the command line will be recursively searched, following | |
1327 | their DT_NEEDED tags to other libraries, in order to resolve symbols | |
1328 | required by the output binary. With the default setting however | |
1329 | the searching of dynamic libraries that follow it will stop with the | |
1330 | dynamic library itself. No DT_NEEDED links will be traversed to resolve | |
ddbb8a31 NC |
1331 | symbols. |
1332 | ||
252b5132 RH |
1333 | @cindex cross reference table |
1334 | @kindex --cref | |
1335 | @item --cref | |
1336 | Output a cross reference table. If a linker map file is being | |
1337 | generated, the cross reference table is printed to the map file. | |
1338 | Otherwise, it is printed on the standard output. | |
1339 | ||
1340 | The format of the table is intentionally simple, so that it may be | |
1341 | easily processed by a script if necessary. The symbols are printed out, | |
1342 | sorted by name. For each symbol, a list of file names is given. If the | |
1343 | symbol is defined, the first file listed is the location of the | |
049c1c8e NC |
1344 | definition. If the symbol is defined as a common value then any files |
1345 | where this happens appear next. Finally any files that reference the | |
1346 | symbol are listed. | |
252b5132 | 1347 | |
4818e05f AM |
1348 | @cindex common allocation |
1349 | @kindex --no-define-common | |
1350 | @item --no-define-common | |
1351 | This option inhibits the assignment of addresses to common symbols. | |
1352 | The script command @code{INHIBIT_COMMON_ALLOCATION} has the same effect. | |
1353 | @xref{Miscellaneous Commands}. | |
1354 | ||
1355 | The @samp{--no-define-common} option allows decoupling | |
1356 | the decision to assign addresses to Common symbols from the choice | |
1357 | of the output file type; otherwise a non-Relocatable output type | |
1358 | forces assigning addresses to Common symbols. | |
1359 | Using @samp{--no-define-common} allows Common symbols that are referenced | |
1360 | from a shared library to be assigned addresses only in the main program. | |
1361 | This eliminates the unused duplicate space in the shared library, | |
1362 | and also prevents any possible confusion over resolving to the wrong | |
1363 | duplicate when there are many dynamic modules with specialized search | |
1364 | paths for runtime symbol resolution. | |
1365 | ||
252b5132 | 1366 | @cindex symbols, from command line |
2509a395 SL |
1367 | @kindex --defsym=@var{symbol}=@var{exp} |
1368 | @item --defsym=@var{symbol}=@var{expression} | |
252b5132 RH |
1369 | Create a global symbol in the output file, containing the absolute |
1370 | address given by @var{expression}. You may use this option as many | |
1371 | times as necessary to define multiple symbols in the command line. A | |
1372 | limited form of arithmetic is supported for the @var{expression} in this | |
1373 | context: you may give a hexadecimal constant or the name of an existing | |
1374 | symbol, or use @code{+} and @code{-} to add or subtract hexadecimal | |
1375 | constants or symbols. If you need more elaborate expressions, consider | |
66bc8739 AM |
1376 | using the linker command language from a script (@pxref{Assignments}). |
1377 | @emph{Note:} there should be no white space between @var{symbol}, the | |
1378 | equals sign (``@key{=}''), and @var{expression}. | |
252b5132 RH |
1379 | |
1380 | @cindex demangling, from command line | |
28c309a2 | 1381 | @kindex --demangle[=@var{style}] |
252b5132 | 1382 | @kindex --no-demangle |
28c309a2 | 1383 | @item --demangle[=@var{style}] |
252b5132 RH |
1384 | @itemx --no-demangle |
1385 | These options control whether to demangle symbol names in error messages | |
1386 | and other output. When the linker is told to demangle, it tries to | |
1387 | present symbol names in a readable fashion: it strips leading | |
1388 | underscores if they are used by the object file format, and converts C++ | |
a1ab1d2a UD |
1389 | mangled symbol names into user readable names. Different compilers have |
1390 | different mangling styles. The optional demangling style argument can be used | |
1391 | to choose an appropriate demangling style for your compiler. The linker will | |
28c309a2 NC |
1392 | demangle by default unless the environment variable @samp{COLLECT_NO_DEMANGLE} |
1393 | is set. These options may be used to override the default. | |
252b5132 RH |
1394 | |
1395 | @cindex dynamic linker, from command line | |
506eee22 | 1396 | @kindex -I@var{file} |
2509a395 SL |
1397 | @kindex --dynamic-linker=@var{file} |
1398 | @item -I@var{file} | |
1399 | @itemx --dynamic-linker=@var{file} | |
252b5132 RH |
1400 | Set the name of the dynamic linker. This is only meaningful when |
1401 | generating dynamically linked ELF executables. The default dynamic | |
1402 | linker is normally correct; don't use this unless you know what you are | |
1403 | doing. | |
1404 | ||
7ce691ae | 1405 | @kindex --fatal-warnings |
0fe58ccd | 1406 | @kindex --no-fatal-warnings |
7ce691ae | 1407 | @item --fatal-warnings |
0fe58ccd NC |
1408 | @itemx --no-fatal-warnings |
1409 | Treat all warnings as errors. The default behaviour can be restored | |
1410 | with the option @option{--no-fatal-warnings}. | |
7ce691ae | 1411 | |
252b5132 RH |
1412 | @kindex --force-exe-suffix |
1413 | @item --force-exe-suffix | |
1414 | Make sure that an output file has a .exe suffix. | |
1415 | ||
1416 | If a successfully built fully linked output file does not have a | |
1417 | @code{.exe} or @code{.dll} suffix, this option forces the linker to copy | |
1418 | the output file to one of the same name with a @code{.exe} suffix. This | |
1419 | option is useful when using unmodified Unix makefiles on a Microsoft | |
1420 | Windows host, since some versions of Windows won't run an image unless | |
1421 | it ends in a @code{.exe} suffix. | |
1422 | ||
1423 | @kindex --gc-sections | |
1424 | @kindex --no-gc-sections | |
1425 | @cindex garbage collection | |
c17d87de NC |
1426 | @item --gc-sections |
1427 | @itemx --no-gc-sections | |
252b5132 | 1428 | Enable garbage collection of unused input sections. It is ignored on |
ac69cbc6 | 1429 | targets that do not support this option. The default behaviour (of not |
b3549761 NC |
1430 | performing this garbage collection) can be restored by specifying |
1431 | @samp{--no-gc-sections} on the command line. | |
252b5132 | 1432 | |
d5465ba2 AM |
1433 | @samp{--gc-sections} decides which input sections are used by |
1434 | examining symbols and relocations. The section containing the entry | |
1435 | symbol and all sections containing symbols undefined on the | |
1436 | command-line will be kept, as will sections containing symbols | |
1437 | referenced by dynamic objects. Note that when building shared | |
1438 | libraries, the linker must assume that any visible symbol is | |
1439 | referenced. Once this initial set of sections has been determined, | |
1440 | the linker recursively marks as used any section referenced by their | |
1441 | relocations. See @samp{--entry} and @samp{--undefined}. | |
1442 | ||
ac69cbc6 | 1443 | This option can be set when doing a partial link (enabled with option |
9d5777a3 | 1444 | @samp{-r}). In this case the root of symbols kept must be explicitly |
ac69cbc6 TG |
1445 | specified either by an @samp{--entry} or @samp{--undefined} option or by |
1446 | a @code{ENTRY} command in the linker script. | |
1447 | ||
c17d87de NC |
1448 | @kindex --print-gc-sections |
1449 | @kindex --no-print-gc-sections | |
1450 | @cindex garbage collection | |
1451 | @item --print-gc-sections | |
1452 | @itemx --no-print-gc-sections | |
1453 | List all sections removed by garbage collection. The listing is | |
1454 | printed on stderr. This option is only effective if garbage | |
1455 | collection has been enabled via the @samp{--gc-sections}) option. The | |
1456 | default behaviour (of not listing the sections that are removed) can | |
1457 | be restored by specifying @samp{--no-print-gc-sections} on the command | |
1458 | line. | |
1459 | ||
30824704 RM |
1460 | @kindex --print-output-format |
1461 | @cindex output format | |
1462 | @item --print-output-format | |
1463 | Print the name of the default output format (perhaps influenced by | |
1464 | other command-line options). This is the string that would appear | |
1465 | in an @code{OUTPUT_FORMAT} linker script command (@pxref{File Commands}). | |
1466 | ||
252b5132 RH |
1467 | @cindex help |
1468 | @cindex usage | |
1469 | @kindex --help | |
1470 | @item --help | |
1471 | Print a summary of the command-line options on the standard output and exit. | |
1472 | ||
ea20a7da CC |
1473 | @kindex --target-help |
1474 | @item --target-help | |
1475 | Print a summary of all target specific options on the standard output and exit. | |
1476 | ||
2509a395 SL |
1477 | @kindex -Map=@var{mapfile} |
1478 | @item -Map=@var{mapfile} | |
252b5132 | 1479 | Print a link map to the file @var{mapfile}. See the description of the |
560e09e9 | 1480 | @option{-M} option, above. |
252b5132 RH |
1481 | |
1482 | @cindex memory usage | |
1483 | @kindex --no-keep-memory | |
1484 | @item --no-keep-memory | |
ff5dcc92 SC |
1485 | @command{ld} normally optimizes for speed over memory usage by caching the |
1486 | symbol tables of input files in memory. This option tells @command{ld} to | |
252b5132 | 1487 | instead optimize for memory usage, by rereading the symbol tables as |
ff5dcc92 | 1488 | necessary. This may be required if @command{ld} runs out of memory space |
252b5132 RH |
1489 | while linking a large executable. |
1490 | ||
1491 | @kindex --no-undefined | |
a1ab1d2a | 1492 | @kindex -z defs |
252b5132 | 1493 | @item --no-undefined |
a1ab1d2a | 1494 | @itemx -z defs |
560e09e9 NC |
1495 | Report unresolved symbol references from regular object files. This |
1496 | is done even if the linker is creating a non-symbolic shared library. | |
1497 | The switch @option{--[no-]allow-shlib-undefined} controls the | |
1498 | behaviour for reporting unresolved references found in shared | |
ece2d90e | 1499 | libraries being linked in. |
252b5132 | 1500 | |
aa713662 L |
1501 | @kindex --allow-multiple-definition |
1502 | @kindex -z muldefs | |
1503 | @item --allow-multiple-definition | |
1504 | @itemx -z muldefs | |
1505 | Normally when a symbol is defined multiple times, the linker will | |
1506 | report a fatal error. These options allow multiple definitions and the | |
1507 | first definition will be used. | |
1508 | ||
b79e8c78 | 1509 | @kindex --allow-shlib-undefined |
ae9a127f | 1510 | @kindex --no-allow-shlib-undefined |
b79e8c78 | 1511 | @item --allow-shlib-undefined |
ae9a127f | 1512 | @itemx --no-allow-shlib-undefined |
903249d7 | 1513 | Allows or disallows undefined symbols in shared libraries. |
560e09e9 NC |
1514 | This switch is similar to @option{--no-undefined} except that it |
1515 | determines the behaviour when the undefined symbols are in a | |
1516 | shared library rather than a regular object file. It does not affect | |
1517 | how undefined symbols in regular object files are handled. | |
1518 | ||
903249d7 NC |
1519 | The default behaviour is to report errors for any undefined symbols |
1520 | referenced in shared libraries if the linker is being used to create | |
1521 | an executable, but to allow them if the linker is being used to create | |
1522 | a shared library. | |
1523 | ||
1524 | The reasons for allowing undefined symbol references in shared | |
1525 | libraries specified at link time are that: | |
1526 | ||
1527 | @itemize @bullet | |
1528 | @item | |
1529 | A shared library specified at link time may not be the same as the one | |
1530 | that is available at load time, so the symbol might actually be | |
1531 | resolvable at load time. | |
1532 | @item | |
1533 | There are some operating systems, eg BeOS and HPPA, where undefined | |
1534 | symbols in shared libraries are normal. | |
1535 | ||
1536 | The BeOS kernel for example patches shared libraries at load time to | |
1537 | select whichever function is most appropriate for the current | |
1538 | architecture. This is used, for example, to dynamically select an | |
1539 | appropriate memset function. | |
1540 | @end itemize | |
b79e8c78 | 1541 | |
31941635 L |
1542 | @kindex --no-undefined-version |
1543 | @item --no-undefined-version | |
1544 | Normally when a symbol has an undefined version, the linker will ignore | |
1545 | it. This option disallows symbols with undefined version and a fatal error | |
1546 | will be issued instead. | |
1547 | ||
3e3b46e5 PB |
1548 | @kindex --default-symver |
1549 | @item --default-symver | |
1550 | Create and use a default symbol version (the soname) for unversioned | |
fc0e6df6 PB |
1551 | exported symbols. |
1552 | ||
1553 | @kindex --default-imported-symver | |
1554 | @item --default-imported-symver | |
1555 | Create and use a default symbol version (the soname) for unversioned | |
1556 | imported symbols. | |
3e3b46e5 | 1557 | |
252b5132 RH |
1558 | @kindex --no-warn-mismatch |
1559 | @item --no-warn-mismatch | |
ff5dcc92 | 1560 | Normally @command{ld} will give an error if you try to link together input |
252b5132 RH |
1561 | files that are mismatched for some reason, perhaps because they have |
1562 | been compiled for different processors or for different endiannesses. | |
ff5dcc92 | 1563 | This option tells @command{ld} that it should silently permit such possible |
252b5132 RH |
1564 | errors. This option should only be used with care, in cases when you |
1565 | have taken some special action that ensures that the linker errors are | |
1566 | inappropriate. | |
1567 | ||
fe7929ce AM |
1568 | @kindex --no-warn-search-mismatch |
1569 | @item --no-warn-search-mismatch | |
1570 | Normally @command{ld} will give a warning if it finds an incompatible | |
1571 | library during a library search. This option silences the warning. | |
1572 | ||
252b5132 RH |
1573 | @kindex --no-whole-archive |
1574 | @item --no-whole-archive | |
ff5dcc92 | 1575 | Turn off the effect of the @option{--whole-archive} option for subsequent |
252b5132 RH |
1576 | archive files. |
1577 | ||
1578 | @cindex output file after errors | |
1579 | @kindex --noinhibit-exec | |
1580 | @item --noinhibit-exec | |
1581 | Retain the executable output file whenever it is still usable. | |
1582 | Normally, the linker will not produce an output file if it encounters | |
1583 | errors during the link process; it exits without writing an output file | |
1584 | when it issues any error whatsoever. | |
1585 | ||
0a9c1c8e CD |
1586 | @kindex -nostdlib |
1587 | @item -nostdlib | |
1588 | Only search library directories explicitly specified on the | |
1589 | command line. Library directories specified in linker scripts | |
1590 | (including linker scripts specified on the command line) are ignored. | |
1591 | ||
252b5132 | 1592 | @ifclear SingleFormat |
2509a395 SL |
1593 | @kindex --oformat=@var{output-format} |
1594 | @item --oformat=@var{output-format} | |
ff5dcc92 SC |
1595 | @command{ld} may be configured to support more than one kind of object |
1596 | file. If your @command{ld} is configured this way, you can use the | |
252b5132 | 1597 | @samp{--oformat} option to specify the binary format for the output |
ff5dcc92 SC |
1598 | object file. Even when @command{ld} is configured to support alternative |
1599 | object formats, you don't usually need to specify this, as @command{ld} | |
252b5132 RH |
1600 | should be configured to produce as a default output format the most |
1601 | usual format on each machine. @var{output-format} is a text string, the | |
1602 | name of a particular format supported by the BFD libraries. (You can | |
1603 | list the available binary formats with @samp{objdump -i}.) The script | |
1604 | command @code{OUTPUT_FORMAT} can also specify the output format, but | |
1605 | this option overrides it. @xref{BFD}. | |
1606 | @end ifclear | |
1607 | ||
36af4a4e JJ |
1608 | @kindex -pie |
1609 | @kindex --pic-executable | |
1610 | @item -pie | |
1611 | @itemx --pic-executable | |
1612 | @cindex position independent executables | |
1613 | Create a position independent executable. This is currently only supported on | |
1614 | ELF platforms. Position independent executables are similar to shared | |
1615 | libraries in that they are relocated by the dynamic linker to the virtual | |
7e7d5768 | 1616 | address the OS chooses for them (which can vary between invocations). Like |
36af4a4e JJ |
1617 | normal dynamically linked executables they can be executed and symbols |
1618 | defined in the executable cannot be overridden by shared libraries. | |
1619 | ||
252b5132 RH |
1620 | @kindex -qmagic |
1621 | @item -qmagic | |
1622 | This option is ignored for Linux compatibility. | |
1623 | ||
1624 | @kindex -Qy | |
1625 | @item -Qy | |
1626 | This option is ignored for SVR4 compatibility. | |
1627 | ||
1628 | @kindex --relax | |
1629 | @cindex synthesizing linker | |
1630 | @cindex relaxing addressing modes | |
28d5f677 | 1631 | @cindex --no-relax |
252b5132 | 1632 | @item --relax |
28d5f677 | 1633 | @itemx --no-relax |
a1ab1d2a | 1634 | An option with machine dependent effects. |
252b5132 RH |
1635 | @ifset GENERIC |
1636 | This option is only supported on a few targets. | |
1637 | @end ifset | |
1638 | @ifset H8300 | |
ff5dcc92 | 1639 | @xref{H8/300,,@command{ld} and the H8/300}. |
252b5132 RH |
1640 | @end ifset |
1641 | @ifset I960 | |
ff5dcc92 | 1642 | @xref{i960,, @command{ld} and the Intel 960 family}. |
252b5132 | 1643 | @end ifset |
e0001a05 NC |
1644 | @ifset XTENSA |
1645 | @xref{Xtensa,, @command{ld} and Xtensa Processors}. | |
1646 | @end ifset | |
93fd0973 SC |
1647 | @ifset M68HC11 |
1648 | @xref{M68HC11/68HC12,,@command{ld} and the 68HC11 and 68HC12}. | |
1649 | @end ifset | |
78058a5e SL |
1650 | @ifset NIOSII |
1651 | @xref{Nios II,,@command{ld} and the Altera Nios II}. | |
1652 | @end ifset | |
2a60a7a8 AM |
1653 | @ifset POWERPC |
1654 | @xref{PowerPC ELF32,,@command{ld} and PowerPC 32-bit ELF Support}. | |
1655 | @end ifset | |
252b5132 | 1656 | |
28d5f677 NC |
1657 | On some platforms the @samp{--relax} option performs target specific, |
1658 | global optimizations that become possible when the linker resolves | |
1659 | addressing in the program, such as relaxing address modes, | |
1660 | synthesizing new instructions, selecting shorter version of current | |
11e7fd74 | 1661 | instructions, and combining constant values. |
252b5132 RH |
1662 | |
1663 | On some platforms these link time global optimizations may make symbolic | |
1664 | debugging of the resulting executable impossible. | |
1665 | @ifset GENERIC | |
28d5f677 NC |
1666 | This is known to be the case for the Matsushita MN10200 and MN10300 |
1667 | family of processors. | |
252b5132 RH |
1668 | @end ifset |
1669 | ||
1670 | @ifset GENERIC | |
1671 | On platforms where this is not supported, @samp{--relax} is accepted, | |
1672 | but ignored. | |
1673 | @end ifset | |
1674 | ||
28d5f677 NC |
1675 | On platforms where @samp{--relax} is accepted the option |
1676 | @samp{--no-relax} can be used to disable the feature. | |
1677 | ||
252b5132 RH |
1678 | @cindex retaining specified symbols |
1679 | @cindex stripping all but some symbols | |
1680 | @cindex symbols, retaining selectively | |
2509a395 SL |
1681 | @kindex --retain-symbols-file=@var{filename} |
1682 | @item --retain-symbols-file=@var{filename} | |
252b5132 RH |
1683 | Retain @emph{only} the symbols listed in the file @var{filename}, |
1684 | discarding all others. @var{filename} is simply a flat file, with one | |
1685 | symbol name per line. This option is especially useful in environments | |
1686 | @ifset GENERIC | |
1687 | (such as VxWorks) | |
1688 | @end ifset | |
1689 | where a large global symbol table is accumulated gradually, to conserve | |
1690 | run-time memory. | |
1691 | ||
1692 | @samp{--retain-symbols-file} does @emph{not} discard undefined symbols, | |
1693 | or symbols needed for relocations. | |
1694 | ||
1695 | You may only specify @samp{--retain-symbols-file} once in the command | |
1696 | line. It overrides @samp{-s} and @samp{-S}. | |
1697 | ||
1698 | @ifset GENERIC | |
2509a395 | 1699 | @item -rpath=@var{dir} |
252b5132 | 1700 | @cindex runtime library search path |
2509a395 | 1701 | @kindex -rpath=@var{dir} |
252b5132 | 1702 | Add a directory to the runtime library search path. This is used when |
ff5dcc92 | 1703 | linking an ELF executable with shared objects. All @option{-rpath} |
252b5132 | 1704 | arguments are concatenated and passed to the runtime linker, which uses |
ff5dcc92 | 1705 | them to locate shared objects at runtime. The @option{-rpath} option is |
252b5132 RH |
1706 | also used when locating shared objects which are needed by shared |
1707 | objects explicitly included in the link; see the description of the | |
ff5dcc92 | 1708 | @option{-rpath-link} option. If @option{-rpath} is not used when linking an |
252b5132 RH |
1709 | ELF executable, the contents of the environment variable |
1710 | @code{LD_RUN_PATH} will be used if it is defined. | |
1711 | ||
ff5dcc92 | 1712 | The @option{-rpath} option may also be used on SunOS. By default, on |
252b5132 | 1713 | SunOS, the linker will form a runtime search patch out of all the |
ff5dcc92 SC |
1714 | @option{-L} options it is given. If a @option{-rpath} option is used, the |
1715 | runtime search path will be formed exclusively using the @option{-rpath} | |
1716 | options, ignoring the @option{-L} options. This can be useful when using | |
1717 | gcc, which adds many @option{-L} options which may be on NFS mounted | |
b45619c0 | 1718 | file systems. |
252b5132 | 1719 | |
ff5dcc92 | 1720 | For compatibility with other ELF linkers, if the @option{-R} option is |
252b5132 | 1721 | followed by a directory name, rather than a file name, it is treated as |
ff5dcc92 | 1722 | the @option{-rpath} option. |
252b5132 RH |
1723 | @end ifset |
1724 | ||
1725 | @ifset GENERIC | |
1726 | @cindex link-time runtime library search path | |
2509a395 SL |
1727 | @kindex -rpath-link=@var{dir} |
1728 | @item -rpath-link=@var{dir} | |
252b5132 RH |
1729 | When using ELF or SunOS, one shared library may require another. This |
1730 | happens when an @code{ld -shared} link includes a shared library as one | |
1731 | of the input files. | |
1732 | ||
1733 | When the linker encounters such a dependency when doing a non-shared, | |
1734 | non-relocatable link, it will automatically try to locate the required | |
1735 | shared library and include it in the link, if it is not included | |
ff5dcc92 | 1736 | explicitly. In such a case, the @option{-rpath-link} option |
252b5132 | 1737 | specifies the first set of directories to search. The |
ff5dcc92 | 1738 | @option{-rpath-link} option may specify a sequence of directory names |
252b5132 RH |
1739 | either by specifying a list of names separated by colons, or by |
1740 | appearing multiple times. | |
1741 | ||
28c309a2 NC |
1742 | This option should be used with caution as it overrides the search path |
1743 | that may have been hard compiled into a shared library. In such a case it | |
1744 | is possible to use unintentionally a different search path than the | |
1745 | runtime linker would do. | |
1746 | ||
252b5132 | 1747 | The linker uses the following search paths to locate required shared |
ece2d90e | 1748 | libraries: |
252b5132 RH |
1749 | @enumerate |
1750 | @item | |
ff5dcc92 | 1751 | Any directories specified by @option{-rpath-link} options. |
252b5132 | 1752 | @item |
ff5dcc92 SC |
1753 | Any directories specified by @option{-rpath} options. The difference |
1754 | between @option{-rpath} and @option{-rpath-link} is that directories | |
1755 | specified by @option{-rpath} options are included in the executable and | |
1756 | used at runtime, whereas the @option{-rpath-link} option is only effective | |
ece2d90e NC |
1757 | at link time. Searching @option{-rpath} in this way is only supported |
1758 | by native linkers and cross linkers which have been configured with | |
1759 | the @option{--with-sysroot} option. | |
252b5132 | 1760 | @item |
e2a83dd0 NC |
1761 | On an ELF system, for native linkers, if the @option{-rpath} and |
1762 | @option{-rpath-link} options were not used, search the contents of the | |
1763 | environment variable @code{LD_RUN_PATH}. | |
252b5132 | 1764 | @item |
ff5dcc92 SC |
1765 | On SunOS, if the @option{-rpath} option was not used, search any |
1766 | directories specified using @option{-L} options. | |
252b5132 | 1767 | @item |
a1b8d843 | 1768 | For a native linker, search the contents of the environment |
e2a83dd0 | 1769 | variable @code{LD_LIBRARY_PATH}. |
252b5132 | 1770 | @item |
ec4eb78a L |
1771 | For a native ELF linker, the directories in @code{DT_RUNPATH} or |
1772 | @code{DT_RPATH} of a shared library are searched for shared | |
1773 | libraries needed by it. The @code{DT_RPATH} entries are ignored if | |
1774 | @code{DT_RUNPATH} entries exist. | |
1775 | @item | |
252b5132 RH |
1776 | The default directories, normally @file{/lib} and @file{/usr/lib}. |
1777 | @item | |
1778 | For a native linker on an ELF system, if the file @file{/etc/ld.so.conf} | |
1779 | exists, the list of directories found in that file. | |
1780 | @end enumerate | |
1781 | ||
1782 | If the required shared library is not found, the linker will issue a | |
1783 | warning and continue with the link. | |
1784 | @end ifset | |
1785 | ||
1786 | @kindex -shared | |
1787 | @kindex -Bshareable | |
1788 | @item -shared | |
1789 | @itemx -Bshareable | |
1790 | @cindex shared libraries | |
1791 | Create a shared library. This is currently only supported on ELF, XCOFF | |
1792 | and SunOS platforms. On SunOS, the linker will automatically create a | |
ff5dcc92 | 1793 | shared library if the @option{-e} option is not used and there are |
252b5132 RH |
1794 | undefined symbols in the link. |
1795 | ||
252b5132 | 1796 | @kindex --sort-common |
2509a395 SL |
1797 | @item --sort-common |
1798 | @itemx --sort-common=ascending | |
1799 | @itemx --sort-common=descending | |
de7dd2bd NC |
1800 | This option tells @command{ld} to sort the common symbols by alignment in |
1801 | ascending or descending order when it places them in the appropriate output | |
1802 | sections. The symbol alignments considered are sixteen-byte or larger, | |
1803 | eight-byte, four-byte, two-byte, and one-byte. This is to prevent gaps | |
1804 | between symbols due to alignment constraints. If no sorting order is | |
1805 | specified, then descending order is assumed. | |
252b5132 | 1806 | |
2509a395 SL |
1807 | @kindex --sort-section=name |
1808 | @item --sort-section=name | |
bcaa7b3e L |
1809 | This option will apply @code{SORT_BY_NAME} to all wildcard section |
1810 | patterns in the linker script. | |
1811 | ||
2509a395 SL |
1812 | @kindex --sort-section=alignment |
1813 | @item --sort-section=alignment | |
bcaa7b3e L |
1814 | This option will apply @code{SORT_BY_ALIGNMENT} to all wildcard section |
1815 | patterns in the linker script. | |
1816 | ||
252b5132 | 1817 | @kindex --split-by-file |
2509a395 | 1818 | @item --split-by-file[=@var{size}] |
ff5dcc92 | 1819 | Similar to @option{--split-by-reloc} but creates a new output section for |
a854a4a7 AM |
1820 | each input file when @var{size} is reached. @var{size} defaults to a |
1821 | size of 1 if not given. | |
252b5132 RH |
1822 | |
1823 | @kindex --split-by-reloc | |
2509a395 | 1824 | @item --split-by-reloc[=@var{count}] |
a854a4a7 | 1825 | Tries to creates extra sections in the output file so that no single |
252b5132 | 1826 | output section in the file contains more than @var{count} relocations. |
a854a4a7 | 1827 | This is useful when generating huge relocatable files for downloading into |
252b5132 RH |
1828 | certain real time kernels with the COFF object file format; since COFF |
1829 | cannot represent more than 65535 relocations in a single section. Note | |
1830 | that this will fail to work with object file formats which do not | |
1831 | support arbitrary sections. The linker will not split up individual | |
1832 | input sections for redistribution, so if a single input section contains | |
1833 | more than @var{count} relocations one output section will contain that | |
a854a4a7 | 1834 | many relocations. @var{count} defaults to a value of 32768. |
252b5132 RH |
1835 | |
1836 | @kindex --stats | |
1837 | @item --stats | |
1838 | Compute and display statistics about the operation of the linker, such | |
1839 | as execution time and memory usage. | |
1840 | ||
2509a395 | 1841 | @kindex --sysroot=@var{directory} |
e2243057 RS |
1842 | @item --sysroot=@var{directory} |
1843 | Use @var{directory} as the location of the sysroot, overriding the | |
1844 | configure-time default. This option is only supported by linkers | |
1845 | that were configured using @option{--with-sysroot}. | |
1846 | ||
252b5132 RH |
1847 | @kindex --traditional-format |
1848 | @cindex traditional format | |
1849 | @item --traditional-format | |
ff5dcc92 SC |
1850 | For some targets, the output of @command{ld} is different in some ways from |
1851 | the output of some existing linker. This switch requests @command{ld} to | |
252b5132 RH |
1852 | use the traditional format instead. |
1853 | ||
1854 | @cindex dbx | |
ff5dcc92 | 1855 | For example, on SunOS, @command{ld} combines duplicate entries in the |
252b5132 RH |
1856 | symbol string table. This can reduce the size of an output file with |
1857 | full debugging information by over 30 percent. Unfortunately, the SunOS | |
1858 | @code{dbx} program can not read the resulting program (@code{gdb} has no | |
ff5dcc92 | 1859 | trouble). The @samp{--traditional-format} switch tells @command{ld} to not |
252b5132 RH |
1860 | combine duplicate entries. |
1861 | ||
2509a395 SL |
1862 | @kindex --section-start=@var{sectionname}=@var{org} |
1863 | @item --section-start=@var{sectionname}=@var{org} | |
176355da NC |
1864 | Locate a section in the output file at the absolute |
1865 | address given by @var{org}. You may use this option as many | |
1866 | times as necessary to locate multiple sections in the command | |
1867 | line. | |
1868 | @var{org} must be a single hexadecimal integer; | |
1869 | for compatibility with other linkers, you may omit the leading | |
1870 | @samp{0x} usually associated with hexadecimal values. @emph{Note:} there | |
1871 | should be no white space between @var{sectionname}, the equals | |
1872 | sign (``@key{=}''), and @var{org}. | |
1873 | ||
2509a395 SL |
1874 | @kindex -Tbss=@var{org} |
1875 | @kindex -Tdata=@var{org} | |
1876 | @kindex -Ttext=@var{org} | |
252b5132 | 1877 | @cindex segment origins, cmd line |
2509a395 SL |
1878 | @item -Tbss=@var{org} |
1879 | @itemx -Tdata=@var{org} | |
1880 | @itemx -Ttext=@var{org} | |
1881 | Same as @option{--section-start}, with @code{.bss}, @code{.data} or | |
a6e02871 | 1882 | @code{.text} as the @var{sectionname}. |
252b5132 | 1883 | |
2509a395 SL |
1884 | @kindex -Ttext-segment=@var{org} |
1885 | @item -Ttext-segment=@var{org} | |
258795f5 | 1886 | @cindex text segment origin, cmd line |
2b8c06a3 L |
1887 | When creating an ELF executable, it will set the address of the first |
1888 | byte of the text segment. | |
258795f5 | 1889 | |
9d5777a3 RM |
1890 | @kindex -Trodata-segment=@var{org} |
1891 | @item -Trodata-segment=@var{org} | |
1892 | @cindex rodata segment origin, cmd line | |
1893 | When creating an ELF executable or shared object for a target where | |
1894 | the read-only data is in its own segment separate from the executable | |
1895 | text, it will set the address of the first byte of the read-only data segment. | |
1896 | ||
0d705e9f AM |
1897 | @kindex -Tldata-segment=@var{org} |
1898 | @item -Tldata-segment=@var{org} | |
1899 | @cindex ldata segment origin, cmd line | |
1900 | When creating an ELF executable or shared object for x86-64 medium memory | |
1901 | model, it will set the address of the first byte of the ldata segment. | |
1902 | ||
560e09e9 NC |
1903 | @kindex --unresolved-symbols |
1904 | @item --unresolved-symbols=@var{method} | |
1905 | Determine how to handle unresolved symbols. There are four possible | |
1906 | values for @samp{method}: | |
1907 | ||
1908 | @table @samp | |
1909 | @item ignore-all | |
da8bce14 | 1910 | Do not report any unresolved symbols. |
560e09e9 NC |
1911 | |
1912 | @item report-all | |
da8bce14 | 1913 | Report all unresolved symbols. This is the default. |
560e09e9 NC |
1914 | |
1915 | @item ignore-in-object-files | |
1916 | Report unresolved symbols that are contained in shared libraries, but | |
1917 | ignore them if they come from regular object files. | |
1918 | ||
1919 | @item ignore-in-shared-libs | |
1920 | Report unresolved symbols that come from regular object files, but | |
1921 | ignore them if they come from shared libraries. This can be useful | |
1922 | when creating a dynamic binary and it is known that all the shared | |
1923 | libraries that it should be referencing are included on the linker's | |
1924 | command line. | |
1925 | @end table | |
1926 | ||
1927 | The behaviour for shared libraries on their own can also be controlled | |
1928 | by the @option{--[no-]allow-shlib-undefined} option. | |
1929 | ||
1930 | Normally the linker will generate an error message for each reported | |
1931 | unresolved symbol but the option @option{--warn-unresolved-symbols} | |
1932 | can change this to a warning. | |
1933 | ||
1715a13c L |
1934 | @kindex --verbose[=@var{NUMBER}] |
1935 | @cindex verbose[=@var{NUMBER}] | |
252b5132 | 1936 | @item --dll-verbose |
1715a13c | 1937 | @itemx --verbose[=@var{NUMBER}] |
ff5dcc92 | 1938 | Display the version number for @command{ld} and list the linker emulations |
252b5132 | 1939 | supported. Display which input files can and cannot be opened. Display |
1715a13c L |
1940 | the linker script being used by the linker. If the optional @var{NUMBER} |
1941 | argument > 1, plugin symbol status will also be displayed. | |
252b5132 RH |
1942 | |
1943 | @kindex --version-script=@var{version-scriptfile} | |
1944 | @cindex version script, symbol versions | |
2509a395 | 1945 | @item --version-script=@var{version-scriptfile} |
252b5132 RH |
1946 | Specify the name of a version script to the linker. This is typically |
1947 | used when creating shared libraries to specify additional information | |
36f63dca | 1948 | about the version hierarchy for the library being created. This option |
09e2aba4 DK |
1949 | is only fully supported on ELF platforms which support shared libraries; |
1950 | see @ref{VERSION}. It is partially supported on PE platforms, which can | |
1951 | use version scripts to filter symbol visibility in auto-export mode: any | |
1952 | symbols marked @samp{local} in the version script will not be exported. | |
1953 | @xref{WIN32}. | |
252b5132 | 1954 | |
7ce691ae | 1955 | @kindex --warn-common |
252b5132 RH |
1956 | @cindex warnings, on combining symbols |
1957 | @cindex combining symbols, warnings on | |
1958 | @item --warn-common | |
1959 | Warn when a common symbol is combined with another common symbol or with | |
11e7fd74 | 1960 | a symbol definition. Unix linkers allow this somewhat sloppy practice, |
252b5132 RH |
1961 | but linkers on some other operating systems do not. This option allows |
1962 | you to find potential problems from combining global symbols. | |
11e7fd74 | 1963 | Unfortunately, some C libraries use this practice, so you may get some |
252b5132 RH |
1964 | warnings about symbols in the libraries as well as in your programs. |
1965 | ||
1966 | There are three kinds of global symbols, illustrated here by C examples: | |
1967 | ||
1968 | @table @samp | |
1969 | @item int i = 1; | |
1970 | A definition, which goes in the initialized data section of the output | |
1971 | file. | |
1972 | ||
1973 | @item extern int i; | |
1974 | An undefined reference, which does not allocate space. | |
1975 | There must be either a definition or a common symbol for the | |
1976 | variable somewhere. | |
1977 | ||
1978 | @item int i; | |
1979 | A common symbol. If there are only (one or more) common symbols for a | |
1980 | variable, it goes in the uninitialized data area of the output file. | |
1981 | The linker merges multiple common symbols for the same variable into a | |
1982 | single symbol. If they are of different sizes, it picks the largest | |
1983 | size. The linker turns a common symbol into a declaration, if there is | |
1984 | a definition of the same variable. | |
1985 | @end table | |
1986 | ||
1987 | The @samp{--warn-common} option can produce five kinds of warnings. | |
1988 | Each warning consists of a pair of lines: the first describes the symbol | |
1989 | just encountered, and the second describes the previous symbol | |
1990 | encountered with the same name. One or both of the two symbols will be | |
1991 | a common symbol. | |
1992 | ||
1993 | @enumerate | |
1994 | @item | |
1995 | Turning a common symbol into a reference, because there is already a | |
1996 | definition for the symbol. | |
1997 | @smallexample | |
1998 | @var{file}(@var{section}): warning: common of `@var{symbol}' | |
1999 | overridden by definition | |
2000 | @var{file}(@var{section}): warning: defined here | |
2001 | @end smallexample | |
2002 | ||
2003 | @item | |
2004 | Turning a common symbol into a reference, because a later definition for | |
2005 | the symbol is encountered. This is the same as the previous case, | |
2006 | except that the symbols are encountered in a different order. | |
2007 | @smallexample | |
2008 | @var{file}(@var{section}): warning: definition of `@var{symbol}' | |
2009 | overriding common | |
2010 | @var{file}(@var{section}): warning: common is here | |
2011 | @end smallexample | |
2012 | ||
2013 | @item | |
2014 | Merging a common symbol with a previous same-sized common symbol. | |
2015 | @smallexample | |
2016 | @var{file}(@var{section}): warning: multiple common | |
2017 | of `@var{symbol}' | |
2018 | @var{file}(@var{section}): warning: previous common is here | |
2019 | @end smallexample | |
2020 | ||
2021 | @item | |
2022 | Merging a common symbol with a previous larger common symbol. | |
2023 | @smallexample | |
2024 | @var{file}(@var{section}): warning: common of `@var{symbol}' | |
2025 | overridden by larger common | |
2026 | @var{file}(@var{section}): warning: larger common is here | |
2027 | @end smallexample | |
2028 | ||
2029 | @item | |
2030 | Merging a common symbol with a previous smaller common symbol. This is | |
2031 | the same as the previous case, except that the symbols are | |
2032 | encountered in a different order. | |
2033 | @smallexample | |
2034 | @var{file}(@var{section}): warning: common of `@var{symbol}' | |
2035 | overriding smaller common | |
2036 | @var{file}(@var{section}): warning: smaller common is here | |
2037 | @end smallexample | |
2038 | @end enumerate | |
2039 | ||
2040 | @kindex --warn-constructors | |
2041 | @item --warn-constructors | |
2042 | Warn if any global constructors are used. This is only useful for a few | |
2043 | object file formats. For formats like COFF or ELF, the linker can not | |
2044 | detect the use of global constructors. | |
2045 | ||
2046 | @kindex --warn-multiple-gp | |
2047 | @item --warn-multiple-gp | |
2048 | Warn if multiple global pointer values are required in the output file. | |
2049 | This is only meaningful for certain processors, such as the Alpha. | |
2050 | Specifically, some processors put large-valued constants in a special | |
2051 | section. A special register (the global pointer) points into the middle | |
2052 | of this section, so that constants can be loaded efficiently via a | |
2053 | base-register relative addressing mode. Since the offset in | |
2054 | base-register relative mode is fixed and relatively small (e.g., 16 | |
2055 | bits), this limits the maximum size of the constant pool. Thus, in | |
2056 | large programs, it is often necessary to use multiple global pointer | |
2057 | values in order to be able to address all possible constants. This | |
2058 | option causes a warning to be issued whenever this case occurs. | |
2059 | ||
2060 | @kindex --warn-once | |
2061 | @cindex warnings, on undefined symbols | |
2062 | @cindex undefined symbols, warnings on | |
2063 | @item --warn-once | |
2064 | Only warn once for each undefined symbol, rather than once per module | |
2065 | which refers to it. | |
2066 | ||
3ea60775 NC |
2067 | @kindex --warn-orphan |
2068 | @kindex --no-warn-orphan | |
2069 | @cindex warnings, on orphan sections | |
2070 | @cindex orphan sections, warnings on | |
2071 | @item --warn-orphan | |
2072 | The @option{--warn-orphan} option tells the linker to generate a | |
2073 | warning message whenever it has to place an orphan section into the | |
2074 | output file. @xref{Orphan Sections} The @option{--no-warn-orphan} | |
2075 | option restores the default behaviour of just silently placing these | |
2076 | sections. | |
2077 | ||
252b5132 RH |
2078 | @kindex --warn-section-align |
2079 | @cindex warnings, on section alignment | |
2080 | @cindex section alignment, warnings on | |
2081 | @item --warn-section-align | |
2082 | Warn if the address of an output section is changed because of | |
2083 | alignment. Typically, the alignment will be set by an input section. | |
2084 | The address will only be changed if it not explicitly specified; that | |
2085 | is, if the @code{SECTIONS} command does not specify a start address for | |
2086 | the section (@pxref{SECTIONS}). | |
2087 | ||
8fdd7217 NC |
2088 | @kindex --warn-shared-textrel |
2089 | @item --warn-shared-textrel | |
ece2d90e | 2090 | Warn if the linker adds a DT_TEXTREL to a shared object. |
8fdd7217 | 2091 | |
a0c402a5 L |
2092 | @kindex --warn-alternate-em |
2093 | @item --warn-alternate-em | |
2094 | Warn if an object has alternate ELF machine code. | |
2095 | ||
560e09e9 NC |
2096 | @kindex --warn-unresolved-symbols |
2097 | @item --warn-unresolved-symbols | |
2098 | If the linker is going to report an unresolved symbol (see the option | |
2099 | @option{--unresolved-symbols}) it will normally generate an error. | |
2100 | This option makes it generate a warning instead. | |
2101 | ||
2102 | @kindex --error-unresolved-symbols | |
2103 | @item --error-unresolved-symbols | |
2104 | This restores the linker's default behaviour of generating errors when | |
2105 | it is reporting unresolved symbols. | |
2106 | ||
252b5132 RH |
2107 | @kindex --whole-archive |
2108 | @cindex including an entire archive | |
2109 | @item --whole-archive | |
2110 | For each archive mentioned on the command line after the | |
ff5dcc92 | 2111 | @option{--whole-archive} option, include every object file in the archive |
252b5132 RH |
2112 | in the link, rather than searching the archive for the required object |
2113 | files. This is normally used to turn an archive file into a shared | |
2114 | library, forcing every object to be included in the resulting shared | |
2115 | library. This option may be used more than once. | |
2116 | ||
7ec229ce | 2117 | Two notes when using this option from gcc: First, gcc doesn't know |
ff5dcc92 SC |
2118 | about this option, so you have to use @option{-Wl,-whole-archive}. |
2119 | Second, don't forget to use @option{-Wl,-no-whole-archive} after your | |
7ec229ce DD |
2120 | list of archives, because gcc will add its own list of archives to |
2121 | your link and you may not want this flag to affect those as well. | |
2122 | ||
2509a395 SL |
2123 | @kindex --wrap=@var{symbol} |
2124 | @item --wrap=@var{symbol} | |
252b5132 RH |
2125 | Use a wrapper function for @var{symbol}. Any undefined reference to |
2126 | @var{symbol} will be resolved to @code{__wrap_@var{symbol}}. Any | |
2127 | undefined reference to @code{__real_@var{symbol}} will be resolved to | |
2128 | @var{symbol}. | |
2129 | ||
2130 | This can be used to provide a wrapper for a system function. The | |
2131 | wrapper function should be called @code{__wrap_@var{symbol}}. If it | |
2132 | wishes to call the system function, it should call | |
2133 | @code{__real_@var{symbol}}. | |
2134 | ||
2135 | Here is a trivial example: | |
2136 | ||
2137 | @smallexample | |
2138 | void * | |
cc2f008e | 2139 | __wrap_malloc (size_t c) |
252b5132 | 2140 | @{ |
cc2f008e | 2141 | printf ("malloc called with %zu\n", c); |
252b5132 RH |
2142 | return __real_malloc (c); |
2143 | @} | |
2144 | @end smallexample | |
2145 | ||
ff5dcc92 | 2146 | If you link other code with this file using @option{--wrap malloc}, then |
252b5132 RH |
2147 | all calls to @code{malloc} will call the function @code{__wrap_malloc} |
2148 | instead. The call to @code{__real_malloc} in @code{__wrap_malloc} will | |
2149 | call the real @code{malloc} function. | |
2150 | ||
2151 | You may wish to provide a @code{__real_malloc} function as well, so that | |
ff5dcc92 | 2152 | links without the @option{--wrap} option will succeed. If you do this, |
252b5132 RH |
2153 | you should not put the definition of @code{__real_malloc} in the same |
2154 | file as @code{__wrap_malloc}; if you do, the assembler may resolve the | |
2155 | call before the linker has a chance to wrap it to @code{malloc}. | |
2156 | ||
6aa29e7b JJ |
2157 | @kindex --eh-frame-hdr |
2158 | @item --eh-frame-hdr | |
2159 | Request creation of @code{.eh_frame_hdr} section and ELF | |
2160 | @code{PT_GNU_EH_FRAME} segment header. | |
2161 | ||
e41b3a13 JJ |
2162 | @kindex --ld-generated-unwind-info |
2163 | @item --no-ld-generated-unwind-info | |
2164 | Request creation of @code{.eh_frame} unwind info for linker | |
2165 | generated code sections like PLT. This option is on by default | |
2166 | if linker generated unwind info is supported. | |
2167 | ||
6c1439be L |
2168 | @kindex --enable-new-dtags |
2169 | @kindex --disable-new-dtags | |
2170 | @item --enable-new-dtags | |
2171 | @itemx --disable-new-dtags | |
2172 | This linker can create the new dynamic tags in ELF. But the older ELF | |
2173 | systems may not understand them. If you specify | |
b1b00fcc MF |
2174 | @option{--enable-new-dtags}, the new dynamic tags will be created as needed |
2175 | and older dynamic tags will be omitted. | |
ff5dcc92 | 2176 | If you specify @option{--disable-new-dtags}, no new dynamic tags will be |
6c1439be L |
2177 | created. By default, the new dynamic tags are not created. Note that |
2178 | those options are only available for ELF systems. | |
2179 | ||
2d643429 | 2180 | @kindex --hash-size=@var{number} |
e185dd51 | 2181 | @item --hash-size=@var{number} |
2d643429 NC |
2182 | Set the default size of the linker's hash tables to a prime number |
2183 | close to @var{number}. Increasing this value can reduce the length of | |
2184 | time it takes the linker to perform its tasks, at the expense of | |
2185 | increasing the linker's memory requirements. Similarly reducing this | |
2186 | value can reduce the memory requirements at the expense of speed. | |
2187 | ||
fdc90cb4 JJ |
2188 | @kindex --hash-style=@var{style} |
2189 | @item --hash-style=@var{style} | |
2190 | Set the type of linker's hash table(s). @var{style} can be either | |
2191 | @code{sysv} for classic ELF @code{.hash} section, @code{gnu} for | |
2192 | new style GNU @code{.gnu.hash} section or @code{both} for both | |
2193 | the classic ELF @code{.hash} and new style GNU @code{.gnu.hash} | |
2194 | hash tables. The default is @code{sysv}. | |
2195 | ||
35835446 JR |
2196 | @kindex --reduce-memory-overheads |
2197 | @item --reduce-memory-overheads | |
2198 | This option reduces memory requirements at ld runtime, at the expense of | |
f2a8f148 | 2199 | linking speed. This was introduced to select the old O(n^2) algorithm |
35835446 | 2200 | for link map file generation, rather than the new O(n) algorithm which uses |
2d643429 NC |
2201 | about 40% more memory for symbol storage. |
2202 | ||
4f9c04f7 | 2203 | Another effect of the switch is to set the default hash table size to |
2d643429 | 2204 | 1021, which again saves memory at the cost of lengthening the linker's |
a85785bc | 2205 | run time. This is not done however if the @option{--hash-size} switch |
2d643429 NC |
2206 | has been used. |
2207 | ||
2208 | The @option{--reduce-memory-overheads} switch may be also be used to | |
2209 | enable other tradeoffs in future versions of the linker. | |
35835446 | 2210 | |
c0065db7 RM |
2211 | @kindex --build-id |
2212 | @kindex --build-id=@var{style} | |
2213 | @item --build-id | |
2214 | @itemx --build-id=@var{style} | |
61e2488c JT |
2215 | Request the creation of a @code{.note.gnu.build-id} ELF note section |
2216 | or a @code{.build-id} COFF section. The contents of the note are | |
2217 | unique bits identifying this linked file. @var{style} can be | |
2218 | @code{uuid} to use 128 random bits, @code{sha1} to use a 160-bit | |
2219 | @sc{SHA1} hash on the normative parts of the output contents, | |
2220 | @code{md5} to use a 128-bit @sc{MD5} hash on the normative parts of | |
2221 | the output contents, or @code{0x@var{hexstring}} to use a chosen bit | |
2222 | string specified as an even number of hexadecimal digits (@code{-} and | |
2223 | @code{:} characters between digit pairs are ignored). If @var{style} | |
2224 | is omitted, @code{sha1} is used. | |
24382dca RM |
2225 | |
2226 | The @code{md5} and @code{sha1} styles produces an identifier | |
2227 | that is always the same in an identical output file, but will be | |
2228 | unique among all nonidentical output files. It is not intended | |
2229 | to be compared as a checksum for the file's contents. A linked | |
2230 | file may be changed later by other tools, but the build ID bit | |
2231 | string identifying the original linked file does not change. | |
c0065db7 RM |
2232 | |
2233 | Passing @code{none} for @var{style} disables the setting from any | |
2234 | @code{--build-id} options earlier on the command line. | |
252b5132 RH |
2235 | @end table |
2236 | ||
0285c67d NC |
2237 | @c man end |
2238 | ||
36f63dca | 2239 | @subsection Options Specific to i386 PE Targets |
252b5132 | 2240 | |
0285c67d NC |
2241 | @c man begin OPTIONS |
2242 | ||
ff5dcc92 | 2243 | The i386 PE linker supports the @option{-shared} option, which causes |
252b5132 RH |
2244 | the output to be a dynamically linked library (DLL) instead of a |
2245 | normal executable. You should name the output @code{*.dll} when you | |
2246 | use this option. In addition, the linker fully supports the standard | |
2247 | @code{*.def} files, which may be specified on the linker command line | |
2248 | like an object file (in fact, it should precede archives it exports | |
2249 | symbols from, to ensure that they get linked in, just like a normal | |
2250 | object file). | |
2251 | ||
2252 | In addition to the options common to all targets, the i386 PE linker | |
2253 | support additional command line options that are specific to the i386 | |
2254 | PE target. Options that take values may be separated from their | |
2255 | values by either a space or an equals sign. | |
2256 | ||
ff5dcc92 | 2257 | @table @gcctabopt |
252b5132 RH |
2258 | |
2259 | @kindex --add-stdcall-alias | |
2260 | @item --add-stdcall-alias | |
2261 | If given, symbols with a stdcall suffix (@@@var{nn}) will be exported | |
2262 | as-is and also with the suffix stripped. | |
bb10df36 | 2263 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 RH |
2264 | |
2265 | @kindex --base-file | |
2266 | @item --base-file @var{file} | |
2267 | Use @var{file} as the name of a file in which to save the base | |
2268 | addresses of all the relocations needed for generating DLLs with | |
2269 | @file{dlltool}. | |
bb10df36 | 2270 | [This is an i386 PE specific option] |
252b5132 RH |
2271 | |
2272 | @kindex --dll | |
2273 | @item --dll | |
2274 | Create a DLL instead of a regular executable. You may also use | |
ff5dcc92 | 2275 | @option{-shared} or specify a @code{LIBRARY} in a given @code{.def} |
252b5132 | 2276 | file. |
bb10df36 | 2277 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 | 2278 | |
88183869 DK |
2279 | @kindex --enable-long-section-names |
2280 | @kindex --disable-long-section-names | |
2281 | @item --enable-long-section-names | |
2282 | @itemx --disable-long-section-names | |
2283 | The PE variants of the Coff object format add an extension that permits | |
2284 | the use of section names longer than eight characters, the normal limit | |
2285 | for Coff. By default, these names are only allowed in object files, as | |
2286 | fully-linked executable images do not carry the Coff string table required | |
2287 | to support the longer names. As a GNU extension, it is possible to | |
2288 | allow their use in executable images as well, or to (probably pointlessly!) | |
2289 | disallow it in object files, by using these two options. Executable images | |
2290 | generated with these long section names are slightly non-standard, carrying | |
2291 | as they do a string table, and may generate confusing output when examined | |
9d5777a3 RM |
2292 | with non-GNU PE-aware tools, such as file viewers and dumpers. However, |
2293 | GDB relies on the use of PE long section names to find Dwarf-2 debug | |
3efd345c DK |
2294 | information sections in an executable image at runtime, and so if neither |
2295 | option is specified on the command-line, @command{ld} will enable long | |
2296 | section names, overriding the default and technically correct behaviour, | |
2297 | when it finds the presence of debug information while linking an executable | |
2298 | image and not stripping symbols. | |
88183869 DK |
2299 | [This option is valid for all PE targeted ports of the linker] |
2300 | ||
252b5132 RH |
2301 | @kindex --enable-stdcall-fixup |
2302 | @kindex --disable-stdcall-fixup | |
2303 | @item --enable-stdcall-fixup | |
2304 | @itemx --disable-stdcall-fixup | |
2305 | If the link finds a symbol that it cannot resolve, it will attempt to | |
36f63dca | 2306 | do ``fuzzy linking'' by looking for another defined symbol that differs |
252b5132 RH |
2307 | only in the format of the symbol name (cdecl vs stdcall) and will |
2308 | resolve that symbol by linking to the match. For example, the | |
2309 | undefined symbol @code{_foo} might be linked to the function | |
2310 | @code{_foo@@12}, or the undefined symbol @code{_bar@@16} might be linked | |
2311 | to the function @code{_bar}. When the linker does this, it prints a | |
2312 | warning, since it normally should have failed to link, but sometimes | |
2313 | import libraries generated from third-party dlls may need this feature | |
ff5dcc92 | 2314 | to be usable. If you specify @option{--enable-stdcall-fixup}, this |
252b5132 | 2315 | feature is fully enabled and warnings are not printed. If you specify |
ff5dcc92 | 2316 | @option{--disable-stdcall-fixup}, this feature is disabled and such |
252b5132 | 2317 | mismatches are considered to be errors. |
bb10df36 | 2318 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 | 2319 | |
522f09cd KT |
2320 | @kindex --leading-underscore |
2321 | @kindex --no-leading-underscore | |
2322 | @item --leading-underscore | |
2323 | @itemx --no-leading-underscore | |
2324 | For most targets default symbol-prefix is an underscore and is defined | |
2325 | in target's description. By this option it is possible to | |
2326 | disable/enable the default underscore symbol-prefix. | |
2327 | ||
252b5132 RH |
2328 | @cindex DLLs, creating |
2329 | @kindex --export-all-symbols | |
2330 | @item --export-all-symbols | |
2331 | If given, all global symbols in the objects used to build a DLL will | |
2332 | be exported by the DLL. Note that this is the default if there | |
2333 | otherwise wouldn't be any exported symbols. When symbols are | |
2334 | explicitly exported via DEF files or implicitly exported via function | |
2335 | attributes, the default is to not export anything else unless this | |
2336 | option is given. Note that the symbols @code{DllMain@@12}, | |
ece2d90e | 2337 | @code{DllEntryPoint@@0}, @code{DllMainCRTStartup@@12}, and |
b044cda1 | 2338 | @code{impure_ptr} will not be automatically |
ece2d90e NC |
2339 | exported. Also, symbols imported from other DLLs will not be |
2340 | re-exported, nor will symbols specifying the DLL's internal layout | |
2341 | such as those beginning with @code{_head_} or ending with | |
2342 | @code{_iname}. In addition, no symbols from @code{libgcc}, | |
b044cda1 CW |
2343 | @code{libstd++}, @code{libmingw32}, or @code{crtX.o} will be exported. |
2344 | Symbols whose names begin with @code{__rtti_} or @code{__builtin_} will | |
2345 | not be exported, to help with C++ DLLs. Finally, there is an | |
ece2d90e | 2346 | extensive list of cygwin-private symbols that are not exported |
b044cda1 | 2347 | (obviously, this applies on when building DLLs for cygwin targets). |
ece2d90e | 2348 | These cygwin-excludes are: @code{_cygwin_dll_entry@@12}, |
b044cda1 | 2349 | @code{_cygwin_crt0_common@@8}, @code{_cygwin_noncygwin_dll_entry@@12}, |
ece2d90e | 2350 | @code{_fmode}, @code{_impure_ptr}, @code{cygwin_attach_dll}, |
b044cda1 | 2351 | @code{cygwin_premain0}, @code{cygwin_premain1}, @code{cygwin_premain2}, |
ece2d90e | 2352 | @code{cygwin_premain3}, and @code{environ}. |
bb10df36 | 2353 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 RH |
2354 | |
2355 | @kindex --exclude-symbols | |
1d0a3c9c | 2356 | @item --exclude-symbols @var{symbol},@var{symbol},... |
252b5132 RH |
2357 | Specifies a list of symbols which should not be automatically |
2358 | exported. The symbol names may be delimited by commas or colons. | |
bb10df36 | 2359 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 | 2360 | |
2927aaca NC |
2361 | @kindex --exclude-all-symbols |
2362 | @item --exclude-all-symbols | |
2363 | Specifies no symbols should be automatically exported. | |
2364 | [This option is specific to the i386 PE targeted port of the linker] | |
2365 | ||
252b5132 RH |
2366 | @kindex --file-alignment |
2367 | @item --file-alignment | |
2368 | Specify the file alignment. Sections in the file will always begin at | |
2369 | file offsets which are multiples of this number. This defaults to | |
2370 | 512. | |
bb10df36 | 2371 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 RH |
2372 | |
2373 | @cindex heap size | |
2374 | @kindex --heap | |
2375 | @item --heap @var{reserve} | |
2376 | @itemx --heap @var{reserve},@var{commit} | |
a00b50c5 | 2377 | Specify the number of bytes of memory to reserve (and optionally commit) |
fe6d7d6a | 2378 | to be used as heap for this program. The default is 1MB reserved, 4K |
252b5132 | 2379 | committed. |
bb10df36 | 2380 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 RH |
2381 | |
2382 | @cindex image base | |
2383 | @kindex --image-base | |
2384 | @item --image-base @var{value} | |
2385 | Use @var{value} as the base address of your program or dll. This is | |
2386 | the lowest memory location that will be used when your program or dll | |
2387 | is loaded. To reduce the need to relocate and improve performance of | |
2388 | your dlls, each should have a unique base address and not overlap any | |
2389 | other dlls. The default is 0x400000 for executables, and 0x10000000 | |
2390 | for dlls. | |
bb10df36 | 2391 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 RH |
2392 | |
2393 | @kindex --kill-at | |
2394 | @item --kill-at | |
2395 | If given, the stdcall suffixes (@@@var{nn}) will be stripped from | |
2396 | symbols before they are exported. | |
bb10df36 | 2397 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 | 2398 | |
26d2d8a2 BF |
2399 | @kindex --large-address-aware |
2400 | @item --large-address-aware | |
b45619c0 | 2401 | If given, the appropriate bit in the ``Characteristics'' field of the COFF |
26d2d8a2 | 2402 | header is set to indicate that this executable supports virtual addresses |
b45619c0 | 2403 | greater than 2 gigabytes. This should be used in conjunction with the /3GB |
26d2d8a2 BF |
2404 | or /USERVA=@var{value} megabytes switch in the ``[operating systems]'' |
2405 | section of the BOOT.INI. Otherwise, this bit has no effect. | |
2406 | [This option is specific to PE targeted ports of the linker] | |
2407 | ||
f69a2f97 NC |
2408 | @kindex --disable-large-address-aware |
2409 | @item --disable-large-address-aware | |
2410 | Reverts the effect of a previous @samp{--large-address-aware} option. | |
2411 | This is useful if @samp{--large-address-aware} is always set by the compiler | |
2412 | driver (e.g. Cygwin gcc) and the executable does not support virtual | |
2413 | addresses greater than 2 gigabytes. | |
2414 | [This option is specific to PE targeted ports of the linker] | |
2415 | ||
252b5132 RH |
2416 | @kindex --major-image-version |
2417 | @item --major-image-version @var{value} | |
36f63dca | 2418 | Sets the major number of the ``image version''. Defaults to 1. |
bb10df36 | 2419 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 RH |
2420 | |
2421 | @kindex --major-os-version | |
2422 | @item --major-os-version @var{value} | |
36f63dca | 2423 | Sets the major number of the ``os version''. Defaults to 4. |
bb10df36 | 2424 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 RH |
2425 | |
2426 | @kindex --major-subsystem-version | |
2427 | @item --major-subsystem-version @var{value} | |
36f63dca | 2428 | Sets the major number of the ``subsystem version''. Defaults to 4. |
bb10df36 | 2429 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 RH |
2430 | |
2431 | @kindex --minor-image-version | |
2432 | @item --minor-image-version @var{value} | |
36f63dca | 2433 | Sets the minor number of the ``image version''. Defaults to 0. |
bb10df36 | 2434 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 RH |
2435 | |
2436 | @kindex --minor-os-version | |
2437 | @item --minor-os-version @var{value} | |
36f63dca | 2438 | Sets the minor number of the ``os version''. Defaults to 0. |
bb10df36 | 2439 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 RH |
2440 | |
2441 | @kindex --minor-subsystem-version | |
2442 | @item --minor-subsystem-version @var{value} | |
36f63dca | 2443 | Sets the minor number of the ``subsystem version''. Defaults to 0. |
bb10df36 | 2444 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 RH |
2445 | |
2446 | @cindex DEF files, creating | |
2447 | @cindex DLLs, creating | |
2448 | @kindex --output-def | |
2449 | @item --output-def @var{file} | |
2450 | The linker will create the file @var{file} which will contain a DEF | |
2451 | file corresponding to the DLL the linker is generating. This DEF file | |
2452 | (which should be called @code{*.def}) may be used to create an import | |
2453 | library with @code{dlltool} or may be used as a reference to | |
2454 | automatically or implicitly exported symbols. | |
bb10df36 | 2455 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 | 2456 | |
b044cda1 CW |
2457 | @cindex DLLs, creating |
2458 | @kindex --out-implib | |
2459 | @item --out-implib @var{file} | |
2460 | The linker will create the file @var{file} which will contain an | |
2461 | import lib corresponding to the DLL the linker is generating. This | |
2462 | import lib (which should be called @code{*.dll.a} or @code{*.a} | |
560e09e9 | 2463 | may be used to link clients against the generated DLL; this behaviour |
b044cda1 CW |
2464 | makes it possible to skip a separate @code{dlltool} import library |
2465 | creation step. | |
bb10df36 | 2466 | [This option is specific to the i386 PE targeted port of the linker] |
b044cda1 CW |
2467 | |
2468 | @kindex --enable-auto-image-base | |
2469 | @item --enable-auto-image-base | |
d0e6d77b CF |
2470 | @itemx --enable-auto-image-base=@var{value} |
2471 | Automatically choose the image base for DLLs, optionally starting with base | |
2472 | @var{value}, unless one is specified using the @code{--image-base} argument. | |
2473 | By using a hash generated from the dllname to create unique image bases | |
2474 | for each DLL, in-memory collisions and relocations which can delay program | |
2475 | execution are avoided. | |
bb10df36 | 2476 | [This option is specific to the i386 PE targeted port of the linker] |
b044cda1 CW |
2477 | |
2478 | @kindex --disable-auto-image-base | |
2479 | @item --disable-auto-image-base | |
2480 | Do not automatically generate a unique image base. If there is no | |
2481 | user-specified image base (@code{--image-base}) then use the platform | |
2482 | default. | |
bb10df36 | 2483 | [This option is specific to the i386 PE targeted port of the linker] |
b044cda1 CW |
2484 | |
2485 | @cindex DLLs, linking to | |
2486 | @kindex --dll-search-prefix | |
2487 | @item --dll-search-prefix @var{string} | |
489d0400 | 2488 | When linking dynamically to a dll without an import library, |
ece2d90e | 2489 | search for @code{<string><basename>.dll} in preference to |
560e09e9 | 2490 | @code{lib<basename>.dll}. This behaviour allows easy distinction |
b044cda1 CW |
2491 | between DLLs built for the various "subplatforms": native, cygwin, |
2492 | uwin, pw, etc. For instance, cygwin DLLs typically use | |
ece2d90e | 2493 | @code{--dll-search-prefix=cyg}. |
bb10df36 | 2494 | [This option is specific to the i386 PE targeted port of the linker] |
b044cda1 CW |
2495 | |
2496 | @kindex --enable-auto-import | |
2497 | @item --enable-auto-import | |
ece2d90e NC |
2498 | Do sophisticated linking of @code{_symbol} to @code{__imp__symbol} for |
2499 | DATA imports from DLLs, and create the necessary thunking symbols when | |
4d8907ac DS |
2500 | building the import libraries with those DATA exports. Note: Use of the |
2501 | 'auto-import' extension will cause the text section of the image file | |
2502 | to be made writable. This does not conform to the PE-COFF format | |
2503 | specification published by Microsoft. | |
2504 | ||
e2a83dd0 NC |
2505 | Note - use of the 'auto-import' extension will also cause read only |
2506 | data which would normally be placed into the .rdata section to be | |
2507 | placed into the .data section instead. This is in order to work | |
2508 | around a problem with consts that is described here: | |
2509 | http://www.cygwin.com/ml/cygwin/2004-09/msg01101.html | |
2510 | ||
4d8907ac DS |
2511 | Using 'auto-import' generally will 'just work' -- but sometimes you may |
2512 | see this message: | |
0d888aac | 2513 | |
ece2d90e | 2514 | "variable '<var>' can't be auto-imported. Please read the |
0d888aac CW |
2515 | documentation for ld's @code{--enable-auto-import} for details." |
2516 | ||
ece2d90e NC |
2517 | This message occurs when some (sub)expression accesses an address |
2518 | ultimately given by the sum of two constants (Win32 import tables only | |
c0065db7 RM |
2519 | allow one). Instances where this may occur include accesses to member |
2520 | fields of struct variables imported from a DLL, as well as using a | |
2521 | constant index into an array variable imported from a DLL. Any | |
2f8d8971 NC |
2522 | multiword variable (arrays, structs, long long, etc) may trigger |
2523 | this error condition. However, regardless of the exact data type | |
2524 | of the offending exported variable, ld will always detect it, issue | |
2525 | the warning, and exit. | |
2526 | ||
2527 | There are several ways to address this difficulty, regardless of the | |
2528 | data type of the exported variable: | |
0d888aac | 2529 | |
2fa9fc65 NC |
2530 | One way is to use --enable-runtime-pseudo-reloc switch. This leaves the task |
2531 | of adjusting references in your client code for runtime environment, so | |
560e09e9 | 2532 | this method works only when runtime environment supports this feature. |
2fa9fc65 | 2533 | |
c0065db7 RM |
2534 | A second solution is to force one of the 'constants' to be a variable -- |
2535 | that is, unknown and un-optimizable at compile time. For arrays, | |
2536 | there are two possibilities: a) make the indexee (the array's address) | |
0d888aac CW |
2537 | a variable, or b) make the 'constant' index a variable. Thus: |
2538 | ||
2539 | @example | |
2540 | extern type extern_array[]; | |
c0065db7 | 2541 | extern_array[1] --> |
0d888aac CW |
2542 | @{ volatile type *t=extern_array; t[1] @} |
2543 | @end example | |
2544 | ||
2545 | or | |
2546 | ||
2547 | @example | |
2548 | extern type extern_array[]; | |
c0065db7 | 2549 | extern_array[1] --> |
0d888aac CW |
2550 | @{ volatile int t=1; extern_array[t] @} |
2551 | @end example | |
2552 | ||
c0065db7 | 2553 | For structs (and most other multiword data types) the only option |
2f8d8971 | 2554 | is to make the struct itself (or the long long, or the ...) variable: |
0d888aac CW |
2555 | |
2556 | @example | |
2557 | extern struct s extern_struct; | |
c0065db7 | 2558 | extern_struct.field --> |
0d888aac CW |
2559 | @{ volatile struct s *t=&extern_struct; t->field @} |
2560 | @end example | |
2561 | ||
c406afaf NC |
2562 | or |
2563 | ||
2564 | @example | |
2565 | extern long long extern_ll; | |
2566 | extern_ll --> | |
2567 | @{ volatile long long * local_ll=&extern_ll; *local_ll @} | |
2568 | @end example | |
2569 | ||
2fa9fc65 | 2570 | A third method of dealing with this difficulty is to abandon |
c0065db7 | 2571 | 'auto-import' for the offending symbol and mark it with |
11e7fd74 | 2572 | @code{__declspec(dllimport)}. However, in practice that |
0d888aac | 2573 | requires using compile-time #defines to indicate whether you are |
c0065db7 RM |
2574 | building a DLL, building client code that will link to the DLL, or |
2575 | merely building/linking to a static library. In making the choice | |
2576 | between the various methods of resolving the 'direct address with | |
0d888aac CW |
2577 | constant offset' problem, you should consider typical real-world usage: |
2578 | ||
2579 | Original: | |
2580 | @example | |
2581 | --foo.h | |
2582 | extern int arr[]; | |
2583 | --foo.c | |
2584 | #include "foo.h" | |
2585 | void main(int argc, char **argv)@{ | |
2586 | printf("%d\n",arr[1]); | |
2587 | @} | |
2588 | @end example | |
2589 | ||
2590 | Solution 1: | |
2591 | @example | |
2592 | --foo.h | |
2593 | extern int arr[]; | |
2594 | --foo.c | |
2595 | #include "foo.h" | |
2596 | void main(int argc, char **argv)@{ | |
2597 | /* This workaround is for win32 and cygwin; do not "optimize" */ | |
2598 | volatile int *parr = arr; | |
2599 | printf("%d\n",parr[1]); | |
2600 | @} | |
2601 | @end example | |
2602 | ||
2603 | Solution 2: | |
2604 | @example | |
2605 | --foo.h | |
2606 | /* Note: auto-export is assumed (no __declspec(dllexport)) */ | |
2607 | #if (defined(_WIN32) || defined(__CYGWIN__)) && \ | |
2608 | !(defined(FOO_BUILD_DLL) || defined(FOO_STATIC)) | |
2609 | #define FOO_IMPORT __declspec(dllimport) | |
2610 | #else | |
2611 | #define FOO_IMPORT | |
2612 | #endif | |
2613 | extern FOO_IMPORT int arr[]; | |
2614 | --foo.c | |
2615 | #include "foo.h" | |
2616 | void main(int argc, char **argv)@{ | |
2617 | printf("%d\n",arr[1]); | |
2618 | @} | |
2619 | @end example | |
2620 | ||
c0065db7 | 2621 | A fourth way to avoid this problem is to re-code your |
0d888aac CW |
2622 | library to use a functional interface rather than a data interface |
2623 | for the offending variables (e.g. set_foo() and get_foo() accessor | |
2624 | functions). | |
bb10df36 | 2625 | [This option is specific to the i386 PE targeted port of the linker] |
b044cda1 CW |
2626 | |
2627 | @kindex --disable-auto-import | |
2628 | @item --disable-auto-import | |
c0065db7 | 2629 | Do not attempt to do sophisticated linking of @code{_symbol} to |
b044cda1 | 2630 | @code{__imp__symbol} for DATA imports from DLLs. |
bb10df36 | 2631 | [This option is specific to the i386 PE targeted port of the linker] |
b044cda1 | 2632 | |
2fa9fc65 NC |
2633 | @kindex --enable-runtime-pseudo-reloc |
2634 | @item --enable-runtime-pseudo-reloc | |
2635 | If your code contains expressions described in --enable-auto-import section, | |
2636 | that is, DATA imports from DLL with non-zero offset, this switch will create | |
2637 | a vector of 'runtime pseudo relocations' which can be used by runtime | |
c0065db7 | 2638 | environment to adjust references to such data in your client code. |
bb10df36 | 2639 | [This option is specific to the i386 PE targeted port of the linker] |
2fa9fc65 NC |
2640 | |
2641 | @kindex --disable-runtime-pseudo-reloc | |
2642 | @item --disable-runtime-pseudo-reloc | |
2643 | Do not create pseudo relocations for non-zero offset DATA imports from | |
676ee43b | 2644 | DLLs. |
bb10df36 | 2645 | [This option is specific to the i386 PE targeted port of the linker] |
2fa9fc65 | 2646 | |
b044cda1 CW |
2647 | @kindex --enable-extra-pe-debug |
2648 | @item --enable-extra-pe-debug | |
2649 | Show additional debug info related to auto-import symbol thunking. | |
bb10df36 | 2650 | [This option is specific to the i386 PE targeted port of the linker] |
b044cda1 | 2651 | |
252b5132 RH |
2652 | @kindex --section-alignment |
2653 | @item --section-alignment | |
2654 | Sets the section alignment. Sections in memory will always begin at | |
2655 | addresses which are a multiple of this number. Defaults to 0x1000. | |
bb10df36 | 2656 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 RH |
2657 | |
2658 | @cindex stack size | |
2659 | @kindex --stack | |
2660 | @item --stack @var{reserve} | |
2661 | @itemx --stack @var{reserve},@var{commit} | |
a00b50c5 | 2662 | Specify the number of bytes of memory to reserve (and optionally commit) |
fe6d7d6a | 2663 | to be used as stack for this program. The default is 2MB reserved, 4K |
252b5132 | 2664 | committed. |
bb10df36 | 2665 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 RH |
2666 | |
2667 | @kindex --subsystem | |
2668 | @item --subsystem @var{which} | |
2669 | @itemx --subsystem @var{which}:@var{major} | |
2670 | @itemx --subsystem @var{which}:@var{major}.@var{minor} | |
2671 | Specifies the subsystem under which your program will execute. The | |
2672 | legal values for @var{which} are @code{native}, @code{windows}, | |
33f362e1 NC |
2673 | @code{console}, @code{posix}, and @code{xbox}. You may optionally set |
2674 | the subsystem version also. Numeric values are also accepted for | |
2675 | @var{which}. | |
bb10df36 | 2676 | [This option is specific to the i386 PE targeted port of the linker] |
252b5132 | 2677 | |
2f563b51 DK |
2678 | The following options set flags in the @code{DllCharacteristics} field |
2679 | of the PE file header: | |
2680 | [These options are specific to PE targeted ports of the linker] | |
2681 | ||
2d5c3743 NC |
2682 | @kindex --high-entropy-va |
2683 | @item --high-entropy-va | |
2684 | Image is compatible with 64-bit address space layout randomization | |
2685 | (ASLR). | |
2686 | ||
2f563b51 DK |
2687 | @kindex --dynamicbase |
2688 | @item --dynamicbase | |
2689 | The image base address may be relocated using address space layout | |
2690 | randomization (ASLR). This feature was introduced with MS Windows | |
2691 | Vista for i386 PE targets. | |
2692 | ||
2693 | @kindex --forceinteg | |
2694 | @item --forceinteg | |
2695 | Code integrity checks are enforced. | |
2696 | ||
2697 | @kindex --nxcompat | |
2698 | @item --nxcompat | |
2699 | The image is compatible with the Data Execution Prevention. | |
2700 | This feature was introduced with MS Windows XP SP2 for i386 PE targets. | |
2701 | ||
2702 | @kindex --no-isolation | |
2703 | @item --no-isolation | |
2704 | Although the image understands isolation, do not isolate the image. | |
2705 | ||
2706 | @kindex --no-seh | |
2707 | @item --no-seh | |
2708 | The image does not use SEH. No SE handler may be called from | |
2709 | this image. | |
2710 | ||
2711 | @kindex --no-bind | |
2712 | @item --no-bind | |
2713 | Do not bind this image. | |
2714 | ||
2715 | @kindex --wdmdriver | |
2716 | @item --wdmdriver | |
2717 | The driver uses the MS Windows Driver Model. | |
9d5777a3 | 2718 | |
2f563b51 DK |
2719 | @kindex --tsaware |
2720 | @item --tsaware | |
2721 | The image is Terminal Server aware. | |
2722 | ||
0cb112f7 CF |
2723 | @kindex --insert-timestamp |
2724 | @item --insert-timestamp | |
eeb14e5a LZ |
2725 | @itemx --no-insert-timestamp |
2726 | Insert a real timestamp into the image. This is the default behaviour | |
2727 | as it matches legacy code and it means that the image will work with | |
2728 | other, proprietary tools. The problem with this default is that it | |
2729 | will result in slightly different images being produced each tiem the | |
2730 | same sources are linked. The option @option{--no-insert-timestamp} | |
2731 | can be used to insert a zero value for the timestamp, this ensuring | |
2732 | that binaries produced from indentical sources will compare | |
2733 | identically. | |
252b5132 RH |
2734 | @end table |
2735 | ||
0285c67d NC |
2736 | @c man end |
2737 | ||
ac145307 BS |
2738 | @ifset C6X |
2739 | @subsection Options specific to C6X uClinux targets | |
2740 | ||
2741 | @c man begin OPTIONS | |
2742 | ||
2743 | The C6X uClinux target uses a binary format called DSBT to support shared | |
2744 | libraries. Each shared library in the system needs to have a unique index; | |
2745 | all executables use an index of 0. | |
2746 | ||
2747 | @table @gcctabopt | |
2748 | ||
2749 | @kindex --dsbt-size | |
2750 | @item --dsbt-size @var{size} | |
2751 | This option sets the number of entires in the DSBT of the current executable | |
2752 | or shared library to @var{size}. The default is to create a table with 64 | |
2753 | entries. | |
2754 | ||
2755 | @kindex --dsbt-index | |
2756 | @item --dsbt-index @var{index} | |
2757 | This option sets the DSBT index of the current executable or shared library | |
2758 | to @var{index}. The default is 0, which is appropriate for generating | |
2759 | executables. If a shared library is generated with a DSBT index of 0, the | |
2760 | @code{R_C6000_DSBT_INDEX} relocs are copied into the output file. | |
2761 | ||
fbd9ad90 PB |
2762 | @kindex --no-merge-exidx-entries |
2763 | The @samp{--no-merge-exidx-entries} switch disables the merging of adjacent | |
2764 | exidx entries in frame unwind info. | |
2765 | ||
ac145307 BS |
2766 | @end table |
2767 | ||
2768 | @c man end | |
2769 | @end ifset | |
2770 | ||
93fd0973 SC |
2771 | @ifset M68HC11 |
2772 | @subsection Options specific to Motorola 68HC11 and 68HC12 targets | |
2773 | ||
2774 | @c man begin OPTIONS | |
2775 | ||
2776 | The 68HC11 and 68HC12 linkers support specific options to control the | |
2777 | memory bank switching mapping and trampoline code generation. | |
2778 | ||
2779 | @table @gcctabopt | |
2780 | ||
2781 | @kindex --no-trampoline | |
2782 | @item --no-trampoline | |
2783 | This option disables the generation of trampoline. By default a trampoline | |
2784 | is generated for each far function which is called using a @code{jsr} | |
2785 | instruction (this happens when a pointer to a far function is taken). | |
2786 | ||
2787 | @kindex --bank-window | |
2788 | @item --bank-window @var{name} | |
2789 | This option indicates to the linker the name of the memory region in | |
2790 | the @samp{MEMORY} specification that describes the memory bank window. | |
2791 | The definition of such region is then used by the linker to compute | |
2792 | paging and addresses within the memory window. | |
2793 | ||
2794 | @end table | |
2795 | ||
2796 | @c man end | |
2797 | @end ifset | |
2798 | ||
7fb9f789 NC |
2799 | @ifset M68K |
2800 | @subsection Options specific to Motorola 68K target | |
2801 | ||
2802 | @c man begin OPTIONS | |
2803 | ||
2804 | The following options are supported to control handling of GOT generation | |
2805 | when linking for 68K targets. | |
2806 | ||
2807 | @table @gcctabopt | |
2808 | ||
2809 | @kindex --got | |
2810 | @item --got=@var{type} | |
2811 | This option tells the linker which GOT generation scheme to use. | |
2812 | @var{type} should be one of @samp{single}, @samp{negative}, | |
2813 | @samp{multigot} or @samp{target}. For more information refer to the | |
2814 | Info entry for @file{ld}. | |
2815 | ||
2816 | @end table | |
2817 | ||
2818 | @c man end | |
2819 | @end ifset | |
2820 | ||
833794fc MR |
2821 | @ifset MIPS |
2822 | @subsection Options specific to MIPS targets | |
2823 | ||
2824 | @c man begin OPTIONS | |
2825 | ||
2826 | The following options are supported to control microMIPS instruction | |
2827 | generation when linking for MIPS targets. | |
2828 | ||
2829 | @table @gcctabopt | |
2830 | ||
2831 | @kindex --insn32 | |
2832 | @item --insn32 | |
2833 | @kindex --no-insn32 | |
2834 | @itemx --no-insn32 | |
2835 | These options control the choice of microMIPS instructions used in code | |
2836 | generated by the linker, such as that in the PLT or lazy binding stubs, | |
2837 | or in relaxation. If @samp{--insn32} is used, then the linker only uses | |
2838 | 32-bit instruction encodings. By default or if @samp{--no-insn32} is | |
2839 | used, all instruction encodings are used, including 16-bit ones where | |
2840 | possible. | |
2841 | ||
2842 | @end table | |
2843 | ||
2844 | @c man end | |
2845 | @end ifset | |
2846 | ||
252b5132 RH |
2847 | @ifset UsesEnvVars |
2848 | @node Environment | |
2849 | @section Environment Variables | |
2850 | ||
0285c67d NC |
2851 | @c man begin ENVIRONMENT |
2852 | ||
560e09e9 | 2853 | You can change the behaviour of @command{ld} with the environment variables |
36f63dca NC |
2854 | @ifclear SingleFormat |
2855 | @code{GNUTARGET}, | |
2856 | @end ifclear | |
2857 | @code{LDEMULATION} and @code{COLLECT_NO_DEMANGLE}. | |
252b5132 | 2858 | |
36f63dca | 2859 | @ifclear SingleFormat |
252b5132 RH |
2860 | @kindex GNUTARGET |
2861 | @cindex default input format | |
2862 | @code{GNUTARGET} determines the input-file object format if you don't | |
2863 | use @samp{-b} (or its synonym @samp{--format}). Its value should be one | |
2864 | of the BFD names for an input format (@pxref{BFD}). If there is no | |
ff5dcc92 | 2865 | @code{GNUTARGET} in the environment, @command{ld} uses the natural format |
252b5132 RH |
2866 | of the target. If @code{GNUTARGET} is set to @code{default} then BFD |
2867 | attempts to discover the input format by examining binary input files; | |
2868 | this method often succeeds, but there are potential ambiguities, since | |
2869 | there is no method of ensuring that the magic number used to specify | |
2870 | object-file formats is unique. However, the configuration procedure for | |
2871 | BFD on each system places the conventional format for that system first | |
2872 | in the search-list, so ambiguities are resolved in favor of convention. | |
36f63dca | 2873 | @end ifclear |
252b5132 RH |
2874 | |
2875 | @kindex LDEMULATION | |
2876 | @cindex default emulation | |
2877 | @cindex emulation, default | |
2878 | @code{LDEMULATION} determines the default emulation if you don't use the | |
2879 | @samp{-m} option. The emulation can affect various aspects of linker | |
2880 | behaviour, particularly the default linker script. You can list the | |
2881 | available emulations with the @samp{--verbose} or @samp{-V} options. If | |
2882 | the @samp{-m} option is not used, and the @code{LDEMULATION} environment | |
2883 | variable is not defined, the default emulation depends upon how the | |
2884 | linker was configured. | |
252b5132 RH |
2885 | |
2886 | @kindex COLLECT_NO_DEMANGLE | |
2887 | @cindex demangling, default | |
2888 | Normally, the linker will default to demangling symbols. However, if | |
2889 | @code{COLLECT_NO_DEMANGLE} is set in the environment, then it will | |
2890 | default to not demangling symbols. This environment variable is used in | |
2891 | a similar fashion by the @code{gcc} linker wrapper program. The default | |
2892 | may be overridden by the @samp{--demangle} and @samp{--no-demangle} | |
2893 | options. | |
2894 | ||
0285c67d NC |
2895 | @c man end |
2896 | @end ifset | |
2897 | ||
252b5132 RH |
2898 | @node Scripts |
2899 | @chapter Linker Scripts | |
2900 | ||
2901 | @cindex scripts | |
2902 | @cindex linker scripts | |
2903 | @cindex command files | |
2904 | Every link is controlled by a @dfn{linker script}. This script is | |
2905 | written in the linker command language. | |
2906 | ||
2907 | The main purpose of the linker script is to describe how the sections in | |
2908 | the input files should be mapped into the output file, and to control | |
2909 | the memory layout of the output file. Most linker scripts do nothing | |
2910 | more than this. However, when necessary, the linker script can also | |
2911 | direct the linker to perform many other operations, using the commands | |
2912 | described below. | |
2913 | ||
2914 | The linker always uses a linker script. If you do not supply one | |
2915 | yourself, the linker will use a default script that is compiled into the | |
2916 | linker executable. You can use the @samp{--verbose} command line option | |
2917 | to display the default linker script. Certain command line options, | |
2918 | such as @samp{-r} or @samp{-N}, will affect the default linker script. | |
2919 | ||
2920 | You may supply your own linker script by using the @samp{-T} command | |
2921 | line option. When you do this, your linker script will replace the | |
2922 | default linker script. | |
2923 | ||
2924 | You may also use linker scripts implicitly by naming them as input files | |
2925 | to the linker, as though they were files to be linked. @xref{Implicit | |
2926 | Linker Scripts}. | |
2927 | ||
2928 | @menu | |
2929 | * Basic Script Concepts:: Basic Linker Script Concepts | |
2930 | * Script Format:: Linker Script Format | |
2931 | * Simple Example:: Simple Linker Script Example | |
2932 | * Simple Commands:: Simple Linker Script Commands | |
2933 | * Assignments:: Assigning Values to Symbols | |
2934 | * SECTIONS:: SECTIONS Command | |
2935 | * MEMORY:: MEMORY Command | |
2936 | * PHDRS:: PHDRS Command | |
2937 | * VERSION:: VERSION Command | |
2938 | * Expressions:: Expressions in Linker Scripts | |
2939 | * Implicit Linker Scripts:: Implicit Linker Scripts | |
2940 | @end menu | |
2941 | ||
2942 | @node Basic Script Concepts | |
2943 | @section Basic Linker Script Concepts | |
2944 | @cindex linker script concepts | |
2945 | We need to define some basic concepts and vocabulary in order to | |
2946 | describe the linker script language. | |
2947 | ||
2948 | The linker combines input files into a single output file. The output | |
2949 | file and each input file are in a special data format known as an | |
2950 | @dfn{object file format}. Each file is called an @dfn{object file}. | |
2951 | The output file is often called an @dfn{executable}, but for our | |
2952 | purposes we will also call it an object file. Each object file has, | |
2953 | among other things, a list of @dfn{sections}. We sometimes refer to a | |
2954 | section in an input file as an @dfn{input section}; similarly, a section | |
2955 | in the output file is an @dfn{output section}. | |
2956 | ||
2957 | Each section in an object file has a name and a size. Most sections | |
2958 | also have an associated block of data, known as the @dfn{section | |
56dd11f0 | 2959 | contents}. A section may be marked as @dfn{loadable}, which means that |
252b5132 RH |
2960 | the contents should be loaded into memory when the output file is run. |
2961 | A section with no contents may be @dfn{allocatable}, which means that an | |
2962 | area in memory should be set aside, but nothing in particular should be | |
2963 | loaded there (in some cases this memory must be zeroed out). A section | |
2964 | which is neither loadable nor allocatable typically contains some sort | |
2965 | of debugging information. | |
2966 | ||
2967 | Every loadable or allocatable output section has two addresses. The | |
2968 | first is the @dfn{VMA}, or virtual memory address. This is the address | |
2969 | the section will have when the output file is run. The second is the | |
2970 | @dfn{LMA}, or load memory address. This is the address at which the | |
2971 | section will be loaded. In most cases the two addresses will be the | |
2972 | same. An example of when they might be different is when a data section | |
2973 | is loaded into ROM, and then copied into RAM when the program starts up | |
2974 | (this technique is often used to initialize global variables in a ROM | |
2975 | based system). In this case the ROM address would be the LMA, and the | |
2976 | RAM address would be the VMA. | |
2977 | ||
2978 | You can see the sections in an object file by using the @code{objdump} | |
2979 | program with the @samp{-h} option. | |
2980 | ||
2981 | Every object file also has a list of @dfn{symbols}, known as the | |
2982 | @dfn{symbol table}. A symbol may be defined or undefined. Each symbol | |
2983 | has a name, and each defined symbol has an address, among other | |
2984 | information. If you compile a C or C++ program into an object file, you | |
2985 | will get a defined symbol for every defined function and global or | |
2986 | static variable. Every undefined function or global variable which is | |
2987 | referenced in the input file will become an undefined symbol. | |
2988 | ||
2989 | You can see the symbols in an object file by using the @code{nm} | |
2990 | program, or by using the @code{objdump} program with the @samp{-t} | |
2991 | option. | |
2992 | ||
2993 | @node Script Format | |
2994 | @section Linker Script Format | |
2995 | @cindex linker script format | |
2996 | Linker scripts are text files. | |
2997 | ||
2998 | You write a linker script as a series of commands. Each command is | |
2999 | either a keyword, possibly followed by arguments, or an assignment to a | |
3000 | symbol. You may separate commands using semicolons. Whitespace is | |
3001 | generally ignored. | |
3002 | ||
3003 | Strings such as file or format names can normally be entered directly. | |
3004 | If the file name contains a character such as a comma which would | |
3005 | otherwise serve to separate file names, you may put the file name in | |
3006 | double quotes. There is no way to use a double quote character in a | |
3007 | file name. | |
3008 | ||
3009 | You may include comments in linker scripts just as in C, delimited by | |
3010 | @samp{/*} and @samp{*/}. As in C, comments are syntactically equivalent | |
3011 | to whitespace. | |
3012 | ||
3013 | @node Simple Example | |
3014 | @section Simple Linker Script Example | |
3015 | @cindex linker script example | |
3016 | @cindex example of linker script | |
3017 | Many linker scripts are fairly simple. | |
3018 | ||
3019 | The simplest possible linker script has just one command: | |
3020 | @samp{SECTIONS}. You use the @samp{SECTIONS} command to describe the | |
3021 | memory layout of the output file. | |
3022 | ||
3023 | The @samp{SECTIONS} command is a powerful command. Here we will | |
3024 | describe a simple use of it. Let's assume your program consists only of | |
3025 | code, initialized data, and uninitialized data. These will be in the | |
3026 | @samp{.text}, @samp{.data}, and @samp{.bss} sections, respectively. | |
3027 | Let's assume further that these are the only sections which appear in | |
3028 | your input files. | |
3029 | ||
3030 | For this example, let's say that the code should be loaded at address | |
3031 | 0x10000, and that the data should start at address 0x8000000. Here is a | |
3032 | linker script which will do that: | |
3033 | @smallexample | |
3034 | SECTIONS | |
3035 | @{ | |
3036 | . = 0x10000; | |
3037 | .text : @{ *(.text) @} | |
3038 | . = 0x8000000; | |
3039 | .data : @{ *(.data) @} | |
3040 | .bss : @{ *(.bss) @} | |
3041 | @} | |
3042 | @end smallexample | |
3043 | ||
3044 | You write the @samp{SECTIONS} command as the keyword @samp{SECTIONS}, | |
3045 | followed by a series of symbol assignments and output section | |
3046 | descriptions enclosed in curly braces. | |
3047 | ||
252b5132 RH |
3048 | The first line inside the @samp{SECTIONS} command of the above example |
3049 | sets the value of the special symbol @samp{.}, which is the location | |
3050 | counter. If you do not specify the address of an output section in some | |
3051 | other way (other ways are described later), the address is set from the | |
3052 | current value of the location counter. The location counter is then | |
3053 | incremented by the size of the output section. At the start of the | |
3054 | @samp{SECTIONS} command, the location counter has the value @samp{0}. | |
3055 | ||
3056 | The second line defines an output section, @samp{.text}. The colon is | |
3057 | required syntax which may be ignored for now. Within the curly braces | |
3058 | after the output section name, you list the names of the input sections | |
3059 | which should be placed into this output section. The @samp{*} is a | |
3060 | wildcard which matches any file name. The expression @samp{*(.text)} | |
3061 | means all @samp{.text} input sections in all input files. | |
3062 | ||
3063 | Since the location counter is @samp{0x10000} when the output section | |
3064 | @samp{.text} is defined, the linker will set the address of the | |
3065 | @samp{.text} section in the output file to be @samp{0x10000}. | |
3066 | ||
3067 | The remaining lines define the @samp{.data} and @samp{.bss} sections in | |
3068 | the output file. The linker will place the @samp{.data} output section | |
3069 | at address @samp{0x8000000}. After the linker places the @samp{.data} | |
3070 | output section, the value of the location counter will be | |
3071 | @samp{0x8000000} plus the size of the @samp{.data} output section. The | |
3072 | effect is that the linker will place the @samp{.bss} output section | |
58434bc1 | 3073 | immediately after the @samp{.data} output section in memory. |
252b5132 RH |
3074 | |
3075 | The linker will ensure that each output section has the required | |
3076 | alignment, by increasing the location counter if necessary. In this | |
3077 | example, the specified addresses for the @samp{.text} and @samp{.data} | |
3078 | sections will probably satisfy any alignment constraints, but the linker | |
3079 | may have to create a small gap between the @samp{.data} and @samp{.bss} | |
3080 | sections. | |
3081 | ||
3082 | That's it! That's a simple and complete linker script. | |
3083 | ||
3084 | @node Simple Commands | |
3085 | @section Simple Linker Script Commands | |
3086 | @cindex linker script simple commands | |
3087 | In this section we describe the simple linker script commands. | |
3088 | ||
3089 | @menu | |
3090 | * Entry Point:: Setting the entry point | |
3091 | * File Commands:: Commands dealing with files | |
3092 | @ifclear SingleFormat | |
3093 | * Format Commands:: Commands dealing with object file formats | |
3094 | @end ifclear | |
3095 | ||
4a93e180 | 3096 | * REGION_ALIAS:: Assign alias names to memory regions |
252b5132 RH |
3097 | * Miscellaneous Commands:: Other linker script commands |
3098 | @end menu | |
3099 | ||
3100 | @node Entry Point | |
36f63dca | 3101 | @subsection Setting the Entry Point |
252b5132 RH |
3102 | @kindex ENTRY(@var{symbol}) |
3103 | @cindex start of execution | |
3104 | @cindex first instruction | |
3105 | @cindex entry point | |
3106 | The first instruction to execute in a program is called the @dfn{entry | |
3107 | point}. You can use the @code{ENTRY} linker script command to set the | |
3108 | entry point. The argument is a symbol name: | |
3109 | @smallexample | |
3110 | ENTRY(@var{symbol}) | |
3111 | @end smallexample | |
3112 | ||
3113 | There are several ways to set the entry point. The linker will set the | |
3114 | entry point by trying each of the following methods in order, and | |
3115 | stopping when one of them succeeds: | |
3116 | @itemize @bullet | |
a1ab1d2a | 3117 | @item |
252b5132 | 3118 | the @samp{-e} @var{entry} command-line option; |
a1ab1d2a | 3119 | @item |
252b5132 | 3120 | the @code{ENTRY(@var{symbol})} command in a linker script; |
a1ab1d2a | 3121 | @item |
3ab904c4 NC |
3122 | the value of a target specific symbol, if it is defined; For many |
3123 | targets this is @code{start}, but PE and BeOS based systems for example | |
3124 | check a list of possible entry symbols, matching the first one found. | |
a1ab1d2a | 3125 | @item |
252b5132 | 3126 | the address of the first byte of the @samp{.text} section, if present; |
a1ab1d2a | 3127 | @item |
252b5132 RH |
3128 | The address @code{0}. |
3129 | @end itemize | |
3130 | ||
3131 | @node File Commands | |
36f63dca | 3132 | @subsection Commands Dealing with Files |
252b5132 RH |
3133 | @cindex linker script file commands |
3134 | Several linker script commands deal with files. | |
3135 | ||
3136 | @table @code | |
3137 | @item INCLUDE @var{filename} | |
3138 | @kindex INCLUDE @var{filename} | |
3139 | @cindex including a linker script | |
3140 | Include the linker script @var{filename} at this point. The file will | |
3141 | be searched for in the current directory, and in any directory specified | |
ff5dcc92 | 3142 | with the @option{-L} option. You can nest calls to @code{INCLUDE} up to |
252b5132 RH |
3143 | 10 levels deep. |
3144 | ||
4006703d NS |
3145 | You can place @code{INCLUDE} directives at the top level, in @code{MEMORY} or |
3146 | @code{SECTIONS} commands, or in output section descriptions. | |
3147 | ||
252b5132 RH |
3148 | @item INPUT(@var{file}, @var{file}, @dots{}) |
3149 | @itemx INPUT(@var{file} @var{file} @dots{}) | |
3150 | @kindex INPUT(@var{files}) | |
3151 | @cindex input files in linker scripts | |
3152 | @cindex input object files in linker scripts | |
3153 | @cindex linker script input object files | |
3154 | The @code{INPUT} command directs the linker to include the named files | |
3155 | in the link, as though they were named on the command line. | |
3156 | ||
3157 | For example, if you always want to include @file{subr.o} any time you do | |
3158 | a link, but you can't be bothered to put it on every link command line, | |
3159 | then you can put @samp{INPUT (subr.o)} in your linker script. | |
3160 | ||
3161 | In fact, if you like, you can list all of your input files in the linker | |
3162 | script, and then invoke the linker with nothing but a @samp{-T} option. | |
3163 | ||
e3f2db7f AO |
3164 | In case a @dfn{sysroot prefix} is configured, and the filename starts |
3165 | with the @samp{/} character, and the script being processed was | |
3166 | located inside the @dfn{sysroot prefix}, the filename will be looked | |
3167 | for in the @dfn{sysroot prefix}. Otherwise, the linker will try to | |
3168 | open the file in the current directory. If it is not found, the | |
cad60a33 HPN |
3169 | linker will search through the archive library search path. |
3170 | The @dfn{sysroot prefix} can also be forced by specifying @code{=} | |
3171 | as the first character in the filename path. See also the | |
e3f2db7f | 3172 | description of @samp{-L} in @ref{Options,,Command Line Options}. |
252b5132 | 3173 | |
ff5dcc92 | 3174 | If you use @samp{INPUT (-l@var{file})}, @command{ld} will transform the |
252b5132 RH |
3175 | name to @code{lib@var{file}.a}, as with the command line argument |
3176 | @samp{-l}. | |
3177 | ||
3178 | When you use the @code{INPUT} command in an implicit linker script, the | |
3179 | files will be included in the link at the point at which the linker | |
3180 | script file is included. This can affect archive searching. | |
3181 | ||
3182 | @item GROUP(@var{file}, @var{file}, @dots{}) | |
3183 | @itemx GROUP(@var{file} @var{file} @dots{}) | |
3184 | @kindex GROUP(@var{files}) | |
3185 | @cindex grouping input files | |
3186 | The @code{GROUP} command is like @code{INPUT}, except that the named | |
3187 | files should all be archives, and they are searched repeatedly until no | |
3188 | new undefined references are created. See the description of @samp{-(} | |
3189 | in @ref{Options,,Command Line Options}. | |
3190 | ||
b717d30e JJ |
3191 | @item AS_NEEDED(@var{file}, @var{file}, @dots{}) |
3192 | @itemx AS_NEEDED(@var{file} @var{file} @dots{}) | |
3193 | @kindex AS_NEEDED(@var{files}) | |
3194 | This construct can appear only inside of the @code{INPUT} or @code{GROUP} | |
3195 | commands, among other filenames. The files listed will be handled | |
3196 | as if they appear directly in the @code{INPUT} or @code{GROUP} commands, | |
3197 | with the exception of ELF shared libraries, that will be added only | |
3198 | when they are actually needed. This construct essentially enables | |
3199 | @option{--as-needed} option for all the files listed inside of it | |
3200 | and restores previous @option{--as-needed} resp. @option{--no-as-needed} | |
3201 | setting afterwards. | |
3202 | ||
252b5132 RH |
3203 | @item OUTPUT(@var{filename}) |
3204 | @kindex OUTPUT(@var{filename}) | |
b45619c0 | 3205 | @cindex output file name in linker script |
252b5132 RH |
3206 | The @code{OUTPUT} command names the output file. Using |
3207 | @code{OUTPUT(@var{filename})} in the linker script is exactly like using | |
3208 | @samp{-o @var{filename}} on the command line (@pxref{Options,,Command | |
3209 | Line Options}). If both are used, the command line option takes | |
3210 | precedence. | |
3211 | ||
3212 | You can use the @code{OUTPUT} command to define a default name for the | |
3213 | output file other than the usual default of @file{a.out}. | |
3214 | ||
3215 | @item SEARCH_DIR(@var{path}) | |
3216 | @kindex SEARCH_DIR(@var{path}) | |
3217 | @cindex library search path in linker script | |
3218 | @cindex archive search path in linker script | |
3219 | @cindex search path in linker script | |
3220 | The @code{SEARCH_DIR} command adds @var{path} to the list of paths where | |
ff5dcc92 | 3221 | @command{ld} looks for archive libraries. Using |
252b5132 RH |
3222 | @code{SEARCH_DIR(@var{path})} is exactly like using @samp{-L @var{path}} |
3223 | on the command line (@pxref{Options,,Command Line Options}). If both | |
3224 | are used, then the linker will search both paths. Paths specified using | |
3225 | the command line option are searched first. | |
3226 | ||
3227 | @item STARTUP(@var{filename}) | |
3228 | @kindex STARTUP(@var{filename}) | |
3229 | @cindex first input file | |
3230 | The @code{STARTUP} command is just like the @code{INPUT} command, except | |
3231 | that @var{filename} will become the first input file to be linked, as | |
3232 | though it were specified first on the command line. This may be useful | |
3233 | when using a system in which the entry point is always the start of the | |
3234 | first file. | |
3235 | @end table | |
3236 | ||
3237 | @ifclear SingleFormat | |
3238 | @node Format Commands | |
36f63dca | 3239 | @subsection Commands Dealing with Object File Formats |
252b5132 RH |
3240 | A couple of linker script commands deal with object file formats. |
3241 | ||
3242 | @table @code | |
3243 | @item OUTPUT_FORMAT(@var{bfdname}) | |
3244 | @itemx OUTPUT_FORMAT(@var{default}, @var{big}, @var{little}) | |
3245 | @kindex OUTPUT_FORMAT(@var{bfdname}) | |
3246 | @cindex output file format in linker script | |
3247 | The @code{OUTPUT_FORMAT} command names the BFD format to use for the | |
3248 | output file (@pxref{BFD}). Using @code{OUTPUT_FORMAT(@var{bfdname})} is | |
024531e2 | 3249 | exactly like using @samp{--oformat @var{bfdname}} on the command line |
252b5132 RH |
3250 | (@pxref{Options,,Command Line Options}). If both are used, the command |
3251 | line option takes precedence. | |
3252 | ||
3253 | You can use @code{OUTPUT_FORMAT} with three arguments to use different | |
3254 | formats based on the @samp{-EB} and @samp{-EL} command line options. | |
3255 | This permits the linker script to set the output format based on the | |
3256 | desired endianness. | |
3257 | ||
3258 | If neither @samp{-EB} nor @samp{-EL} are used, then the output format | |
3259 | will be the first argument, @var{default}. If @samp{-EB} is used, the | |
3260 | output format will be the second argument, @var{big}. If @samp{-EL} is | |
3261 | used, the output format will be the third argument, @var{little}. | |
3262 | ||
3263 | For example, the default linker script for the MIPS ELF target uses this | |
3264 | command: | |
3265 | @smallexample | |
3266 | OUTPUT_FORMAT(elf32-bigmips, elf32-bigmips, elf32-littlemips) | |
3267 | @end smallexample | |
3268 | This says that the default format for the output file is | |
3269 | @samp{elf32-bigmips}, but if the user uses the @samp{-EL} command line | |
3270 | option, the output file will be created in the @samp{elf32-littlemips} | |
3271 | format. | |
3272 | ||
3273 | @item TARGET(@var{bfdname}) | |
3274 | @kindex TARGET(@var{bfdname}) | |
3275 | @cindex input file format in linker script | |
3276 | The @code{TARGET} command names the BFD format to use when reading input | |
3277 | files. It affects subsequent @code{INPUT} and @code{GROUP} commands. | |
3278 | This command is like using @samp{-b @var{bfdname}} on the command line | |
3279 | (@pxref{Options,,Command Line Options}). If the @code{TARGET} command | |
3280 | is used but @code{OUTPUT_FORMAT} is not, then the last @code{TARGET} | |
3281 | command is also used to set the format for the output file. @xref{BFD}. | |
3282 | @end table | |
3283 | @end ifclear | |
3284 | ||
4a93e180 NC |
3285 | @node REGION_ALIAS |
3286 | @subsection Assign alias names to memory regions | |
3287 | @kindex REGION_ALIAS(@var{alias}, @var{region}) | |
3288 | @cindex region alias | |
3289 | @cindex region names | |
3290 | ||
3291 | Alias names can be added to existing memory regions created with the | |
3292 | @ref{MEMORY} command. Each name corresponds to at most one memory region. | |
3293 | ||
3294 | @smallexample | |
3295 | REGION_ALIAS(@var{alias}, @var{region}) | |
3296 | @end smallexample | |
3297 | ||
3298 | The @code{REGION_ALIAS} function creates an alias name @var{alias} for the | |
3299 | memory region @var{region}. This allows a flexible mapping of output sections | |
3300 | to memory regions. An example follows. | |
3301 | ||
3302 | Suppose we have an application for embedded systems which come with various | |
3303 | memory storage devices. All have a general purpose, volatile memory @code{RAM} | |
3304 | that allows code execution or data storage. Some may have a read-only, | |
3305 | non-volatile memory @code{ROM} that allows code execution and read-only data | |
3306 | access. The last variant is a read-only, non-volatile memory @code{ROM2} with | |
3307 | read-only data access and no code execution capability. We have four output | |
3308 | sections: | |
3309 | ||
3310 | @itemize @bullet | |
3311 | @item | |
3312 | @code{.text} program code; | |
3313 | @item | |
3314 | @code{.rodata} read-only data; | |
3315 | @item | |
3316 | @code{.data} read-write initialized data; | |
3317 | @item | |
3318 | @code{.bss} read-write zero initialized data. | |
3319 | @end itemize | |
3320 | ||
3321 | The goal is to provide a linker command file that contains a system independent | |
3322 | part defining the output sections and a system dependent part mapping the | |
3323 | output sections to the memory regions available on the system. Our embedded | |
3324 | systems come with three different memory setups @code{A}, @code{B} and | |
3325 | @code{C}: | |
3326 | @multitable @columnfractions .25 .25 .25 .25 | |
3327 | @item Section @tab Variant A @tab Variant B @tab Variant C | |
9d5777a3 | 3328 | @item .text @tab RAM @tab ROM @tab ROM |
4a93e180 NC |
3329 | @item .rodata @tab RAM @tab ROM @tab ROM2 |
3330 | @item .data @tab RAM @tab RAM/ROM @tab RAM/ROM2 | |
3331 | @item .bss @tab RAM @tab RAM @tab RAM | |
3332 | @end multitable | |
3333 | The notation @code{RAM/ROM} or @code{RAM/ROM2} means that this section is | |
3334 | loaded into region @code{ROM} or @code{ROM2} respectively. Please note that | |
3335 | the load address of the @code{.data} section starts in all three variants at | |
3336 | the end of the @code{.rodata} section. | |
3337 | ||
3338 | The base linker script that deals with the output sections follows. It | |
3339 | includes the system dependent @code{linkcmds.memory} file that describes the | |
3340 | memory layout: | |
3341 | @smallexample | |
3342 | INCLUDE linkcmds.memory | |
3343 | ||
3344 | SECTIONS | |
3345 | @{ | |
3346 | .text : | |
3347 | @{ | |
3348 | *(.text) | |
3349 | @} > REGION_TEXT | |
3350 | .rodata : | |
3351 | @{ | |
3352 | *(.rodata) | |
3353 | rodata_end = .; | |
3354 | @} > REGION_RODATA | |
3355 | .data : AT (rodata_end) | |
3356 | @{ | |
3357 | data_start = .; | |
3358 | *(.data) | |
3359 | @} > REGION_DATA | |
3360 | data_size = SIZEOF(.data); | |
3361 | data_load_start = LOADADDR(.data); | |
3362 | .bss : | |
3363 | @{ | |
3364 | *(.bss) | |
3365 | @} > REGION_BSS | |
3366 | @} | |
3367 | @end smallexample | |
3368 | ||
3369 | Now we need three different @code{linkcmds.memory} files to define memory | |
3370 | regions and alias names. The content of @code{linkcmds.memory} for the three | |
3371 | variants @code{A}, @code{B} and @code{C}: | |
3372 | @table @code | |
3373 | @item A | |
3374 | Here everything goes into the @code{RAM}. | |
3375 | @smallexample | |
3376 | MEMORY | |
3377 | @{ | |
3378 | RAM : ORIGIN = 0, LENGTH = 4M | |
3379 | @} | |
3380 | ||
3381 | REGION_ALIAS("REGION_TEXT", RAM); | |
3382 | REGION_ALIAS("REGION_RODATA", RAM); | |
3383 | REGION_ALIAS("REGION_DATA", RAM); | |
3384 | REGION_ALIAS("REGION_BSS", RAM); | |
3385 | @end smallexample | |
3386 | @item B | |
3387 | Program code and read-only data go into the @code{ROM}. Read-write data goes | |
3388 | into the @code{RAM}. An image of the initialized data is loaded into the | |
3389 | @code{ROM} and will be copied during system start into the @code{RAM}. | |
3390 | @smallexample | |
3391 | MEMORY | |
3392 | @{ | |
3393 | ROM : ORIGIN = 0, LENGTH = 3M | |
3394 | RAM : ORIGIN = 0x10000000, LENGTH = 1M | |
3395 | @} | |
3396 | ||
3397 | REGION_ALIAS("REGION_TEXT", ROM); | |
3398 | REGION_ALIAS("REGION_RODATA", ROM); | |
3399 | REGION_ALIAS("REGION_DATA", RAM); | |
3400 | REGION_ALIAS("REGION_BSS", RAM); | |
3401 | @end smallexample | |
3402 | @item C | |
3403 | Program code goes into the @code{ROM}. Read-only data goes into the | |
3404 | @code{ROM2}. Read-write data goes into the @code{RAM}. An image of the | |
3405 | initialized data is loaded into the @code{ROM2} and will be copied during | |
3406 | system start into the @code{RAM}. | |
3407 | @smallexample | |
3408 | MEMORY | |
3409 | @{ | |
3410 | ROM : ORIGIN = 0, LENGTH = 2M | |
3411 | ROM2 : ORIGIN = 0x10000000, LENGTH = 1M | |
3412 | RAM : ORIGIN = 0x20000000, LENGTH = 1M | |
3413 | @} | |
3414 | ||
3415 | REGION_ALIAS("REGION_TEXT", ROM); | |
3416 | REGION_ALIAS("REGION_RODATA", ROM2); | |
3417 | REGION_ALIAS("REGION_DATA", RAM); | |
3418 | REGION_ALIAS("REGION_BSS", RAM); | |
3419 | @end smallexample | |
3420 | @end table | |
3421 | ||
3422 | It is possible to write a common system initialization routine to copy the | |
3423 | @code{.data} section from @code{ROM} or @code{ROM2} into the @code{RAM} if | |
3424 | necessary: | |
3425 | @smallexample | |
3426 | #include <string.h> | |
3427 | ||
3428 | extern char data_start []; | |
3429 | extern char data_size []; | |
3430 | extern char data_load_start []; | |
3431 | ||
3432 | void copy_data(void) | |
3433 | @{ | |
3434 | if (data_start != data_load_start) | |
3435 | @{ | |
3436 | memcpy(data_start, data_load_start, (size_t) data_size); | |
3437 | @} | |
3438 | @} | |
3439 | @end smallexample | |
3440 | ||
252b5132 | 3441 | @node Miscellaneous Commands |
36f63dca | 3442 | @subsection Other Linker Script Commands |
252b5132 RH |
3443 | There are a few other linker scripts commands. |
3444 | ||
3445 | @table @code | |
3446 | @item ASSERT(@var{exp}, @var{message}) | |
3447 | @kindex ASSERT | |
3448 | @cindex assertion in linker script | |
3449 | Ensure that @var{exp} is non-zero. If it is zero, then exit the linker | |
3450 | with an error code, and print @var{message}. | |
3451 | ||
3452 | @item EXTERN(@var{symbol} @var{symbol} @dots{}) | |
3453 | @kindex EXTERN | |
3454 | @cindex undefined symbol in linker script | |
3455 | Force @var{symbol} to be entered in the output file as an undefined | |
3456 | symbol. Doing this may, for example, trigger linking of additional | |
3457 | modules from standard libraries. You may list several @var{symbol}s for | |
3458 | each @code{EXTERN}, and you may use @code{EXTERN} multiple times. This | |
3459 | command has the same effect as the @samp{-u} command-line option. | |
3460 | ||
3461 | @item FORCE_COMMON_ALLOCATION | |
3462 | @kindex FORCE_COMMON_ALLOCATION | |
3463 | @cindex common allocation in linker script | |
3464 | This command has the same effect as the @samp{-d} command-line option: | |
ff5dcc92 | 3465 | to make @command{ld} assign space to common symbols even if a relocatable |
252b5132 RH |
3466 | output file is specified (@samp{-r}). |
3467 | ||
4818e05f AM |
3468 | @item INHIBIT_COMMON_ALLOCATION |
3469 | @kindex INHIBIT_COMMON_ALLOCATION | |
3470 | @cindex common allocation in linker script | |
3471 | This command has the same effect as the @samp{--no-define-common} | |
3472 | command-line option: to make @code{ld} omit the assignment of addresses | |
3473 | to common symbols even for a non-relocatable output file. | |
3474 | ||
53d25da6 AM |
3475 | @item INSERT [ AFTER | BEFORE ] @var{output_section} |
3476 | @kindex INSERT | |
3477 | @cindex insert user script into default script | |
3478 | This command is typically used in a script specified by @samp{-T} to | |
3479 | augment the default @code{SECTIONS} with, for example, overlays. It | |
3480 | inserts all prior linker script statements after (or before) | |
3481 | @var{output_section}, and also causes @samp{-T} to not override the | |
3482 | default linker script. The exact insertion point is as for orphan | |
3483 | sections. @xref{Location Counter}. The insertion happens after the | |
3484 | linker has mapped input sections to output sections. Prior to the | |
3485 | insertion, since @samp{-T} scripts are parsed before the default | |
3486 | linker script, statements in the @samp{-T} script occur before the | |
3487 | default linker script statements in the internal linker representation | |
3488 | of the script. In particular, input section assignments will be made | |
3489 | to @samp{-T} output sections before those in the default script. Here | |
3490 | is an example of how a @samp{-T} script using @code{INSERT} might look: | |
3491 | ||
3492 | @smallexample | |
3493 | SECTIONS | |
3494 | @{ | |
3495 | OVERLAY : | |
3496 | @{ | |
3497 | .ov1 @{ ov1*(.text) @} | |
3498 | .ov2 @{ ov2*(.text) @} | |
3499 | @} | |
3500 | @} | |
3501 | INSERT AFTER .text; | |
3502 | @end smallexample | |
3503 | ||
252b5132 RH |
3504 | @item NOCROSSREFS(@var{section} @var{section} @dots{}) |
3505 | @kindex NOCROSSREFS(@var{sections}) | |
3506 | @cindex cross references | |
ff5dcc92 | 3507 | This command may be used to tell @command{ld} to issue an error about any |
252b5132 RH |
3508 | references among certain output sections. |
3509 | ||
3510 | In certain types of programs, particularly on embedded systems when | |
3511 | using overlays, when one section is loaded into memory, another section | |
3512 | will not be. Any direct references between the two sections would be | |
3513 | errors. For example, it would be an error if code in one section called | |
3514 | a function defined in the other section. | |
3515 | ||
3516 | The @code{NOCROSSREFS} command takes a list of output section names. If | |
ff5dcc92 | 3517 | @command{ld} detects any cross references between the sections, it reports |
252b5132 RH |
3518 | an error and returns a non-zero exit status. Note that the |
3519 | @code{NOCROSSREFS} command uses output section names, not input section | |
3520 | names. | |
3521 | ||
3522 | @ifclear SingleFormat | |
3523 | @item OUTPUT_ARCH(@var{bfdarch}) | |
3524 | @kindex OUTPUT_ARCH(@var{bfdarch}) | |
3525 | @cindex machine architecture | |
3526 | @cindex architecture | |
3527 | Specify a particular output machine architecture. The argument is one | |
3528 | of the names used by the BFD library (@pxref{BFD}). You can see the | |
3529 | architecture of an object file by using the @code{objdump} program with | |
3530 | the @samp{-f} option. | |
3531 | @end ifclear | |
01554a74 AM |
3532 | |
3533 | @item LD_FEATURE(@var{string}) | |
3534 | @kindex LD_FEATURE(@var{string}) | |
3535 | This command may be used to modify @command{ld} behavior. If | |
3536 | @var{string} is @code{"SANE_EXPR"} then absolute symbols and numbers | |
3537 | in a script are simply treated as numbers everywhere. | |
3538 | @xref{Expression Section}. | |
252b5132 RH |
3539 | @end table |
3540 | ||
3541 | @node Assignments | |
3542 | @section Assigning Values to Symbols | |
3543 | @cindex assignment in scripts | |
3544 | @cindex symbol definition, scripts | |
3545 | @cindex variables, defining | |
3546 | You may assign a value to a symbol in a linker script. This will define | |
73ae6183 | 3547 | the symbol and place it into the symbol table with a global scope. |
252b5132 RH |
3548 | |
3549 | @menu | |
3550 | * Simple Assignments:: Simple Assignments | |
eb8476a6 | 3551 | * HIDDEN:: HIDDEN |
252b5132 | 3552 | * PROVIDE:: PROVIDE |
7af8e998 | 3553 | * PROVIDE_HIDDEN:: PROVIDE_HIDDEN |
73ae6183 | 3554 | * Source Code Reference:: How to use a linker script defined symbol in source code |
252b5132 RH |
3555 | @end menu |
3556 | ||
3557 | @node Simple Assignments | |
3558 | @subsection Simple Assignments | |
3559 | ||
3560 | You may assign to a symbol using any of the C assignment operators: | |
3561 | ||
3562 | @table @code | |
3563 | @item @var{symbol} = @var{expression} ; | |
3564 | @itemx @var{symbol} += @var{expression} ; | |
3565 | @itemx @var{symbol} -= @var{expression} ; | |
3566 | @itemx @var{symbol} *= @var{expression} ; | |
3567 | @itemx @var{symbol} /= @var{expression} ; | |
3568 | @itemx @var{symbol} <<= @var{expression} ; | |
3569 | @itemx @var{symbol} >>= @var{expression} ; | |
3570 | @itemx @var{symbol} &= @var{expression} ; | |
3571 | @itemx @var{symbol} |= @var{expression} ; | |
3572 | @end table | |
3573 | ||
3574 | The first case will define @var{symbol} to the value of | |
3575 | @var{expression}. In the other cases, @var{symbol} must already be | |
3576 | defined, and the value will be adjusted accordingly. | |
3577 | ||
3578 | The special symbol name @samp{.} indicates the location counter. You | |
b5666f2f | 3579 | may only use this within a @code{SECTIONS} command. @xref{Location Counter}. |
252b5132 RH |
3580 | |
3581 | The semicolon after @var{expression} is required. | |
3582 | ||
3583 | Expressions are defined below; see @ref{Expressions}. | |
3584 | ||
3585 | You may write symbol assignments as commands in their own right, or as | |
3586 | statements within a @code{SECTIONS} command, or as part of an output | |
3587 | section description in a @code{SECTIONS} command. | |
3588 | ||
3589 | The section of the symbol will be set from the section of the | |
3590 | expression; for more information, see @ref{Expression Section}. | |
3591 | ||
3592 | Here is an example showing the three different places that symbol | |
3593 | assignments may be used: | |
3594 | ||
3595 | @smallexample | |
3596 | floating_point = 0; | |
3597 | SECTIONS | |
3598 | @{ | |
3599 | .text : | |
3600 | @{ | |
3601 | *(.text) | |
3602 | _etext = .; | |
3603 | @} | |
156e34dd | 3604 | _bdata = (. + 3) & ~ 3; |
252b5132 RH |
3605 | .data : @{ *(.data) @} |
3606 | @} | |
3607 | @end smallexample | |
3608 | @noindent | |
3609 | In this example, the symbol @samp{floating_point} will be defined as | |
3610 | zero. The symbol @samp{_etext} will be defined as the address following | |
3611 | the last @samp{.text} input section. The symbol @samp{_bdata} will be | |
3612 | defined as the address following the @samp{.text} output section aligned | |
3613 | upward to a 4 byte boundary. | |
3614 | ||
eb8476a6 MR |
3615 | @node HIDDEN |
3616 | @subsection HIDDEN | |
3617 | @cindex HIDDEN | |
3618 | For ELF targeted ports, define a symbol that will be hidden and won't be | |
3619 | exported. The syntax is @code{HIDDEN(@var{symbol} = @var{expression})}. | |
3620 | ||
3621 | Here is the example from @ref{Simple Assignments}, rewritten to use | |
3622 | @code{HIDDEN}: | |
3623 | ||
3624 | @smallexample | |
3625 | HIDDEN(floating_point = 0); | |
3626 | SECTIONS | |
3627 | @{ | |
3628 | .text : | |
3629 | @{ | |
3630 | *(.text) | |
3631 | HIDDEN(_etext = .); | |
3632 | @} | |
3633 | HIDDEN(_bdata = (. + 3) & ~ 3); | |
3634 | .data : @{ *(.data) @} | |
3635 | @} | |
3636 | @end smallexample | |
3637 | @noindent | |
3638 | In this case none of the three symbols will be visible outside this module. | |
3639 | ||
252b5132 RH |
3640 | @node PROVIDE |
3641 | @subsection PROVIDE | |
3642 | @cindex PROVIDE | |
3643 | In some cases, it is desirable for a linker script to define a symbol | |
3644 | only if it is referenced and is not defined by any object included in | |
3645 | the link. For example, traditional linkers defined the symbol | |
3646 | @samp{etext}. However, ANSI C requires that the user be able to use | |
3647 | @samp{etext} as a function name without encountering an error. The | |
3648 | @code{PROVIDE} keyword may be used to define a symbol, such as | |
3649 | @samp{etext}, only if it is referenced but not defined. The syntax is | |
3650 | @code{PROVIDE(@var{symbol} = @var{expression})}. | |
3651 | ||
3652 | Here is an example of using @code{PROVIDE} to define @samp{etext}: | |
3653 | @smallexample | |
3654 | SECTIONS | |
3655 | @{ | |
3656 | .text : | |
3657 | @{ | |
3658 | *(.text) | |
3659 | _etext = .; | |
3660 | PROVIDE(etext = .); | |
3661 | @} | |
3662 | @} | |
3663 | @end smallexample | |
3664 | ||
3665 | In this example, if the program defines @samp{_etext} (with a leading | |
3666 | underscore), the linker will give a multiple definition error. If, on | |
3667 | the other hand, the program defines @samp{etext} (with no leading | |
3668 | underscore), the linker will silently use the definition in the program. | |
3669 | If the program references @samp{etext} but does not define it, the | |
3670 | linker will use the definition in the linker script. | |
3671 | ||
7af8e998 L |
3672 | @node PROVIDE_HIDDEN |
3673 | @subsection PROVIDE_HIDDEN | |
3674 | @cindex PROVIDE_HIDDEN | |
3675 | Similar to @code{PROVIDE}. For ELF targeted ports, the symbol will be | |
3676 | hidden and won't be exported. | |
3677 | ||
73ae6183 NC |
3678 | @node Source Code Reference |
3679 | @subsection Source Code Reference | |
3680 | ||
3681 | Accessing a linker script defined variable from source code is not | |
3682 | intuitive. In particular a linker script symbol is not equivalent to | |
3683 | a variable declaration in a high level language, it is instead a | |
3684 | symbol that does not have a value. | |
3685 | ||
3686 | Before going further, it is important to note that compilers often | |
3687 | transform names in the source code into different names when they are | |
3688 | stored in the symbol table. For example, Fortran compilers commonly | |
3689 | prepend or append an underscore, and C++ performs extensive @samp{name | |
3690 | mangling}. Therefore there might be a discrepancy between the name | |
3691 | of a variable as it is used in source code and the name of the same | |
3692 | variable as it is defined in a linker script. For example in C a | |
3693 | linker script variable might be referred to as: | |
3694 | ||
3695 | @smallexample | |
3696 | extern int foo; | |
3697 | @end smallexample | |
3698 | ||
3699 | But in the linker script it might be defined as: | |
3700 | ||
3701 | @smallexample | |
3702 | _foo = 1000; | |
3703 | @end smallexample | |
3704 | ||
3705 | In the remaining examples however it is assumed that no name | |
3706 | transformation has taken place. | |
3707 | ||
3708 | When a symbol is declared in a high level language such as C, two | |
3709 | things happen. The first is that the compiler reserves enough space | |
3710 | in the program's memory to hold the @emph{value} of the symbol. The | |
3711 | second is that the compiler creates an entry in the program's symbol | |
3712 | table which holds the symbol's @emph{address}. ie the symbol table | |
3713 | contains the address of the block of memory holding the symbol's | |
3714 | value. So for example the following C declaration, at file scope: | |
3715 | ||
3716 | @smallexample | |
3717 | int foo = 1000; | |
3718 | @end smallexample | |
3719 | ||
10bf6894 | 3720 | creates an entry called @samp{foo} in the symbol table. This entry |
73ae6183 NC |
3721 | holds the address of an @samp{int} sized block of memory where the |
3722 | number 1000 is initially stored. | |
3723 | ||
3724 | When a program references a symbol the compiler generates code that | |
3725 | first accesses the symbol table to find the address of the symbol's | |
3726 | memory block and then code to read the value from that memory block. | |
3727 | So: | |
3728 | ||
3729 | @smallexample | |
3730 | foo = 1; | |
3731 | @end smallexample | |
3732 | ||
3733 | looks up the symbol @samp{foo} in the symbol table, gets the address | |
3734 | associated with this symbol and then writes the value 1 into that | |
3735 | address. Whereas: | |
3736 | ||
3737 | @smallexample | |
3738 | int * a = & foo; | |
3739 | @end smallexample | |
3740 | ||
10bf6894 | 3741 | looks up the symbol @samp{foo} in the symbol table, gets its address |
73ae6183 NC |
3742 | and then copies this address into the block of memory associated with |
3743 | the variable @samp{a}. | |
3744 | ||
3745 | Linker scripts symbol declarations, by contrast, create an entry in | |
3746 | the symbol table but do not assign any memory to them. Thus they are | |
3747 | an address without a value. So for example the linker script definition: | |
3748 | ||
3749 | @smallexample | |
3750 | foo = 1000; | |
3751 | @end smallexample | |
3752 | ||
3753 | creates an entry in the symbol table called @samp{foo} which holds | |
3754 | the address of memory location 1000, but nothing special is stored at | |
3755 | address 1000. This means that you cannot access the @emph{value} of a | |
3756 | linker script defined symbol - it has no value - all you can do is | |
3757 | access the @emph{address} of a linker script defined symbol. | |
3758 | ||
3759 | Hence when you are using a linker script defined symbol in source code | |
3760 | you should always take the address of the symbol, and never attempt to | |
3761 | use its value. For example suppose you want to copy the contents of a | |
3762 | section of memory called .ROM into a section called .FLASH and the | |
3763 | linker script contains these declarations: | |
3764 | ||
3765 | @smallexample | |
3766 | @group | |
3767 | start_of_ROM = .ROM; | |
3768 | end_of_ROM = .ROM + sizeof (.ROM) - 1; | |
3769 | start_of_FLASH = .FLASH; | |
3770 | @end group | |
3771 | @end smallexample | |
3772 | ||
3773 | Then the C source code to perform the copy would be: | |
3774 | ||
3775 | @smallexample | |
3776 | @group | |
3777 | extern char start_of_ROM, end_of_ROM, start_of_FLASH; | |
c0065db7 | 3778 | |
73ae6183 NC |
3779 | memcpy (& start_of_FLASH, & start_of_ROM, & end_of_ROM - & start_of_ROM); |
3780 | @end group | |
3781 | @end smallexample | |
3782 | ||
3783 | Note the use of the @samp{&} operators. These are correct. | |
3784 | ||
252b5132 | 3785 | @node SECTIONS |
36f63dca | 3786 | @section SECTIONS Command |
252b5132 RH |
3787 | @kindex SECTIONS |
3788 | The @code{SECTIONS} command tells the linker how to map input sections | |
3789 | into output sections, and how to place the output sections in memory. | |
3790 | ||
3791 | The format of the @code{SECTIONS} command is: | |
3792 | @smallexample | |
3793 | SECTIONS | |
3794 | @{ | |
3795 | @var{sections-command} | |
3796 | @var{sections-command} | |
3797 | @dots{} | |
3798 | @} | |
3799 | @end smallexample | |
3800 | ||
3801 | Each @var{sections-command} may of be one of the following: | |
3802 | ||
3803 | @itemize @bullet | |
3804 | @item | |
3805 | an @code{ENTRY} command (@pxref{Entry Point,,Entry command}) | |
3806 | @item | |
3807 | a symbol assignment (@pxref{Assignments}) | |
3808 | @item | |
3809 | an output section description | |
3810 | @item | |
3811 | an overlay description | |
3812 | @end itemize | |
3813 | ||
3814 | The @code{ENTRY} command and symbol assignments are permitted inside the | |
3815 | @code{SECTIONS} command for convenience in using the location counter in | |
3816 | those commands. This can also make the linker script easier to | |
3817 | understand because you can use those commands at meaningful points in | |
3818 | the layout of the output file. | |
3819 | ||
3820 | Output section descriptions and overlay descriptions are described | |
3821 | below. | |
3822 | ||
3823 | If you do not use a @code{SECTIONS} command in your linker script, the | |
3824 | linker will place each input section into an identically named output | |
3825 | section in the order that the sections are first encountered in the | |
3826 | input files. If all input sections are present in the first file, for | |
3827 | example, the order of sections in the output file will match the order | |
3828 | in the first input file. The first section will be at address zero. | |
3829 | ||
3830 | @menu | |
3831 | * Output Section Description:: Output section description | |
3832 | * Output Section Name:: Output section name | |
3833 | * Output Section Address:: Output section address | |
3834 | * Input Section:: Input section description | |
3835 | * Output Section Data:: Output section data | |
3836 | * Output Section Keywords:: Output section keywords | |
3837 | * Output Section Discarding:: Output section discarding | |
3838 | * Output Section Attributes:: Output section attributes | |
3839 | * Overlay Description:: Overlay description | |
3840 | @end menu | |
3841 | ||
3842 | @node Output Section Description | |
36f63dca | 3843 | @subsection Output Section Description |
252b5132 RH |
3844 | The full description of an output section looks like this: |
3845 | @smallexample | |
a1ab1d2a | 3846 | @group |
7e7d5768 | 3847 | @var{section} [@var{address}] [(@var{type})] : |
0c71d759 | 3848 | [AT(@var{lma})] |
1eec346e | 3849 | [ALIGN(@var{section_align}) | ALIGN_WITH_INPUT] |
0c71d759 NC |
3850 | [SUBALIGN(@var{subsection_align})] |
3851 | [@var{constraint}] | |
252b5132 RH |
3852 | @{ |
3853 | @var{output-section-command} | |
3854 | @var{output-section-command} | |
3855 | @dots{} | |
abc9061b | 3856 | @} [>@var{region}] [AT>@var{lma_region}] [:@var{phdr} :@var{phdr} @dots{}] [=@var{fillexp}] [,] |
252b5132 RH |
3857 | @end group |
3858 | @end smallexample | |
3859 | ||
3860 | Most output sections do not use most of the optional section attributes. | |
3861 | ||
3862 | The whitespace around @var{section} is required, so that the section | |
3863 | name is unambiguous. The colon and the curly braces are also required. | |
abc9061b CC |
3864 | The comma at the end may be required if a @var{fillexp} is used and |
3865 | the next @var{sections-command} looks like a continuation of the expression. | |
252b5132 RH |
3866 | The line breaks and other white space are optional. |
3867 | ||
3868 | Each @var{output-section-command} may be one of the following: | |
3869 | ||
3870 | @itemize @bullet | |
3871 | @item | |
3872 | a symbol assignment (@pxref{Assignments}) | |
3873 | @item | |
3874 | an input section description (@pxref{Input Section}) | |
3875 | @item | |
3876 | data values to include directly (@pxref{Output Section Data}) | |
3877 | @item | |
3878 | a special output section keyword (@pxref{Output Section Keywords}) | |
3879 | @end itemize | |
3880 | ||
3881 | @node Output Section Name | |
36f63dca | 3882 | @subsection Output Section Name |
252b5132 RH |
3883 | @cindex name, section |
3884 | @cindex section name | |
3885 | The name of the output section is @var{section}. @var{section} must | |
3886 | meet the constraints of your output format. In formats which only | |
3887 | support a limited number of sections, such as @code{a.out}, the name | |
3888 | must be one of the names supported by the format (@code{a.out}, for | |
3889 | example, allows only @samp{.text}, @samp{.data} or @samp{.bss}). If the | |
3890 | output format supports any number of sections, but with numbers and not | |
3891 | names (as is the case for Oasys), the name should be supplied as a | |
3892 | quoted numeric string. A section name may consist of any sequence of | |
3893 | characters, but a name which contains any unusual characters such as | |
3894 | commas must be quoted. | |
3895 | ||
3896 | The output section name @samp{/DISCARD/} is special; @ref{Output Section | |
3897 | Discarding}. | |
3898 | ||
3899 | @node Output Section Address | |
2a16d82a | 3900 | @subsection Output Section Address |
252b5132 RH |
3901 | @cindex address, section |
3902 | @cindex section address | |
3903 | The @var{address} is an expression for the VMA (the virtual memory | |
ea5cae92 NC |
3904 | address) of the output section. This address is optional, but if it |
3905 | is provided then the output address will be set exactly as specified. | |
3906 | ||
3907 | If the output address is not specified then one will be chosen for the | |
3908 | section, based on the heuristic below. This address will be adjusted | |
3909 | to fit the alignment requirement of the output section. The | |
3910 | alignment requirement is the strictest alignment of any input section | |
3911 | contained within the output section. | |
3912 | ||
3913 | The output section address heuristic is as follows: | |
3914 | ||
3915 | @itemize @bullet | |
3916 | @item | |
3917 | If an output memory @var{region} is set for the section then it | |
3918 | is added to this region and its address will be the next free address | |
3919 | in that region. | |
3920 | ||
3921 | @item | |
3922 | If the MEMORY command has been used to create a list of memory | |
3923 | regions then the first region which has attributes compatible with the | |
3924 | section is selected to contain it. The section's output address will | |
3925 | be the next free address in that region; @ref{MEMORY}. | |
3926 | ||
3927 | @item | |
3928 | If no memory regions were specified, or none match the section then | |
3929 | the output address will be based on the current value of the location | |
3930 | counter. | |
3931 | @end itemize | |
3932 | ||
3933 | @noindent | |
3934 | For example: | |
3935 | ||
252b5132 RH |
3936 | @smallexample |
3937 | .text . : @{ *(.text) @} | |
3938 | @end smallexample | |
ea5cae92 | 3939 | |
252b5132 RH |
3940 | @noindent |
3941 | and | |
ea5cae92 | 3942 | |
252b5132 RH |
3943 | @smallexample |
3944 | .text : @{ *(.text) @} | |
3945 | @end smallexample | |
ea5cae92 | 3946 | |
252b5132 RH |
3947 | @noindent |
3948 | are subtly different. The first will set the address of the | |
3949 | @samp{.text} output section to the current value of the location | |
3950 | counter. The second will set it to the current value of the location | |
ea5cae92 NC |
3951 | counter aligned to the strictest alignment of any of the @samp{.text} |
3952 | input sections. | |
252b5132 RH |
3953 | |
3954 | The @var{address} may be an arbitrary expression; @ref{Expressions}. | |
3955 | For example, if you want to align the section on a 0x10 byte boundary, | |
3956 | so that the lowest four bits of the section address are zero, you could | |
3957 | do something like this: | |
3958 | @smallexample | |
3959 | .text ALIGN(0x10) : @{ *(.text) @} | |
3960 | @end smallexample | |
3961 | @noindent | |
3962 | This works because @code{ALIGN} returns the current location counter | |
3963 | aligned upward to the specified value. | |
3964 | ||
3965 | Specifying @var{address} for a section will change the value of the | |
6ce340f1 NC |
3966 | location counter, provided that the section is non-empty. (Empty |
3967 | sections are ignored). | |
252b5132 RH |
3968 | |
3969 | @node Input Section | |
36f63dca | 3970 | @subsection Input Section Description |
252b5132 RH |
3971 | @cindex input sections |
3972 | @cindex mapping input sections to output sections | |
3973 | The most common output section command is an input section description. | |
3974 | ||
3975 | The input section description is the most basic linker script operation. | |
3976 | You use output sections to tell the linker how to lay out your program | |
3977 | in memory. You use input section descriptions to tell the linker how to | |
3978 | map the input files into your memory layout. | |
3979 | ||
3980 | @menu | |
3981 | * Input Section Basics:: Input section basics | |
3982 | * Input Section Wildcards:: Input section wildcard patterns | |
3983 | * Input Section Common:: Input section for common symbols | |
3984 | * Input Section Keep:: Input section and garbage collection | |
3985 | * Input Section Example:: Input section example | |
3986 | @end menu | |
3987 | ||
3988 | @node Input Section Basics | |
36f63dca | 3989 | @subsubsection Input Section Basics |
252b5132 RH |
3990 | @cindex input section basics |
3991 | An input section description consists of a file name optionally followed | |
3992 | by a list of section names in parentheses. | |
3993 | ||
3994 | The file name and the section name may be wildcard patterns, which we | |
3995 | describe further below (@pxref{Input Section Wildcards}). | |
3996 | ||
3997 | The most common input section description is to include all input | |
3998 | sections with a particular name in the output section. For example, to | |
3999 | include all input @samp{.text} sections, you would write: | |
4000 | @smallexample | |
4001 | *(.text) | |
4002 | @end smallexample | |
4003 | @noindent | |
18625d54 CM |
4004 | Here the @samp{*} is a wildcard which matches any file name. To exclude a list |
4005 | of files from matching the file name wildcard, EXCLUDE_FILE may be used to | |
4006 | match all files except the ones specified in the EXCLUDE_FILE list. For | |
4007 | example: | |
252b5132 | 4008 | @smallexample |
b4346c09 | 4009 | *(EXCLUDE_FILE (*crtend.o *otherfile.o) .ctors) |
252b5132 | 4010 | @end smallexample |
765b7cbe JB |
4011 | will cause all .ctors sections from all files except @file{crtend.o} and |
4012 | @file{otherfile.o} to be included. | |
252b5132 RH |
4013 | |
4014 | There are two ways to include more than one section: | |
4015 | @smallexample | |
4016 | *(.text .rdata) | |
4017 | *(.text) *(.rdata) | |
4018 | @end smallexample | |
4019 | @noindent | |
4020 | The difference between these is the order in which the @samp{.text} and | |
4021 | @samp{.rdata} input sections will appear in the output section. In the | |
b6bf44ba AM |
4022 | first example, they will be intermingled, appearing in the same order as |
4023 | they are found in the linker input. In the second example, all | |
252b5132 RH |
4024 | @samp{.text} input sections will appear first, followed by all |
4025 | @samp{.rdata} input sections. | |
4026 | ||
4027 | You can specify a file name to include sections from a particular file. | |
4028 | You would do this if one or more of your files contain special data that | |
4029 | needs to be at a particular location in memory. For example: | |
4030 | @smallexample | |
4031 | data.o(.data) | |
4032 | @end smallexample | |
4033 | ||
ae17ab41 CM |
4034 | To refine the sections that are included based on the section flags |
4035 | of an input section, INPUT_SECTION_FLAGS may be used. | |
4036 | ||
4037 | Here is a simple example for using Section header flags for ELF sections: | |
4038 | ||
4039 | @smallexample | |
4040 | @group | |
4041 | SECTIONS @{ | |
4042 | .text : @{ INPUT_SECTION_FLAGS (SHF_MERGE & SHF_STRINGS) *(.text) @} | |
4043 | .text2 : @{ INPUT_SECTION_FLAGS (!SHF_WRITE) *(.text) @} | |
4044 | @} | |
4045 | @end group | |
4046 | @end smallexample | |
4047 | ||
4048 | In this example, the output section @samp{.text} will be comprised of any | |
4049 | input section matching the name *(.text) whose section header flags | |
4050 | @code{SHF_MERGE} and @code{SHF_STRINGS} are set. The output section | |
4051 | @samp{.text2} will be comprised of any input section matching the name *(.text) | |
4052 | whose section header flag @code{SHF_WRITE} is clear. | |
4053 | ||
967928e9 AM |
4054 | You can also specify files within archives by writing a pattern |
4055 | matching the archive, a colon, then the pattern matching the file, | |
4056 | with no whitespace around the colon. | |
4057 | ||
4058 | @table @samp | |
4059 | @item archive:file | |
4060 | matches file within archive | |
4061 | @item archive: | |
4062 | matches the whole archive | |
4063 | @item :file | |
4064 | matches file but not one in an archive | |
4065 | @end table | |
4066 | ||
4067 | Either one or both of @samp{archive} and @samp{file} can contain shell | |
4068 | wildcards. On DOS based file systems, the linker will assume that a | |
4069 | single letter followed by a colon is a drive specifier, so | |
4070 | @samp{c:myfile.o} is a simple file specification, not @samp{myfile.o} | |
4071 | within an archive called @samp{c}. @samp{archive:file} filespecs may | |
4072 | also be used within an @code{EXCLUDE_FILE} list, but may not appear in | |
4073 | other linker script contexts. For instance, you cannot extract a file | |
4074 | from an archive by using @samp{archive:file} in an @code{INPUT} | |
4075 | command. | |
4076 | ||
252b5132 RH |
4077 | If you use a file name without a list of sections, then all sections in |
4078 | the input file will be included in the output section. This is not | |
4079 | commonly done, but it may by useful on occasion. For example: | |
4080 | @smallexample | |
4081 | data.o | |
4082 | @end smallexample | |
4083 | ||
967928e9 AM |
4084 | When you use a file name which is not an @samp{archive:file} specifier |
4085 | and does not contain any wild card | |
252b5132 RH |
4086 | characters, the linker will first see if you also specified the file |
4087 | name on the linker command line or in an @code{INPUT} command. If you | |
4088 | did not, the linker will attempt to open the file as an input file, as | |
4089 | though it appeared on the command line. Note that this differs from an | |
4090 | @code{INPUT} command, because the linker will not search for the file in | |
4091 | the archive search path. | |
4092 | ||
4093 | @node Input Section Wildcards | |
36f63dca | 4094 | @subsubsection Input Section Wildcard Patterns |
252b5132 RH |
4095 | @cindex input section wildcards |
4096 | @cindex wildcard file name patterns | |
4097 | @cindex file name wildcard patterns | |
4098 | @cindex section name wildcard patterns | |
4099 | In an input section description, either the file name or the section | |
4100 | name or both may be wildcard patterns. | |
4101 | ||
4102 | The file name of @samp{*} seen in many examples is a simple wildcard | |
4103 | pattern for the file name. | |
4104 | ||
4105 | The wildcard patterns are like those used by the Unix shell. | |
4106 | ||
4107 | @table @samp | |
4108 | @item * | |
4109 | matches any number of characters | |
4110 | @item ? | |
4111 | matches any single character | |
4112 | @item [@var{chars}] | |
4113 | matches a single instance of any of the @var{chars}; the @samp{-} | |
4114 | character may be used to specify a range of characters, as in | |
4115 | @samp{[a-z]} to match any lower case letter | |
4116 | @item \ | |
4117 | quotes the following character | |
4118 | @end table | |
4119 | ||
4120 | When a file name is matched with a wildcard, the wildcard characters | |
4121 | will not match a @samp{/} character (used to separate directory names on | |
4122 | Unix). A pattern consisting of a single @samp{*} character is an | |
4123 | exception; it will always match any file name, whether it contains a | |
4124 | @samp{/} or not. In a section name, the wildcard characters will match | |
4125 | a @samp{/} character. | |
4126 | ||
4127 | File name wildcard patterns only match files which are explicitly | |
4128 | specified on the command line or in an @code{INPUT} command. The linker | |
4129 | does not search directories to expand wildcards. | |
4130 | ||
4131 | If a file name matches more than one wildcard pattern, or if a file name | |
4132 | appears explicitly and is also matched by a wildcard pattern, the linker | |
4133 | will use the first match in the linker script. For example, this | |
4134 | sequence of input section descriptions is probably in error, because the | |
4135 | @file{data.o} rule will not be used: | |
4136 | @smallexample | |
4137 | .data : @{ *(.data) @} | |
4138 | .data1 : @{ data.o(.data) @} | |
4139 | @end smallexample | |
4140 | ||
bcaa7b3e | 4141 | @cindex SORT_BY_NAME |
252b5132 RH |
4142 | Normally, the linker will place files and sections matched by wildcards |
4143 | in the order in which they are seen during the link. You can change | |
bcaa7b3e L |
4144 | this by using the @code{SORT_BY_NAME} keyword, which appears before a wildcard |
4145 | pattern in parentheses (e.g., @code{SORT_BY_NAME(.text*)}). When the | |
4146 | @code{SORT_BY_NAME} keyword is used, the linker will sort the files or sections | |
252b5132 RH |
4147 | into ascending order by name before placing them in the output file. |
4148 | ||
bcaa7b3e L |
4149 | @cindex SORT_BY_ALIGNMENT |
4150 | @code{SORT_BY_ALIGNMENT} is very similar to @code{SORT_BY_NAME}. The | |
4151 | difference is @code{SORT_BY_ALIGNMENT} will sort sections into | |
1ae5c3ae | 4152 | descending order by alignment before placing them in the output file. |
ee83b8a6 NC |
4153 | Larger alignments are placed before smaller alignments in order to |
4154 | reduce the amount of padding necessary. | |
bcaa7b3e | 4155 | |
02ecc8e9 L |
4156 | @cindex SORT_BY_INIT_PRIORITY |
4157 | @code{SORT_BY_INIT_PRIORITY} is very similar to @code{SORT_BY_NAME}. The | |
4158 | difference is @code{SORT_BY_INIT_PRIORITY} will sort sections into | |
4159 | ascending order by numerical value of the GCC init_priority attribute | |
4160 | encoded in the section name before placing them in the output file. | |
4161 | ||
bcaa7b3e L |
4162 | @cindex SORT |
4163 | @code{SORT} is an alias for @code{SORT_BY_NAME}. | |
4164 | ||
4165 | When there are nested section sorting commands in linker script, there | |
4166 | can be at most 1 level of nesting for section sorting commands. | |
4167 | ||
4168 | @enumerate | |
4169 | @item | |
4170 | @code{SORT_BY_NAME} (@code{SORT_BY_ALIGNMENT} (wildcard section pattern)). | |
1ae5c3ae | 4171 | It will sort the input sections by name first, then by alignment if two |
bcaa7b3e L |
4172 | sections have the same name. |
4173 | @item | |
4174 | @code{SORT_BY_ALIGNMENT} (@code{SORT_BY_NAME} (wildcard section pattern)). | |
1ae5c3ae | 4175 | It will sort the input sections by alignment first, then by name if two |
bcaa7b3e L |
4176 | sections have the same alignment. |
4177 | @item | |
c0065db7 | 4178 | @code{SORT_BY_NAME} (@code{SORT_BY_NAME} (wildcard section pattern)) is |
bcaa7b3e L |
4179 | treated the same as @code{SORT_BY_NAME} (wildcard section pattern). |
4180 | @item | |
4181 | @code{SORT_BY_ALIGNMENT} (@code{SORT_BY_ALIGNMENT} (wildcard section pattern)) | |
4182 | is treated the same as @code{SORT_BY_ALIGNMENT} (wildcard section pattern). | |
4183 | @item | |
4184 | All other nested section sorting commands are invalid. | |
4185 | @end enumerate | |
4186 | ||
4187 | When both command line section sorting option and linker script | |
4188 | section sorting command are used, section sorting command always | |
4189 | takes precedence over the command line option. | |
4190 | ||
4191 | If the section sorting command in linker script isn't nested, the | |
4192 | command line option will make the section sorting command to be | |
4193 | treated as nested sorting command. | |
4194 | ||
4195 | @enumerate | |
4196 | @item | |
4197 | @code{SORT_BY_NAME} (wildcard section pattern ) with | |
4198 | @option{--sort-sections alignment} is equivalent to | |
4199 | @code{SORT_BY_NAME} (@code{SORT_BY_ALIGNMENT} (wildcard section pattern)). | |
4200 | @item | |
4201 | @code{SORT_BY_ALIGNMENT} (wildcard section pattern) with | |
4202 | @option{--sort-section name} is equivalent to | |
4203 | @code{SORT_BY_ALIGNMENT} (@code{SORT_BY_NAME} (wildcard section pattern)). | |
4204 | @end enumerate | |
4205 | ||
4206 | If the section sorting command in linker script is nested, the | |
4207 | command line option will be ignored. | |
4208 | ||
eda680f8 L |
4209 | @cindex SORT_NONE |
4210 | @code{SORT_NONE} disables section sorting by ignoring the command line | |
4211 | section sorting option. | |
4212 | ||
252b5132 RH |
4213 | If you ever get confused about where input sections are going, use the |
4214 | @samp{-M} linker option to generate a map file. The map file shows | |
4215 | precisely how input sections are mapped to output sections. | |
4216 | ||
4217 | This example shows how wildcard patterns might be used to partition | |
4218 | files. This linker script directs the linker to place all @samp{.text} | |
4219 | sections in @samp{.text} and all @samp{.bss} sections in @samp{.bss}. | |
4220 | The linker will place the @samp{.data} section from all files beginning | |
4221 | with an upper case character in @samp{.DATA}; for all other files, the | |
4222 | linker will place the @samp{.data} section in @samp{.data}. | |
4223 | @smallexample | |
4224 | @group | |
4225 | SECTIONS @{ | |
4226 | .text : @{ *(.text) @} | |
4227 | .DATA : @{ [A-Z]*(.data) @} | |
4228 | .data : @{ *(.data) @} | |
4229 | .bss : @{ *(.bss) @} | |
4230 | @} | |
4231 | @end group | |
4232 | @end smallexample | |
4233 | ||
4234 | @node Input Section Common | |
36f63dca | 4235 | @subsubsection Input Section for Common Symbols |
252b5132 RH |
4236 | @cindex common symbol placement |
4237 | @cindex uninitialized data placement | |
4238 | A special notation is needed for common symbols, because in many object | |
4239 | file formats common symbols do not have a particular input section. The | |
4240 | linker treats common symbols as though they are in an input section | |
4241 | named @samp{COMMON}. | |
4242 | ||
4243 | You may use file names with the @samp{COMMON} section just as with any | |
4244 | other input sections. You can use this to place common symbols from a | |
4245 | particular input file in one section while common symbols from other | |
4246 | input files are placed in another section. | |
4247 | ||
4248 | In most cases, common symbols in input files will be placed in the | |
4249 | @samp{.bss} section in the output file. For example: | |
4250 | @smallexample | |
4251 | .bss @{ *(.bss) *(COMMON) @} | |
4252 | @end smallexample | |
4253 | ||
4254 | @cindex scommon section | |
4255 | @cindex small common symbols | |
4256 | Some object file formats have more than one type of common symbol. For | |
4257 | example, the MIPS ELF object file format distinguishes standard common | |
4258 | symbols and small common symbols. In this case, the linker will use a | |
4259 | different special section name for other types of common symbols. In | |
4260 | the case of MIPS ELF, the linker uses @samp{COMMON} for standard common | |
4261 | symbols and @samp{.scommon} for small common symbols. This permits you | |
4262 | to map the different types of common symbols into memory at different | |
4263 | locations. | |
4264 | ||
4265 | @cindex [COMMON] | |
4266 | You will sometimes see @samp{[COMMON]} in old linker scripts. This | |
4267 | notation is now considered obsolete. It is equivalent to | |
4268 | @samp{*(COMMON)}. | |
4269 | ||
4270 | @node Input Section Keep | |
36f63dca | 4271 | @subsubsection Input Section and Garbage Collection |
252b5132 RH |
4272 | @cindex KEEP |
4273 | @cindex garbage collection | |
4274 | When link-time garbage collection is in use (@samp{--gc-sections}), | |
a1ab1d2a | 4275 | it is often useful to mark sections that should not be eliminated. |
252b5132 RH |
4276 | This is accomplished by surrounding an input section's wildcard entry |
4277 | with @code{KEEP()}, as in @code{KEEP(*(.init))} or | |
bcaa7b3e | 4278 | @code{KEEP(SORT_BY_NAME(*)(.ctors))}. |
252b5132 RH |
4279 | |
4280 | @node Input Section Example | |
36f63dca | 4281 | @subsubsection Input Section Example |
252b5132 RH |
4282 | The following example is a complete linker script. It tells the linker |
4283 | to read all of the sections from file @file{all.o} and place them at the | |
4284 | start of output section @samp{outputa} which starts at location | |
4285 | @samp{0x10000}. All of section @samp{.input1} from file @file{foo.o} | |
4286 | follows immediately, in the same output section. All of section | |
4287 | @samp{.input2} from @file{foo.o} goes into output section | |
4288 | @samp{outputb}, followed by section @samp{.input1} from @file{foo1.o}. | |
4289 | All of the remaining @samp{.input1} and @samp{.input2} sections from any | |
4290 | files are written to output section @samp{outputc}. | |
4291 | ||
4292 | @smallexample | |
4293 | @group | |
4294 | SECTIONS @{ | |
4295 | outputa 0x10000 : | |
4296 | @{ | |
4297 | all.o | |
4298 | foo.o (.input1) | |
4299 | @} | |
36f63dca NC |
4300 | @end group |
4301 | @group | |
252b5132 RH |
4302 | outputb : |
4303 | @{ | |
4304 | foo.o (.input2) | |
4305 | foo1.o (.input1) | |
4306 | @} | |
36f63dca NC |
4307 | @end group |
4308 | @group | |
252b5132 RH |
4309 | outputc : |
4310 | @{ | |
4311 | *(.input1) | |
4312 | *(.input2) | |
4313 | @} | |
4314 | @} | |
4315 | @end group | |
a1ab1d2a | 4316 | @end smallexample |
252b5132 RH |
4317 | |
4318 | @node Output Section Data | |
36f63dca | 4319 | @subsection Output Section Data |
252b5132 RH |
4320 | @cindex data |
4321 | @cindex section data | |
4322 | @cindex output section data | |
4323 | @kindex BYTE(@var{expression}) | |
4324 | @kindex SHORT(@var{expression}) | |
4325 | @kindex LONG(@var{expression}) | |
4326 | @kindex QUAD(@var{expression}) | |
4327 | @kindex SQUAD(@var{expression}) | |
4328 | You can include explicit bytes of data in an output section by using | |
4329 | @code{BYTE}, @code{SHORT}, @code{LONG}, @code{QUAD}, or @code{SQUAD} as | |
4330 | an output section command. Each keyword is followed by an expression in | |
4331 | parentheses providing the value to store (@pxref{Expressions}). The | |
4332 | value of the expression is stored at the current value of the location | |
4333 | counter. | |
4334 | ||
4335 | The @code{BYTE}, @code{SHORT}, @code{LONG}, and @code{QUAD} commands | |
4336 | store one, two, four, and eight bytes (respectively). After storing the | |
4337 | bytes, the location counter is incremented by the number of bytes | |
4338 | stored. | |
4339 | ||
4340 | For example, this will store the byte 1 followed by the four byte value | |
4341 | of the symbol @samp{addr}: | |
4342 | @smallexample | |
4343 | BYTE(1) | |
4344 | LONG(addr) | |
4345 | @end smallexample | |
4346 | ||
4347 | When using a 64 bit host or target, @code{QUAD} and @code{SQUAD} are the | |
4348 | same; they both store an 8 byte, or 64 bit, value. When both host and | |
4349 | target are 32 bits, an expression is computed as 32 bits. In this case | |
4350 | @code{QUAD} stores a 32 bit value zero extended to 64 bits, and | |
4351 | @code{SQUAD} stores a 32 bit value sign extended to 64 bits. | |
4352 | ||
4353 | If the object file format of the output file has an explicit endianness, | |
4354 | which is the normal case, the value will be stored in that endianness. | |
4355 | When the object file format does not have an explicit endianness, as is | |
4356 | true of, for example, S-records, the value will be stored in the | |
4357 | endianness of the first input object file. | |
4358 | ||
36f63dca | 4359 | Note---these commands only work inside a section description and not |
2b5fc1f5 NC |
4360 | between them, so the following will produce an error from the linker: |
4361 | @smallexample | |
4362 | SECTIONS @{@ .text : @{@ *(.text) @}@ LONG(1) .data : @{@ *(.data) @}@ @}@ | |
4363 | @end smallexample | |
4364 | whereas this will work: | |
4365 | @smallexample | |
4366 | SECTIONS @{@ .text : @{@ *(.text) ; LONG(1) @}@ .data : @{@ *(.data) @}@ @}@ | |
4367 | @end smallexample | |
4368 | ||
252b5132 RH |
4369 | @kindex FILL(@var{expression}) |
4370 | @cindex holes, filling | |
4371 | @cindex unspecified memory | |
4372 | You may use the @code{FILL} command to set the fill pattern for the | |
4373 | current section. It is followed by an expression in parentheses. Any | |
4374 | otherwise unspecified regions of memory within the section (for example, | |
4375 | gaps left due to the required alignment of input sections) are filled | |
a139d329 | 4376 | with the value of the expression, repeated as |
252b5132 RH |
4377 | necessary. A @code{FILL} statement covers memory locations after the |
4378 | point at which it occurs in the section definition; by including more | |
4379 | than one @code{FILL} statement, you can have different fill patterns in | |
4380 | different parts of an output section. | |
4381 | ||
4382 | This example shows how to fill unspecified regions of memory with the | |
563e308f | 4383 | value @samp{0x90}: |
252b5132 | 4384 | @smallexample |
563e308f | 4385 | FILL(0x90909090) |
252b5132 RH |
4386 | @end smallexample |
4387 | ||
4388 | The @code{FILL} command is similar to the @samp{=@var{fillexp}} output | |
9673c93c | 4389 | section attribute, but it only affects the |
252b5132 RH |
4390 | part of the section following the @code{FILL} command, rather than the |
4391 | entire section. If both are used, the @code{FILL} command takes | |
9673c93c | 4392 | precedence. @xref{Output Section Fill}, for details on the fill |
a139d329 | 4393 | expression. |
252b5132 RH |
4394 | |
4395 | @node Output Section Keywords | |
36f63dca | 4396 | @subsection Output Section Keywords |
252b5132 RH |
4397 | There are a couple of keywords which can appear as output section |
4398 | commands. | |
4399 | ||
4400 | @table @code | |
4401 | @kindex CREATE_OBJECT_SYMBOLS | |
4402 | @cindex input filename symbols | |
4403 | @cindex filename symbols | |
4404 | @item CREATE_OBJECT_SYMBOLS | |
4405 | The command tells the linker to create a symbol for each input file. | |
4406 | The name of each symbol will be the name of the corresponding input | |
4407 | file. The section of each symbol will be the output section in which | |
4408 | the @code{CREATE_OBJECT_SYMBOLS} command appears. | |
4409 | ||
4410 | This is conventional for the a.out object file format. It is not | |
4411 | normally used for any other object file format. | |
4412 | ||
4413 | @kindex CONSTRUCTORS | |
4414 | @cindex C++ constructors, arranging in link | |
4415 | @cindex constructors, arranging in link | |
4416 | @item CONSTRUCTORS | |
4417 | When linking using the a.out object file format, the linker uses an | |
4418 | unusual set construct to support C++ global constructors and | |
4419 | destructors. When linking object file formats which do not support | |
4420 | arbitrary sections, such as ECOFF and XCOFF, the linker will | |
4421 | automatically recognize C++ global constructors and destructors by name. | |
4422 | For these object file formats, the @code{CONSTRUCTORS} command tells the | |
4423 | linker to place constructor information in the output section where the | |
4424 | @code{CONSTRUCTORS} command appears. The @code{CONSTRUCTORS} command is | |
4425 | ignored for other object file formats. | |
4426 | ||
4427 | The symbol @w{@code{__CTOR_LIST__}} marks the start of the global | |
7e69709c AM |
4428 | constructors, and the symbol @w{@code{__CTOR_END__}} marks the end. |
4429 | Similarly, @w{@code{__DTOR_LIST__}} and @w{@code{__DTOR_END__}} mark | |
4430 | the start and end of the global destructors. The | |
252b5132 RH |
4431 | first word in the list is the number of entries, followed by the address |
4432 | of each constructor or destructor, followed by a zero word. The | |
4433 | compiler must arrange to actually run the code. For these object file | |
4434 | formats @sc{gnu} C++ normally calls constructors from a subroutine | |
4435 | @code{__main}; a call to @code{__main} is automatically inserted into | |
4436 | the startup code for @code{main}. @sc{gnu} C++ normally runs | |
4437 | destructors either by using @code{atexit}, or directly from the function | |
4438 | @code{exit}. | |
4439 | ||
4440 | For object file formats such as @code{COFF} or @code{ELF} which support | |
4441 | arbitrary section names, @sc{gnu} C++ will normally arrange to put the | |
4442 | addresses of global constructors and destructors into the @code{.ctors} | |
4443 | and @code{.dtors} sections. Placing the following sequence into your | |
4444 | linker script will build the sort of table which the @sc{gnu} C++ | |
4445 | runtime code expects to see. | |
4446 | ||
4447 | @smallexample | |
4448 | __CTOR_LIST__ = .; | |
4449 | LONG((__CTOR_END__ - __CTOR_LIST__) / 4 - 2) | |
4450 | *(.ctors) | |
4451 | LONG(0) | |
4452 | __CTOR_END__ = .; | |
4453 | __DTOR_LIST__ = .; | |
4454 | LONG((__DTOR_END__ - __DTOR_LIST__) / 4 - 2) | |
4455 | *(.dtors) | |
4456 | LONG(0) | |
4457 | __DTOR_END__ = .; | |
4458 | @end smallexample | |
4459 | ||
4460 | If you are using the @sc{gnu} C++ support for initialization priority, | |
4461 | which provides some control over the order in which global constructors | |
4462 | are run, you must sort the constructors at link time to ensure that they | |
4463 | are executed in the correct order. When using the @code{CONSTRUCTORS} | |
bcaa7b3e L |
4464 | command, use @samp{SORT_BY_NAME(CONSTRUCTORS)} instead. When using the |
4465 | @code{.ctors} and @code{.dtors} sections, use @samp{*(SORT_BY_NAME(.ctors))} and | |
4466 | @samp{*(SORT_BY_NAME(.dtors))} instead of just @samp{*(.ctors)} and | |
252b5132 RH |
4467 | @samp{*(.dtors)}. |
4468 | ||
4469 | Normally the compiler and linker will handle these issues automatically, | |
4470 | and you will not need to concern yourself with them. However, you may | |
4471 | need to consider this if you are using C++ and writing your own linker | |
4472 | scripts. | |
4473 | ||
4474 | @end table | |
4475 | ||
4476 | @node Output Section Discarding | |
36f63dca | 4477 | @subsection Output Section Discarding |
252b5132 RH |
4478 | @cindex discarding sections |
4479 | @cindex sections, discarding | |
4480 | @cindex removing sections | |
2edab91c AM |
4481 | The linker will not normally create output sections with no contents. |
4482 | This is for convenience when referring to input sections that may or | |
4483 | may not be present in any of the input files. For example: | |
252b5132 | 4484 | @smallexample |
49c13adb | 4485 | .foo : @{ *(.foo) @} |
252b5132 RH |
4486 | @end smallexample |
4487 | @noindent | |
4488 | will only create a @samp{.foo} section in the output file if there is a | |
74541ad4 AM |
4489 | @samp{.foo} section in at least one input file, and if the input |
4490 | sections are not all empty. Other link script directives that allocate | |
2edab91c AM |
4491 | space in an output section will also create the output section. So |
4492 | too will assignments to dot even if the assignment does not create | |
4493 | space, except for @samp{. = 0}, @samp{. = . + 0}, @samp{. = sym}, | |
4494 | @samp{. = . + sym} and @samp{. = ALIGN (. != 0, expr, 1)} when | |
4495 | @samp{sym} is an absolute symbol of value 0 defined in the script. | |
4496 | This allows you to force output of an empty section with @samp{. = .}. | |
74541ad4 | 4497 | |
a0976ea4 | 4498 | The linker will ignore address assignments (@pxref{Output Section Address}) |
74541ad4 AM |
4499 | on discarded output sections, except when the linker script defines |
4500 | symbols in the output section. In that case the linker will obey | |
a0976ea4 AM |
4501 | the address assignments, possibly advancing dot even though the |
4502 | section is discarded. | |
252b5132 RH |
4503 | |
4504 | @cindex /DISCARD/ | |
4505 | The special output section name @samp{/DISCARD/} may be used to discard | |
4506 | input sections. Any input sections which are assigned to an output | |
4507 | section named @samp{/DISCARD/} are not included in the output file. | |
4508 | ||
4509 | @node Output Section Attributes | |
36f63dca | 4510 | @subsection Output Section Attributes |
252b5132 RH |
4511 | @cindex output section attributes |
4512 | We showed above that the full description of an output section looked | |
4513 | like this: | |
0c71d759 | 4514 | |
252b5132 | 4515 | @smallexample |
a1ab1d2a | 4516 | @group |
7e7d5768 | 4517 | @var{section} [@var{address}] [(@var{type})] : |
0c71d759 NC |
4518 | [AT(@var{lma})] |
4519 | [ALIGN(@var{section_align})] | |
4520 | [SUBALIGN(@var{subsection_align})] | |
4521 | [@var{constraint}] | |
252b5132 RH |
4522 | @{ |
4523 | @var{output-section-command} | |
4524 | @var{output-section-command} | |
4525 | @dots{} | |
562d3460 | 4526 | @} [>@var{region}] [AT>@var{lma_region}] [:@var{phdr} :@var{phdr} @dots{}] [=@var{fillexp}] |
252b5132 RH |
4527 | @end group |
4528 | @end smallexample | |
0c71d759 | 4529 | |
252b5132 RH |
4530 | We've already described @var{section}, @var{address}, and |
4531 | @var{output-section-command}. In this section we will describe the | |
4532 | remaining section attributes. | |
4533 | ||
a1ab1d2a | 4534 | @menu |
252b5132 RH |
4535 | * Output Section Type:: Output section type |
4536 | * Output Section LMA:: Output section LMA | |
bbf115d3 | 4537 | * Forced Output Alignment:: Forced Output Alignment |
7e7d5768 | 4538 | * Forced Input Alignment:: Forced Input Alignment |
0c71d759 | 4539 | * Output Section Constraint:: Output section constraint |
252b5132 RH |
4540 | * Output Section Region:: Output section region |
4541 | * Output Section Phdr:: Output section phdr | |
4542 | * Output Section Fill:: Output section fill | |
4543 | @end menu | |
4544 | ||
4545 | @node Output Section Type | |
36f63dca | 4546 | @subsubsection Output Section Type |
252b5132 RH |
4547 | Each output section may have a type. The type is a keyword in |
4548 | parentheses. The following types are defined: | |
4549 | ||
4550 | @table @code | |
4551 | @item NOLOAD | |
4552 | The section should be marked as not loadable, so that it will not be | |
4553 | loaded into memory when the program is run. | |
4554 | @item DSECT | |
4555 | @itemx COPY | |
4556 | @itemx INFO | |
4557 | @itemx OVERLAY | |
4558 | These type names are supported for backward compatibility, and are | |
4559 | rarely used. They all have the same effect: the section should be | |
4560 | marked as not allocatable, so that no memory is allocated for the | |
4561 | section when the program is run. | |
4562 | @end table | |
4563 | ||
4564 | @kindex NOLOAD | |
4565 | @cindex prevent unnecessary loading | |
4566 | @cindex loading, preventing | |
4567 | The linker normally sets the attributes of an output section based on | |
4568 | the input sections which map into it. You can override this by using | |
4569 | the section type. For example, in the script sample below, the | |
4570 | @samp{ROM} section is addressed at memory location @samp{0} and does not | |
2e76e85a | 4571 | need to be loaded when the program is run. |
252b5132 RH |
4572 | @smallexample |
4573 | @group | |
4574 | SECTIONS @{ | |
4575 | ROM 0 (NOLOAD) : @{ @dots{} @} | |
4576 | @dots{} | |
4577 | @} | |
4578 | @end group | |
4579 | @end smallexample | |
4580 | ||
4581 | @node Output Section LMA | |
36f63dca | 4582 | @subsubsection Output Section LMA |
562d3460 | 4583 | @kindex AT>@var{lma_region} |
252b5132 RH |
4584 | @kindex AT(@var{lma}) |
4585 | @cindex load address | |
4586 | @cindex section load address | |
4587 | Every section has a virtual address (VMA) and a load address (LMA); see | |
ea5cae92 NC |
4588 | @ref{Basic Script Concepts}. The virtual address is specified by the |
4589 | @pxref{Output Section Address} described earlier. The load address is | |
4590 | specified by the @code{AT} or @code{AT>} keywords. Specifying a load | |
4591 | address is optional. | |
6bdafbeb | 4592 | |
ea5cae92 NC |
4593 | The @code{AT} keyword takes an expression as an argument. This |
4594 | specifies the exact load address of the section. The @code{AT>} keyword | |
4595 | takes the name of a memory region as an argument. @xref{MEMORY}. The | |
4596 | load address of the section is set to the next free address in the | |
4597 | region, aligned to the section's alignment requirements. | |
dc0b6aa0 AM |
4598 | |
4599 | If neither @code{AT} nor @code{AT>} is specified for an allocatable | |
ea5cae92 NC |
4600 | section, the linker will use the following heuristic to determine the |
4601 | load address: | |
4602 | ||
4603 | @itemize @bullet | |
4604 | @item | |
4605 | If the section has a specific VMA address, then this is used as | |
4606 | the LMA address as well. | |
4607 | ||
4608 | @item | |
4609 | If the section is not allocatable then its LMA is set to its VMA. | |
4610 | ||
4611 | @item | |
4612 | Otherwise if a memory region can be found that is compatible | |
4613 | with the current section, and this region contains at least one | |
4614 | section, then the LMA is set so the difference between the | |
4615 | VMA and LMA is the same as the difference between the VMA and LMA of | |
4616 | the last section in the located region. | |
4617 | ||
4618 | @item | |
4619 | If no memory regions have been declared then a default region | |
4620 | that covers the entire address space is used in the previous step. | |
4621 | ||
4622 | @item | |
4623 | If no suitable region could be found, or there was no previous | |
4624 | section then the LMA is set equal to the VMA. | |
4625 | @end itemize | |
252b5132 RH |
4626 | |
4627 | @cindex ROM initialized data | |
4628 | @cindex initialized data in ROM | |
4629 | This feature is designed to make it easy to build a ROM image. For | |
4630 | example, the following linker script creates three output sections: one | |
4631 | called @samp{.text}, which starts at @code{0x1000}, one called | |
4632 | @samp{.mdata}, which is loaded at the end of the @samp{.text} section | |
4633 | even though its VMA is @code{0x2000}, and one called @samp{.bss} to hold | |
4634 | uninitialized data at address @code{0x3000}. The symbol @code{_data} is | |
4635 | defined with the value @code{0x2000}, which shows that the location | |
4636 | counter holds the VMA value, not the LMA value. | |
4637 | ||
4638 | @smallexample | |
4639 | @group | |
4640 | SECTIONS | |
4641 | @{ | |
4642 | .text 0x1000 : @{ *(.text) _etext = . ; @} | |
a1ab1d2a | 4643 | .mdata 0x2000 : |
252b5132 RH |
4644 | AT ( ADDR (.text) + SIZEOF (.text) ) |
4645 | @{ _data = . ; *(.data); _edata = . ; @} | |
4646 | .bss 0x3000 : | |
4647 | @{ _bstart = . ; *(.bss) *(COMMON) ; _bend = . ;@} | |
4648 | @} | |
4649 | @end group | |
4650 | @end smallexample | |
4651 | ||
4652 | The run-time initialization code for use with a program generated with | |
4653 | this linker script would include something like the following, to copy | |
4654 | the initialized data from the ROM image to its runtime address. Notice | |
4655 | how this code takes advantage of the symbols defined by the linker | |
4656 | script. | |
4657 | ||
4658 | @smallexample | |
4659 | @group | |
4660 | extern char _etext, _data, _edata, _bstart, _bend; | |
4661 | char *src = &_etext; | |
4662 | char *dst = &_data; | |
4663 | ||
ea5cae92 NC |
4664 | /* ROM has data at end of text; copy it. */ |
4665 | while (dst < &_edata) | |
252b5132 | 4666 | *dst++ = *src++; |
252b5132 | 4667 | |
ea5cae92 | 4668 | /* Zero bss. */ |
252b5132 RH |
4669 | for (dst = &_bstart; dst< &_bend; dst++) |
4670 | *dst = 0; | |
4671 | @end group | |
4672 | @end smallexample | |
4673 | ||
bbf115d3 L |
4674 | @node Forced Output Alignment |
4675 | @subsubsection Forced Output Alignment | |
4676 | @kindex ALIGN(@var{section_align}) | |
4677 | @cindex forcing output section alignment | |
4678 | @cindex output section alignment | |
1eec346e | 4679 | You can increase an output section's alignment by using ALIGN. As an |
13075d04 SH |
4680 | alternative you can enforce that the difference between the VMA and LMA remains |
4681 | intact throughout this output section with the ALIGN_WITH_INPUT attribute. | |
bbf115d3 | 4682 | |
7e7d5768 AM |
4683 | @node Forced Input Alignment |
4684 | @subsubsection Forced Input Alignment | |
4685 | @kindex SUBALIGN(@var{subsection_align}) | |
4686 | @cindex forcing input section alignment | |
4687 | @cindex input section alignment | |
4688 | You can force input section alignment within an output section by using | |
4689 | SUBALIGN. The value specified overrides any alignment given by input | |
4690 | sections, whether larger or smaller. | |
4691 | ||
0c71d759 NC |
4692 | @node Output Section Constraint |
4693 | @subsubsection Output Section Constraint | |
4694 | @kindex ONLY_IF_RO | |
4695 | @kindex ONLY_IF_RW | |
4696 | @cindex constraints on output sections | |
4697 | You can specify that an output section should only be created if all | |
4698 | of its input sections are read-only or all of its input sections are | |
4699 | read-write by using the keyword @code{ONLY_IF_RO} and | |
4700 | @code{ONLY_IF_RW} respectively. | |
4701 | ||
252b5132 | 4702 | @node Output Section Region |
36f63dca | 4703 | @subsubsection Output Section Region |
252b5132 RH |
4704 | @kindex >@var{region} |
4705 | @cindex section, assigning to memory region | |
4706 | @cindex memory regions and sections | |
4707 | You can assign a section to a previously defined region of memory by | |
4708 | using @samp{>@var{region}}. @xref{MEMORY}. | |
4709 | ||
4710 | Here is a simple example: | |
4711 | @smallexample | |
4712 | @group | |
4713 | MEMORY @{ rom : ORIGIN = 0x1000, LENGTH = 0x1000 @} | |
4714 | SECTIONS @{ ROM : @{ *(.text) @} >rom @} | |
4715 | @end group | |
4716 | @end smallexample | |
4717 | ||
4718 | @node Output Section Phdr | |
36f63dca | 4719 | @subsubsection Output Section Phdr |
252b5132 RH |
4720 | @kindex :@var{phdr} |
4721 | @cindex section, assigning to program header | |
4722 | @cindex program headers and sections | |
4723 | You can assign a section to a previously defined program segment by | |
4724 | using @samp{:@var{phdr}}. @xref{PHDRS}. If a section is assigned to | |
4725 | one or more segments, then all subsequent allocated sections will be | |
4726 | assigned to those segments as well, unless they use an explicitly | |
4727 | @code{:@var{phdr}} modifier. You can use @code{:NONE} to tell the | |
4728 | linker to not put the section in any segment at all. | |
4729 | ||
4730 | Here is a simple example: | |
4731 | @smallexample | |
4732 | @group | |
4733 | PHDRS @{ text PT_LOAD ; @} | |
4734 | SECTIONS @{ .text : @{ *(.text) @} :text @} | |
4735 | @end group | |
4736 | @end smallexample | |
4737 | ||
4738 | @node Output Section Fill | |
36f63dca | 4739 | @subsubsection Output Section Fill |
252b5132 RH |
4740 | @kindex =@var{fillexp} |
4741 | @cindex section fill pattern | |
4742 | @cindex fill pattern, entire section | |
4743 | You can set the fill pattern for an entire section by using | |
4744 | @samp{=@var{fillexp}}. @var{fillexp} is an expression | |
4745 | (@pxref{Expressions}). Any otherwise unspecified regions of memory | |
4746 | within the output section (for example, gaps left due to the required | |
a139d329 AM |
4747 | alignment of input sections) will be filled with the value, repeated as |
4748 | necessary. If the fill expression is a simple hex number, ie. a string | |
9673c93c | 4749 | of hex digit starting with @samp{0x} and without a trailing @samp{k} or @samp{M}, then |
a139d329 AM |
4750 | an arbitrarily long sequence of hex digits can be used to specify the |
4751 | fill pattern; Leading zeros become part of the pattern too. For all | |
9673c93c | 4752 | other cases, including extra parentheses or a unary @code{+}, the fill |
a139d329 AM |
4753 | pattern is the four least significant bytes of the value of the |
4754 | expression. In all cases, the number is big-endian. | |
252b5132 RH |
4755 | |
4756 | You can also change the fill value with a @code{FILL} command in the | |
9673c93c | 4757 | output section commands; (@pxref{Output Section Data}). |
252b5132 RH |
4758 | |
4759 | Here is a simple example: | |
4760 | @smallexample | |
4761 | @group | |
563e308f | 4762 | SECTIONS @{ .text : @{ *(.text) @} =0x90909090 @} |
252b5132 RH |
4763 | @end group |
4764 | @end smallexample | |
4765 | ||
4766 | @node Overlay Description | |
36f63dca | 4767 | @subsection Overlay Description |
252b5132 RH |
4768 | @kindex OVERLAY |
4769 | @cindex overlays | |
4770 | An overlay description provides an easy way to describe sections which | |
4771 | are to be loaded as part of a single memory image but are to be run at | |
4772 | the same memory address. At run time, some sort of overlay manager will | |
4773 | copy the overlaid sections in and out of the runtime memory address as | |
4774 | required, perhaps by simply manipulating addressing bits. This approach | |
4775 | can be useful, for example, when a certain region of memory is faster | |
4776 | than another. | |
4777 | ||
4778 | Overlays are described using the @code{OVERLAY} command. The | |
4779 | @code{OVERLAY} command is used within a @code{SECTIONS} command, like an | |
4780 | output section description. The full syntax of the @code{OVERLAY} | |
4781 | command is as follows: | |
4782 | @smallexample | |
4783 | @group | |
4784 | OVERLAY [@var{start}] : [NOCROSSREFS] [AT ( @var{ldaddr} )] | |
4785 | @{ | |
4786 | @var{secname1} | |
4787 | @{ | |
4788 | @var{output-section-command} | |
4789 | @var{output-section-command} | |
4790 | @dots{} | |
4791 | @} [:@var{phdr}@dots{}] [=@var{fill}] | |
4792 | @var{secname2} | |
4793 | @{ | |
4794 | @var{output-section-command} | |
4795 | @var{output-section-command} | |
4796 | @dots{} | |
4797 | @} [:@var{phdr}@dots{}] [=@var{fill}] | |
4798 | @dots{} | |
abc9061b | 4799 | @} [>@var{region}] [:@var{phdr}@dots{}] [=@var{fill}] [,] |
252b5132 RH |
4800 | @end group |
4801 | @end smallexample | |
4802 | ||
4803 | Everything is optional except @code{OVERLAY} (a keyword), and each | |
4804 | section must have a name (@var{secname1} and @var{secname2} above). The | |
4805 | section definitions within the @code{OVERLAY} construct are identical to | |
11e7fd74 | 4806 | those within the general @code{SECTIONS} construct (@pxref{SECTIONS}), |
252b5132 RH |
4807 | except that no addresses and no memory regions may be defined for |
4808 | sections within an @code{OVERLAY}. | |
4809 | ||
abc9061b CC |
4810 | The comma at the end may be required if a @var{fill} is used and |
4811 | the next @var{sections-command} looks like a continuation of the expression. | |
4812 | ||
252b5132 RH |
4813 | The sections are all defined with the same starting address. The load |
4814 | addresses of the sections are arranged such that they are consecutive in | |
4815 | memory starting at the load address used for the @code{OVERLAY} as a | |
4816 | whole (as with normal section definitions, the load address is optional, | |
4817 | and defaults to the start address; the start address is also optional, | |
4818 | and defaults to the current value of the location counter). | |
4819 | ||
56dd11f0 NC |
4820 | If the @code{NOCROSSREFS} keyword is used, and there are any |
4821 | references among the sections, the linker will report an error. Since | |
4822 | the sections all run at the same address, it normally does not make | |
4823 | sense for one section to refer directly to another. | |
4824 | @xref{Miscellaneous Commands, NOCROSSREFS}. | |
252b5132 RH |
4825 | |
4826 | For each section within the @code{OVERLAY}, the linker automatically | |
34711ca3 | 4827 | provides two symbols. The symbol @code{__load_start_@var{secname}} is |
252b5132 RH |
4828 | defined as the starting load address of the section. The symbol |
4829 | @code{__load_stop_@var{secname}} is defined as the final load address of | |
4830 | the section. Any characters within @var{secname} which are not legal | |
4831 | within C identifiers are removed. C (or assembler) code may use these | |
4832 | symbols to move the overlaid sections around as necessary. | |
4833 | ||
4834 | At the end of the overlay, the value of the location counter is set to | |
4835 | the start address of the overlay plus the size of the largest section. | |
4836 | ||
4837 | Here is an example. Remember that this would appear inside a | |
4838 | @code{SECTIONS} construct. | |
4839 | @smallexample | |
4840 | @group | |
4841 | OVERLAY 0x1000 : AT (0x4000) | |
4842 | @{ | |
4843 | .text0 @{ o1/*.o(.text) @} | |
4844 | .text1 @{ o2/*.o(.text) @} | |
4845 | @} | |
4846 | @end group | |
4847 | @end smallexample | |
4848 | @noindent | |
4849 | This will define both @samp{.text0} and @samp{.text1} to start at | |
4850 | address 0x1000. @samp{.text0} will be loaded at address 0x4000, and | |
4851 | @samp{.text1} will be loaded immediately after @samp{.text0}. The | |
34711ca3 | 4852 | following symbols will be defined if referenced: @code{__load_start_text0}, |
252b5132 RH |
4853 | @code{__load_stop_text0}, @code{__load_start_text1}, |
4854 | @code{__load_stop_text1}. | |
4855 | ||
4856 | C code to copy overlay @code{.text1} into the overlay area might look | |
4857 | like the following. | |
4858 | ||
4859 | @smallexample | |
4860 | @group | |
4861 | extern char __load_start_text1, __load_stop_text1; | |
4862 | memcpy ((char *) 0x1000, &__load_start_text1, | |
4863 | &__load_stop_text1 - &__load_start_text1); | |
4864 | @end group | |
4865 | @end smallexample | |
4866 | ||
4867 | Note that the @code{OVERLAY} command is just syntactic sugar, since | |
4868 | everything it does can be done using the more basic commands. The above | |
4869 | example could have been written identically as follows. | |
4870 | ||
4871 | @smallexample | |
4872 | @group | |
4873 | .text0 0x1000 : AT (0x4000) @{ o1/*.o(.text) @} | |
34711ca3 AM |
4874 | PROVIDE (__load_start_text0 = LOADADDR (.text0)); |
4875 | PROVIDE (__load_stop_text0 = LOADADDR (.text0) + SIZEOF (.text0)); | |
252b5132 | 4876 | .text1 0x1000 : AT (0x4000 + SIZEOF (.text0)) @{ o2/*.o(.text) @} |
34711ca3 AM |
4877 | PROVIDE (__load_start_text1 = LOADADDR (.text1)); |
4878 | PROVIDE (__load_stop_text1 = LOADADDR (.text1) + SIZEOF (.text1)); | |
252b5132 RH |
4879 | . = 0x1000 + MAX (SIZEOF (.text0), SIZEOF (.text1)); |
4880 | @end group | |
4881 | @end smallexample | |
4882 | ||
4883 | @node MEMORY | |
36f63dca | 4884 | @section MEMORY Command |
252b5132 RH |
4885 | @kindex MEMORY |
4886 | @cindex memory regions | |
4887 | @cindex regions of memory | |
4888 | @cindex allocating memory | |
4889 | @cindex discontinuous memory | |
4890 | The linker's default configuration permits allocation of all available | |
4891 | memory. You can override this by using the @code{MEMORY} command. | |
4892 | ||
4893 | The @code{MEMORY} command describes the location and size of blocks of | |
4894 | memory in the target. You can use it to describe which memory regions | |
4895 | may be used by the linker, and which memory regions it must avoid. You | |
4896 | can then assign sections to particular memory regions. The linker will | |
4897 | set section addresses based on the memory regions, and will warn about | |
4898 | regions that become too full. The linker will not shuffle sections | |
4899 | around to fit into the available regions. | |
4900 | ||
4901 | A linker script may contain at most one use of the @code{MEMORY} | |
4902 | command. However, you can define as many blocks of memory within it as | |
4903 | you wish. The syntax is: | |
4904 | @smallexample | |
4905 | @group | |
a1ab1d2a | 4906 | MEMORY |
252b5132 RH |
4907 | @{ |
4908 | @var{name} [(@var{attr})] : ORIGIN = @var{origin}, LENGTH = @var{len} | |
4909 | @dots{} | |
4910 | @} | |
4911 | @end group | |
4912 | @end smallexample | |
4913 | ||
4914 | The @var{name} is a name used in the linker script to refer to the | |
4915 | region. The region name has no meaning outside of the linker script. | |
4916 | Region names are stored in a separate name space, and will not conflict | |
4917 | with symbol names, file names, or section names. Each memory region | |
4a93e180 NC |
4918 | must have a distinct name within the @code{MEMORY} command. However you can |
4919 | add later alias names to existing memory regions with the @ref{REGION_ALIAS} | |
9d5777a3 | 4920 | command. |
252b5132 RH |
4921 | |
4922 | @cindex memory region attributes | |
4923 | The @var{attr} string is an optional list of attributes that specify | |
4924 | whether to use a particular memory region for an input section which is | |
4925 | not explicitly mapped in the linker script. As described in | |
4926 | @ref{SECTIONS}, if you do not specify an output section for some input | |
4927 | section, the linker will create an output section with the same name as | |
4928 | the input section. If you define region attributes, the linker will use | |
4929 | them to select the memory region for the output section that it creates. | |
4930 | ||
4931 | The @var{attr} string must consist only of the following characters: | |
4932 | @table @samp | |
4933 | @item R | |
4934 | Read-only section | |
4935 | @item W | |
4936 | Read/write section | |
4937 | @item X | |
4938 | Executable section | |
4939 | @item A | |
4940 | Allocatable section | |
4941 | @item I | |
4942 | Initialized section | |
4943 | @item L | |
4944 | Same as @samp{I} | |
4945 | @item ! | |
c09e9a8c | 4946 | Invert the sense of any of the attributes that follow |
252b5132 RH |
4947 | @end table |
4948 | ||
4949 | If a unmapped section matches any of the listed attributes other than | |
4950 | @samp{!}, it will be placed in the memory region. The @samp{!} | |
4951 | attribute reverses this test, so that an unmapped section will be placed | |
4952 | in the memory region only if it does not match any of the listed | |
4953 | attributes. | |
4954 | ||
4955 | @kindex ORIGIN = | |
4956 | @kindex o = | |
4957 | @kindex org = | |
9cd6d51a NC |
4958 | The @var{origin} is an numerical expression for the start address of |
4959 | the memory region. The expression must evaluate to a constant and it | |
4960 | cannot involve any symbols. The keyword @code{ORIGIN} may be | |
4961 | abbreviated to @code{org} or @code{o} (but not, for example, | |
4962 | @code{ORG}). | |
252b5132 RH |
4963 | |
4964 | @kindex LENGTH = | |
4965 | @kindex len = | |
4966 | @kindex l = | |
4967 | The @var{len} is an expression for the size in bytes of the memory | |
4968 | region. As with the @var{origin} expression, the expression must | |
9cd6d51a NC |
4969 | be numerical only and must evaluate to a constant. The keyword |
4970 | @code{LENGTH} may be abbreviated to @code{len} or @code{l}. | |
252b5132 RH |
4971 | |
4972 | In the following example, we specify that there are two memory regions | |
4973 | available for allocation: one starting at @samp{0} for 256 kilobytes, | |
4974 | and the other starting at @samp{0x40000000} for four megabytes. The | |
4975 | linker will place into the @samp{rom} memory region every section which | |
4976 | is not explicitly mapped into a memory region, and is either read-only | |
4977 | or executable. The linker will place other sections which are not | |
4978 | explicitly mapped into a memory region into the @samp{ram} memory | |
4979 | region. | |
4980 | ||
4981 | @smallexample | |
4982 | @group | |
a1ab1d2a | 4983 | MEMORY |
252b5132 RH |
4984 | @{ |
4985 | rom (rx) : ORIGIN = 0, LENGTH = 256K | |
4986 | ram (!rx) : org = 0x40000000, l = 4M | |
4987 | @} | |
4988 | @end group | |
4989 | @end smallexample | |
4990 | ||
4991 | Once you define a memory region, you can direct the linker to place | |
4992 | specific output sections into that memory region by using the | |
4993 | @samp{>@var{region}} output section attribute. For example, if you have | |
4994 | a memory region named @samp{mem}, you would use @samp{>mem} in the | |
4995 | output section definition. @xref{Output Section Region}. If no address | |
4996 | was specified for the output section, the linker will set the address to | |
4997 | the next available address within the memory region. If the combined | |
4998 | output sections directed to a memory region are too large for the | |
4999 | region, the linker will issue an error message. | |
5000 | ||
3ec57632 | 5001 | It is possible to access the origin and length of a memory in an |
c0065db7 | 5002 | expression via the @code{ORIGIN(@var{memory})} and |
3ec57632 NC |
5003 | @code{LENGTH(@var{memory})} functions: |
5004 | ||
5005 | @smallexample | |
5006 | @group | |
c0065db7 | 5007 | _fstack = ORIGIN(ram) + LENGTH(ram) - 4; |
3ec57632 NC |
5008 | @end group |
5009 | @end smallexample | |
5010 | ||
252b5132 RH |
5011 | @node PHDRS |
5012 | @section PHDRS Command | |
5013 | @kindex PHDRS | |
5014 | @cindex program headers | |
5015 | @cindex ELF program headers | |
5016 | @cindex program segments | |
5017 | @cindex segments, ELF | |
5018 | The ELF object file format uses @dfn{program headers}, also knows as | |
5019 | @dfn{segments}. The program headers describe how the program should be | |
5020 | loaded into memory. You can print them out by using the @code{objdump} | |
5021 | program with the @samp{-p} option. | |
5022 | ||
5023 | When you run an ELF program on a native ELF system, the system loader | |
5024 | reads the program headers in order to figure out how to load the | |
5025 | program. This will only work if the program headers are set correctly. | |
5026 | This manual does not describe the details of how the system loader | |
5027 | interprets program headers; for more information, see the ELF ABI. | |
5028 | ||
5029 | The linker will create reasonable program headers by default. However, | |
5030 | in some cases, you may need to specify the program headers more | |
5031 | precisely. You may use the @code{PHDRS} command for this purpose. When | |
5032 | the linker sees the @code{PHDRS} command in the linker script, it will | |
5033 | not create any program headers other than the ones specified. | |
5034 | ||
5035 | The linker only pays attention to the @code{PHDRS} command when | |
5036 | generating an ELF output file. In other cases, the linker will simply | |
5037 | ignore @code{PHDRS}. | |
5038 | ||
5039 | This is the syntax of the @code{PHDRS} command. The words @code{PHDRS}, | |
5040 | @code{FILEHDR}, @code{AT}, and @code{FLAGS} are keywords. | |
5041 | ||
5042 | @smallexample | |
5043 | @group | |
5044 | PHDRS | |
5045 | @{ | |
5046 | @var{name} @var{type} [ FILEHDR ] [ PHDRS ] [ AT ( @var{address} ) ] | |
5047 | [ FLAGS ( @var{flags} ) ] ; | |
5048 | @} | |
5049 | @end group | |
5050 | @end smallexample | |
5051 | ||
5052 | The @var{name} is used only for reference in the @code{SECTIONS} command | |
5053 | of the linker script. It is not put into the output file. Program | |
5054 | header names are stored in a separate name space, and will not conflict | |
5055 | with symbol names, file names, or section names. Each program header | |
5c1a3f0f NS |
5056 | must have a distinct name. The headers are processed in order and it |
5057 | is usual for them to map to sections in ascending load address order. | |
252b5132 RH |
5058 | |
5059 | Certain program header types describe segments of memory which the | |
5060 | system loader will load from the file. In the linker script, you | |
5061 | specify the contents of these segments by placing allocatable output | |
5062 | sections in the segments. You use the @samp{:@var{phdr}} output section | |
5063 | attribute to place a section in a particular segment. @xref{Output | |
5064 | Section Phdr}. | |
5065 | ||
5066 | It is normal to put certain sections in more than one segment. This | |
5067 | merely implies that one segment of memory contains another. You may | |
5068 | repeat @samp{:@var{phdr}}, using it once for each segment which should | |
5069 | contain the section. | |
5070 | ||
5071 | If you place a section in one or more segments using @samp{:@var{phdr}}, | |
5072 | then the linker will place all subsequent allocatable sections which do | |
5073 | not specify @samp{:@var{phdr}} in the same segments. This is for | |
5074 | convenience, since generally a whole set of contiguous sections will be | |
5075 | placed in a single segment. You can use @code{:NONE} to override the | |
5076 | default segment and tell the linker to not put the section in any | |
5077 | segment at all. | |
5078 | ||
5079 | @kindex FILEHDR | |
5080 | @kindex PHDRS | |
5c1a3f0f | 5081 | You may use the @code{FILEHDR} and @code{PHDRS} keywords after |
252b5132 RH |
5082 | the program header type to further describe the contents of the segment. |
5083 | The @code{FILEHDR} keyword means that the segment should include the ELF | |
5084 | file header. The @code{PHDRS} keyword means that the segment should | |
5c1a3f0f | 5085 | include the ELF program headers themselves. If applied to a loadable |
4100cea3 AM |
5086 | segment (@code{PT_LOAD}), all prior loadable segments must have one of |
5087 | these keywords. | |
252b5132 RH |
5088 | |
5089 | The @var{type} may be one of the following. The numbers indicate the | |
5090 | value of the keyword. | |
5091 | ||
5092 | @table @asis | |
5093 | @item @code{PT_NULL} (0) | |
5094 | Indicates an unused program header. | |
5095 | ||
5096 | @item @code{PT_LOAD} (1) | |
5097 | Indicates that this program header describes a segment to be loaded from | |
5098 | the file. | |
5099 | ||
5100 | @item @code{PT_DYNAMIC} (2) | |
5101 | Indicates a segment where dynamic linking information can be found. | |
5102 | ||
5103 | @item @code{PT_INTERP} (3) | |
5104 | Indicates a segment where the name of the program interpreter may be | |
5105 | found. | |
5106 | ||
5107 | @item @code{PT_NOTE} (4) | |
5108 | Indicates a segment holding note information. | |
5109 | ||
5110 | @item @code{PT_SHLIB} (5) | |
5111 | A reserved program header type, defined but not specified by the ELF | |
5112 | ABI. | |
5113 | ||
5114 | @item @code{PT_PHDR} (6) | |
5115 | Indicates a segment where the program headers may be found. | |
5116 | ||
5117 | @item @var{expression} | |
5118 | An expression giving the numeric type of the program header. This may | |
5119 | be used for types not defined above. | |
5120 | @end table | |
5121 | ||
5122 | You can specify that a segment should be loaded at a particular address | |
5123 | in memory by using an @code{AT} expression. This is identical to the | |
5124 | @code{AT} command used as an output section attribute (@pxref{Output | |
5125 | Section LMA}). The @code{AT} command for a program header overrides the | |
5126 | output section attribute. | |
5127 | ||
5128 | The linker will normally set the segment flags based on the sections | |
5129 | which comprise the segment. You may use the @code{FLAGS} keyword to | |
5130 | explicitly specify the segment flags. The value of @var{flags} must be | |
5131 | an integer. It is used to set the @code{p_flags} field of the program | |
5132 | header. | |
5133 | ||
5134 | Here is an example of @code{PHDRS}. This shows a typical set of program | |
5135 | headers used on a native ELF system. | |
5136 | ||
5137 | @example | |
5138 | @group | |
5139 | PHDRS | |
5140 | @{ | |
5141 | headers PT_PHDR PHDRS ; | |
5142 | interp PT_INTERP ; | |
5143 | text PT_LOAD FILEHDR PHDRS ; | |
5144 | data PT_LOAD ; | |
5145 | dynamic PT_DYNAMIC ; | |
5146 | @} | |
5147 | ||
5148 | SECTIONS | |
5149 | @{ | |
5150 | . = SIZEOF_HEADERS; | |
5151 | .interp : @{ *(.interp) @} :text :interp | |
5152 | .text : @{ *(.text) @} :text | |
5153 | .rodata : @{ *(.rodata) @} /* defaults to :text */ | |
5154 | @dots{} | |
5155 | . = . + 0x1000; /* move to a new page in memory */ | |
5156 | .data : @{ *(.data) @} :data | |
5157 | .dynamic : @{ *(.dynamic) @} :data :dynamic | |
5158 | @dots{} | |
5159 | @} | |
5160 | @end group | |
5161 | @end example | |
5162 | ||
5163 | @node VERSION | |
5164 | @section VERSION Command | |
5165 | @kindex VERSION @{script text@} | |
5166 | @cindex symbol versions | |
5167 | @cindex version script | |
5168 | @cindex versions of symbols | |
5169 | The linker supports symbol versions when using ELF. Symbol versions are | |
5170 | only useful when using shared libraries. The dynamic linker can use | |
5171 | symbol versions to select a specific version of a function when it runs | |
5172 | a program that may have been linked against an earlier version of the | |
5173 | shared library. | |
5174 | ||
5175 | You can include a version script directly in the main linker script, or | |
5176 | you can supply the version script as an implicit linker script. You can | |
5177 | also use the @samp{--version-script} linker option. | |
5178 | ||
5179 | The syntax of the @code{VERSION} command is simply | |
5180 | @smallexample | |
5181 | VERSION @{ version-script-commands @} | |
5182 | @end smallexample | |
5183 | ||
5184 | The format of the version script commands is identical to that used by | |
5185 | Sun's linker in Solaris 2.5. The version script defines a tree of | |
5186 | version nodes. You specify the node names and interdependencies in the | |
5187 | version script. You can specify which symbols are bound to which | |
5188 | version nodes, and you can reduce a specified set of symbols to local | |
5189 | scope so that they are not globally visible outside of the shared | |
5190 | library. | |
5191 | ||
5192 | The easiest way to demonstrate the version script language is with a few | |
5193 | examples. | |
5194 | ||
5195 | @smallexample | |
5196 | VERS_1.1 @{ | |
5197 | global: | |
5198 | foo1; | |
5199 | local: | |
a1ab1d2a UD |
5200 | old*; |
5201 | original*; | |
5202 | new*; | |
252b5132 RH |
5203 | @}; |
5204 | ||
5205 | VERS_1.2 @{ | |
5206 | foo2; | |
5207 | @} VERS_1.1; | |
5208 | ||
5209 | VERS_2.0 @{ | |
5210 | bar1; bar2; | |
c0065db7 | 5211 | extern "C++" @{ |
86043bbb | 5212 | ns::*; |
bb1515f2 MF |
5213 | "f(int, double)"; |
5214 | @}; | |
252b5132 RH |
5215 | @} VERS_1.2; |
5216 | @end smallexample | |
5217 | ||
5218 | This example version script defines three version nodes. The first | |
5219 | version node defined is @samp{VERS_1.1}; it has no other dependencies. | |
5220 | The script binds the symbol @samp{foo1} to @samp{VERS_1.1}. It reduces | |
5221 | a number of symbols to local scope so that they are not visible outside | |
313e35ee AM |
5222 | of the shared library; this is done using wildcard patterns, so that any |
5223 | symbol whose name begins with @samp{old}, @samp{original}, or @samp{new} | |
5224 | is matched. The wildcard patterns available are the same as those used | |
5225 | in the shell when matching filenames (also known as ``globbing''). | |
86043bbb MM |
5226 | However, if you specify the symbol name inside double quotes, then the |
5227 | name is treated as literal, rather than as a glob pattern. | |
252b5132 RH |
5228 | |
5229 | Next, the version script defines node @samp{VERS_1.2}. This node | |
5230 | depends upon @samp{VERS_1.1}. The script binds the symbol @samp{foo2} | |
5231 | to the version node @samp{VERS_1.2}. | |
5232 | ||
5233 | Finally, the version script defines node @samp{VERS_2.0}. This node | |
5234 | depends upon @samp{VERS_1.2}. The scripts binds the symbols @samp{bar1} | |
5235 | and @samp{bar2} are bound to the version node @samp{VERS_2.0}. | |
5236 | ||
5237 | When the linker finds a symbol defined in a library which is not | |
5238 | specifically bound to a version node, it will effectively bind it to an | |
5239 | unspecified base version of the library. You can bind all otherwise | |
a981ed6f | 5240 | unspecified symbols to a given version node by using @samp{global: *;} |
ae5a3597 AM |
5241 | somewhere in the version script. Note that it's slightly crazy to use |
5242 | wildcards in a global spec except on the last version node. Global | |
5243 | wildcards elsewhere run the risk of accidentally adding symbols to the | |
5244 | set exported for an old version. That's wrong since older versions | |
5245 | ought to have a fixed set of symbols. | |
252b5132 RH |
5246 | |
5247 | The names of the version nodes have no specific meaning other than what | |
5248 | they might suggest to the person reading them. The @samp{2.0} version | |
5249 | could just as well have appeared in between @samp{1.1} and @samp{1.2}. | |
5250 | However, this would be a confusing way to write a version script. | |
5251 | ||
0f6bf451 | 5252 | Node name can be omitted, provided it is the only version node |
6b9b879a JJ |
5253 | in the version script. Such version script doesn't assign any versions to |
5254 | symbols, only selects which symbols will be globally visible out and which | |
5255 | won't. | |
5256 | ||
5257 | @smallexample | |
7c9c73be | 5258 | @{ global: foo; bar; local: *; @}; |
9d201f2f | 5259 | @end smallexample |
6b9b879a | 5260 | |
252b5132 RH |
5261 | When you link an application against a shared library that has versioned |
5262 | symbols, the application itself knows which version of each symbol it | |
5263 | requires, and it also knows which version nodes it needs from each | |
5264 | shared library it is linked against. Thus at runtime, the dynamic | |
5265 | loader can make a quick check to make sure that the libraries you have | |
5266 | linked against do in fact supply all of the version nodes that the | |
5267 | application will need to resolve all of the dynamic symbols. In this | |
5268 | way it is possible for the dynamic linker to know with certainty that | |
5269 | all external symbols that it needs will be resolvable without having to | |
5270 | search for each symbol reference. | |
5271 | ||
5272 | The symbol versioning is in effect a much more sophisticated way of | |
5273 | doing minor version checking that SunOS does. The fundamental problem | |
5274 | that is being addressed here is that typically references to external | |
5275 | functions are bound on an as-needed basis, and are not all bound when | |
5276 | the application starts up. If a shared library is out of date, a | |
5277 | required interface may be missing; when the application tries to use | |
5278 | that interface, it may suddenly and unexpectedly fail. With symbol | |
5279 | versioning, the user will get a warning when they start their program if | |
5280 | the libraries being used with the application are too old. | |
5281 | ||
5282 | There are several GNU extensions to Sun's versioning approach. The | |
5283 | first of these is the ability to bind a symbol to a version node in the | |
5284 | source file where the symbol is defined instead of in the versioning | |
5285 | script. This was done mainly to reduce the burden on the library | |
5286 | maintainer. You can do this by putting something like: | |
5287 | @smallexample | |
5288 | __asm__(".symver original_foo,foo@@VERS_1.1"); | |
5289 | @end smallexample | |
5290 | @noindent | |
5291 | in the C source file. This renames the function @samp{original_foo} to | |
5292 | be an alias for @samp{foo} bound to the version node @samp{VERS_1.1}. | |
5293 | The @samp{local:} directive can be used to prevent the symbol | |
96a94295 L |
5294 | @samp{original_foo} from being exported. A @samp{.symver} directive |
5295 | takes precedence over a version script. | |
252b5132 RH |
5296 | |
5297 | The second GNU extension is to allow multiple versions of the same | |
5298 | function to appear in a given shared library. In this way you can make | |
5299 | an incompatible change to an interface without increasing the major | |
5300 | version number of the shared library, while still allowing applications | |
5301 | linked against the old interface to continue to function. | |
5302 | ||
5303 | To do this, you must use multiple @samp{.symver} directives in the | |
5304 | source file. Here is an example: | |
5305 | ||
5306 | @smallexample | |
5307 | __asm__(".symver original_foo,foo@@"); | |
5308 | __asm__(".symver old_foo,foo@@VERS_1.1"); | |
5309 | __asm__(".symver old_foo1,foo@@VERS_1.2"); | |
5310 | __asm__(".symver new_foo,foo@@@@VERS_2.0"); | |
5311 | @end smallexample | |
5312 | ||
5313 | In this example, @samp{foo@@} represents the symbol @samp{foo} bound to the | |
5314 | unspecified base version of the symbol. The source file that contains this | |
5315 | example would define 4 C functions: @samp{original_foo}, @samp{old_foo}, | |
5316 | @samp{old_foo1}, and @samp{new_foo}. | |
5317 | ||
5318 | When you have multiple definitions of a given symbol, there needs to be | |
5319 | some way to specify a default version to which external references to | |
5320 | this symbol will be bound. You can do this with the | |
5321 | @samp{foo@@@@VERS_2.0} type of @samp{.symver} directive. You can only | |
5322 | declare one version of a symbol as the default in this manner; otherwise | |
5323 | you would effectively have multiple definitions of the same symbol. | |
5324 | ||
5325 | If you wish to bind a reference to a specific version of the symbol | |
5326 | within the shared library, you can use the aliases of convenience | |
36f63dca | 5327 | (i.e., @samp{old_foo}), or you can use the @samp{.symver} directive to |
252b5132 RH |
5328 | specifically bind to an external version of the function in question. |
5329 | ||
cb840a31 L |
5330 | You can also specify the language in the version script: |
5331 | ||
5332 | @smallexample | |
5333 | VERSION extern "lang" @{ version-script-commands @} | |
5334 | @end smallexample | |
5335 | ||
c0065db7 | 5336 | The supported @samp{lang}s are @samp{C}, @samp{C++}, and @samp{Java}. |
cb840a31 L |
5337 | The linker will iterate over the list of symbols at the link time and |
5338 | demangle them according to @samp{lang} before matching them to the | |
bb1515f2 MF |
5339 | patterns specified in @samp{version-script-commands}. The default |
5340 | @samp{lang} is @samp{C}. | |
cb840a31 | 5341 | |
86043bbb MM |
5342 | Demangled names may contains spaces and other special characters. As |
5343 | described above, you can use a glob pattern to match demangled names, | |
5344 | or you can use a double-quoted string to match the string exactly. In | |
5345 | the latter case, be aware that minor differences (such as differing | |
5346 | whitespace) between the version script and the demangler output will | |
5347 | cause a mismatch. As the exact string generated by the demangler | |
5348 | might change in the future, even if the mangled name does not, you | |
5349 | should check that all of your version directives are behaving as you | |
5350 | expect when you upgrade. | |
5351 | ||
252b5132 RH |
5352 | @node Expressions |
5353 | @section Expressions in Linker Scripts | |
5354 | @cindex expressions | |
5355 | @cindex arithmetic | |
5356 | The syntax for expressions in the linker script language is identical to | |
5357 | that of C expressions. All expressions are evaluated as integers. All | |
5358 | expressions are evaluated in the same size, which is 32 bits if both the | |
5359 | host and target are 32 bits, and is otherwise 64 bits. | |
5360 | ||
5361 | You can use and set symbol values in expressions. | |
5362 | ||
5363 | The linker defines several special purpose builtin functions for use in | |
5364 | expressions. | |
5365 | ||
5366 | @menu | |
5367 | * Constants:: Constants | |
0c71d759 | 5368 | * Symbolic Constants:: Symbolic constants |
252b5132 | 5369 | * Symbols:: Symbol Names |
ecca9871 | 5370 | * Orphan Sections:: Orphan Sections |
252b5132 RH |
5371 | * Location Counter:: The Location Counter |
5372 | * Operators:: Operators | |
5373 | * Evaluation:: Evaluation | |
5374 | * Expression Section:: The Section of an Expression | |
5375 | * Builtin Functions:: Builtin Functions | |
5376 | @end menu | |
5377 | ||
5378 | @node Constants | |
5379 | @subsection Constants | |
5380 | @cindex integer notation | |
5381 | @cindex constants in linker scripts | |
5382 | All constants are integers. | |
5383 | ||
5384 | As in C, the linker considers an integer beginning with @samp{0} to be | |
5385 | octal, and an integer beginning with @samp{0x} or @samp{0X} to be | |
8a308ae8 | 5386 | hexadecimal. Alternatively the linker accepts suffixes of @samp{h} or |
11e7fd74 | 5387 | @samp{H} for hexadecimal, @samp{o} or @samp{O} for octal, @samp{b} or |
8a308ae8 NC |
5388 | @samp{B} for binary and @samp{d} or @samp{D} for decimal. Any integer |
5389 | value without a prefix or a suffix is considered to be decimal. | |
252b5132 RH |
5390 | |
5391 | @cindex scaled integers | |
5392 | @cindex K and M integer suffixes | |
5393 | @cindex M and K integer suffixes | |
5394 | @cindex suffixes for integers | |
5395 | @cindex integer suffixes | |
5396 | In addition, you can use the suffixes @code{K} and @code{M} to scale a | |
5397 | constant by | |
5398 | @c TEXI2ROFF-KILL | |
36f63dca | 5399 | @ifnottex |
252b5132 RH |
5400 | @c END TEXI2ROFF-KILL |
5401 | @code{1024} or @code{1024*1024} | |
5402 | @c TEXI2ROFF-KILL | |
36f63dca | 5403 | @end ifnottex |
252b5132 RH |
5404 | @tex |
5405 | ${\rm 1024}$ or ${\rm 1024}^2$ | |
5406 | @end tex | |
5407 | @c END TEXI2ROFF-KILL | |
8a308ae8 NC |
5408 | respectively. For example, the following |
5409 | all refer to the same quantity: | |
5410 | ||
252b5132 | 5411 | @smallexample |
36f63dca NC |
5412 | _fourk_1 = 4K; |
5413 | _fourk_2 = 4096; | |
5414 | _fourk_3 = 0x1000; | |
8a308ae8 | 5415 | _fourk_4 = 10000o; |
252b5132 RH |
5416 | @end smallexample |
5417 | ||
8a308ae8 NC |
5418 | Note - the @code{K} and @code{M} suffixes cannot be used in |
5419 | conjunction with the base suffixes mentioned above. | |
5420 | ||
0c71d759 NC |
5421 | @node Symbolic Constants |
5422 | @subsection Symbolic Constants | |
5423 | @cindex symbolic constants | |
5424 | @kindex CONSTANT | |
5425 | It is possible to refer to target specific constants via the use of | |
5426 | the @code{CONSTANT(@var{name})} operator, where @var{name} is one of: | |
5427 | ||
5428 | @table @code | |
5429 | @item MAXPAGESIZE | |
5430 | @kindex MAXPAGESIZE | |
5431 | The target's maximum page size. | |
5432 | ||
5433 | @item COMMONPAGESIZE | |
5434 | @kindex COMMONPAGESIZE | |
5435 | The target's default page size. | |
5436 | @end table | |
5437 | ||
5438 | So for example: | |
5439 | ||
5440 | @smallexample | |
9d5777a3 | 5441 | .text ALIGN (CONSTANT (MAXPAGESIZE)) : @{ *(.text) @} |
0c71d759 NC |
5442 | @end smallexample |
5443 | ||
5444 | will create a text section aligned to the largest page boundary | |
5445 | supported by the target. | |
5446 | ||
252b5132 RH |
5447 | @node Symbols |
5448 | @subsection Symbol Names | |
5449 | @cindex symbol names | |
5450 | @cindex names | |
5451 | @cindex quoted symbol names | |
5452 | @kindex " | |
5453 | Unless quoted, symbol names start with a letter, underscore, or period | |
5454 | and may include letters, digits, underscores, periods, and hyphens. | |
5455 | Unquoted symbol names must not conflict with any keywords. You can | |
5456 | specify a symbol which contains odd characters or has the same name as a | |
5457 | keyword by surrounding the symbol name in double quotes: | |
5458 | @smallexample | |
36f63dca NC |
5459 | "SECTION" = 9; |
5460 | "with a space" = "also with a space" + 10; | |
252b5132 RH |
5461 | @end smallexample |
5462 | ||
5463 | Since symbols can contain many non-alphabetic characters, it is safest | |
5464 | to delimit symbols with spaces. For example, @samp{A-B} is one symbol, | |
5465 | whereas @samp{A - B} is an expression involving subtraction. | |
5466 | ||
ecca9871 L |
5467 | @node Orphan Sections |
5468 | @subsection Orphan Sections | |
5469 | @cindex orphan | |
5470 | Orphan sections are sections present in the input files which | |
5471 | are not explicitly placed into the output file by the linker | |
5472 | script. The linker will still copy these sections into the | |
5473 | output file, but it has to guess as to where they should be | |
5474 | placed. The linker uses a simple heuristic to do this. It | |
5475 | attempts to place orphan sections after non-orphan sections of the | |
5476 | same attribute, such as code vs data, loadable vs non-loadable, etc. | |
5477 | If there is not enough room to do this then it places | |
5478 | at the end of the file. | |
5479 | ||
5480 | For ELF targets, the attribute of the section includes section type as | |
5481 | well as section flag. | |
5482 | ||
41911f68 | 5483 | If an orphaned section's name is representable as a C identifier then |
a61ca861 | 5484 | the linker will automatically @pxref{PROVIDE} two symbols: |
9aec8434 | 5485 | __start_SECNAME and __stop_SECNAME, where SECNAME is the name of the |
41911f68 NC |
5486 | section. These indicate the start address and end address of the |
5487 | orphaned section respectively. Note: most section names are not | |
5488 | representable as C identifiers because they contain a @samp{.} | |
5489 | character. | |
5490 | ||
252b5132 RH |
5491 | @node Location Counter |
5492 | @subsection The Location Counter | |
5493 | @kindex . | |
5494 | @cindex dot | |
5495 | @cindex location counter | |
5496 | @cindex current output location | |
5497 | The special linker variable @dfn{dot} @samp{.} always contains the | |
5498 | current output location counter. Since the @code{.} always refers to a | |
5499 | location in an output section, it may only appear in an expression | |
5500 | within a @code{SECTIONS} command. The @code{.} symbol may appear | |
5501 | anywhere that an ordinary symbol is allowed in an expression. | |
5502 | ||
5503 | @cindex holes | |
5504 | Assigning a value to @code{.} will cause the location counter to be | |
5505 | moved. This may be used to create holes in the output section. The | |
dc0b6aa0 AM |
5506 | location counter may not be moved backwards inside an output section, |
5507 | and may not be moved backwards outside of an output section if so | |
5508 | doing creates areas with overlapping LMAs. | |
252b5132 RH |
5509 | |
5510 | @smallexample | |
5511 | SECTIONS | |
5512 | @{ | |
5513 | output : | |
5514 | @{ | |
5515 | file1(.text) | |
5516 | . = . + 1000; | |
5517 | file2(.text) | |
5518 | . += 1000; | |
5519 | file3(.text) | |
563e308f | 5520 | @} = 0x12345678; |
252b5132 RH |
5521 | @} |
5522 | @end smallexample | |
5523 | @noindent | |
5524 | In the previous example, the @samp{.text} section from @file{file1} is | |
5525 | located at the beginning of the output section @samp{output}. It is | |
5526 | followed by a 1000 byte gap. Then the @samp{.text} section from | |
5527 | @file{file2} appears, also with a 1000 byte gap following before the | |
563e308f | 5528 | @samp{.text} section from @file{file3}. The notation @samp{= 0x12345678} |
252b5132 RH |
5529 | specifies what data to write in the gaps (@pxref{Output Section Fill}). |
5530 | ||
5c6bbab8 NC |
5531 | @cindex dot inside sections |
5532 | Note: @code{.} actually refers to the byte offset from the start of the | |
5533 | current containing object. Normally this is the @code{SECTIONS} | |
69da35b5 | 5534 | statement, whose start address is 0, hence @code{.} can be used as an |
5c6bbab8 NC |
5535 | absolute address. If @code{.} is used inside a section description |
5536 | however, it refers to the byte offset from the start of that section, | |
5537 | not an absolute address. Thus in a script like this: | |
5538 | ||
5539 | @smallexample | |
5540 | SECTIONS | |
5541 | @{ | |
5542 | . = 0x100 | |
5543 | .text: @{ | |
5544 | *(.text) | |
5545 | . = 0x200 | |
5546 | @} | |
5547 | . = 0x500 | |
5548 | .data: @{ | |
5549 | *(.data) | |
5550 | . += 0x600 | |
5551 | @} | |
5552 | @} | |
5553 | @end smallexample | |
5554 | ||
5555 | The @samp{.text} section will be assigned a starting address of 0x100 | |
5556 | and a size of exactly 0x200 bytes, even if there is not enough data in | |
5557 | the @samp{.text} input sections to fill this area. (If there is too | |
5558 | much data, an error will be produced because this would be an attempt to | |
5559 | move @code{.} backwards). The @samp{.data} section will start at 0x500 | |
5560 | and it will have an extra 0x600 bytes worth of space after the end of | |
5561 | the values from the @samp{.data} input sections and before the end of | |
5562 | the @samp{.data} output section itself. | |
5563 | ||
b5666f2f AM |
5564 | @cindex dot outside sections |
5565 | Setting symbols to the value of the location counter outside of an | |
5566 | output section statement can result in unexpected values if the linker | |
5567 | needs to place orphan sections. For example, given the following: | |
5568 | ||
5569 | @smallexample | |
5570 | SECTIONS | |
5571 | @{ | |
5572 | start_of_text = . ; | |
5573 | .text: @{ *(.text) @} | |
5574 | end_of_text = . ; | |
5575 | ||
5576 | start_of_data = . ; | |
5577 | .data: @{ *(.data) @} | |
5578 | end_of_data = . ; | |
5579 | @} | |
5580 | @end smallexample | |
5581 | ||
5582 | If the linker needs to place some input section, e.g. @code{.rodata}, | |
5583 | not mentioned in the script, it might choose to place that section | |
5584 | between @code{.text} and @code{.data}. You might think the linker | |
5585 | should place @code{.rodata} on the blank line in the above script, but | |
5586 | blank lines are of no particular significance to the linker. As well, | |
5587 | the linker doesn't associate the above symbol names with their | |
5588 | sections. Instead, it assumes that all assignments or other | |
5589 | statements belong to the previous output section, except for the | |
5590 | special case of an assignment to @code{.}. I.e., the linker will | |
5591 | place the orphan @code{.rodata} section as if the script was written | |
5592 | as follows: | |
5593 | ||
5594 | @smallexample | |
5595 | SECTIONS | |
5596 | @{ | |
5597 | start_of_text = . ; | |
5598 | .text: @{ *(.text) @} | |
5599 | end_of_text = . ; | |
5600 | ||
5601 | start_of_data = . ; | |
5602 | .rodata: @{ *(.rodata) @} | |
5603 | .data: @{ *(.data) @} | |
5604 | end_of_data = . ; | |
5605 | @} | |
5606 | @end smallexample | |
5607 | ||
5608 | This may or may not be the script author's intention for the value of | |
5609 | @code{start_of_data}. One way to influence the orphan section | |
5610 | placement is to assign the location counter to itself, as the linker | |
5611 | assumes that an assignment to @code{.} is setting the start address of | |
5612 | a following output section and thus should be grouped with that | |
5613 | section. So you could write: | |
5614 | ||
5615 | @smallexample | |
5616 | SECTIONS | |
5617 | @{ | |
5618 | start_of_text = . ; | |
5619 | .text: @{ *(.text) @} | |
5620 | end_of_text = . ; | |
5621 | ||
5622 | . = . ; | |
5623 | start_of_data = . ; | |
5624 | .data: @{ *(.data) @} | |
5625 | end_of_data = . ; | |
5626 | @} | |
5627 | @end smallexample | |
5628 | ||
5629 | Now, the orphan @code{.rodata} section will be placed between | |
5630 | @code{end_of_text} and @code{start_of_data}. | |
5631 | ||
252b5132 RH |
5632 | @need 2000 |
5633 | @node Operators | |
5634 | @subsection Operators | |
5635 | @cindex operators for arithmetic | |
5636 | @cindex arithmetic operators | |
5637 | @cindex precedence in expressions | |
5638 | The linker recognizes the standard C set of arithmetic operators, with | |
5639 | the standard bindings and precedence levels: | |
5640 | @c TEXI2ROFF-KILL | |
36f63dca | 5641 | @ifnottex |
252b5132 RH |
5642 | @c END TEXI2ROFF-KILL |
5643 | @smallexample | |
5644 | precedence associativity Operators Notes | |
5645 | (highest) | |
5646 | 1 left ! - ~ (1) | |
5647 | 2 left * / % | |
5648 | 3 left + - | |
5649 | 4 left >> << | |
5650 | 5 left == != > < <= >= | |
5651 | 6 left & | |
5652 | 7 left | | |
5653 | 8 left && | |
5654 | 9 left || | |
5655 | 10 right ? : | |
5656 | 11 right &= += -= *= /= (2) | |
5657 | (lowest) | |
5658 | @end smallexample | |
5659 | Notes: | |
a1ab1d2a | 5660 | (1) Prefix operators |
252b5132 RH |
5661 | (2) @xref{Assignments}. |
5662 | @c TEXI2ROFF-KILL | |
36f63dca | 5663 | @end ifnottex |
252b5132 RH |
5664 | @tex |
5665 | \vskip \baselineskip | |
5666 | %"lispnarrowing" is the extra indent used generally for smallexample | |
5667 | \hskip\lispnarrowing\vbox{\offinterlineskip | |
5668 | \hrule | |
5669 | \halign | |
5670 | {\vrule#&\strut\hfil\ #\ \hfil&\vrule#&\strut\hfil\ #\ \hfil&\vrule#&\strut\hfil\ {\tt #}\ \hfil&\vrule#\cr | |
5671 | height2pt&\omit&&\omit&&\omit&\cr | |
5672 | &Precedence&& Associativity &&{\rm Operators}&\cr | |
5673 | height2pt&\omit&&\omit&&\omit&\cr | |
5674 | \noalign{\hrule} | |
5675 | height2pt&\omit&&\omit&&\omit&\cr | |
5676 | &highest&&&&&\cr | |
5677 | % '176 is tilde, '~' in tt font | |
a1ab1d2a | 5678 | &1&&left&&\qquad- \char'176\ !\qquad\dag&\cr |
252b5132 RH |
5679 | &2&&left&&* / \%&\cr |
5680 | &3&&left&&+ -&\cr | |
5681 | &4&&left&&>> <<&\cr | |
5682 | &5&&left&&== != > < <= >=&\cr | |
5683 | &6&&left&&\&&\cr | |
5684 | &7&&left&&|&\cr | |
5685 | &8&&left&&{\&\&}&\cr | |
5686 | &9&&left&&||&\cr | |
5687 | &10&&right&&? :&\cr | |
5688 | &11&&right&&\qquad\&= += -= *= /=\qquad\ddag&\cr | |
5689 | &lowest&&&&&\cr | |
5690 | height2pt&\omit&&\omit&&\omit&\cr} | |
5691 | \hrule} | |
5692 | @end tex | |
5693 | @iftex | |
5694 | { | |
5695 | @obeylines@parskip=0pt@parindent=0pt | |
5696 | @dag@quad Prefix operators. | |
5697 | @ddag@quad @xref{Assignments}. | |
5698 | } | |
5699 | @end iftex | |
5700 | @c END TEXI2ROFF-KILL | |
5701 | ||
5702 | @node Evaluation | |
5703 | @subsection Evaluation | |
5704 | @cindex lazy evaluation | |
5705 | @cindex expression evaluation order | |
5706 | The linker evaluates expressions lazily. It only computes the value of | |
5707 | an expression when absolutely necessary. | |
5708 | ||
5709 | The linker needs some information, such as the value of the start | |
5710 | address of the first section, and the origins and lengths of memory | |
5711 | regions, in order to do any linking at all. These values are computed | |
5712 | as soon as possible when the linker reads in the linker script. | |
5713 | ||
5714 | However, other values (such as symbol values) are not known or needed | |
5715 | until after storage allocation. Such values are evaluated later, when | |
5716 | other information (such as the sizes of output sections) is available | |
5717 | for use in the symbol assignment expression. | |
5718 | ||
5719 | The sizes of sections cannot be known until after allocation, so | |
5720 | assignments dependent upon these are not performed until after | |
5721 | allocation. | |
5722 | ||
5723 | Some expressions, such as those depending upon the location counter | |
5724 | @samp{.}, must be evaluated during section allocation. | |
5725 | ||
5726 | If the result of an expression is required, but the value is not | |
5727 | available, then an error results. For example, a script like the | |
5728 | following | |
5729 | @smallexample | |
5730 | @group | |
5731 | SECTIONS | |
5732 | @{ | |
a1ab1d2a | 5733 | .text 9+this_isnt_constant : |
252b5132 RH |
5734 | @{ *(.text) @} |
5735 | @} | |
5736 | @end group | |
5737 | @end smallexample | |
5738 | @noindent | |
5739 | will cause the error message @samp{non constant expression for initial | |
5740 | address}. | |
5741 | ||
5742 | @node Expression Section | |
5743 | @subsection The Section of an Expression | |
5744 | @cindex expression sections | |
5745 | @cindex absolute expressions | |
5746 | @cindex relative expressions | |
5747 | @cindex absolute and relocatable symbols | |
5748 | @cindex relocatable and absolute symbols | |
5749 | @cindex symbols, relocatable and absolute | |
7542af2a AM |
5750 | Addresses and symbols may be section relative, or absolute. A section |
5751 | relative symbol is relocatable. If you request relocatable output | |
5752 | using the @samp{-r} option, a further link operation may change the | |
5753 | value of a section relative symbol. On the other hand, an absolute | |
5754 | symbol will retain the same value throughout any further link | |
5755 | operations. | |
5756 | ||
abf4be64 AM |
5757 | Some terms in linker expressions are addresses. This is true of |
5758 | section relative symbols and for builtin functions that return an | |
5759 | address, such as @code{ADDR}, @code{LOADADDR}, @code{ORIGIN} and | |
5760 | @code{SEGMENT_START}. Other terms are simply numbers, or are builtin | |
5761 | functions that return a non-address value, such as @code{LENGTH}. | |
01554a74 AM |
5762 | One complication is that unless you set @code{LD_FEATURE ("SANE_EXPR")} |
5763 | (@pxref{Miscellaneous Commands}), numbers and absolute symbols are treated | |
5c3049d2 AM |
5764 | differently depending on their location, for compatibility with older |
5765 | versions of @code{ld}. Expressions appearing outside an output | |
5766 | section definition treat all numbers as absolute addresses. | |
5767 | Expressions appearing inside an output section definition treat | |
01554a74 AM |
5768 | absolute symbols as numbers. If @code{LD_FEATURE ("SANE_EXPR")} is |
5769 | given, then absolute symbols and numbers are simply treated as numbers | |
5770 | everywhere. | |
5c3049d2 AM |
5771 | |
5772 | In the following simple example, | |
252b5132 | 5773 | |
7542af2a AM |
5774 | @smallexample |
5775 | @group | |
5776 | SECTIONS | |
5777 | @{ | |
5778 | . = 0x100; | |
5779 | __executable_start = 0x100; | |
5780 | .data : | |
5781 | @{ | |
5782 | . = 0x10; | |
5783 | __data_start = 0x10; | |
5784 | *(.data) | |
5785 | @} | |
5786 | @dots{} | |
5787 | @} | |
5788 | @end group | |
5789 | @end smallexample | |
252b5132 | 5790 | |
7542af2a AM |
5791 | both @code{.} and @code{__executable_start} are set to the absolute |
5792 | address 0x100 in the first two assignments, then both @code{.} and | |
5793 | @code{__data_start} are set to 0x10 relative to the @code{.data} | |
5794 | section in the second two assignments. | |
252b5132 | 5795 | |
5c3049d2 AM |
5796 | For expressions involving numbers, relative addresses and absolute |
5797 | addresses, ld follows these rules to evaluate terms: | |
7542af2a AM |
5798 | |
5799 | @itemize @bullet | |
5800 | @item | |
c05f749e AM |
5801 | Unary operations on an absolute address or number, and binary |
5802 | operations on two absolute addresses or two numbers, or between one | |
5803 | absolute address and a number, apply the operator to the value(s). | |
5804 | @item | |
7542af2a AM |
5805 | Unary operations on a relative address, and binary operations on two |
5806 | relative addresses in the same section or between one relative address | |
5807 | and a number, apply the operator to the offset part of the address(es). | |
5808 | @item | |
c05f749e AM |
5809 | Other binary operations, that is, between two relative addresses not |
5810 | in the same section, or between a relative address and an absolute | |
5811 | address, first convert any non-absolute term to an absolute address | |
5812 | before applying the operator. | |
7542af2a AM |
5813 | @end itemize |
5814 | ||
5815 | The result section of each sub-expression is as follows: | |
5816 | ||
5817 | @itemize @bullet | |
5818 | @item | |
5819 | An operation involving only numbers results in a number. | |
5820 | @item | |
5821 | The result of comparisons, @samp{&&} and @samp{||} is also a number. | |
5822 | @item | |
9bc8bb33 | 5823 | The result of other binary arithmetic and logical operations on two |
11e7fd74 | 5824 | relative addresses in the same section or two absolute addresses |
9bc8bb33 AM |
5825 | (after above conversions) is also a number. |
5826 | @item | |
5827 | The result of other operations on relative addresses or one | |
5828 | relative address and a number, is a relative address in the same | |
5829 | section as the relative operand(s). | |
7542af2a AM |
5830 | @item |
5831 | The result of other operations on absolute addresses (after above | |
5832 | conversions) is an absolute address. | |
5833 | @end itemize | |
252b5132 RH |
5834 | |
5835 | You can use the builtin function @code{ABSOLUTE} to force an expression | |
5836 | to be absolute when it would otherwise be relative. For example, to | |
5837 | create an absolute symbol set to the address of the end of the output | |
5838 | section @samp{.data}: | |
5839 | @smallexample | |
5840 | SECTIONS | |
5841 | @{ | |
5842 | .data : @{ *(.data) _edata = ABSOLUTE(.); @} | |
5843 | @} | |
5844 | @end smallexample | |
5845 | @noindent | |
5846 | If @samp{ABSOLUTE} were not used, @samp{_edata} would be relative to the | |
5847 | @samp{.data} section. | |
5848 | ||
7542af2a AM |
5849 | Using @code{LOADADDR} also forces an expression absolute, since this |
5850 | particular builtin function returns an absolute address. | |
5851 | ||
252b5132 RH |
5852 | @node Builtin Functions |
5853 | @subsection Builtin Functions | |
5854 | @cindex functions in expressions | |
5855 | The linker script language includes a number of builtin functions for | |
5856 | use in linker script expressions. | |
5857 | ||
5858 | @table @code | |
5859 | @item ABSOLUTE(@var{exp}) | |
5860 | @kindex ABSOLUTE(@var{exp}) | |
5861 | @cindex expression, absolute | |
5862 | Return the absolute (non-relocatable, as opposed to non-negative) value | |
5863 | of the expression @var{exp}. Primarily useful to assign an absolute | |
5864 | value to a symbol within a section definition, where symbol values are | |
5865 | normally section relative. @xref{Expression Section}. | |
5866 | ||
5867 | @item ADDR(@var{section}) | |
5868 | @kindex ADDR(@var{section}) | |
5869 | @cindex section address in expression | |
7542af2a | 5870 | Return the address (VMA) of the named @var{section}. Your |
252b5132 | 5871 | script must previously have defined the location of that section. In |
7542af2a AM |
5872 | the following example, @code{start_of_output_1}, @code{symbol_1} and |
5873 | @code{symbol_2} are assigned equivalent values, except that | |
5874 | @code{symbol_1} will be relative to the @code{.output1} section while | |
5875 | the other two will be absolute: | |
252b5132 RH |
5876 | @smallexample |
5877 | @group | |
5878 | SECTIONS @{ @dots{} | |
5879 | .output1 : | |
a1ab1d2a | 5880 | @{ |
252b5132 RH |
5881 | start_of_output_1 = ABSOLUTE(.); |
5882 | @dots{} | |
5883 | @} | |
5884 | .output : | |
5885 | @{ | |
5886 | symbol_1 = ADDR(.output1); | |
5887 | symbol_2 = start_of_output_1; | |
5888 | @} | |
5889 | @dots{} @} | |
5890 | @end group | |
5891 | @end smallexample | |
5892 | ||
876f4090 NS |
5893 | @item ALIGN(@var{align}) |
5894 | @itemx ALIGN(@var{exp},@var{align}) | |
5895 | @kindex ALIGN(@var{align}) | |
5896 | @kindex ALIGN(@var{exp},@var{align}) | |
252b5132 RH |
5897 | @cindex round up location counter |
5898 | @cindex align location counter | |
876f4090 NS |
5899 | @cindex round up expression |
5900 | @cindex align expression | |
5901 | Return the location counter (@code{.}) or arbitrary expression aligned | |
5902 | to the next @var{align} boundary. The single operand @code{ALIGN} | |
5903 | doesn't change the value of the location counter---it just does | |
5904 | arithmetic on it. The two operand @code{ALIGN} allows an arbitrary | |
5905 | expression to be aligned upwards (@code{ALIGN(@var{align})} is | |
5906 | equivalent to @code{ALIGN(., @var{align})}). | |
5907 | ||
5908 | Here is an example which aligns the output @code{.data} section to the | |
5909 | next @code{0x2000} byte boundary after the preceding section and sets a | |
5910 | variable within the section to the next @code{0x8000} boundary after the | |
5911 | input sections: | |
252b5132 RH |
5912 | @smallexample |
5913 | @group | |
5914 | SECTIONS @{ @dots{} | |
5915 | .data ALIGN(0x2000): @{ | |
5916 | *(.data) | |
5917 | variable = ALIGN(0x8000); | |
5918 | @} | |
5919 | @dots{} @} | |
5920 | @end group | |
5921 | @end smallexample | |
5922 | @noindent | |
5923 | The first use of @code{ALIGN} in this example specifies the location of | |
5924 | a section because it is used as the optional @var{address} attribute of | |
5925 | a section definition (@pxref{Output Section Address}). The second use | |
5926 | of @code{ALIGN} is used to defines the value of a symbol. | |
5927 | ||
5928 | The builtin function @code{NEXT} is closely related to @code{ALIGN}. | |
5929 | ||
362c1d1a NS |
5930 | @item ALIGNOF(@var{section}) |
5931 | @kindex ALIGNOF(@var{section}) | |
5932 | @cindex section alignment | |
5933 | Return the alignment in bytes of the named @var{section}, if that section has | |
5934 | been allocated. If the section has not been allocated when this is | |
5935 | evaluated, the linker will report an error. In the following example, | |
5936 | the alignment of the @code{.output} section is stored as the first | |
5937 | value in that section. | |
5938 | @smallexample | |
5939 | @group | |
5940 | SECTIONS@{ @dots{} | |
5941 | .output @{ | |
5942 | LONG (ALIGNOF (.output)) | |
5943 | @dots{} | |
5944 | @} | |
5945 | @dots{} @} | |
5946 | @end group | |
5947 | @end smallexample | |
5948 | ||
252b5132 RH |
5949 | @item BLOCK(@var{exp}) |
5950 | @kindex BLOCK(@var{exp}) | |
5951 | This is a synonym for @code{ALIGN}, for compatibility with older linker | |
5952 | scripts. It is most often seen when setting the address of an output | |
5953 | section. | |
5954 | ||
2d20f7bf JJ |
5955 | @item DATA_SEGMENT_ALIGN(@var{maxpagesize}, @var{commonpagesize}) |
5956 | @kindex DATA_SEGMENT_ALIGN(@var{maxpagesize}, @var{commonpagesize}) | |
5957 | This is equivalent to either | |
5958 | @smallexample | |
5959 | (ALIGN(@var{maxpagesize}) + (. & (@var{maxpagesize} - 1))) | |
5960 | @end smallexample | |
5961 | or | |
5962 | @smallexample | |
5963 | (ALIGN(@var{maxpagesize}) + (. & (@var{maxpagesize} - @var{commonpagesize}))) | |
5964 | @end smallexample | |
5965 | @noindent | |
5966 | depending on whether the latter uses fewer @var{commonpagesize} sized pages | |
5967 | for the data segment (area between the result of this expression and | |
5968 | @code{DATA_SEGMENT_END}) than the former or not. | |
5969 | If the latter form is used, it means @var{commonpagesize} bytes of runtime | |
5970 | memory will be saved at the expense of up to @var{commonpagesize} wasted | |
5971 | bytes in the on-disk file. | |
5972 | ||
5973 | This expression can only be used directly in @code{SECTIONS} commands, not in | |
5974 | any output section descriptions and only once in the linker script. | |
5975 | @var{commonpagesize} should be less or equal to @var{maxpagesize} and should | |
5976 | be the system page size the object wants to be optimized for (while still | |
5977 | working on system page sizes up to @var{maxpagesize}). | |
5978 | ||
5979 | @noindent | |
5980 | Example: | |
5981 | @smallexample | |
5982 | . = DATA_SEGMENT_ALIGN(0x10000, 0x2000); | |
5983 | @end smallexample | |
5984 | ||
5985 | @item DATA_SEGMENT_END(@var{exp}) | |
5986 | @kindex DATA_SEGMENT_END(@var{exp}) | |
5987 | This defines the end of data segment for @code{DATA_SEGMENT_ALIGN} | |
5988 | evaluation purposes. | |
5989 | ||
5990 | @smallexample | |
5991 | . = DATA_SEGMENT_END(.); | |
5992 | @end smallexample | |
5993 | ||
a4f5ad88 JJ |
5994 | @item DATA_SEGMENT_RELRO_END(@var{offset}, @var{exp}) |
5995 | @kindex DATA_SEGMENT_RELRO_END(@var{offset}, @var{exp}) | |
5996 | This defines the end of the @code{PT_GNU_RELRO} segment when | |
eec2f3ed | 5997 | @samp{-z relro} option is used. |
a4f5ad88 JJ |
5998 | When @samp{-z relro} option is not present, @code{DATA_SEGMENT_RELRO_END} |
5999 | does nothing, otherwise @code{DATA_SEGMENT_ALIGN} is padded so that | |
6000 | @var{exp} + @var{offset} is aligned to the most commonly used page | |
6001 | boundary for particular target. If present in the linker script, | |
6002 | it must always come in between @code{DATA_SEGMENT_ALIGN} and | |
eec2f3ed AM |
6003 | @code{DATA_SEGMENT_END}. Evaluates to the second argument plus any |
6004 | padding needed at the end of the @code{PT_GNU_RELRO} segment due to | |
6005 | section alignment. | |
a4f5ad88 JJ |
6006 | |
6007 | @smallexample | |
6008 | . = DATA_SEGMENT_RELRO_END(24, .); | |
6009 | @end smallexample | |
6010 | ||
252b5132 RH |
6011 | @item DEFINED(@var{symbol}) |
6012 | @kindex DEFINED(@var{symbol}) | |
6013 | @cindex symbol defaults | |
6014 | Return 1 if @var{symbol} is in the linker global symbol table and is | |
420e579c HPN |
6015 | defined before the statement using DEFINED in the script, otherwise |
6016 | return 0. You can use this function to provide | |
252b5132 RH |
6017 | default values for symbols. For example, the following script fragment |
6018 | shows how to set a global symbol @samp{begin} to the first location in | |
6019 | the @samp{.text} section---but if a symbol called @samp{begin} already | |
6020 | existed, its value is preserved: | |
6021 | ||
6022 | @smallexample | |
6023 | @group | |
6024 | SECTIONS @{ @dots{} | |
6025 | .text : @{ | |
6026 | begin = DEFINED(begin) ? begin : . ; | |
6027 | @dots{} | |
6028 | @} | |
6029 | @dots{} | |
6030 | @} | |
6031 | @end group | |
6032 | @end smallexample | |
6033 | ||
3ec57632 NC |
6034 | @item LENGTH(@var{memory}) |
6035 | @kindex LENGTH(@var{memory}) | |
6036 | Return the length of the memory region named @var{memory}. | |
6037 | ||
252b5132 RH |
6038 | @item LOADADDR(@var{section}) |
6039 | @kindex LOADADDR(@var{section}) | |
6040 | @cindex section load address in expression | |
7542af2a | 6041 | Return the absolute LMA of the named @var{section}. (@pxref{Output |
252b5132 RH |
6042 | Section LMA}). |
6043 | ||
2e53f7d6 NC |
6044 | @item LOG2CEIL(@var{exp}) |
6045 | @kindex LOG2CEIL(@var{exp}) | |
6046 | Return the binary logarithm of @var{exp} rounded towards infinity. | |
6047 | @code{LOG2CEIL(0)} returns 0. | |
6048 | ||
252b5132 RH |
6049 | @kindex MAX |
6050 | @item MAX(@var{exp1}, @var{exp2}) | |
6051 | Returns the maximum of @var{exp1} and @var{exp2}. | |
6052 | ||
6053 | @kindex MIN | |
6054 | @item MIN(@var{exp1}, @var{exp2}) | |
6055 | Returns the minimum of @var{exp1} and @var{exp2}. | |
6056 | ||
6057 | @item NEXT(@var{exp}) | |
6058 | @kindex NEXT(@var{exp}) | |
6059 | @cindex unallocated address, next | |
6060 | Return the next unallocated address that is a multiple of @var{exp}. | |
6061 | This function is closely related to @code{ALIGN(@var{exp})}; unless you | |
6062 | use the @code{MEMORY} command to define discontinuous memory for the | |
6063 | output file, the two functions are equivalent. | |
6064 | ||
3ec57632 NC |
6065 | @item ORIGIN(@var{memory}) |
6066 | @kindex ORIGIN(@var{memory}) | |
6067 | Return the origin of the memory region named @var{memory}. | |
6068 | ||
ba916c8a MM |
6069 | @item SEGMENT_START(@var{segment}, @var{default}) |
6070 | @kindex SEGMENT_START(@var{segment}, @var{default}) | |
6071 | Return the base address of the named @var{segment}. If an explicit | |
c5da8c7d NC |
6072 | value has already been given for this segment (with a command-line |
6073 | @samp{-T} option) then that value will be returned otherwise the value | |
6074 | will be @var{default}. At present, the @samp{-T} command-line option | |
6075 | can only be used to set the base address for the ``text'', ``data'', and | |
7542af2a | 6076 | ``bss'' sections, but you can use @code{SEGMENT_START} with any segment |
ba916c8a MM |
6077 | name. |
6078 | ||
252b5132 RH |
6079 | @item SIZEOF(@var{section}) |
6080 | @kindex SIZEOF(@var{section}) | |
6081 | @cindex section size | |
6082 | Return the size in bytes of the named @var{section}, if that section has | |
6083 | been allocated. If the section has not been allocated when this is | |
6084 | evaluated, the linker will report an error. In the following example, | |
6085 | @code{symbol_1} and @code{symbol_2} are assigned identical values: | |
6086 | @smallexample | |
6087 | @group | |
6088 | SECTIONS@{ @dots{} | |
6089 | .output @{ | |
6090 | .start = . ; | |
6091 | @dots{} | |
6092 | .end = . ; | |
6093 | @} | |
6094 | symbol_1 = .end - .start ; | |
6095 | symbol_2 = SIZEOF(.output); | |
6096 | @dots{} @} | |
6097 | @end group | |
6098 | @end smallexample | |
6099 | ||
6100 | @item SIZEOF_HEADERS | |
6101 | @itemx sizeof_headers | |
6102 | @kindex SIZEOF_HEADERS | |
6103 | @cindex header size | |
6104 | Return the size in bytes of the output file's headers. This is | |
6105 | information which appears at the start of the output file. You can use | |
6106 | this number when setting the start address of the first section, if you | |
6107 | choose, to facilitate paging. | |
6108 | ||
6109 | @cindex not enough room for program headers | |
6110 | @cindex program headers, not enough room | |
6111 | When producing an ELF output file, if the linker script uses the | |
6112 | @code{SIZEOF_HEADERS} builtin function, the linker must compute the | |
6113 | number of program headers before it has determined all the section | |
6114 | addresses and sizes. If the linker later discovers that it needs | |
6115 | additional program headers, it will report an error @samp{not enough | |
6116 | room for program headers}. To avoid this error, you must avoid using | |
6117 | the @code{SIZEOF_HEADERS} function, or you must rework your linker | |
6118 | script to avoid forcing the linker to use additional program headers, or | |
6119 | you must define the program headers yourself using the @code{PHDRS} | |
6120 | command (@pxref{PHDRS}). | |
6121 | @end table | |
6122 | ||
6123 | @node Implicit Linker Scripts | |
6124 | @section Implicit Linker Scripts | |
6125 | @cindex implicit linker scripts | |
6126 | If you specify a linker input file which the linker can not recognize as | |
6127 | an object file or an archive file, it will try to read the file as a | |
6128 | linker script. If the file can not be parsed as a linker script, the | |
6129 | linker will report an error. | |
6130 | ||
6131 | An implicit linker script will not replace the default linker script. | |
6132 | ||
6133 | Typically an implicit linker script would contain only symbol | |
6134 | assignments, or the @code{INPUT}, @code{GROUP}, or @code{VERSION} | |
6135 | commands. | |
6136 | ||
6137 | Any input files read because of an implicit linker script will be read | |
6138 | at the position in the command line where the implicit linker script was | |
6139 | read. This can affect archive searching. | |
6140 | ||
6141 | @ifset GENERIC | |
6142 | @node Machine Dependent | |
6143 | @chapter Machine Dependent Features | |
6144 | ||
6145 | @cindex machine dependencies | |
ff5dcc92 SC |
6146 | @command{ld} has additional features on some platforms; the following |
6147 | sections describe them. Machines where @command{ld} has no additional | |
252b5132 RH |
6148 | functionality are not listed. |
6149 | ||
6150 | @menu | |
36f63dca NC |
6151 | @ifset H8300 |
6152 | * H8/300:: @command{ld} and the H8/300 | |
6153 | @end ifset | |
6154 | @ifset I960 | |
6155 | * i960:: @command{ld} and the Intel 960 family | |
6156 | @end ifset | |
7ca01ed9 NC |
6157 | @ifset M68HC11 |
6158 | * M68HC11/68HC12:: @code{ld} and the Motorola 68HC11 and 68HC12 families | |
6159 | @end ifset | |
36f63dca NC |
6160 | @ifset ARM |
6161 | * ARM:: @command{ld} and the ARM family | |
6162 | @end ifset | |
6163 | @ifset HPPA | |
6164 | * HPPA ELF32:: @command{ld} and HPPA 32-bit ELF | |
6165 | @end ifset | |
7fb9f789 NC |
6166 | @ifset M68K |
6167 | * M68K:: @command{ld} and the Motorola 68K family | |
6168 | @end ifset | |
833794fc MR |
6169 | @ifset MIPS |
6170 | * MIPS:: @command{ld} and the MIPS family | |
6171 | @end ifset | |
3c3bdf30 | 6172 | @ifset MMIX |
36f63dca | 6173 | * MMIX:: @command{ld} and MMIX |
3c3bdf30 | 6174 | @end ifset |
2469cfa2 | 6175 | @ifset MSP430 |
36f63dca | 6176 | * MSP430:: @command{ld} and MSP430 |
2469cfa2 | 6177 | @end ifset |
35c08157 KLC |
6178 | @ifset NDS32 |
6179 | * NDS32:: @command{ld} and NDS32 | |
6180 | @end ifset | |
78058a5e SL |
6181 | @ifset NIOSII |
6182 | * Nios II:: @command{ld} and the Altera Nios II | |
6183 | @end ifset | |
2a60a7a8 AM |
6184 | @ifset POWERPC |
6185 | * PowerPC ELF32:: @command{ld} and PowerPC 32-bit ELF Support | |
6186 | @end ifset | |
6187 | @ifset POWERPC64 | |
6188 | * PowerPC64 ELF64:: @command{ld} and PowerPC64 64-bit ELF Support | |
6189 | @end ifset | |
49fa1e15 AM |
6190 | @ifset SPU |
6191 | * SPU ELF:: @command{ld} and SPU ELF Support | |
6192 | @end ifset | |
74459f0e | 6193 | @ifset TICOFF |
ff5dcc92 | 6194 | * TI COFF:: @command{ld} and TI COFF |
74459f0e | 6195 | @end ifset |
2ca22b03 NC |
6196 | @ifset WIN32 |
6197 | * WIN32:: @command{ld} and WIN32 (cygwin/mingw) | |
6198 | @end ifset | |
e0001a05 NC |
6199 | @ifset XTENSA |
6200 | * Xtensa:: @command{ld} and Xtensa Processors | |
6201 | @end ifset | |
252b5132 RH |
6202 | @end menu |
6203 | @end ifset | |
6204 | ||
252b5132 RH |
6205 | @ifset H8300 |
6206 | @ifclear GENERIC | |
6207 | @raisesections | |
6208 | @end ifclear | |
6209 | ||
6210 | @node H8/300 | |
ff5dcc92 | 6211 | @section @command{ld} and the H8/300 |
252b5132 RH |
6212 | |
6213 | @cindex H8/300 support | |
ff5dcc92 | 6214 | For the H8/300, @command{ld} can perform these global optimizations when |
252b5132 RH |
6215 | you specify the @samp{--relax} command-line option. |
6216 | ||
6217 | @table @emph | |
6218 | @cindex relaxing on H8/300 | |
6219 | @item relaxing address modes | |
ff5dcc92 | 6220 | @command{ld} finds all @code{jsr} and @code{jmp} instructions whose |
252b5132 RH |
6221 | targets are within eight bits, and turns them into eight-bit |
6222 | program-counter relative @code{bsr} and @code{bra} instructions, | |
6223 | respectively. | |
6224 | ||
6225 | @cindex synthesizing on H8/300 | |
6226 | @item synthesizing instructions | |
81f5558e | 6227 | @c FIXME: specifically mov.b, or any mov instructions really? -> mov.b only, at least on H8, H8H, H8S |
ff5dcc92 | 6228 | @command{ld} finds all @code{mov.b} instructions which use the |
252b5132 RH |
6229 | sixteen-bit absolute address form, but refer to the top |
6230 | page of memory, and changes them to use the eight-bit address form. | |
6231 | (That is: the linker turns @samp{mov.b @code{@@}@var{aa}:16} into | |
6232 | @samp{mov.b @code{@@}@var{aa}:8} whenever the address @var{aa} is in the | |
6233 | top page of memory). | |
1502569c | 6234 | |
81f5558e NC |
6235 | @command{ld} finds all @code{mov} instructions which use the register |
6236 | indirect with 32-bit displacement addressing mode, but use a small | |
6237 | displacement inside 16-bit displacement range, and changes them to use | |
6238 | the 16-bit displacement form. (That is: the linker turns @samp{mov.b | |
6239 | @code{@@}@var{d}:32,ERx} into @samp{mov.b @code{@@}@var{d}:16,ERx} | |
6240 | whenever the displacement @var{d} is in the 16 bit signed integer | |
6241 | range. Only implemented in ELF-format ld). | |
6242 | ||
1502569c | 6243 | @item bit manipulation instructions |
c0065db7 | 6244 | @command{ld} finds all bit manipulation instructions like @code{band, bclr, |
1502569c | 6245 | biand, bild, bior, bist, bixor, bld, bnot, bor, bset, bst, btst, bxor} |
c0065db7 | 6246 | which use 32 bit and 16 bit absolute address form, but refer to the top |
1502569c NC |
6247 | page of memory, and changes them to use the 8 bit address form. |
6248 | (That is: the linker turns @samp{bset #xx:3,@code{@@}@var{aa}:32} into | |
c0065db7 | 6249 | @samp{bset #xx:3,@code{@@}@var{aa}:8} whenever the address @var{aa} is in |
1502569c NC |
6250 | the top page of memory). |
6251 | ||
6252 | @item system control instructions | |
c0065db7 RM |
6253 | @command{ld} finds all @code{ldc.w, stc.w} instructions which use the |
6254 | 32 bit absolute address form, but refer to the top page of memory, and | |
1502569c NC |
6255 | changes them to use 16 bit address form. |
6256 | (That is: the linker turns @samp{ldc.w @code{@@}@var{aa}:32,ccr} into | |
c0065db7 | 6257 | @samp{ldc.w @code{@@}@var{aa}:16,ccr} whenever the address @var{aa} is in |
1502569c | 6258 | the top page of memory). |
252b5132 RH |
6259 | @end table |
6260 | ||
6261 | @ifclear GENERIC | |
6262 | @lowersections | |
6263 | @end ifclear | |
6264 | @end ifset | |
6265 | ||
36f63dca | 6266 | @ifclear GENERIC |
c2dcd04e | 6267 | @ifset Renesas |
36f63dca | 6268 | @c This stuff is pointless to say unless you're especially concerned |
c2dcd04e NC |
6269 | @c with Renesas chips; don't enable it for generic case, please. |
6270 | @node Renesas | |
6271 | @chapter @command{ld} and Other Renesas Chips | |
36f63dca | 6272 | |
c2dcd04e NC |
6273 | @command{ld} also supports the Renesas (formerly Hitachi) H8/300H, |
6274 | H8/500, and SH chips. No special features, commands, or command-line | |
6275 | options are required for these chips. | |
36f63dca NC |
6276 | @end ifset |
6277 | @end ifclear | |
6278 | ||
6279 | @ifset I960 | |
6280 | @ifclear GENERIC | |
6281 | @raisesections | |
6282 | @end ifclear | |
6283 | ||
6284 | @node i960 | |
6285 | @section @command{ld} and the Intel 960 Family | |
6286 | ||
6287 | @cindex i960 support | |
6288 | ||
6289 | You can use the @samp{-A@var{architecture}} command line option to | |
6290 | specify one of the two-letter names identifying members of the 960 | |
6291 | family; the option specifies the desired output target, and warns of any | |
6292 | incompatible instructions in the input files. It also modifies the | |
6293 | linker's search strategy for archive libraries, to support the use of | |
6294 | libraries specific to each particular architecture, by including in the | |
6295 | search loop names suffixed with the string identifying the architecture. | |
6296 | ||
6297 | For example, if your @command{ld} command line included @w{@samp{-ACA}} as | |
6298 | well as @w{@samp{-ltry}}, the linker would look (in its built-in search | |
6299 | paths, and in any paths you specify with @samp{-L}) for a library with | |
6300 | the names | |
6301 | ||
6302 | @smallexample | |
6303 | @group | |
6304 | try | |
6305 | libtry.a | |
6306 | tryca | |
6307 | libtryca.a | |
6308 | @end group | |
6309 | @end smallexample | |
6310 | ||
6311 | @noindent | |
6312 | The first two possibilities would be considered in any event; the last | |
6313 | two are due to the use of @w{@samp{-ACA}}. | |
6314 | ||
6315 | You can meaningfully use @samp{-A} more than once on a command line, since | |
6316 | the 960 architecture family allows combination of target architectures; each | |
6317 | use will add another pair of name variants to search for when @w{@samp{-l}} | |
6318 | specifies a library. | |
6319 | ||
6320 | @cindex @option{--relax} on i960 | |
6321 | @cindex relaxing on i960 | |
6322 | @command{ld} supports the @samp{--relax} option for the i960 family. If | |
6323 | you specify @samp{--relax}, @command{ld} finds all @code{balx} and | |
6324 | @code{calx} instructions whose targets are within 24 bits, and turns | |
6325 | them into 24-bit program-counter relative @code{bal} and @code{cal} | |
6326 | instructions, respectively. @command{ld} also turns @code{cal} | |
6327 | instructions into @code{bal} instructions when it determines that the | |
6328 | target subroutine is a leaf routine (that is, the target subroutine does | |
6329 | not itself call any subroutines). | |
6330 | ||
6331 | @ifclear GENERIC | |
6332 | @lowersections | |
6333 | @end ifclear | |
6334 | @end ifset | |
6335 | ||
6336 | @ifset ARM | |
6337 | @ifclear GENERIC | |
6338 | @raisesections | |
6339 | @end ifclear | |
6340 | ||
93fd0973 SC |
6341 | @ifset M68HC11 |
6342 | @ifclear GENERIC | |
6343 | @raisesections | |
6344 | @end ifclear | |
6345 | ||
6346 | @node M68HC11/68HC12 | |
6347 | @section @command{ld} and the Motorola 68HC11 and 68HC12 families | |
6348 | ||
6349 | @cindex M68HC11 and 68HC12 support | |
6350 | ||
6351 | @subsection Linker Relaxation | |
6352 | ||
6353 | For the Motorola 68HC11, @command{ld} can perform these global | |
6354 | optimizations when you specify the @samp{--relax} command-line option. | |
6355 | ||
6356 | @table @emph | |
6357 | @cindex relaxing on M68HC11 | |
6358 | @item relaxing address modes | |
6359 | @command{ld} finds all @code{jsr} and @code{jmp} instructions whose | |
6360 | targets are within eight bits, and turns them into eight-bit | |
6361 | program-counter relative @code{bsr} and @code{bra} instructions, | |
6362 | respectively. | |
6363 | ||
6364 | @command{ld} also looks at all 16-bit extended addressing modes and | |
6365 | transforms them in a direct addressing mode when the address is in | |
6366 | page 0 (between 0 and 0x0ff). | |
6367 | ||
6368 | @item relaxing gcc instruction group | |
6369 | When @command{gcc} is called with @option{-mrelax}, it can emit group | |
6370 | of instructions that the linker can optimize to use a 68HC11 direct | |
6371 | addressing mode. These instructions consists of @code{bclr} or | |
6372 | @code{bset} instructions. | |
6373 | ||
6374 | @end table | |
6375 | ||
6376 | @subsection Trampoline Generation | |
6377 | ||
6378 | @cindex trampoline generation on M68HC11 | |
6379 | @cindex trampoline generation on M68HC12 | |
6380 | For 68HC11 and 68HC12, @command{ld} can generate trampoline code to | |
6381 | call a far function using a normal @code{jsr} instruction. The linker | |
c0065db7 | 6382 | will also change the relocation to some far function to use the |
93fd0973 SC |
6383 | trampoline address instead of the function address. This is typically the |
6384 | case when a pointer to a function is taken. The pointer will in fact | |
6385 | point to the function trampoline. | |
6386 | ||
6387 | @ifclear GENERIC | |
6388 | @lowersections | |
6389 | @end ifclear | |
6390 | @end ifset | |
6391 | ||
36f63dca | 6392 | @node ARM |
3674e28a | 6393 | @section @command{ld} and the ARM family |
36f63dca NC |
6394 | |
6395 | @cindex ARM interworking support | |
6396 | @kindex --support-old-code | |
6397 | For the ARM, @command{ld} will generate code stubs to allow functions calls | |
b45619c0 | 6398 | between ARM and Thumb code. These stubs only work with code that has |
36f63dca NC |
6399 | been compiled and assembled with the @samp{-mthumb-interwork} command |
6400 | line option. If it is necessary to link with old ARM object files or | |
6401 | libraries, which have not been compiled with the -mthumb-interwork | |
6402 | option then the @samp{--support-old-code} command line switch should be | |
6403 | given to the linker. This will make it generate larger stub functions | |
6404 | which will work with non-interworking aware ARM code. Note, however, | |
6405 | the linker does not support generating stubs for function calls to | |
6406 | non-interworking aware Thumb code. | |
6407 | ||
6408 | @cindex thumb entry point | |
6409 | @cindex entry point, thumb | |
6410 | @kindex --thumb-entry=@var{entry} | |
6411 | The @samp{--thumb-entry} switch is a duplicate of the generic | |
6412 | @samp{--entry} switch, in that it sets the program's starting address. | |
6413 | But it also sets the bottom bit of the address, so that it can be | |
6414 | branched to using a BX instruction, and the program will start | |
6415 | executing in Thumb mode straight away. | |
6416 | ||
ce11ba6c KT |
6417 | @cindex PE import table prefixing |
6418 | @kindex --use-nul-prefixed-import-tables | |
6419 | The @samp{--use-nul-prefixed-import-tables} switch is specifying, that | |
6420 | the import tables idata4 and idata5 have to be generated with a zero | |
11e7fd74 | 6421 | element prefix for import libraries. This is the old style to generate |
ce11ba6c KT |
6422 | import tables. By default this option is turned off. |
6423 | ||
e489d0ae PB |
6424 | @cindex BE8 |
6425 | @kindex --be8 | |
6426 | The @samp{--be8} switch instructs @command{ld} to generate BE8 format | |
6427 | executables. This option is only valid when linking big-endian objects. | |
6428 | The resulting image will contain big-endian data and little-endian code. | |
6429 | ||
3674e28a PB |
6430 | @cindex TARGET1 |
6431 | @kindex --target1-rel | |
6432 | @kindex --target1-abs | |
6433 | The @samp{R_ARM_TARGET1} relocation is typically used for entries in the | |
6434 | @samp{.init_array} section. It is interpreted as either @samp{R_ARM_REL32} | |
6435 | or @samp{R_ARM_ABS32}, depending on the target. The @samp{--target1-rel} | |
6436 | and @samp{--target1-abs} switches override the default. | |
6437 | ||
6438 | @cindex TARGET2 | |
6439 | @kindex --target2=@var{type} | |
6440 | The @samp{--target2=type} switch overrides the default definition of the | |
6441 | @samp{R_ARM_TARGET2} relocation. Valid values for @samp{type}, their | |
6442 | meanings, and target defaults are as follows: | |
6443 | @table @samp | |
6444 | @item rel | |
eeac373a PB |
6445 | @samp{R_ARM_REL32} (arm*-*-elf, arm*-*-eabi) |
6446 | @item abs | |
6447 | @samp{R_ARM_ABS32} (arm*-*-symbianelf) | |
3674e28a PB |
6448 | @item got-rel |
6449 | @samp{R_ARM_GOT_PREL} (arm*-*-linux, arm*-*-*bsd) | |
6450 | @end table | |
6451 | ||
319850b4 JB |
6452 | @cindex FIX_V4BX |
6453 | @kindex --fix-v4bx | |
6454 | The @samp{R_ARM_V4BX} relocation (defined by the ARM AAELF | |
6455 | specification) enables objects compiled for the ARMv4 architecture to be | |
6456 | interworking-safe when linked with other objects compiled for ARMv4t, but | |
6457 | also allows pure ARMv4 binaries to be built from the same ARMv4 objects. | |
6458 | ||
6459 | In the latter case, the switch @option{--fix-v4bx} must be passed to the | |
6460 | linker, which causes v4t @code{BX rM} instructions to be rewritten as | |
6461 | @code{MOV PC,rM}, since v4 processors do not have a @code{BX} instruction. | |
6462 | ||
6463 | In the former case, the switch should not be used, and @samp{R_ARM_V4BX} | |
6464 | relocations are ignored. | |
6465 | ||
845b51d6 PB |
6466 | @cindex FIX_V4BX_INTERWORKING |
6467 | @kindex --fix-v4bx-interworking | |
6468 | Replace @code{BX rM} instructions identified by @samp{R_ARM_V4BX} | |
6469 | relocations with a branch to the following veneer: | |
6470 | ||
6471 | @smallexample | |
6472 | TST rM, #1 | |
6473 | MOVEQ PC, rM | |
6474 | BX Rn | |
6475 | @end smallexample | |
6476 | ||
6477 | This allows generation of libraries/applications that work on ARMv4 cores | |
6478 | and are still interworking safe. Note that the above veneer clobbers the | |
11e7fd74 | 6479 | condition flags, so may cause incorrect program behavior in rare cases. |
845b51d6 | 6480 | |
33bfe774 JB |
6481 | @cindex USE_BLX |
6482 | @kindex --use-blx | |
6483 | The @samp{--use-blx} switch enables the linker to use ARM/Thumb | |
6484 | BLX instructions (available on ARMv5t and above) in various | |
6485 | situations. Currently it is used to perform calls via the PLT from Thumb | |
6486 | code using BLX rather than using BX and a mode-switching stub before | |
6487 | each PLT entry. This should lead to such calls executing slightly faster. | |
6488 | ||
6489 | This option is enabled implicitly for SymbianOS, so there is no need to | |
6490 | specify it if you are using that target. | |
6491 | ||
c6dd86c6 JB |
6492 | @cindex VFP11_DENORM_FIX |
6493 | @kindex --vfp11-denorm-fix | |
6494 | The @samp{--vfp11-denorm-fix} switch enables a link-time workaround for a | |
6495 | bug in certain VFP11 coprocessor hardware, which sometimes allows | |
6496 | instructions with denorm operands (which must be handled by support code) | |
6497 | to have those operands overwritten by subsequent instructions before | |
6498 | the support code can read the intended values. | |
6499 | ||
6500 | The bug may be avoided in scalar mode if you allow at least one | |
6501 | intervening instruction between a VFP11 instruction which uses a register | |
6502 | and another instruction which writes to the same register, or at least two | |
6503 | intervening instructions if vector mode is in use. The bug only affects | |
6504 | full-compliance floating-point mode: you do not need this workaround if | |
6505 | you are using "runfast" mode. Please contact ARM for further details. | |
6506 | ||
6507 | If you know you are using buggy VFP11 hardware, you can | |
6508 | enable this workaround by specifying the linker option | |
6509 | @samp{--vfp-denorm-fix=scalar} if you are using the VFP11 scalar | |
6510 | mode only, or @samp{--vfp-denorm-fix=vector} if you are using | |
6511 | vector mode (the latter also works for scalar code). The default is | |
6512 | @samp{--vfp-denorm-fix=none}. | |
6513 | ||
6514 | If the workaround is enabled, instructions are scanned for | |
6515 | potentially-troublesome sequences, and a veneer is created for each | |
6516 | such sequence which may trigger the erratum. The veneer consists of the | |
6517 | first instruction of the sequence and a branch back to the subsequent | |
6518 | instruction. The original instruction is then replaced with a branch to | |
6519 | the veneer. The extra cycles required to call and return from the veneer | |
6520 | are sufficient to avoid the erratum in both the scalar and vector cases. | |
6521 | ||
2de70689 MGD |
6522 | @cindex ARM1176 erratum workaround |
6523 | @kindex --fix-arm1176 | |
6524 | @kindex --no-fix-arm1176 | |
9d5777a3 RM |
6525 | The @samp{--fix-arm1176} switch enables a link-time workaround for an erratum |
6526 | in certain ARM1176 processors. The workaround is enabled by default if you | |
6527 | are targeting ARM v6 (excluding ARM v6T2) or earlier. It can be disabled | |
2de70689 MGD |
6528 | unconditionally by specifying @samp{--no-fix-arm1176}. |
6529 | ||
9d5777a3 | 6530 | Further information is available in the ``ARM1176JZ-S and ARM1176JZF-S |
11e7fd74 | 6531 | Programmer Advice Notice'' available on the ARM documentation website at: |
2de70689 MGD |
6532 | http://infocenter.arm.com/. |
6533 | ||
bf21ed78 MS |
6534 | @cindex NO_ENUM_SIZE_WARNING |
6535 | @kindex --no-enum-size-warning | |
726150b7 | 6536 | The @option{--no-enum-size-warning} switch prevents the linker from |
bf21ed78 MS |
6537 | warning when linking object files that specify incompatible EABI |
6538 | enumeration size attributes. For example, with this switch enabled, | |
6539 | linking of an object file using 32-bit enumeration values with another | |
6540 | using enumeration values fitted into the smallest possible space will | |
6541 | not be diagnosed. | |
a9dc9481 JM |
6542 | |
6543 | @cindex NO_WCHAR_SIZE_WARNING | |
6544 | @kindex --no-wchar-size-warning | |
6545 | The @option{--no-wchar-size-warning} switch prevents the linker from | |
6546 | warning when linking object files that specify incompatible EABI | |
6547 | @code{wchar_t} size attributes. For example, with this switch enabled, | |
6548 | linking of an object file using 32-bit @code{wchar_t} values with another | |
6549 | using 16-bit @code{wchar_t} values will not be diagnosed. | |
bf21ed78 | 6550 | |
726150b7 NC |
6551 | @cindex PIC_VENEER |
6552 | @kindex --pic-veneer | |
6553 | The @samp{--pic-veneer} switch makes the linker use PIC sequences for | |
6554 | ARM/Thumb interworking veneers, even if the rest of the binary | |
6555 | is not PIC. This avoids problems on uClinux targets where | |
6556 | @samp{--emit-relocs} is used to generate relocatable binaries. | |
6557 | ||
6558 | @cindex STUB_GROUP_SIZE | |
6559 | @kindex --stub-group-size=@var{N} | |
6560 | The linker will automatically generate and insert small sequences of | |
6561 | code into a linked ARM ELF executable whenever an attempt is made to | |
6562 | perform a function call to a symbol that is too far away. The | |
6563 | placement of these sequences of instructions - called stubs - is | |
6564 | controlled by the command line option @option{--stub-group-size=N}. | |
6565 | The placement is important because a poor choice can create a need for | |
11e7fd74 | 6566 | duplicate stubs, increasing the code size. The linker will try to |
726150b7 NC |
6567 | group stubs together in order to reduce interruptions to the flow of |
6568 | code, but it needs guidance as to how big these groups should be and | |
6569 | where they should be placed. | |
6570 | ||
6571 | The value of @samp{N}, the parameter to the | |
6572 | @option{--stub-group-size=} option controls where the stub groups are | |
07d72278 | 6573 | placed. If it is negative then all stubs are placed after the first |
726150b7 NC |
6574 | branch that needs them. If it is positive then the stubs can be |
6575 | placed either before or after the branches that need them. If the | |
6576 | value of @samp{N} is 1 (either +1 or -1) then the linker will choose | |
6577 | exactly where to place groups of stubs, using its built in heuristics. | |
6578 | A value of @samp{N} greater than 1 (or smaller than -1) tells the | |
6579 | linker that a single group of stubs can service at most @samp{N} bytes | |
6580 | from the input sections. | |
6581 | ||
6582 | The default, if @option{--stub-group-size=} is not specified, is | |
6583 | @samp{N = +1}. | |
6584 | ||
1a51c1a4 NC |
6585 | Farcalls stubs insertion is fully supported for the ARM-EABI target |
6586 | only, because it relies on object files properties not present | |
6587 | otherwise. | |
6588 | ||
1db37fe6 YG |
6589 | @cindex Cortex-A8 erratum workaround |
6590 | @kindex --fix-cortex-a8 | |
6591 | @kindex --no-fix-cortex-a8 | |
6592 | The @samp{--fix-cortex-a8} switch enables a link-time workaround for an erratum in certain Cortex-A8 processors. The workaround is enabled by default if you are targeting the ARM v7-A architecture profile. It can be enabled otherwise by specifying @samp{--fix-cortex-a8}, or disabled unconditionally by specifying @samp{--no-fix-cortex-a8}. | |
6593 | ||
6594 | The erratum only affects Thumb-2 code. Please contact ARM for further details. | |
6595 | ||
68fcca92 JW |
6596 | @cindex Cortex-A53 erratum 835769 workaround |
6597 | @kindex --fix-cortex-a53-835769 | |
6598 | @kindex --no-fix-cortex-a53-835769 | |
6599 | The @samp{--fix-cortex-a53-835769} switch enables a link-time workaround for erratum 835769 present on certain early revisions of Cortex-A53 processors. The workaround is disabled by default. It can be enabled by specifying @samp{--fix-cortex-a53-835769}, or disabled unconditionally by specifying @samp{--no-fix-cortex-a53-835769}. | |
6600 | ||
6601 | Please contact ARM for further details. | |
6602 | ||
1db37fe6 YG |
6603 | @kindex --merge-exidx-entries |
6604 | @kindex --no-merge-exidx-entries | |
6605 | @cindex Merging exidx entries | |
6606 | The @samp{--no-merge-exidx-entries} switch disables the merging of adjacent exidx entries in debuginfo. | |
6607 | ||
6608 | @kindex --long-plt | |
6609 | @cindex 32-bit PLT entries | |
6610 | The @samp{--long-plt} option enables the use of 16 byte PLT entries | |
6611 | which support up to 4Gb of code. The default is to use 12 byte PLT | |
6612 | entries which only support 512Mb of code. | |
6613 | ||
36f63dca NC |
6614 | @ifclear GENERIC |
6615 | @lowersections | |
6616 | @end ifclear | |
6617 | @end ifset | |
6618 | ||
6619 | @ifset HPPA | |
6620 | @ifclear GENERIC | |
6621 | @raisesections | |
6622 | @end ifclear | |
6623 | ||
6624 | @node HPPA ELF32 | |
6625 | @section @command{ld} and HPPA 32-bit ELF Support | |
6626 | @cindex HPPA multiple sub-space stubs | |
6627 | @kindex --multi-subspace | |
6628 | When generating a shared library, @command{ld} will by default generate | |
6629 | import stubs suitable for use with a single sub-space application. | |
6630 | The @samp{--multi-subspace} switch causes @command{ld} to generate export | |
6631 | stubs, and different (larger) import stubs suitable for use with | |
6632 | multiple sub-spaces. | |
6633 | ||
6634 | @cindex HPPA stub grouping | |
6635 | @kindex --stub-group-size=@var{N} | |
6636 | Long branch stubs and import/export stubs are placed by @command{ld} in | |
6637 | stub sections located between groups of input sections. | |
6638 | @samp{--stub-group-size} specifies the maximum size of a group of input | |
6639 | sections handled by one stub section. Since branch offsets are signed, | |
6640 | a stub section may serve two groups of input sections, one group before | |
6641 | the stub section, and one group after it. However, when using | |
6642 | conditional branches that require stubs, it may be better (for branch | |
6643 | prediction) that stub sections only serve one group of input sections. | |
6644 | A negative value for @samp{N} chooses this scheme, ensuring that | |
6645 | branches to stubs always use a negative offset. Two special values of | |
6646 | @samp{N} are recognized, @samp{1} and @samp{-1}. These both instruct | |
6647 | @command{ld} to automatically size input section groups for the branch types | |
6648 | detected, with the same behaviour regarding stub placement as other | |
6649 | positive or negative values of @samp{N} respectively. | |
6650 | ||
6651 | Note that @samp{--stub-group-size} does not split input sections. A | |
6652 | single input section larger than the group size specified will of course | |
6653 | create a larger group (of one section). If input sections are too | |
6654 | large, it may not be possible for a branch to reach its stub. | |
6655 | ||
6656 | @ifclear GENERIC | |
6657 | @lowersections | |
6658 | @end ifclear | |
6659 | @end ifset | |
6660 | ||
7fb9f789 NC |
6661 | @ifset M68K |
6662 | @ifclear GENERIC | |
6663 | @raisesections | |
6664 | @end ifclear | |
6665 | ||
6666 | @node M68K | |
6667 | @section @command{ld} and the Motorola 68K family | |
6668 | ||
6669 | @cindex Motorola 68K GOT generation | |
6670 | @kindex --got=@var{type} | |
6671 | The @samp{--got=@var{type}} option lets you choose the GOT generation scheme. | |
6672 | The choices are @samp{single}, @samp{negative}, @samp{multigot} and | |
6673 | @samp{target}. When @samp{target} is selected the linker chooses | |
6674 | the default GOT generation scheme for the current target. | |
6675 | @samp{single} tells the linker to generate a single GOT with | |
6676 | entries only at non-negative offsets. | |
6677 | @samp{negative} instructs the linker to generate a single GOT with | |
6678 | entries at both negative and positive offsets. Not all environments | |
6679 | support such GOTs. | |
6680 | @samp{multigot} allows the linker to generate several GOTs in the | |
6681 | output file. All GOT references from a single input object | |
6682 | file access the same GOT, but references from different input object | |
6683 | files might access different GOTs. Not all environments support such GOTs. | |
6684 | ||
6685 | @ifclear GENERIC | |
6686 | @lowersections | |
6687 | @end ifclear | |
6688 | @end ifset | |
6689 | ||
833794fc MR |
6690 | @ifset MIPS |
6691 | @ifclear GENERIC | |
6692 | @raisesections | |
6693 | @end ifclear | |
6694 | ||
6695 | @node MIPS | |
6696 | @section @command{ld} and the MIPS family | |
6697 | ||
6698 | @cindex MIPS microMIPS instruction choice selection | |
6699 | @kindex --insn32 | |
6700 | @kindex --no-insn32 | |
6701 | The @samp{--insn32} and @samp{--no-insn32} options control the choice of | |
6702 | microMIPS instructions used in code generated by the linker, such as that | |
6703 | in the PLT or lazy binding stubs, or in relaxation. If @samp{--insn32} is | |
6704 | used, then the linker only uses 32-bit instruction encodings. By default | |
6705 | or if @samp{--no-insn32} is used, all instruction encodings are used, | |
6706 | including 16-bit ones where possible. | |
6707 | ||
6708 | @ifclear GENERIC | |
6709 | @lowersections | |
6710 | @end ifclear | |
6711 | @end ifset | |
6712 | ||
36f63dca NC |
6713 | @ifset MMIX |
6714 | @ifclear GENERIC | |
6715 | @raisesections | |
6716 | @end ifclear | |
6717 | ||
6718 | @node MMIX | |
6719 | @section @code{ld} and MMIX | |
6720 | For MMIX, there is a choice of generating @code{ELF} object files or | |
6721 | @code{mmo} object files when linking. The simulator @code{mmix} | |
6722 | understands the @code{mmo} format. The binutils @code{objcopy} utility | |
6723 | can translate between the two formats. | |
6724 | ||
6725 | There is one special section, the @samp{.MMIX.reg_contents} section. | |
6726 | Contents in this section is assumed to correspond to that of global | |
6727 | registers, and symbols referring to it are translated to special symbols, | |
6728 | equal to registers. In a final link, the start address of the | |
6729 | @samp{.MMIX.reg_contents} section corresponds to the first allocated | |
6730 | global register multiplied by 8. Register @code{$255} is not included in | |
6731 | this section; it is always set to the program entry, which is at the | |
6732 | symbol @code{Main} for @code{mmo} files. | |
6733 | ||
7a2de473 HPN |
6734 | Global symbols with the prefix @code{__.MMIX.start.}, for example |
6735 | @code{__.MMIX.start..text} and @code{__.MMIX.start..data} are special. | |
6736 | The default linker script uses these to set the default start address | |
6737 | of a section. | |
36f63dca NC |
6738 | |
6739 | Initial and trailing multiples of zero-valued 32-bit words in a section, | |
6740 | are left out from an mmo file. | |
6741 | ||
6742 | @ifclear GENERIC | |
6743 | @lowersections | |
6744 | @end ifclear | |
6745 | @end ifset | |
6746 | ||
6747 | @ifset MSP430 | |
6748 | @ifclear GENERIC | |
6749 | @raisesections | |
6750 | @end ifclear | |
6751 | ||
6752 | @node MSP430 | |
6753 | @section @code{ld} and MSP430 | |
6754 | For the MSP430 it is possible to select the MPU architecture. The flag @samp{-m [mpu type]} | |
6755 | will select an appropriate linker script for selected MPU type. (To get a list of known MPUs | |
6756 | just pass @samp{-m help} option to the linker). | |
6757 | ||
6758 | @cindex MSP430 extra sections | |
6759 | The linker will recognize some extra sections which are MSP430 specific: | |
6760 | ||
6761 | @table @code | |
6762 | @item @samp{.vectors} | |
6763 | Defines a portion of ROM where interrupt vectors located. | |
6764 | ||
6765 | @item @samp{.bootloader} | |
6766 | Defines the bootloader portion of the ROM (if applicable). Any code | |
6767 | in this section will be uploaded to the MPU. | |
6768 | ||
6769 | @item @samp{.infomem} | |
6770 | Defines an information memory section (if applicable). Any code in | |
6771 | this section will be uploaded to the MPU. | |
6772 | ||
c0065db7 | 6773 | @item @samp{.infomemnobits} |
36f63dca NC |
6774 | This is the same as the @samp{.infomem} section except that any code |
6775 | in this section will not be uploaded to the MPU. | |
6776 | ||
6777 | @item @samp{.noinit} | |
6778 | Denotes a portion of RAM located above @samp{.bss} section. | |
6779 | ||
c0065db7 | 6780 | The last two sections are used by gcc. |
36f63dca NC |
6781 | @end table |
6782 | ||
6783 | @ifclear GENERIC | |
6784 | @lowersections | |
6785 | @end ifclear | |
6786 | @end ifset | |
6787 | ||
35c08157 KLC |
6788 | @ifset NDS32 |
6789 | @ifclear GENERIC | |
6790 | @raisesections | |
6791 | @end ifclear | |
6792 | ||
6793 | @node NDS32 | |
6794 | @section @code{ld} and NDS32 | |
6795 | @kindex relaxing on NDS32 | |
6796 | For NDS32, there are some options to select relaxation behavior. The linker | |
6797 | relaxes objects according to these options. | |
6798 | ||
6799 | @table @code | |
6800 | @item @samp{--m[no-]fp-as-gp} | |
6801 | Disable/enable fp-as-gp relaxation. | |
6802 | ||
6803 | @item @samp{--mexport-symbols=FILE} | |
6804 | Exporting symbols and their address into FILE as linker script. | |
6805 | ||
6806 | @item @samp{--m[no-]ex9} | |
6807 | Disable/enable link-time EX9 relaxation. | |
6808 | ||
6809 | @item @samp{--mexport-ex9=FILE} | |
6810 | Export the EX9 table after linking. | |
6811 | ||
6812 | @item @samp{--mimport-ex9=FILE} | |
6813 | Import the Ex9 table for EX9 relaxation. | |
6814 | ||
6815 | @item @samp{--mupdate-ex9} | |
6816 | Update the existing EX9 table. | |
6817 | ||
6818 | @item @samp{--mex9-limit=NUM} | |
6819 | Maximum number of entries in the ex9 table. | |
6820 | ||
6821 | @item @samp{--mex9-loop-aware} | |
6822 | Avoid generating the EX9 instruction inside the loop. | |
6823 | ||
6824 | @item @samp{--m[no-]ifc} | |
6825 | Disable/enable the link-time IFC optimization. | |
6826 | ||
6827 | @item @samp{--mifc-loop-aware} | |
6828 | Avoid generating the IFC instruction inside the loop. | |
6829 | @end table | |
6830 | ||
6831 | @ifclear GENERIC | |
6832 | @lowersections | |
6833 | @end ifclear | |
6834 | @end ifset | |
6835 | ||
78058a5e SL |
6836 | @ifset NIOSII |
6837 | @ifclear GENERIC | |
6838 | @raisesections | |
6839 | @end ifclear | |
6840 | ||
6841 | @node Nios II | |
6842 | @section @command{ld} and the Altera Nios II | |
6843 | @cindex Nios II call relaxation | |
6844 | @kindex --relax on Nios II | |
6845 | ||
6846 | Call and immediate jump instructions on Nios II processors are limited to | |
6847 | transferring control to addresses in the same 256MB memory segment, | |
6848 | which may result in @command{ld} giving | |
6849 | @samp{relocation truncated to fit} errors with very large programs. | |
6850 | The command-line option @option{--relax} enables the generation of | |
6851 | trampolines that can access the entire 32-bit address space for calls | |
6852 | outside the normal @code{call} and @code{jmpi} address range. These | |
6853 | trampolines are inserted at section boundaries, so may not themselves | |
6854 | be reachable if an input section and its associated call trampolines are | |
6855 | larger than 256MB. | |
6856 | ||
6857 | The @option{--relax} option is enabled by default unless @option{-r} | |
6858 | is also specified. You can disable trampoline generation by using the | |
6859 | @option{--no-relax} linker option. You can also disable this optimization | |
6860 | locally by using the @samp{set .noat} directive in assembly-language | |
6861 | source files, as the linker-inserted trampolines use the @code{at} | |
6862 | register as a temporary. | |
6863 | ||
6864 | Note that the linker @option{--relax} option is independent of assembler | |
6865 | relaxation options, and that using the GNU assembler's @option{-relax-all} | |
6866 | option interferes with the linker's more selective call instruction relaxation. | |
6867 | ||
6868 | @ifclear GENERIC | |
6869 | @lowersections | |
6870 | @end ifclear | |
6871 | @end ifset | |
6872 | ||
2a60a7a8 AM |
6873 | @ifset POWERPC |
6874 | @ifclear GENERIC | |
6875 | @raisesections | |
6876 | @end ifclear | |
6877 | ||
6878 | @node PowerPC ELF32 | |
6879 | @section @command{ld} and PowerPC 32-bit ELF Support | |
6880 | @cindex PowerPC long branches | |
6881 | @kindex --relax on PowerPC | |
6882 | Branches on PowerPC processors are limited to a signed 26-bit | |
6883 | displacement, which may result in @command{ld} giving | |
6884 | @samp{relocation truncated to fit} errors with very large programs. | |
6885 | @samp{--relax} enables the generation of trampolines that can access | |
6886 | the entire 32-bit address space. These trampolines are inserted at | |
6887 | section boundaries, so may not themselves be reachable if an input | |
c8a1f254 NS |
6888 | section exceeds 33M in size. You may combine @samp{-r} and |
6889 | @samp{--relax} to add trampolines in a partial link. In that case | |
6890 | both branches to undefined symbols and inter-section branches are also | |
6891 | considered potentially out of range, and trampolines inserted. | |
2a60a7a8 AM |
6892 | |
6893 | @cindex PowerPC ELF32 options | |
6894 | @table @option | |
6895 | @cindex PowerPC PLT | |
6896 | @kindex --bss-plt | |
6897 | @item --bss-plt | |
6898 | Current PowerPC GCC accepts a @samp{-msecure-plt} option that | |
6899 | generates code capable of using a newer PLT and GOT layout that has | |
6900 | the security advantage of no executable section ever needing to be | |
6901 | writable and no writable section ever being executable. PowerPC | |
6902 | @command{ld} will generate this layout, including stubs to access the | |
6903 | PLT, if all input files (including startup and static libraries) were | |
6904 | compiled with @samp{-msecure-plt}. @samp{--bss-plt} forces the old | |
6905 | BSS PLT (and GOT layout) which can give slightly better performance. | |
6906 | ||
016687f8 AM |
6907 | @kindex --secure-plt |
6908 | @item --secure-plt | |
6909 | @command{ld} will use the new PLT and GOT layout if it is linking new | |
6910 | @samp{-fpic} or @samp{-fPIC} code, but does not do so automatically | |
6911 | when linking non-PIC code. This option requests the new PLT and GOT | |
6912 | layout. A warning will be given if some object file requires the old | |
6913 | style BSS PLT. | |
6914 | ||
2a60a7a8 AM |
6915 | @cindex PowerPC GOT |
6916 | @kindex --sdata-got | |
6917 | @item --sdata-got | |
6918 | The new secure PLT and GOT are placed differently relative to other | |
6919 | sections compared to older BSS PLT and GOT placement. The location of | |
6920 | @code{.plt} must change because the new secure PLT is an initialized | |
6921 | section while the old PLT is uninitialized. The reason for the | |
6922 | @code{.got} change is more subtle: The new placement allows | |
6923 | @code{.got} to be read-only in applications linked with | |
6924 | @samp{-z relro -z now}. However, this placement means that | |
6925 | @code{.sdata} cannot always be used in shared libraries, because the | |
6926 | PowerPC ABI accesses @code{.sdata} in shared libraries from the GOT | |
6927 | pointer. @samp{--sdata-got} forces the old GOT placement. PowerPC | |
6928 | GCC doesn't use @code{.sdata} in shared libraries, so this option is | |
6929 | really only useful for other compilers that may do so. | |
6930 | ||
6931 | @cindex PowerPC stub symbols | |
6932 | @kindex --emit-stub-syms | |
6933 | @item --emit-stub-syms | |
6934 | This option causes @command{ld} to label linker stubs with a local | |
6935 | symbol that encodes the stub type and destination. | |
6936 | ||
6937 | @cindex PowerPC TLS optimization | |
6938 | @kindex --no-tls-optimize | |
6939 | @item --no-tls-optimize | |
6940 | PowerPC @command{ld} normally performs some optimization of code | |
6941 | sequences used to access Thread-Local Storage. Use this option to | |
6942 | disable the optimization. | |
6943 | @end table | |
6944 | ||
6945 | @ifclear GENERIC | |
6946 | @lowersections | |
6947 | @end ifclear | |
6948 | @end ifset | |
6949 | ||
6950 | @ifset POWERPC64 | |
6951 | @ifclear GENERIC | |
6952 | @raisesections | |
6953 | @end ifclear | |
6954 | ||
6955 | @node PowerPC64 ELF64 | |
6956 | @section @command{ld} and PowerPC64 64-bit ELF Support | |
6957 | ||
6958 | @cindex PowerPC64 ELF64 options | |
6959 | @table @option | |
6960 | @cindex PowerPC64 stub grouping | |
6961 | @kindex --stub-group-size | |
6962 | @item --stub-group-size | |
6963 | Long branch stubs, PLT call stubs and TOC adjusting stubs are placed | |
6964 | by @command{ld} in stub sections located between groups of input sections. | |
6965 | @samp{--stub-group-size} specifies the maximum size of a group of input | |
6966 | sections handled by one stub section. Since branch offsets are signed, | |
6967 | a stub section may serve two groups of input sections, one group before | |
6968 | the stub section, and one group after it. However, when using | |
6969 | conditional branches that require stubs, it may be better (for branch | |
6970 | prediction) that stub sections only serve one group of input sections. | |
6971 | A negative value for @samp{N} chooses this scheme, ensuring that | |
6972 | branches to stubs always use a negative offset. Two special values of | |
6973 | @samp{N} are recognized, @samp{1} and @samp{-1}. These both instruct | |
6974 | @command{ld} to automatically size input section groups for the branch types | |
6975 | detected, with the same behaviour regarding stub placement as other | |
6976 | positive or negative values of @samp{N} respectively. | |
6977 | ||
6978 | Note that @samp{--stub-group-size} does not split input sections. A | |
6979 | single input section larger than the group size specified will of course | |
6980 | create a larger group (of one section). If input sections are too | |
6981 | large, it may not be possible for a branch to reach its stub. | |
6982 | ||
6983 | @cindex PowerPC64 stub symbols | |
6984 | @kindex --emit-stub-syms | |
6985 | @item --emit-stub-syms | |
6986 | This option causes @command{ld} to label linker stubs with a local | |
6987 | symbol that encodes the stub type and destination. | |
6988 | ||
6989 | @cindex PowerPC64 dot symbols | |
6990 | @kindex --dotsyms | |
6991 | @kindex --no-dotsyms | |
6992 | @item --dotsyms, --no-dotsyms | |
6993 | These two options control how @command{ld} interprets version patterns | |
6994 | in a version script. Older PowerPC64 compilers emitted both a | |
6995 | function descriptor symbol with the same name as the function, and a | |
6996 | code entry symbol with the name prefixed by a dot (@samp{.}). To | |
6997 | properly version a function @samp{foo}, the version script thus needs | |
6998 | to control both @samp{foo} and @samp{.foo}. The option | |
6999 | @samp{--dotsyms}, on by default, automatically adds the required | |
7000 | dot-prefixed patterns. Use @samp{--no-dotsyms} to disable this | |
7001 | feature. | |
7002 | ||
7003 | @cindex PowerPC64 TLS optimization | |
7004 | @kindex --no-tls-optimize | |
7005 | @item --no-tls-optimize | |
7006 | PowerPC64 @command{ld} normally performs some optimization of code | |
7007 | sequences used to access Thread-Local Storage. Use this option to | |
7008 | disable the optimization. | |
7009 | ||
7010 | @cindex PowerPC64 OPD optimization | |
7011 | @kindex --no-opd-optimize | |
7012 | @item --no-opd-optimize | |
7013 | PowerPC64 @command{ld} normally removes @code{.opd} section entries | |
7014 | corresponding to deleted link-once functions, or functions removed by | |
e7fc76dd | 7015 | the action of @samp{--gc-sections} or linker script @code{/DISCARD/}. |
2a60a7a8 AM |
7016 | Use this option to disable @code{.opd} optimization. |
7017 | ||
7018 | @cindex PowerPC64 OPD spacing | |
7019 | @kindex --non-overlapping-opd | |
7020 | @item --non-overlapping-opd | |
7021 | Some PowerPC64 compilers have an option to generate compressed | |
7022 | @code{.opd} entries spaced 16 bytes apart, overlapping the third word, | |
7023 | the static chain pointer (unused in C) with the first word of the next | |
7024 | entry. This option expands such entries to the full 24 bytes. | |
7025 | ||
7026 | @cindex PowerPC64 TOC optimization | |
7027 | @kindex --no-toc-optimize | |
7028 | @item --no-toc-optimize | |
7029 | PowerPC64 @command{ld} normally removes unused @code{.toc} section | |
7030 | entries. Such entries are detected by examining relocations that | |
7031 | reference the TOC in code sections. A reloc in a deleted code section | |
7032 | marks a TOC word as unneeded, while a reloc in a kept code section | |
7033 | marks a TOC word as needed. Since the TOC may reference itself, TOC | |
7034 | relocs are also examined. TOC words marked as both needed and | |
7035 | unneeded will of course be kept. TOC words without any referencing | |
7036 | reloc are assumed to be part of a multi-word entry, and are kept or | |
7037 | discarded as per the nearest marked preceding word. This works | |
7038 | reliably for compiler generated code, but may be incorrect if assembly | |
7039 | code is used to insert TOC entries. Use this option to disable the | |
7040 | optimization. | |
7041 | ||
7042 | @cindex PowerPC64 multi-TOC | |
7043 | @kindex --no-multi-toc | |
7044 | @item --no-multi-toc | |
794e51c0 AM |
7045 | If given any toc option besides @code{-mcmodel=medium} or |
7046 | @code{-mcmodel=large}, PowerPC64 GCC generates code for a TOC model | |
7047 | where TOC | |
2a60a7a8 AM |
7048 | entries are accessed with a 16-bit offset from r2. This limits the |
7049 | total TOC size to 64K. PowerPC64 @command{ld} extends this limit by | |
7050 | grouping code sections such that each group uses less than 64K for its | |
7051 | TOC entries, then inserts r2 adjusting stubs between inter-group | |
7052 | calls. @command{ld} does not split apart input sections, so cannot | |
7053 | help if a single input file has a @code{.toc} section that exceeds | |
7054 | 64K, most likely from linking multiple files with @command{ld -r}. | |
7055 | Use this option to turn off this feature. | |
794e51c0 AM |
7056 | |
7057 | @cindex PowerPC64 TOC sorting | |
7058 | @kindex --no-toc-sort | |
7059 | @item --no-toc-sort | |
7060 | By default, @command{ld} sorts TOC sections so that those whose file | |
7061 | happens to have a section called @code{.init} or @code{.fini} are | |
7062 | placed first, followed by TOC sections referenced by code generated | |
7063 | with PowerPC64 gcc's @code{-mcmodel=small}, and lastly TOC sections | |
7064 | referenced only by code generated with PowerPC64 gcc's | |
7065 | @code{-mcmodel=medium} or @code{-mcmodel=large} options. Doing this | |
7066 | results in better TOC grouping for multi-TOC. Use this option to turn | |
7067 | off this feature. | |
7068 | ||
7069 | @cindex PowerPC64 PLT stub alignment | |
7070 | @kindex --plt-align | |
7071 | @kindex --no-plt-align | |
7072 | @item --plt-align | |
7073 | @itemx --no-plt-align | |
7074 | Use these options to control whether individual PLT call stubs are | |
e05fa0ba AM |
7075 | padded so that they don't cross a 32-byte boundary, or to the |
7076 | specified power of two boundary when using @code{--plt-align=}. Note | |
7077 | that this isn't alignment in the usual sense. By default PLT call | |
7078 | stubs are packed tightly. | |
794e51c0 AM |
7079 | |
7080 | @cindex PowerPC64 PLT call stub static chain | |
7081 | @kindex --plt-static-chain | |
7082 | @kindex --no-plt-static-chain | |
7083 | @item --plt-static-chain | |
7084 | @itemx --no-plt-static-chain | |
7085 | Use these options to control whether PLT call stubs load the static | |
7086 | chain pointer (r11). @code{ld} defaults to not loading the static | |
7087 | chain since there is never any need to do so on a PLT call. | |
7088 | ||
7089 | @cindex PowerPC64 PLT call stub thread safety | |
7090 | @kindex --plt-thread-safe | |
7091 | @kindex --no-plt-thread-safe | |
7092 | @item --plt-thread-safe | |
7093 | @itemx --no-thread-safe | |
7094 | With power7's weakly ordered memory model, it is possible when using | |
7095 | lazy binding for ld.so to update a plt entry in one thread and have | |
7096 | another thread see the individual plt entry words update in the wrong | |
7097 | order, despite ld.so carefully writing in the correct order and using | |
7098 | memory write barriers. To avoid this we need some sort of read | |
7099 | barrier in the call stub, or use LD_BIND_NOW=1. By default, @code{ld} | |
7100 | looks for calls to commonly used functions that create threads, and if | |
7101 | seen, adds the necessary barriers. Use these options to change the | |
7102 | default behaviour. | |
2a60a7a8 AM |
7103 | @end table |
7104 | ||
7105 | @ifclear GENERIC | |
7106 | @lowersections | |
7107 | @end ifclear | |
7108 | @end ifset | |
7109 | ||
49fa1e15 AM |
7110 | @ifset SPU |
7111 | @ifclear GENERIC | |
7112 | @raisesections | |
7113 | @end ifclear | |
7114 | ||
7115 | @node SPU ELF | |
7116 | @section @command{ld} and SPU ELF Support | |
7117 | ||
7118 | @cindex SPU ELF options | |
7119 | @table @option | |
7120 | ||
7121 | @cindex SPU plugins | |
7122 | @kindex --plugin | |
7123 | @item --plugin | |
7124 | This option marks an executable as a PIC plugin module. | |
7125 | ||
7126 | @cindex SPU overlays | |
7127 | @kindex --no-overlays | |
7128 | @item --no-overlays | |
7129 | Normally, @command{ld} recognizes calls to functions within overlay | |
7130 | regions, and redirects such calls to an overlay manager via a stub. | |
7131 | @command{ld} also provides a built-in overlay manager. This option | |
7132 | turns off all this special overlay handling. | |
7133 | ||
7134 | @cindex SPU overlay stub symbols | |
7135 | @kindex --emit-stub-syms | |
7136 | @item --emit-stub-syms | |
7137 | This option causes @command{ld} to label overlay stubs with a local | |
7138 | symbol that encodes the stub type and destination. | |
7139 | ||
7140 | @cindex SPU extra overlay stubs | |
7141 | @kindex --extra-overlay-stubs | |
7142 | @item --extra-overlay-stubs | |
7143 | This option causes @command{ld} to add overlay call stubs on all | |
7144 | function calls out of overlay regions. Normally stubs are not added | |
7145 | on calls to non-overlay regions. | |
7146 | ||
7147 | @cindex SPU local store size | |
7148 | @kindex --local-store=lo:hi | |
7149 | @item --local-store=lo:hi | |
7150 | @command{ld} usually checks that a final executable for SPU fits in | |
7151 | the address range 0 to 256k. This option may be used to change the | |
7152 | range. Disable the check entirely with @option{--local-store=0:0}. | |
7153 | ||
c0065db7 | 7154 | @cindex SPU |
49fa1e15 AM |
7155 | @kindex --stack-analysis |
7156 | @item --stack-analysis | |
7157 | SPU local store space is limited. Over-allocation of stack space | |
7158 | unnecessarily limits space available for code and data, while | |
7159 | under-allocation results in runtime failures. If given this option, | |
7160 | @command{ld} will provide an estimate of maximum stack usage. | |
7161 | @command{ld} does this by examining symbols in code sections to | |
7162 | determine the extents of functions, and looking at function prologues | |
7163 | for stack adjusting instructions. A call-graph is created by looking | |
7164 | for relocations on branch instructions. The graph is then searched | |
7165 | for the maximum stack usage path. Note that this analysis does not | |
7166 | find calls made via function pointers, and does not handle recursion | |
7167 | and other cycles in the call graph. Stack usage may be | |
7168 | under-estimated if your code makes such calls. Also, stack usage for | |
7169 | dynamic allocation, e.g. alloca, will not be detected. If a link map | |
7170 | is requested, detailed information about each function's stack usage | |
7171 | and calls will be given. | |
7172 | ||
c0065db7 | 7173 | @cindex SPU |
49fa1e15 AM |
7174 | @kindex --emit-stack-syms |
7175 | @item --emit-stack-syms | |
7176 | This option, if given along with @option{--stack-analysis} will result | |
7177 | in @command{ld} emitting stack sizing symbols for each function. | |
7178 | These take the form @code{__stack_<function_name>} for global | |
7179 | functions, and @code{__stack_<number>_<function_name>} for static | |
7180 | functions. @code{<number>} is the section id in hex. The value of | |
7181 | such symbols is the stack requirement for the corresponding function. | |
7182 | The symbol size will be zero, type @code{STT_NOTYPE}, binding | |
c0065db7 | 7183 | @code{STB_LOCAL}, and section @code{SHN_ABS}. |
49fa1e15 AM |
7184 | @end table |
7185 | ||
7186 | @ifclear GENERIC | |
7187 | @lowersections | |
7188 | @end ifclear | |
7189 | @end ifset | |
7190 | ||
36f63dca NC |
7191 | @ifset TICOFF |
7192 | @ifclear GENERIC | |
7193 | @raisesections | |
7194 | @end ifclear | |
7195 | ||
7196 | @node TI COFF | |
7197 | @section @command{ld}'s Support for Various TI COFF Versions | |
7198 | @cindex TI COFF versions | |
7199 | @kindex --format=@var{version} | |
7200 | The @samp{--format} switch allows selection of one of the various | |
7201 | TI COFF versions. The latest of this writing is 2; versions 0 and 1 are | |
7202 | also supported. The TI COFF versions also vary in header byte-order | |
7203 | format; @command{ld} will read any version or byte order, but the output | |
7204 | header format depends on the default specified by the specific target. | |
7205 | ||
7206 | @ifclear GENERIC | |
7207 | @lowersections | |
7208 | @end ifclear | |
7209 | @end ifset | |
7210 | ||
2ca22b03 NC |
7211 | @ifset WIN32 |
7212 | @ifclear GENERIC | |
7213 | @raisesections | |
7214 | @end ifclear | |
7215 | ||
7216 | @node WIN32 | |
7217 | @section @command{ld} and WIN32 (cygwin/mingw) | |
7218 | ||
c0065db7 | 7219 | This section describes some of the win32 specific @command{ld} issues. |
b45619c0 | 7220 | See @ref{Options,,Command Line Options} for detailed description of the |
dc8465bf | 7221 | command line options mentioned here. |
2ca22b03 NC |
7222 | |
7223 | @table @emph | |
c0065db7 RM |
7224 | @cindex import libraries |
7225 | @item import libraries | |
69da35b5 | 7226 | The standard Windows linker creates and uses so-called import |
2ca22b03 | 7227 | libraries, which contains information for linking to dll's. They are |
69da35b5 NC |
7228 | regular static archives and are handled as any other static |
7229 | archive. The cygwin and mingw ports of @command{ld} have specific | |
2ca22b03 NC |
7230 | support for creating such libraries provided with the |
7231 | @samp{--out-implib} command line option. | |
7232 | ||
c0065db7 RM |
7233 | @item exporting DLL symbols |
7234 | @cindex exporting DLL symbols | |
dc8465bf NC |
7235 | The cygwin/mingw @command{ld} has several ways to export symbols for dll's. |
7236 | ||
7237 | @table @emph | |
7238 | @item using auto-export functionality | |
7239 | @cindex using auto-export functionality | |
7240 | By default @command{ld} exports symbols with the auto-export functionality, | |
7241 | which is controlled by the following command line options: | |
7242 | ||
0a5d968e NC |
7243 | @itemize |
7244 | @item --export-all-symbols [This is the default] | |
7245 | @item --exclude-symbols | |
7246 | @item --exclude-libs | |
e1c37eb5 | 7247 | @item --exclude-modules-for-implib |
09e2aba4 | 7248 | @item --version-script |
0a5d968e NC |
7249 | @end itemize |
7250 | ||
09e2aba4 DK |
7251 | When auto-export is in operation, @command{ld} will export all the non-local |
7252 | (global and common) symbols it finds in a DLL, with the exception of a few | |
7253 | symbols known to belong to the system's runtime and libraries. As it will | |
7254 | often not be desirable to export all of a DLL's symbols, which may include | |
7255 | private functions that are not part of any public interface, the command-line | |
9d5777a3 | 7256 | options listed above may be used to filter symbols out from the list for |
09e2aba4 DK |
7257 | exporting. The @samp{--output-def} option can be used in order to see the |
7258 | final list of exported symbols with all exclusions taken into effect. | |
7259 | ||
7260 | If @samp{--export-all-symbols} is not given explicitly on the | |
0a5d968e NC |
7261 | command line, then the default auto-export behavior will be @emph{disabled} |
7262 | if either of the following are true: | |
7263 | ||
7264 | @itemize | |
7265 | @item A DEF file is used. | |
7266 | @item Any symbol in any object file was marked with the __declspec(dllexport) attribute. | |
7267 | @end itemize | |
dc8465bf | 7268 | |
c0065db7 RM |
7269 | @item using a DEF file |
7270 | @cindex using a DEF file | |
dc8465bf NC |
7271 | Another way of exporting symbols is using a DEF file. A DEF file is |
7272 | an ASCII file containing definitions of symbols which should be | |
7273 | exported when a dll is created. Usually it is named @samp{<dll | |
7274 | name>.def} and is added as any other object file to the linker's | |
0a5d968e | 7275 | command line. The file's name must end in @samp{.def} or @samp{.DEF}. |
dc8465bf NC |
7276 | |
7277 | @example | |
7278 | gcc -o <output> <objectfiles> <dll name>.def | |
7279 | @end example | |
7280 | ||
0a5d968e NC |
7281 | Using a DEF file turns off the normal auto-export behavior, unless the |
7282 | @samp{--export-all-symbols} option is also used. | |
7283 | ||
dc8465bf NC |
7284 | Here is an example of a DEF file for a shared library called @samp{xyz.dll}: |
7285 | ||
7286 | @example | |
4b5bd4e7 | 7287 | LIBRARY "xyz.dll" BASE=0x20000000 |
dc8465bf NC |
7288 | |
7289 | EXPORTS | |
7290 | foo | |
7291 | bar | |
7292 | _bar = bar | |
4b5bd4e7 DS |
7293 | another_foo = abc.dll.afoo |
7294 | var1 DATA | |
7fcab871 KT |
7295 | doo = foo == foo2 |
7296 | eoo DATA == var1 | |
c0065db7 | 7297 | @end example |
dc8465bf | 7298 | |
7fcab871 | 7299 | This example defines a DLL with a non-default base address and seven |
4b5bd4e7 DS |
7300 | symbols in the export table. The third exported symbol @code{_bar} is an |
7301 | alias for the second. The fourth symbol, @code{another_foo} is resolved | |
7302 | by "forwarding" to another module and treating it as an alias for | |
7303 | @code{afoo} exported from the DLL @samp{abc.dll}. The final symbol | |
7fcab871 KT |
7304 | @code{var1} is declared to be a data object. The @samp{doo} symbol in |
7305 | export library is an alias of @samp{foo}, which gets the string name | |
7306 | in export table @samp{foo2}. The @samp{eoo} symbol is an data export | |
7307 | symbol, which gets in export table the name @samp{var1}. | |
4b5bd4e7 | 7308 | |
6b31ad16 DS |
7309 | The optional @code{LIBRARY <name>} command indicates the @emph{internal} |
7310 | name of the output DLL. If @samp{<name>} does not include a suffix, | |
7311 | the default library suffix, @samp{.DLL} is appended. | |
7312 | ||
b45619c0 NC |
7313 | When the .DEF file is used to build an application, rather than a |
7314 | library, the @code{NAME <name>} command should be used instead of | |
6b31ad16 | 7315 | @code{LIBRARY}. If @samp{<name>} does not include a suffix, the default |
c0065db7 | 7316 | executable suffix, @samp{.EXE} is appended. |
6b31ad16 DS |
7317 | |
7318 | With either @code{LIBRARY <name>} or @code{NAME <name>} the optional | |
7319 | specification @code{BASE = <number>} may be used to specify a | |
c0065db7 | 7320 | non-default base address for the image. |
6b31ad16 DS |
7321 | |
7322 | If neither @code{LIBRARY <name>} nor @code{NAME <name>} is specified, | |
a2877985 DS |
7323 | or they specify an empty string, the internal name is the same as the |
7324 | filename specified on the command line. | |
6b31ad16 | 7325 | |
4b5bd4e7 DS |
7326 | The complete specification of an export symbol is: |
7327 | ||
7328 | @example | |
7329 | EXPORTS | |
7330 | ( ( ( <name1> [ = <name2> ] ) | |
7331 | | ( <name1> = <module-name> . <external-name>)) | |
7fcab871 | 7332 | [ @@ <integer> ] [NONAME] [DATA] [CONSTANT] [PRIVATE] [== <name3>] ) * |
c0065db7 | 7333 | @end example |
4b5bd4e7 DS |
7334 | |
7335 | Declares @samp{<name1>} as an exported symbol from the DLL, or declares | |
7336 | @samp{<name1>} as an exported alias for @samp{<name2>}; or declares | |
7337 | @samp{<name1>} as a "forward" alias for the symbol | |
7338 | @samp{<external-name>} in the DLL @samp{<module-name>}. | |
7339 | Optionally, the symbol may be exported by the specified ordinal | |
7fcab871 KT |
7340 | @samp{<integer>} alias. The optional @samp{<name3>} is the to be used |
7341 | string in import/export table for the symbol. | |
4b5bd4e7 DS |
7342 | |
7343 | The optional keywords that follow the declaration indicate: | |
7344 | ||
7345 | @code{NONAME}: Do not put the symbol name in the DLL's export table. It | |
7346 | will still be exported by its ordinal alias (either the value specified | |
7347 | by the .def specification or, otherwise, the value assigned by the | |
7348 | linker). The symbol name, however, does remain visible in the import | |
7349 | library (if any), unless @code{PRIVATE} is also specified. | |
7350 | ||
7351 | @code{DATA}: The symbol is a variable or object, rather than a function. | |
7352 | The import lib will export only an indirect reference to @code{foo} as | |
7353 | the symbol @code{_imp__foo} (ie, @code{foo} must be resolved as | |
7354 | @code{*_imp__foo}). | |
7355 | ||
7356 | @code{CONSTANT}: Like @code{DATA}, but put the undecorated @code{foo} as | |
7357 | well as @code{_imp__foo} into the import library. Both refer to the | |
7358 | read-only import address table's pointer to the variable, not to the | |
7359 | variable itself. This can be dangerous. If the user code fails to add | |
7360 | the @code{dllimport} attribute and also fails to explicitly add the | |
7361 | extra indirection that the use of the attribute enforces, the | |
7362 | application will behave unexpectedly. | |
7363 | ||
7364 | @code{PRIVATE}: Put the symbol in the DLL's export table, but do not put | |
7365 | it into the static import library used to resolve imports at link time. The | |
7366 | symbol can still be imported using the @code{LoadLibrary/GetProcAddress} | |
7367 | API at runtime or by by using the GNU ld extension of linking directly to | |
7368 | the DLL without an import library. | |
c0065db7 | 7369 | |
4b5bd4e7 DS |
7370 | See ld/deffilep.y in the binutils sources for the full specification of |
7371 | other DEF file statements | |
dc8465bf NC |
7372 | |
7373 | @cindex creating a DEF file | |
7374 | While linking a shared dll, @command{ld} is able to create a DEF file | |
7375 | with the @samp{--output-def <file>} command line option. | |
0a5d968e NC |
7376 | |
7377 | @item Using decorations | |
7378 | @cindex Using decorations | |
7379 | Another way of marking symbols for export is to modify the source code | |
7380 | itself, so that when building the DLL each symbol to be exported is | |
7381 | declared as: | |
7382 | ||
7383 | @example | |
7384 | __declspec(dllexport) int a_variable | |
7385 | __declspec(dllexport) void a_function(int with_args) | |
7386 | @end example | |
7387 | ||
7388 | All such symbols will be exported from the DLL. If, however, | |
7389 | any of the object files in the DLL contain symbols decorated in | |
7390 | this way, then the normal auto-export behavior is disabled, unless | |
7391 | the @samp{--export-all-symbols} option is also used. | |
7392 | ||
7393 | Note that object files that wish to access these symbols must @emph{not} | |
c0065db7 | 7394 | decorate them with dllexport. Instead, they should use dllimport, |
0a5d968e NC |
7395 | instead: |
7396 | ||
7397 | @example | |
7398 | __declspec(dllimport) int a_variable | |
7399 | __declspec(dllimport) void a_function(int with_args) | |
7400 | @end example | |
7401 | ||
c0065db7 RM |
7402 | This complicates the structure of library header files, because |
7403 | when included by the library itself the header must declare the | |
0a5d968e NC |
7404 | variables and functions as dllexport, but when included by client |
7405 | code the header must declare them as dllimport. There are a number | |
c0065db7 | 7406 | of idioms that are typically used to do this; often client code can |
0a5d968e NC |
7407 | omit the __declspec() declaration completely. See |
7408 | @samp{--enable-auto-import} and @samp{automatic data imports} for more | |
b45619c0 | 7409 | information. |
c0065db7 | 7410 | @end table |
dc8465bf | 7411 | |
2ca22b03 NC |
7412 | @cindex automatic data imports |
7413 | @item automatic data imports | |
7414 | The standard Windows dll format supports data imports from dlls only | |
69da35b5 | 7415 | by adding special decorations (dllimport/dllexport), which let the |
2ca22b03 | 7416 | compiler produce specific assembler instructions to deal with this |
c0065db7 | 7417 | issue. This increases the effort necessary to port existing Un*x |
69da35b5 | 7418 | code to these platforms, especially for large |
2ca22b03 | 7419 | c++ libraries and applications. The auto-import feature, which was |
c0065db7 | 7420 | initially provided by Paul Sokolovsky, allows one to omit the |
b45619c0 | 7421 | decorations to achieve a behavior that conforms to that on POSIX/Un*x |
c0065db7 | 7422 | platforms. This feature is enabled with the @samp{--enable-auto-import} |
69da35b5 NC |
7423 | command-line option, although it is enabled by default on cygwin/mingw. |
7424 | The @samp{--enable-auto-import} option itself now serves mainly to | |
7425 | suppress any warnings that are ordinarily emitted when linked objects | |
7426 | trigger the feature's use. | |
7427 | ||
c0065db7 | 7428 | auto-import of variables does not always work flawlessly without |
69da35b5 NC |
7429 | additional assistance. Sometimes, you will see this message |
7430 | ||
c0065db7 | 7431 | "variable '<var>' can't be auto-imported. Please read the |
69da35b5 NC |
7432 | documentation for ld's @code{--enable-auto-import} for details." |
7433 | ||
c0065db7 RM |
7434 | The @samp{--enable-auto-import} documentation explains why this error |
7435 | occurs, and several methods that can be used to overcome this difficulty. | |
7436 | One of these methods is the @emph{runtime pseudo-relocs} feature, described | |
69da35b5 NC |
7437 | below. |
7438 | ||
7439 | @cindex runtime pseudo-relocation | |
c0065db7 RM |
7440 | For complex variables imported from DLLs (such as structs or classes), |
7441 | object files typically contain a base address for the variable and an | |
7442 | offset (@emph{addend}) within the variable--to specify a particular | |
7443 | field or public member, for instance. Unfortunately, the runtime loader used | |
7444 | in win32 environments is incapable of fixing these references at runtime | |
69da35b5 | 7445 | without the additional information supplied by dllimport/dllexport decorations. |
c0065db7 | 7446 | The standard auto-import feature described above is unable to resolve these |
69da35b5 NC |
7447 | references. |
7448 | ||
c0065db7 RM |
7449 | The @samp{--enable-runtime-pseudo-relocs} switch allows these references to |
7450 | be resolved without error, while leaving the task of adjusting the references | |
7451 | themselves (with their non-zero addends) to specialized code provided by the | |
7452 | runtime environment. Recent versions of the cygwin and mingw environments and | |
7453 | compilers provide this runtime support; older versions do not. However, the | |
7454 | support is only necessary on the developer's platform; the compiled result will | |
69da35b5 NC |
7455 | run without error on an older system. |
7456 | ||
c0065db7 RM |
7457 | @samp{--enable-runtime-pseudo-relocs} is not the default; it must be explicitly |
7458 | enabled as needed. | |
2ca22b03 NC |
7459 | |
7460 | @cindex direct linking to a dll | |
7461 | @item direct linking to a dll | |
7462 | The cygwin/mingw ports of @command{ld} support the direct linking, | |
7463 | including data symbols, to a dll without the usage of any import | |
69da35b5 | 7464 | libraries. This is much faster and uses much less memory than does the |
b45619c0 | 7465 | traditional import library method, especially when linking large |
c0065db7 RM |
7466 | libraries or applications. When @command{ld} creates an import lib, each |
7467 | function or variable exported from the dll is stored in its own bfd, even | |
7468 | though a single bfd could contain many exports. The overhead involved in | |
69da35b5 | 7469 | storing, loading, and processing so many bfd's is quite large, and explains the |
c0065db7 | 7470 | tremendous time, memory, and storage needed to link against particularly |
69da35b5 NC |
7471 | large or complex libraries when using import libs. |
7472 | ||
c0065db7 | 7473 | Linking directly to a dll uses no extra command-line switches other than |
69da35b5 | 7474 | @samp{-L} and @samp{-l}, because @command{ld} already searches for a number |
c0065db7 | 7475 | of names to match each library. All that is needed from the developer's |
69da35b5 NC |
7476 | perspective is an understanding of this search, in order to force ld to |
7477 | select the dll instead of an import library. | |
7478 | ||
2ca22b03 | 7479 | |
69da35b5 NC |
7480 | For instance, when ld is called with the argument @samp{-lxxx} it will attempt |
7481 | to find, in the first directory of its search path, | |
2ca22b03 NC |
7482 | |
7483 | @example | |
45e948fe NC |
7484 | libxxx.dll.a |
7485 | xxx.dll.a | |
7486 | libxxx.a | |
7487 | xxx.lib | |
69da35b5 | 7488 | cygxxx.dll (*) |
45e948fe NC |
7489 | libxxx.dll |
7490 | xxx.dll | |
2ca22b03 NC |
7491 | @end example |
7492 | ||
69da35b5 NC |
7493 | before moving on to the next directory in the search path. |
7494 | ||
c0065db7 RM |
7495 | (*) Actually, this is not @samp{cygxxx.dll} but in fact is @samp{<prefix>xxx.dll}, |
7496 | where @samp{<prefix>} is set by the @command{ld} option | |
7497 | @samp{--dll-search-prefix=<prefix>}. In the case of cygwin, the standard gcc spec | |
7498 | file includes @samp{--dll-search-prefix=cyg}, so in effect we actually search for | |
69da35b5 NC |
7499 | @samp{cygxxx.dll}. |
7500 | ||
c0065db7 RM |
7501 | Other win32-based unix environments, such as mingw or pw32, may use other |
7502 | @samp{<prefix>}es, although at present only cygwin makes use of this feature. It | |
69da35b5 NC |
7503 | was originally intended to help avoid name conflicts among dll's built for the |
7504 | various win32/un*x environments, so that (for example) two versions of a zlib dll | |
7505 | could coexist on the same machine. | |
7506 | ||
2ca22b03 NC |
7507 | The generic cygwin/mingw path layout uses a @samp{bin} directory for |
7508 | applications and dll's and a @samp{lib} directory for the import | |
69da35b5 | 7509 | libraries (using cygwin nomenclature): |
2ca22b03 NC |
7510 | |
7511 | @example | |
7512 | bin/ | |
7513 | cygxxx.dll | |
7514 | lib/ | |
7515 | libxxx.dll.a (in case of dll's) | |
c0065db7 | 7516 | libxxx.a (in case of static archive) |
2ca22b03 NC |
7517 | @end example |
7518 | ||
c0065db7 RM |
7519 | Linking directly to a dll without using the import library can be |
7520 | done two ways: | |
2ca22b03 NC |
7521 | |
7522 | 1. Use the dll directly by adding the @samp{bin} path to the link line | |
7523 | @example | |
7524 | gcc -Wl,-verbose -o a.exe -L../bin/ -lxxx | |
c0065db7 | 7525 | @end example |
2ca22b03 | 7526 | |
69da35b5 NC |
7527 | However, as the dll's often have version numbers appended to their names |
7528 | (@samp{cygncurses-5.dll}) this will often fail, unless one specifies | |
7529 | @samp{-L../bin -lncurses-5} to include the version. Import libs are generally | |
7530 | not versioned, and do not have this difficulty. | |
7531 | ||
2ca22b03 NC |
7532 | 2. Create a symbolic link from the dll to a file in the @samp{lib} |
7533 | directory according to the above mentioned search pattern. This | |
7534 | should be used to avoid unwanted changes in the tools needed for | |
7535 | making the app/dll. | |
7536 | ||
7537 | @example | |
7538 | ln -s bin/cygxxx.dll lib/[cyg|lib|]xxx.dll[.a] | |
c0065db7 | 7539 | @end example |
2ca22b03 NC |
7540 | |
7541 | Then you can link without any make environment changes. | |
7542 | ||
7543 | @example | |
7544 | gcc -Wl,-verbose -o a.exe -L../lib/ -lxxx | |
c0065db7 | 7545 | @end example |
69da35b5 NC |
7546 | |
7547 | This technique also avoids the version number problems, because the following is | |
7548 | perfectly legal | |
7549 | ||
7550 | @example | |
7551 | bin/ | |
7552 | cygxxx-5.dll | |
7553 | lib/ | |
c0065db7 | 7554 | libxxx.dll.a -> ../bin/cygxxx-5.dll |
69da35b5 NC |
7555 | @end example |
7556 | ||
dc8465bf | 7557 | Linking directly to a dll without using an import lib will work |
69da35b5 NC |
7558 | even when auto-import features are exercised, and even when |
7559 | @samp{--enable-runtime-pseudo-relocs} is used. | |
7560 | ||
7561 | Given the improvements in speed and memory usage, one might justifiably | |
45e948fe | 7562 | wonder why import libraries are used at all. There are three reasons: |
69da35b5 NC |
7563 | |
7564 | 1. Until recently, the link-directly-to-dll functionality did @emph{not} | |
7565 | work with auto-imported data. | |
7566 | ||
dc8465bf NC |
7567 | 2. Sometimes it is necessary to include pure static objects within the |
7568 | import library (which otherwise contains only bfd's for indirection | |
7569 | symbols that point to the exports of a dll). Again, the import lib | |
7570 | for the cygwin kernel makes use of this ability, and it is not | |
7571 | possible to do this without an import lib. | |
69da35b5 | 7572 | |
45e948fe NC |
7573 | 3. Symbol aliases can only be resolved using an import lib. This is |
7574 | critical when linking against OS-supplied dll's (eg, the win32 API) | |
7575 | in which symbols are usually exported as undecorated aliases of their | |
7576 | stdcall-decorated assembly names. | |
7577 | ||
69da35b5 | 7578 | So, import libs are not going away. But the ability to replace |
c0065db7 RM |
7579 | true import libs with a simple symbolic link to (or a copy of) |
7580 | a dll, in many cases, is a useful addition to the suite of tools | |
7581 | binutils makes available to the win32 developer. Given the | |
69da35b5 NC |
7582 | massive improvements in memory requirements during linking, storage |
7583 | requirements, and linking speed, we expect that many developers | |
7584 | will soon begin to use this feature whenever possible. | |
dc8465bf | 7585 | |
c0065db7 | 7586 | @item symbol aliasing |
dc8465bf | 7587 | @table @emph |
c0065db7 RM |
7588 | @item adding additional names |
7589 | Sometimes, it is useful to export symbols with additional names. | |
dc8465bf NC |
7590 | A symbol @samp{foo} will be exported as @samp{foo}, but it can also be |
7591 | exported as @samp{_foo} by using special directives in the DEF file | |
7592 | when creating the dll. This will affect also the optional created | |
c0065db7 | 7593 | import library. Consider the following DEF file: |
dc8465bf | 7594 | |
c0065db7 | 7595 | @example |
dc8465bf NC |
7596 | LIBRARY "xyz.dll" BASE=0x61000000 |
7597 | ||
7598 | EXPORTS | |
c0065db7 | 7599 | foo |
dc8465bf | 7600 | _foo = foo |
c0065db7 | 7601 | @end example |
dc8465bf NC |
7602 | |
7603 | The line @samp{_foo = foo} maps the symbol @samp{foo} to @samp{_foo}. | |
7604 | ||
7605 | Another method for creating a symbol alias is to create it in the | |
7606 | source code using the "weak" attribute: | |
7607 | ||
c0065db7 RM |
7608 | @example |
7609 | void foo () @{ /* Do something. */; @} | |
dc8465bf | 7610 | void _foo () __attribute__ ((weak, alias ("foo"))); |
c0065db7 | 7611 | @end example |
dc8465bf NC |
7612 | |
7613 | See the gcc manual for more information about attributes and weak | |
7614 | symbols. | |
7615 | ||
7616 | @item renaming symbols | |
7617 | Sometimes it is useful to rename exports. For instance, the cygwin | |
c0065db7 | 7618 | kernel does this regularly. A symbol @samp{_foo} can be exported as |
dc8465bf NC |
7619 | @samp{foo} but not as @samp{_foo} by using special directives in the |
7620 | DEF file. (This will also affect the import library, if it is | |
c0065db7 | 7621 | created). In the following example: |
dc8465bf | 7622 | |
c0065db7 | 7623 | @example |
dc8465bf NC |
7624 | LIBRARY "xyz.dll" BASE=0x61000000 |
7625 | ||
7626 | EXPORTS | |
7627 | _foo = foo | |
c0065db7 | 7628 | @end example |
dc8465bf NC |
7629 | |
7630 | The line @samp{_foo = foo} maps the exported symbol @samp{foo} to | |
7631 | @samp{_foo}. | |
c0065db7 | 7632 | @end table |
dc8465bf | 7633 | |
0a5d968e | 7634 | Note: using a DEF file disables the default auto-export behavior, |
c0065db7 | 7635 | unless the @samp{--export-all-symbols} command line option is used. |
0a5d968e | 7636 | If, however, you are trying to rename symbols, then you should list |
c0065db7 RM |
7637 | @emph{all} desired exports in the DEF file, including the symbols |
7638 | that are not being renamed, and do @emph{not} use the | |
7639 | @samp{--export-all-symbols} option. If you list only the | |
7640 | renamed symbols in the DEF file, and use @samp{--export-all-symbols} | |
7641 | to handle the other symbols, then the both the new names @emph{and} | |
7642 | the original names for the renamed symbols will be exported. | |
7643 | In effect, you'd be aliasing those symbols, not renaming them, | |
0a5d968e | 7644 | which is probably not what you wanted. |
c87db184 CF |
7645 | |
7646 | @cindex weak externals | |
7647 | @item weak externals | |
7648 | The Windows object format, PE, specifies a form of weak symbols called | |
7649 | weak externals. When a weak symbol is linked and the symbol is not | |
7650 | defined, the weak symbol becomes an alias for some other symbol. There | |
7651 | are three variants of weak externals: | |
7652 | @itemize | |
7653 | @item Definition is searched for in objects and libraries, historically | |
7654 | called lazy externals. | |
7655 | @item Definition is searched for only in other objects, not in libraries. | |
7656 | This form is not presently implemented. | |
7657 | @item No search; the symbol is an alias. This form is not presently | |
7658 | implemented. | |
7659 | @end itemize | |
7660 | As a GNU extension, weak symbols that do not specify an alternate symbol | |
7661 | are supported. If the symbol is undefined when linking, the symbol | |
7662 | uses a default value. | |
c1711530 DK |
7663 | |
7664 | @cindex aligned common symbols | |
7665 | @item aligned common symbols | |
7666 | As a GNU extension to the PE file format, it is possible to specify the | |
7667 | desired alignment for a common symbol. This information is conveyed from | |
7668 | the assembler or compiler to the linker by means of GNU-specific commands | |
7669 | carried in the object file's @samp{.drectve} section, which are recognized | |
7670 | by @command{ld} and respected when laying out the common symbols. Native | |
7671 | tools will be able to process object files employing this GNU extension, | |
7672 | but will fail to respect the alignment instructions, and may issue noisy | |
7673 | warnings about unknown linker directives. | |
5063daf7 | 7674 | |
2ca22b03 NC |
7675 | @end table |
7676 | ||
7677 | @ifclear GENERIC | |
7678 | @lowersections | |
7679 | @end ifclear | |
7680 | @end ifset | |
7681 | ||
e0001a05 NC |
7682 | @ifset XTENSA |
7683 | @ifclear GENERIC | |
7684 | @raisesections | |
7685 | @end ifclear | |
7686 | ||
7687 | @node Xtensa | |
7688 | @section @code{ld} and Xtensa Processors | |
7689 | ||
7690 | @cindex Xtensa processors | |
7691 | The default @command{ld} behavior for Xtensa processors is to interpret | |
7692 | @code{SECTIONS} commands so that lists of explicitly named sections in a | |
7693 | specification with a wildcard file will be interleaved when necessary to | |
7694 | keep literal pools within the range of PC-relative load offsets. For | |
7695 | example, with the command: | |
7696 | ||
7697 | @smallexample | |
7698 | SECTIONS | |
7699 | @{ | |
7700 | .text : @{ | |
7701 | *(.literal .text) | |
7702 | @} | |
7703 | @} | |
7704 | @end smallexample | |
7705 | ||
7706 | @noindent | |
7707 | @command{ld} may interleave some of the @code{.literal} | |
7708 | and @code{.text} sections from different object files to ensure that the | |
7709 | literal pools are within the range of PC-relative load offsets. A valid | |
7710 | interleaving might place the @code{.literal} sections from an initial | |
7711 | group of files followed by the @code{.text} sections of that group of | |
7712 | files. Then, the @code{.literal} sections from the rest of the files | |
7713 | and the @code{.text} sections from the rest of the files would follow. | |
e0001a05 | 7714 | |
43cd72b9 | 7715 | @cindex @option{--relax} on Xtensa |
e0001a05 | 7716 | @cindex relaxing on Xtensa |
43cd72b9 BW |
7717 | Relaxation is enabled by default for the Xtensa version of @command{ld} and |
7718 | provides two important link-time optimizations. The first optimization | |
7719 | is to combine identical literal values to reduce code size. A redundant | |
7720 | literal will be removed and all the @code{L32R} instructions that use it | |
7721 | will be changed to reference an identical literal, as long as the | |
7722 | location of the replacement literal is within the offset range of all | |
7723 | the @code{L32R} instructions. The second optimization is to remove | |
7724 | unnecessary overhead from assembler-generated ``longcall'' sequences of | |
7725 | @code{L32R}/@code{CALLX@var{n}} when the target functions are within | |
7726 | range of direct @code{CALL@var{n}} instructions. | |
7727 | ||
7728 | For each of these cases where an indirect call sequence can be optimized | |
7729 | to a direct call, the linker will change the @code{CALLX@var{n}} | |
7730 | instruction to a @code{CALL@var{n}} instruction, remove the @code{L32R} | |
7731 | instruction, and remove the literal referenced by the @code{L32R} | |
7732 | instruction if it is not used for anything else. Removing the | |
7733 | @code{L32R} instruction always reduces code size but can potentially | |
7734 | hurt performance by changing the alignment of subsequent branch targets. | |
7735 | By default, the linker will always preserve alignments, either by | |
7736 | switching some instructions between 24-bit encodings and the equivalent | |
7737 | density instructions or by inserting a no-op in place of the @code{L32R} | |
7738 | instruction that was removed. If code size is more important than | |
7739 | performance, the @option{--size-opt} option can be used to prevent the | |
7740 | linker from widening density instructions or inserting no-ops, except in | |
7741 | a few cases where no-ops are required for correctness. | |
7742 | ||
7743 | The following Xtensa-specific command-line options can be used to | |
7744 | control the linker: | |
7745 | ||
7746 | @cindex Xtensa options | |
7747 | @table @option | |
43cd72b9 BW |
7748 | @item --size-opt |
7749 | When optimizing indirect calls to direct calls, optimize for code size | |
7750 | more than performance. With this option, the linker will not insert | |
7751 | no-ops or widen density instructions to preserve branch target | |
7752 | alignment. There may still be some cases where no-ops are required to | |
7753 | preserve the correctness of the code. | |
7754 | @end table | |
e0001a05 NC |
7755 | |
7756 | @ifclear GENERIC | |
7757 | @lowersections | |
7758 | @end ifclear | |
7759 | @end ifset | |
7760 | ||
252b5132 RH |
7761 | @ifclear SingleFormat |
7762 | @node BFD | |
7763 | @chapter BFD | |
7764 | ||
7765 | @cindex back end | |
7766 | @cindex object file management | |
7767 | @cindex object formats available | |
7768 | @kindex objdump -i | |
7769 | The linker accesses object and archive files using the BFD libraries. | |
7770 | These libraries allow the linker to use the same routines to operate on | |
7771 | object files whatever the object file format. A different object file | |
7772 | format can be supported simply by creating a new BFD back end and adding | |
7773 | it to the library. To conserve runtime memory, however, the linker and | |
7774 | associated tools are usually configured to support only a subset of the | |
7775 | object file formats available. You can use @code{objdump -i} | |
7776 | (@pxref{objdump,,objdump,binutils.info,The GNU Binary Utilities}) to | |
7777 | list all the formats available for your configuration. | |
7778 | ||
7779 | @cindex BFD requirements | |
7780 | @cindex requirements for BFD | |
7781 | As with most implementations, BFD is a compromise between | |
7782 | several conflicting requirements. The major factor influencing | |
7783 | BFD design was efficiency: any time used converting between | |
7784 | formats is time which would not have been spent had BFD not | |
7785 | been involved. This is partly offset by abstraction payback; since | |
7786 | BFD simplifies applications and back ends, more time and care | |
7787 | may be spent optimizing algorithms for a greater speed. | |
7788 | ||
7789 | One minor artifact of the BFD solution which you should bear in | |
7790 | mind is the potential for information loss. There are two places where | |
7791 | useful information can be lost using the BFD mechanism: during | |
7792 | conversion and during output. @xref{BFD information loss}. | |
7793 | ||
7794 | @menu | |
7795 | * BFD outline:: How it works: an outline of BFD | |
7796 | @end menu | |
7797 | ||
7798 | @node BFD outline | |
36f63dca | 7799 | @section How It Works: An Outline of BFD |
252b5132 RH |
7800 | @cindex opening object files |
7801 | @include bfdsumm.texi | |
7802 | @end ifclear | |
7803 | ||
7804 | @node Reporting Bugs | |
7805 | @chapter Reporting Bugs | |
ff5dcc92 SC |
7806 | @cindex bugs in @command{ld} |
7807 | @cindex reporting bugs in @command{ld} | |
252b5132 | 7808 | |
ff5dcc92 | 7809 | Your bug reports play an essential role in making @command{ld} reliable. |
252b5132 RH |
7810 | |
7811 | Reporting a bug may help you by bringing a solution to your problem, or | |
7812 | it may not. But in any case the principal function of a bug report is | |
ff5dcc92 | 7813 | to help the entire community by making the next version of @command{ld} |
252b5132 | 7814 | work better. Bug reports are your contribution to the maintenance of |
ff5dcc92 | 7815 | @command{ld}. |
252b5132 RH |
7816 | |
7817 | In order for a bug report to serve its purpose, you must include the | |
7818 | information that enables us to fix the bug. | |
7819 | ||
7820 | @menu | |
7821 | * Bug Criteria:: Have you found a bug? | |
7822 | * Bug Reporting:: How to report bugs | |
7823 | @end menu | |
7824 | ||
7825 | @node Bug Criteria | |
36f63dca | 7826 | @section Have You Found a Bug? |
252b5132 RH |
7827 | @cindex bug criteria |
7828 | ||
7829 | If you are not sure whether you have found a bug, here are some guidelines: | |
7830 | ||
7831 | @itemize @bullet | |
7832 | @cindex fatal signal | |
7833 | @cindex linker crash | |
7834 | @cindex crash of linker | |
7835 | @item | |
7836 | If the linker gets a fatal signal, for any input whatever, that is a | |
ff5dcc92 | 7837 | @command{ld} bug. Reliable linkers never crash. |
252b5132 RH |
7838 | |
7839 | @cindex error on valid input | |
7840 | @item | |
ff5dcc92 | 7841 | If @command{ld} produces an error message for valid input, that is a bug. |
252b5132 RH |
7842 | |
7843 | @cindex invalid input | |
7844 | @item | |
ff5dcc92 | 7845 | If @command{ld} does not produce an error message for invalid input, that |
252b5132 RH |
7846 | may be a bug. In the general case, the linker can not verify that |
7847 | object files are correct. | |
7848 | ||
7849 | @item | |
7850 | If you are an experienced user of linkers, your suggestions for | |
ff5dcc92 | 7851 | improvement of @command{ld} are welcome in any case. |
252b5132 RH |
7852 | @end itemize |
7853 | ||
7854 | @node Bug Reporting | |
36f63dca | 7855 | @section How to Report Bugs |
252b5132 | 7856 | @cindex bug reports |
ff5dcc92 | 7857 | @cindex @command{ld} bugs, reporting |
252b5132 RH |
7858 | |
7859 | A number of companies and individuals offer support for @sc{gnu} | |
ff5dcc92 | 7860 | products. If you obtained @command{ld} from a support organization, we |
252b5132 RH |
7861 | recommend you contact that organization first. |
7862 | ||
7863 | You can find contact information for many support companies and | |
7864 | individuals in the file @file{etc/SERVICE} in the @sc{gnu} Emacs | |
7865 | distribution. | |
7866 | ||
ad22bfe8 | 7867 | @ifset BUGURL |
ff5dcc92 | 7868 | Otherwise, send bug reports for @command{ld} to |
ad22bfe8 JM |
7869 | @value{BUGURL}. |
7870 | @end ifset | |
252b5132 RH |
7871 | |
7872 | The fundamental principle of reporting bugs usefully is this: | |
7873 | @strong{report all the facts}. If you are not sure whether to state a | |
7874 | fact or leave it out, state it! | |
7875 | ||
7876 | Often people omit facts because they think they know what causes the | |
7877 | problem and assume that some details do not matter. Thus, you might | |
b553b183 NC |
7878 | assume that the name of a symbol you use in an example does not |
7879 | matter. Well, probably it does not, but one cannot be sure. Perhaps | |
7880 | the bug is a stray memory reference which happens to fetch from the | |
7881 | location where that name is stored in memory; perhaps, if the name | |
7882 | were different, the contents of that location would fool the linker | |
7883 | into doing the right thing despite the bug. Play it safe and give a | |
7884 | specific, complete example. That is the easiest thing for you to do, | |
c0065db7 | 7885 | and the most helpful. |
b553b183 NC |
7886 | |
7887 | Keep in mind that the purpose of a bug report is to enable us to fix | |
7888 | the bug if it is new to us. Therefore, always write your bug reports | |
7889 | on the assumption that the bug has not been reported previously. | |
252b5132 RH |
7890 | |
7891 | Sometimes people give a few sketchy facts and ask, ``Does this ring a | |
36f63dca NC |
7892 | bell?'' This cannot help us fix a bug, so it is basically useless. We |
7893 | respond by asking for enough details to enable us to investigate. | |
7894 | You might as well expedite matters by sending them to begin with. | |
252b5132 RH |
7895 | |
7896 | To enable us to fix the bug, you should include all these things: | |
7897 | ||
7898 | @itemize @bullet | |
7899 | @item | |
ff5dcc92 | 7900 | The version of @command{ld}. @command{ld} announces it if you start it with |
252b5132 RH |
7901 | the @samp{--version} argument. |
7902 | ||
7903 | Without this, we will not know whether there is any point in looking for | |
ff5dcc92 | 7904 | the bug in the current version of @command{ld}. |
252b5132 RH |
7905 | |
7906 | @item | |
ff5dcc92 | 7907 | Any patches you may have applied to the @command{ld} source, including any |
252b5132 RH |
7908 | patches made to the @code{BFD} library. |
7909 | ||
7910 | @item | |
7911 | The type of machine you are using, and the operating system name and | |
7912 | version number. | |
7913 | ||
7914 | @item | |
ff5dcc92 | 7915 | What compiler (and its version) was used to compile @command{ld}---e.g. |
252b5132 RH |
7916 | ``@code{gcc-2.7}''. |
7917 | ||
7918 | @item | |
7919 | The command arguments you gave the linker to link your example and | |
7920 | observe the bug. To guarantee you will not omit something important, | |
7921 | list them all. A copy of the Makefile (or the output from make) is | |
7922 | sufficient. | |
7923 | ||
7924 | If we were to try to guess the arguments, we would probably guess wrong | |
7925 | and then we might not encounter the bug. | |
7926 | ||
7927 | @item | |
7928 | A complete input file, or set of input files, that will reproduce the | |
b553b183 NC |
7929 | bug. It is generally most helpful to send the actual object files |
7930 | provided that they are reasonably small. Say no more than 10K. For | |
7931 | bigger files you can either make them available by FTP or HTTP or else | |
7932 | state that you are willing to send the object file(s) to whomever | |
7933 | requests them. (Note - your email will be going to a mailing list, so | |
7934 | we do not want to clog it up with large attachments). But small | |
7935 | attachments are best. | |
252b5132 RH |
7936 | |
7937 | If the source files were assembled using @code{gas} or compiled using | |
7938 | @code{gcc}, then it may be OK to send the source files rather than the | |
7939 | object files. In this case, be sure to say exactly what version of | |
7940 | @code{gas} or @code{gcc} was used to produce the object files. Also say | |
7941 | how @code{gas} or @code{gcc} were configured. | |
7942 | ||
7943 | @item | |
7944 | A description of what behavior you observe that you believe is | |
7945 | incorrect. For example, ``It gets a fatal signal.'' | |
7946 | ||
ff5dcc92 | 7947 | Of course, if the bug is that @command{ld} gets a fatal signal, then we |
252b5132 RH |
7948 | will certainly notice it. But if the bug is incorrect output, we might |
7949 | not notice unless it is glaringly wrong. You might as well not give us | |
7950 | a chance to make a mistake. | |
7951 | ||
7952 | Even if the problem you experience is a fatal signal, you should still | |
7953 | say so explicitly. Suppose something strange is going on, such as, your | |
b45619c0 | 7954 | copy of @command{ld} is out of sync, or you have encountered a bug in the |
252b5132 RH |
7955 | C library on your system. (This has happened!) Your copy might crash |
7956 | and ours would not. If you told us to expect a crash, then when ours | |
7957 | fails to crash, we would know that the bug was not happening for us. If | |
7958 | you had not told us to expect a crash, then we would not be able to draw | |
7959 | any conclusion from our observations. | |
7960 | ||
7961 | @item | |
ff5dcc92 | 7962 | If you wish to suggest changes to the @command{ld} source, send us context |
252b5132 RH |
7963 | diffs, as generated by @code{diff} with the @samp{-u}, @samp{-c}, or |
7964 | @samp{-p} option. Always send diffs from the old file to the new file. | |
ff5dcc92 | 7965 | If you even discuss something in the @command{ld} source, refer to it by |
252b5132 RH |
7966 | context, not by line number. |
7967 | ||
7968 | The line numbers in our development sources will not match those in your | |
7969 | sources. Your line numbers would convey no useful information to us. | |
7970 | @end itemize | |
7971 | ||
7972 | Here are some things that are not necessary: | |
7973 | ||
7974 | @itemize @bullet | |
7975 | @item | |
7976 | A description of the envelope of the bug. | |
7977 | ||
7978 | Often people who encounter a bug spend a lot of time investigating | |
7979 | which changes to the input file will make the bug go away and which | |
7980 | changes will not affect it. | |
7981 | ||
7982 | This is often time consuming and not very useful, because the way we | |
7983 | will find the bug is by running a single example under the debugger | |
7984 | with breakpoints, not by pure deduction from a series of examples. | |
7985 | We recommend that you save your time for something else. | |
7986 | ||
7987 | Of course, if you can find a simpler example to report @emph{instead} | |
7988 | of the original one, that is a convenience for us. Errors in the | |
7989 | output will be easier to spot, running under the debugger will take | |
7990 | less time, and so on. | |
7991 | ||
7992 | However, simplification is not vital; if you do not want to do this, | |
7993 | report the bug anyway and send us the entire test case you used. | |
7994 | ||
7995 | @item | |
7996 | A patch for the bug. | |
7997 | ||
7998 | A patch for the bug does help us if it is a good one. But do not omit | |
7999 | the necessary information, such as the test case, on the assumption that | |
8000 | a patch is all we need. We might see problems with your patch and decide | |
8001 | to fix the problem another way, or we might not understand it at all. | |
8002 | ||
ff5dcc92 | 8003 | Sometimes with a program as complicated as @command{ld} it is very hard to |
252b5132 RH |
8004 | construct an example that will make the program follow a certain path |
8005 | through the code. If you do not send us the example, we will not be | |
8006 | able to construct one, so we will not be able to verify that the bug is | |
8007 | fixed. | |
8008 | ||
8009 | And if we cannot understand what bug you are trying to fix, or why your | |
8010 | patch should be an improvement, we will not install it. A test case will | |
8011 | help us to understand. | |
8012 | ||
8013 | @item | |
8014 | A guess about what the bug is or what it depends on. | |
8015 | ||
8016 | Such guesses are usually wrong. Even we cannot guess right about such | |
8017 | things without first using the debugger to find the facts. | |
8018 | @end itemize | |
8019 | ||
8020 | @node MRI | |
8021 | @appendix MRI Compatible Script Files | |
8022 | @cindex MRI compatibility | |
ff5dcc92 SC |
8023 | To aid users making the transition to @sc{gnu} @command{ld} from the MRI |
8024 | linker, @command{ld} can use MRI compatible linker scripts as an | |
252b5132 RH |
8025 | alternative to the more general-purpose linker scripting language |
8026 | described in @ref{Scripts}. MRI compatible linker scripts have a much | |
8027 | simpler command set than the scripting language otherwise used with | |
ff5dcc92 | 8028 | @command{ld}. @sc{gnu} @command{ld} supports the most commonly used MRI |
252b5132 RH |
8029 | linker commands; these commands are described here. |
8030 | ||
8031 | In general, MRI scripts aren't of much use with the @code{a.out} object | |
8032 | file format, since it only has three sections and MRI scripts lack some | |
8033 | features to make use of them. | |
8034 | ||
8035 | You can specify a file containing an MRI-compatible script using the | |
8036 | @samp{-c} command-line option. | |
8037 | ||
8038 | Each command in an MRI-compatible script occupies its own line; each | |
8039 | command line starts with the keyword that identifies the command (though | |
8040 | blank lines are also allowed for punctuation). If a line of an | |
ff5dcc92 | 8041 | MRI-compatible script begins with an unrecognized keyword, @command{ld} |
252b5132 RH |
8042 | issues a warning message, but continues processing the script. |
8043 | ||
8044 | Lines beginning with @samp{*} are comments. | |
8045 | ||
8046 | You can write these commands using all upper-case letters, or all | |
8047 | lower case; for example, @samp{chip} is the same as @samp{CHIP}. | |
8048 | The following list shows only the upper-case form of each command. | |
8049 | ||
8050 | @table @code | |
8051 | @cindex @code{ABSOLUTE} (MRI) | |
8052 | @item ABSOLUTE @var{secname} | |
8053 | @itemx ABSOLUTE @var{secname}, @var{secname}, @dots{} @var{secname} | |
ff5dcc92 | 8054 | Normally, @command{ld} includes in the output file all sections from all |
252b5132 RH |
8055 | the input files. However, in an MRI-compatible script, you can use the |
8056 | @code{ABSOLUTE} command to restrict the sections that will be present in | |
8057 | your output program. If the @code{ABSOLUTE} command is used at all in a | |
8058 | script, then only the sections named explicitly in @code{ABSOLUTE} | |
8059 | commands will appear in the linker output. You can still use other | |
8060 | input sections (whatever you select on the command line, or using | |
8061 | @code{LOAD}) to resolve addresses in the output file. | |
8062 | ||
8063 | @cindex @code{ALIAS} (MRI) | |
8064 | @item ALIAS @var{out-secname}, @var{in-secname} | |
8065 | Use this command to place the data from input section @var{in-secname} | |
8066 | in a section called @var{out-secname} in the linker output file. | |
8067 | ||
8068 | @var{in-secname} may be an integer. | |
8069 | ||
8070 | @cindex @code{ALIGN} (MRI) | |
8071 | @item ALIGN @var{secname} = @var{expression} | |
8072 | Align the section called @var{secname} to @var{expression}. The | |
8073 | @var{expression} should be a power of two. | |
8074 | ||
8075 | @cindex @code{BASE} (MRI) | |
8076 | @item BASE @var{expression} | |
8077 | Use the value of @var{expression} as the lowest address (other than | |
8078 | absolute addresses) in the output file. | |
8079 | ||
8080 | @cindex @code{CHIP} (MRI) | |
8081 | @item CHIP @var{expression} | |
8082 | @itemx CHIP @var{expression}, @var{expression} | |
8083 | This command does nothing; it is accepted only for compatibility. | |
8084 | ||
8085 | @cindex @code{END} (MRI) | |
8086 | @item END | |
8087 | This command does nothing whatever; it's only accepted for compatibility. | |
8088 | ||
8089 | @cindex @code{FORMAT} (MRI) | |
8090 | @item FORMAT @var{output-format} | |
8091 | Similar to the @code{OUTPUT_FORMAT} command in the more general linker | |
a1ab1d2a | 8092 | language, but restricted to one of these output formats: |
252b5132 RH |
8093 | |
8094 | @enumerate | |
a1ab1d2a | 8095 | @item |
252b5132 RH |
8096 | S-records, if @var{output-format} is @samp{S} |
8097 | ||
8098 | @item | |
8099 | IEEE, if @var{output-format} is @samp{IEEE} | |
8100 | ||
8101 | @item | |
8102 | COFF (the @samp{coff-m68k} variant in BFD), if @var{output-format} is | |
8103 | @samp{COFF} | |
8104 | @end enumerate | |
8105 | ||
8106 | @cindex @code{LIST} (MRI) | |
8107 | @item LIST @var{anything}@dots{} | |
8108 | Print (to the standard output file) a link map, as produced by the | |
ff5dcc92 | 8109 | @command{ld} command-line option @samp{-M}. |
252b5132 RH |
8110 | |
8111 | The keyword @code{LIST} may be followed by anything on the | |
8112 | same line, with no change in its effect. | |
8113 | ||
8114 | @cindex @code{LOAD} (MRI) | |
8115 | @item LOAD @var{filename} | |
8116 | @itemx LOAD @var{filename}, @var{filename}, @dots{} @var{filename} | |
8117 | Include one or more object file @var{filename} in the link; this has the | |
ff5dcc92 | 8118 | same effect as specifying @var{filename} directly on the @command{ld} |
252b5132 RH |
8119 | command line. |
8120 | ||
8121 | @cindex @code{NAME} (MRI) | |
8122 | @item NAME @var{output-name} | |
ff5dcc92 | 8123 | @var{output-name} is the name for the program produced by @command{ld}; the |
252b5132 RH |
8124 | MRI-compatible command @code{NAME} is equivalent to the command-line |
8125 | option @samp{-o} or the general script language command @code{OUTPUT}. | |
8126 | ||
8127 | @cindex @code{ORDER} (MRI) | |
8128 | @item ORDER @var{secname}, @var{secname}, @dots{} @var{secname} | |
8129 | @itemx ORDER @var{secname} @var{secname} @var{secname} | |
ff5dcc92 | 8130 | Normally, @command{ld} orders the sections in its output file in the |
252b5132 RH |
8131 | order in which they first appear in the input files. In an MRI-compatible |
8132 | script, you can override this ordering with the @code{ORDER} command. The | |
8133 | sections you list with @code{ORDER} will appear first in your output | |
8134 | file, in the order specified. | |
8135 | ||
8136 | @cindex @code{PUBLIC} (MRI) | |
8137 | @item PUBLIC @var{name}=@var{expression} | |
8138 | @itemx PUBLIC @var{name},@var{expression} | |
8139 | @itemx PUBLIC @var{name} @var{expression} | |
8140 | Supply a value (@var{expression}) for external symbol | |
8141 | @var{name} used in the linker input files. | |
8142 | ||
8143 | @cindex @code{SECT} (MRI) | |
8144 | @item SECT @var{secname}, @var{expression} | |
8145 | @itemx SECT @var{secname}=@var{expression} | |
8146 | @itemx SECT @var{secname} @var{expression} | |
8147 | You can use any of these three forms of the @code{SECT} command to | |
8148 | specify the start address (@var{expression}) for section @var{secname}. | |
8149 | If you have more than one @code{SECT} statement for the same | |
8150 | @var{secname}, only the @emph{first} sets the start address. | |
8151 | @end table | |
8152 | ||
793c5807 NC |
8153 | @node GNU Free Documentation License |
8154 | @appendix GNU Free Documentation License | |
36f63dca | 8155 | @include fdl.texi |
704c465c | 8156 | |
370b66a1 CD |
8157 | @node LD Index |
8158 | @unnumbered LD Index | |
252b5132 RH |
8159 | |
8160 | @printindex cp | |
8161 | ||
8162 | @tex | |
7ca01ed9 | 8163 | % I think something like @@colophon should be in texinfo. In the |
252b5132 RH |
8164 | % meantime: |
8165 | \long\def\colophon{\hbox to0pt{}\vfill | |
8166 | \centerline{The body of this manual is set in} | |
8167 | \centerline{\fontname\tenrm,} | |
8168 | \centerline{with headings in {\bf\fontname\tenbf}} | |
8169 | \centerline{and examples in {\tt\fontname\tentt}.} | |
8170 | \centerline{{\it\fontname\tenit\/} and} | |
8171 | \centerline{{\sl\fontname\tensl\/}} | |
8172 | \centerline{are used for emphasis.}\vfill} | |
8173 | \page\colophon | |
7ca01ed9 | 8174 | % Blame: doc@@cygnus.com, 28mar91. |
252b5132 RH |
8175 | @end tex |
8176 | ||
252b5132 | 8177 | @bye |