Lines Matching full:linker

3 Linker Design
12 lld is a new generation of linker.  It is not "section" based like traditional
17 functions for locality, and C++ coalescing require the linker to work at a finer
25 The Atom model allows the linker to use standard graph theory models for linking
75 The linker views the input files as basically containers of Atoms and
76 References, and just a few attributes of their own.  The linker works with three
79 expected by the linker.
86 atoms representing all content in the .o file.  The linker adds all those atoms
96 remaining in the master graph, the linker reads the table of contents for each
108 this is modeled in the linker is that a dynamic library contributes no atoms to
112 instantiated by the by the reader which the linker uses to replace the
120 out into a separate "options" abstraction which enables the linker to be driven
168 The linker support coalescing by-name and by-content. By-name is used for
174 structures, the linker iterates all atoms in all input files. For each atom, it
182 linker scans all libraries (both static and dynamic) looking for definitions to
186 Dead code stripping (if requested) is done at the end of resolving.  The linker
193 throughout the linker. The file readers parse (mach-o, ELF, COFF) into an
196 a simpler, consistent model, but it enables the state of the linker to be dumped
287 for the linker to parse.  Since an atom has lots of attributes most of which are
315 its own optimization reasons which my inadvertently disable or break the linker
318 specific linker logic.
341 linker merges object files.  All test cases are written in YAML.  One feature of
343 That means one text file can appear to the linker as multiple .o files - the
344 normal case for the linker.