Home | History | Annotate | Download | only in docs

Lines Matching full:bitcode

22     <li><a href="#phase1">Phase 1 : Read LLVM Bitcode Files</a></li>

24 <li><a href="#phase3">Phase 3 : Optimize Bitcode Files</a></li>
65 treates LLVM bitcode files like native object files and allows mixing and
67 object, to handle LLVM bitcode files. This tight integration between
84 <li> Input source file <tt>a.c</tt> is compiled into LLVM bitcode form.
130 $ clang -emit-llvm -c a.c -o a.o # &lt;-- a.o is LLVM bitcode file
137 externally visible symbol defined in LLVM bitcode file. The linker
206 <a name="phase1">Phase 1 : Read LLVM Bitcode Files</a>
211 symbol information. This includes native object files as well as LLVM bitcode
215 <tt>lto_module_create()</tt> returns that the file is an LLVM bitcode file,
237 does not know the exact content of input LLVM bitcode files. If dead code
244 <a name="phase3">Phase 3 : Optimize Bitcode Files</a>
252 which returns a native object file creating by merging the LLVM bitcode files
266 LLVM bitcode files. In the example above, the linker notes that
271 bitcode files.</p>