1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
4 <title>Using The LLVM Libraries</title>
5 <link rel="stylesheet" href="llvm.css" type="text/css">
8 <div class="doc_title">Using The LLVM Libraries</div>
10 <li><a href="#abstract">Abstract</a></li>
11 <li><a href="#introduction">Introduction</a></li>
12 <li><a href="#descriptions">Library Descriptions</a></li>
13 <li><a href="#dependencies">Library Dependencies</a></li>
14 <li><a href="#rot">Linkage Rules Of Thumb</a>
16 <li><a href="#always">Always link LLVMCore, LLVMSupport, LLVMSystem</a>
17 <li><a href="#onlyone">Never link both archive and re-linked</a>
22 <div class="doc_author">
23 <p>Written by <a href="mailto:rspencer@x10sys.com">Reid Spencer</a></p>
26 <p class="doc_warning">Warning: This document is out of date, please see <a href="CommandGuide/html/llvm-config.html">llvm-config</a> for more information.</p>
28 <!-- ======================================================================= -->
29 <div class="doc_section"><a name="abstract">Abstract</a></div>
30 <div class="doc_text">
31 <p>Amongst other things, LLVM is a toolkit for building compilers, linkers,
32 runtime executives, virtual machines, and other program execution related
33 tools. In addition to the LLVM tool set, the functionality of LLVM is
34 available through a set of libraries. To use LLVM as a toolkit for
35 constructing tools, a developer needs to understand what is contained in the
36 various libraries, what they depend on, and how to use them. Fortunately,
37 there is a tool, <tt>llvm-config</tt> to aid with this. This document
38 describes the contents of the libraries and how to use <tt>llvm-config</tt>
39 to generate command line options.
43 <!-- ======================================================================= -->
44 <div class="doc_section"> <a name="introduction">Introduction</a></div>
45 <div class="doc_text">
46 <p>If you're writing a compiler, virtual machine, or any other utility based
47 on LLVM, you'll need to figure out which of the many libraries files you will
48 need to link with to be successful. An understanding of the contents of these
49 libraries will be useful in coming up with an optimal specification for the
50 libraries to link with. The purpose of this document is to reduce some of
51 the trial and error that the author experienced in using LLVM.</p>
52 <p>LLVM produces two types of libraries: archives (ending in <tt>.a</tt>) and
53 objects (ending in <tt>.o</tt>). However, both are libraries. Libraries ending
54 in <tt>.o</tt> are known as re-linked libraries because they contain all the
55 compilation units of the library linked together as a single <tt>.o</tt> file.
56 Furthermore, several of the libraries have <em>both</em> forms of library. The
57 re-linked libraries are used whenever you want to include all symbols from the
58 library. The archive libraries are used whenever you want to only resolve
59 outstanding symbols at that point in the link without including everything in
61 <p>If you're using the LLVM Makefile system to link your tools,you will use
62 the <tt>LLVMLIBS</tt> make variable.
63 (see the <a href="MakefileGuide.html#LLVMLIBS">Makefile Guide</a> for
64 details). This variable specifies which LLVM libraries to link into your tool
65 and the order in which they will be linked. You specify re-linked libraries by
66 naming the library without a suffix. You specify archive libraries by naming
67 the library with a <tt>.a</tt> suffix but without the <tt>lib</tt> prefix. The
68 order in which the libraries appear in the <tt>LLVMLIBS</tt> variable
69 definition is the order in which they will be linked. Getting this order
70 correct for your tool can sometimes be challenging.
72 <!-- ======================================================================= -->
73 <div class="doc_section"><a name="descriptions"></a>Library Descriptions</div>
74 <div class="doc_text">
75 <p>The table below categorizes each library
76 <table style="text-align:left">
77 <tr><th>Library</th><th>Forms</th><th>Description</th></tr>
78 <tr><th colspan="3">Core Libraries</th></tr>
79 <tr><td>LLVMArchive</td><td><tt>.a</tt></td>
80 <td>LLVM archive reading and writing</td></tr>
81 <tr><td>LLVMAsmParser</td><td><tt>.a</tt></td>
82 <td>LLVM assembly parsing</td></tr>
83 <tr><td>LLVMBCReader</td><td><tt>.a</tt></td>
84 <td>LLVM bytecode reading</td></tr>
85 <tr><td>LLVMBCWriter</td><td><tt>.a</tt></td>
86 <td>LLVM bytecode writing</td></tr>
87 <tr><td>LLVMCore</td><td><tt>.a</tt></td>
88 <td>LLVM core intermediate representation</td></tr>
89 <tr><td>LLVMDebugger</td><td><tt>.a</tt></td>
90 <td>Source level debugging support</td></tr>
91 <tr><td>LLVMLinker</td><td><tt>.a</tt></td>
92 <td>Bytecode and archive linking interface</td></tr>
93 <tr><td>LLVMSupport</td><td><tt>.a</tt></td>
94 <td>General support utilities</td></tr>
95 <tr><td>LLVMSystem</td><td><tt>.a</tt></td>
96 <td>Operating system abstraction layer</td></tr>
97 <tr><td>LLVMbzip2</td><td><tt>.a</tt></td>
98 <td>BZip2 compression library</td></tr>
100 <tr><th colspan="3">Analysis Libraries</th></tr>
101 <tr><td>LLVMAnalysis</td><td><tt>.a</tt></td>
102 <td>Various analysis passes.</td></tr>
103 <tr><td>LLVMDataStructure</td><td><tt>.o</tt></td>
104 <td>Data structure analysis passes.</td></tr>
105 <tr><td>LLVMipa</td><td><tt>.a</tt></td>
106 <td>Inter-procedural analysis passes.</td></tr>
108 <tr><th colspan="3">Transformation Libraries</th></tr>
109 <tr><td>LLVMInstrumentation</td><td><tt>.a</tt></td>
110 <td>Instrumentation passes.</td></tr>
111 <tr><td>LLVMipo</td><td><tt>.a</tt></td>
112 <td>All inter-procedural optimization passes.</td></tr>
113 <tr><td>LLVMScalarOpts</td><td><tt>.a</tt></td>
114 <td>All scalar optimization passes.</td></tr>
115 <tr><td>LLVMTransforms</td><td><tt>.a</tt></td>
116 <td>Uncategorized transformation passes.</td></tr>
117 <tr><td>LLVMTransformUtils</td><td><tt>.a</tt></td>
118 <td>Transformation utilities.</td></tr>
120 <tr><th colspan="3">Code Generation Libraries </th></tr>
121 <tr><td>LLVMCodeGen</td><td><tt>.o</tt></td>
122 <td>Native code generation infrastructure</td></tr>
123 <tr><td>LLVMSelectionDAG</td><td><tt>.o</tt></td>
124 <td>Aggressive instruction selector for directed acyclic graphs</td></tr>
126 <tr><th colspan="3">Target Libraries</th></tr>
127 <tr><td>LLVMAlpha</td><td><tt>.o</tt></td>
128 <td>Code generation for Alpha architecture</td></tr>
129 <tr><td>LLVMARM</td><td><tt>.o</tt></td>
130 <td>Code generation for ARM architecture</td></tr>
131 <tr><td>LLVMCBackend</td><td><tt>.o</tt></td>
132 <td>'C' language code generator.</td></tr>
133 <tr><td>LLVMIA64</td><td><tt>.o</tt></td>
134 <td>Code generation for IA64 architecture</td></tr>
135 <tr><td>LLVMPowerPC</td><td><tt>.o</tt></td>
136 <td>Code generation for PowerPC architecture</td></tr>
137 <tr><td>LLVMSparc</td><td><tt>.o</tt></td>
138 <td>Code generation for Sparc architecture</td></tr>
139 <tr><td>LLVMTarget</td><td><tt>.a</tt></td>
140 <td>Generic code generation utilities.</td></tr>
141 <tr><td>LLVMX86</td><td><tt>.o</tt></td>
142 <td>Code generation for Intel x86 architecture</td></tr>
144 <tr><th colspan="3">Runtime Libraries</th></tr>
145 <tr><td>LLVMInterpreter</td><td><tt>.o</tt></td>
146 <td>Bytecode Interpreter</td></tr>
147 <tr><td>LLVMJIT</td><td><tt>.o</tt></td>
148 <td>Bytecode JIT Compiler</td></tr>
149 <tr><td>LLVMExecutionEngine</td><td><tt>.o</tt></td>
150 <td>Virtual machine engine</td></tr>
154 <!-- ======================================================================= -->
155 <div class="doc_section"><a name="dependencies"></a>Using llvm-config</div>
156 <div class="doc_text">
157 <p>The <tt>llvm-config</tt> tool is a perl script that produces on its output
158 various kinds of information. For example, the source or object directories
159 used to build LLVM can be accessed by passing options to <tt>llvm-config</tt>.
160 For complete details on this tool, please see the
161 <a href="CommandGuide/html/llvm-config.html">manual page</a>.</p>
162 <p>To understand the relationships between libraries, the <tt>llvm-config</tt>
163 can be very useful. If all you know is that you want certain libraries to
164 be available, you can generate the complete set of libraries to link with
165 using one of four options, as below:</p>
167 <li><tt>--ldflags</tt>. This generates the command line options necessary to
168 be passed to the <tt>ld</tt> tool in order to link with LLVM. Most notably,
169 the <tt>-L</tt> option is provided to specify a library search directory
170 that contains the LLVM libraries.</li>
171 <li><tt>--libs</tt>. This generates command line options suitable for
172 use with a gcc-style linker. That is, libraries are given with a -l option
173 and object files are given with a full path.</li>
174 <li><tt>--libnames</tt>. This generates a list of just the library file
175 names. If you know the directory in which these files reside (see --ldflags)
176 then you can find the libraries there.</li>
177 <li><tt>--libfiles</tt>. This generates the full path names of the
178 LLVM library files.</li>
180 <p>If you wish to delve further into how <tt>llvm-config</tt> generates the
181 correct order (based on library dependencies), please see the tool named
182 <tt>GenLibDeps.pl</tt> in the <tt>utils</tt> source directory of LLVM.</p>
184 <!-- =======NOTE: =========================================================-->
185 <!-- === The following graphs and <dl> list are generated automatically ===-->
186 <!-- === by the util named GenLibDeps.pl in the llvm/utils directory. ===-->
187 <!-- === This should be updated whenever new libraries are added, ===-->
188 <!-- === removed, or changed ===-->
189 <!-- =======NOTE: =========================================================-->
190 <h2>Dependency Relationships Of Libraries</h2>
191 <p>This graph shows the dependency of archive libraries on other archive
192 libraries or objects. Where a library has both archive and object forms, only
193 the archive form is shown.</p>
194 <img src="img/libdeps.gif" alt="Library Dependencies"/>
195 <h2>Dependency Relationships Of Object Files</h2>
196 <p>This graph shows the dependency of object files on archive libraries or
197 other objects. Where a library has both object and archive forms, only the
198 dependency to the archive form is shown.</p>
199 <img src="img/objdeps.gif" alt="Object File Dependencies"/>
200 <p>The following list shows the dependency relationships between libraries in
201 textual form. The information is the same as shown on the graphs but arranged
204 <dt><b>libLLVMAnalysis.a</b</dt><dd><ul>
205 <li>libLLVMCore.a</li>
206 <li>libLLVMSupport.a</li>
207 <li>libLLVMSystem.a</li>
208 <li>libLLVMTarget.a</li>
210 <dt><b>libLLVMArchive.a</b</dt><dd><ul>
211 <li>libLLVMBCReader.a</li>
212 <li>libLLVMCore.a</li>
213 <li>libLLVMSupport.a</li>
214 <li>libLLVMSystem.a</li>
216 <dt><b>libLLVMAsmParser.a</b</dt><dd><ul>
217 <li>libLLVMCore.a</li>
218 <li>libLLVMSupport.a</li>
219 <li>libLLVMSystem.a</li>
221 <dt><b>libLLVMBCReader.a</b</dt><dd><ul>
222 <li>libLLVMCore.a</li>
223 <li>libLLVMSupport.a</li>
224 <li>libLLVMSystem.a</li>
226 <dt><b>libLLVMBCWriter.a</b</dt><dd><ul>
227 <li>libLLVMCore.a</li>
228 <li>libLLVMSupport.a</li>
229 <li>libLLVMSystem.a</li>
231 <dt><b>libLLVMCodeGen.a</b</dt><dd><ul>
232 <li>libLLVMAnalysis.a</li>
233 <li>libLLVMCore.a</li>
234 <li>libLLVMSupport.a</li>
235 <li>libLLVMSystem.a</li>
236 <li>libLLVMTarget.a</li>
238 <dt><b>libLLVMCore.a</b</dt><dd><ul>
239 <li>libLLVMSupport.a</li>
240 <li>libLLVMSystem.a</li>
242 <dt><b>libLLVMDebugger.a</b</dt><dd><ul>
243 <li>libLLVMBCReader.a</li>
244 <li>libLLVMCore.a</li>
245 <li>libLLVMSupport.a</li>
246 <li>libLLVMSystem.a</li>
248 <dt><b>libLLVMInstrumentation.a</b</dt><dd><ul>
249 <li>libLLVMCore.a</li>
250 <li>libLLVMScalarOpts.a</li>
251 <li>libLLVMSupport.a</li>
252 <li>libLLVMTransformUtils.a</li>
254 <dt><b>libLLVMLinker.a</b</dt><dd><ul>
255 <li>libLLVMArchive.a</li>
256 <li>libLLVMBCReader.a</li>
257 <li>libLLVMCore.a</li>
258 <li>libLLVMSystem.a</li>
260 <dt><b>libLLVMScalarOpts.a</b</dt><dd><ul>
261 <li>libLLVMAnalysis.a</li>
262 <li>libLLVMCore.a</li>
263 <li>libLLVMSupport.a</li>
264 <li>libLLVMSystem.a</li>
265 <li>libLLVMTarget.a</li>
266 <li>libLLVMTransformUtils.a</li>
268 <dt><b>libLLVMSelectionDAG.a</b</dt><dd><ul>
269 <li>libLLVMCodeGen.a</li>
270 <li>libLLVMCore.a</li>
271 <li>libLLVMSupport.a</li>
272 <li>libLLVMSystem.a</li>
273 <li>libLLVMTarget.a</li>
274 <li>libLLVMTransformUtils.a</li>
276 <dt><b>libLLVMSupport.a</b</dt><dd><ul>
277 <li>libLLVMSystem.a</li>
278 <li>libLLVMbzip2.a</li>
280 <dt><b>libLLVMSystem.a</b</dt><dd></dd>
281 <dt><b>libLLVMTarget.a</b</dt><dd><ul>
282 <li>libLLVMCodeGen.a</li>
283 <li>libLLVMCore.a</li>
284 <li>libLLVMSelectionDAG.a</li>
285 <li>libLLVMSupport.a</li>
286 <li>libLLVMSystem.a</li>
288 <dt><b>libLLVMTransformUtils.a</b</dt><dd><ul>
289 <li>libLLVMAnalysis.a</li>
290 <li>libLLVMCore.a</li>
291 <li>libLLVMScalarOpts.a</li>
292 <li>libLLVMSupport.a</li>
293 <li>libLLVMSystem.a</li>
294 <li>libLLVMipa.a</li>
296 <dt><b>libLLVMTransforms.a</b</dt><dd><ul>
297 <li>libLLVMCore.a</li>
298 <li>libLLVMSupport.a</li>
299 <li>libLLVMTarget.a</li>
300 <li>libLLVMTransformUtils.a</li>
302 <dt><b>libLLVMbzip2.a</b</dt><dd></dd>
303 <dt><b>libLLVMipa.a</b</dt><dd><ul>
304 <li>libLLVMAnalysis.a</li>
305 <li>libLLVMCore.a</li>
306 <li>libLLVMSupport.a</li>
307 <li>libLLVMSystem.a</li>
309 <dt><b>libLLVMipo.a</b</dt><dd><ul>
310 <li>libLLVMAnalysis.a</li>
311 <li>libLLVMCore.a</li>
312 <li>libLLVMSupport.a</li>
313 <li>libLLVMSystem.a</li>
314 <li>libLLVMTarget.a</li>
315 <li>libLLVMTransformUtils.a</li>
316 <li>libLLVMipa.a</li>
318 <dt><b>LLVMARM.o</b</dt><dd><ul>
319 <li>libLLVMCodeGen.a</li>
320 <li>libLLVMCore.a</li>
321 <li>libLLVMScalarOpts.a</li>
322 <li>libLLVMSelectionDAG.a</li>
323 <li>libLLVMSupport.a</li>
324 <li>libLLVMSystem.a</li>
325 <li>libLLVMTarget.a</li>
327 <dt><b>LLVMAlpha.o</b</dt><dd><ul>
328 <li>libLLVMCodeGen.a</li>
329 <li>libLLVMCore.a</li>
330 <li>libLLVMScalarOpts.a</li>
331 <li>libLLVMSelectionDAG.a</li>
332 <li>libLLVMSupport.a</li>
333 <li>libLLVMSystem.a</li>
334 <li>libLLVMTarget.a</li>
336 <dt><b>LLVMCBackend.o</b</dt><dd><ul>
337 <li>libLLVMAnalysis.a</li>
338 <li>libLLVMCodeGen.a</li>
339 <li>libLLVMCore.a</li>
340 <li>libLLVMScalarOpts.a</li>
341 <li>libLLVMSupport.a</li>
342 <li>libLLVMSystem.a</li>
343 <li>libLLVMTarget.a</li>
344 <li>libLLVMipa.a</li>
346 <dt><b>LLVMDataStructure.o</b</dt><dd><ul>
347 <li>libLLVMAnalysis.a</li>
348 <li>libLLVMCore.a</li>
349 <li>libLLVMSupport.a</li>
350 <li>libLLVMSystem.a</li>
351 <li>libLLVMTarget.a</li>
353 <dt><b>LLVMExecutionEngine.o</b</dt><dd><ul>
354 <li>libLLVMCore.a</li>
355 <li>libLLVMSupport.a</li>
356 <li>libLLVMSystem.a</li>
357 <li>libLLVMTarget.a</li>
359 <dt><b>LLVMIA64.o</b</dt><dd><ul>
360 <li>libLLVMCodeGen.a</li>
361 <li>libLLVMCore.a</li>
362 <li>libLLVMScalarOpts.a</li>
363 <li>libLLVMSelectionDAG.a</li>
364 <li>libLLVMSupport.a</li>
365 <li>libLLVMSystem.a</li>
366 <li>libLLVMTarget.a</li>
368 <dt><b>LLVMInterpreter.o</b</dt><dd><ul>
369 <li>LLVMExecutionEngine.o</li>
370 <li>libLLVMCore.a</li>
371 <li>libLLVMSupport.a</li>
372 <li>libLLVMSystem.a</li>
373 <li>libLLVMTarget.a</li>
375 <dt><b>LLVMJIT.o</b</dt><dd><ul>
376 <li>LLVMExecutionEngine.o</li>
377 <li>libLLVMCodeGen.a</li>
378 <li>libLLVMCore.a</li>
379 <li>libLLVMSupport.a</li>
380 <li>libLLVMSystem.a</li>
381 <li>libLLVMTarget.a</li>
383 <dt><b>LLVMPowerPC.o</b</dt><dd><ul>
384 <li>libLLVMCodeGen.a</li>
385 <li>libLLVMCore.a</li>
386 <li>libLLVMScalarOpts.a</li>
387 <li>libLLVMSelectionDAG.a</li>
388 <li>libLLVMSupport.a</li>
389 <li>libLLVMSystem.a</li>
390 <li>libLLVMTarget.a</li>
392 <dt><b>LLVMSparc.o</b</dt><dd><ul>
393 <li>libLLVMCodeGen.a</li>
394 <li>libLLVMCore.a</li>
395 <li>libLLVMScalarOpts.a</li>
396 <li>libLLVMSelectionDAG.a</li>
397 <li>libLLVMSupport.a</li>
398 <li>libLLVMSystem.a</li>
399 <li>libLLVMTarget.a</li>
401 <dt><b>LLVMX86.o</b</dt><dd><ul>
402 <li>libLLVMCodeGen.a</li>
403 <li>libLLVMCore.a</li>
404 <li>libLLVMScalarOpts.a</li>
405 <li>libLLVMSelectionDAG.a</li>
406 <li>libLLVMSupport.a</li>
407 <li>libLLVMSystem.a</li>
408 <li>libLLVMTarget.a</li>
413 <!-- ======================================================================= -->
414 <div class="doc_section"><a name="rot">Linkage Rules Of Thumb</a></div>
415 <div class="doc_text">
416 <p>This section contains various "rules of thumb" about what files you
417 should link into your programs.</p>
419 <!-- ======================================================================= -->
420 <div class="doc_subsection"><a name="always">Always Link LLVMCore, LLVMSupport,
421 and LLVMSystem</a></div>
422 <div class="doc_text">
423 <p>No matter what you do with LLVM, the last three entries in the value of
424 your LLVMLIBS make variable should always be:
425 <tt>LLVMCore LLVMSupport.a LLVMSystem.a</tt>. There are no <tt>LLVM</tt>
426 programs that don't depend on these three.</p>
428 <!-- ======================================================================= -->
429 <div class="doc_subsection"><a name="onlyone">Never link both archive and
430 re-linked library</a></div>
431 <div class="doc_text">
432 <p>There is never any point to linking both the re-linked (<tt>.o</tt>) and
433 the archive (<tt>.a</tt>) versions of a library. Since the re-linked version
434 includes the entire library, the archive version will not resolve any symbols.
435 You could even end up with link error if you place the archive version before
436 the re-linked version on the linker's command line.</p>
438 <!-- ======================================================================= -->
440 <div class="doc_footer">
442 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
443 src="http://jigsaw.w3.org/css-validator/images/vcss" alt="Valid CSS!"/></a>
444 <a href="http://validator.w3.org/check/referer"><img
445 src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" /></a>
446 <a href="mailto:rspencer@x10sys.com">Reid Spencer</a>
448 <a href="http://llvm.org">The LLVM Compiler Infrastructure</a>
449 <br>Last modified: $Date$ </div>
452 <!-- vim: sw=2 ts=2 ai