| /openbsd/src/gnu/llvm/llvm/utils/ |
| D | check-each-file | 7 if [ x$1 = x--make-linker-script ]
10 linker=./link-$program
16 echo "rm -f $program" > $linker
17 gmake -n $program >> $linker
18 chmod 755 $linker
19 echo "Linker script created in $linker; testing it out"
20 output=`./$linker 2>&1`
26 echo "Done; rebuilding $linker"
27 echo "rm -f $program" > $linker
28 gmake -n $program 2>&1 | sed '/gcc/s/$/__main.o/' >> $linker
[all …]
|
| /openbsd/src/gnu/llvm/llvm/docs/ |
| D | LinkTimeOptimization.rst | 14 interface and design between the LTO optimizer and the linker.
23 achieved through tight integration with the linker. In this model, the linker
25 matching among them. The linker uses `libLTO`_, a shared object, to handle LLVM
26 bitcode files. This tight integration between the linker and LLVM optimizer
27 helps to do optimizations that are not possible in other models. The linker
36 and clean interface. This example requires a system linker which supports LTO
38 invokes system linker.
94 * In this example, the linker recognizes that ``foo2()`` is an externally
95 visible symbol defined in LLVM bitcode file. The linker completes its usual
104 * And this in turn, enables linker to remove ``foo4()``.
[all …]
|
| /openbsd/src/gnu/usr.bin/binutils/ld/ |
| D | NEWS | 3 * The linker script operator DEFINED() will now yield 1 only for a symbol that
11 * Improved linker's handling of unresolved symbols. The switch
12 --unresolved-symbols=<method> has been added to tell the linker when it
23 * Added --accept-unknown-linker-format to restore old linker behaviour (pre
54 * Support for -z nocopyreloc in the x86 ELF linker, which disables
58 * Support for -z combreloc in the ELF linker, which puts dynamic
59 relocations against the same symbol together, so that dynamic linker
71 linker then merges these sections together into the normal .debug_info
74 * The native ELF linker now searches the directories in DT_RUNPATH or
96 * Added AT> to the linker script language to allow load-time allocation of
[all …]
|
| D | README | 3 This is the GNU linker. It is distributed with other "binary
7 There are many features of the linker:
9 * The linker uses a Binary File Descriptor library (../bfd)
11 insulate the linker itself from the format of object files.
13 * The linker supports a number of different object file
17 * The linker can be configured for cross-linking.
19 * The linker supports a control language.
29 If you want to make a cross-linker, you may want to specify
34 To build just the linker, make the target all-ld from the top level
50 The Solaris linker normally exports all dynamic symbols from an
[all …]
|
| D | ld.texinfo | 55 * Ld: (ld). The GNU linker.
61 This file documents the @sc{gnu} linker LD version @value{VERSION}.
85 @settitle Using LD, the GNU linker
88 @subtitle The GNU linker
100 \hfill {\it Using LD, the GNU linker}\par
121 @c FIXME: Talk about importance of *order* of args, cmds to linker!
126 This file documents the @sc{gnu} linker ld version @value{VERSION}.
180 @cindex @sc{gnu} linker
209 ld: the GNU linker, for full details on the command language and
210 on other aspects of the GNU linker.
[all …]
|
| D | ldint.texinfo | 9 * Ld-Internals: (ldint). The GNU linker internals.
15 This file documents the internals of the GNU linker ld.
42 @title{A guide to the internals of the GNU linker}
74 This file documents the internals of the GNU linker @code{ld}. It is a
85 * Emulations:: How linker emulations are generated
98 @chapter How linker emulations are generated
100 Each linker target has an @dfn{emulation}. The emulation includes the
101 default linker script, and certain emulations also modify certain types
102 of linker behaviour.
113 @file{scripttempl} directory in order to create default linker scripts
[all …]
|
| /openbsd/src/gnu/usr.bin/binutils-2.17/ld/ |
| D | NEWS | 5 * Modify the Linux linker search order to better match ld.so search order.
23 * New linker script construct AS_NEEDED(), which sets the --as-needed flag
30 * New linker script functions: ORIGIN() and LENGTH() which return information
35 * Added SEGMENT_START to the linker script language to permit the user to
41 * Added SORT_BY_NAME and SORT_BY_ALIGNMENT to the linker script
45 * Added a new linker command line switch, --sort-section name|alignment,
55 * A new linker command line switch has been added which allows the hash table
77 * The linker script operator DEFINED() will now yield 1 only for a symbol that
87 * Improved linker's handling of unresolved symbols. The switch
88 --unresolved-symbols=<method> has been added to tell the linker when it
[all …]
|
| D | README | 3 This is the GNU linker. It is distributed with other "binary
7 There are many features of the linker:
9 * The linker uses a Binary File Descriptor library (../bfd)
11 insulate the linker itself from the format of object files.
13 * The linker supports a number of different object file
17 * The linker can be configured for cross-linking.
19 * The linker supports a control language.
29 If you want to make a cross-linker, you may want to specify
34 To build just the linker, make the target all-ld from the top level
50 The Solaris linker normally exports all dynamic symbols from an
[all …]
|
| D | ld.texinfo | 58 * Ld: (ld). The GNU linker.
64 This file documents the @sc{gnu} linker LD version @value{VERSION}.
88 @settitle Using LD, the GNU linker
91 @subtitle The GNU linker
103 \hfill {\it Using LD, the GNU linker}\par
124 @c FIXME: Talk about importance of *order* of args, cmds to linker!
129 This file documents the @sc{gnu} linker ld version @value{VERSION}.
192 @cindex @sc{gnu} linker
221 ld: the GNU linker, for full details on the command language and
222 on other aspects of the GNU linker.
[all …]
|
| /openbsd/src/gnu/llvm/clang/docs/ |
| D | ClangLinkerWrapper.rst | 8 .. _clang-linker-wrapper:
15 register them. It works by first scanning the linker's input for embedded device
26 only for the linker wrapper will be forwarded to the wrapped linker job.
30 USAGE: clang-linker-wrapper [options] -- <options to passed to the linker>
37 --device-linker=<value> or <triple>=<value>
38 Arguments to pass to the device linker invocation
44 --linker-path=<path> The linker executable to invoke
61 -- The separator for the wrapped linker arguments
74 clang-linker-wrapper --host-triple=x86_64 --linker-path=/usr/bin/ld -- <Args>
|
| /openbsd/src/gnu/llvm/compiler-rt/lib/lsan/ |
| D | lsan_common_linux.cpp | 32 static LoadedModule *linker = nullptr; variable
59 if (linker == nullptr) { in InitializePlatformSpecificModules()
60 linker = reinterpret_cast<LoadedModule *>(linker_placeholder); in InitializePlatformSpecificModules()
61 *linker = module; in InitializePlatformSpecificModules()
67 linker->clear(); in InitializePlatformSpecificModules()
68 linker = nullptr; in InitializePlatformSpecificModules()
72 if (linker == nullptr) { in InitializePlatformSpecificModules()
107 LoadedModule *GetLinker() { return linker; } in GetLinker()
|
| /openbsd/src/gnu/llvm/lld/docs/ |
| D | index.rst | 4 LLD is a linker from the LLVM project that is a drop-in replacement
8 The linker supports ELF (Unix), PE/COFF (Windows), Mach-O (macOS) and
19 same command line arguments and linker scripts as GNU.
23 gold linker. Your mileage may vary, though.
30 - It is always a cross-linker, meaning that it always supports all the
33 easy to use our linker as part of a cross-compile toolchain.
38 external linker and then call the linker's main function,
110 instead of the default linker.
112 The easiest way to do that is to overwrite the default linker. After
132 - May 2015: We decided to rewrite the COFF linker and did that.
[all …]
|
| D | NewLLD.rst | 7 You can embed LLD to your program by linking against it and calling the linker's
14 files in the usual way and give them to the linker. It is naturally expected to
15 work, or otherwise it's a linker's bug.
26 There are many design choices you have to make to create a complete linker.
48 Since we are trying to create a high-performance linker,
63 We'll describe how the traditional Unix linker handles archive files, what the
66 The traditional Unix linker maintains a set of undefined symbols during
67 linking. The linker visits each file in the order as they appeared in the
68 command line until the set becomes empty. What the linker would do depends on
71 - If the linker visits an object file, the linker links object files to the
[all …]
|
| D | WebAssembly.rst | 23 common linker flags with **ld.lld** but also includes several
42 Note that this will not export linker-generated mutable globals unless
68 linker to shrink the code section to remove any padding from the final
90 Report all unresolved symbols. This is the default. Normally the linker
97 this is trivial. For direct function calls, the linker will generate a
111 symbols are resolved by a dynamic linker. Since the dynamic linking API is
140 In general, where possible, the WebAssembly linker attempts to emulate the
141 behaviour of a traditional ELF linker, and in particular the ELF port of lld.
148 One way in which the WebAssembly linker differs from traditional native linkers
176 In addition, symbols can be exported via the linker command line using
[all …]
|
| /openbsd/src/gnu/usr.bin/binutils-2.17/bfd/doc/ |
| D | linker.texi | 3 The linker uses three special entry points in the BFD target
14 file. These routines are designed so that the linker proper
16 files that it is linking. The linker merely arranges the
17 sections as directed by the linker script and lets BFD handle
23 including the linker hash table (which was created by the
24 first routine) and a set of callback functions to the linker
27 The generic linker routines are in @code{linker.c}, and use the
40 @subsection Creating a linker hash table
43 The linker routines must create a hash table, which must be
47 the target vector of the linker output file.
[all …]
|
| D | hash.texi | 15 entry, because they were designed for use by the linker back
16 ends. The linker may create thousands of hash table entries,
117 An example of a derived hash table is the linker hash table.
119 functions are in @code{linker.c}.
122 table. For example, the a.out linker backend code uses a hash
123 table derived from the linker hash table.
145 For example, the linker hash table defines @code{struct
210 The creation routine for the linker hash table, which is in
211 @code{linker.c}, looks just like this example.
218 in a linker hash table entry: @code{type}, @code{written} and
[all …]
|
| /openbsd/src/gnu/usr.bin/binutils/bfd/doc/ |
| D | linker.texi | 3 The linker uses three special entry points in the BFD target
14 file. These routines are designed so that the linker proper
16 files that it is linking. The linker merely arranges the
17 sections as directed by the linker script and lets BFD handle
23 including the linker hash table (which was created by the
24 first routine) and a set of callback functions to the linker
27 The generic linker routines are in @code{linker.c}, and use the
40 @subsection Creating a linker hash table
43 The linker routines must create a hash table, which must be
47 the target vector of the linker output file.
[all …]
|
| D | hash.texi | 15 entry, because they were designed for use by the linker back
16 ends. The linker may create thousands of hash table entries,
113 An example of a derived hash table is the linker hash table.
115 functions are in @code{linker.c}.
118 table. For example, the a.out linker backend code uses a hash
119 table derived from the linker hash table.
141 For example, the linker hash table defines @code{struct
208 The creation routine for the linker hash table, which is in
209 @code{linker.c}, looks just like this example.
216 in a linker hash table entry: @code{type}, @code{written} and
[all …]
|
| D | Makefile.am | 10 syms.texi targets.texi init.texi hash.texi linker.texi \
34 $(srcdir)/../hash.c $(srcdir)/../linker.c \
205 s-linker: $(MKDOC) $(srcdir)/../linker.c $(srcdir)/doc.str
206 ./$(MKDOC) -f $(srcdir)/doc.str <$(srcdir)/../linker.c >linker.tmp
207 $(SHELL) $(srcdir)/../../move-if-change linker.tmp linker.texi
208 touch s-linker
209 linker.texi: s-linker
272 $(srcdir)/../linker.c \
|
| /openbsd/src/gnu/llvm/compiler-rt/lib/profile/ |
| D | InstrProfilingPlatformWindows.c | 16 #pragma comment(linker, "/MERGE:.lprfc=.data")
17 #pragma comment(linker, "/MERGE:.lprfd=.data")
18 #pragma comment(linker, "/MERGE:.lprfv=.data")
19 #pragma comment(linker, "/MERGE:.lprfnd=.data")
|
| /openbsd/src/usr.bin/libtool/LT/Mode/Link/ |
| D | Program.pm | 40 my ($linker, $self, $ltprog, $ltconfig, $dirs, $libs, $deplibs,
57 $linker->common1($parser, $gp, $deplibs, $libdirs, $dirs, $libs);
92 $linker->create_symlinks($symlinkdir, $libs);
99 push @libflags, $linker->infer_libparameter($a, $k);
113 push(@linkeropts, $linker->export_symbols($ltconfig,
|
| D | Library.pm | 38 my ($linker, $self, $ltprog, $ltconfig, $la, $fname, $odir, $shared,
60 $linker->common1($parser, $gp, $deplibs, $libdirs, $dirs, $libs);
133 $linker->create_symlinks($symlinkdir, $libs);
149 push @libflags, $linker->infer_libparameter($a, $k);
179 my @e = $linker->export_symbols($ltconfig,
|
| /openbsd/src/gnu/llvm/compiler-rt/lib/sanitizer_common/ |
| D | sanitizer_win_defs.h | 69 __pragma(comment(linker, "/alternatename:" WIN_SYM_PREFIX STRINGIFY(Name) "="\
73 __pragma(comment(linker, "/include:" WIN_SYM_PREFIX STRINGIFY(Name)))
76 __pragma(comment(linker, "/export:" WIN_EXPORT_PREFIX STRINGIFY(ExportedName)\
|
| /openbsd/src/gnu/usr.bin/binutils/ld/scripttempl/ |
| D | tic80coff.sc | 5 # time this script is run to generate one of the linker scripts for ldscripts:
7 # RELOCATING: Set to a non-empty string when the linker is going to be doing
10 # CONSTRUCTING: Set to a non-empty string when the linker is going to be
17 # the -shared linker arg.
|
| /openbsd/src/gnu/usr.bin/binutils-2.17/ld/scripttempl/ |
| D | tic80coff.sc | 5 # time this script is run to generate one of the linker scripts for ldscripts:
7 # RELOCATING: Set to a non-empty string when the linker is going to be doing
10 # CONSTRUCTING: Set to a non-empty string when the linker is going to be
17 # the -shared linker arg.
|