1 <?xml version=
"1.0" encoding=
"utf-8" ?>
2 <!DOCTYPE html PUBLIC
"-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3 <html xmlns=
"http://www.w3.org/1999/xhtml" xml:
lang=
"en" lang=
"en">
5 <meta http-equiv=
"Content-Type" content=
"text/html; charset=utf-8" />
6 <meta name=
"generator" content=
"Docutils 0.5: http://docutils.sourceforge.net/" />
7 <title>Tutorial - Using LLVMC
</title>
8 <link rel=
"stylesheet" href=
"llvm.css" type=
"text/css" />
11 <div class=
"document" id=
"tutorial-using-llvmc">
12 <h1 class=
"title">Tutorial - Using LLVMC
</h1>
14 <!-- This file was automatically generated by rst2html.
15 Please do not edit directly!
16 The ReST source lives in the directory 'tools/llvmc/doc'. -->
17 <div class=
"contents topic" id=
"contents">
18 <p class=
"topic-title first">Contents
</p>
20 <li><a class=
"reference internal" href=
"#introduction" id=
"id1">Introduction
</a></li>
21 <li><a class=
"reference internal" href=
"#compiling-with-llvmc" id=
"id2">Compiling with LLVMC
</a></li>
22 <li><a class=
"reference internal" href=
"#using-llvmc-to-generate-toolchain-drivers" id=
"id3">Using LLVMC to generate toolchain drivers
</a></li>
25 <div class=
"doc_author">
26 <p>Written by
<a href=
"mailto:foldr@codedgers.com">Mikhail Glushenkov
</a></p>
27 </div><div class=
"section" id=
"introduction">
28 <h1><a class=
"toc-backref" href=
"#id1">Introduction
</a></h1>
29 <p>LLVMC is a generic compiler driver, which plays the same role for LLVM
30 as the
<tt class=
"docutils literal"><span class=
"pre">gcc
</span></tt> program does for GCC - the difference being that LLVMC
31 is designed to be more adaptable and easier to customize. Most of
32 LLVMC functionality is implemented via plugins, which can be loaded
33 dynamically or compiled in. This tutorial describes the basic usage
34 and configuration of LLVMC.
</p>
36 <div class=
"section" id=
"compiling-with-llvmc">
37 <h1><a class=
"toc-backref" href=
"#id2">Compiling with LLVMC
</a></h1>
38 <p>In general, LLVMC tries to be command-line compatible with
<tt class=
"docutils literal"><span class=
"pre">gcc
</span></tt> as
39 much as possible, so most of the familiar options work:
</p>
40 <pre class=
"literal-block">
41 $ llvmc -O3 -Wall hello.cpp
45 <p>This will invoke
<tt class=
"docutils literal"><span class=
"pre">llvm-g++
</span></tt> under the hood (you can see which
46 commands are executed by using the
<tt class=
"docutils literal"><span class=
"pre">-v
</span></tt> option). For further help on
47 command-line LLVMC usage, refer to the
<tt class=
"docutils literal"><span class=
"pre">llvmc
</span> <span class=
"pre">--help
</span></tt> output.
</p>
49 <div class=
"section" id=
"using-llvmc-to-generate-toolchain-drivers">
50 <h1><a class=
"toc-backref" href=
"#id3">Using LLVMC to generate toolchain drivers
</a></h1>
51 <p>LLVMC plugins are written mostly using
<a class=
"reference external" href=
"http://llvm.cs.uiuc.edu/docs/TableGenFundamentals.html">TableGen
</a>, so you need to
52 be familiar with it to get anything done.
</p>
53 <p>Start by compiling
<tt class=
"docutils literal"><span class=
"pre">plugins/Simple/Simple.td
</span></tt>, which is a primitive
54 wrapper for
<tt class=
"docutils literal"><span class=
"pre">gcc
</span></tt>:
</p>
55 <pre class=
"literal-block">
56 $ cd $LLVM_DIR/tools/llvmc
57 $ make DRIVER_NAME=mygcc BUILTIN_PLUGINS=Simple
64 <p>Here we link our plugin with the LLVMC core statically to form an
65 executable file called
<tt class=
"docutils literal"><span class=
"pre">mygcc
</span></tt>. It is also possible to build our
66 plugin as a standalone dynamic library; this is described in the
68 <p>Contents of the file
<tt class=
"docutils literal"><span class=
"pre">Simple.td
</span></tt> look like this:
</p>
69 <pre class=
"literal-block">
70 // Include common definitions
71 include
"llvm/CompilerDriver/Common.td
"
75 [(in_language
"c
"),
76 (out_language
"executable
"),
77 (output_suffix
"out
"),
78 (cmd_line
"gcc $INFILE -o $OUTFILE
"),
83 def LanguageMap : LanguageMap
<[LangToSuffixes
<"c
", [
"c
"]
>]
>;
86 def CompilationGraph : CompilationGraph
<[Edge
<"root
",
"gcc
">]
>;
88 <p>As you can see, this file consists of three parts: tool descriptions,
89 language map, and the compilation graph definition.
</p>
90 <p>At the heart of LLVMC is the idea of a compilation graph: vertices in
91 this graph are tools, and edges represent a transformation path
92 between two tools (for example, assembly source produced by the
93 compiler can be transformed into executable code by an assembler). The
94 compilation graph is basically a list of edges; a special node named
95 <tt class=
"docutils literal"><span class=
"pre">root
</span></tt> is used to mark graph entry points.
</p>
96 <p>Tool descriptions are represented as property lists: most properties
97 in the example above should be self-explanatory; the
<tt class=
"docutils literal"><span class=
"pre">sink
</span></tt> property
98 means that all options lacking an explicit description should be
99 forwarded to this tool.
</p>
100 <p>The
<tt class=
"docutils literal"><span class=
"pre">LanguageMap
</span></tt> associates a language name with a list of suffixes
101 and is used for deciding which toolchain corresponds to a given input
103 <p>To learn more about LLVMC customization, refer to the reference
104 manual and plugin source code in the
<tt class=
"docutils literal"><span class=
"pre">plugins
</span></tt> directory.
</p>
107 <a href=
"http://jigsaw.w3.org/css-validator/check/referer">
108 <img src=
"http://jigsaw.w3.org/css-validator/images/vcss-blue"
109 alt=
"Valid CSS" /></a>
110 <a href=
"http://validator.w3.org/check?uri=referer">
111 <img src=
"http://www.w3.org/Icons/valid-xhtml10-blue"
112 alt=
"Valid XHTML 1.0 Transitional"/></a>
114 <a href=
"mailto:foldr@codedgers.com">Mikhail Glushenkov
</a><br />
115 <a href=
"http://llvm.org">LLVM Compiler Infrastructure
</a><br />
117 Last modified: $Date:
2008-
12-
11 11:
34:
48 -
0600 (Thu,
11 Dec
2008) $