Lines Matching full:will
104 which will come from the standard search directories. (See the
112 argument will either have no further effect, or override prior
128 If the linker cannot recognize the format of an object file, it will
175 exist, or cannot be read, then the option will be treated
183 additional @FILE options; any such options will be processed
252 symbol named ENTRY, the linker will try to parse ENTRY as a number,
253 and use that as the entry address (the number will be interpreted
267 option will be treated as hidden.
275 If you do not use this option, the dynamic symbol table will
281 dynamic object, then you will probably need to use this option when
303 you run the program, the dynamic linker will see the DT_AUXILIARY
305 object, it will first check whether there is a definition in the
306 shared object NAME. If there is one, it will be used instead of
313 entries will be created in the order in which they appear on the
325 you run the program, the dynamic linker will see the DT_FILTER
326 field. The dynamic linker will resolve symbols according to the
327 symbol table of the filter object as usual, but it will actually
337 environment variable. The GNU linker will ignore the `-F' option
362 executable is run the dynamic linker will attempt to load the
379 If NAMESPEC is of the form `:FILENAME', `ld' will search the
380 library path for a file called FILENAME, otherise it will search
385 systems, `ld' will search a directory for a library called
391 The linker will search an archive only once, at the location where
394 the archive on the command line, the linker will include the
396 symbol in an object appearing later on the command line will not
410 Add path SEARCHDIR to the list of paths that `ld' will search for
418 If SEARCHDIR begins with `=', then the `=' will be replaced by the
459 circumstances the linker will display the final value
467 will produce the following output in the link map if the `-M'
662 It marks the object so that its runtime initialization will
665 runtime finalization of the object will occur after the
693 object will ignore any default library search paths.
765 Normally, the linker will add a DT_NEEDED tag for each dynamic
777 after the `--no-add-needed' option. Normally, the linker will add
779 `--no-add-needed' causes DT_NEEDED tags will never be emitted for
859 linker will perform this check, and if it finds any overlaps it
860 will produce suitable error messages. The linker does know about,
915 demangling style for your compiler. The linker will demangle by
950 will be kept, as will sections containing symbols referenced by
1000 Normally when a symbol is defined multiple times, the linker will
1002 the first definition will be used.
1024 Normally when a symbol has an undefined version, the linker will
1026 and a fatal error will be issued instead.
1037 Normally `ld' will give an error if you try to link together input
1046 Normally `ld' will give a warning if it finds an incompatible
1055 Normally, the linker will not produce an output file if it
1137 variable `LD_RUN_PATH' will be used if it is defined.
1140 SunOS, the linker will form a runtime search patch out of all the
1142 runtime search path will be formed exclusively using the `-rpath'
1157 non-shared, non-relocatable link, it will automatically try to
1203 If the required shared library is not found, the linker will issue
1209 XCOFF and SunOS platforms. On SunOS, the linker will
1223 This option will apply `SORT_BY_NAME' to all wildcard section
1227 This option will apply `SORT_BY_ALIGNMENT' to all wildcard section
1241 relocations in a single section. Note that this will fail to work
1243 The linker will not split up individual input sections for
1245 COUNT relocations one output section will contain that many
1309 Normally the linker will generate an error message for each
1360 symbols will be a common symbol.
1419 alignment. Typically, the alignment will be set by an input
1420 section. The address will only be changed if it not explicitly
1429 option `--unresolved-symbols') it will normally generate an error.
1447 list of archives, because gcc will add its own list of archives to
1452 SYMBOL will be resolved to `__wrap_SYMBOL'. Any undefined
1453 reference to `__real_SYMBOL' will be resolved to SYMBOL.
1469 all calls to `malloc' will call the function `__wrap_malloc'
1470 instead. The call to `__real_malloc' in `__wrap_malloc' will call
1474 links without the `--wrap' option will succeed. If you do this,
1487 `--enable-new-dtags', the dynamic tags will be created as needed.
1488 If you specify `--disable-new-dtags', no new dynamic tags will be
1533 the same in an identical output file, but will be unique among all
1559 If given, symbols with a stdcall suffix (@NN) will be exported
1575 If the link finds a symbol that it cannot resolve, it will attempt
1578 and will resolve that symbol by linking to the match. For
1593 will be exported by the DLL. Note that this is the default if
1598 `DllEntryPoint@0', `DllMainCRTStartup@12', and `impure_ptr' will
1600 DLLs will not be re-exported, nor will symbols specifying the
1603 `libstd++', `libmingw32', or `crtX.o' will be exported. Symbols
1604 whose names begin with `__rtti_' or `__builtin_' will not be
1622 Specify the file alignment. Sections in the file will always
1636 lowest memory location that will be used when your program or dll
1644 If given, the stdcall suffixes (@NN) will be stripped from symbols
1686 The linker will create the file FILE which will contain a DEF file
1694 The linker will create the file FILE which will contain an import
1729 of the 'auto-import' extension will cause the text section of the
1733 Note - use of the 'auto-import' extension will also cause read only
1739 Using 'auto-import' generally will 'just work' - but sometimes you
1752 data type of the offending exported variable, ld will always
1797 building client code that will link to the DLL, or merely
1853 switch will create a vector of 'runtime pseudo relocations' which
1869 Sets the section alignment. Sections in memory will always begin
1884 Specifies the subsystem under which your program will execute. The
1951 Normally, the linker will default to demangling symbols. However, if
1952 `COLLECT_NO_DEMANGLE' is set in the environment, then it will default
1974 yourself, the linker will use a default script that is compiled into the
1977 as `-r' or `-N', will affect the default linker script.
1980 option. When you do this, your linker script will replace the default
2014 will also call it an object file. Each object file has, among other
2031 section will have when the output file is run. The second is the
2033 section will be loaded. In most cases the two addresses will be the
2046 you compile a C or C++ program into an object file, you will get a
2049 referenced in the input file will become an undefined symbol.
2089 The `SECTIONS' command is a powerful command. Here we will describe
2091 initialized data, and uninitialized data. These will be in the
2098 linker script which will do that:
2128 `.text' is defined, the linker will set the address of the `.text'
2132 output file. The linker will place the `.data' output section at
2134 section, the value of the location counter will be `0x8000000' plus the
2135 size of the `.data' output section. The effect is that the linker will
2139 The linker will ensure that each output section has the required
2142 will probably satisfy any alignment constraints, but the linker may
2175 There are several ways to set the entry point. The linker will set
2197 Include the linker script FILENAME at this point. The file will
2220 inside the "sysroot prefix", the filename will
2221 the "sysroot prefix". Otherwise, the linker will try to open the
2223 will search through the archive library search path. See the
2226 If you use `INPUT (-lFILE)', `ld' will transform the name to
2230 files will be included in the link at the point at which the linker
2243 commands, among other filenames. The files listed will be handled
2245 with the exception of ELF shared libraries, that will be added only
2265 Options: Options.). If both are used, then the linker will search
2271 that FILENAME will become the first input file to be linked, as
2297 If neither `-EB' nor `-EL' are used, then the output format will
2299 format will be the second argument, BIG. If `-EL' is used, the
2300 output format will be the third argument, LITTLE.
2307 option, the output file will be created in the `elf32-littlemips'
2359 assignments will be made to `-T' output sections before those in
2379 section will not be. Any direct references between the two
2401 You may assign a value to a symbol in a linker script. This will define
2429 The first case will define SYMBOL to the value of EXPRESSION. In
2430 the other cases, SYMBOL must already be defined, and the value will be
2444 The section of the symbol will be set from the section of the
2461 In this example, the symbol `floating_point' will be defined as
2462 zero. The symbol `_etext' will be defined as the address following the
2463 last `.text' input section. The symbol `_bdata' will be defined as the
2493 underscore), the linker will give a multiple definition error. If, on
2495 underscore), the linker will silently use the definition in the program.
2497 will use the definition in the linker script.
2505 Similar to `PROVIDE'. For ELF targeted ports, the symbol will be
2636 linker will
2639 example, the order of sections in the output file will match the order
2640 in the first input file. The first section will be at address zero.
2712 of the output section. If you do not provide ADDRESS, the linker will
2716 If you provide ADDRESS, the address of the output section will be
2718 the address of the output section will be set to the current value of
2728 are subtly different. The first will set the address of the `.text'
2730 second will set it to the current value of the location counter aligned
2741 Specifying ADDRESS for a section will change the value of the
2786 will cause all .ctors sections from all files except `crtend.o' and
2793 `.rdata' input sections will appear in the output section. In the
2794 first example, they will be intermingled, appearing in the same order as
2796 input sections will appear first, followed by all `.rdata' input
2818 wildcards. On DOS based file systems, the linker will assume that a
2827 in the input file will be included in the output section. This is not
2832 and does not contain any wild card characters, the linker will first
2834 in an `INPUT' command. If you did not, the linker will attempt to open
2836 Note that this differs from an `INPUT' command, because the linker will
2868 will not match a `/' character (used to separate directory names on
2870 it will always match any file name, whether it contains a `/' or not.
2871 In a section name, the wildcard characters will match a `/' character.
2879 linker will use the first match in the linker script. For example, this
2881 `data.o' rule will not be used:
2885 Normally, the linker will place files and sections matched by
2889 the `SORT_BY_NAME' keyword is used, the linker will sort the files or
2894 difference is `SORT_BY_ALIGNMENT' will sort sections into ascending
2903 It will sort the input sections by name first, then by alignment
2907 It will sort the input sections by alignment first, then by name
2924 command line option will make the section sorting command to be treated
2936 command line option will be ignored.
2944 sections in `.text' and all `.bss' sections in `.bss'. The linker will
2946 character in `.DATA'; for all other files, the linker will place the
2971 In most cases, common symbols in input files will be placed in the
2977 common symbols and small common symbols. In this case, the linker will
2984 You will sometimes see `[COMMON]' in old linker scripts. This
3047 For example, this will store the byte 1 followed by the four byte
3059 endianness, which is the normal case, the value will be stored in that
3061 endianness, as is true of, for example, S-records, the value will be
3065 between them, so the following will produce an error from the linker:
3067 whereas this will work:
3101 file. The name of each symbol will be the name of the
3102 corresponding input file. The section of each symbol will be the
3113 arbitrary sections, such as ECOFF and XCOFF, the linker will
3133 arbitrary section names, GNU C++ will normally arrange to put the
3136 linker script will build the sort of table which the GNU C++
3159 Normally the compiler and linker will handle these issues
3160 automatically, and you will not need to concern yourself with
3171 The linker will not create output sections with no contents. This is
3175 will only create a `.foo' section in the output file if there is a
3178 an output section will also create the output section.
3180 The linker will ignore address assignments (*note Output Section
3182 defines symbols in the output section. In that case the linker will
3206 OUTPUT-SECTION-COMMAND. In this section we will describe the remaining
3229 The section should be marked as not loadable, so that it will not
3245 loaded when the program is run. The contents of the `ROM' section will
3269 will use the LMA_REGION as the VMA region as well.
3272 the linker will set the LMA such that the difference between VMA and
3275 not allocatable, the linker will set the LMA equal to the VMA. *Note
3354 segments, then all subsequent allocated sections will be assigned to
3372 gaps left due to the required alignment of input sections) will be
3396 the same memory address. At run time, some sort of overlay manager will
3438 the sections, the linker will report an error. Since the sections all
3462 This will define both `.text0' and `.text1' to start at address
3463 0x1000. `.text0' will be loaded at address 0x4000, and `.text1' will
3464 be loaded immediately after `.text0'. The following symbols will be
3499 can then assign sections to particular memory regions. The linker will
3500 set section addresses based on the memory regions, and will warn about
3501 regions that become too full. The linker will not shuffle sections
3515 names are stored in a separate name space, and will not conflict with
3523 section, the linker will create an output section with the same name as
3524 the input section. If you define region attributes, the linker will use
3550 `!', it will be placed in the memory region. The `!' attribute
3551 reverses this test, so that an unmapped section will be placed in the
3567 will place into the `rom' memory region every section which is not
3569 executable. The linker will place other sections which are not
3583 output section, the linker will set the address to the next available
3586 will issue an error message.
3606 program. This will only work if the program headers are set correctly.
3610 The linker will create reasonable program headers by default.
3613 linker sees the `PHDRS' command in the linker script, it will not
3617 generating an ELF output file. In other cases, the linker will simply
3631 names are stored in a separate name space, and will not conflict with
3636 system loader will load from the file. In the linker script, you
3648 the linker will place all subsequent allocatable sections which do not
3650 generally a whole set of contiguous sections will be placed in a single
3697 The linker will normally set the segment flags based on the sections
3798 specifically bound to a version node, it will effectively bind it to an
3810 symbols, only selects which symbols will be globally visible out and
3821 application will need to resolve all of the dynamic symbols. In this
3823 all external symbols that it needs will be resolvable without having to
3833 versioning, the user will get a warning when they start their program if
3869 this symbol will be bound. You can do this with the `foo@@VERS_2.0'
3883 The supported `lang's are `C', `C++', and `Java'. The linker will
3892 whitespace) between the version script and the demangler output will
3970 linker will still copy these sections into the output file, but it has
3981 the linker will automatically *note PROVIDE:: two symbols:
3999 Assigning a value to `.' will cause the location counter to be
4044 The `.text' section will be assigned a starting address of 0x100 and
4047 an error will be produced because this would be an attempt to move `.'
4048 backwards). The `.data' section will start at 0x500 and it will have
4076 I.e., the linker will place the orphan `.rodata' section as if the
4110 Now, the orphan `.rodata' section will be placed between
4171 will cause the error message `non constant expression for initial
4187 section. An expression which appears elsewhere will be absolute.
4189 A symbol set to a relative expression will be relocatable if you
4192 section will be the section of the relative expression.
4194 A symbol set to an absolute expression will retain the same value
4195 through any further link operation. The symbol will be absolute, and
4196 will not have any particular associated section.
4273 when this is evaluated, the linker will report an error. In the
4297 memory will be saved at the expense of up to COMMONPAGESIZE wasted
4370 option) that value will be returned; otherwise the value will be
4378 evaluated, the linker will report an error. In the following
4401 additional program headers, it will report an error `not enough
4415 an object file or an archive file, it will try to read the file as a
4417 linker will report an error.
4419 An implicit linker script will not replace the default linker script.
4424 Any input files read because of an implicit linker script will be
4534 each use will add another pair of name variants to search for when `-l'
4577 function using a normal `jsr' instruction. The linker will also change
4580 pointer to a function is taken. The pointer will in fact point to the
4589 For the ARM, `ld' will generate code stubs to allow functions calls
4595 given to the linker. This will make it generate larger stub functions
4596 which will work with non-interworking aware ARM code. Note, however,
4603 a BX instruction, and the program will start executing in Thumb mode
4608 The resulting image will contain big-endian data and little-endian code.
4693 enumeration values fitted into the smallest possible space will not be
4700 using 16-bit `wchar_t' values will not be diagnosed.
4707 The linker will automatically generate and insert small sequences of
4713 duplicate stubs, increasing the code sizw. The linker will try to
4723 then the linker will choose exactly where to place groups of stubs,
4740 When generating a shared library, `ld' will by default generate import
4761 single input section larger than the group size specified will of course
4818 `-m [mpu type]' will select an appropriate linker script for selected
4822 The linker will recognize some extra sections which are MSP430
4830 code in this section will be uploaded to the MPU.
4834 this section will be uploaded to the MPU.
4838 this section will not be uploaded to the MPU.
4863 `ld' will generate this layout, including stubs to access the PLT,
4869 `ld' will use the new PLT and GOT layout if it is linking new
4872 layout. A warning will be given if some object file requires the
4922 single input section larger than the group size specified will of
4965 unneeded will of course be kept. TOC words without any referencing
5016 option, `ld' will provide an estimate of maximum stack usage.
5025 for dynamic allocation, e.g. alloca, will not be detected. If a
5027 stack usage and calls will be given.
5030 This option, if given along with `--stack-analysis' will result in
5036 size will be zero, type `STT_NOTYPE', binding `STB_LOCAL', and
5048 `ld' will read any version or byte order, but the output header format
5085 will be _disabled_ if either of the following are true:
5159 table. It will still be exported by its ordinal alias
5166 function. The import lib will export only an indirect
5176 attribute enforces, the application will behave unexpectedly.
5199 All such symbols will be exported from the DLL. If, however,
5237 additional assistance. Sometimes, you will see this message
5264 compiled result will run without error on an older system.
5288 For instance, when ld is called with the argument `-lxxx' it will
5331 names (`cygncurses-5.dll') this will often fail, unless one
5354 Linking directly to a dll without using an import lib will work
5382 will soon begin to use this feature whenever possible.
5388 names. A symbol `foo' will be exported as `foo', but it can
5390 DEF file when creating the dll. This will affect also the
5415 directives in the DEF file. (This will also affect the import
5434 symbols will be exported. In effect, you'd be aliasing those
5462 specification with a wildcard file will be interleaved when necessary to
5484 literal will be removed and all the `L32R' instructions that use it
5485 will be changed to reference an identical literal, as long as the
5493 optimized to a direct call, the linker will change the `CALLXN'
5498 alignment of subsequent branch targets. By default, the linker will
5516 size more than performance. With this option, the linker will not
5562 memory with pointers to routines that will be used to access elements of
5595 image is produced, alignment information will not propagate to the
5596 output file. (The linker will still use the alignment information
5621 is then written back in the same format, the back end routine will be
5671 so an output file (no matter its format) will retain symbols
5682 information will be preserved.
5798 Without this, we will not know whether there is any point in
5811 observe the bug. To guarantee you will not omit something
5818 * A complete input file, or set of input files, that will reproduce
5823 file(s) to whomever requests them. (Note - your email will be
5837 will certainly notice it. But if the bug is incorrect output, we
5857 The line numbers in our development sources will not match those
5866 which changes to the input file will make the bug go away and which
5867 changes will not affect it.
5870 we will find the bug is by running a single example under the
5876 output will be easier to spot, running under the debugger will take
5892 construct an example that will make the program follow a certain
5893 path through the code. If you do not send us the example, we will
5894 not be able to construct one, so we will not be able to verify
5898 your patch should be an improvement, we will not install it. A
5899 test case will help us to understand.
5943 use the `ABSOLUTE' command to restrict the sections that will be
5946 `ABSOLUTE' commands will appear in the linker output. You can
6006 `ORDER' command. The sections you list with `ORDER' will appear
6170 this Transparent copy will remain thus accessible at the stated
6341 version of this License, the original English version will prevail.
6348 void, and will automatically terminate your rights under this
6350 from you under this License will not have their licenses
6357 versions will be similar in spirit to the present version, but may
