Lines Matching full:files

24 treats LLVM bitcode files like native object files and allows mixing and
26 bitcode files. This tight integration between the linker and LLVM optimizer
120 **Use separate tool to collect symbol information from all object files.**
140 looking at the definitions and uses of symbols in native .o files and using
148 Phase 1 : Read LLVM Bitcode Files
151 The linker first reads all object files in natural order and collects symbol
152 information. This includes native object files as well as LLVM bitcode files.
153 To minimize the cost to the linker in the case that all .o files are native
154 object files, the linker only calls ``lto_module_create()`` when a supplied
172 content of input LLVM bitcode files. If dead code stripping is enabled then the
175 Phase 3 : Optimize Bitcode Files
179 are needed by native object files. In the example above, the linker reports
180 that only ``foo1()`` is used by native object files using
183 native object file creating by merging the LLVM bitcode files and applying
192 files. In the example above, the linker notes that ``foo4()`` is not used any
197 files.
210 their object files and the standard linker tool.
252 Tools working with object files on Darwin (e.g. lipo) may need to know properties like the CPU type:
261 Once the linker has loaded each non-native object files into an
305 files.