Lines Matching refs:native

24 treates LLVM bitcode files like native object files and allows mixing and
41 * Input source file ``main.c`` is compiled into native object code.
91   % clang -c main.c -o main.o        # <-- main.o is native object file
140 looking at the definitions and uses of symbols in native .o files and using
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
155 object file is found to not be a native object file.  If ``lto_module_create()``
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
189 In this phase, the linker reads optimized a native object file and updates the
215 A non-native object file is handled via an ``lto_module_t``.  The following
241 The linker can introspect the non-native object file by getting the number of
255 Once the linker has loaded each non-native object files into an
257 native object file.  This is done in a couple of steps.  First, a code generator
264 Then, each non-native object file is added to the code generator with:
283 And each symbol that is referenced by a native object file or otherwise must not
290 After all these settings are done, the linker requests that a native object file
297 which returns a pointer to a buffer containing the generated native object file.
298 The linker then parses that and links it with the rest of the native object