Lines Matching refs:command
206 @command{ld} combines a number of object and archive files, relocates
208 compiling a program is to run @command{ld}.
210 @command{ld} accepts Linker Command Language files written in
216 This man page does not describe the command language; see the
217 @command{ld} entry in @code{info} for full details on the command
222 This version of @command{ld} uses the general purpose BFD libraries
223 to operate on object files. This allows @command{ld} to read, combine, and
232 @command{ld} continues executing, allowing you to identify other errors
242 The @sc{gnu} linker @command{ld} is meant to cover a broad range of situations,
258 @cindex command line
263 The linker supports a plethora of command-line options, but in actual
266 For instance, a frequent use of @command{ld} is to link standard Unix
274 This tells @command{ld} to produce a file called @var{output} as the
279 Some of the command-line options to @command{ld} may be specified at any
280 point in the command line. However, options which refer to files, such
282 which the option appears in the command line, relative to the object
285 occurrences (those further to the left on the command line) of that
291 together. They may follow, precede, or be mixed in with command-line
297 and the script command language. If @emph{no} binary input files at all
311 the @code{INSERT} command. @xref{Scripts}.
335 (e.g. @samp{gcc}) then all the linker command line options should be
355 Here is a table of the generic command line switches accepted by the GNU
386 In the current release of @command{ld}, this option is useful only for the
387 Intel 960 family of architectures. In that @command{ld} configuration, the
390 archive-library search path. @xref{i960,,@command{ld} and the Intel 960
393 Future releases of @command{ld} may support similar functionality for
405 @command{ld} may be configured to support more than one kind of object
406 file. If your @command{ld} is configured this way, you can use the
408 that follow this option on the command line. Even when @command{ld} is
410 to specify this, as @command{ld} should be configured to expect as a
428 You can also define the input format from a script, using the command
440 For compatibility with linkers produced by MRI, @command{ld} accepts script
441 files written in an alternate, restricted command language, described in
450 scripts written in the general-purpose @command{ld} scripting language.
451 If @var{MRI-cmdfile} does not exist, @command{ld} looks for it in the directories
464 script command @code{FORCE_COMMON_ALLOCATION} has the same effect.
478 @cindex entry point, from command line
508 used by @command{ld} to open the files; for archive members, this is simply
511 command-line. This option is available only for the i386 PE targeted port
578 will be created in the order in which they appear on the command line.
603 @code{TARGET} command in linker scripts, and the @code{GNUTARGET}
662 If @var{namespec} is of the form @file{:@var{filename}}, @command{ld}
666 On systems which support shared libraries, @command{ld} may also search for
668 and SunOS systems, @command{ld} will search a directory for a library
676 specified on the command line. If the archive defines a symbol which
678 command line, the linker will include the appropriate file(s) from the
680 the command line will not cause the linker to search the archive again.
685 You may list the same archive multiple times on the command line.
689 if you are using @command{ld} on AIX, note that it is different from the
698 Add path @var{searchdir} to the list of paths that @command{ld} will search
699 for archive libraries and @command{ld} control scripts. You may use this
701 in which they are specified on the command line. Directories specified
702 on the command line are searched before the default directories. All
705 how @command{ld} searches for a linker script unless @option{-T}
714 @samp{-L}) depends on which emulation mode @command{ld} is using, and in
719 @code{SEARCH_DIR} command. Directories specified this way are searched
720 at the point in which the linker script appears in the command line.
816 Use @var{output} as the name for the program produced by @command{ld}; if this
818 script command @code{OUTPUT} can also specify the output file name.
823 If @var{level} is a numeric values greater than zero @command{ld} optimizes
884 turn serve as input to @command{ld}. This is often called @dfn{partial
934 Print the names of the input files as @command{ld} processes them.
942 @command{ld}'s default linker script (rather than adding to it), so
958 command line has been processed. This allows options placed after the
959 @option{--default-script} option on the command line to affect the
961 command line cannot be directly controlled by the user. (eg because
962 the command line is being constructed by another tool, such as
974 option is equivalent to the @code{EXTERN} linker script command.
981 turn serve as input to @command{ld}. When linking C++ programs, @samp{-Ur}
994 multiple times on the command line; It prevents the normal merging of
1005 Display the version number for @command{ld}. The @option{-V} option also
1149 the order that it is specified on the command line. If a symbol in that
1151 object in an archive that appears later on the command line, the linker
1177 on the command line after the @option{--as-needed} option. Normally
1179 on the command line, regardless of whether the library is actually
1185 Object files or libraries appearing on the command line @emph{after}
1213 multiple times on the command line: it affects library searching for
1235 may use this option multiple times on the command line: it affects
1293 restored by using the command line switch @option{--check-sections}.
1304 command line. Normally the linker won't add a DT_NEEDED tag to the
1307 specified on the command line however any dynamic libraries that
1313 mentioned on the command line will be recursively searched, following
1339 The script command @code{INHIBIT_COMMON_ALLOCATION} has the same effect.
1353 @cindex symbols, from command line
1358 times as necessary to define multiple symbols in the command line. A
1363 using the linker command language from a script (@pxref{Assignments,,
1368 @cindex demangling, from command line
1383 @cindex dynamic linker, from command line
1419 @samp{--no-gc-sections} on the command line.
1424 command-line will be kept, as will sections containing symbols
1434 a @code{ENTRY} command in the linker script.
1445 be restored by specifying @samp{--no-print-gc-sections} on the command
1452 other command-line options). This is the string that would appear
1453 in an @code{OUTPUT_FORMAT} linker script command (@pxref{File Commands}).
1459 Print a summary of the command-line options on the standard output and exit.
1473 @command{ld} normally optimizes for speed over memory usage by caching the
1474 symbol tables of input files in memory. This option tells @command{ld} to
1476 necessary. This may be required if @command{ld} runs out of memory space
1548 Normally @command{ld} will give an error if you try to link together input
1551 This option tells @command{ld} that it should silently permit such possible
1558 Normally @command{ld} will give a warning if it finds an incompatible
1577 command line. Library directories specified in linker scripts
1578 (including linker scripts specified on the command line) are ignored.
1583 @command{ld} may be configured to support more than one kind of object
1584 file. If your @command{ld} is configured this way, you can use the
1586 object file. Even when @command{ld} is configured to support alternative
1587 object formats, you don't usually need to specify this, as @command{ld}
1592 command @code{OUTPUT_FORMAT} can also specify the output format, but
1627 @xref{H8/300,,@command{ld} and the H8/300}.
1630 @xref{i960,, @command{ld} and the Intel 960 family}.
1633 @xref{Xtensa,, @command{ld} and Xtensa Processors}.
1636 @xref{M68HC11/68HC12,,@command{ld} and the 68HC11 and 68HC12}.
1639 @xref{Nios II,,@command{ld} and the Altera Nios II}.
1642 @xref{PowerPC ELF32,,@command{ld} and PowerPC 32-bit ELF Support}.
1683 You may only specify @samp{--retain-symbols-file} once in the command
1788 This option tells @command{ld} to sort the common symbols by alignment in
1838 For some targets, the output of @command{ld} is different in some ways from
1839 the output of some existing linker. This switch requests @command{ld} to
1843 For example, on SunOS, @command{ld} combines duplicate entries in the
1847 trouble). The @samp{--traditional-format} switch tells @command{ld} to not
1854 times as necessary to locate multiple sections in the command
1912 command line.
1926 Display the version number for @command{ld} and list the linker emulations
2062 is, if the @code{SECTIONS} command does not specify a start address for
2087 For each archive mentioned on the command line after the
2211 @code{--build-id} options earlier on the command line.
2242 @code{*.def} files, which may be specified on the linker command line
2248 support additional command line options that are specific to the i386
2290 option is specified on the command-line, @command{ld} will enable long
2855 You can change the behaviour of @command{ld} with the environment variables
2867 @code{GNUTARGET} in the environment, @command{ld} uses the natural format
2905 @cindex command files
2907 written in the linker command language.
2918 linker executable. You can use the @samp{--verbose} command line option
2919 to display the default linker script. Certain command line options,
2922 You may supply your own linker script by using the @samp{-T} command
3000 You write a linker script as a series of commands. Each command is
3021 The simplest possible linker script has just one command:
3022 @samp{SECTIONS}. You use the @samp{SECTIONS} command to describe the
3025 The @samp{SECTIONS} command is a powerful command. Here we will
3046 You write the @samp{SECTIONS} command as the keyword @samp{SECTIONS},
3050 The first line inside the @samp{SECTIONS} command of the above example
3056 @samp{SECTIONS} command, the location counter has the value @samp{0}.
3109 point}. You can use the @code{ENTRY} linker script command to set the
3120 the @samp{-e} @var{entry} command-line option;
3122 the @code{ENTRY(@var{symbol})} command in a linker script;
3156 The @code{INPUT} command directs the linker to include the named files
3157 in the link, as though they were named on the command line.
3160 a link, but you can't be bothered to put it on every link command line,
3176 If you use @samp{INPUT (-l@var{file})}, @command{ld} will transform the
3177 name to @code{lib@var{file}.a}, as with the command line argument
3180 When you use the @code{INPUT} command in an implicit linker script, the
3188 The @code{GROUP} command is like @code{INPUT}, except that the named
3208 The @code{OUTPUT} command names the output file. Using
3210 @samp{-o @var{filename}} on the command line (@pxref{Options,,Command
3211 Line Options}). If both are used, the command line option takes
3214 You can use the @code{OUTPUT} command to define a default name for the
3222 The @code{SEARCH_DIR} command adds @var{path} to the list of paths where
3223 @command{ld} looks for archive libraries. Using
3225 on the command line (@pxref{Options,,Command Line Options}). If both
3227 the command line option are searched first.
3232 The @code{STARTUP} command is just like the @code{INPUT} command, except
3234 though it were specified first on the command line. This may be useful
3249 The @code{OUTPUT_FORMAT} command names the BFD format to use for the
3251 exactly like using @samp{--oformat @var{bfdname}} on the command line
3252 (@pxref{Options,,Command Line Options}). If both are used, the command
3256 formats based on the @samp{-EB} and @samp{-EL} command line options.
3266 command:
3271 @samp{elf32-bigmips}, but if the user uses the @samp{-EL} command line
3278 The @code{TARGET} command names the BFD format to use when reading input
3280 This command is like using @samp{-b @var{bfdname}} on the command line
3281 (@pxref{Options,,Command Line Options}). If the @code{TARGET} command
3283 command is also used to set the format for the output file. @xref{BFD}.
3294 @ref{MEMORY} command. Each name corresponds to at most one memory region.
3323 The goal is to provide a linker command file that contains a system independent
3461 command has the same effect as the @samp{-u} command-line option.
3466 This command has the same effect as the @samp{-d} command-line option:
3467 to make @command{ld} assign space to common symbols even if a relocatable
3473 This command has the same effect as the @samp{--no-define-common}
3474 command-line option: to make @code{ld} omit the assignment of addresses
3480 This command is typically used in a script specified by @samp{-T} to
3509 This command may be used to tell @command{ld} to issue an error about any
3518 The @code{NOCROSSREFS} command takes a list of output section names. If
3519 @command{ld} detects any cross references between the sections, it reports
3521 @code{NOCROSSREFS} command uses output section names, not input section
3537 This command may be used to modify @command{ld} behavior. If
3581 may only use this within a @code{SECTIONS} command. @xref{Location Counter}.
3588 statements within a @code{SECTIONS} command, or as part of an output
3589 section description in a @code{SECTIONS} command.
3790 The @code{SECTIONS} command tells the linker how to map input sections
3793 The format of the @code{SECTIONS} command is:
3797 @var{sections-command}
3798 @var{sections-command}
3803 Each @var{sections-command} may of be one of the following:
3807 an @code{ENTRY} command (@pxref{Entry Point,,Entry command})
3816 The @code{ENTRY} command and symbol assignments are permitted inside the
3817 @code{SECTIONS} command for convenience in using the location counter in
3825 If you do not use a @code{SECTIONS} command in your linker script, the
3855 @var{output-section-command}
3856 @var{output-section-command}
3867 the next @var{sections-command} looks like a continuation of the expression.
3870 Each @var{output-section-command} may be one of the following:
3924 If the MEMORY command has been used to create a list of memory
3975 The most common output section command is an input section description.
4077 command.
4089 name on the linker command line or in an @code{INPUT} command. If you
4091 though it appeared on the command line. Note that this differs from an
4092 @code{INPUT} command, because the linker will not search for the file in
4130 specified on the command line or in an @code{INPUT} command. The linker
4189 When both command line section sorting option and linker script
4190 section sorting command are used, section sorting command always
4191 takes precedence over the command line option.
4193 If the section sorting command in linker script isn't nested, the
4194 command line option will make the section sorting command to be
4195 treated as nested sorting command.
4208 If the section sorting command in linker script is nested, the
4209 command line option will be ignored.
4212 @code{SORT_NONE} disables section sorting by ignoring the command line
4332 an output section command. Each keyword is followed by an expression in
4374 You may use the @code{FILL} command to set the fill pattern for the
4390 The @code{FILL} command is similar to the @samp{=@var{fillexp}} output
4392 part of the section following the @code{FILL} command, rather than the
4393 entire section. If both are used, the @code{FILL} command takes
4407 The command tells the linker to create a symbol for each input file.
4410 the @code{CREATE_OBJECT_SYMBOLS} command appears.
4424 For these object file formats, the @code{CONSTRUCTORS} command tells the
4426 @code{CONSTRUCTORS} command appears. The @code{CONSTRUCTORS} command is
4466 command, use @samp{SORT_BY_NAME(CONSTRUCTORS)} instead. When using the
4525 @var{output-section-command}
4526 @var{output-section-command}
4533 @var{output-section-command}. In this section we will describe the
4758 You can also change the fill value with a @code{FILL} command in the
4780 Overlays are described using the @code{OVERLAY} command. The
4781 @code{OVERLAY} command is used within a @code{SECTIONS} command, like an
4783 command is as follows:
4790 @var{output-section-command}
4791 @var{output-section-command}
4796 @var{output-section-command}
4797 @var{output-section-command}
4813 the next @var{sections-command} looks like a continuation of the expression.
4869 Note that the @code{OVERLAY} command is just syntactic sugar, since
4893 memory. You can override this by using the @code{MEMORY} command.
4895 The @code{MEMORY} command describes the location and size of blocks of
4904 command. However, you can define as many blocks of memory within it as
4920 must have a distinct name within the @code{MEMORY} command. However you can
4922 command.
5033 precisely. You may use the @code{PHDRS} command for this purpose. When
5034 the linker sees the @code{PHDRS} command in the linker script, it will
5037 The linker only pays attention to the @code{PHDRS} command when
5041 This is the syntax of the @code{PHDRS} command. The words @code{PHDRS},
5054 The @var{name} is used only for reference in the @code{SECTIONS} command
5126 @code{AT} command used as an output section attribute (@pxref{Output
5127 Section LMA}). The @code{AT} command for a program header overrides the
5181 The syntax of the @code{VERSION} command is simply
5502 within a @code{SECTIONS} command. The @code{.} symbol may appear
6064 use the @code{MEMORY} command to define discontinuous memory for the
6074 value has already been given for this segment (with a command-line
6076 will be @var{default}. At present, the @samp{-T} command-line option
6122 command (@pxref{PHDRS}).
6140 at the position in the command line where the implicit linker script was
6148 @command{ld} has additional features on some platforms; the following
6149 sections describe them. Machines where @command{ld} has no additional
6154 * H8/300:: @command{ld} and the H8/300
6157 * i960:: @command{ld} and the Intel 960 family
6163 * ARM:: @command{ld} and the ARM family
6166 * HPPA ELF32:: @command{ld} and HPPA 32-bit ELF
6169 * M68K:: @command{ld} and the Motorola 68K family
6172 * MIPS:: @command{ld} and the MIPS family
6175 * MMIX:: @command{ld} and MMIX
6178 * MSP430:: @command{ld} and MSP430
6181 * NDS32:: @command{ld} and NDS32
6184 * Nios II:: @command{ld} and the Altera Nios II
6187 * PowerPC ELF32:: @command{ld} and PowerPC 32-bit ELF Support
6190 * PowerPC64 ELF64:: @command{ld} and PowerPC64 64-bit ELF Support
6193 * SPU ELF:: @command{ld} and SPU ELF Support
6196 * TI COFF:: @command{ld} and TI COFF
6199 * WIN32:: @command{ld} and WIN32 (cygwin/mingw)
6202 * Xtensa:: @command{ld} and Xtensa Processors
6213 @section @command{ld} and the H8/300
6216 For the H8/300, @command{ld} can perform these global optimizations when
6217 you specify the @samp{--relax} command-line option.
6222 @command{ld} finds all @code{jsr} and @code{jmp} instructions whose
6230 @command{ld} finds all @code{mov.b} instructions which use the
6237 @command{ld} finds all @code{mov} instructions which use the register
6246 @command{ld} finds all bit manipulation instructions like @code{band, bclr,
6255 @command{ld} finds all @code{ldc.w, stc.w} instructions which use the
6273 @chapter @command{ld} and Other Renesas Chips
6275 @command{ld} also supports the Renesas (formerly Hitachi) H8/300H,
6276 H8/500, and SH chips. No special features, commands, or command-line
6287 @section @command{ld} and the Intel 960 Family
6291 You can use the @samp{-A@var{architecture}} command line option to
6299 For example, if your @command{ld} command line included @w{@samp{-ACA}} as
6317 You can meaningfully use @samp{-A} more than once on a command line, since
6324 @command{ld} supports the @samp{--relax} option for the i960 family. If
6325 you specify @samp{--relax}, @command{ld} finds all @code{balx} and
6328 instructions, respectively. @command{ld} also turns @code{cal}
6349 @section @command{ld} and the Motorola 68HC11 and 68HC12 families
6355 For the Motorola 68HC11, @command{ld} can perform these global
6356 optimizations when you specify the @samp{--relax} command-line option.
6361 @command{ld} finds all @code{jsr} and @code{jmp} instructions whose
6366 @command{ld} also looks at all 16-bit extended addressing modes and
6371 When @command{gcc} is called with @option{-mrelax}, it can emit group
6382 For 68HC11 and 68HC12, @command{ld} can generate trampoline code to
6395 @section @command{ld} and the ARM family
6399 For the ARM, @command{ld} will generate code stubs to allow functions calls
6401 been compiled and assembled with the @samp{-mthumb-interwork} command
6404 option then the @samp{--support-old-code} command line switch should be
6428 The @samp{--be8} switch instructs @command{ld} to generate BE8 format
6566 controlled by the command line option @option{--stub-group-size=N}.
6627 @section @command{ld} and HPPA 32-bit ELF Support
6630 When generating a shared library, @command{ld} will by default generate
6632 The @samp{--multi-subspace} switch causes @command{ld} to generate export
6638 Long branch stubs and import/export stubs are placed by @command{ld} in
6649 @command{ld} to automatically size input section groups for the branch types
6669 @section @command{ld} and the Motorola 68K family
6698 @section @command{ld} and the MIPS family
6844 @section @command{ld} and the Altera Nios II
6850 which may result in @command{ld} giving
6852 The command-line option @option{--relax} enables the generation of
6881 @section @command{ld} and PowerPC 32-bit ELF Support
6885 displacement, which may result in @command{ld} giving
6904 @command{ld} will generate this layout, including stubs to access the
6911 @command{ld} will use the new PLT and GOT layout if it is linking new
6936 This option causes @command{ld} to label linker stubs with a local
6942 PowerPC @command{ld} normally performs some optimization of code
6958 @section @command{ld} and PowerPC64 64-bit ELF Support
6966 by @command{ld} in stub sections located between groups of input sections.
6976 @command{ld} to automatically size input section groups for the branch types
6988 This option causes @command{ld} to label linker stubs with a local
6995 These two options control how @command{ld} interprets version patterns
7008 PowerPC64 @command{ld} normally performs some optimization of code
7015 PowerPC64 @command{ld} normally removes @code{.opd} section entries
7031 PowerPC64 @command{ld} normally removes unused @code{.toc} section
7051 total TOC size to 64K. PowerPC64 @command{ld} extends this limit by
7054 calls. @command{ld} does not split apart input sections, so cannot
7056 64K, most likely from linking multiple files with @command{ld -r}.
7062 By default, @command{ld} sorts TOC sections so that those whose file
7117 @section @command{ld} and SPU ELF Support
7130 Normally, @command{ld} recognizes calls to functions within overlay
7132 @command{ld} also provides a built-in overlay manager. This option
7138 This option causes @command{ld} to label overlay stubs with a local
7144 This option causes @command{ld} to add overlay call stubs on all
7151 @command{ld} usually checks that a final executable for SPU fits in
7161 @command{ld} will provide an estimate of maximum stack usage.
7162 @command{ld} does this by examining symbols in code sections to
7178 in @command{ld} emitting stack sizing symbols for each function.
7198 @section @command{ld}'s Support for Various TI COFF Versions
7204 format; @command{ld} will read any version or byte order, but the output
7218 @section @command{ld} and WIN32 (cygwin/mingw)
7220 This section describes some of the win32 specific @command{ld} issues.
7222 command line options mentioned here.
7230 archive. The cygwin and mingw ports of @command{ld} have specific
7232 @samp{--out-implib} command line option.
7236 The cygwin/mingw @command{ld} has several ways to export symbols for dll's.
7241 By default @command{ld} exports symbols with the auto-export functionality,
7242 which is controlled by the following command line options:
7252 When auto-export is in operation, @command{ld} will export all the non-local
7256 private functions that are not part of any public interface, the command-line
7262 command line, then the default auto-export behavior will be @emph{disabled}
7276 command line. The file's name must end in @samp{.def} or @samp{.DEF}.
7310 The optional @code{LIBRARY <name>} command indicates the @emph{internal}
7315 library, the @code{NAME <name>} command should be used instead of
7325 filename specified on the command line.
7375 While linking a shared dll, @command{ld} is able to create a DEF file
7376 with the @samp{--output-def <file>} command line option.
7424 command-line option, although it is enabled by default on cygwin/mingw.
7463 The cygwin/mingw ports of @command{ld} support the direct linking,
7467 libraries or applications. When @command{ld} creates an import lib, each
7474 Linking directly to a dll uses no extra command-line switches other than
7475 @samp{-L} and @samp{-l}, because @command{ld} already searches for a number
7497 where @samp{<prefix>} is set by the @command{ld} option
7636 unless the @samp{--export-all-symbols} command line option is used.
7671 by @command{ld} and respected when laying out the common symbols. Native
7692 The default @command{ld} behavior for Xtensa processors is to interpret
7696 example, with the command:
7708 @command{ld} may interleave some of the @code{.literal}
7718 Relaxation is enabled by default for the Xtensa version of @command{ld} and
7744 The following Xtensa-specific command-line options can be used to
7807 @cindex bugs in @command{ld}
7808 @cindex reporting bugs in @command{ld}
7810 Your bug reports play an essential role in making @command{ld} reliable.
7814 to help the entire community by making the next version of @command{ld}
7816 @command{ld}.
7838 @command{ld} bug. Reliable linkers never crash.
7842 If @command{ld} produces an error message for valid input, that is a bug.
7846 If @command{ld} does not produce an error message for invalid input, that
7852 improvement of @command{ld} are welcome in any case.
7858 @cindex @command{ld} bugs, reporting
7861 products. If you obtained @command{ld} from a support organization, we
7869 Otherwise, send bug reports for @command{ld} to
7901 The version of @command{ld}. @command{ld} announces it if you start it with
7905 the bug in the current version of @command{ld}.
7908 Any patches you may have applied to the @command{ld} source, including any
7916 What compiler (and its version) was used to compile @command{ld}---e.g.
7920 The command arguments you gave the linker to link your example and
7948 Of course, if the bug is that @command{ld} gets a fatal signal, then we
7955 copy of @command{ld} is out of sync, or you have encountered a bug in the
7963 If you wish to suggest changes to the @command{ld} source, send us context
7966 If you even discuss something in the @command{ld} source, refer to it by
8004 Sometimes with a program as complicated as @command{ld} it is very hard to
8024 To aid users making the transition to @sc{gnu} @command{ld} from the MRI
8025 linker, @command{ld} can use MRI compatible linker scripts as an
8028 simpler command set than the scripting language otherwise used with
8029 @command{ld}. @sc{gnu} @command{ld} supports the most commonly used MRI
8037 @samp{-c} command-line option.
8039 Each command in an MRI-compatible script occupies its own line; each
8040 command line starts with the keyword that identifies the command (though
8042 MRI-compatible script begins with an unrecognized keyword, @command{ld}
8049 The following list shows only the upper-case form of each command.
8055 Normally, @command{ld} includes in the output file all sections from all
8057 @code{ABSOLUTE} command to restrict the sections that will be present in
8058 your output program. If the @code{ABSOLUTE} command is used at all in a
8061 input sections (whatever you select on the command line, or using
8066 Use this command to place the data from input section @var{in-secname}
8084 This command does nothing; it is accepted only for compatibility.
8088 This command does nothing whatever; it's only accepted for compatibility.
8092 Similar to the @code{OUTPUT_FORMAT} command in the more general linker
8110 @command{ld} command-line option @samp{-M}.
8119 same effect as specifying @var{filename} directly on the @command{ld}
8120 command line.
8124 @var{output-name} is the name for the program produced by @command{ld}; the
8125 MRI-compatible command @code{NAME} is equivalent to the command-line
8126 option @samp{-o} or the general script language command @code{OUTPUT}.
8131 Normally, @command{ld} orders the sections in its output file in the
8133 script, you can override this ordering with the @code{ORDER} command. The
8148 You can use any of these three forms of the @code{SECT} command to