Lines Matching full:will
103 which will come from the standard search directories. (See the
111 argument will either have no further effect, or override prior
127 If the linker cannot recognize the format of an object file, it will
174 exist, or cannot be read, then the option will be treated
182 additional @FILE options; any such options will be processed
251 symbol named ENTRY, the linker will try to parse ENTRY as a number,
252 and use that as the entry address (the number will be interpreted
266 option will be treated as hidden.
274 If you do not use this option, the dynamic symbol table will
280 dynamic object, then you will probably need to use this option when
302 you run the program, the dynamic linker will see the DT_AUXILIARY
304 object, it will first check whether there is a definition in the
305 shared object NAME. If there is one, it will be used instead of
312 entries will be created in the order in which they appear on the
324 you run the program, the dynamic linker will see the DT_FILTER
325 field. The dynamic linker will resolve symbols according to the
326 symbol table of the filter object as usual, but it will actually
336 environment variable. The GNU linker will ignore the `-F' option
361 executable is run the dynamic linker will attempt to load the
378 If NAMESPEC is of the form `:FILENAME', `ld' will search the
379 library path for a file called FILENAME, otherise it will search
384 systems, `ld' will search a directory for a library called
390 The linker will search an archive only once, at the location where
393 the archive on the command line, the linker will include the
395 symbol in an object appearing later on the command line will not
409 Add path SEARCHDIR to the list of paths that `ld' will search for
417 If SEARCHDIR begins with `=', then the `=' will be replaced by the
458 circumstances the linker will display the final value
466 will produce the following output in the link map if the `-M'
661 It marks the object so that its runtime initialization will
664 runtime finalization of the object will occur after the
692 object will ignore any default library search paths.
764 Normally, the linker will add a DT_NEEDED tag for each dynamic
776 after the `--no-add-needed' option. Normally, the linker will add
778 `--no-add-needed' causes DT_NEEDED tags will never be emitted for
858 linker will perform this check, and if it finds any overlaps it
859 will produce suitable error messages. The linker does know about,
914 demangling style for your compiler. The linker will demangle by
949 will be kept, as will sections containing symbols referenced by
999 Normally when a symbol is defined multiple times, the linker will
1001 the first definition will be used.
1023 Normally when a symbol has an undefined version, the linker will
1025 and a fatal error will be issued instead.
1036 Normally `ld' will give an error if you try to link together input
1045 Normally `ld' will give a warning if it finds an incompatible
1054 Normally, the linker will not produce an output file if it
1136 variable `LD_RUN_PATH' will be used if it is defined.
1139 SunOS, the linker will form a runtime search patch out of all the
1141 runtime search path will be formed exclusively using the `-rpath'
1156 non-shared, non-relocatable link, it will automatically try to
1202 If the required shared library is not found, the linker will issue
1208 XCOFF and SunOS platforms. On SunOS, the linker will
1222 This option will apply `SORT_BY_NAME' to all wildcard section
1226 This option will apply `SORT_BY_ALIGNMENT' to all wildcard section
1240 relocations in a single section. Note that this will fail to work
1242 The linker will not split up individual input sections for
1244 COUNT relocations one output section will contain that many
1308 Normally the linker will generate an error message for each
1359 symbols will be a common symbol.
1418 alignment. Typically, the alignment will be set by an input
1419 section. The address will only be changed if it not explicitly
1428 option `--unresolved-symbols') it will normally generate an error.
1446 list of archives, because gcc will add its own list of archives to
1451 SYMBOL will be resolved to `__wrap_SYMBOL'. Any undefined
1452 reference to `__real_SYMBOL' will be resolved to SYMBOL.
1468 all calls to `malloc' will call the function `__wrap_malloc'
1469 instead. The call to `__real_malloc' in `__wrap_malloc' will call
1473 links without the `--wrap' option will succeed. If you do this,
1486 `--enable-new-dtags', the dynamic tags will be created as needed.
1487 If you specify `--disable-new-dtags', no new dynamic tags will be
1532 the same in an identical output file, but will be unique among all
1558 If given, symbols with a stdcall suffix (@NN) will be exported
1574 If the link finds a symbol that it cannot resolve, it will attempt
1577 and will resolve that symbol by linking to the match. For
1592 will be exported by the DLL. Note that this is the default if
1597 `DllEntryPoint@0', `DllMainCRTStartup@12', and `impure_ptr' will
1599 DLLs will not be re-exported, nor will symbols specifying the
1602 `libstd++', `libmingw32', or `crtX.o' will be exported. Symbols
1603 whose names begin with `__rtti_' or `__builtin_' will not be
1621 Specify the file alignment. Sections in the file will always
1635 lowest memory location that will be used when your program or dll
1643 If given, the stdcall suffixes (@NN) will be stripped from symbols
1685 The linker will create the file FILE which will contain a DEF file
1693 The linker will create the file FILE which will contain an import
1728 of the 'auto-import' extension will cause the text section of the
1732 Note - use of the 'auto-import' extension will also cause read only
1738 Using 'auto-import' generally will 'just work' - but sometimes you
1751 data type of the offending exported variable, ld will always
1796 building client code that will link to the DLL, or merely
1852 switch will create a vector of 'runtime pseudo relocations' which
1868 Sets the section alignment. Sections in memory will always begin
1883 Specifies the subsystem under which your program will execute. The
1950 Normally, the linker will default to demangling symbols. However, if
1951 `COLLECT_NO_DEMANGLE' is set in the environment, then it will default
1973 yourself, the linker will use a default script that is compiled into the
1976 as `-r' or `-N', will affect the default linker script.
1979 option. When you do this, your linker script will replace the default
2013 will also call it an object file. Each object file has, among other
2030 section will have when the output file is run. The second is the
2032 section will be loaded. In most cases the two addresses will be the
2045 you compile a C or C++ program into an object file, you will get a
2048 referenced in the input file will become an undefined symbol.
2088 The `SECTIONS' command is a powerful command. Here we will describe
2090 initialized data, and uninitialized data. These will be in the
2097 linker script which will do that:
2127 `.text' is defined, the linker will set the address of the `.text'
2131 output file. The linker will place the `.data' output section at
2133 section, the value of the location counter will be `0x8000000' plus the
2134 size of the `.data' output section. The effect is that the linker will
2138 The linker will ensure that each output section has the required
2141 will probably satisfy any alignment constraints, but the linker may
2174 There are several ways to set the entry point. The linker will set
2196 Include the linker script FILENAME at this point. The file will
2219 inside the "sysroot prefix", the filename will be looked for in
2220 will try to open the
2222 will search through the archive library search path. See the
2225 If you use `INPUT (-lFILE)', `ld' will transform the name to
2229 files will be included in the link at the point at which the linker
2242 commands, among other filenames. The files listed will be handled
2244 with the exception of ELF shared libraries, that will be added only
2264 Options: Options.). If both are used, then the linker will search
2270 that FILENAME will become the first input file to be linked, as
2296 If neither `-EB' nor `-EL' are used, then the output format will
2298 format will be the second argument, BIG. If `-EL' is used, the
2299 output format will be the third argument, LITTLE.
2306 option, the output file will be created in the `elf32-littlemips'
2358 assignments will be made to `-T' output sections before those in
2378 section will not be. Any direct references between the two
2400 You may assign a value to a symbol in a linker script. This will define
2428 The first case will define SYMBOL to the value of EXPRESSION. In
2429 the other cases, SYMBOL must already be defined, and the value will be
2443 The section of the symbol will be set from the section of the
2460 In this example, the symbol `floating_point' will be defined as
2461 zero. The symbol `_etext' will be defined as the address following the
2462 last `.text' input section. The symbol `_bdata' will be defined as the
2492 underscore), the linker will give a multiple definition error. If, on
2494 underscore), the linker will silently use the definition in the program.
2496 will use the definition in the linker script.
2504 Similar to `PROVIDE'. For ELF targeted ports, the symbol will be
2635 linker will place each input section into an identically named output
2638 example, the order of sections in the output file will match the order
2639 in the first input file. The first section will be at address zero.
2711 of the output section. If you do not provide ADDRESS, the linker will
2715 If you provide ADDRESS, the address of the output section will be
2717 the address of the output section will be set to the current value of
2727 are subtly different. The first will set the address of the `.text'
2729 second will set it to the current value of the location counter aligned
2740 Specifying ADDRESS for a section will change the value of the
2785 will cause all .ctors sections from all files except `crtend.o' and
2792 `.rdata' input sections will appear in the output section. In the
2793 first example, they will be intermingled, appearing in the same order as
2795 input sections will appear first, followed by all `.rdata' input
2817 wildcards. On DOS based file systems, the linker will assume that a
2826 in the input file will be included in the output section. This is not
2831 and does not contain any wild card characters, the linker will first
2833 in an `INPUT' command. If you did not, the linker will attempt to open
2835 Note that this differs from an `INPUT' command, because the linker will
2867 will not match a `/' character (used to separate directory names on
2869 it will always match any file name, whether it contains a `/' or not.
2870 In a section name, the wildcard characters will match a `/' character.
2878 linker will use the first match in the linker script. For example, this
2880 `data.o' rule will not be used:
2884 Normally, the linker will place files and sections matched by
2888 the `SORT_BY_NAME' keyword is used, the linker will sort the files or
2893 difference is `SORT_BY_ALIGNMENT' will sort sections into ascending
2902 It will sort the input sections by name first, then by alignment
2906 It will sort the input sections by alignment first, then by name
2923 command line option will make the section sorting command to be treated
2935 command line option will be ignored.
2943 sections in `.text' and all `.bss' sections in `.bss'. The linker will
2945 character in `.DATA'; for all other files, the linker will place the
2970 In most cases, common symbols in input files will be placed in the
2976 common symbols and small common symbols. In this case, the linker will
2983 You will sometimes see `[COMMON]' in old linker scripts. This
3046 For example, this will store the byte 1 followed by the four byte
3058 endianness, which is the normal case, the value will be stored in that
3060 endianness, as is true of, for example, S-records, the value will be
3064 between them, so the following will produce an error from the linker:
3066 whereas this will work:
3100 file. The name of each symbol will be the name of the
3101 corresponding input file. The section of each symbol will be the
3112 arbitrary sections, such as ECOFF and XCOFF, the linker will
3132 arbitrary section names, GNU C++ will normally arrange to put the
3135 linker script will build the sort of table which the GNU C++
3158 Normally the compiler and linker will handle these issues
3159 automatically, and you will not need to concern yourself with
3170 The linker will not create output sections with no contents. This is
3174 will only create a `.foo' section in the output file if there is a
3177 an output section will also create the output section.
3179 The linker will ignore address assignments (*note Output Section
3181 defines symbols in the output section. In that case the linker will
3205 OUTPUT-SECTION-COMMAND. In this section we will describe the remaining
3228 The section should be marked as not loadable, so that it will not
3244 loaded when the program is run. The contents of the `ROM' section will
3268 will use the LMA_REGION as the VMA region as well.
3271 the linker will set the LMA such that the difference between VMA and
3274 not allocatable, the linker will set the LMA equal to the VMA. *Note
3353 segments, then all subsequent allocated sections will be assigned to
3371 gaps left due to the required alignment of input sections) will be
3395 the same memory address. At run time, some sort of overlay manager will
3437 the sections, the linker will report an error. Since the sections all
3461 This will define both `.text0' and `.text1' to start at address
3462 0x1000. `.text0' will be loaded at address 0x4000, and `.text1' will
3463 be loaded immediately after `.text0'. The following symbols will be
3498 can then assign sections to particular memory regions. The linker will
3499 set section addresses based on the memory regions, and will warn about
3500 regions that become too full. The linker will not shuffle sections
3514 names are stored in a separate name space, and will not conflict with
3522 section, the linker will create an output section with the same name as
3523 the input section. If you define region attributes, the linker will use
3549 `!', it will be placed in the memory region. The `!' attribute
3550 reverses this test, so that an unmapped section will be placed in the
3566 will place into the `rom' memory region every section which is not
3568 executable. The linker will place other sections which are not
3582 output section, the linker will set the address to the next available
3585 will issue an error message.
3605 program. This will only work if the program headers are set correctly.
3609 The linker will create reasonable program headers by default.
3612 linker sees the `PHDRS' command in the linker script, it will not
3616 generating an ELF output file. In other cases, the linker will simply
3630 names are stored in a separate name space, and will not conflict with
3635 system loader will load from the file. In the linker script, you
3647 the linker will place all subsequent allocatable sections which do not
3649 generally a whole set of contiguous sections will be placed in a single
3696 The linker will normally set the segment flags based on the sections
3797 specifically bound to a version node, it will effectively bind it to an
3809 symbols, only selects which symbols will be globally visible out and
3820 application will need to resolve all of the dynamic symbols. In this
3822 all external symbols that it needs will be resolvable without having to
3832 will get a warning when they start their program if
3868 this symbol will be bound. You can do this with the `foo@@VERS_2.0'
3882 The supported `lang's are `C', `C++', and `Java'. The linker will
3891 whitespace) between the version script and the demangler output will
3969 linker will still copy these sections into the output file, but it has
3980 the linker will automatically *note PROVIDE:: two symbols:
3998 Assigning a value to `.' will cause the location counter to be
4043 The `.text' section will be assigned a starting address of 0x100 and
4046 an error will be produced because this would be an attempt to move `.'
4047 backwards). The `.data' section will start at 0x500 and it will have
4075 I.e., the linker will place the orphan `.rodata' section as if the
4109 Now, the orphan `.rodata' section will be placed between
4170 will cause the error message `non constant expression for initial
4186 section. An expression which appears elsewhere will be absolute.
4188 A symbol set to a relative expression will be relocatable if you
4191 section will be the section of the relative expression.
4193 A symbol set to an absolute expression will retain the same value
4194 through any further link operation. The symbol will be absolute, and
4195 will not have any particular associated section.
4272 when this is evaluated, the linker will report an error. In the
4296 memory will be saved at the expense of up to COMMONPAGESIZE wasted
4369 option) that value will be returned; otherwise the value will be
4377 evaluated, the linker will report an error. In the following
4400 additional program headers, it will report an error `not enough
4414 an object file or an archive file, it will try to read the file as a
4416 linker will report an error.
4418 An implicit linker script will not replace the default linker script.
4423 Any input files read because of an implicit linker script will be
4533 each use will add another pair of name variants to search for when `-l'
4576 function using a normal `jsr' instruction. The linker will also change
4579 pointer to a function is taken. The pointer will in fact point to the
4588 For the ARM, `ld' will generate code stubs to allow functions calls
4594 given to the linker. This will make it generate larger stub functions
4595 which will work with non-interworking aware ARM code. Note, however,
4602 a BX instruction, and the program will start executing in Thumb mode
4607 The resulting image will contain big-endian data and little-endian code.
4692 enumeration values fitted into the smallest possible space will not be
4699 using 16-bit `wchar_t' values will not be diagnosed.
4706 The linker will automatically generate and insert small sequences of
4712 duplicate stubs, increasing the code sizw. The linker will try to
4722 then the linker will choose exactly where to place groups of stubs,
4739 When generating a shared library, `ld' will by default generate import
4760 single input section larger than the group size specified will of course
4817 `-m [mpu type]' will select an appropriate linker script for selected
4821 The linker will recognize some extra sections which are MSP430
4829 code in this section will be uploaded to the MPU.
4833 this section will be uploaded to the MPU.
4837 this section will not be uploaded to the MPU.
4862 `ld' will generate this layout, including stubs to access the PLT,
4868 `ld' will use the new PLT and GOT layout if it is linking new
4871 layout. A warning will be given if some object file requires the
4921 single input section larger than the group size specified will of
4964 unneeded will of course be kept. TOC words without any referencing
5015 option, `ld' will provide an estimate of maximum stack usage.
5024 for dynamic allocation, e.g. alloca, will not be detected. If a
5026 stack usage and calls will be given.
5029 This option, if given along with `--stack-analysis' will result in
5035 size will be zero, type `STT_NOTYPE', binding `STB_LOCAL', and
5047 `ld' will read any version or byte order, but the output header format
5084 will be _disabled_ if either of the following are true:
5158 table. It will still be exported by its ordinal alias
5165 function. The import lib will export only an indirect
5175 attribute enforces, the application will behave unexpectedly.
5198 All such symbols will be exported from the DLL. If, however,
5236 additional assistance. Sometimes, you will see this message
5263 compiled result will run without error on an older system.
5287 For instance, when ld is called with the argument `-lxxx' it will
5330 names (`cygncurses-5.dll') this will often fail, unless one
5353 Linking directly to a dll without using an import lib will work
5381 will soon begin to use this feature whenever possible.
5387 names. A symbol `foo' will be exported as `foo', but it can
5389 DEF file when creating the dll. This will affect also the
5414 directives in the DEF file. (This will also affect the import
5433 symbols will be exported. In effect, you'd be aliasing those
5461 specification with a wildcard file will be interleaved when necessary to
5483 literal will be removed and all the `L32R' instructions that use it
5484 will be changed to reference an identical literal, as long as the
5492 optimized to a direct call, the linker will change the `CALLXN'
5497 alignment of subsequent branch targets. By default, the linker will
5515 size more than performance. With this option, the linker will not
5561 memory with pointers to routines that will be used to access elements of
5594 image is produced, alignment information will not propagate to the
5595 output file. (The linker will still use the alignment information
5620 is then written back in the same format, the back end routine will be
5670 so an output file (no matter its format) will retain symbols
5681 information will be preserved.
5797 Without this, we will not know whether there is any point in
5810 observe the bug. To guarantee you will not omit something
5817 * A complete input file, or set of input files, that will reproduce
5822 file(s) to whomever requests them. (Note - your email will be
5836 will certainly notice it. But if the bug is incorrect output, we
5856 The line numbers in our development sources will not match those
5865 which changes to the input file will make the bug go away and which
5866 changes will not affect it.
5869 we will find the bug is by running a single example under the
5875 output will be easier to spot, running under the debugger will take
5891 construct an example that will make the program follow a certain
5892 path through the code. If you do not send us the example, we will
5893 not be able to construct one, so we will not be able to verify
5897 your patch should be an improvement, we will not install it. A
5898 test case will help us to understand.
5942 use the `ABSOLUTE' command to restrict the sections that will be
5945 `ABSOLUTE' commands will appear in the linker output. You can
6005 `ORDER' command. The sections you list with `ORDER' will appear
6169 this Transparent copy will remain thus accessible at the stated
6340 version of this License, the original English version will prevail.
6347 void, and will automatically terminate your rights under this
6349 from you under this License will not have their licenses
6356 versions will be similar in spirit to the present version, but may
