]>
Commit | Line | Data |
---|---|---|
f22eee08 | 1 | \input texinfo |
c8072296 | 2 | @setfilename ld.info |
b4d4e8e3 | 3 | @syncodeindex ky cp |
7f9ae73e | 4 | @include configdoc.texi |
8de26d62 | 5 | @c (configdoc.texi is generated by the Makefile) |
ec40bbb8 DM |
6 | |
7 | @c @smallbook | |
1c48127e RP |
8 | |
9 | @ifinfo | |
10 | @format | |
11 | START-INFO-DIR-ENTRY | |
f9d3d71a | 12 | * Ld: (ld). The GNU linker. |
1c48127e RP |
13 | END-INFO-DIR-ENTRY |
14 | @end format | |
15 | @end ifinfo | |
16 | ||
b4d4e8e3 | 17 | @ifinfo |
c653b370 | 18 | This file documents the @sc{gnu} linker LD. |
b4d4e8e3 | 19 | |
f4175166 | 20 | Copyright (C) 1991, 92, 93, 94, 95, 96, 97, 1998 Free Software Foundation, Inc. |
b4d4e8e3 RP |
21 | |
22 | Permission is granted to make and distribute verbatim copies of | |
23 | this manual provided the copyright notice and this permission notice | |
24 | are preserved on all copies. | |
25 | ||
d76ae847 RP |
26 | Permission is granted to copy and distribute modified versions of this |
27 | manual under the conditions for verbatim copying, provided also that | |
28 | the entire resulting derived work is distributed under the terms of a | |
29 | permission notice identical to this one. | |
30 | ||
31 | Permission is granted to copy and distribute translations of this manual | |
32 | into another language, under the above conditions for modified versions. | |
33 | ||
b4d4e8e3 RP |
34 | @ignore |
35 | Permission is granted to process this file through Tex and print the | |
36 | results, provided the printed document carries copying permission | |
37 | notice identical to this one except for the removal of this paragraph | |
38 | (this paragraph not being relevant to the printed manual). | |
39 | ||
40 | @end ignore | |
b4d4e8e3 | 41 | @end ifinfo |
2c5c0674 RP |
42 | @iftex |
43 | @finalout | |
b4d4e8e3 | 44 | @setchapternewpage odd |
246504a5 | 45 | @settitle Using LD, the GNU linker |
f22eee08 | 46 | @titlepage |
246504a5 | 47 | @title Using ld |
c8072296 | 48 | @subtitle The GNU linker |
f22eee08 | 49 | @sp 1 |
cb70c872 | 50 | @subtitle @code{ld} version 2 |
ed1cc83d | 51 | @subtitle April 1998 |
c653b370 | 52 | @author Steve Chamberlain |
ed1cc83d ILT |
53 | @author Ian Lance Taylor |
54 | @author Cygnus Solutions | |
b4d4e8e3 RP |
55 | @page |
56 | ||
57 | @tex | |
b4d4e8e3 | 58 | {\parskip=0pt |
ed1cc83d ILT |
59 | \hfill Cygnus Solutions\par |
60 | \hfill ian\@cygnus.com, doc\@cygnus.com\par | |
ec40bbb8 | 61 | \hfill {\it Using LD, the GNU linker}\par |
d4e5e3c3 | 62 | \hfill Edited by Jeffrey Osier (jeffrey\@cygnus.com)\par |
b4d4e8e3 RP |
63 | } |
64 | \global\parindent=0pt % Steve likes it this way. | |
65 | @end tex | |
66 | ||
f22eee08 | 67 | @vskip 0pt plus 1filll |
f4175166 | 68 | Copyright @copyright{} 1991, 92, 93, 94, 95, 96, 97, 1998 Free Software Foundation, Inc. |
f22eee08 RP |
69 | |
70 | Permission is granted to make and distribute verbatim copies of | |
71 | this manual provided the copyright notice and this permission notice | |
72 | are preserved on all copies. | |
73 | ||
74 | Permission is granted to copy and distribute modified versions of this | |
75 | manual under the conditions for verbatim copying, provided also that | |
76 | the entire resulting derived work is distributed under the terms of a | |
77 | permission notice identical to this one. | |
78 | ||
79 | Permission is granted to copy and distribute translations of this manual | |
80 | into another language, under the above conditions for modified versions. | |
f22eee08 | 81 | @end titlepage |
2c5c0674 | 82 | @end iftex |
b4d4e8e3 | 83 | @c FIXME: Talk about importance of *order* of args, cmds to linker! |
f22eee08 | 84 | |
f22eee08 | 85 | @ifinfo |
ec40bbb8 DM |
86 | @node Top |
87 | @top Using ld | |
c653b370 | 88 | This file documents the @sc{gnu} linker ld. |
f22eee08 | 89 | |
2c5c0674 | 90 | @menu |
2d59b2c3 RP |
91 | * Overview:: Overview |
92 | * Invocation:: Invocation | |
af54556a | 93 | * Scripts:: Linker Scripts |
ec40bbb8 | 94 | @ifset GENERIC |
2d59b2c3 | 95 | * Machine Dependent:: Machine Dependent Features |
ec40bbb8 DM |
96 | @end ifset |
97 | @ifclear GENERIC | |
98 | @ifset H8300 | |
99 | * H8/300:: ld and the H8/300 | |
100 | @end ifset | |
f9d3d71a ILT |
101 | @ifset Hitachi |
102 | * Hitachi:: ld and other Hitachi micros | |
103 | @end ifset | |
ec40bbb8 DM |
104 | @ifset I960 |
105 | * i960:: ld and the Intel 960 family | |
106 | @end ifset | |
107 | @end ifclear | |
108 | @ifclear SingleFormat | |
2d59b2c3 | 109 | * BFD:: BFD |
ec40bbb8 DM |
110 | @end ifclear |
111 | @c Following blank line required for remaining bug in makeinfo conds/menus | |
112 | ||
9fde46a4 | 113 | * Reporting Bugs:: Reporting Bugs |
2d59b2c3 RP |
114 | * MRI:: MRI Compatible Script Files |
115 | * Index:: Index | |
2c5c0674 | 116 | @end menu |
ec40bbb8 | 117 | @end ifinfo |
2c5c0674 | 118 | |
ec40bbb8 | 119 | @node Overview |
f22eee08 RP |
120 | @chapter Overview |
121 | ||
c653b370 | 122 | @cindex @sc{gnu} linker |
2c5c0674 | 123 | @cindex what is this? |
246504a5 | 124 | @code{ld} combines a number of object and archive files, relocates |
ec40bbb8 DM |
125 | their data and ties up symbol references. Usually the last step in |
126 | compiling a program is to run @code{ld}. | |
f22eee08 | 127 | |
246504a5 | 128 | @code{ld} accepts Linker Command Language files written in |
2c5c0674 | 129 | a superset of AT&T's Link Editor Command Language syntax, |
b4d4e8e3 | 130 | to provide explicit and total control over the linking process. |
f22eee08 | 131 | |
ec40bbb8 | 132 | @ifclear SingleFormat |
246504a5 RP |
133 | This version of @code{ld} uses the general purpose BFD libraries |
134 | to operate on object files. This allows @code{ld} to read, combine, and | |
b4d4e8e3 RP |
135 | write object files in many different formats---for example, COFF or |
136 | @code{a.out}. Different formats may be linked together to produce any | |
d4e5e3c3 | 137 | available kind of object file. @xref{BFD}, for more information. |
ec40bbb8 | 138 | @end ifclear |
f22eee08 | 139 | |
c653b370 | 140 | Aside from its flexibility, the @sc{gnu} linker is more helpful than other |
2c5c0674 RP |
141 | linkers in providing diagnostic information. Many linkers abandon |
142 | execution immediately upon encountering an error; whenever possible, | |
246504a5 | 143 | @code{ld} continues executing, allowing you to identify other errors |
2c5c0674 RP |
144 | (or, in some cases, to get an output file in spite of the error). |
145 | ||
ec40bbb8 | 146 | @node Invocation |
2c5c0674 RP |
147 | @chapter Invocation |
148 | ||
c653b370 | 149 | The @sc{gnu} linker @code{ld} is meant to cover a broad range of situations, |
2c5c0674 | 150 | and to be as compatible as possible with other linkers. As a result, |
ec40bbb8 | 151 | you have many choices to control its behavior. |
2c5c0674 | 152 | |
ec40bbb8 | 153 | @ifset UsesEnvVars |
2c5c0674 | 154 | @menu |
2d59b2c3 RP |
155 | * Options:: Command Line Options |
156 | * Environment:: Environment Variables | |
2c5c0674 | 157 | @end menu |
f22eee08 | 158 | |
ec40bbb8 | 159 | @node Options |
2c5c0674 | 160 | @section Command Line Options |
ec40bbb8 | 161 | @end ifset |
2c5c0674 RP |
162 | |
163 | @cindex command line | |
164 | @cindex options | |
67afbcea DE |
165 | The linker supports a plethora of command-line options, but in actual |
166 | practice few of them are used in any particular context. | |
2c5c0674 | 167 | @cindex standard Unix system |
246504a5 | 168 | For instance, a frequent use of @code{ld} is to link standard Unix |
b4d4e8e3 RP |
169 | object files on a standard, supported Unix system. On such a system, to |
170 | link a file @code{hello.o}: | |
ec40bbb8 | 171 | |
c653b370 | 172 | @smallexample |
ec40bbb8 | 173 | ld -o @var{output} /lib/crt0.o hello.o -lc |
c653b370 | 174 | @end smallexample |
ec40bbb8 | 175 | |
d76ae847 | 176 | This tells @code{ld} to produce a file called @var{output} as the |
b4d4e8e3 | 177 | result of linking the file @code{/lib/crt0.o} with @code{hello.o} and |
ec40bbb8 DM |
178 | the library @code{libc.a}, which will come from the standard search |
179 | directories. (See the discussion of the @samp{-l} option below.) | |
f22eee08 | 180 | |
246504a5 | 181 | The command-line options to @code{ld} may be specified in any order, and |
67afbcea DE |
182 | may be repeated at will. Repeating most options with a different |
183 | argument will either have no further effect, or override prior | |
ec40bbb8 | 184 | occurrences (those further to the left on the command line) of that |
67afbcea DE |
185 | option. Options which may be meaningfully specified more than once are |
186 | noted in the descriptions below. | |
f22eee08 | 187 | |
2c5c0674 | 188 | @cindex object files |
67afbcea DE |
189 | Non-option arguments are objects files which are to be linked together. |
190 | They may follow, precede, or be mixed in with command-line options, | |
191 | except that an object file argument may not be placed between an option | |
192 | and its argument. | |
f22eee08 | 193 | |
7f9ae73e RP |
194 | Usually the linker is invoked with at least one object file, but you can |
195 | specify other forms of binary input files using @samp{-l}, @samp{-R}, | |
196 | and the script command language. If @emph{no} binary input files at all | |
197 | are specified, the linker does not produce any output, and issues the | |
198 | message @samp{No input files}. | |
2c5c0674 | 199 | |
0b3499f6 ILT |
200 | If the linker can not recognize the format of an object file, it will |
201 | assume that it is a linker script. A script specified in this way | |
202 | augments the main linker script used for the link (either the default | |
203 | linker script or the one specified by using @samp{-T}). This feature | |
204 | permits the linker to link against a file which appears to be an object | |
205 | or an archive, but actually merely defines some symbol values, or uses | |
cc28f8fb ILT |
206 | @code{INPUT} or @code{GROUP} to load other objects. Note that |
207 | specifying a script in this way should only be used to augment the main | |
208 | linker script; if you want to use some command that logically can only | |
209 | appear once, such as the @code{SECTIONS} or @code{MEMORY} command, you | |
210 | must replace the default linker script using the @samp{-T} option. | |
af54556a | 211 | @xref{Scripts}. |
0b3499f6 | 212 | |
d4e5e3c3 DM |
213 | For options whose names are a single letter, |
214 | option arguments must either follow the option letter without intervening | |
f22eee08 RP |
215 | whitespace, or be given as separate arguments immediately following the |
216 | option that requires them. | |
217 | ||
d4e5e3c3 DM |
218 | For options whose names are multiple letters, either one dash or two can |
219 | precede the option name; for example, @samp{--oformat} and | |
9fde46a4 | 220 | @samp{--oformat} are equivalent. Arguments to multiple-letter options |
d4e5e3c3 DM |
221 | must either be separated from the option name by an equals sign, or be |
222 | given as separate arguments immediately following the option that | |
223 | requires them. For example, @samp{--oformat srec} and | |
224 | @samp{--oformat=srec} are equivalent. Unique abbreviations of the names | |
225 | of multiple-letter options are accepted. | |
226 | ||
f22eee08 | 227 | @table @code |
67afbcea DE |
228 | @kindex -a@var{keyword} |
229 | @item -a@var{keyword} | |
230 | This option is supported for HP/UX compatibility. The @var{keyword} | |
231 | argument must be one of the strings @samp{archive}, @samp{shared}, or | |
232 | @samp{default}. @samp{-aarchive} is functionally equivalent to | |
233 | @samp{-Bstatic}, and the other two keywords are functionally equivalent | |
234 | to @samp{-Bdynamic}. This option may be used any number of times. | |
235 | ||
ec40bbb8 | 236 | @ifset I960 |
2c5c0674 RP |
237 | @cindex architectures |
238 | @kindex -A@var{arch} | |
b4d4e8e3 | 239 | @item -A@var{architecture} |
67afbcea DE |
240 | @kindex --architecture=@var{arch} |
241 | @itemx --architecture=@var{architecture} | |
246504a5 RP |
242 | In the current release of @code{ld}, this option is useful only for the |
243 | Intel 960 family of architectures. In that @code{ld} configuration, the | |
1c48127e RP |
244 | @var{architecture} argument identifies the particular architecture in |
245 | the 960 family, enabling some safeguards and modifying the | |
d76ae847 RP |
246 | archive-library search path. @xref{i960,,@code{ld} and the Intel 960 |
247 | family}, for details. | |
b4d4e8e3 | 248 | |
246504a5 | 249 | Future releases of @code{ld} may support similar functionality for |
b4d4e8e3 | 250 | other architecture families. |
ec40bbb8 | 251 | @end ifset |
b4d4e8e3 | 252 | |
ec40bbb8 | 253 | @ifclear SingleFormat |
2c5c0674 RP |
254 | @cindex binary input format |
255 | @kindex -b @var{format} | |
67afbcea | 256 | @kindex --format=@var{format} |
2c5c0674 | 257 | @cindex input format |
2c5c0674 | 258 | @cindex input format |
c653b370 | 259 | @item -b @var{input-format} |
67afbcea | 260 | @itemx --format=@var{input-format} |
1fb57a5d RP |
261 | @code{ld} may be configured to support more than one kind of object |
262 | file. If your @code{ld} is configured this way, you can use the | |
263 | @samp{-b} option to specify the binary format for input object files | |
264 | that follow this option on the command line. Even when @code{ld} is | |
265 | configured to support alternative object formats, you don't usually need | |
266 | to specify this, as @code{ld} should be configured to expect as a | |
267 | default input format the most usual format on each machine. | |
268 | @var{input-format} is a text string, the name of a particular format | |
269 | supported by the BFD libraries. (You can list the available binary | |
67afbcea | 270 | formats with @samp{objdump -i}.) |
1fb57a5d | 271 | @xref{BFD}. |
2c5c0674 RP |
272 | |
273 | You may want to use this option if you are linking files with an unusual | |
ec40bbb8 | 274 | binary format. You can also use @samp{-b} to switch formats explicitly (when |
2c5c0674 | 275 | linking object files of different formats), by including |
ec40bbb8 | 276 | @samp{-b @var{input-format}} before each group of object files in a |
2c5c0674 RP |
277 | particular format. |
278 | ||
279 | The default format is taken from the environment variable | |
ec40bbb8 DM |
280 | @code{GNUTARGET}. |
281 | @ifset UsesEnvVars | |
282 | @xref{Environment}. | |
283 | @end ifset | |
af54556a ILT |
284 | You can also define the input format from a script, using the command |
285 | @code{TARGET}; see @ref{Format Commands}. | |
ec40bbb8 | 286 | @end ifclear |
2c5c0674 | 287 | |
2d59b2c3 | 288 | @kindex -c @var{MRI-cmdfile} |
67afbcea | 289 | @kindex --mri-script=@var{MRI-cmdfile} |
2d59b2c3 RP |
290 | @cindex compatibility, MRI |
291 | @item -c @var{MRI-commandfile} | |
67afbcea | 292 | @itemx --mri-script=@var{MRI-commandfile} |
2d59b2c3 RP |
293 | For compatibility with linkers produced by MRI, @code{ld} accepts script |
294 | files written in an alternate, restricted command language, described in | |
d76ae847 | 295 | @ref{MRI,,MRI Compatible Script Files}. Introduce MRI script files with |
ec40bbb8 | 296 | the option @samp{-c}; use the @samp{-T} option to run linker |
d76ae847 | 297 | scripts written in the general-purpose @code{ld} scripting language. |
8ddef552 DM |
298 | If @var{MRI-cmdfile} does not exist, @code{ld} looks for it in the directories |
299 | specified by any @samp{-L} options. | |
b4d4e8e3 | 300 | |
2c5c0674 RP |
301 | @cindex common allocation |
302 | @kindex -d | |
2c5c0674 | 303 | @kindex -dc |
2c5c0674 | 304 | @kindex -dp |
c653b370 ILT |
305 | @item -d |
306 | @itemx -dc | |
b4d4e8e3 RP |
307 | @itemx -dp |
308 | These three options are equivalent; multiple forms are supported for | |
af54556a ILT |
309 | compatibility with other linkers. They assign space to common symbols |
310 | even if a relocatable output file is specified (with @samp{-r}). The | |
311 | script command @code{FORCE_COMMON_ALLOCATION} has the same effect. | |
312 | @xref{Miscellaneous Commands}. | |
b4d4e8e3 | 313 | |
2c5c0674 RP |
314 | @cindex entry point, from command line |
315 | @kindex -e @var{entry} | |
67afbcea | 316 | @kindex --entry=@var{entry} |
f22eee08 | 317 | @item -e @var{entry} |
67afbcea | 318 | @itemx --entry=@var{entry} |
f22eee08 | 319 | Use @var{entry} as the explicit symbol for beginning execution of your |
e2ebb8ed JL |
320 | program, rather than the default entry point. If there is no symbol |
321 | named @var{entry}, the linker will try to parse @var{entry} as a number, | |
322 | and use that as the entry address (the number will be interpreted in | |
323 | base 10; you may use a leading @samp{0x} for base 16, or a leading | |
324 | @samp{0} for base 8). @xref{Entry Point}, for a discussion of defaults | |
325 | and other ways of specifying the entry point. | |
f22eee08 | 326 | |
c653b370 | 327 | @cindex dynamic symbol table |
7ec9d825 | 328 | @kindex -E |
9fde46a4 | 329 | @kindex --export-dynamic |
7ec9d825 | 330 | @item -E |
9fde46a4 | 331 | @itemx --export-dynamic |
67afbcea | 332 | When creating a dynamically linked executable, add all symbols to the |
5a59e34d ILT |
333 | dynamic symbol table. The dynamic symbol table is the set of symbols |
334 | which are visible from dynamic objects at run time. | |
335 | ||
336 | If you do not use this option, the dynamic symbol table will normally | |
337 | contain only those symbols which are referenced by some dynamic object | |
338 | mentioned in the link. | |
339 | ||
340 | If you use @code{dlopen} to load a dynamic object which needs to refer | |
341 | back to the symbols defined by the program, rather than some other | |
342 | dynamic object, then you will probably need to use this option when | |
343 | linking the program itself. | |
c653b370 | 344 | |
de220cbd ILT |
345 | @kindex -f |
346 | @kindex --auxiliary | |
347 | @item -f | |
348 | @itemx --auxiliary @var{name} | |
349 | When creating an ELF shared object, set the internal DT_AUXILIARY field | |
350 | to the specified name. This tells the dynamic linker that the symbol | |
351 | table of the shared object should be used as an auxiliary filter on the | |
352 | symbol table of the shared object @var{name}. | |
353 | ||
cc28f8fb ILT |
354 | If you later link a program against this filter object, then, when you |
355 | run the program, the dynamic linker will see the DT_AUXILIARY field. If | |
356 | the dynamic linker resolves any symbols from the filter object, it will | |
357 | first check whether there is a definition in the shared object | |
358 | @var{name}. If there is one, it will be used instead of the definition | |
359 | in the filter object. The shared object @var{name} need not exist. | |
360 | Thus the shared object @var{name} may be used to provide an alternative | |
361 | implementation of certain functions, perhaps for debugging or for | |
362 | machine specific performance. | |
363 | ||
5a59e34d ILT |
364 | This option may be specified more than once. The DT_AUXILIARY entries |
365 | will be created in the order in which they appear on the command line. | |
366 | ||
2c5c0674 | 367 | @kindex -F |
de220cbd ILT |
368 | @kindex --filter |
369 | @item -F @var{name} | |
370 | @itemx --filter @var{name} | |
371 | When creating an ELF shared object, set the internal DT_FILTER field to | |
372 | the specified name. This tells the dynamic linker that the symbol table | |
cc28f8fb ILT |
373 | of the shared object which is being created should be used as a filter |
374 | on the symbol table of the shared object @var{name}. | |
375 | ||
376 | If you later link a program against this filter object, then, when you | |
377 | run the program, the dynamic linker will see the DT_FILTER field. The | |
378 | dynamic linker will resolve symbols according to the symbol table of the | |
379 | filter object as usual, but it will actually link to the definitions | |
380 | found in the shared object @var{name}. Thus the filter object can be | |
381 | used to select a subset of the symbols provided by the object | |
382 | @var{name}. | |
de220cbd ILT |
383 | |
384 | Some older linkers used the @code{-F} option throughout a compilation | |
ec40bbb8 | 385 | toolchain for specifying object-file format for both input and output |
de220cbd ILT |
386 | object files. The @sc{gnu} linker uses other mechanisms for this |
387 | purpose: the @code{-b}, @code{--format}, @code{--oformat} options, the | |
388 | @code{TARGET} command in linker scripts, and the @code{GNUTARGET} | |
389 | environment variable. The @sc{gnu} linker will ignore the @code{-F} | |
390 | option when not creating an ELF shared object. | |
2c5c0674 | 391 | |
a1d393cf ILT |
392 | @kindex --force-exe-suffix |
393 | @item --force-exe-suffix | |
394 | Make sure that an output file has a .exe suffix. | |
395 | ||
396 | If a successfully built fully linked output file does not have a | |
397 | @code{.exe} or @code{.dll} suffix, this option forces the linker to copy | |
398 | the output file to one of the same name with a @code{.exe} suffix. This | |
399 | option is useful when using unmodified Unix makefiles on a Microsoft | |
400 | Windows host, since some versions of Windows won't run an image unless | |
401 | it ends in a @code{.exe} suffix. | |
402 | ||
2c5c0674 | 403 | @kindex -g |
b4d4e8e3 | 404 | @item -g |
ec40bbb8 | 405 | Ignored. Provided for compatibility with other tools. |
b4d4e8e3 | 406 | |
8ddef552 | 407 | @kindex -G |
67afbcea | 408 | @kindex --gpsize |
8ddef552 DM |
409 | @cindex object size |
410 | @item -G@var{value} | |
67afbcea | 411 | @itemx --gpsize=@var{value} |
8ddef552 | 412 | Set the maximum size of objects to be optimized using the GP register to |
67afbcea DE |
413 | @var{size}. This is only meaningful for object file formats such as |
414 | MIPS ECOFF which supports putting large and small objects into different | |
415 | sections. This is ignored for other object file formats. | |
8ddef552 | 416 | |
67afbcea DE |
417 | @cindex runtime library name |
418 | @kindex -h@var{name} | |
419 | @kindex -soname=@var{name} | |
420 | @item -h@var{name} | |
421 | @itemx -soname=@var{name} | |
422 | When creating an ELF shared object, set the internal DT_SONAME field to | |
423 | the specified name. When an executable is linked with a shared object | |
424 | which has a DT_SONAME field, then when the executable is run the dynamic | |
425 | linker will attempt to load the shared object specified by the DT_SONAME | |
426 | field rather than the using the file name given to the linker. | |
de87cdb4 | 427 | |
2c5c0674 RP |
428 | @kindex -i |
429 | @cindex incremental link | |
f22eee08 | 430 | @item -i |
ec40bbb8 | 431 | Perform an incremental link (same as option @samp{-r}). |
f22eee08 | 432 | |
2c5c0674 | 433 | @cindex archive files, from cmd line |
de87cdb4 | 434 | @kindex -l@var{archive} |
67afbcea DE |
435 | @kindex --library=@var{archive} |
436 | @item -l@var{archive} | |
437 | @itemx --library=@var{archive} | |
438 | Add archive file @var{archive} to the list of files to link. This | |
f22eee08 | 439 | option may be used any number of times. @code{ld} will search its |
67afbcea | 440 | path-list for occurrences of @code{lib@var{archive}.a} for every |
4164f2d5 ILT |
441 | @var{archive} specified. |
442 | ||
443 | On systems which support shared libraries, @code{ld} may also search for | |
444 | libraries with extensions other than @code{.a}. Specifically, on ELF | |
445 | and SunOS systems, @code{ld} will search a directory for a library with | |
446 | an extension of @code{.so} before searching for one with an extension of | |
447 | @code{.a}. By convention, a @code{.so} extension indicates a shared | |
448 | library. | |
f22eee08 | 449 | |
b61364cc ILT |
450 | The linker will search an archive only once, at the location where it is |
451 | specified on the command line. If the archive defines a symbol which | |
452 | was undefined in some object which appeared before the archive on the | |
453 | command line, the linker will include the appropriate file(s) from the | |
454 | archive. However, an undefined symbol in an object appearing later on | |
455 | the command line will not cause the linker to search the archive again. | |
456 | ||
457 | See the @code{-(} option for a way to force the linker to search | |
458 | archives multiple times. | |
459 | ||
460 | You may list the same archive multiple times on the command line. | |
461 | ||
462 | @ifset GENERIC | |
463 | This type of archive searching is standard for Unix linkers. However, | |
464 | if you are using @code{ld} on AIX, note that it is different from the | |
465 | behaviour of the AIX linker. | |
466 | @end ifset | |
467 | ||
2c5c0674 RP |
468 | @cindex search directory, from cmd line |
469 | @kindex -L@var{dir} | |
67afbcea | 470 | @kindex --library-path=@var{dir} |
b4d4e8e3 | 471 | @item -L@var{searchdir} |
67afbcea | 472 | @itemx --library-path=@var{searchdir} |
ec40bbb8 | 473 | Add path @var{searchdir} to the list of paths that @code{ld} will search |
8ddef552 | 474 | for archive libraries and @code{ld} control scripts. You may use this |
0b0642d6 ILT |
475 | option any number of times. The directories are searched in the order |
476 | in which they are specified on the command line. Directories specified | |
477 | on the command line are searched before the default directories. All | |
478 | @code{-L} options apply to all @code{-l} options, regardless of the | |
479 | order in which the options appear. | |
f22eee08 | 480 | |
ec40bbb8 | 481 | @ifset UsesEnvVars |
2c5c0674 | 482 | The default set of paths searched (without being specified with |
ec40bbb8 DM |
483 | @samp{-L}) depends on which emulation mode @code{ld} is using, and in |
484 | some cases also on how it was configured. @xref{Environment}. | |
485 | @end ifset | |
486 | ||
487 | The paths can also be specified in a link script with the | |
0b0642d6 ILT |
488 | @code{SEARCH_DIR} command. Directories specified this way are searched |
489 | at the point in which the linker script appears in the command line. | |
f22eee08 | 490 | |
8ddef552 DM |
491 | @cindex emulation |
492 | @kindex -m @var{emulation} | |
493 | @item -m@var{emulation} | |
8ddef552 | 494 | Emulate the @var{emulation} linker. You can list the available |
f4175166 ILT |
495 | emulations with the @samp{--verbose} or @samp{-V} options. |
496 | ||
497 | If the @samp{-m} option is not used, the emulation is taken from the | |
498 | @code{LDEMULATION} environment variable, if that is defined. | |
499 | ||
500 | Otherwise, the default emulation depends upon how the linker was | |
501 | configured. | |
8ddef552 | 502 | |
67afbcea DE |
503 | @cindex link map |
504 | @kindex -M | |
505 | @kindex --print-map | |
506 | @item -M | |
507 | @itemx --print-map | |
af54556a ILT |
508 | Print a link map to the standard output. A link map provides |
509 | information about the link, including the following: | |
510 | ||
511 | @itemize @bullet | |
512 | @item | |
513 | Where object files and symbols are mapped into memory. | |
514 | @item | |
515 | How common symbols are allocated. | |
516 | @item | |
517 | All archive members included in the link, with a mention of the symbol | |
518 | which caused the archive member to be brought in. | |
519 | @end itemize | |
67afbcea DE |
520 | |
521 | @kindex -n | |
522 | @cindex read-only text | |
523 | @cindex NMAGIC | |
524 | @kindex --nmagic | |
525 | @item -n | |
526 | @itemx --nmagic | |
527 | Set the text segment to be read only, and mark the output as | |
528 | @code{NMAGIC} if possible. | |
529 | ||
2c5c0674 | 530 | @kindex -N |
67afbcea | 531 | @kindex --omagic |
2c5c0674 | 532 | @cindex read/write from cmd line |
67afbcea | 533 | @cindex OMAGIC |
f22eee08 | 534 | @item -N |
67afbcea | 535 | @itemx --omagic |
ec40bbb8 DM |
536 | Set the text and data sections to be readable and writable. Also, do |
537 | not page-align the data segment. If the output format supports Unix | |
538 | style magic numbers, mark the output as @code{OMAGIC}. | |
f22eee08 | 539 | |
67afbcea DE |
540 | @kindex -o @var{output} |
541 | @kindex --output=@var{output} | |
542 | @cindex naming the output file | |
543 | @item -o @var{output} | |
544 | @itemx --output=@var{output} | |
545 | Use @var{output} as the name for the program produced by @code{ld}; if this | |
546 | option is not specified, the name @file{a.out} is used by default. The | |
547 | script command @code{OUTPUT} can also specify the output file name. | |
f22eee08 | 548 | |
67afbcea DE |
549 | @cindex partial link |
550 | @cindex relocatable output | |
551 | @kindex -r | |
552 | @kindex --relocateable | |
553 | @item -r | |
554 | @itemx --relocateable | |
555 | Generate relocatable output---i.e., generate an output file that can in | |
556 | turn serve as input to @code{ld}. This is often called @dfn{partial | |
557 | linking}. As a side effect, in environments that support standard Unix | |
558 | magic numbers, this option also sets the output file's magic number to | |
559 | @code{OMAGIC}. | |
560 | @c ; see @code{-N}. | |
561 | If this option is not specified, an absolute file is produced. When | |
562 | linking C++ programs, this option @emph{will not} resolve references to | |
563 | constructors; to do that, use @samp{-Ur}. | |
564 | ||
565 | This option does the same thing as @samp{-i}. | |
566 | ||
567 | @kindex -R @var{file} | |
568 | @kindex --just-symbols=@var{file} | |
569 | @cindex symbol-only input | |
570 | @item -R @var{filename} | |
571 | @itemx --just-symbols=@var{filename} | |
572 | Read symbol names and their addresses from @var{filename}, but do not | |
573 | relocate it or include it in the output. This allows your output file | |
574 | to refer symbolically to absolute locations of memory defined in other | |
575 | programs. You may use this option more than once. | |
576 | ||
577 | For compatibility with other ELF linkers, if the @code{-R} option is | |
578 | followed by a directory name, rather than a file name, it is treated as | |
579 | the @code{-rpath} option. | |
580 | ||
581 | @kindex -s | |
582 | @kindex --strip-all | |
583 | @cindex strip all symbols | |
584 | @item -s | |
585 | @itemx --strip-all | |
586 | Omit all symbol information from the output file. | |
587 | ||
588 | @kindex -S | |
589 | @kindex --strip-debug | |
590 | @cindex strip debugger symbols | |
591 | @item -S | |
592 | @itemx --strip-debug | |
593 | Omit debugger symbol information (but not all symbols) from the output file. | |
594 | ||
595 | @kindex -t | |
596 | @kindex --trace | |
597 | @cindex input files, displaying | |
598 | @item -t | |
599 | @itemx --trace | |
600 | Print the names of the input files as @code{ld} processes them. | |
601 | ||
602 | @kindex -T @var{script} | |
603 | @kindex --script=@var{script} | |
604 | @cindex script files | |
af54556a ILT |
605 | @item -T @var{scriptfile} |
606 | @itemx --script=@var{scriptfile} | |
607 | Use @var{scriptfile} as the linker script. This script replaces | |
608 | @code{ld}'s default linker script (rather than adding to it), so | |
cc28f8fb | 609 | @var{commandfile} must specify everything necessary to describe the |
af54556a | 610 | output file. You must use this option if you want to use a command |
cc28f8fb | 611 | which can only appear once in a linker script, such as the |
af54556a ILT |
612 | @code{SECTIONS} or @code{MEMORY} command. @xref{Scripts}. If |
613 | @var{scriptfile} does not exist in the current directory, @code{ld} | |
614 | looks for it in the directories specified by any preceding @samp{-L} | |
615 | options. Multiple @samp{-T} options accumulate. | |
67afbcea DE |
616 | |
617 | @kindex -u @var{symbol} | |
618 | @kindex --undefined=@var{symbol} | |
619 | @cindex undefined symbol | |
620 | @item -u @var{symbol} | |
621 | @itemx --undefined=@var{symbol} | |
622 | Force @var{symbol} to be entered in the output file as an undefined symbol. | |
623 | Doing this may, for example, trigger linking of additional modules from | |
624 | standard libraries. @samp{-u} may be repeated with different option | |
625 | arguments to enter additional undefined symbols. | |
626 | @c Nice idea, but no such command: This option is equivalent | |
627 | @c to the @code{EXTERN} linker command. | |
628 | ||
629 | @kindex -v | |
630 | @kindex -V | |
631 | @kindex --version | |
632 | @cindex version | |
633 | @item -v | |
634 | @itemx --version | |
635 | @itemx -V | |
636 | Display the version number for @code{ld}. The @code{-V} option also | |
637 | lists the supported emulations. | |
638 | ||
639 | @kindex -x | |
640 | @kindex --discard-all | |
641 | @cindex deleting local symbols | |
642 | @item -x | |
643 | @itemx --discard-all | |
644 | Delete all local symbols. | |
645 | ||
646 | @kindex -X | |
647 | @kindex --discard-locals | |
648 | @cindex local symbols, deleting | |
649 | @cindex L, deleting symbols beginning | |
650 | @item -X | |
651 | @itemx --discard-locals | |
652 | Delete all temporary local symbols. For most targets, this is all local | |
653 | symbols whose names begin with @samp{L}. | |
654 | ||
655 | @kindex -y @var{symbol} | |
656 | @kindex --trace-symbol=@var{symbol} | |
657 | @cindex symbol tracing | |
658 | @item -y @var{symbol} | |
659 | @itemx --trace-symbol=@var{symbol} | |
660 | Print the name of each linked file in which @var{symbol} appears. This | |
661 | option may be given any number of times. On many systems it is necessary | |
662 | to prepend an underscore. | |
663 | ||
664 | This option is useful when you have an undefined symbol in your link but | |
665 | don't know where the reference is coming from. | |
666 | ||
667 | @kindex -Y @var{path} | |
668 | @item -Y @var{path} | |
669 | Add @var{path} to the default library search path. This option exists | |
670 | for Solaris compatibility. | |
671 | ||
672 | @kindex -z @var{keyword} | |
673 | @item -z @var{keyword} | |
674 | This option is ignored for Solaris compatibility. | |
675 | ||
676 | @kindex -( | |
677 | @cindex groups of archives | |
678 | @item -( @var{archives} -) | |
679 | @itemx --start-group @var{archives} --end-group | |
680 | The @var{archives} should be a list of archive files. They may be | |
681 | either explicit file names, or @samp{-l} options. | |
682 | ||
683 | The specified archives are searched repeatedly until no new undefined | |
684 | references are created. Normally, an archive is searched only once in | |
685 | the order that it is specified on the command line. If a symbol in that | |
686 | archive is needed to resolve an undefined symbol referred to by an | |
687 | object in an archive that appears later on the command line, the linker | |
688 | would not be able to resolve that reference. By grouping the archives, | |
689 | they all be searched repeatedly until all possible references are | |
690 | resolved. | |
691 | ||
692 | Using this option has a significant performance cost. It is best to use | |
693 | it only when there are unavoidable circular references between two or | |
694 | more archives. | |
695 | ||
696 | @kindex -assert @var{keyword} | |
697 | @item -assert @var{keyword} | |
698 | This option is ignored for SunOS compatibility. | |
699 | ||
700 | @kindex -Bdynamic | |
701 | @kindex -dy | |
702 | @kindex -call_shared | |
703 | @item -Bdynamic | |
704 | @itemx -dy | |
705 | @itemx -call_shared | |
706 | Link against dynamic libraries. This is only meaningful on platforms | |
707 | for which shared libraries are supported. This option is normally the | |
708 | default on such platforms. The different variants of this option are | |
709 | for compatibility with various systems. You may use this option | |
710 | multiple times on the command line: it affects library searching for | |
711 | @code{-l} options which follow it. | |
712 | ||
713 | @kindex -Bstatic | |
714 | @kindex -dn | |
715 | @kindex -non_shared | |
716 | @kindex -static | |
717 | @item -Bstatic | |
718 | @itemx -dn | |
719 | @itemx -non_shared | |
720 | @itemx -static | |
721 | Do not link against shared libraries. This is only meaningful on | |
722 | platforms for which shared libraries are supported. The different | |
723 | variants of this option are for compatibility with various systems. You | |
724 | may use this option multiple times on the command line: it affects | |
725 | library searching for @code{-l} options which follow it. | |
726 | ||
727 | @kindex -Bsymbolic | |
728 | @item -Bsymbolic | |
729 | When creating a shared library, bind references to global symbols to the | |
730 | definition within the shared library, if any. Normally, it is possible | |
731 | for a program linked against a shared library to override the definition | |
732 | within the shared library. This option is only meaningful on ELF | |
733 | platforms which support shared libraries. | |
734 | ||
86bc0974 ILT |
735 | @cindex cross reference table |
736 | @kindex --cref | |
737 | @item --cref | |
738 | Output a cross reference table. If a linker map file is being | |
739 | generated, the cross reference table is printed to the map file. | |
740 | Otherwise, it is printed on the standard output. | |
741 | ||
742 | The format of the table is intentionally simple, so that it may be | |
743 | easily processed by a script if necessary. The symbols are printed out, | |
744 | sorted by name. For each symbol, a list of file names is given. If the | |
745 | symbol is defined, the first file listed is the location of the | |
746 | definition. The remaining files contain references to the symbol. | |
747 | ||
67afbcea DE |
748 | @cindex symbols, from command line |
749 | @kindex --defsym @var{symbol}=@var{exp} | |
750 | @item --defsym @var{symbol}=@var{expression} | |
751 | Create a global symbol in the output file, containing the absolute | |
752 | address given by @var{expression}. You may use this option as many | |
753 | times as necessary to define multiple symbols in the command line. A | |
754 | limited form of arithmetic is supported for the @var{expression} in this | |
755 | context: you may give a hexadecimal constant or the name of an existing | |
756 | symbol, or use @code{+} and @code{-} to add or subtract hexadecimal | |
757 | constants or symbols. If you need more elaborate expressions, consider | |
af54556a ILT |
758 | using the linker command language from a script (@pxref{Assignments,, |
759 | Assignment: Symbol Definitions}). @emph{Note:} there should be no white | |
760 | space between @var{symbol}, the equals sign (``@key{=}''), and | |
67afbcea DE |
761 | @var{expression}. |
762 | ||
763 | @cindex dynamic linker, from command line | |
764 | @kindex --dynamic-linker @var{file} | |
765 | @item --dynamic-linker @var{file} | |
766 | Set the name of the dynamic linker. This is only meaningful when | |
767 | generating dynamically linked ELF executables. The default dynamic | |
768 | linker is normally correct; don't use this unless you know what you are | |
769 | doing. | |
770 | ||
771 | @cindex big-endian objects | |
772 | @cindex endianness | |
773 | @kindex -EB | |
774 | @item -EB | |
775 | Link big-endian objects. This affects the default output format. | |
776 | ||
777 | @cindex little-endian objects | |
778 | @kindex -EL | |
779 | @item -EL | |
780 | Link little-endian objects. This affects the default output format. | |
781 | ||
782 | @cindex MIPS embedded PIC code | |
9fde46a4 ILT |
783 | @kindex --embedded-relocs |
784 | @item --embedded-relocs | |
67afbcea DE |
785 | This option is only meaningful when linking MIPS embedded PIC code, |
786 | generated by the -membedded-pic option to the @sc{gnu} compiler and | |
787 | assembler. It causes the linker to create a table which may be used at | |
788 | runtime to relocate any data which was statically initialized to pointer | |
789 | values. See the code in testsuite/ld-empic for details. | |
790 | ||
791 | @cindex help | |
792 | @cindex usage | |
793 | @kindex --help | |
794 | @item --help | |
795 | Print a summary of the command-line options on the standard output and exit. | |
796 | ||
67afbcea DE |
797 | @kindex -Map |
798 | @item -Map @var{mapfile} | |
af54556a ILT |
799 | Print a link map to the file @var{mapfile}. See the description of the |
800 | @samp{-M} option, above. | |
b4d4e8e3 | 801 | |
4551e108 | 802 | @cindex memory usage |
67afbcea DE |
803 | @kindex --no-keep-memory |
804 | @item --no-keep-memory | |
4551e108 ILT |
805 | @code{ld} normally optimizes for speed over memory usage by caching the |
806 | symbol tables of input files in memory. This option tells @code{ld} to | |
807 | instead optimize for memory usage, by rereading the symbol tables as | |
808 | necessary. This may be required if @code{ld} runs out of memory space | |
809 | while linking a large executable. | |
810 | ||
5a59e34d ILT |
811 | @kindex --no-warn-mismatch |
812 | @item --no-warn-mismatch | |
813 | Normally @code{ld} will give an error if you try to link together input | |
814 | files that are mismatched for some reason, perhaps because they have | |
815 | been compiled for different processors or for different endiannesses. | |
816 | This option tells @code{ld} that it should silently permit such possible | |
817 | errors. This option should only be used with care, in cases when you | |
818 | have taken some special action that ensures that the linker errors are | |
819 | inappropriate. | |
820 | ||
67afbcea DE |
821 | @kindex --no-whole-archive |
822 | @item --no-whole-archive | |
823 | Turn off the effect of the @code{--whole-archive} option for subsequent | |
824 | archive files. | |
825 | ||
826 | @cindex output file after errors | |
827 | @kindex --noinhibit-exec | |
828 | @item --noinhibit-exec | |
829 | Retain the executable output file whenever it is still usable. | |
830 | Normally, the linker will not produce an output file if it encounters | |
831 | errors during the link process; it exits without writing an output file | |
832 | when it issues any error whatsoever. | |
f22eee08 | 833 | |
7f9ae73e | 834 | @ifclear SingleFormat |
9fde46a4 ILT |
835 | @kindex --oformat |
836 | @item --oformat @var{output-format} | |
1fb57a5d RP |
837 | @code{ld} may be configured to support more than one kind of object |
838 | file. If your @code{ld} is configured this way, you can use the | |
9fde46a4 | 839 | @samp{--oformat} option to specify the binary format for the output |
1fb57a5d RP |
840 | object file. Even when @code{ld} is configured to support alternative |
841 | object formats, you don't usually need to specify this, as @code{ld} | |
842 | should be configured to produce as a default output format the most | |
843 | usual format on each machine. @var{output-format} is a text string, the | |
844 | name of a particular format supported by the BFD libraries. (You can | |
845 | list the available binary formats with @samp{objdump -i}.) The script | |
846 | command @code{OUTPUT_FORMAT} can also specify the output format, but | |
847 | this option overrides it. @xref{BFD}. | |
7f9ae73e | 848 | @end ifclear |
346535cc | 849 | |
67afbcea DE |
850 | @kindex -qmagic |
851 | @item -qmagic | |
852 | This option is ignored for Linux compatibility. | |
c653b370 | 853 | |
67afbcea DE |
854 | @kindex -Qy |
855 | @item -Qy | |
856 | This option is ignored for SVR4 compatibility. | |
c653b370 | 857 | |
67afbcea | 858 | @kindex --relax |
1c48127e RP |
859 | @cindex synthesizing linker |
860 | @cindex relaxing addressing modes | |
67afbcea | 861 | @item --relax |
1fb57a5d RP |
862 | An option with machine dependent effects. |
863 | @ifset GENERIC | |
67afbcea | 864 | This option is only supported on a few targets. |
1fb57a5d | 865 | @end ifset |
ec40bbb8 DM |
866 | @ifset H8300 |
867 | @xref{H8/300,,@code{ld} and the H8/300}. | |
868 | @end ifset | |
1fb57a5d RP |
869 | @ifset I960 |
870 | @xref{i960,, @code{ld} and the Intel 960 family}. | |
871 | @end ifset | |
1c48127e | 872 | |
e2ebb8ed | 873 | |
67afbcea DE |
874 | On some platforms, the @samp{--relax} option performs global |
875 | optimizations that become possible when the linker resolves addressing | |
876 | in the program, such as relaxing address modes and synthesizing new | |
877 | instructions in the output object file. | |
1c48127e | 878 | |
e2ebb8ed JL |
879 | On some platforms these link time global optimizations may make symbolic |
880 | debugging of the resulting executable impossible. This is known to be | |
881 | the case for the Matsushita MN10200 and MN10300 family of processors. | |
882 | ||
1fb57a5d | 883 | @ifset GENERIC |
9fde46a4 ILT |
884 | On platforms where this is not supported, @samp{--relax} is accepted, |
885 | but ignored. | |
1fb57a5d | 886 | @end ifset |
1c48127e | 887 | |
7c8fab26 RP |
888 | @cindex retaining specified symbols |
889 | @cindex stripping all but some symbols | |
890 | @cindex symbols, retaining selectively | |
67afbcea | 891 | @item --retain-symbols-file @var{filename} |
7c8fab26 RP |
892 | Retain @emph{only} the symbols listed in the file @var{filename}, |
893 | discarding all others. @var{filename} is simply a flat file, with one | |
894 | symbol name per line. This option is especially useful in environments | |
895 | @ifset GENERIC | |
896 | (such as VxWorks) | |
897 | @end ifset | |
898 | where a large global symbol table is accumulated gradually, to conserve | |
899 | run-time memory. | |
900 | ||
9fde46a4 | 901 | @samp{--retain-symbols-file} does @emph{not} discard undefined symbols, |
7c8fab26 RP |
902 | or symbols needed for relocations. |
903 | ||
9fde46a4 | 904 | You may only specify @samp{--retain-symbols-file} once in the command |
7c8fab26 RP |
905 | line. It overrides @samp{-s} and @samp{-S}. |
906 | ||
a1ad915d ILT |
907 | @ifset GENERIC |
908 | @item -rpath @var{dir} | |
909 | @cindex runtime library search path | |
910 | @kindex -rpath | |
0b0642d6 ILT |
911 | Add a directory to the runtime library search path. This is used when |
912 | linking an ELF executable with shared objects. All @code{-rpath} | |
913 | arguments are concatenated and passed to the runtime linker, which uses | |
e54bf1c1 ILT |
914 | them to locate shared objects at runtime. The @code{-rpath} option is |
915 | also used when locating shared objects which are needed by shared | |
916 | objects explicitly included in the link; see the description of the | |
c653b370 ILT |
917 | @code{-rpath-link} option. If @code{-rpath} is not used when linking an |
918 | ELF executable, the contents of the environment variable | |
919 | @code{LD_RUN_PATH} will be used if it is defined. | |
0b0642d6 ILT |
920 | |
921 | The @code{-rpath} option may also be used on SunOS. By default, on | |
922 | SunOS, the linker will form a runtime search patch out of all the | |
e54bf1c1 | 923 | @code{-L} options it is given. If a @code{-rpath} option is used, the |
0b0642d6 ILT |
924 | runtime search path will be formed exclusively using the @code{-rpath} |
925 | options, ignoring the @code{-L} options. This can be useful when using | |
926 | gcc, which adds many @code{-L} options which may be on NFS mounted | |
927 | filesystems. | |
c653b370 ILT |
928 | |
929 | For compatibility with other ELF linkers, if the @code{-R} option is | |
930 | followed by a directory name, rather than a file name, it is treated as | |
931 | the @code{-rpath} option. | |
a1ad915d ILT |
932 | @end ifset |
933 | ||
e54bf1c1 ILT |
934 | @ifset GENERIC |
935 | @cindex link-time runtime library search path | |
936 | @kindex -rpath-link | |
937 | @item -rpath-link @var{DIR} | |
938 | When using ELF or SunOS, one shared library may require another. This | |
939 | happens when an @code{ld -shared} link includes a shared library as one | |
940 | of the input files. | |
941 | ||
942 | When the linker encounters such a dependency when doing a non-shared, | |
af54556a | 943 | non-relocatable link, it will automatically try to locate the required |
e54bf1c1 ILT |
944 | shared library and include it in the link, if it is not included |
945 | explicitly. In such a case, the @code{-rpath-link} option | |
946 | specifies the first set of directories to search. The | |
947 | @code{-rpath-link} option may specify a sequence of directory names | |
948 | either by specifying a list of names separated by colons, or by | |
949 | appearing multiple times. | |
950 | ||
951 | The linker uses the following search paths to locate required shared | |
952 | libraries. | |
953 | @enumerate | |
954 | @item | |
955 | Any directories specified by @code{-rpath-link} options. | |
956 | @item | |
957 | Any directories specified by @code{-rpath} options. The difference | |
958 | between @code{-rpath} and @code{-rpath-link} is that directories | |
959 | specified by @code{-rpath} options are included in the executable and | |
960 | used at runtime, whereas the @code{-rpath-link} option is only effective | |
961 | at link time. | |
962 | @item | |
c653b370 ILT |
963 | On an ELF system, if the @code{-rpath} and @code{rpath-link} options |
964 | were not used, search the contents of the environment variable | |
965 | @code{LD_RUN_PATH}. | |
966 | @item | |
e54bf1c1 ILT |
967 | On SunOS, if the @code{-rpath} option was not used, search any |
968 | directories specified using @code{-L} options. | |
969 | @item | |
970 | For a native linker, the contents of the environment variable | |
971 | @code{LD_LIBRARY_PATH}. | |
972 | @item | |
973 | The default directories, normally @file{/lib} and @file{/usr/lib}. | |
6581c418 ILT |
974 | @item |
975 | For a native linker on an ELF system, if the file @file{/etc/ld.so.conf} | |
976 | exists, the list of directories found in that file. | |
e54bf1c1 ILT |
977 | @end enumerate |
978 | ||
979 | If the required shared library is not found, the linker will issue a | |
980 | warning and continue with the link. | |
981 | @end ifset | |
982 | ||
67afbcea DE |
983 | @kindex -shared |
984 | @kindex -Bshareable | |
4551e108 | 985 | @item -shared |
67afbcea | 986 | @itemx -Bshareable |
4551e108 | 987 | @cindex shared libraries |
67afbcea DE |
988 | Create a shared library. This is currently only supported on ELF, XCOFF |
989 | and SunOS platforms. On SunOS, the linker will automatically create a | |
e54bf1c1 ILT |
990 | shared library if the @code{-e} option is not used and there are |
991 | undefined symbols in the link. | |
4551e108 | 992 | |
67afbcea DE |
993 | @item --sort-common |
994 | @kindex --sort-common | |
995 | This option tells @code{ld} to sort the common symbols by size when it | |
996 | places them in the appropriate output sections. First come all the one | |
997 | byte symbols, then all the two bytes, then all the four bytes, and then | |
998 | everything else. This is to prevent gaps between symbols due to | |
999 | alignment constraints. | |
1000 | ||
1001 | @kindex --split-by-file | |
1002 | @item --split-by-file | |
1003 | Similar to @code{--split-by-reloc} but creates a new output section for | |
1004 | each input file. | |
1005 | ||
1006 | @kindex --split-by-reloc | |
1007 | @item --split-by-reloc @var{count} | |
1008 | Trys to creates extra sections in the output file so that no single | |
1009 | output section in the file contains more than @var{count} relocations. | |
1010 | This is useful when generating huge relocatable for downloading into | |
1011 | certain real time kernels with the COFF object file format; since COFF | |
1012 | cannot represent more than 65535 relocations in a single section. Note | |
1013 | that this will fail to work with object file formats which do not | |
1014 | support arbitrary sections. The linker will not split up individual | |
1015 | input sections for redistribution, so if a single input section contains | |
01bc8f35 ILT |
1016 | more than @var{count} relocations one output section will contain that |
1017 | many relocations. | |
1018 | ||
67afbcea DE |
1019 | @kindex --stats |
1020 | @item --stats | |
1021 | Compute and display statistics about the operation of the linker, such | |
1022 | as execution time and memory usage. | |
f22eee08 | 1023 | |
9fde46a4 | 1024 | @kindex --traditional-format |
c96386c4 | 1025 | @cindex traditional format |
9fde46a4 | 1026 | @item --traditional-format |
c96386c4 ILT |
1027 | For some targets, the output of @code{ld} is different in some ways from |
1028 | the output of some existing linker. This switch requests @code{ld} to | |
1029 | use the traditional format instead. | |
1030 | ||
1031 | @cindex dbx | |
1032 | For example, on SunOS, @code{ld} combines duplicate entries in the | |
1033 | symbol string table. This can reduce the size of an output file with | |
1034 | full debugging information by over 30 percent. Unfortunately, the SunOS | |
1035 | @code{dbx} program can not read the resulting program (@code{gdb} has no | |
9fde46a4 | 1036 | trouble). The @samp{--traditional-format} switch tells @code{ld} to not |
c96386c4 ILT |
1037 | combine duplicate entries. |
1038 | ||
67afbcea DE |
1039 | @kindex -Tbss @var{org} |
1040 | @kindex -Tdata @var{org} | |
1041 | @kindex -Ttext @var{org} | |
1042 | @cindex segment origins, cmd line | |
1043 | @item -Tbss @var{org} | |
1044 | @itemx -Tdata @var{org} | |
1045 | @itemx -Ttext @var{org} | |
1046 | Use @var{org} as the starting address for---respectively---the | |
1047 | @code{bss}, @code{data}, or the @code{text} segment of the output file. | |
1048 | @var{org} must be a single hexadecimal integer; | |
1049 | for compatibility with other linkers, you may omit the leading | |
1050 | @samp{0x} usually associated with hexadecimal values. | |
f22eee08 | 1051 | |
2c5c0674 | 1052 | @kindex -Ur |
b4d4e8e3 | 1053 | @cindex constructors |
d4e5e3c3 | 1054 | @item -Ur |
b4d4e8e3 | 1055 | For anything other than C++ programs, this option is equivalent to |
ec40bbb8 DM |
1056 | @samp{-r}: it generates relocatable output---i.e., an output file that can in |
1057 | turn serve as input to @code{ld}. When linking C++ programs, @samp{-Ur} | |
1fb57a5d | 1058 | @emph{does} resolve references to constructors, unlike @samp{-r}. |
3e27cc11 | 1059 | It does not work to use @samp{-Ur} on files that were themselves linked |
1fb57a5d | 1060 | with @samp{-Ur}; once the constructor table has been built, it cannot |
3e27cc11 DM |
1061 | be added to. Use @samp{-Ur} only for the last partial link, and |
1062 | @samp{-r} for the others. | |
b4d4e8e3 | 1063 | |
01bc8f35 | 1064 | @kindex --verbose |
cf2e4f5f | 1065 | @cindex verbose |
01bc8f35 | 1066 | @item --verbose |
1fb57a5d | 1067 | Display the version number for @code{ld} and list the linker emulations |
cf2e4f5f ILT |
1068 | supported. Display which input files can and cannot be opened. Display |
1069 | the linker script if using a default builtin script. | |
8ddef552 | 1070 | |
5a59e34d ILT |
1071 | @kindex --version-script=@var{version-scriptfile} |
1072 | @cindex version script, symbol versions | |
1073 | @itemx --version-script=@var{version-scriptfile} | |
1074 | Specify the name of a version script to the linker. This is typically | |
1075 | used when creating shared libraries to specify additional information | |
1076 | about the version heirarchy for the library being created. This option | |
1077 | is only meaningful on ELF platforms which support shared libraries. | |
af54556a | 1078 | @xref{VERSION}. |
5a59e34d | 1079 | |
458fc056 | 1080 | @kindex --warn-comon |
7f9ae73e RP |
1081 | @cindex warnings, on combining symbols |
1082 | @cindex combining symbols, warnings on | |
458fc056 | 1083 | @item --warn-common |
2a28d8b0 DM |
1084 | Warn when a common symbol is combined with another common symbol or with |
1085 | a symbol definition. Unix linkers allow this somewhat sloppy practice, | |
1086 | but linkers on some other operating systems do not. This option allows | |
1087 | you to find potential problems from combining global symbols. | |
1cd4cca9 DM |
1088 | Unfortunately, some C libraries use this practice, so you may get some |
1089 | warnings about symbols in the libraries as well as in your programs. | |
2a28d8b0 DM |
1090 | |
1091 | There are three kinds of global symbols, illustrated here by C examples: | |
1092 | ||
1093 | @table @samp | |
1094 | @item int i = 1; | |
1095 | A definition, which goes in the initialized data section of the output | |
1096 | file. | |
1097 | ||
1098 | @item extern int i; | |
1099 | An undefined reference, which does not allocate space. | |
1100 | There must be either a definition or a common symbol for the | |
1101 | variable somewhere. | |
1102 | ||
1103 | @item int i; | |
1104 | A common symbol. If there are only (one or more) common symbols for a | |
1105 | variable, it goes in the uninitialized data area of the output file. | |
1106 | The linker merges multiple common symbols for the same variable into a | |
1107 | single symbol. If they are of different sizes, it picks the largest | |
1108 | size. The linker turns a common symbol into a declaration, if there is | |
1109 | a definition of the same variable. | |
1110 | @end table | |
1111 | ||
458fc056 ILT |
1112 | The @samp{--warn-common} option can produce five kinds of warnings. |
1113 | Each warning consists of a pair of lines: the first describes the symbol | |
1114 | just encountered, and the second describes the previous symbol | |
1115 | encountered with the same name. One or both of the two symbols will be | |
1116 | a common symbol. | |
2a28d8b0 DM |
1117 | |
1118 | @enumerate | |
1119 | @item | |
1120 | Turning a common symbol into a reference, because there is already a | |
1121 | definition for the symbol. | |
1122 | @smallexample | |
8920addc RP |
1123 | @var{file}(@var{section}): warning: common of `@var{symbol}' |
1124 | overridden by definition | |
2a28d8b0 DM |
1125 | @var{file}(@var{section}): warning: defined here |
1126 | @end smallexample | |
1127 | ||
1128 | @item | |
1129 | Turning a common symbol into a reference, because a later definition for | |
1130 | the symbol is encountered. This is the same as the previous case, | |
1131 | except that the symbols are encountered in a different order. | |
1132 | @smallexample | |
8920addc RP |
1133 | @var{file}(@var{section}): warning: definition of `@var{symbol}' |
1134 | overriding common | |
2a28d8b0 DM |
1135 | @var{file}(@var{section}): warning: common is here |
1136 | @end smallexample | |
1137 | ||
1138 | @item | |
1139 | Merging a common symbol with a previous same-sized common symbol. | |
1140 | @smallexample | |
8920addc RP |
1141 | @var{file}(@var{section}): warning: multiple common |
1142 | of `@var{symbol}' | |
2a28d8b0 DM |
1143 | @var{file}(@var{section}): warning: previous common is here |
1144 | @end smallexample | |
1145 | ||
1146 | @item | |
1147 | Merging a common symbol with a previous larger common symbol. | |
1148 | @smallexample | |
8920addc RP |
1149 | @var{file}(@var{section}): warning: common of `@var{symbol}' |
1150 | overridden by larger common | |
2a28d8b0 DM |
1151 | @var{file}(@var{section}): warning: larger common is here |
1152 | @end smallexample | |
1153 | ||
1154 | @item | |
1155 | Merging a common symbol with a previous smaller common symbol. This is | |
1156 | the same as the previous case, except that the symbols are | |
1157 | encountered in a different order. | |
1158 | @smallexample | |
8920addc RP |
1159 | @var{file}(@var{section}): warning: common of `@var{symbol}' |
1160 | overriding smaller common | |
2a28d8b0 DM |
1161 | @var{file}(@var{section}): warning: smaller common is here |
1162 | @end smallexample | |
1163 | @end enumerate | |
1164 | ||
458fc056 ILT |
1165 | @kindex --warn-constructors |
1166 | @item --warn-constructors | |
0b0642d6 ILT |
1167 | Warn if any global constructors are used. This is only useful for a few |
1168 | object file formats. For formats like COFF or ELF, the linker can not | |
1169 | detect the use of global constructors. | |
1170 | ||
458fc056 ILT |
1171 | @kindex --warn-multiple-gp |
1172 | @item --warn-multiple-gp | |
4b7d2399 ILT |
1173 | Warn if multiple global pointer values are required in the output file. |
1174 | This is only meaningful for certain processors, such as the Alpha. | |
1175 | Specifically, some processors put large-valued constants in a special | |
1176 | section. A special register (the global pointer) points into the middle | |
1177 | of this section, so that constants can be loaded efficiently via a | |
1178 | base-register relative addressing mode. Since the offset in | |
1179 | base-register relative mode is fixed and relatively small (e.g., 16 | |
1180 | bits), this limits the maximum size of the constant pool. Thus, in | |
1181 | large programs, it is often necessary to use multiple global pointer | |
1182 | values in order to be able to address all possible constants. This | |
1183 | option causes a warning to be issued whenever this case occurs. | |
1184 | ||
458fc056 | 1185 | @kindex --warn-once |
01bc8f35 ILT |
1186 | @cindex warnings, on undefined symbols |
1187 | @cindex undefined symbols, warnings on | |
458fc056 | 1188 | @item --warn-once |
01bc8f35 ILT |
1189 | Only warn once for each undefined symbol, rather than once per module |
1190 | which refers to it. | |
1191 | ||
458fc056 ILT |
1192 | @kindex --warn-section-align |
1193 | @cindex warnings, on section alignment | |
1194 | @cindex section alignment, warnings on | |
1195 | @item --warn-section-align | |
1196 | Warn if the address of an output section is changed because of | |
1197 | alignment. Typically, the alignment will be set by an input section. | |
1198 | The address will only be changed if it not explicitly specified; that | |
1199 | is, if the @code{SECTIONS} command does not specify a start address for | |
1200 | the section (@pxref{SECTIONS}). | |
1201 | ||
4551e108 ILT |
1202 | @kindex --whole-archive |
1203 | @cindex including an entire archive | |
4b7d2399 | 1204 | @item --whole-archive |
3c8deccc ILT |
1205 | For each archive mentioned on the command line after the |
1206 | @code{--whole-archive} option, include every object file in the archive | |
1207 | in the link, rather than searching the archive for the required object | |
1208 | files. This is normally used to turn an archive file into a shared | |
1209 | library, forcing every object to be included in the resulting shared | |
67afbcea | 1210 | library. This option may be used more than once. |
4551e108 | 1211 | |
e3d73386 ILT |
1212 | @kindex --wrap |
1213 | @item --wrap @var{symbol} | |
1214 | Use a wrapper function for @var{symbol}. Any undefined reference to | |
1215 | @var{symbol} will be resolved to @code{__wrap_@var{symbol}}. Any | |
1216 | undefined reference to @code{__real_@var{symbol}} will be resolved to | |
1217 | @var{symbol}. | |
1218 | ||
1219 | This can be used to provide a wrapper for a system function. The | |
1220 | wrapper function should be called @code{__wrap_@var{symbol}}. If it | |
1221 | wishes to call the system function, it should call | |
1222 | @code{__real_@var{symbol}}. | |
1223 | ||
1224 | Here is a trivial example: | |
1225 | ||
1226 | @smallexample | |
1227 | void * | |
1228 | __wrap_malloc (int c) | |
1229 | @{ | |
1230 | printf ("malloc called with %ld\n", c); | |
1231 | return __real_malloc (c); | |
1232 | @} | |
1233 | @end smallexample | |
1234 | ||
1235 | If you link other code with this file using @code{--wrap malloc}, then | |
1236 | all calls to @code{malloc} will call the function @code{__wrap_malloc} | |
1237 | instead. The call to @code{__real_malloc} in @code{__wrap_malloc} will | |
1238 | call the real @code{malloc} function. | |
1239 | ||
1240 | You may wish to provide a @code{__real_malloc} function as well, so that | |
1241 | links without the @code{--wrap} option will succeed. If you do this, | |
1242 | you should not put the definition of @code{__real_malloc} in the same | |
1243 | file as @code{__wrap_malloc}; if you do, the assembler may resolve the | |
1244 | call before the linker has a chance to wrap it to @code{malloc}. | |
1245 | ||
f22eee08 | 1246 | @end table |
b4d4e8e3 | 1247 | |
ec40bbb8 DM |
1248 | @ifset UsesEnvVars |
1249 | @node Environment | |
2c5c0674 RP |
1250 | @section Environment Variables |
1251 | ||
f4175166 ILT |
1252 | You can change the behavior of @code{ld} with the environment variables |
1253 | @code{GNUTARGET} and @code{LDEMULATION}. | |
2c5c0674 RP |
1254 | |
1255 | @kindex GNUTARGET | |
1256 | @cindex default input format | |
1257 | @code{GNUTARGET} determines the input-file object format if you don't | |
9fde46a4 | 1258 | use @samp{-b} (or its synonym @samp{--format}). Its value should be one |
2c5c0674 | 1259 | of the BFD names for an input format (@pxref{BFD}). If there is no |
246504a5 | 1260 | @code{GNUTARGET} in the environment, @code{ld} uses the natural format |
9fde46a4 ILT |
1261 | of the target. If @code{GNUTARGET} is set to @code{default} then BFD |
1262 | attempts to discover the input format by examining binary input files; | |
1263 | this method often succeeds, but there are potential ambiguities, since | |
1264 | there is no method of ensuring that the magic number used to specify | |
1265 | object-file formats is unique. However, the configuration procedure for | |
1266 | BFD on each system places the conventional format for that system first | |
1267 | in the search-list, so ambiguities are resolved in favor of convention. | |
f4175166 ILT |
1268 | |
1269 | @kindex LDEMULATION | |
1270 | @cindex default emulation | |
1271 | @cindex emulation, default | |
1272 | @code{LDEMULATION} determines the default emulation if you don't use the | |
1273 | @samp{-m} option. The emulation can affect various aspects of linker | |
1274 | behaviour, particularly the default linker script. You can list the | |
1275 | available emulations with the @samp{--verbose} or @samp{-V} options. If | |
1276 | the @samp{-m} option is not used, and the @code{LDEMULATION} environment | |
1277 | variable is not defined, the default emulation depends upon how the | |
1278 | linker was configured. | |
ec40bbb8 | 1279 | @end ifset |
2c5c0674 | 1280 | |
af54556a ILT |
1281 | @node Scripts |
1282 | @chapter Linker Scripts | |
f22eee08 | 1283 | |
af54556a ILT |
1284 | @cindex scripts |
1285 | @cindex linker scripts | |
2c5c0674 | 1286 | @cindex command files |
af54556a ILT |
1287 | Every link is controlled by a @dfn{linker script}. This script is |
1288 | written in the linker command language. | |
1289 | ||
1290 | The main purpose of the linker script is to describe how the sections in | |
1291 | the input files should be mapped into the output file, and to control | |
1292 | the memory layout of the output file. Most linker scripts do nothing | |
1293 | more than this. However, when necessary, the linker script can also | |
1294 | direct the linker to perform many other operations, using the commands | |
1295 | described below. | |
1296 | ||
1297 | The linker always uses a linker script. If you do not supply one | |
1298 | yourself, the linker will use a default script that is compiled into the | |
1299 | linker executable. You can use the @samp{--verbose} command line option | |
1300 | to display the default linker script. Certain command line options, | |
1301 | such as @samp{-r} or @samp{-N}, will affect the default linker script. | |
1302 | ||
1303 | You may supply your own linker script by using the @samp{-T} command | |
1304 | line option. When you do this, your linker script will replace the | |
1305 | default linker script. | |
1306 | ||
1307 | You may also use linker scripts implicitly by naming them as input files | |
f8cf2baa ILT |
1308 | to the linker, as though they were files to be linked. @xref{Implicit |
1309 | Linker Scripts}. | |
f22eee08 | 1310 | |
af54556a ILT |
1311 | @menu |
1312 | * Basic Script Concepts:: Basic Linker Script Concepts | |
1313 | * Script Format:: Linker Script Format | |
1314 | * Simple Example:: Simple Linker Script Example | |
1315 | * Simple Commands:: Simple Linker Script Commands | |
1316 | * Assignments:: Assigning Values to Symbols | |
1317 | * SECTIONS:: SECTIONS Command | |
1318 | * MEMORY:: MEMORY Command | |
1319 | * PHDRS:: PHDRS Command | |
1320 | * VERSION:: VERSION Command | |
1321 | * Expressions:: Expressions in Linker Scripts | |
f8cf2baa | 1322 | * Implicit Linker Scripts:: Implicit Linker Scripts |
af54556a ILT |
1323 | @end menu |
1324 | ||
1325 | @node Basic Script Concepts | |
1326 | @section Basic Linker Script Concepts | |
1327 | @cindex linker script concepts | |
1328 | We need to define some basic concepts and vocabulary in order to | |
1329 | describe the linker script language. | |
1330 | ||
1331 | The linker combines input files into a single output file. The output | |
1332 | file and each input file are in a special data format known as an | |
1333 | @dfn{object file format}. Each file is called an @dfn{object file}. | |
1334 | The output file is often called an @dfn{executable}, but for our | |
1335 | purposes we will also call it an object file. Each object file has, | |
1336 | among other things, a list of @dfn{sections}. We sometimes refer to a | |
1337 | section in an input file as an @dfn{input section}; similarly, a section | |
1338 | in the output file is an @dfn{output section}. | |
1339 | ||
1340 | Each section in an object file has a name and a size. Most sections | |
1341 | also have an associated block of data, known as the @dfn{section | |
1342 | contents}. A section may be marked as @dfn{loadable}, which mean that | |
1343 | the contents should be loaded into memory when the output file is run. | |
1344 | A section with no contents may be @dfn{allocatable}, which means that an | |
1345 | area in memory should be set aside, but nothing in particular should be | |
1346 | loaded there (in some cases this memory must be zeroed out). A section | |
1347 | which is neither loadable nor allocatable typically contains some sort | |
1348 | of debugging information. | |
1349 | ||
1350 | Every loadable or allocatable output section has two addresses. The | |
1351 | first is the @dfn{VMA}, or virtual memory address. This is the address | |
36a8f215 | 1352 | the section will have when the output file is run. The second is the |
af54556a ILT |
1353 | @dfn{LMA}, or load memory address. This is the address at which the |
1354 | section will be loaded. In most cases the two addresses will be the | |
1355 | same. An example of when they might be different is when a data section | |
1356 | is loaded into ROM, and then copied into RAM when the program starts up | |
1357 | (this technique is often used to initialize global variables in a ROM | |
1358 | based system). In this case the ROM address would be the LMA, and the | |
1359 | RAM address would be the VMA. | |
1360 | ||
1361 | You can see the sections in an object file by using the @code{objdump} | |
1362 | program with the @samp{-h} option. | |
1363 | ||
1364 | Every object file also has a list of @dfn{symbols}, known as the | |
1365 | @dfn{symbol table}. A symbol may be defined or undefined. Each symbol | |
1366 | has a name, and each defined symbol has an address, among other | |
1367 | information. If you compile a C or C++ program into an object file, you | |
1368 | will get a defined symbol for every defined function and global or | |
1369 | static variable. Every undefined function or global variable which is | |
1370 | referenced in the input file will become an undefined symbol. | |
1371 | ||
1372 | You can see the symbols in an object file by using the @code{nm} | |
1373 | program, or by using the @code{objdump} program with the @samp{-t} | |
1374 | option. | |
1375 | ||
1376 | @node Script Format | |
1377 | @section Linker Script Format | |
1378 | @cindex linker script format | |
1379 | Linker scripts are text files. | |
1380 | ||
1381 | You write a linker script as a series of commands. Each command is | |
1382 | either a keyword, possibly followed by arguments, or an assignment to a | |
1383 | symbol. You may separate commands using semicolons. Whitespace is | |
1384 | generally ignored. | |
1385 | ||
1386 | Strings such as file or format names can normally be entered directly. | |
1387 | If the file name contains a character such as a comma which would | |
1388 | otherwise serve to separate file names, you may put the file name in | |
1389 | double quotes. There is no way to use a double quote character in a | |
1390 | file name. | |
1391 | ||
1392 | You may include comments in linker scripts just as in C, delimited by | |
1393 | @samp{/*} and @samp{*/}. As in C, comments are syntactically equivalent | |
1394 | to whitespace. | |
1395 | ||
1396 | @node Simple Example | |
1397 | @section Simple Linker Script Example | |
1398 | @cindex linker script example | |
1399 | @cindex example of linker script | |
1400 | Many linker scripts are fairly simple. | |
1401 | ||
1402 | The simplest possible linker script has just one command: | |
1403 | @samp{SECTIONS}. You use the @samp{SECTIONS} command to describe the | |
1404 | memory layout of the output file. | |
1405 | ||
1406 | The @samp{SECTIONS} command is a powerful command. Here we will | |
1407 | describe a simple use of it. Let's assume your program consists only of | |
1408 | code, initialized data, and uninitialized data. These will be in the | |
1409 | @samp{.text}, @samp{.data}, and @samp{.bss} sections, respectively. | |
1410 | Let's assume further that these are the only sections which appear in | |
1411 | your input files. | |
1412 | ||
1413 | For this example, let's say that the code should be loaded at address | |
1414 | 0x10000, and that the data should start at address 0x8000000. Here is a | |
1415 | linker script which will do that: | |
1416 | @smallexample | |
1417 | SECTIONS | |
1418 | @{ | |
1419 | . = 0x10000; | |
1420 | .text : @{ *(.text) @} | |
1421 | . = 0x8000000; | |
1422 | .data : @{ *(.data) @} | |
1423 | .bss : @{ *(.bss) @} | |
1424 | @} | |
1425 | @end smallexample | |
f9c5c231 | 1426 | |
af54556a ILT |
1427 | You write the @samp{SECTIONS} command as the keyword @samp{SECTIONS}, |
1428 | followed by a series of symbol assignments and output section | |
1429 | descriptions enclosed in curly braces. | |
1430 | ||
1431 | The first line in the above example sets the special symbol @samp{.}, | |
1432 | which is the location counter. If you do not specify the address of an | |
1433 | output section in some other way (other ways are described later), the | |
1434 | address is set from the current value of the location counter. The | |
1435 | location counter is then incremented by the size of the output section. | |
1436 | ||
36a8f215 ILT |
1437 | The first line inside the @samp{SECTIONS} command of the above example |
1438 | sets the value of the special symbol @samp{.}, which is the location | |
1439 | counter. If you do not specify the address of an output section in some | |
1440 | other way (other ways are described later), the address is set from the | |
1441 | current value of the location counter. The location counter is then | |
1442 | incremented by the size of the output section. At the start of the | |
1443 | @samp{SECTIONS} command, the location counter has the value @samp{0}. | |
1444 | ||
af54556a ILT |
1445 | The second line defines an output section, @samp{.text}. The colon is |
1446 | required syntax which may be ignored for now. Within the curly braces | |
1447 | after the output section name, you list the names of the input sections | |
1448 | which should be placed into this output section. The @samp{*} is a | |
1449 | wildcard which matches any file name. The expression @samp{*(.text)} | |
1450 | means all @samp{.text} input sections in all input files. | |
1451 | ||
1452 | Since the location counter is @samp{0x10000} when the output section | |
1453 | @samp{.text} is defined, the linker will set the address of the | |
1454 | @samp{.text} section in the output file to be @samp{0x10000}. | |
1455 | ||
1456 | The remaining lines define the @samp{.data} and @samp{.bss} sections in | |
36a8f215 ILT |
1457 | the output file. The linker will place the @samp{.data} output section |
1458 | at address @samp{0x8000000}. After the linker places the @samp{.data} | |
1459 | output section, the value of the location counter will be | |
1460 | @samp{0x8000000} plus the size of the @samp{.data} output section. The | |
1461 | effect is that the linker will place the @samp{.bss} output section | |
1462 | immediately after the @samp{.data} output section in memory | |
1463 | ||
1464 | The linker will ensure that each output section has the required | |
1465 | alignment, by increasing the location counter if necessary. In this | |
1466 | example, the specified addresses for the @samp{.text} and @samp{.data} | |
1467 | sections will probably satisfy any alignment constraints, but the linker | |
1468 | may have to create a small gap between the @samp{.data} and @samp{.bss} | |
1469 | sections. | |
af54556a ILT |
1470 | |
1471 | That's it! That's a simple and complete linker script. | |
1472 | ||
1473 | @node Simple Commands | |
1474 | @section Simple Linker Script Commands | |
1475 | @cindex linker script simple commands | |
1476 | In this section we describe the simple linker script commands. | |
2c5c0674 | 1477 | |
2c5c0674 | 1478 | @menu |
af54556a ILT |
1479 | * Entry Point:: Setting the entry point |
1480 | * File Commands:: Commands dealing with files | |
1481 | @ifclear SingleFormat | |
1482 | * Format Commands:: Commands dealing with object file formats | |
1483 | @end ifclear | |
1484 | ||
1485 | * Miscellaneous Commands:: Other linker script commands | |
2c5c0674 RP |
1486 | @end menu |
1487 | ||
af54556a ILT |
1488 | @node Entry Point |
1489 | @subsection Setting the entry point | |
1490 | @kindex ENTRY(@var{symbol}) | |
1491 | @cindex start of execution | |
1492 | @cindex first instruction | |
1493 | @cindex entry point | |
1494 | The first instruction to execute in a program is called the @dfn{entry | |
1495 | point}. You can use the @code{ENTRY} linker script command to set the | |
1496 | entry point. The argument is a symbol name: | |
1497 | @smallexample | |
1498 | ENTRY(@var{symbol}) | |
1499 | @end smallexample | |
2c5c0674 | 1500 | |
af54556a ILT |
1501 | There are several ways to set the entry point. The linker will set the |
1502 | entry point by trying each of the following methods in order, and | |
1503 | stopping when one of them succeeds: | |
b4d4e8e3 | 1504 | @itemize @bullet |
2c5c0674 | 1505 | @item |
af54556a | 1506 | the @samp{-e} @var{entry} command-line option; |
2c5c0674 | 1507 | @item |
af54556a | 1508 | the @code{ENTRY(@var{symbol})} command in a linker script; |
2c5c0674 | 1509 | @item |
af54556a | 1510 | the value of the symbol @code{start}, if defined; |
2c5c0674 | 1511 | @item |
af54556a | 1512 | the address of the first byte of the @samp{.text} section, if present; |
2c5c0674 | 1513 | @item |
af54556a | 1514 | The address @code{0}. |
b4d4e8e3 | 1515 | @end itemize |
f22eee08 | 1516 | |
af54556a ILT |
1517 | @node File Commands |
1518 | @subsection Commands dealing with files | |
1519 | @cindex linker script file commands | |
1520 | Several linker script commands deal with files. | |
f22eee08 | 1521 | |
af54556a ILT |
1522 | @table @code |
1523 | @item INCLUDE @var{filename} | |
1524 | @kindex INCLUDE @var{filename} | |
1525 | @cindex including a linker script | |
1526 | Include the linker script @var{filename} at this point. The file will | |
1527 | be searched for in the current directory, and in any directory specified | |
1528 | with the @code{-L} option. You can nest calls to @code{INCLUDE} up to | |
1529 | 10 levels deep. | |
f22eee08 | 1530 | |
af54556a ILT |
1531 | @item INPUT(@var{file}, @var{file}, @dots{}) |
1532 | @itemx INPUT(@var{file} @var{file} @dots{}) | |
1533 | @kindex INPUT(@var{files}) | |
1534 | @cindex input files in linker scripts | |
1535 | @cindex input object files in linker scripts | |
1536 | @cindex linker script input object files | |
1537 | The @code{INPUT} command directs the linker to include the named files | |
1538 | in the link, as though they were named on the command line. | |
1539 | ||
1540 | For example, if you always want to include @file{subr.o} any time you do | |
1541 | a link, but you can't be bothered to put it on every link command line, | |
1542 | then you can put @samp{INPUT (subr.o)} in your linker script. | |
1543 | ||
1544 | In fact, if you like, you can list all of your input files in the linker | |
1545 | script, and then invoke the linker with nothing but a @samp{-T} option. | |
1546 | ||
1547 | The linker will first try to open the file in the current directory. If | |
1548 | it is not found, the linker will search through the archive library | |
1549 | search path. See the description of @samp{-L} in @ref{Options,,Command | |
1550 | Line Options}. | |
1551 | ||
1552 | If you use @samp{INPUT (-l@var{file})}, @code{ld} will transform the | |
1553 | name to @code{lib@var{file}.a}, as with the command line argument | |
1554 | @samp{-l}. | |
1555 | ||
1556 | When you use the @code{INPUT} command in an implicit linker script, the | |
1557 | files will be included in the link at the point at which the linker | |
1558 | script file is included. This can affect archive searching. | |
1559 | ||
1560 | @item GROUP(@var{file}, @var{file}, @dots{}) | |
1561 | @itemx GROUP(@var{file} @var{file} @dots{}) | |
1562 | @kindex GROUP(@var{files}) | |
1563 | @cindex grouping input files | |
1564 | The @code{GROUP} command is like @code{INPUT}, except that the named | |
1565 | files should all be archives, and they are searched repeatedly until no | |
1566 | new undefined references are created. See the description of @samp{-(} | |
1567 | in @ref{Options,,Command Line Options}. | |
1568 | ||
1569 | @item OUTPUT(@var{filename}) | |
1570 | @kindex OUTPUT(@var{filename}) | |
1571 | @cindex output file name in linker scripot | |
1572 | The @code{OUTPUT} command names the output file. Using | |
1573 | @code{OUTPUT(@var{filename})} in the linker script is exactly like using | |
1574 | @samp{-o @var{filename}} on the command line (@pxref{Options,,Command | |
1575 | Line Options}). If both are used, the command line option takes | |
1576 | precedence. | |
1577 | ||
1578 | You can use the @code{OUTPUT} command to define a default name for the | |
1579 | output file other than the usual default of @file{a.out}. | |
1580 | ||
1581 | @item SEARCH_DIR(@var{path}) | |
1582 | @kindex SEARCH_DIR(@var{path}) | |
1583 | @cindex library search path in linker script | |
1584 | @cindex archive search path in linker script | |
1585 | @cindex search path in linker script | |
1586 | The @code{SEARCH_DIR} command adds @var{path} to the list of paths where | |
1587 | @code{ld} looks for archive libraries. Using | |
1588 | @code{SEARCH_DIR(@var{path})} is exactly like using @samp{-L @var{path}} | |
1589 | on the command line (@pxref{Options,,Command Line Options}). If both | |
1590 | are used, then the linker will search both paths. Paths specified using | |
1591 | the command line option are searched first. | |
1592 | ||
1593 | @item STARTUP(@var{filename}) | |
1594 | @kindex STARTUP(@var{filename}) | |
1595 | @cindex first input file | |
1596 | The @code{STARTUP} command is just like the @code{INPUT} command, except | |
1597 | that @var{filename} will become the first input file to be linked, as | |
1598 | though it were specified first on the command line. This may be useful | |
1599 | when using a system in which the entry point is always the start of the | |
1600 | first file. | |
1601 | @end table | |
f22eee08 | 1602 | |
af54556a ILT |
1603 | @ifclear SingleFormat |
1604 | @node Format Commands | |
1605 | @subsection Commands dealing with object file formats | |
1606 | A couple of linker script commands deal with object file formats. | |
f22eee08 | 1607 | |
af54556a ILT |
1608 | @table @code |
1609 | @item OUTPUT_FORMAT(@var{bfdname}) | |
1610 | @itemx OUTPUT_FORMAT(@var{default}, @var{big}, @var{little}) | |
1611 | @kindex OUTPUT_FORMAT(@var{bfdname}) | |
1612 | @cindex output file format in linker script | |
1613 | The @code{OUTPUT_FORMAT} command names the BFD format to use for the | |
1614 | output file (@pxref{BFD}). Using @code{OUTPUT_FORMAT(@var{bfdname})} is | |
1615 | exactly like using @samp{-oformat @var{bfdname}} on the command line | |
1616 | (@pxref{Options,,Command Line Options}). If both are used, the command | |
1617 | line option takes precedence. | |
1618 | ||
1619 | You can use @code{OUTPUT_FORMAT} with three arguments to use different | |
1620 | formats based on the @samp{-EB} and @samp{-EL} command line options. | |
1621 | This permits the linker script to set the output format based on the | |
1622 | desired endianness. | |
1623 | ||
1624 | If neither @samp{-EB} nor @samp{-EL} are used, then the output format | |
1625 | will be the first argument, @var{default}. If @samp{-EB} is used, the | |
1626 | output format will be the second argument, @var{big}. If @samp{-EL} is | |
1627 | used, the output format will be the third argument, @var{little}. | |
1628 | ||
1629 | For example, the default linker script for the MIPS ELF target uses this | |
1630 | command: | |
c653b370 | 1631 | @smallexample |
af54556a | 1632 | OUTPUT_FORMAT(elf32-bigmips, elf32-bigmips, elf32-littlemips) |
c653b370 | 1633 | @end smallexample |
af54556a ILT |
1634 | This says that the default format for the output file is |
1635 | @samp{elf32-bigmips}, but if the user uses the @samp{-EL} command line | |
1636 | option, the output file will be created in the @samp{elf32-littlemips} | |
1637 | format. | |
1638 | ||
1639 | @item TARGET(@var{bfdname}) | |
1640 | @kindex TARGET(@var{bfdname}) | |
1641 | @cindex input file format in linker script | |
1642 | The @code{TARGET} command names the BFD format to use when reading input | |
1643 | files. It affects subsequent @code{INPUT} and @code{GROUP} commands. | |
1644 | This command is like using @samp{-b @var{bfdname}} on the command line | |
1645 | (@pxref{Options,,Command Line Options}). If the @code{TARGET} command | |
1646 | is used but @code{OUTPUT_FORMAT} is not, then the last @code{TARGET} | |
1647 | command is also used to set the format for the output file. @xref{BFD}. | |
1648 | @end table | |
1649 | @end ifclear | |
b4d4e8e3 | 1650 | |
af54556a ILT |
1651 | @node Miscellaneous Commands |
1652 | @subsection Other linker script commands | |
1653 | There are a few other linker scripts commands. | |
b4d4e8e3 | 1654 | |
af54556a ILT |
1655 | @table @code |
1656 | @item FORCE_COMMON_ALLOCATION | |
1657 | @kindex FORCE_COMMON_ALLOCATION | |
ed1cc83d | 1658 | @cindex common allocation in linker script |
af54556a ILT |
1659 | This command has the same effect as the @samp{-d} command-line option: |
1660 | to make @code{ld} assign space to common symbols even if a relocatable | |
1661 | output file is specified (@samp{-r}). | |
1fb57a5d | 1662 | |
af54556a ILT |
1663 | @item NOCROSSREFS(@var{section} @var{section} @dots{}) |
1664 | @kindex NOCROSSREFS(@var{sections}) | |
1665 | @cindex cross references | |
1666 | This command may be used to tell @code{ld} to issue an error about any | |
1667 | references among certain output sections. | |
b4d4e8e3 | 1668 | |
af54556a ILT |
1669 | In certain types of programs, particularly on embedded systems when |
1670 | using overlays, when one section is loaded into memory, another section | |
1671 | will not be. Any direct references between the two sections would be | |
1672 | errors. For example, it would be an error if code in one section called | |
1673 | a function defined in the other section. | |
d4e5e3c3 | 1674 | |
af54556a ILT |
1675 | The @code{NOCROSSREFS} command takes a list of output section names. If |
1676 | @code{ld} detects any cross references between the sections, it reports | |
1677 | an error and returns a non-zero exit status. Note that the | |
1678 | @code{NOCROSSREFS} command uses output section names, not input section | |
1679 | names. | |
f22eee08 | 1680 | |
af54556a ILT |
1681 | @ifclear SingleFormat |
1682 | @item OUTPUT_ARCH(@var{bfdarch}) | |
1683 | @kindex OUTPUT_ARCH(@var{bfdarch}) | |
1684 | @cindex machine architecture | |
1685 | @cindex architecture | |
1686 | Specify a particular output machine architecture. The argument is one | |
1687 | of the names used by the BFD library (@pxref{BFD}). You can see the | |
1688 | architecture of an object file by using the @code{objdump} program with | |
1689 | the @samp{-f} option. | |
1690 | @end ifclear | |
1691 | @end table | |
b4d4e8e3 | 1692 | |
af54556a ILT |
1693 | @node Assignments |
1694 | @section Assigning Values to Symbols | |
2c5c0674 RP |
1695 | @cindex assignment in scripts |
1696 | @cindex symbol definition, scripts | |
1697 | @cindex variables, defining | |
af54556a ILT |
1698 | You may assign a value to a symbol in a linker script. This will define |
1699 | the symbol as a global symbol. | |
1700 | ||
1701 | @menu | |
1702 | * Simple Assignments:: Simple Assignments | |
1703 | * PROVIDE:: PROVIDE | |
1704 | @end menu | |
1705 | ||
1706 | @node Simple Assignments | |
1707 | @subsection Simple Assignments | |
1708 | ||
1709 | You may assign to a symbol using any of the C assignment operators: | |
b4d4e8e3 RP |
1710 | |
1711 | @table @code | |
af54556a | 1712 | @item @var{symbol} = @var{expression} ; |
b4d4e8e3 RP |
1713 | @itemx @var{symbol} += @var{expression} ; |
1714 | @itemx @var{symbol} -= @var{expression} ; | |
1715 | @itemx @var{symbol} *= @var{expression} ; | |
1716 | @itemx @var{symbol} /= @var{expression} ; | |
af54556a ILT |
1717 | @itemx @var{symbol} <<= @var{expression} ; |
1718 | @itemx @var{symbol} >>= @var{expression} ; | |
1719 | @itemx @var{symbol} &= @var{expression} ; | |
1720 | @itemx @var{symbol} |= @var{expression} ; | |
b4d4e8e3 RP |
1721 | @end table |
1722 | ||
af54556a ILT |
1723 | The first case will define @var{symbol} to the value of |
1724 | @var{expression}. In the other cases, @var{symbol} must already be | |
1725 | defined, and the value will be adjusted accordingly. | |
2c5c0674 | 1726 | |
af54556a ILT |
1727 | The special symbol name @samp{.} indicates the location counter. You |
1728 | may only use this within a @code{SECTIONS} command. | |
b4d4e8e3 | 1729 | |
af54556a | 1730 | The semicolon after @var{expression} is required. |
b4d4e8e3 | 1731 | |
af54556a | 1732 | Expressions are defined below; see @ref{Expressions}. |
b4d4e8e3 | 1733 | |
af54556a ILT |
1734 | You may write symbol assignments as commands in their own right, or as |
1735 | statements within a @code{SECTIONS} command, or as part of an output | |
1736 | section description in a @code{SECTIONS} command. | |
1737 | ||
1738 | The section of the symbol will be set from the section of the | |
1739 | expression; for more information, see @ref{Expression Section}. | |
1740 | ||
1741 | Here is an example showing the three different places that symbol | |
1742 | assignments may be used: | |
b4d4e8e3 | 1743 | |
c653b370 | 1744 | @smallexample |
af54556a ILT |
1745 | floating_point = 0; |
1746 | SECTIONS | |
1747 | @{ | |
1748 | .text : | |
1749 | @{ | |
1750 | *(.text) | |
1751 | _etext = .; | |
d4e5e3c3 | 1752 | @} |
af54556a ILT |
1753 | _bdata = (. + 3) & ~ 4; |
1754 | .data : @{ *(.data) @} | |
1755 | @} | |
c653b370 | 1756 | @end smallexample |
2c5c0674 | 1757 | @noindent |
af54556a ILT |
1758 | In this example, the symbol @samp{floating_point} will be defined as |
1759 | zero. The symbol @samp{_etext} will be defined as the address following | |
1760 | the last @samp{.text} input section. The symbol @samp{_bdata} will be | |
1761 | defined as the address following the @samp{.text} output section aligned | |
1762 | upward to a 4 byte boundary. | |
1763 | ||
1764 | @node PROVIDE | |
1765 | @subsection PROVIDE | |
1766 | @cindex PROVIDE | |
0b3499f6 | 1767 | In some cases, it is desirable for a linker script to define a symbol |
af54556a ILT |
1768 | only if it is referenced and is not defined by any object included in |
1769 | the link. For example, traditional linkers defined the symbol | |
1770 | @samp{etext}. However, ANSI C requires that the user be able to use | |
1771 | @samp{etext} as a function name without encountering an error. The | |
1772 | @code{PROVIDE} keyword may be used to define a symbol, such as | |
0b3499f6 ILT |
1773 | @samp{etext}, only if it is referenced but not defined. The syntax is |
1774 | @code{PROVIDE(@var{symbol} = @var{expression})}. | |
b4d4e8e3 | 1775 | |
af54556a | 1776 | Here is an example of using @code{PROVIDE} to define @samp{etext}: |
c653b370 | 1777 | @smallexample |
af54556a ILT |
1778 | SECTIONS |
1779 | @{ | |
1780 | .text : | |
d4e5e3c3 | 1781 | @{ |
af54556a ILT |
1782 | *(.text) |
1783 | _etext = .; | |
1784 | PROVIDE(etext = .); | |
d4e5e3c3 | 1785 | @} |
af54556a | 1786 | @} |
c653b370 | 1787 | @end smallexample |
d4e5e3c3 | 1788 | |
36a8f215 ILT |
1789 | In this example, if the program defines @samp{_etext} (with a leading |
1790 | underscore), the linker will give a multiple definition error. If, on | |
1791 | the other hand, the program defines @samp{etext} (with no leading | |
1792 | underscore), the linker will silently use the definition in the program. | |
1793 | If the program references @samp{etext} but does not define it, the | |
1794 | linker will use the definition in the linker script. | |
f22eee08 | 1795 | |
af54556a ILT |
1796 | @node SECTIONS |
1797 | @section SECTIONS command | |
1798 | @kindex SECTIONS | |
1799 | The @code{SECTIONS} command tells the linker how to map input sections | |
1800 | into output sections, and how to place the output sections in memory. | |
2c5c0674 | 1801 | |
af54556a | 1802 | The format of the @code{SECTIONS} command is: |
c653b370 | 1803 | @smallexample |
af54556a ILT |
1804 | SECTIONS |
1805 | @{ | |
1806 | @var{sections-command} | |
1807 | @var{sections-command} | |
1808 | @dots{} | |
1809 | @} | |
c653b370 | 1810 | @end smallexample |
f22eee08 | 1811 | |
af54556a | 1812 | Each @var{sections-command} may of be one of the following: |
b61364cc | 1813 | |
af54556a ILT |
1814 | @itemize @bullet |
1815 | @item | |
1816 | an @code{ENTRY} command (@pxref{Entry Point,,Entry command}) | |
1817 | @item | |
1818 | a symbol assignment (@pxref{Assignments}) | |
1819 | @item | |
1820 | an output section description | |
1821 | @item | |
1822 | an overlay description | |
1823 | @end itemize | |
2c5c0674 | 1824 | |
af54556a ILT |
1825 | The @code{ENTRY} command and symbol assignments are permitted inside the |
1826 | @code{SECTIONS} command for convenience in using the location counter in | |
1827 | those commands. This can also make the linker script easier to | |
1828 | understand because you can use those commands at meaningful points in | |
1829 | the layout of the output file. | |
67afbcea | 1830 | |
af54556a ILT |
1831 | Output section descriptions and overlay descriptions are described |
1832 | below. | |
67afbcea | 1833 | |
af54556a ILT |
1834 | If you do not use a @code{SECTIONS} command in your linker script, the |
1835 | linker will place each input section into an identically named output | |
1836 | section in the order that the sections are first encountered in the | |
1837 | input files. If all input sections are present in the first file, for | |
1838 | example, the order of sections in the output file will match the order | |
1839 | in the first input file. The first section will be at address zero. | |
67afbcea | 1840 | |
af54556a ILT |
1841 | @menu |
1842 | * Output Section Description:: Output section description | |
1843 | * Output Section Name:: Output section name | |
1844 | * Output Section Address:: Output section address | |
1845 | * Input Section:: Input section description | |
1846 | * Output Section Data:: Output section data | |
1847 | * Output Section Keywords:: Output section keywords | |
1848 | * Output Section Discarding:: Output section discarding | |
1849 | * Output Section Attributes:: Output section attributes | |
1850 | * Overlay Description:: Overlay description | |
1851 | @end menu | |
67afbcea | 1852 | |
af54556a ILT |
1853 | @node Output Section Description |
1854 | @subsection Output section description | |
1855 | The full description of an output section looks like this: | |
c653b370 | 1856 | @smallexample |
af54556a ILT |
1857 | @group |
1858 | @var{section} [@var{address}] [(@var{type})] : [AT(@var{lma})] | |
d4e5e3c3 | 1859 | @{ |
af54556a ILT |
1860 | @var{output-section-command} |
1861 | @var{output-section-command} | |
d4e5e3c3 | 1862 | @dots{} |
af54556a | 1863 | @} [>@var{region}] [:@var{phdr} :@var{phdr} @dots{}] [=@var{fillexp}] |
c653b370 ILT |
1864 | @end group |
1865 | @end smallexample | |
5a59e34d | 1866 | |
af54556a | 1867 | Most output sections do not use most of the optional section attributes. |
5a59e34d | 1868 | |
af54556a ILT |
1869 | The whitespace around @var{section} is required, so that the section |
1870 | name is unambiguous. The colon and the curly braces are also required. | |
1871 | The line breaks and other white space are optional. | |
d4e5e3c3 | 1872 | |
af54556a | 1873 | Each @var{output-section-command} may be one of the following: |
d4e5e3c3 | 1874 | |
af54556a ILT |
1875 | @itemize @bullet |
1876 | @item | |
1877 | a symbol assignment (@pxref{Assignments}) | |
1878 | @item | |
1879 | an input section description (@pxref{Input Section}) | |
1880 | @item | |
1881 | data values to include directly (@pxref{Output Section Data}) | |
1882 | @item | |
1883 | a special output section keyword (@pxref{Output Section Keywords}) | |
1884 | @end itemize | |
f22eee08 | 1885 | |
af54556a ILT |
1886 | @node Output Section Name |
1887 | @subsection Output section name | |
1888 | @cindex name, section | |
1889 | @cindex section name | |
1890 | The name of the output section is @var{section}. @var{section} must | |
1891 | meet the constraints of your output format. In formats which only | |
1892 | support a limited number of sections, such as @code{a.out}, the name | |
1893 | must be one of the names supported by the format (@code{a.out}, for | |
1894 | example, allows only @samp{.text}, @samp{.data} or @samp{.bss}). If the | |
1895 | output format supports any number of sections, but with numbers and not | |
1896 | names (as is the case for Oasys), the name should be supplied as a | |
1897 | quoted numeric string. A section name may consist of any sequence of | |
1898 | characters, but a name which contains any unusual characters such as | |
1899 | commas must be quoted. | |
1900 | ||
1901 | The output section name @samp{/DISCARD/} is special; @ref{Output Section | |
1902 | Discarding}. | |
1903 | ||
1904 | @node Output Section Address | |
1905 | @subsection Output section address | |
1906 | @cindex address, section | |
1907 | @cindex section address | |
1908 | The @var{address} is an expression for the VMA (the virtual memory | |
1909 | address) of the output section. If you do not provide @var{address}, | |
1910 | the linker will set it based on @var{region} if present, or otherwise | |
1911 | based on the current value of the location counter. | |
1912 | ||
1913 | If you provide @var{address}, the address of the output section will be | |
1914 | set to precisely that. If you provide neither @var{address} nor | |
1915 | @var{region}, then the address of the output section will be set to the | |
1916 | current value of the location counter aligned to the alignment | |
1917 | requirements of the output section. The alignment requirement of the | |
1918 | output section is the strictest alignment of any input section contained | |
1919 | within the output section. | |
1920 | ||
1921 | For example, | |
c653b370 | 1922 | @smallexample |
af54556a | 1923 | .text . : @{ *(.text) @} |
c653b370 | 1924 | @end smallexample |
af54556a ILT |
1925 | @noindent |
1926 | and | |
1927 | @smallexample | |
1928 | .text : @{ *(.text) @} | |
1929 | @end smallexample | |
1930 | @noindent | |
1931 | are subtly different. The first will set the address of the | |
1932 | @samp{.text} output section to the current value of the location | |
1933 | counter. The second will set it to the current value of the location | |
1934 | counter aligned to the strictest alignment of a @samp{.text} input | |
1935 | section. | |
1936 | ||
1937 | The @var{address} may be an arbitrary expression; @ref{Expressions}. | |
1938 | For example, if you want to align the section on a 0x10 byte boundary, | |
1939 | so that the lowest four bits of the section address are zero, you could | |
1940 | do something like this: | |
1941 | @smallexample | |
1942 | .text ALIGN(0x10) : @{ *(.text) @} | |
1943 | @end smallexample | |
1944 | @noindent | |
1945 | This works because @code{ALIGN} returns the current location counter | |
1946 | aligned upward to the specified value. | |
f22eee08 | 1947 | |
af54556a ILT |
1948 | Specifying @var{address} for a section will change the value of the |
1949 | location counter. | |
67c4333b | 1950 | |
af54556a ILT |
1951 | @node Input Section |
1952 | @subsection Input section description | |
1953 | @cindex input sections | |
1954 | @cindex mapping input sections to output sections | |
1955 | The most common output section command is an input section description. | |
67c4333b | 1956 | |
af54556a ILT |
1957 | The input section description is the most basic linker script operation. |
1958 | You use output sections to tell the linker how to lay out your program | |
1959 | in memory. You use input section descriptions to tell the linker how to | |
1960 | map the input files into your memory layout. | |
67c4333b | 1961 | |
af54556a ILT |
1962 | @menu |
1963 | * Input Section Basics:: Input section basics | |
1964 | * Input Section Wildcards:: Input section wildcard patterns | |
1965 | * Input Section Common:: Input section for common symbols | |
1966 | * Input Section Example:: Input section example | |
1967 | @end menu | |
b4d4e8e3 | 1968 | |
af54556a ILT |
1969 | @node Input Section Basics |
1970 | @subsubsection Input section basics | |
1971 | @cindex input section basics | |
1972 | An input section description consists of a file name optionally followed | |
1973 | by a list of section names in parentheses. | |
f22eee08 | 1974 | |
af54556a ILT |
1975 | The file name and the section name may be wildcard patterns, which we |
1976 | describe further below (@pxref{Input Section Wildcards}). | |
b4d4e8e3 | 1977 | |
af54556a ILT |
1978 | The most common input section description is to include all input |
1979 | sections with a particular name in the output section. For example, to | |
1980 | include all input @samp{.text} sections, you would write: | |
1981 | @smallexample | |
1982 | *(.text) | |
1983 | @end smallexample | |
1984 | @noindent | |
1985 | Here the @samp{*} is a wildcard which matches any file name. | |
2c5c0674 | 1986 | |
af54556a | 1987 | There are two ways to include more than one section: |
c653b370 | 1988 | @smallexample |
af54556a ILT |
1989 | *(.text .rdata) |
1990 | *(.text) *(.rdata) | |
c653b370 | 1991 | @end smallexample |
b4d4e8e3 | 1992 | @noindent |
af54556a ILT |
1993 | The difference between these is the order in which the @samp{.text} and |
1994 | @samp{.rdata} input sections will appear in the output section. In the | |
1995 | first example, they will be intermingled. In the second example, all | |
1996 | @samp{.text} input sections will appear first, followed by all | |
1997 | @samp{.rdata} input sections. | |
1998 | ||
1999 | You can specify a file name to include sections from a particular file. | |
2000 | You would do this if one or more of your files contain special data that | |
2001 | needs to be at a particular location in memory. For example: | |
c653b370 | 2002 | @smallexample |
af54556a | 2003 | data.o(.data) |
c653b370 | 2004 | @end smallexample |
f9d3d71a | 2005 | |
af54556a ILT |
2006 | If you use a file name without a list of sections, then all sections in |
2007 | the input file will be included in the output section. This is not | |
2008 | commonly done, but it may by useful on occasion. For example: | |
2009 | @smallexample | |
2010 | data.o | |
2011 | @end smallexample | |
67c4333b | 2012 | |
af54556a ILT |
2013 | When you use a file name which does not contain any wild card |
2014 | characters, the linker will first see if you also specified the file | |
2015 | name on the linker command line or in an @code{INPUT} command. If you | |
2016 | did not, the linker will attempt to open the file as an input file, as | |
2017 | though it appeared on the command line. Note that this differs from an | |
2018 | @code{INPUT} command, because the linker will not search for the file in | |
2019 | the archive search path. | |
b4d4e8e3 | 2020 | |
af54556a ILT |
2021 | @node Input Section Wildcards |
2022 | @subsubsection Input section wildcard patterns | |
2023 | @cindex input section wildcards | |
2024 | @cindex wildcard file name patterns | |
2025 | @cindex file name wildcard patterns | |
2026 | @cindex section name wildcard patterns | |
2027 | In an input section description, either the file name or the section | |
2028 | name or both may be wildcard patterns. | |
f22eee08 | 2029 | |
af54556a ILT |
2030 | The file name of @samp{*} seen in many examples is a simple wildcard |
2031 | pattern for the file name. | |
f22eee08 | 2032 | |
af54556a | 2033 | The wildcard patterns are like those used by the Unix shell. |
b4d4e8e3 | 2034 | |
af54556a ILT |
2035 | @table @samp |
2036 | @item * | |
2037 | matches any number of characters | |
2038 | @item ? | |
2039 | matches any single character | |
2040 | @item [@var{chars}] | |
2041 | matches a single instance of any of the @var{chars}; the @samp{-} | |
2042 | character may be used to specify a range of characters, as in | |
2043 | @samp{[a-z]} to match any lower case letter | |
2044 | @item \ | |
2045 | quotes the following character | |
2046 | @end table | |
86bc0974 | 2047 | |
c2ba3684 ILT |
2048 | When a file name is matched with a wildcard, the wildcard characters |
2049 | will not match a @samp{/} character (used to separate directory names on | |
86bc0974 | 2050 | Unix). A pattern consisting of a single @samp{*} character is an |
af54556a ILT |
2051 | exception; it will always match any file name, whether it contains a |
2052 | @samp{/} or not. In a section name, the wildcard characters will match | |
2053 | a @samp{/} character. | |
2054 | ||
2055 | File name wildcard patterns only match files which are explicitly | |
2056 | specified on the command line or in an @code{INPUT} command. The linker | |
2057 | does not search directories to expand wildcards. | |
2058 | ||
2059 | If a file name matches more than one wildcard pattern, or if a file name | |
2060 | appears explicitly and is also matched by a wildcard pattern, the linker | |
2061 | will use the first match in the linker script. For example, this | |
2062 | sequence of input section descriptions is probably in error, because the | |
2063 | @file{data.o} rule will not be used: | |
2064 | @smallexample | |
2065 | .data : @{ *(.data) @} | |
2066 | .data1 : @{ data.o(.data) @} | |
2067 | @end smallexample | |
86bc0974 | 2068 | |
da713b8f ILT |
2069 | @cindex SORT |
2070 | Normally, the linker will place files and sections matched by wildcards | |
2071 | in the order in which they are seen during the link. You can change | |
2072 | this by using the @code{SORT} keyword, which appears before a wildcard | |
2073 | pattern in parentheses (e.g., @code{SORT(.text*)}). When the | |
2074 | @code{SORT} keyword is used, the linker will sort the files or sections | |
2075 | into ascending order by name before placing them in the output file. | |
2076 | ||
af54556a ILT |
2077 | If you ever get confused about where input sections are going, use the |
2078 | @samp{-M} linker option to generate a map file. The map file shows | |
2079 | precisely how input sections are mapped to output sections. | |
d4e5e3c3 | 2080 | |
af54556a ILT |
2081 | This example shows how wildcard patterns might be used to partition |
2082 | files. This linker script directs the linker to place all @samp{.text} | |
2083 | sections in @samp{.text} and all @samp{.bss} sections in @samp{.bss}. | |
2084 | The linker will place the @samp{.data} section from all files beginning | |
2085 | with an upper case character in @samp{.DATA}; for all other files, the | |
2086 | linker will place the @samp{.data} section in @samp{.data}. | |
c653b370 ILT |
2087 | @smallexample |
2088 | @group | |
af54556a | 2089 | SECTIONS @{ |
d76ae847 | 2090 | .text : @{ *(.text) @} |
af54556a ILT |
2091 | .DATA : @{ [A-Z]*(.data) @} |
2092 | .data : @{ *(.data) @} | |
2093 | .bss : @{ *(.bss) @} | |
2094 | @} | |
c653b370 ILT |
2095 | @end group |
2096 | @end smallexample | |
b4d4e8e3 | 2097 | |
af54556a ILT |
2098 | @node Input Section Common |
2099 | @subsubsection Input section for common symbols | |
2100 | @cindex common symbol placement | |
2101 | @cindex uninitialized data placement | |
2102 | A special notation is needed for common symbols, because in many object | |
2103 | file formats common symbols do not have a particular input section. The | |
2104 | linker treats common symbols as though they are in an input section | |
2105 | named @samp{COMMON}. | |
2106 | ||
2107 | You may use file names with the @samp{COMMON} section just as with any | |
2108 | other input sections. You can use this to place common symbols from a | |
2109 | particular input file in one section while common symbols from other | |
2110 | input files are placed in another section. | |
2111 | ||
2112 | In most cases, common symbols in input files will be placed in the | |
2113 | @samp{.bss} section in the output file. For example: | |
2114 | @smallexample | |
2115 | .bss @{ *(.bss) *(COMMON) @} | |
2116 | @end smallexample | |
2117 | ||
2118 | @cindex scommon section | |
2119 | @cindex small common symbols | |
2120 | Some object file formats have more than one type of common symbol. For | |
2121 | example, the MIPS ELF object file format distinguishes standard common | |
2122 | symbols and small common symbols. In this case, the linker will use a | |
2123 | different special section name for other types of common symbols. In | |
2124 | the case of MIPS ELF, the linker uses @samp{COMMON} for standard common | |
2125 | symbols and @samp{.scommon} for small common symbols. This permits you | |
2126 | to map the different types of common symbols into memory at different | |
2127 | locations. | |
2128 | ||
2129 | @cindex [COMMON] | |
2130 | You will sometimes see @samp{[COMMON]} in old linker scripts. This | |
2131 | notation is now considered obsolete. It is equivalent to | |
2132 | @samp{*(COMMON)}. | |
2133 | ||
2134 | @node Input Section Example | |
2135 | @subsubsection Input section example | |
2136 | The following example is a complete linker script. It tells the linker | |
2137 | to read all of the sections from file @file{all.o} and place them at the | |
2138 | start of output section @samp{outputa} which starts at location | |
2139 | @samp{0x10000}. All of section @samp{.input1} from file @file{foo.o} | |
2140 | follows immediately, in the same output section. All of section | |
2141 | @samp{.input2} from @file{foo.o} goes into output section | |
2142 | @samp{outputb}, followed by section @samp{.input1} from @file{foo1.o}. | |
2143 | All of the remaining @samp{.input1} and @samp{.input2} sections from any | |
2144 | files are written to output section @samp{outputc}. | |
b4d4e8e3 | 2145 | |
c653b370 ILT |
2146 | @smallexample |
2147 | @group | |
2c5c0674 | 2148 | SECTIONS @{ |
d4e5e3c3 DM |
2149 | outputa 0x10000 : |
2150 | @{ | |
2151 | all.o | |
2152 | foo.o (.input1) | |
2153 | @} | |
2154 | outputb : | |
2155 | @{ | |
2156 | foo.o (.input2) | |
2157 | foo1.o (.input1) | |
2158 | @} | |
2159 | outputc : | |
2160 | @{ | |
2161 | *(.input1) | |
2162 | *(.input2) | |
2163 | @} | |
2c5c0674 | 2164 | @} |
c653b370 ILT |
2165 | @end group |
2166 | @end smallexample | |
b4d4e8e3 | 2167 | |
af54556a ILT |
2168 | @node Output Section Data |
2169 | @subsection Output section data | |
2170 | @cindex data | |
2171 | @cindex section data | |
2172 | @cindex output section data | |
2173 | @kindex BYTE(@var{expression}) | |
2174 | @kindex SHORT(@var{expression}) | |
2175 | @kindex LONG(@var{expression}) | |
2176 | @kindex QUAD(@var{expression}) | |
2177 | @kindex SQUAD(@var{expression}) | |
2178 | You can include explicit bytes of data in an output section by using | |
2179 | @code{BYTE}, @code{SHORT}, @code{LONG}, @code{QUAD}, or @code{SQUAD} as | |
2180 | an output section command. Each keyword is followed by an expression in | |
2181 | parentheses providing the value to store (@pxref{Expressions}). The | |
2182 | value of the expression is stored at the current value of the location | |
2183 | counter. | |
2184 | ||
2185 | The @code{BYTE}, @code{SHORT}, @code{LONG}, and @code{QUAD} commands | |
2186 | store one, two, four, and eight bytes (respectively). After storing the | |
2187 | bytes, the location counter is incremented by the number of bytes | |
2188 | stored. | |
2189 | ||
2190 | For example, this will store the byte 1 followed by the four byte value | |
2191 | of the symbol @samp{addr}: | |
2192 | @smallexample | |
2193 | BYTE(1) | |
2194 | LONG(addr) | |
2195 | @end smallexample | |
2196 | ||
2197 | When using a 64 bit host or target, @code{QUAD} and @code{SQUAD} are the | |
2198 | same; they both store an 8 byte, or 64 bit, value. When both host and | |
2199 | target are 32 bits, an expression is computed as 32 bits. In this case | |
2200 | @code{QUAD} stores a 32 bit value zero extended to 64 bits, and | |
2201 | @code{SQUAD} stores a 32 bit value sign extended to 64 bits. | |
86bc0974 | 2202 | |
af54556a ILT |
2203 | If the object file format of the output file has an explicit endianness, |
2204 | which is the normal case, the value will be stored in that endianness. | |
2205 | When the object file format does not have an explicit endianness, as is | |
2206 | true of, for example, S-records, the value will be stored in the | |
2207 | endianness of the first input object file. | |
2208 | ||
2209 | @kindex FILL(@var{expression}) | |
2210 | @cindex holes, filling | |
2211 | @cindex unspecified memory | |
2212 | You may use the @code{FILL} command to set the fill pattern for the | |
2213 | current section. It is followed by an expression in parentheses. Any | |
2214 | otherwise unspecified regions of memory within the section (for example, | |
2215 | gaps left due to the required alignment of input sections) are filled | |
2216 | with the two least significant bytes of the expression, repeated as | |
2217 | necessary. A @code{FILL} statement covers memory locations after the | |
2218 | point at which it occurs in the section definition; by including more | |
2219 | than one @code{FILL} statement, you can have different fill patterns in | |
2220 | different parts of an output section. | |
2221 | ||
2222 | This example shows how to fill unspecified regions of memory with the | |
2223 | value @samp{0x9090}: | |
86bc0974 | 2224 | @smallexample |
af54556a | 2225 | FILL(0x9090) |
86bc0974 ILT |
2226 | @end smallexample |
2227 | ||
af54556a ILT |
2228 | The @code{FILL} command is similar to the @samp{=@var{fillexp}} output |
2229 | section attribute (@pxref{Output Section Fill}), but it only affects the | |
2230 | part of the section following the @code{FILL} command, rather than the | |
2231 | entire section. If both are used, the @code{FILL} command takes | |
2232 | precedence. | |
67c4333b | 2233 | |
af54556a ILT |
2234 | @node Output Section Keywords |
2235 | @subsection Output section keywords | |
2236 | There are a couple of keywords which can appear as output section | |
2237 | commands. | |
f22eee08 | 2238 | |
b4d4e8e3 | 2239 | @table @code |
af54556a | 2240 | @kindex CREATE_OBJECT_SYMBOLS |
2c5c0674 RP |
2241 | @cindex input filename symbols |
2242 | @cindex filename symbols | |
d4e5e3c3 | 2243 | @item CREATE_OBJECT_SYMBOLS |
af54556a ILT |
2244 | The command tells the linker to create a symbol for each input file. |
2245 | The name of each symbol will be the name of the corresponding input | |
2246 | file. The section of each symbol will be the output section in which | |
2247 | the @code{CREATE_OBJECT_SYMBOLS} command appears. | |
b4d4e8e3 | 2248 | |
af54556a ILT |
2249 | This is conventional for the a.out object file format. It is not |
2250 | normally used for any other object file format. | |
f22eee08 | 2251 | |
af54556a ILT |
2252 | @kindex CONSTRUCTORS |
2253 | @cindex C++ constructors, arranging in link | |
2254 | @cindex constructors, arranging in link | |
2255 | @item CONSTRUCTORS | |
2256 | When linking using the a.out object file format, the linker uses an | |
2257 | unusual set construct to support C++ global constructors and | |
2258 | destructors. When linking object file formats which do not support | |
2259 | arbitrary sections, such as ECOFF and XCOFF, the linker will | |
2260 | automatically recognize C++ global constructors and destructors by name. | |
2261 | For these object file formats, the @code{CONSTRUCTORS} command tells the | |
2262 | linker to place constructor information in the output section where the | |
2263 | @code{CONSTRUCTORS} command appears. The @code{CONSTRUCTORS} command is | |
2264 | ignored for other object file formats. | |
f22eee08 | 2265 | |
af54556a ILT |
2266 | The symbol @w{@code{__CTOR_LIST__}} marks the start of the global |
2267 | constructors, and the symbol @w{@code{__DTOR_LIST}} marks the end. The | |
2268 | first word in the list is the number of entries, followed by the address | |
2269 | of each constructor or destructor, followed by a zero word. The | |
2270 | compiler must arrange to actually run the code. For these object file | |
2271 | formats @sc{gnu} C++ normally calls constructors from a subroutine | |
2272 | @code{__main}; a call to @code{__main} is automatically inserted into | |
2273 | the startup code for @code{main}. @sc{gnu} C++ normally runs | |
2274 | destructors either by using @code{atexit}, or directly from the function | |
2275 | @code{exit}. | |
2c5c0674 | 2276 | |
af54556a ILT |
2277 | For object file formats such as @code{COFF} or @code{ELF} which support |
2278 | arbitrary section names, @sc{gnu} C++ will normally arrange to put the | |
2279 | addresses of global constructors and destructors into the @code{.ctors} | |
2280 | and @code{.dtors} sections. Placing the following sequence into your | |
2281 | linker script will build the sort of table which the @sc{gnu} C++ | |
2282 | runtime code expects to see. | |
d4e5e3c3 | 2283 | |
c653b370 | 2284 | @smallexample |
af54556a ILT |
2285 | __CTOR_LIST__ = .; |
2286 | LONG((__CTOR_END__ - __CTOR_LIST__) / 4 - 2) | |
2287 | *(.ctors) | |
2288 | LONG(0) | |
2289 | __CTOR_END__ = .; | |
2290 | __DTOR_LIST__ = .; | |
2291 | LONG((__DTOR_END__ - __DTOR_LIST__) / 4 - 2) | |
2292 | *(.dtors) | |
2293 | LONG(0) | |
2294 | __DTOR_END__ = .; | |
c653b370 | 2295 | @end smallexample |
d4e5e3c3 | 2296 | |
af54556a ILT |
2297 | Normally the compiler and linker will handle these issues automatically, |
2298 | and you will not need to concern yourself with them. However, you may | |
2299 | need to consider this if you are using C++ and writing your own linker | |
2300 | scripts. | |
b4d4e8e3 RP |
2301 | @end table |
2302 | ||
af54556a ILT |
2303 | @node Output Section Discarding |
2304 | @subsection Output section discarding | |
2305 | @cindex discarding sections | |
2306 | @cindex sections, discarding | |
2307 | @cindex removing sections | |
2308 | The linker will not create output section which do not have any | |
2309 | contents. This is for convenience when referring to input sections that | |
2310 | may or may not be present in any of the input files. For example: | |
d76ae847 | 2311 | @smallexample |
af54556a | 2312 | .foo @{ *(.foo) @} |
d76ae847 | 2313 | @end smallexample |
af54556a ILT |
2314 | @noindent |
2315 | will only create a @samp{.foo} section in the output file if there is a | |
2316 | @samp{.foo} section in at least one input file. | |
b4d4e8e3 | 2317 | |
af54556a ILT |
2318 | If you use anything other than an input section description as an output |
2319 | section command, such as a symbol assignment, then the output section | |
2320 | will always be created, even if there are no matching input sections. | |
f22eee08 | 2321 | |
af54556a ILT |
2322 | The special output section name @samp{/DISCARD/} may be used to discard |
2323 | input sections. Any input sections which are assigned to an output | |
2324 | section named @samp{/DISCARD/} are not included in the output file. | |
d4e5e3c3 | 2325 | |
af54556a ILT |
2326 | @node Output Section Attributes |
2327 | @subsection Output section attributes | |
2328 | @cindex output section attributes | |
2329 | We showed above that the full description of an output section looked | |
2330 | like this: | |
c653b370 | 2331 | @smallexample |
af54556a ILT |
2332 | @group |
2333 | @var{section} [@var{address}] [(@var{type})] : [AT(@var{lma})] | |
2334 | @{ | |
2335 | @var{output-section-command} | |
2336 | @var{output-section-command} | |
d4e5e3c3 | 2337 | @dots{} |
af54556a | 2338 | @} [>@var{region}] [:@var{phdr} :@var{phdr} @dots{}] [=@var{fillexp}] |
c653b370 ILT |
2339 | @end group |
2340 | @end smallexample | |
af54556a ILT |
2341 | We've already described @var{section}, @var{address}, and |
2342 | @var{output-section-command}. In this section we will describe the | |
2343 | remaining section attributes. | |
2344 | ||
2345 | @menu | |
2346 | * Output Section Type:: Output section type | |
2347 | * Output Section LMA:: Output section LMA | |
2348 | * Output Section Region:: Output section region | |
2349 | * Output Section Phdr:: Output section phdr | |
2350 | * Output Section Fill:: Output section fill | |
2351 | @end menu | |
f22eee08 | 2352 | |
af54556a ILT |
2353 | @node Output Section Type |
2354 | @subsubsection Output section type | |
2355 | Each output section may have a type. The type is a keyword in | |
2356 | parentheses. The following types are defined: | |
2357 | ||
2358 | @table @code | |
2359 | @item NOLOAD | |
2360 | The section should be marked as not loadable, so that it will not be | |
2361 | loaded into memory when the program is run. | |
2362 | @item DSECT | |
2363 | @itemx COPY | |
2364 | @itemx INFO | |
2365 | @itemx OVERLAY | |
2366 | These type names are supported for backward compatibility, and are | |
2367 | rarely used. They all have the same effect: the section should be | |
2368 | marked as not allocatable, so that no memory is allocated for the | |
2369 | section when the program is run. | |
2370 | @end table | |
f22eee08 | 2371 | |
d76ae847 RP |
2372 | @kindex NOLOAD |
2373 | @cindex prevent unnecessary loading | |
67c4333b | 2374 | @cindex loading, preventing |
af54556a ILT |
2375 | The linker normally sets the attributes of an output section based on |
2376 | the input sections which map into it. You can override this by using | |
2377 | the section type. For example, in the script sample below, the | |
2378 | @samp{ROM} section is addressed at memory location @samp{0} and does not | |
2379 | need to be loaded when the program is run. The contents of the | |
2380 | @samp{ROM} section will appear in the linker output file as usual. | |
c653b370 ILT |
2381 | @smallexample |
2382 | @group | |
d76ae847 | 2383 | SECTIONS @{ |
af54556a | 2384 | ROM 0 (NOLOAD) : @{ @dots{} @} |
d4e5e3c3 | 2385 | @dots{} |
d76ae847 | 2386 | @} |
c653b370 ILT |
2387 | @end group |
2388 | @end smallexample | |
d76ae847 | 2389 | |
af54556a ILT |
2390 | @node Output Section LMA |
2391 | @subsubsection Output section LMA | |
2392 | @kindex AT(@var{lma}) | |
2393 | @cindex load address | |
2394 | @cindex section load address | |
2395 | Every section has a virtual address (VMA) and a load address (LMA); see | |
2396 | @ref{Basic Script Concepts}. The address expression which may appear in | |
2397 | an output section description sets the VMA (@pxref{Output Section | |
2398 | Address}). | |
2399 | ||
2400 | The linker will normally set the LMA equal to the VMA. You can change | |
2401 | that by using the @code{AT} keyword. The expression @var{lma} that | |
2402 | follows the @code{AT} keyword specifies the load address of the section. | |
2403 | ||
2404 | @cindex ROM initialized data | |
2405 | @cindex initialized data in ROM | |
2406 | This feature is designed to make it easy to build a ROM image. For | |
2407 | example, the following linker script creates three output sections: one | |
2408 | called @samp{.text}, which starts at @code{0x1000}, one called | |
2409 | @samp{.mdata}, which is loaded at the end of the @samp{.text} section | |
2410 | even though its VMA is @code{0x2000}, and one called @samp{.bss} to hold | |
2411 | uninitialized data at address @code{0x3000}. The symbol @code{_data} is | |
2412 | defined with the value @code{0x2000}, which shows that the location | |
2413 | counter holds the VMA value, not the LMA value. | |
67c4333b RP |
2414 | |
2415 | @smallexample | |
c653b370 | 2416 | @group |
67c4333b | 2417 | SECTIONS |
139c8857 RP |
2418 | @{ |
2419 | .text 0x1000 : @{ *(.text) _etext = . ; @} | |
2420 | .mdata 0x2000 : | |
af54556a | 2421 | AT ( ADDR (.text) + SIZEOF (.text) ) |
139c8857 RP |
2422 | @{ _data = . ; *(.data); _edata = . ; @} |
2423 | .bss 0x3000 : | |
2424 | @{ _bstart = . ; *(.bss) *(COMMON) ; _bend = . ;@} | |
67c4333b | 2425 | @} |
c653b370 | 2426 | @end group |
67c4333b RP |
2427 | @end smallexample |
2428 | ||
af54556a ILT |
2429 | The run-time initialization code for use with a program generated with |
2430 | this linker script would include something like the following, to copy | |
2431 | the initialized data from the ROM image to its runtime address. Notice | |
2432 | how this code takes advantage of the symbols defined by the linker | |
2433 | script. | |
67c4333b | 2434 | |
139c8857 | 2435 | @smallexample |
c653b370 | 2436 | @group |
af54556a ILT |
2437 | extern char _etext, _data, _edata, _bstart, _bend; |
2438 | char *src = &_etext; | |
2439 | char *dst = &_data; | |
67c4333b | 2440 | |
139c8857 | 2441 | /* ROM has data at end of text; copy it. */ |
af54556a | 2442 | while (dst < &_edata) @{ |
139c8857 | 2443 | *dst++ = *src++; |
67c4333b RP |
2444 | @} |
2445 | ||
2446 | /* Zero bss */ | |
af54556a | 2447 | for (dst = &_bstart; dst< &_bend; dst++) |
139c8857 | 2448 | *dst = 0; |
c653b370 | 2449 | @end group |
139c8857 | 2450 | @end smallexample |
67c4333b | 2451 | |
af54556a ILT |
2452 | @node Output Section Region |
2453 | @subsubsection Output section region | |
f9d3d71a ILT |
2454 | @kindex >@var{region} |
2455 | @cindex section, assigning to memory region | |
2456 | @cindex memory regions and sections | |
af54556a ILT |
2457 | You can assign a section to a previously defined region of memory by |
2458 | using @samp{>@var{region}}. @xref{MEMORY}. | |
2459 | ||
2460 | Here is a simple example: | |
2461 | @smallexample | |
2462 | @group | |
2463 | MEMORY @{ rom : ORIGIN = 0x1000, LENGTH = 0x1000 @} | |
2464 | SECTIONS @{ ROM : @{ *(.text) @} >rom @} | |
2465 | @end group | |
2466 | @end smallexample | |
f9d3d71a | 2467 | |
af54556a ILT |
2468 | @node Output Section Phdr |
2469 | @subsubsection Output section phdr | |
c653b370 ILT |
2470 | @kindex :@var{phdr} |
2471 | @cindex section, assigning to program header | |
2472 | @cindex program headers and sections | |
af54556a ILT |
2473 | You can assign a section to a previously defined program segment by |
2474 | using @samp{:@var{phdr}}. @xref{PHDRS}. If a section is assigned to | |
2475 | one or more segments, then all subsequent allocated sections will be | |
2476 | assigned to those segments as well, unless they use an explicitly | |
36a8f215 ILT |
2477 | @code{:@var{phdr}} modifier. You can use @code{:NONE} to tell the |
2478 | linker to not put the section in any segment at all. | |
af54556a ILT |
2479 | |
2480 | Here is a simple example: | |
2481 | @smallexample | |
2482 | @group | |
2483 | PHDRS @{ text PT_LOAD ; @} | |
2484 | SECTIONS @{ .text : @{ *(.text) @} :text @} | |
2485 | @end group | |
2486 | @end smallexample | |
2487 | ||
2488 | @node Output Section Fill | |
2489 | @subsubsection Output section fill | |
2490 | @kindex =@var{fillexp} | |
2c5c0674 RP |
2491 | @cindex section fill pattern |
2492 | @cindex fill pattern, entire section | |
af54556a ILT |
2493 | You can set the fill pattern for an entire section by using |
2494 | @samp{=@var{fillexp}}. @var{fillexp} is an expression | |
2495 | (@pxref{Expressions}). Any otherwise unspecified regions of memory | |
2496 | within the output section (for example, gaps left due to the required | |
2497 | alignment of input sections) will be filled with the two least | |
2498 | significant bytes of the value, repeated as necessary. | |
f22eee08 | 2499 | |
af54556a ILT |
2500 | You can also change the fill value with a @code{FILL} command in the |
2501 | output section commands; see @ref{Output Section Data}. | |
b4d4e8e3 | 2502 | |
af54556a ILT |
2503 | Here is a simple example: |
2504 | @smallexample | |
2505 | @group | |
2506 | SECTIONS @{ .text : @{ *(.text) @} =0x9090 @} | |
2507 | @end group | |
2508 | @end smallexample | |
2509 | ||
2510 | @node Overlay Description | |
2511 | @subsection Overlay description | |
b61364cc ILT |
2512 | @kindex OVERLAY |
2513 | @cindex overlays | |
af54556a ILT |
2514 | An overlay description provides an easy way to describe sections which |
2515 | are to be loaded as part of a single memory image but are to be run at | |
2516 | the same memory address. At run time, some sort of overlay manager will | |
2517 | copy the overlaid sections in and out of the runtime memory address as | |
2518 | required, perhaps by simply manipulating addressing bits. This approach | |
2519 | can be useful, for example, when a certain region of memory is faster | |
2520 | than another. | |
2521 | ||
2522 | Overlays are described using the @code{OVERLAY} command. The | |
2523 | @code{OVERLAY} command is used within a @code{SECTIONS} command, like an | |
2524 | output section description. The full syntax of the @code{OVERLAY} | |
2525 | command is as follows: | |
b61364cc ILT |
2526 | @smallexample |
2527 | @group | |
af54556a ILT |
2528 | OVERLAY [@var{start}] : [NOCROSSREFS] [AT ( @var{ldaddr} )] |
2529 | @{ | |
2530 | @var{secname1} | |
2531 | @{ | |
2532 | @var{output-section-command} | |
2533 | @var{output-section-command} | |
2534 | @dots{} | |
2535 | @} [:@var{phdr}@dots{}] [=@var{fill}] | |
2536 | @var{secname2} | |
2537 | @{ | |
2538 | @var{output-section-command} | |
2539 | @var{output-section-command} | |
2540 | @dots{} | |
2541 | @} [:@var{phdr}@dots{}] [=@var{fill}] | |
2542 | @dots{} | |
2543 | @} [>@var{region}] [:@var{phdr}@dots{}] [=@var{fill}] | |
b61364cc ILT |
2544 | @end group |
2545 | @end smallexample | |
2546 | ||
2547 | Everything is optional except @code{OVERLAY} (a keyword), and each | |
2548 | section must have a name (@var{secname1} and @var{secname2} above). The | |
2549 | section definitions within the @code{OVERLAY} construct are identical to | |
2550 | those within the general @code{SECTIONS} contruct (@pxref{SECTIONS}), | |
2551 | except that no addresses and no memory regions may be defined for | |
2552 | sections within an @code{OVERLAY}. | |
2553 | ||
2554 | The sections are all defined with the same starting address. The load | |
2555 | addresses of the sections are arranged such that they are consecutive in | |
2556 | memory starting at the load address used for the @code{OVERLAY} as a | |
2557 | whole (as with normal section definitions, the load address is optional, | |
2558 | and defaults to the start address; the start address is also optional, | |
af54556a | 2559 | and defaults to the current value of the location counter). |
b61364cc ILT |
2560 | |
2561 | If the @code{NOCROSSREFS} keyword is used, and there any references | |
2562 | among the sections, the linker will report an error. Since the sections | |
2563 | all run at the same address, it normally does not make sense for one | |
af54556a | 2564 | section to refer directly to another. @xref{Miscellaneous Commands, |
b61364cc ILT |
2565 | NOCROSSREFS}. |
2566 | ||
2567 | For each section within the @code{OVERLAY}, the linker automatically | |
2568 | defines two symbols. The symbol @code{__load_start_@var{secname}} is | |
2569 | defined as the starting load address of the section. The symbol | |
2570 | @code{__load_stop_@var{secname}} is defined as the final load address of | |
2571 | the section. Any characters within @var{secname} which are not legal | |
2572 | within C identifiers are removed. C (or assembler) code may use these | |
2573 | symbols to move the overlaid sections around as necessary. | |
2574 | ||
af54556a ILT |
2575 | At the end of the overlay, the value of the location counter is set to |
2576 | the start address of the overlay plus the size of the largest section. | |
b61364cc ILT |
2577 | |
2578 | Here is an example. Remember that this would appear inside a | |
2579 | @code{SECTIONS} construct. | |
b61364cc ILT |
2580 | @smallexample |
2581 | @group | |
2582 | OVERLAY 0x1000 : AT (0x4000) | |
2583 | @{ | |
2584 | .text0 @{ o1/*.o(.text) @} | |
2585 | .text1 @{ o2/*.o(.text) @} | |
2586 | @} | |
2587 | @end group | |
2588 | @end smallexample | |
af54556a ILT |
2589 | @noindent |
2590 | This will define both @samp{.text0} and @samp{.text1} to start at | |
2591 | address 0x1000. @samp{.text0} will be loaded at address 0x4000, and | |
2592 | @samp{.text1} will be loaded immediately after @samp{.text0}. The | |
b61364cc ILT |
2593 | following symbols will be defined: @code{__load_start_text0}, |
2594 | @code{__load_stop_text0}, @code{__load_start_text1}, | |
2595 | @code{__load_stop_text1}. | |
2596 | ||
2597 | C code to copy overlay @code{.text1} into the overlay area might look | |
2598 | like the following. | |
2599 | ||
2600 | @smallexample | |
2601 | @group | |
2602 | extern char __load_start_text1, __load_stop_text1; | |
2603 | memcpy ((char *) 0x1000, &__load_start_text1, | |
2604 | &__load_stop_text1 - &__load_start_text1); | |
2605 | @end group | |
2606 | @end smallexample | |
2607 | ||
2608 | Note that the @code{OVERLAY} command is just syntactic sugar, since | |
2609 | everything it does can be done using the more basic commands. The above | |
2610 | example could have been written identically as follows. | |
2611 | ||
2612 | @smallexample | |
2613 | @group | |
2614 | .text0 0x1000 : AT (0x4000) @{ o1/*.o(.text) @} | |
2615 | __load_start_text0 = LOADADDR (.text0); | |
2616 | __load_stop_text0 = LOADADDR (.text0) + SIZEOF (.text0); | |
2617 | .text1 0x1000 : AT (0x4000 + SIZEOF (.text0)) @{ o2/*.o(.text) @} | |
2618 | __load_start_text1 = LOADADDR (.text1); | |
2619 | __load_stop_text1 = LOADADDR (.text1) + SIZEOF (.text1); | |
2620 | . = 0x1000 + MAX (SIZEOF (.text0), SIZEOF (.text1)); | |
2621 | @end group | |
2622 | @end smallexample | |
2623 | ||
af54556a ILT |
2624 | @node MEMORY |
2625 | @section MEMORY command | |
2626 | @kindex MEMORY | |
2627 | @cindex memory regions | |
2628 | @cindex regions of memory | |
2629 | @cindex allocating memory | |
2630 | @cindex discontinuous memory | |
2631 | The linker's default configuration permits allocation of all available | |
2632 | memory. You can override this by using the @code{MEMORY} command. | |
2633 | ||
2634 | The @code{MEMORY} command describes the location and size of blocks of | |
2635 | memory in the target. You can use it to describe which memory regions | |
2636 | may be used by the linker, and which memory regions it must avoid. You | |
2637 | can then assign sections to particular memory regions. The linker will | |
2638 | set section addresses based on the memory regions, and will warn about | |
2639 | regions that become too full. The linker will not shuffle sections | |
2640 | around to fit into the available regions. | |
2641 | ||
2642 | A linker script may contain at most one use of the @code{MEMORY} | |
2643 | command. However, you can define as many blocks of memory within it as | |
2644 | you wish. The syntax is: | |
2645 | @smallexample | |
2646 | @group | |
2647 | MEMORY | |
2648 | @{ | |
2649 | @var{name} [(@var{attr})] : ORIGIN = @var{origin}, LENGTH = @var{len} | |
2650 | @dots{} | |
2651 | @} | |
2652 | @end group | |
2653 | @end smallexample | |
2654 | ||
2655 | The @var{name} is a name used in the linker script to refer to the | |
2656 | region. The region name has no meaning outside of the linker script. | |
2657 | Region names are stored in a separate name space, and will not conflict | |
2658 | with symbol names, file names, or section names. Each memory region | |
2659 | must have a distinct name. | |
2660 | ||
2661 | @cindex memory region attributes | |
2662 | The @var{attr} string is an optional list of attributes that specify | |
2663 | whether to use a particular memory region for an input section which is | |
2664 | not explicitly mapped in the linker script. As described in | |
2665 | @ref{SECTIONS}, if you do not specify an output section for some input | |
2666 | section, the linker will create an output section with the same name as | |
2667 | the input section. If you define region attributes, the linker will use | |
2668 | them to select the memory region for the output section that it creates. | |
2669 | ||
2670 | The @var{attr} string must consist only of the following characters: | |
2671 | @table @samp | |
2672 | @item R | |
2673 | Read-only section | |
2674 | @item W | |
2675 | Read/write section | |
2676 | @item X | |
2677 | Executable section | |
2678 | @item A | |
2679 | Allocatable section | |
2680 | @item I | |
2681 | Initialized section | |
2682 | @item L | |
2683 | Same as @samp{I} | |
2684 | @item ! | |
2685 | Invert the sense of any of the preceding attributes | |
2686 | @end table | |
2687 | ||
2688 | If a unmapped section matches any of the listed attributes other than | |
2689 | @samp{!}, it will be placed in the memory region. The @samp{!} | |
2690 | attribute reverses this test, so that an unmapped section will be placed | |
2691 | in the memory region only if it does not match any of the listed | |
2692 | attributes. | |
2693 | ||
2694 | @kindex ORIGIN = | |
2695 | @kindex o = | |
2696 | @kindex org = | |
2697 | The @var{origin} is an expression for the start address of the memory | |
2698 | region. The expression must evaluate to a constant before memory | |
2699 | allocation is performed, which means that you may not use any section | |
2700 | relative symbols. The keyword @code{ORIGIN} may be abbreviated to | |
2701 | @code{org} or @code{o} (but not, for example, @code{ORG}). | |
2702 | ||
2703 | @kindex LENGTH = | |
2704 | @kindex len = | |
2705 | @kindex l = | |
2706 | The @var{len} is an expression for the size in bytes of the memory | |
2707 | region. As with the @var{origin} expression, the expression must | |
2708 | evaluate to a constant before memory allocation is performed. The | |
2709 | keyword @code{LENGTH} may be abbreviated to @code{len} or @code{l}. | |
2710 | ||
2711 | In the following example, we specify that there are two memory regions | |
2712 | available for allocation: one starting at @samp{0} for 256 kilobytes, | |
2713 | and the other starting at @samp{0x40000000} for four megabytes. The | |
2714 | linker will place into the @samp{rom} memory region every section which | |
2715 | is not explicitly mapped into a memory region, and is either read-only | |
2716 | or executable. The linker will place other sections which are not | |
2717 | explicitly mapped into a memory region into the @samp{ram} memory | |
2718 | region. | |
2719 | ||
2720 | @smallexample | |
2721 | @group | |
2722 | MEMORY | |
2723 | @{ | |
2724 | rom (rx) : ORIGIN = 0, LENGTH = 256K | |
2725 | ram (!rx) : org = 0x40000000, l = 4M | |
2726 | @} | |
2727 | @end group | |
2728 | @end smallexample | |
2729 | ||
f8a86f8f ILT |
2730 | Once you define a memory region, you can direct the linker to place |
2731 | specific output sections into that memory region by using the | |
2732 | @samp{>@var{region}} output section attribute. For example, if you have | |
2733 | a memory region named @samp{mem}, you would use @samp{>mem} in the | |
2734 | output section definition. @xref{Output Section Region}. If no address | |
2735 | was specified for the output section, the linker will set the address to | |
2736 | the next available address within the memory region. If the combined | |
2737 | output sections directed to a memory region are too large for the | |
2738 | region, the linker will issue an error message. | |
af54556a | 2739 | |
c653b370 | 2740 | @node PHDRS |
af54556a | 2741 | @section PHDRS Command |
c653b370 | 2742 | @kindex PHDRS |
b61364cc ILT |
2743 | @cindex program headers |
2744 | @cindex ELF program headers | |
af54556a ILT |
2745 | @cindex program segments |
2746 | @cindex segments, ELF | |
2747 | The ELF object file format uses @dfn{program headers}, also knows as | |
2748 | @dfn{segments}. The program headers describe how the program should be | |
2749 | loaded into memory. You can print them out by using the @code{objdump} | |
2750 | program with the @samp{-p} option. | |
2751 | ||
2752 | When you run an ELF program on a native ELF system, the system loader | |
2753 | reads the program headers in order to figure out how to load the | |
2754 | program. This will only work if the program headers are set correctly. | |
2755 | This manual does not describe the details of how the system loader | |
2756 | interprets program headers; for more information, see the ELF ABI. | |
2757 | ||
2758 | The linker will create reasonable program headers by default. However, | |
2759 | in some cases, you may need to specify the program headers more | |
2760 | precisely. You may use the @code{PHDRS} command for this purpose. When | |
2761 | the linker sees the @code{PHDRS} command in the linker script, it will | |
2762 | not create any program headers other than the ones specified. | |
2763 | ||
2764 | The linker only pays attention to the @code{PHDRS} command when | |
2765 | generating an ELF output file. In other cases, the linker will simply | |
2766 | ignore @code{PHDRS}. | |
c653b370 ILT |
2767 | |
2768 | This is the syntax of the @code{PHDRS} command. The words @code{PHDRS}, | |
2769 | @code{FILEHDR}, @code{AT}, and @code{FLAGS} are keywords. | |
2770 | ||
2771 | @smallexample | |
2772 | @group | |
2773 | PHDRS | |
2774 | @{ | |
2775 | @var{name} @var{type} [ FILEHDR ] [ PHDRS ] [ AT ( @var{address} ) ] | |
2776 | [ FLAGS ( @var{flags} ) ] ; | |
2777 | @} | |
2778 | @end group | |
2779 | @end smallexample | |
2780 | ||
2781 | The @var{name} is used only for reference in the @code{SECTIONS} command | |
af54556a ILT |
2782 | of the linker script. It is not put into the output file. Program |
2783 | header names are stored in a separate name space, and will not conflict | |
2784 | with symbol names, file names, or section names. Each program header | |
2785 | must have a distinct name. | |
2786 | ||
2787 | Certain program header types describe segments of memory which the | |
2788 | system loader will load from the file. In the linker script, you | |
2789 | specify the contents of these segments by placing allocatable output | |
2790 | sections in the segments. You use the @samp{:@var{phdr}} output section | |
2791 | attribute to place a section in a particular segment. @xref{Output | |
2792 | Section Phdr}. | |
2793 | ||
2794 | It is normal to put certain sections in more than one segment. This | |
2795 | merely implies that one segment of memory contains another. You may | |
2796 | repeat @samp{:@var{phdr}}, using it once for each segment which should | |
2797 | contain the section. | |
2798 | ||
2799 | If you place a section in one or more segments using @samp{:@var{phdr}}, | |
2800 | then the linker will place all subsequent allocatable sections which do | |
2801 | not specify @samp{:@var{phdr}} in the same segments. This is for | |
c653b370 | 2802 | convenience, since generally a whole set of contiguous sections will be |
36a8f215 ILT |
2803 | placed in a single segment. You can use @code{:NONE} to override the |
2804 | default segment and tell the linker to not put the section in any | |
2805 | segment at all. | |
c653b370 | 2806 | |
af54556a ILT |
2807 | @kindex FILEHDR |
2808 | @kindex PHDRS | |
2809 | You may use the @code{FILEHDR} and @code{PHDRS} keywords appear after | |
2810 | the program header type to further describe the contents of the segment. | |
c653b370 ILT |
2811 | The @code{FILEHDR} keyword means that the segment should include the ELF |
2812 | file header. The @code{PHDRS} keyword means that the segment should | |
2813 | include the ELF program headers themselves. | |
2814 | ||
2815 | The @var{type} may be one of the following. The numbers indicate the | |
2816 | value of the keyword. | |
2817 | ||
2818 | @table @asis | |
2819 | @item @code{PT_NULL} (0) | |
2820 | Indicates an unused program header. | |
2821 | ||
2822 | @item @code{PT_LOAD} (1) | |
2823 | Indicates that this program header describes a segment to be loaded from | |
2824 | the file. | |
2825 | ||
2826 | @item @code{PT_DYNAMIC} (2) | |
2827 | Indicates a segment where dynamic linking information can be found. | |
2828 | ||
2829 | @item @code{PT_INTERP} (3) | |
2830 | Indicates a segment where the name of the program interpreter may be | |
2831 | found. | |
2832 | ||
2833 | @item @code{PT_NOTE} (4) | |
2834 | Indicates a segment holding note information. | |
2835 | ||
2836 | @item @code{PT_SHLIB} (5) | |
2837 | A reserved program header type, defined but not specified by the ELF | |
2838 | ABI. | |
2839 | ||
2840 | @item @code{PT_PHDR} (6) | |
2841 | Indicates a segment where the program headers may be found. | |
2842 | ||
2843 | @item @var{expression} | |
2844 | An expression giving the numeric type of the program header. This may | |
2845 | be used for types not defined above. | |
2846 | @end table | |
2847 | ||
af54556a ILT |
2848 | You can specify that a segment should be loaded at a particular address |
2849 | in memory by using an @code{AT} expression. This is identical to the | |
2850 | @code{AT} command used as an output section attribute (@pxref{Output | |
2851 | Section LMA}). The @code{AT} command for a program header overrides the | |
2852 | output section attribute. | |
c653b370 | 2853 | |
af54556a ILT |
2854 | The linker will normally set the segment flags based on the sections |
2855 | which comprise the segment. You may use the @code{FLAGS} keyword to | |
2856 | explicitly specify the segment flags. The value of @var{flags} must be | |
2857 | an integer. It is used to set the @code{p_flags} field of the program | |
2858 | header. | |
c653b370 | 2859 | |
af54556a ILT |
2860 | Here is an example of @code{PHDRS}. This shows a typical set of program |
2861 | headers used on a native ELF system. | |
c653b370 ILT |
2862 | |
2863 | @example | |
2864 | @group | |
2865 | PHDRS | |
2866 | @{ | |
2867 | headers PT_PHDR PHDRS ; | |
2868 | interp PT_INTERP ; | |
2869 | text PT_LOAD FILEHDR PHDRS ; | |
2870 | data PT_LOAD ; | |
2871 | dynamic PT_DYNAMIC ; | |
2872 | @} | |
2873 | ||
2874 | SECTIONS | |
2875 | @{ | |
2876 | . = SIZEOF_HEADERS; | |
2877 | .interp : @{ *(.interp) @} :text :interp | |
2878 | .text : @{ *(.text) @} :text | |
2879 | .rodata : @{ *(.rodata) @} /* defaults to :text */ | |
2880 | @dots{} | |
2881 | . = . + 0x1000; /* move to a new page in memory */ | |
2882 | .data : @{ *(.data) @} :data | |
2883 | .dynamic : @{ *(.dynamic) @} :data :dynamic | |
2884 | @dots{} | |
2885 | @} | |
2886 | @end group | |
2887 | @end example | |
2888 | ||
af54556a ILT |
2889 | @node VERSION |
2890 | @section VERSION Command | |
5a59e34d ILT |
2891 | @kindex VERSION @{script text@} |
2892 | @cindex symbol versions | |
2893 | @cindex version script | |
2894 | @cindex versions of symbols | |
af54556a ILT |
2895 | The linker supports symbol versions when using ELF. Symbol versions are |
2896 | only useful when using shared libraries. The dynamic linker can use | |
2897 | symbol versions to select a specific version of a function when it runs | |
2898 | a program that may have been linked against an earlier version of the | |
2899 | shared library. | |
2900 | ||
2901 | You can include a version script directly in the main linker script, or | |
2902 | you can supply the version script as an implicit linker script. You can | |
2903 | also use the @samp{--version-script} linker option. | |
2904 | ||
2905 | The syntax of the @code{VERSION} command is simply | |
5a59e34d | 2906 | @smallexample |
af54556a | 2907 | VERSION @{ version-script-commands @} |
5a59e34d | 2908 | @end smallexample |
af54556a ILT |
2909 | |
2910 | The format of the version script commands is identical to that used by | |
2911 | Sun's linker in Solaris 2.5. The version script defines a tree of | |
2912 | version nodes. You specify the node names and interdependencies in the | |
2913 | version script. You can specify which symbols are bound to which | |
2914 | version nodes, and you can reduce a specified set of symbols to local | |
2915 | scope so that they are not globally visible outside of the shared | |
5a59e34d ILT |
2916 | library. |
2917 | ||
2918 | The easiest way to demonstrate the version script language is with a few | |
2919 | examples. | |
2920 | ||
2921 | @smallexample | |
2922 | VERS_1.1 @{ | |
2923 | global: | |
2924 | foo1; | |
2925 | local: | |
2926 | old*; | |
2927 | original*; | |
2928 | new*; | |
2929 | @}; | |
2930 | ||
2931 | VERS_1.2 @{ | |
2932 | foo2; | |
2933 | @} VERS_1.1; | |
2934 | ||
2935 | VERS_2.0 @{ | |
2936 | bar1; bar2; | |
2937 | @} VERS_1.2; | |
2938 | @end smallexample | |
2939 | ||
af54556a ILT |
2940 | This example version script defines three version nodes. The first |
2941 | version node defined is @samp{VERS_1.1}; it has no other dependencies. | |
2942 | The script binds the symbol @samp{foo1} to @samp{VERS_1.1}. It reduces | |
2943 | a number of symbols to local scope so that they are not visible outside | |
2944 | of the shared library. | |
5a59e34d | 2945 | |
af54556a ILT |
2946 | Next, the version script defines node @samp{VERS_1.2}. This node |
2947 | depends upon @samp{VERS_1.1}. The script binds the symbol @samp{foo2} | |
2948 | to the version node @samp{VERS_1.2}. | |
5a59e34d | 2949 | |
af54556a ILT |
2950 | Finally, the version script defines node @samp{VERS_2.0}. This node |
2951 | depends upon @samp{VERS_1.2}. The scripts binds the symbols @samp{bar1} | |
2952 | and @samp{bar2} are bound to the version node @samp{VERS_2.0}. | |
5a59e34d | 2953 | |
af54556a ILT |
2954 | When the linker finds a symbol defined in a library which is not |
2955 | specifically bound to a version node, it will effectively bind it to an | |
2956 | unspecified base version of the library. You can bind all otherwise | |
2957 | unspecified symbols to a given version node by using @samp{global: *} | |
2958 | somewhere in the version script. | |
5a59e34d | 2959 | |
af54556a ILT |
2960 | The names of the version nodes have no specific meaning other than what |
2961 | they might suggest to the person reading them. The @samp{2.0} version | |
2962 | could just as well have appeared in between @samp{1.1} and @samp{1.2}. | |
2963 | However, this would be a confusing way to write a version script. | |
5a59e34d ILT |
2964 | |
2965 | When you link an application against a shared library that has versioned | |
af54556a ILT |
2966 | symbols, the application itself knows which version of each symbol it |
2967 | requires, and it also knows which version nodes it needs from each | |
2968 | shared library it is linked against. Thus at runtime, the dynamic | |
2969 | loader can make a quick check to make sure that the libraries you have | |
2970 | linked against do in fact supply all of the version nodes that the | |
2971 | application will need to resolve all of the dynamic symbols. In this | |
2972 | way it is possible for the dynamic linker to know with certainty that | |
2973 | all external symbols that it needs will be resolvable without having to | |
2974 | search for each symbol reference. | |
5a59e34d ILT |
2975 | |
2976 | The symbol versioning is in effect a much more sophisticated way of | |
2977 | doing minor version checking that SunOS does. The fundamental problem | |
2978 | that is being addressed here is that typically references to external | |
2979 | functions are bound on an as-needed basis, and are not all bound when | |
2980 | the application starts up. If a shared library is out of date, a | |
2981 | required interface may be missing; when the application tries to use | |
2982 | that interface, it may suddenly and unexpectedly fail. With symbol | |
2983 | versioning, the user will get a warning when they start their program if | |
2984 | the libraries being used with the application are too old. | |
2985 | ||
2986 | There are several GNU extensions to Sun's versioning approach. The | |
2987 | first of these is the ability to bind a symbol to a version node in the | |
2988 | source file where the symbol is defined instead of in the versioning | |
2989 | script. This was done mainly to reduce the burden on the library | |
af54556a | 2990 | maintainer. You can do this by putting something like: |
5a59e34d ILT |
2991 | @smallexample |
2992 | __asm__(".symver original_foo,foo@@VERS_1.1"); | |
2993 | @end smallexample | |
af54556a ILT |
2994 | @noindent |
2995 | in the C source file. This renames the function @samp{original_foo} to | |
5a59e34d ILT |
2996 | be an alias for @samp{foo} bound to the version node @samp{VERS_1.1}. |
2997 | The @samp{local:} directive can be used to prevent the symbol | |
2998 | @samp{original_foo} from being exported. | |
2999 | ||
af54556a ILT |
3000 | The second GNU extension is to allow multiple versions of the same |
3001 | function to appear in a given shared library. In this way you can make | |
3002 | an incompatible change to an interface without increasing the major | |
3003 | version number of the shared library, while still allowing applications | |
3004 | linked against the old interface to continue to function. | |
5a59e34d | 3005 | |
af54556a ILT |
3006 | To do this, you must use multiple @samp{.symver} directives in the |
3007 | source file. Here is an example: | |
5a59e34d ILT |
3008 | |
3009 | @smallexample | |
3010 | __asm__(".symver original_foo,foo@@"); | |
3011 | __asm__(".symver old_foo,foo@@VERS_1.1"); | |
3012 | __asm__(".symver old_foo1,foo@@VERS_1.2"); | |
3013 | __asm__(".symver new_foo,foo@@@@VERS_2.0"); | |
3014 | @end smallexample | |
3015 | ||
3016 | In this example, @samp{foo@@} represents the symbol @samp{foo} bound to the | |
3017 | unspecified base version of the symbol. The source file that contains this | |
3018 | example would define 4 C functions: @samp{original_foo}, @samp{old_foo}, | |
3019 | @samp{old_foo1}, and @samp{new_foo}. | |
3020 | ||
3021 | When you have multiple definitions of a given symbol, there needs to be | |
3022 | some way to specify a default version to which external references to | |
af54556a ILT |
3023 | this symbol will be bound. You can do this with the |
3024 | @samp{foo@@@@VERS_2.0} type of @samp{.symver} directive. You can only | |
3025 | declare one version of a symbol as the default in this manner; otherwise | |
3026 | you would effectively have multiple definitions of the same symbol. | |
5a59e34d ILT |
3027 | |
3028 | If you wish to bind a reference to a specific version of the symbol | |
3029 | within the shared library, you can use the aliases of convenience | |
3030 | (i.e. @samp{old_foo}), or you can use the @samp{.symver} directive to | |
3031 | specifically bind to an external version of the function in question. | |
3032 | ||
af54556a ILT |
3033 | @node Expressions |
3034 | @section Expressions in Linker Scripts | |
3035 | @cindex expressions | |
3036 | @cindex arithmetic | |
3037 | The syntax for expressions in the linker script language is identical to | |
3038 | that of C expressions. All expressions are evaluated as integers. All | |
3039 | expressions are evaluated in the same size, which is 32 bits if both the | |
3040 | host and target are 32 bits, and is otherwise 64 bits. | |
b4d4e8e3 | 3041 | |
af54556a | 3042 | You can use and set symbol values in expressions. |
a1d393cf | 3043 | |
af54556a ILT |
3044 | The linker defines several special purpose builtin functions for use in |
3045 | expressions. | |
a1d393cf | 3046 | |
af54556a ILT |
3047 | @menu |
3048 | * Constants:: Constants | |
3049 | * Symbols:: Symbol Names | |
3050 | * Location Counter:: The Location Counter | |
3051 | * Operators:: Operators | |
3052 | * Evaluation:: Evaluation | |
3053 | * Expression Section:: The Section of an Expression | |
3054 | * Builtin Functions:: Builtin Functions | |
3055 | @end menu | |
a1d393cf | 3056 | |
af54556a ILT |
3057 | @node Constants |
3058 | @subsection Constants | |
3059 | @cindex integer notation | |
3060 | @cindex constants in linker scripts | |
3061 | All constants are integers. | |
3062 | ||
3063 | As in C, the linker considers an integer beginning with @samp{0} to be | |
3064 | octal, and an integer beginning with @samp{0x} or @samp{0X} to be | |
3065 | hexadecimal. The linker considers other integers to be decimal. | |
3066 | ||
3067 | @cindex scaled integers | |
3068 | @cindex K and M integer suffixes | |
3069 | @cindex M and K integer suffixes | |
3070 | @cindex suffixes for integers | |
3071 | @cindex integer suffixes | |
3072 | In addition, you can use the suffixes @code{K} and @code{M} to scale a | |
3073 | constant by | |
3074 | @c TEXI2ROFF-KILL | |
3075 | @ifinfo | |
3076 | @c END TEXI2ROFF-KILL | |
3077 | @code{1024} or @code{1024*1024} | |
3078 | @c TEXI2ROFF-KILL | |
3079 | @end ifinfo | |
3080 | @tex | |
3081 | ${\rm 1024}$ or ${\rm 1024}^2$ | |
3082 | @end tex | |
3083 | @c END TEXI2ROFF-KILL | |
3084 | respectively. For example, the following all refer to the same quantity: | |
a1d393cf | 3085 | @smallexample |
af54556a ILT |
3086 | _fourk_1 = 4K; |
3087 | _fourk_2 = 4096; | |
3088 | _fourk_3 = 0x1000; | |
a1d393cf ILT |
3089 | @end smallexample |
3090 | ||
af54556a ILT |
3091 | @node Symbols |
3092 | @subsection Symbol Names | |
3093 | @cindex symbol names | |
3094 | @cindex names | |
3095 | @cindex quoted symbol names | |
3096 | @kindex " | |
3097 | Unless quoted, symbol names start with a letter, underscore, or period | |
3098 | and may include letters, digits, underscores, periods, and hyphens. | |
3099 | Unquoted symbol names must not conflict with any keywords. You can | |
3100 | specify a symbol which contains odd characters or has the same name as a | |
3101 | keyword by surrounding the symbol name in double quotes: | |
3102 | @smallexample | |
3103 | "SECTION" = 9; | |
3104 | "with a space" = "also with a space" + 10; | |
3105 | @end smallexample | |
1fb57a5d | 3106 | |
af54556a ILT |
3107 | Since symbols can contain many non-alphabetic characters, it is safest |
3108 | to delimit symbols with spaces. For example, @samp{A-B} is one symbol, | |
3109 | whereas @samp{A - B} is an expression involving subtraction. | |
2c5c0674 | 3110 | |
af54556a ILT |
3111 | @node Location Counter |
3112 | @subsection The Location Counter | |
3113 | @kindex . | |
3114 | @cindex dot | |
3115 | @cindex location counter | |
3116 | @cindex current output location | |
3117 | The special linker variable @dfn{dot} @samp{.} always contains the | |
3118 | current output location counter. Since the @code{.} always refers to a | |
3119 | location in an output section, it may only appear in an expression | |
3120 | within a @code{SECTIONS} command. The @code{.} symbol may appear | |
3121 | anywhere that an ordinary symbol is allowed in an expression. | |
b4d4e8e3 | 3122 | |
af54556a ILT |
3123 | @cindex holes |
3124 | Assigning a value to @code{.} will cause the location counter to be | |
3125 | moved. This may be used to create holes in the output section. The | |
3126 | location counter may never be moved backwards. | |
3127 | ||
3128 | @smallexample | |
3129 | SECTIONS | |
3130 | @{ | |
3131 | output : | |
3132 | @{ | |
3133 | file1(.text) | |
3134 | . = . + 1000; | |
3135 | file2(.text) | |
3136 | . += 1000; | |
3137 | file3(.text) | |
3138 | @} = 0x1234; | |
3139 | @} | |
3140 | @end smallexample | |
3141 | @noindent | |
3142 | In the previous example, the @samp{.text} section from @file{file1} is | |
3143 | located at the beginning of the output section @samp{output}. It is | |
3144 | followed by a 1000 byte gap. Then the @samp{.text} section from | |
3145 | @file{file2} appears, also with a 1000 byte gap following before the | |
3146 | @samp{.text} section from @file{file3}. The notation @samp{= 0x1234} | |
3147 | specifies what data to write in the gaps (@pxref{Output Section Fill}). | |
5a59e34d | 3148 | |
af54556a ILT |
3149 | @need 2000 |
3150 | @node Operators | |
3151 | @subsection Operators | |
3152 | @cindex operators for arithmetic | |
3153 | @cindex arithmetic operators | |
3154 | @cindex precedence in expressions | |
3155 | The linker recognizes the standard C set of arithmetic operators, with | |
3156 | the standard bindings and precedence levels: | |
3157 | @c TEXI2ROFF-KILL | |
3158 | @ifinfo | |
3159 | @c END TEXI2ROFF-KILL | |
3160 | @smallexample | |
3161 | precedence associativity Operators Notes | |
3162 | (highest) | |
3163 | 1 left ! - ~ (1) | |
3164 | 2 left * / % | |
3165 | 3 left + - | |
3166 | 4 left >> << | |
3167 | 5 left == != > < <= >= | |
3168 | 6 left & | |
3169 | 7 left | | |
3170 | 8 left && | |
3171 | 9 left || | |
3172 | 10 right ? : | |
3173 | 11 right &= += -= *= /= (2) | |
3174 | (lowest) | |
3175 | @end smallexample | |
3176 | Notes: | |
3177 | (1) Prefix operators | |
3178 | (2) @xref{Assignments}. | |
3179 | @c TEXI2ROFF-KILL | |
3180 | @end ifinfo | |
3181 | @tex | |
3182 | \vskip \baselineskip | |
3183 | %"lispnarrowing" is the extra indent used generally for smallexample | |
3184 | \hskip\lispnarrowing\vbox{\offinterlineskip | |
3185 | \hrule | |
3186 | \halign | |
3187 | {\vrule#&\strut\hfil\ #\ \hfil&\vrule#&\strut\hfil\ #\ \hfil&\vrule#&\strut\hfil\ {\tt #}\ \hfil&\vrule#\cr | |
3188 | height2pt&\omit&&\omit&&\omit&\cr | |
3189 | &Precedence&& Associativity &&{\rm Operators}&\cr | |
3190 | height2pt&\omit&&\omit&&\omit&\cr | |
3191 | \noalign{\hrule} | |
3192 | height2pt&\omit&&\omit&&\omit&\cr | |
3193 | &highest&&&&&\cr | |
3194 | % '176 is tilde, '~' in tt font | |
3195 | &1&&left&&\qquad- \char'176\ !\qquad\dag&\cr | |
3196 | &2&&left&&* / \%&\cr | |
3197 | &3&&left&&+ -&\cr | |
3198 | &4&&left&&>> <<&\cr | |
3199 | &5&&left&&== != > < <= >=&\cr | |
3200 | &6&&left&&\&&\cr | |
3201 | &7&&left&&|&\cr | |
3202 | &8&&left&&{\&\&}&\cr | |
3203 | &9&&left&&||&\cr | |
3204 | &10&&right&&? :&\cr | |
3205 | &11&&right&&\qquad\&= += -= *= /=\qquad\ddag&\cr | |
3206 | &lowest&&&&&\cr | |
3207 | height2pt&\omit&&\omit&&\omit&\cr} | |
3208 | \hrule} | |
3209 | @end tex | |
3210 | @iftex | |
3211 | { | |
3212 | @obeylines@parskip=0pt@parindent=0pt | |
3213 | @dag@quad Prefix operators. | |
3214 | @ddag@quad @xref{Assignments}. | |
3215 | } | |
3216 | @end iftex | |
3217 | @c END TEXI2ROFF-KILL | |
7f9ae73e | 3218 | |
af54556a ILT |
3219 | @node Evaluation |
3220 | @subsection Evaluation | |
3221 | @cindex lazy evaluation | |
3222 | @cindex expression evaluation order | |
3223 | The linker evaluates expressions lazily. It only computes the value of | |
3224 | an expression when absolutely necessary. | |
b4d4e8e3 | 3225 | |
af54556a ILT |
3226 | The linker needs some information, such as the value of the start |
3227 | address of the first section, and the origins and lengths of memory | |
3228 | regions, in order to do any linking at all. These values are computed | |
3229 | as soon as possible when the linker reads in the linker script. | |
01bc8f35 | 3230 | |
af54556a ILT |
3231 | However, other values (such as symbol values) are not known or needed |
3232 | until after storage allocation. Such values are evaluated later, when | |
3233 | other information (such as the sizes of output sections) is available | |
3234 | for use in the symbol assignment expression. | |
0b3499f6 | 3235 | |
af54556a ILT |
3236 | The sizes of sections cannot be known until after allocation, so |
3237 | assignments dependent upon these are not performed until after | |
3238 | allocation. | |
b4d4e8e3 | 3239 | |
af54556a ILT |
3240 | Some expressions, such as those depending upon the location counter |
3241 | @samp{.}, must be evaluated during section allocation. | |
2c5c0674 | 3242 | |
af54556a ILT |
3243 | If the result of an expression is required, but the value is not |
3244 | available, then an error results. For example, a script like the | |
3245 | following | |
3246 | @smallexample | |
3247 | @group | |
3248 | SECTIONS | |
3249 | @{ | |
3250 | .text 9+this_isnt_constant : | |
3251 | @{ *(.text) @} | |
3252 | @} | |
3253 | @end group | |
3254 | @end smallexample | |
3255 | @noindent | |
3256 | will cause the error message @samp{non constant expression for initial | |
3257 | address}. | |
3258 | ||
3259 | @node Expression Section | |
3260 | @subsection The Section of an Expression | |
3261 | @cindex expression sections | |
3262 | @cindex absolute expressions | |
3263 | @cindex relative expressions | |
3264 | @cindex absolute and relocatable symbols | |
3265 | @cindex relocatable and absolute symbols | |
3266 | @cindex symbols, relocatable and absolute | |
3267 | When the linker evaluates an expression, the result is either absolute | |
3268 | or relative to some section. A relative expression is expressed as a | |
3269 | fixed offset from the base of a section. | |
3270 | ||
3271 | The position of the expression within the linker script determines | |
3272 | whether it is absolute or relative. An expression which appears within | |
3273 | an output section definition is relative to the base of the output | |
3274 | section. An expression which appears elsewhere will be absolute. | |
3275 | ||
3276 | A symbol set to a relative expression will be relocatable if you request | |
3277 | relocatable output using the @samp{-r} option. That means that a | |
3278 | further link operation may change the value of the symbol. The symbol's | |
3279 | section will be the section of the relative expression. | |
3280 | ||
3281 | A symbol set to an absolute expression will retain the same value | |
3282 | through any further link operation. The symbol will be absolute, and | |
3283 | will not have any particular associated section. | |
3284 | ||
3285 | You can use the builtin function @code{ABSOLUTE} to force an expression | |
3286 | to be absolute when it would otherwise be relative. For example, to | |
3287 | create an absolute symbol set to the address of the end of the output | |
3288 | section @samp{.data}: | |
3289 | @smallexample | |
3290 | SECTIONS | |
3291 | @{ | |
3292 | .data : @{ *(.data) _edata = ABSOLUTE(.); @} | |
3293 | @} | |
3294 | @end smallexample | |
3295 | @noindent | |
3296 | If @samp{ABSOLUTE} were not used, @samp{_edata} would be relative to the | |
3297 | @samp{.data} section. | |
2c5c0674 | 3298 | |
af54556a ILT |
3299 | @node Builtin Functions |
3300 | @subsection Builtin Functions | |
3301 | @cindex functions in expressions | |
3302 | The linker script language includes a number of builtin functions for | |
3303 | use in linker script expressions. | |
2c5c0674 | 3304 | |
af54556a ILT |
3305 | @table @code |
3306 | @item ABSOLUTE(@var{exp}) | |
3307 | @kindex ABSOLUTE(@var{exp}) | |
3308 | @cindex expression, absolute | |
3309 | Return the absolute (non-relocatable, as opposed to non-negative) value | |
3310 | of the expression @var{exp}. Primarily useful to assign an absolute | |
3311 | value to a symbol within a section definition, where symbol values are | |
3312 | normally section relative. @xref{Expression Section}. | |
b4d4e8e3 | 3313 | |
af54556a ILT |
3314 | @item ADDR(@var{section}) |
3315 | @kindex ADDR(@var{section}) | |
3316 | @cindex section address in expression | |
3317 | Return the absolute address (the VMA) of the named @var{section}. Your | |
3318 | script must previously have defined the location of that section. In | |
3319 | the following example, @code{symbol_1} and @code{symbol_2} are assigned | |
3320 | identical values: | |
3321 | @smallexample | |
3322 | @group | |
3323 | SECTIONS @{ @dots{} | |
3324 | .output1 : | |
3325 | @{ | |
3326 | start_of_output_1 = ABSOLUTE(.); | |
3327 | @dots{} | |
3328 | @} | |
3329 | .output : | |
3330 | @{ | |
3331 | symbol_1 = ADDR(.output1); | |
3332 | symbol_2 = start_of_output_1; | |
3333 | @} | |
3334 | @dots{} @} | |
3335 | @end group | |
3336 | @end smallexample | |
2c5c0674 | 3337 | |
af54556a ILT |
3338 | @item ALIGN(@var{exp}) |
3339 | @kindex ALIGN(@var{exp}) | |
3340 | @cindex round up location counter | |
3341 | @cindex align location counter | |
3342 | Return the location counter (@code{.}) aligned to the next @var{exp} | |
3343 | boundary. @var{exp} must be an expression whose value is a power of | |
3344 | two. This is equivalent to | |
3345 | @smallexample | |
3346 | (. + @var{exp} - 1) & ~(@var{exp} - 1) | |
3347 | @end smallexample | |
582dd77f | 3348 | |
af54556a ILT |
3349 | @code{ALIGN} doesn't change the value of the location counter---it just |
3350 | does arithmetic on it. Here is an example which aligns the output | |
3351 | @code{.data} section to the next @code{0x2000} byte boundary after the | |
3352 | preceding section and sets a variable within the section to the next | |
3353 | @code{0x8000} boundary after the input sections: | |
3354 | @smallexample | |
3355 | @group | |
3356 | SECTIONS @{ @dots{} | |
3357 | .data ALIGN(0x2000): @{ | |
3358 | *(.data) | |
3359 | variable = ALIGN(0x8000); | |
3360 | @} | |
3361 | @dots{} @} | |
3362 | @end group | |
3363 | @end smallexample | |
3364 | @noindent | |
3365 | The first use of @code{ALIGN} in this example specifies the location of | |
3366 | a section because it is used as the optional @var{address} attribute of | |
3367 | a section definition (@pxref{Output Section Address}). The second use | |
3368 | of @code{ALIGN} is used to defines the value of a symbol. | |
582dd77f | 3369 | |
af54556a | 3370 | The builtin function @code{NEXT} is closely related to @code{ALIGN}. |
582dd77f | 3371 | |
af54556a ILT |
3372 | @item BLOCK(@var{exp}) |
3373 | @kindex BLOCK(@var{exp}) | |
3374 | This is a synonym for @code{ALIGN}, for compatibility with older linker | |
3375 | scripts. It is most often seen when setting the address of an output | |
3376 | section. | |
3377 | ||
3378 | @item DEFINED(@var{symbol}) | |
3379 | @kindex DEFINED(@var{symbol}) | |
3380 | @cindex symbol defaults | |
3381 | Return 1 if @var{symbol} is in the linker global symbol table and is | |
3382 | defined, otherwise return 0. You can use this function to provide | |
3383 | default values for symbols. For example, the following script fragment | |
3384 | shows how to set a global symbol @samp{begin} to the first location in | |
3385 | the @samp{.text} section---but if a symbol called @samp{begin} already | |
3386 | existed, its value is preserved: | |
3387 | ||
3388 | @smallexample | |
3389 | @group | |
da713b8f | 3390 | SECTIONS @{ @dots{} |
af54556a ILT |
3391 | .text : @{ |
3392 | begin = DEFINED(begin) ? begin : . ; | |
3393 | @dots{} | |
3394 | @} | |
da713b8f ILT |
3395 | @dots{} |
3396 | @} | |
af54556a ILT |
3397 | @end group |
3398 | @end smallexample | |
3399 | ||
3400 | @item LOADADDR(@var{section}) | |
3401 | @kindex LOADADDR(@var{section}) | |
3402 | @cindex section load address in expression | |
3403 | Return the absolute LMA of the named @var{section}. This is normally | |
3404 | the same as @code{ADDR}, but it may be different if the @code{AT} | |
3405 | attribute is used in the output section definition (@pxref{Output | |
3406 | Section LMA}). | |
3407 | ||
3408 | @kindex MAX | |
3409 | @item MAX(@var{exp1}, @var{exp2}) | |
3410 | Returns the maximum of @var{exp1} and @var{exp2}. | |
3411 | ||
3412 | @kindex MIN | |
3413 | @item MIN(@var{exp1}, @var{exp2}) | |
3414 | Returns the minimum of @var{exp1} and @var{exp2}. | |
3415 | ||
3416 | @item NEXT(@var{exp}) | |
3417 | @kindex NEXT(@var{exp}) | |
3418 | @cindex unallocated address, next | |
3419 | Return the next unallocated address that is a multiple of @var{exp}. | |
3420 | This function is closely related to @code{ALIGN(@var{exp})}; unless you | |
3421 | use the @code{MEMORY} command to define discontinuous memory for the | |
3422 | output file, the two functions are equivalent. | |
3423 | ||
3424 | @item SIZEOF(@var{section}) | |
3425 | @kindex SIZEOF(@var{section}) | |
3426 | @cindex section size | |
3427 | Return the size in bytes of the named @var{section}, if that section has | |
3428 | been allocated. If the section has not been allocated when this is | |
3429 | evaluated, the linker will report an error. In the following example, | |
3430 | @code{symbol_1} and @code{symbol_2} are assigned identical values: | |
3431 | @smallexample | |
3432 | @group | |
3433 | SECTIONS@{ @dots{} | |
3434 | .output @{ | |
3435 | .start = . ; | |
3436 | @dots{} | |
3437 | .end = . ; | |
3438 | @} | |
3439 | symbol_1 = .end - .start ; | |
3440 | symbol_2 = SIZEOF(.output); | |
3441 | @dots{} @} | |
3442 | @end group | |
3443 | @end smallexample | |
3444 | ||
3445 | @item SIZEOF_HEADERS | |
3446 | @itemx sizeof_headers | |
3447 | @kindex SIZEOF_HEADERS | |
3448 | @cindex header size | |
3449 | Return the size in bytes of the output file's headers. This is | |
3450 | information which appears at the start of the output file. You can use | |
3451 | this number when setting the start address of the first section, if you | |
3452 | choose, to facilitate paging. | |
3453 | ||
3454 | @cindex not enough room for program headers | |
3455 | @cindex program headers, not enough room | |
3456 | When producing an ELF output file, if the linker script uses the | |
3457 | @code{SIZEOF_HEADERS} builtin function, the linker must compute the | |
3458 | number of program headers before it has determined all the section | |
3459 | addresses and sizes. If the linker later discovers that it needs | |
3460 | additional program headers, it will report an error @samp{not enough | |
3461 | room for program headers}. To avoid this error, you must avoid using | |
3462 | the @code{SIZEOF_HEADERS} function, or you must rework your linker | |
3463 | script to avoid forcing the linker to use additional program headers, or | |
3464 | you must define the program headers yourself using the @code{PHDRS} | |
3465 | command (@pxref{PHDRS}). | |
b4d4e8e3 RP |
3466 | @end table |
3467 | ||
f8cf2baa ILT |
3468 | @node Implicit Linker Scripts |
3469 | @section Implicit Linker Scripts | |
3470 | @cindex implicit linker scripts | |
3471 | If you specify a linker input file which the linker can not recognize as | |
3472 | an object file or an archive file, it will try to read the file as a | |
3473 | linker script. If the file can not be parsed as a linker script, the | |
3474 | linker will report an error. | |
3475 | ||
3476 | An implicit linker script will not replace the default linker script. | |
3477 | ||
3478 | Typically an implicit linker script would contain only symbol | |
3479 | assignments, or the @code{INPUT}, @code{GROUP}, or @code{VERSION} | |
3480 | commands. | |
3481 | ||
3482 | Any input files read because of an implicit linker script will be read | |
3483 | at the position in the command line where the implicit linker script was | |
3484 | read. This can affect archive searching. | |
3485 | ||
ec40bbb8 DM |
3486 | @ifset GENERIC |
3487 | @node Machine Dependent | |
1c48127e RP |
3488 | @chapter Machine Dependent Features |
3489 | ||
3490 | @cindex machine dependencies | |
246504a5 RP |
3491 | @code{ld} has additional features on some platforms; the following |
3492 | sections describe them. Machines where @code{ld} has no additional | |
1c48127e RP |
3493 | functionality are not listed. |
3494 | ||
3495 | @menu | |
246504a5 RP |
3496 | * H8/300:: @code{ld} and the H8/300 |
3497 | * i960:: @code{ld} and the Intel 960 family | |
da713b8f | 3498 | * ARM:: @code{ld} and the ARM family |
1c48127e | 3499 | @end menu |
ec40bbb8 DM |
3500 | @end ifset |
3501 | ||
7f9ae73e | 3502 | @c FIXME! This could use @raisesections/@lowersections, but there seems to be a conflict |
ec40bbb8 DM |
3503 | @c between those and node-defaulting. |
3504 | @ifset H8300 | |
3505 | @ifclear GENERIC | |
7f9ae73e | 3506 | @raisesections |
ec40bbb8 | 3507 | @end ifclear |
da713b8f | 3508 | |
ec40bbb8 | 3509 | @node H8/300 |
246504a5 | 3510 | @section @code{ld} and the H8/300 |
1c48127e RP |
3511 | |
3512 | @cindex H8/300 support | |
246504a5 | 3513 | For the H8/300, @code{ld} can perform these global optimizations when |
9fde46a4 | 3514 | you specify the @samp{--relax} command-line option. |
1c48127e RP |
3515 | |
3516 | @table @emph | |
d76ae847 | 3517 | @cindex relaxing on H8/300 |
c653b370 | 3518 | @item relaxing address modes |
246504a5 | 3519 | @code{ld} finds all @code{jsr} and @code{jmp} instructions whose |
1c48127e RP |
3520 | targets are within eight bits, and turns them into eight-bit |
3521 | program-counter relative @code{bsr} and @code{bra} instructions, | |
3522 | respectively. | |
3523 | ||
d76ae847 | 3524 | @cindex synthesizing on H8/300 |
c653b370 | 3525 | @item synthesizing instructions |
1c48127e | 3526 | @c FIXME: specifically mov.b, or any mov instructions really? |
246504a5 | 3527 | @code{ld} finds all @code{mov.b} instructions which use the |
1c48127e RP |
3528 | sixteen-bit absolute address form, but refer to the top |
3529 | page of memory, and changes them to use the eight-bit address form. | |
3530 | (That is: the linker turns @samp{mov.b @code{@@}@var{aa}:16} into | |
3531 | @samp{mov.b @code{@@}@var{aa}:8} whenever the address @var{aa} is in the | |
3532 | top page of memory). | |
3533 | @end table | |
da713b8f | 3534 | |
ec40bbb8 | 3535 | @ifclear GENERIC |
7f9ae73e | 3536 | @lowersections |
ec40bbb8 DM |
3537 | @end ifclear |
3538 | @end ifset | |
3539 | ||
f9d3d71a ILT |
3540 | @ifclear GENERIC |
3541 | @ifset Hitachi | |
3542 | @c This stuff is pointless to say unless you're especially concerned | |
3543 | @c with Hitachi chips; don't enable it for generic case, please. | |
3544 | @node Hitachi | |
3545 | @chapter @code{ld} and other Hitachi chips | |
3546 | ||
3547 | @code{ld} also supports the H8/300H, the H8/500, and the Hitachi SH. No | |
3548 | special features, commands, or command-line options are required for | |
3549 | these chips. | |
3550 | @end ifset | |
3551 | @end ifclear | |
3552 | ||
ec40bbb8 DM |
3553 | @ifset I960 |
3554 | @ifclear GENERIC | |
7f9ae73e | 3555 | @raisesections |
ec40bbb8 | 3556 | @end ifclear |
da713b8f | 3557 | |
ec40bbb8 | 3558 | @node i960 |
246504a5 | 3559 | @section @code{ld} and the Intel 960 family |
1c48127e RP |
3560 | |
3561 | @cindex i960 support | |
d76ae847 | 3562 | |
1c48127e RP |
3563 | You can use the @samp{-A@var{architecture}} command line option to |
3564 | specify one of the two-letter names identifying members of the 960 | |
3565 | family; the option specifies the desired output target, and warns of any | |
3566 | incompatible instructions in the input files. It also modifies the | |
3567 | linker's search strategy for archive libraries, to support the use of | |
3568 | libraries specific to each particular architecture, by including in the | |
3569 | search loop names suffixed with the string identifying the architecture. | |
3570 | ||
246504a5 | 3571 | For example, if your @code{ld} command line included @w{@samp{-ACA}} as |
1c48127e | 3572 | well as @w{@samp{-ltry}}, the linker would look (in its built-in search |
ec40bbb8 | 3573 | paths, and in any paths you specify with @samp{-L}) for a library with |
1c48127e | 3574 | the names |
ec40bbb8 | 3575 | |
c653b370 ILT |
3576 | @smallexample |
3577 | @group | |
1c48127e RP |
3578 | try |
3579 | libtry.a | |
3580 | tryca | |
3581 | libtryca.a | |
c653b370 ILT |
3582 | @end group |
3583 | @end smallexample | |
ec40bbb8 | 3584 | |
1c48127e RP |
3585 | @noindent |
3586 | The first two possibilities would be considered in any event; the last | |
3587 | two are due to the use of @w{@samp{-ACA}}. | |
3588 | ||
ec40bbb8 | 3589 | You can meaningfully use @samp{-A} more than once on a command line, since |
1c48127e | 3590 | the 960 architecture family allows combination of target architectures; each |
ec40bbb8 | 3591 | use will add another pair of name variants to search for when @w{@samp{-l}} |
1c48127e | 3592 | specifies a library. |
1fb57a5d | 3593 | |
9fde46a4 | 3594 | @cindex @code{--relax} on i960 |
1fb57a5d | 3595 | @cindex relaxing on i960 |
9fde46a4 ILT |
3596 | @code{ld} supports the @samp{--relax} option for the i960 family. If |
3597 | you specify @samp{--relax}, @code{ld} finds all @code{balx} and | |
3598 | @code{calx} instructions whose targets are within 24 bits, and turns | |
3599 | them into 24-bit program-counter relative @code{bal} and @code{cal} | |
1fb57a5d RP |
3600 | instructions, respectively. @code{ld} also turns @code{cal} |
3601 | instructions into @code{bal} instructions when it determines that the | |
3602 | target subroutine is a leaf routine (that is, the target subroutine does | |
3603 | not itself call any subroutines). | |
3604 | ||
ec40bbb8 | 3605 | @ifclear GENERIC |
7f9ae73e | 3606 | @lowersections |
ec40bbb8 DM |
3607 | @end ifclear |
3608 | @end ifset | |
1c48127e | 3609 | |
da713b8f ILT |
3610 | @ifclear GENERIC |
3611 | @raisesections | |
3612 | @end ifclear | |
3613 | ||
3614 | @node ARM | |
3615 | @section @code{ld}'s support for interworking between ARM and Thumb code | |
3616 | ||
3617 | @cindex ARM interworking support | |
3618 | @cindex --support-old-code | |
3619 | For the ARM, @code{ld} will generate code stubs to allow functions calls | |
3620 | betweem ARM and Thumb code. These stubs only work with code that has | |
3621 | been compiled and assembled with the @samp{-mthumb-interwork} command | |
3622 | line option. If it is necessary to link with old ARM object files or | |
3623 | libraries, which have not been compiled with the -mthumb-interwork | |
3624 | option then the @samp{--support-old-code} command line switch should be | |
3625 | given to the linker. This will make it generate larger stub functions | |
3626 | which will work with non-interworking aware ARM code. Note, however, | |
3627 | the linker does not support generating stubs for function calls to | |
3628 | non-interworking aware Thumb code. | |
3629 | ||
3630 | @ifclear GENERIC | |
3631 | @lowersections | |
3632 | @end ifclear | |
3633 | ||
ec40bbb8 DM |
3634 | @ifclear SingleFormat |
3635 | @node BFD | |
f22eee08 RP |
3636 | @chapter BFD |
3637 | ||
2c5c0674 RP |
3638 | @cindex back end |
3639 | @cindex object file management | |
d4e5e3c3 DM |
3640 | @cindex object formats available |
3641 | @kindex objdump -i | |
2c5c0674 RP |
3642 | The linker accesses object and archive files using the BFD libraries. |
3643 | These libraries allow the linker to use the same routines to operate on | |
3644 | object files whatever the object file format. A different object file | |
3645 | format can be supported simply by creating a new BFD back end and adding | |
d4e5e3c3 DM |
3646 | it to the library. To conserve runtime memory, however, the linker and |
3647 | associated tools are usually configured to support only a subset of the | |
3648 | object file formats available. You can use @code{objdump -i} | |
1c48127e | 3649 | (@pxref{objdump,,objdump,binutils.info,The GNU Binary Utilities}) to |
d4e5e3c3 | 3650 | list all the formats available for your configuration. |
f22eee08 | 3651 | |
2c5c0674 RP |
3652 | @cindex BFD requirements |
3653 | @cindex requirements for BFD | |
3654 | As with most implementations, BFD is a compromise between | |
f22eee08 | 3655 | several conflicting requirements. The major factor influencing |
2c5c0674 RP |
3656 | BFD design was efficiency: any time used converting between |
3657 | formats is time which would not have been spent had BFD not | |
f22eee08 | 3658 | been involved. This is partly offset by abstraction payback; since |
2c5c0674 | 3659 | BFD simplifies applications and back ends, more time and care |
f22eee08 RP |
3660 | may be spent optimizing algorithms for a greater speed. |
3661 | ||
2c5c0674 RP |
3662 | One minor artifact of the BFD solution which you should bear in |
3663 | mind is the potential for information loss. There are two places where | |
ec40bbb8 | 3664 | useful information can be lost using the BFD mechanism: during |
2c5c0674 RP |
3665 | conversion and during output. @xref{BFD information loss}. |
3666 | ||
3667 | @menu | |
2d59b2c3 | 3668 | * BFD outline:: How it works: an outline of BFD |
2c5c0674 | 3669 | @end menu |
f22eee08 | 3670 | |
ec40bbb8 | 3671 | @node BFD outline |
b4d4e8e3 | 3672 | @section How it works: an outline of BFD |
2c5c0674 | 3673 | @cindex opening object files |
3e27cc11 | 3674 | @include bfdsumm.texi |
ec40bbb8 | 3675 | @end ifclear |
f22eee08 | 3676 | |
9fde46a4 ILT |
3677 | @node Reporting Bugs |
3678 | @chapter Reporting Bugs | |
3679 | @cindex bugs in @code{ld} | |
3680 | @cindex reporting bugs in @code{ld} | |
3681 | ||
3682 | Your bug reports play an essential role in making @code{ld} reliable. | |
3683 | ||
3684 | Reporting a bug may help you by bringing a solution to your problem, or | |
3685 | it may not. But in any case the principal function of a bug report is | |
3686 | to help the entire community by making the next version of @code{ld} | |
3687 | work better. Bug reports are your contribution to the maintenance of | |
3688 | @code{ld}. | |
3689 | ||
3690 | In order for a bug report to serve its purpose, you must include the | |
3691 | information that enables us to fix the bug. | |
3692 | ||
3693 | @menu | |
3694 | * Bug Criteria:: Have you found a bug? | |
3695 | * Bug Reporting:: How to report bugs | |
3696 | @end menu | |
3697 | ||
3698 | @node Bug Criteria | |
3699 | @section Have you found a bug? | |
3700 | @cindex bug criteria | |
3701 | ||
3702 | If you are not sure whether you have found a bug, here are some guidelines: | |
3703 | ||
3704 | @itemize @bullet | |
3705 | @cindex fatal signal | |
3706 | @cindex linker crash | |
3707 | @cindex crash of linker | |
3708 | @item | |
3709 | If the linker gets a fatal signal, for any input whatever, that is a | |
3710 | @code{ld} bug. Reliable linkers never crash. | |
3711 | ||
3712 | @cindex error on valid input | |
3713 | @item | |
3714 | If @code{ld} produces an error message for valid input, that is a bug. | |
3715 | ||
3716 | @cindex invalid input | |
3717 | @item | |
3718 | If @code{ld} does not produce an error message for invalid input, that | |
3719 | may be a bug. In the general case, the linker can not verify that | |
3720 | object files are correct. | |
3721 | ||
3722 | @item | |
3723 | If you are an experienced user of linkers, your suggestions for | |
3724 | improvement of @code{ld} are welcome in any case. | |
3725 | @end itemize | |
3726 | ||
3727 | @node Bug Reporting | |
3728 | @section How to report bugs | |
3729 | @cindex bug reports | |
3730 | @cindex @code{ld} bugs, reporting | |
3731 | ||
3732 | A number of companies and individuals offer support for @sc{gnu} | |
3733 | products. If you obtained @code{ld} from a support organization, we | |
3734 | recommend you contact that organization first. | |
3735 | ||
3736 | You can find contact information for many support companies and | |
3737 | individuals in the file @file{etc/SERVICE} in the @sc{gnu} Emacs | |
3738 | distribution. | |
3739 | ||
af54556a ILT |
3740 | Otherwise, send bug reports for @code{ld} to |
3741 | @samp{bug-gnu-utils@@gnu.org}. | |
9fde46a4 ILT |
3742 | |
3743 | The fundamental principle of reporting bugs usefully is this: | |
3744 | @strong{report all the facts}. If you are not sure whether to state a | |
3745 | fact or leave it out, state it! | |
3746 | ||
3747 | Often people omit facts because they think they know what causes the | |
3748 | problem and assume that some details do not matter. Thus, you might | |
3749 | assume that the name of a symbol you use in an example does not matter. | |
3750 | Well, probably it does not, but one cannot be sure. Perhaps the bug is | |
3751 | a stray memory reference which happens to fetch from the location where | |
3752 | that name is stored in memory; perhaps, if the name were different, the | |
3753 | contents of that location would fool the linker into doing the right | |
3754 | thing despite the bug. Play it safe and give a specific, complete | |
3755 | example. That is the easiest thing for you to do, and the most helpful. | |
3756 | ||
3757 | Keep in mind that the purpose of a bug report is to enable us to fix the bug if | |
3758 | it is new to us. Therefore, always write your bug reports on the assumption | |
3759 | that the bug has not been reported previously. | |
3760 | ||
3761 | Sometimes people give a few sketchy facts and ask, ``Does this ring a | |
3762 | bell?'' Those bug reports are useless, and we urge everyone to | |
3763 | @emph{refuse to respond to them} except to chide the sender to report | |
3764 | bugs properly. | |
3765 | ||
3766 | To enable us to fix the bug, you should include all these things: | |
3767 | ||
3768 | @itemize @bullet | |
3769 | @item | |
3770 | The version of @code{ld}. @code{ld} announces it if you start it with | |
3771 | the @samp{--version} argument. | |
3772 | ||
3773 | Without this, we will not know whether there is any point in looking for | |
3774 | the bug in the current version of @code{ld}. | |
3775 | ||
3776 | @item | |
3777 | Any patches you may have applied to the @code{ld} source, including any | |
3778 | patches made to the @code{BFD} library. | |
3779 | ||
3780 | @item | |
3781 | The type of machine you are using, and the operating system name and | |
3782 | version number. | |
3783 | ||
3784 | @item | |
3785 | What compiler (and its version) was used to compile @code{ld}---e.g. | |
3786 | ``@code{gcc-2.7}''. | |
3787 | ||
3788 | @item | |
3789 | The command arguments you gave the linker to link your example and | |
3790 | observe the bug. To guarantee you will not omit something important, | |
3791 | list them all. A copy of the Makefile (or the output from make) is | |
3792 | sufficient. | |
3793 | ||
3794 | If we were to try to guess the arguments, we would probably guess wrong | |
3795 | and then we might not encounter the bug. | |
3796 | ||
3797 | @item | |
3798 | A complete input file, or set of input files, that will reproduce the | |
3799 | bug. It is generally most helpful to send the actual object files, | |
3800 | uuencoded if necessary to get them through the mail system. Making them | |
3801 | available for anonymous FTP is not as good, but may be the only | |
3802 | reasonable choice for large object files. | |
3803 | ||
3804 | If the source files were assembled using @code{gas} or compiled using | |
3805 | @code{gcc}, then it may be OK to send the source files rather than the | |
3806 | object files. In this case, be sure to say exactly what version of | |
3807 | @code{gas} or @code{gcc} was used to produce the object files. Also say | |
3808 | how @code{gas} or @code{gcc} were configured. | |
3809 | ||
3810 | @item | |
3811 | A description of what behavior you observe that you believe is | |
3812 | incorrect. For example, ``It gets a fatal signal.'' | |
3813 | ||
3814 | Of course, if the bug is that @code{ld} gets a fatal signal, then we | |
3815 | will certainly notice it. But if the bug is incorrect output, we might | |
3816 | not notice unless it is glaringly wrong. You might as well not give us | |
3817 | a chance to make a mistake. | |
3818 | ||
3819 | Even if the problem you experience is a fatal signal, you should still | |
3820 | say so explicitly. Suppose something strange is going on, such as, your | |
3821 | copy of @code{ld} is out of synch, or you have encountered a bug in the | |
3822 | C library on your system. (This has happened!) Your copy might crash | |
3823 | and ours would not. If you told us to expect a crash, then when ours | |
3824 | fails to crash, we would know that the bug was not happening for us. If | |
3825 | you had not told us to expect a crash, then we would not be able to draw | |
3826 | any conclusion from our observations. | |
3827 | ||
3828 | @item | |
3829 | If you wish to suggest changes to the @code{ld} source, send us context | |
3830 | diffs, as generated by @code{diff} with the @samp{-u}, @samp{-c}, or | |
3831 | @samp{-p} option. Always send diffs from the old file to the new file. | |
3832 | If you even discuss something in the @code{ld} source, refer to it by | |
3833 | context, not by line number. | |
3834 | ||
3835 | The line numbers in our development sources will not match those in your | |
3836 | sources. Your line numbers would convey no useful information to us. | |
3837 | @end itemize | |
3838 | ||
3839 | Here are some things that are not necessary: | |
3840 | ||
3841 | @itemize @bullet | |
3842 | @item | |
3843 | A description of the envelope of the bug. | |
3844 | ||
3845 | Often people who encounter a bug spend a lot of time investigating | |
3846 | which changes to the input file will make the bug go away and which | |
3847 | changes will not affect it. | |
3848 | ||
3849 | This is often time consuming and not very useful, because the way we | |
3850 | will find the bug is by running a single example under the debugger | |
3851 | with breakpoints, not by pure deduction from a series of examples. | |
3852 | We recommend that you save your time for something else. | |
3853 | ||
3854 | Of course, if you can find a simpler example to report @emph{instead} | |
3855 | of the original one, that is a convenience for us. Errors in the | |
3856 | output will be easier to spot, running under the debugger will take | |
3857 | less time, and so on. | |
3858 | ||
3859 | However, simplification is not vital; if you do not want to do this, | |
3860 | report the bug anyway and send us the entire test case you used. | |
3861 | ||
3862 | @item | |
3863 | A patch for the bug. | |
3864 | ||
3865 | A patch for the bug does help us if it is a good one. But do not omit | |
3866 | the necessary information, such as the test case, on the assumption that | |
3867 | a patch is all we need. We might see problems with your patch and decide | |
3868 | to fix the problem another way, or we might not understand it at all. | |
3869 | ||
de220cbd ILT |
3870 | Sometimes with a program as complicated as @code{ld} it is very hard to |
3871 | construct an example that will make the program follow a certain path | |
3872 | through the code. If you do not send us the example, we will not be | |
3873 | able to construct one, so we will not be able to verify that the bug is | |
3874 | fixed. | |
9fde46a4 ILT |
3875 | |
3876 | And if we cannot understand what bug you are trying to fix, or why your | |
3877 | patch should be an improvement, we will not install it. A test case will | |
3878 | help us to understand. | |
3879 | ||
3880 | @item | |
3881 | A guess about what the bug is or what it depends on. | |
3882 | ||
3883 | Such guesses are usually wrong. Even we cannot guess right about such | |
3884 | things without first using the debugger to find the facts. | |
3885 | @end itemize | |
3886 | ||
ec40bbb8 | 3887 | @node MRI |
2d59b2c3 RP |
3888 | @appendix MRI Compatible Script Files |
3889 | @cindex MRI compatibility | |
3890 | To aid users making the transition to @sc{gnu} @code{ld} from the MRI | |
3891 | linker, @code{ld} can use MRI compatible linker scripts as an | |
3892 | alternative to the more general-purpose linker scripting language | |
af54556a ILT |
3893 | described in @ref{Scripts}. MRI compatible linker scripts have a much |
3894 | simpler command set than the scripting language otherwise used with | |
3895 | @code{ld}. @sc{gnu} @code{ld} supports the most commonly used MRI | |
3896 | linker commands; these commands are described here. | |
2d59b2c3 | 3897 | |
867a1b8a DM |
3898 | In general, MRI scripts aren't of much use with the @code{a.out} object |
3899 | file format, since it only has three sections and MRI scripts lack some | |
3900 | features to make use of them. | |
3901 | ||
2d59b2c3 RP |
3902 | You can specify a file containing an MRI-compatible script using the |
3903 | @samp{-c} command-line option. | |
3904 | ||
3905 | Each command in an MRI-compatible script occupies its own line; each | |
3906 | command line starts with the keyword that identifies the command (though | |
3907 | blank lines are also allowed for punctuation). If a line of an | |
3908 | MRI-compatible script begins with an unrecognized keyword, @code{ld} | |
3909 | issues a warning message, but continues processing the script. | |
3910 | ||
3911 | Lines beginning with @samp{*} are comments. | |
3912 | ||
3913 | You can write these commands using all upper-case letters, or all | |
3914 | lower case; for example, @samp{chip} is the same as @samp{CHIP}. | |
3915 | The following list shows only the upper-case form of each command. | |
3916 | ||
3917 | @table @code | |
d4e5e3c3 | 3918 | @cindex @code{ABSOLUTE} (MRI) |
2d59b2c3 | 3919 | @item ABSOLUTE @var{secname} |
c653b370 | 3920 | @itemx ABSOLUTE @var{secname}, @var{secname}, @dots{} @var{secname} |
2d59b2c3 RP |
3921 | Normally, @code{ld} includes in the output file all sections from all |
3922 | the input files. However, in an MRI-compatible script, you can use the | |
3923 | @code{ABSOLUTE} command to restrict the sections that will be present in | |
3924 | your output program. If the @code{ABSOLUTE} command is used at all in a | |
3925 | script, then only the sections named explicitly in @code{ABSOLUTE} | |
3926 | commands will appear in the linker output. You can still use other | |
3927 | input sections (whatever you select on the command line, or using | |
7b015547 | 3928 | @code{LOAD}) to resolve addresses in the output file. |
2d59b2c3 | 3929 | |
2d59b2c3 | 3930 | @cindex @code{ALIAS} (MRI) |
d4e5e3c3 | 3931 | @item ALIAS @var{out-secname}, @var{in-secname} |
2d59b2c3 RP |
3932 | Use this command to place the data from input section @var{in-secname} |
3933 | in a section called @var{out-secname} in the linker output file. | |
3934 | ||
3935 | @var{in-secname} may be an integer. | |
3936 | ||
e54bf1c1 ILT |
3937 | @cindex @code{ALIGN} (MRI) |
3938 | @item ALIGN @var{secname} = @var{expression} | |
3939 | Align the section called @var{secname} to @var{expression}. The | |
3940 | @var{expression} should be a power of two. | |
3941 | ||
2d59b2c3 | 3942 | @cindex @code{BASE} (MRI) |
d4e5e3c3 | 3943 | @item BASE @var{expression} |
2d59b2c3 RP |
3944 | Use the value of @var{expression} as the lowest address (other than |
3945 | absolute addresses) in the output file. | |
3946 | ||
d4e5e3c3 | 3947 | @cindex @code{CHIP} (MRI) |
2d59b2c3 RP |
3948 | @item CHIP @var{expression} |
3949 | @itemx CHIP @var{expression}, @var{expression} | |
ec40bbb8 | 3950 | This command does nothing; it is accepted only for compatibility. |
2d59b2c3 | 3951 | |
2d59b2c3 | 3952 | @cindex @code{END} (MRI) |
d4e5e3c3 | 3953 | @item END |
2d59b2c3 RP |
3954 | This command does nothing whatever; it's only accepted for compatibility. |
3955 | ||
2d59b2c3 | 3956 | @cindex @code{FORMAT} (MRI) |
d4e5e3c3 | 3957 | @item FORMAT @var{output-format} |
2d59b2c3 RP |
3958 | Similar to the @code{OUTPUT_FORMAT} command in the more general linker |
3959 | language, but restricted to one of these output formats: | |
d4e5e3c3 | 3960 | |
2d59b2c3 RP |
3961 | @enumerate |
3962 | @item | |
3963 | S-records, if @var{output-format} is @samp{S} | |
3964 | ||
3965 | @item | |
3966 | IEEE, if @var{output-format} is @samp{IEEE} | |
3967 | ||
3968 | @item | |
3969 | COFF (the @samp{coff-m68k} variant in BFD), if @var{output-format} is | |
3970 | @samp{COFF} | |
3971 | @end enumerate | |
3972 | ||
2d59b2c3 | 3973 | @cindex @code{LIST} (MRI) |
d4e5e3c3 | 3974 | @item LIST @var{anything}@dots{} |
2d59b2c3 RP |
3975 | Print (to the standard output file) a link map, as produced by the |
3976 | @code{ld} command-line option @samp{-M}. | |
3977 | ||
ec40bbb8 DM |
3978 | The keyword @code{LIST} may be followed by anything on the |
3979 | same line, with no change in its effect. | |
2d59b2c3 | 3980 | |
d4e5e3c3 | 3981 | @cindex @code{LOAD} (MRI) |
2d59b2c3 | 3982 | @item LOAD @var{filename} |
c653b370 | 3983 | @itemx LOAD @var{filename}, @var{filename}, @dots{} @var{filename} |
2d59b2c3 RP |
3984 | Include one or more object file @var{filename} in the link; this has the |
3985 | same effect as specifying @var{filename} directly on the @code{ld} | |
3986 | command line. | |
3987 | ||
2d59b2c3 | 3988 | @cindex @code{NAME} (MRI) |
d4e5e3c3 | 3989 | @item NAME @var{output-name} |
2d59b2c3 RP |
3990 | @var{output-name} is the name for the program produced by @code{ld}; the |
3991 | MRI-compatible command @code{NAME} is equivalent to the command-line | |
3992 | option @samp{-o} or the general script language command @code{OUTPUT}. | |
3993 | ||
d4e5e3c3 | 3994 | @cindex @code{ORDER} (MRI) |
2d59b2c3 RP |
3995 | @item ORDER @var{secname}, @var{secname}, @dots{} @var{secname} |
3996 | @itemx ORDER @var{secname} @var{secname} @var{secname} | |
ec40bbb8 DM |
3997 | Normally, @code{ld} orders the sections in its output file in the |
3998 | order in which they first appear in the input files. In an MRI-compatible | |
3999 | script, you can override this ordering with the @code{ORDER} command. The | |
2d59b2c3 RP |
4000 | sections you list with @code{ORDER} will appear first in your output |
4001 | file, in the order specified. | |
4002 | ||
d4e5e3c3 | 4003 | @cindex @code{PUBLIC} (MRI) |
2d59b2c3 RP |
4004 | @item PUBLIC @var{name}=@var{expression} |
4005 | @itemx PUBLIC @var{name},@var{expression} | |
4006 | @itemx PUBLIC @var{name} @var{expression} | |
ec40bbb8 | 4007 | Supply a value (@var{expression}) for external symbol |
2d59b2c3 RP |
4008 | @var{name} used in the linker input files. |
4009 | ||
d4e5e3c3 | 4010 | @cindex @code{SECT} (MRI) |
2d59b2c3 RP |
4011 | @item SECT @var{secname}, @var{expression} |
4012 | @itemx SECT @var{secname}=@var{expression} | |
4013 | @itemx SECT @var{secname} @var{expression} | |
2d59b2c3 RP |
4014 | You can use any of these three forms of the @code{SECT} command to |
4015 | specify the start address (@var{expression}) for section @var{secname}. | |
4016 | If you have more than one @code{SECT} statement for the same | |
4017 | @var{secname}, only the @emph{first} sets the start address. | |
4018 | @end table | |
4019 | ||
ec40bbb8 | 4020 | @node Index |
2c5c0674 RP |
4021 | @unnumbered Index |
4022 | ||
4023 | @printindex cp | |
4024 | ||
4025 | @tex | |
4026 | % I think something like @colophon should be in texinfo. In the | |
4027 | % meantime: | |
4028 | \long\def\colophon{\hbox to0pt{}\vfill | |
4029 | \centerline{The body of this manual is set in} | |
4030 | \centerline{\fontname\tenrm,} | |
4031 | \centerline{with headings in {\bf\fontname\tenbf}} | |
4032 | \centerline{and examples in {\tt\fontname\tentt}.} | |
4033 | \centerline{{\it\fontname\tenit\/} and} | |
4034 | \centerline{{\sl\fontname\tensl\/}} | |
4035 | \centerline{are used for emphasis.}\vfill} | |
4036 | \page\colophon | |
c653b370 | 4037 | % Blame: doc@cygnus.com, 28mar91. |
2c5c0674 RP |
4038 | @end tex |
4039 | ||
4040 | ||
b4d4e8e3 | 4041 | @contents |
f22eee08 RP |
4042 | @bye |
4043 | ||
4044 |