Lines Matching refs:input
1 \input texinfo
296 specify other forms of binary input files using @samp{-l}, @samp{-R},
297 and the script command language. If @emph{no} binary input files at all
299 message @samp{No input files}.
398 @cindex binary input format
401 @cindex input format
402 @cindex input format
403 @item -b @var{input-format}
404 @itemx --format=@var{input-format}
407 @samp{-b} option to specify the binary format for input object files
411 default input format the most usual format on each machine.
412 @var{input-format} is a text string, the name of a particular format
420 @samp{-b @var{input-format}} before each group of object files in a
428 You can also define the input format from a script, using the command
510 match precisely any path used to specify the input file on the linker's
598 toolchain for specifying object-file format for both input and output
832 @cindex push state governing input file handling
835 flags which govern the input file handling so that they can all be
855 @cindex pop state governing input file handling
857 flags governing input file handling.
884 turn serve as input to @command{ld}. This is often called @dfn{partial
893 When an input file does not have the same format as the output file,
894 partial linking is only supported if that input file does not contain any
897 with input files in other formats at all.
903 @cindex symbol-only input
931 @cindex input files, displaying
934 Print the names of the input files as @command{ld} processes them.
981 turn serve as input to @command{ld}. When linking C++ programs, @samp{-Ur}
990 Creates a separate output section for every input section matching
992 missing, for every orphan input section. An orphan section is one not
995 input sections with the same name, overriding output section assignments
1160 @kindex --accept-unknown-input-arch
1161 @kindex --no-accept-unknown-input-arch
1162 @item --accept-unknown-input-arch
1163 @itemx --no-accept-unknown-input-arch
1164 Tells the linker to accept input files whose architecture cannot be
1166 and deliberately wants to link in these unknown input files. This was
1168 behaviour from release 2.14 onwards is to reject such input files, and
1169 so the @samp{--accept-unknown-input-arch} option has been added to
1306 input dynamic library. With @option{--copy-dt-needed-entries}
1416 Enable garbage collection of unused input sections. It is ignored on
1421 @samp{--gc-sections} decides which input sections are used by
1474 symbol tables of input files in memory. This option tells @command{ld} to
1548 Normally @command{ld} will give an error if you try to link together input
1719 of the input files.
1808 each input file when @var{size} is reached. @var{size} defaults to a
1820 input sections for redistribution, so if a single input section contains
1927 supported. Display which input files can and cannot be opened. Display
2060 alignment. Typically, the alignment will be set by an input section.
2863 @cindex default input format
2864 @code{GNUTARGET} determines the input-file object format if you don't
2866 of the BFD names for an input format (@pxref{BFD}). If there is no
2869 attempts to discover the input format by examining binary input files;
2910 the input files should be mapped into the output file, and to control
2926 You may also use linker scripts implicitly by naming them as input files
2950 The linker combines input files into a single output file. The output
2951 file and each input file are in a special data format known as an
2956 section in an input file as an @dfn{input section}; similarly, a section
2989 referenced in the input file will become an undefined symbol.
3030 your input files.
3060 after the output section name, you list the names of the input sections
3063 means all @samp{.text} input sections in all input files.
3153 @cindex input files in linker scripts
3154 @cindex input object files in linker scripts
3155 @cindex linker script input object files
3163 In fact, if you like, you can list all of your input files in the linker
3187 @cindex grouping input files
3231 @cindex first input file
3233 that @var{filename} will become the first input file to be linked, as
3277 @cindex input file format in linker script
3278 The @code{TARGET} command names the BFD format to use when reading input
3486 linker has mapped input sections to output sections. Prior to the
3490 of the script. In particular, input section assignments will be made
3521 @code{NOCROSSREFS} command uses output section names, not input section
3613 the last @samp{.text} input section. The symbol @samp{_bdata} will be
3790 The @code{SECTIONS} command tells the linker how to map input sections
3826 linker will place each input section into an identically named output
3828 input files. If all input sections are present in the first file, for
3830 in the first input file. The first section will be at address zero.
3876 an input section description (@pxref{Input Section})
3912 alignment requirement is the strictest alignment of any input section
3954 input sections.
3973 @cindex input sections
3974 @cindex mapping input sections to output sections
3975 The most common output section command is an input section description.
3977 The input section description is the most basic linker script operation.
3979 in memory. You use input section descriptions to tell the linker how to
3980 map the input files into your memory layout.
3992 @cindex input section basics
3993 An input section description consists of a file name optionally followed
3999 The most common input section description is to include all input
4001 include all input @samp{.text} sections, you would write:
4023 @samp{.rdata} input sections will appear in the output section. In the
4025 they are found in the linker input. In the second example, all
4026 @samp{.text} input sections will appear first, followed by all
4027 @samp{.rdata} input sections.
4037 of an input section, INPUT_SECTION_FLAGS may be used.
4051 input section matching the name *(.text) whose section header flags
4053 @samp{.text2} will be comprised of any input section matching the name *(.text)
4080 the input file will be included in the output section. This is not
4090 did not, the linker will attempt to open the file as an input file, as
4097 @cindex input section wildcards
4101 In an input section description, either the file name or the section
4136 sequence of input section descriptions is probably in error, because the
4173 It will sort the input sections by name first, then by alignment if two
4177 It will sort the input sections by alignment first, then by name if two
4215 If you ever get confused about where input sections are going, use the
4217 precisely how input sections are mapped to output sections.
4241 file formats common symbols do not have a particular input section. The
4242 linker treats common symbols as though they are in an input section
4246 other input sections. You can use this to place common symbols from a
4247 particular input file in one section while common symbols from other
4248 input files are placed in another section.
4250 In most cases, common symbols in input files will be placed in the
4278 This is accomplished by surrounding an input section's wildcard entry
4359 endianness of the first input object file.
4377 gaps left due to the required alignment of input sections) are filled
4404 @cindex input filename symbols
4407 The command tells the linker to create a symbol for each input file.
4408 The name of each symbol will be the name of the corresponding input
4484 This is for convenience when referring to input sections that may or
4485 may not be present in any of the input files. For example:
4491 @samp{.foo} section in at least one input file, and if the input
4508 input sections. Any input sections which are assigned to an output
4570 the input sections which map into it. You can override this by using
4688 @cindex forcing input section alignment
4689 @cindex input section alignment
4690 You can force input section alignment within an output section by using
4691 SUBALIGN. The value specified overrides any alignment given by input
4700 of its input sections are read-only or all of its input sections are
4749 alignment of input sections) will be filled with the value, repeated as
4926 whether to use a particular memory region for an input section which is
4928 @ref{SECTIONS}, if you do not specify an output section for some input
4930 the input section. If you define region attributes, the linker will use
5472 Orphan sections are sections present in the input files which
5559 the @samp{.text} input sections to fill this area. (If there is too
5563 the values from the @samp{.data} input sections and before the end of
5584 If the linker needs to place some input section, e.g. @code{.rodata},
5913 input sections:
6128 If you specify a linker input file which the linker can not recognize as
6139 Any input files read because of an implicit linker script will be read
6294 incompatible instructions in the input files. It also modifies the
6582 from the input sections.
6639 stub sections located between groups of input sections.
6640 @samp{--stub-group-size} specifies the maximum size of a group of input
6642 a stub section may serve two groups of input sections, one group before
6645 prediction) that stub sections only serve one group of input sections.
6649 @command{ld} to automatically size input section groups for the branch types
6653 Note that @samp{--stub-group-size} does not split input sections. A
6654 single input section larger than the group size specified will of course
6655 create a larger group (of one section). If input sections are too
6683 output file. All GOT references from a single input object
6684 file access the same GOT, but references from different input object
6856 be reachable if an input section and its associated call trampolines are
6889 section boundaries, so may not themselves be reachable if an input
6905 PLT, if all input files (including startup and static libraries) were
6966 by @command{ld} in stub sections located between groups of input sections.
6967 @samp{--stub-group-size} specifies the maximum size of a group of input
6969 a stub section may serve two groups of input sections, one group before
6972 prediction) that stub sections only serve one group of input sections.
6976 @command{ld} to automatically size input section groups for the branch types
6980 Note that @samp{--stub-group-size} does not split input sections. A
6981 single input section larger than the group size specified will of course
6982 create a larger group (of one section). If input sections are too
7054 calls. @command{ld} does not split apart input sections, so cannot
7055 help if a single input file has a @code{.toc} section that exceeds
7837 If the linker gets a fatal signal, for any input whatever, that is a
7840 @cindex error on valid input
7842 If @command{ld} produces an error message for valid input, that is a bug.
7844 @cindex invalid input
7846 If @command{ld} does not produce an error message for invalid input, that
7929 A complete input file, or set of input files, that will reproduce the
7980 which changes to the input file will make the bug go away and which
8056 the input files. However, in an MRI-compatible script, you can use the
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}
8132 order in which they first appear in the input files. In an MRI-compatible
8142 @var{name} used in the linker input files.