Gitiles
Code Review Sign In
gerrit-public.fairphone.software / fp2-dev / platform / external / llvm / 4429aaf12f5c0c7a3718e5abf9edfa52a1fcdb8a / . / docs / CompilerDriver.html
blob: 5830a30833d6243e75259de168befcda82dd8784 [file] [log] [blame]
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]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">
Reid Spencerb1254a12004-08-09 03:08:29 +0000[diff] [blame]4<head>
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]5<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
Mikhail Glushenkovd6d2efc2009-05-06 01:41:47 +0000[diff] [blame]6<meta name="generator" content="Docutils 0.5: http://docutils.sourceforge.net/" />
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]7<title>Customizing LLVMC: Reference Manual</title>
Mikhail Glushenkov8cc82882008-12-13 17:50:58 +0000[diff] [blame]8<link rel="stylesheet" href="llvm.css" type="text/css" />
Reid Spencerb1254a12004-08-09 03:08:29 +0000[diff] [blame]9</head>
10<body>
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]11<div class="document" id="customizing-llvmc-reference-manual">
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]12<h1 class="title">Customizing LLVMC: Reference Manual</h1>
Mikhail Glushenkovd6d2efc2009-05-06 01:41:47 +0000[diff] [blame]13
Mikhail Glushenkov23f522a2008-12-13 17:51:47 +0000[diff] [blame]14<!-- This file was automatically generated by rst2html.
15Please do not edit directly!
16The ReST source lives in the directory 'tools/llvmc/doc'. -->
Mikhail Glushenkovd6d2efc2009-05-06 01:41:47 +0000[diff] [blame]17<div class="contents topic" id="contents">
18<p class="topic-title first">Contents</p>
Mikhail Glushenkovd5652032008-12-13 02:28:58 +0000[diff] [blame]19<ul class="simple">
Mikhail Glushenkovd6d2efc2009-05-06 01:41:47 +0000[diff] [blame]20<li><a class="reference internal" href="#introduction" id="id4">Introduction</a></li>
21<li><a class="reference internal" href="#compiling-with-llvmc" id="id5">Compiling with LLVMC</a></li>
22<li><a class="reference internal" href="#predefined-options" id="id6">Predefined options</a></li>
23<li><a class="reference internal" href="#compiling-llvmc-plugins" id="id7">Compiling LLVMC plugins</a></li>
Mikhail Glushenkov502106a2009-06-16 00:14:20 +0000[diff] [blame]24<li><a class="reference internal" href="#compiling-standalone-llvmc-based-drivers" id="id8">Compiling standalone LLVMC-based drivers</a></li>
25<li><a class="reference internal" href="#customizing-llvmc-the-compilation-graph" id="id9">Customizing LLVMC: the compilation graph</a></li>
26<li><a class="reference internal" href="#describing-options" id="id10">Describing options</a><ul>
27<li><a class="reference internal" href="#external-options" id="id11">External options</a></li>
Mikhail Glushenkovd5652032008-12-13 02:28:58 +0000[diff] [blame]28</ul>
29</li>
Mikhail Glushenkov502106a2009-06-16 00:14:20 +0000[diff] [blame]30<li><a class="reference internal" href="#conditional-evaluation" id="id12">Conditional evaluation</a></li>
31<li><a class="reference internal" href="#writing-a-tool-description" id="id13">Writing a tool description</a><ul>
32<li><a class="reference internal" href="#actions" id="id14">Actions</a></li>
Mikhail Glushenkovd5652032008-12-13 02:28:58 +0000[diff] [blame]33</ul>
34</li>
Mikhail Glushenkov502106a2009-06-16 00:14:20 +0000[diff] [blame]35<li><a class="reference internal" href="#language-map" id="id15">Language map</a></li>
36<li><a class="reference internal" href="#more-advanced-topics" id="id16">More advanced topics</a><ul>
37<li><a class="reference internal" href="#hooks-and-environment-variables" id="id17">Hooks and environment variables</a></li>
38<li><a class="reference internal" href="#how-plugins-are-loaded" id="id18">How plugins are loaded</a></li>
39<li><a class="reference internal" href="#debugging" id="id19">Debugging</a></li>
Mikhail Glushenkove25b8452009-06-30 00:16:43 +0000[diff] [blame]40<li><a class="reference internal" href="#conditioning-on-the-executable-name" id="id20">Conditioning on the executable name</a></li>
Mikhail Glushenkovd5652032008-12-13 02:28:58 +0000[diff] [blame]41</ul>
42</li>
43</ul>
44</div>
45<div class="doc_author">
46<p>Written by <a href="mailto:foldr@codedgers.com">Mikhail Glushenkov</a></p>
Mikhail Glushenkovd6d2efc2009-05-06 01:41:47 +0000[diff] [blame]47</div><div class="section" id="introduction">
48<h1><a class="toc-backref" href="#id4">Introduction</a></h1>
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]49<p>LLVMC is a generic compiler driver, designed to be customizable and
50extensible. It plays the same role for LLVM as the <tt class="docutils literal"><span class="pre">gcc</span></tt> program
51does for GCC - LLVMC's job is essentially to transform a set of input
52files into a set of targets depending on configuration rules and user
53options. What makes LLVMC different is that these transformation rules
54are completely customizable - in fact, LLVMC knows nothing about the
55specifics of transformation (even the command-line options are mostly
56not hard-coded) and regards the transformation structure as an
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]57abstract graph. The structure of this graph is completely determined
58by plugins, which can be either statically or dynamically linked. This
59makes it possible to easily adapt LLVMC for other purposes - for
60example, as a build tool for game resources.</p>
Mikhail Glushenkov63dc3182009-06-17 02:56:48 +0000[diff] [blame]61<p>Because LLVMC employs <a class="reference external" href="http://llvm.org/docs/TableGenFundamentals.html">TableGen</a> as its configuration language, you
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]62need to be familiar with it to customize LLVMC.</p>
Reid Spencerb1254a12004-08-09 03:08:29 +0000[diff] [blame]63</div>
Mikhail Glushenkovd6d2efc2009-05-06 01:41:47 +0000[diff] [blame]64<div class="section" id="compiling-with-llvmc">
65<h1><a class="toc-backref" href="#id5">Compiling with LLVMC</a></h1>
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]66<p>LLVMC tries hard to be as compatible with <tt class="docutils literal"><span class="pre">gcc</span></tt> as possible,
67although there are some small differences. Most of the time, however,
68you shouldn't be able to notice them:</p>
69<pre class="literal-block">
70$ # This works as expected:
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]71$ llvmc -O3 -Wall hello.cpp
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]72$ ./a.out
73hello
74</pre>
Mikhail Glushenkov63dc3182009-06-17 02:56:48 +0000[diff] [blame]75<p>One nice feature of LLVMC is that one doesn't have to distinguish between
76different compilers for different languages (think <tt class="docutils literal"><span class="pre">g++</span></tt> vs. <tt class="docutils literal"><span class="pre">gcc</span></tt>) - the
77right toolchain is chosen automatically based on input language names (which
78are, in turn, determined from file extensions). If you want to force files
79ending with &quot;.c&quot; to compile as C++, use the <tt class="docutils literal"><span class="pre">-x</span></tt> option, just like you would
80do it with <tt class="docutils literal"><span class="pre">gcc</span></tt>:</p>
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]81<pre class="literal-block">
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]82$ # hello.c is really a C++ file
83$ llvmc -x c++ hello.c
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]84$ ./a.out
85hello
86</pre>
87<p>On the other hand, when using LLVMC as a linker to combine several C++
88object files you should provide the <tt class="docutils literal"><span class="pre">--linker</span></tt> option since it's
89impossible for LLVMC to choose the right linker in that case:</p>
90<pre class="literal-block">
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]91$ llvmc -c hello.cpp
92$ llvmc hello.o
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]93[A lot of link-time errors skipped]
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]94$ llvmc --linker=c++ hello.o
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]95$ ./a.out
96hello
97</pre>
Mikhail Glushenkove25b8452009-06-30 00:16:43 +0000[diff] [blame]98<p>By default, LLVMC uses <tt class="docutils literal"><span class="pre">llvm-gcc</span></tt> to compile the source code. It is also
99possible to choose the <tt class="docutils literal"><span class="pre">clang</span></tt> compiler with the <tt class="docutils literal"><span class="pre">-clang</span></tt> option.</p>
Reid Spencerb1254a12004-08-09 03:08:29 +0000[diff] [blame]100</div>
Mikhail Glushenkovd6d2efc2009-05-06 01:41:47 +0000[diff] [blame]101<div class="section" id="predefined-options">
102<h1><a class="toc-backref" href="#id6">Predefined options</a></h1>
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]103<p>LLVMC has some built-in options that can't be overridden in the
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]104configuration libraries:</p>
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]105<ul class="simple">
106<li><tt class="docutils literal"><span class="pre">-o</span> <span class="pre">FILE</span></tt> - Output file name.</li>
107<li><tt class="docutils literal"><span class="pre">-x</span> <span class="pre">LANGUAGE</span></tt> - Specify the language of the following input files
108until the next -x option.</li>
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]109<li><tt class="docutils literal"><span class="pre">-load</span> <span class="pre">PLUGIN_NAME</span></tt> - Load the specified plugin DLL. Example:
110<tt class="docutils literal"><span class="pre">-load</span> <span class="pre">$LLVM_DIR/Release/lib/LLVMCSimple.so</span></tt>.</li>
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]111<li><tt class="docutils literal"><span class="pre">-v</span></tt> - Enable verbose mode, i.e. print out all executed commands.</li>
Mikhail Glushenkovd7acf732009-06-25 18:21:10 +0000[diff] [blame]112<li><tt class="docutils literal"><span class="pre">--save-temps</span></tt> - Write temporary files to the current directory and do not
113delete them on exit. This option can also take an argument: the
114<tt class="docutils literal"><span class="pre">--save-temps=obj</span></tt> switch will write files into the directory specified with
115the <tt class="docutils literal"><span class="pre">-o</span></tt> option. The <tt class="docutils literal"><span class="pre">--save-temps=cwd</span></tt> and <tt class="docutils literal"><span class="pre">--save-temps</span></tt> switches are
116both synonyms for the default behaviour.</li>
Mikhail Glushenkov4429aaf2009-07-11 19:28:00 +0000[diff] [blame^]117<li><tt class="docutils literal"><span class="pre">--temp-dir</span> <span class="pre">DIRECTORY</span></tt> - Store temporary files in the given directory. This
118directory is deleted on exit unless <tt class="docutils literal"><span class="pre">--save-temps</span></tt> is specified. If
119<tt class="docutils literal"><span class="pre">--save-temps=obj</span></tt> is also specified, <tt class="docutils literal"><span class="pre">--temp-dir</span></tt> is given the
120precedence.</li>
Mikhail Glushenkov4ad0d572009-03-27 12:58:29 +0000[diff] [blame]121<li><tt class="docutils literal"><span class="pre">--check-graph</span></tt> - Check the compilation for common errors like mismatched
122output/input language names, multiple default edges and cycles. Because of
Mikhail Glushenkov502106a2009-06-16 00:14:20 +0000[diff] [blame]123plugins, these checks can't be performed at compile-time. Exit with code zero
124if no errors were found, and return the number of found errors
125otherwise. Hidden option, useful for debugging LLVMC plugins.</li>
Mikhail Glushenkov4ad0d572009-03-27 12:58:29 +0000[diff] [blame]126<li><tt class="docutils literal"><span class="pre">--view-graph</span></tt> - Show a graphical representation of the compilation graph
127and exit. Requires that you have <tt class="docutils literal"><span class="pre">dot</span></tt> and <tt class="docutils literal"><span class="pre">gv</span></tt> programs installed. Hidden
128option, useful for debugging LLVMC plugins.</li>
129<li><tt class="docutils literal"><span class="pre">--write-graph</span></tt> - Write a <tt class="docutils literal"><span class="pre">compilation-graph.dot</span></tt> file in the current
130directory with the compilation graph description in Graphviz format (identical
Mikhail Glushenkov502106a2009-06-16 00:14:20 +0000[diff] [blame]131to the file used by the <tt class="docutils literal"><span class="pre">--view-graph</span></tt> option). The <tt class="docutils literal"><span class="pre">-o</span></tt> option can be
132used to set the output file name. Hidden option, useful for debugging LLVMC
133plugins.</li>
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]134<li><tt class="docutils literal"><span class="pre">--help</span></tt>, <tt class="docutils literal"><span class="pre">--help-hidden</span></tt>, <tt class="docutils literal"><span class="pre">--version</span></tt> - These options have
135their standard meaning.</li>
136</ul>
Reid Spencerb1254a12004-08-09 03:08:29 +0000[diff] [blame]137</div>
Mikhail Glushenkovd6d2efc2009-05-06 01:41:47 +0000[diff] [blame]138<div class="section" id="compiling-llvmc-plugins">
139<h1><a class="toc-backref" href="#id7">Compiling LLVMC plugins</a></h1>
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]140<p>It's easiest to start working on your own LLVMC plugin by copying the
141skeleton project which lives under <tt class="docutils literal"><span class="pre">$LLVMC_DIR/plugins/Simple</span></tt>:</p>
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]142<pre class="literal-block">
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]143$ cd $LLVMC_DIR/plugins
144$ cp -r Simple MyPlugin
145$ cd MyPlugin
146$ ls
147Makefile PluginMain.cpp Simple.td
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]148</pre>
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]149<p>As you can see, our basic plugin consists of only two files (not
150counting the build script). <tt class="docutils literal"><span class="pre">Simple.td</span></tt> contains TableGen
151description of the compilation graph; its format is documented in the
152following sections. <tt class="docutils literal"><span class="pre">PluginMain.cpp</span></tt> is just a helper file used to
153compile the auto-generated C++ code produced from TableGen source. It
Mikhail Glushenkovd6d2efc2009-05-06 01:41:47 +0000[diff] [blame]154can also contain hook definitions (see <a class="reference internal" href="#hooks">below</a>).</p>
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]155<p>The first thing that you should do is to change the <tt class="docutils literal"><span class="pre">LLVMC_PLUGIN</span></tt>
156variable in the <tt class="docutils literal"><span class="pre">Makefile</span></tt> to avoid conflicts (since this variable
157is used to name the resulting library):</p>
158<pre class="literal-block">
159LLVMC_PLUGIN=MyPlugin
160</pre>
161<p>It is also a good idea to rename <tt class="docutils literal"><span class="pre">Simple.td</span></tt> to something less
162generic:</p>
163<pre class="literal-block">
164$ mv Simple.td MyPlugin.td
165</pre>
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]166<p>To build your plugin as a dynamic library, just <tt class="docutils literal"><span class="pre">cd</span></tt> to its source
167directory and run <tt class="docutils literal"><span class="pre">make</span></tt>. The resulting file will be called
Mikhail Glushenkov63dc3182009-06-17 02:56:48 +0000[diff] [blame]168<tt class="docutils literal"><span class="pre">plugin_llvmc_$(LLVMC_PLUGIN).$(DLL_EXTENSION)</span></tt> (in our case,
169<tt class="docutils literal"><span class="pre">plugin_llvmc_MyPlugin.so</span></tt>). This library can be then loaded in with the
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]170<tt class="docutils literal"><span class="pre">-load</span></tt> option. Example:</p>
171<pre class="literal-block">
172$ cd $LLVMC_DIR/plugins/Simple
173$ make
Mikhail Glushenkov63dc3182009-06-17 02:56:48 +0000[diff] [blame]174$ llvmc -load $LLVM_DIR/Release/lib/plugin_llvmc_Simple.so
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]175</pre>
Mikhail Glushenkov502106a2009-06-16 00:14:20 +0000[diff] [blame]176</div>
177<div class="section" id="compiling-standalone-llvmc-based-drivers">
178<h1><a class="toc-backref" href="#id8">Compiling standalone LLVMC-based drivers</a></h1>
179<p>By default, the <tt class="docutils literal"><span class="pre">llvmc</span></tt> executable consists of a driver core plus several
180statically linked plugins (<tt class="docutils literal"><span class="pre">Base</span></tt> and <tt class="docutils literal"><span class="pre">Clang</span></tt> at the moment). You can
181produce a standalone LLVMC-based driver executable by linking the core with your
182own plugins. The recommended way to do this is by starting with the provided
183<tt class="docutils literal"><span class="pre">Skeleton</span></tt> example (<tt class="docutils literal"><span class="pre">$LLVMC_DIR/example/Skeleton</span></tt>):</p>
184<pre class="literal-block">
185$ cd $LLVMC_DIR/example/
186$ cp -r Skeleton mydriver
187$ cd mydriver
188$ vim Makefile
189[...]
190$ make
191</pre>
192<p>If you're compiling LLVM with different source and object directories, then you
193must perform the following additional steps before running <tt class="docutils literal"><span class="pre">make</span></tt>:</p>
194<pre class="literal-block">
195# LLVMC_SRC_DIR = $LLVM_SRC_DIR/tools/llvmc/
196# LLVMC_OBJ_DIR = $LLVM_OBJ_DIR/tools/llvmc/
197$ cp $LLVMC_SRC_DIR/example/mydriver/Makefile \
198 $LLVMC_OBJ_DIR/example/mydriver/
199$ cd $LLVMC_OBJ_DIR/example/mydriver
200$ make
201</pre>
202<p>Another way to do the same thing is by using the following command:</p>
203<pre class="literal-block">
204$ cd $LLVMC_DIR
205$ make LLVMC_BUILTIN_PLUGINS=MyPlugin LLVMC_BASED_DRIVER_NAME=mydriver
206</pre>
Mikhail Glushenkov63dc3182009-06-17 02:56:48 +0000[diff] [blame]207<p>This works with both srcdir == objdir and srcdir != objdir, but assumes that the
Mikhail Glushenkov502106a2009-06-16 00:14:20 +0000[diff] [blame]208plugin source directory was placed under <tt class="docutils literal"><span class="pre">$LLVMC_DIR/plugins</span></tt>.</p>
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]209<p>Sometimes, you will want a 'bare-bones' version of LLVMC that has no
210built-in plugins. It can be compiled with the following command:</p>
211<pre class="literal-block">
212$ cd $LLVMC_DIR
Mikhail Glushenkov502106a2009-06-16 00:14:20 +0000[diff] [blame]213$ make LLVMC_BUILTIN_PLUGINS=&quot;&quot;
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]214</pre>
215</div>
Mikhail Glushenkovd6d2efc2009-05-06 01:41:47 +0000[diff] [blame]216<div class="section" id="customizing-llvmc-the-compilation-graph">
Mikhail Glushenkov502106a2009-06-16 00:14:20 +0000[diff] [blame]217<h1><a class="toc-backref" href="#id9">Customizing LLVMC: the compilation graph</a></h1>
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]218<p>Each TableGen configuration file should include the common
219definitions:</p>
220<pre class="literal-block">
221include &quot;llvm/CompilerDriver/Common.td&quot;
222</pre>
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]223<p>Internally, LLVMC stores information about possible source
224transformations in form of a graph. Nodes in this graph represent
225tools, and edges between two nodes represent a transformation path. A
226special &quot;root&quot; node is used to mark entry points for the
227transformations. LLVMC also assigns a weight to each edge (more on
228this later) to choose between several alternative edges.</p>
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]229<p>The definition of the compilation graph (see file
230<tt class="docutils literal"><span class="pre">plugins/Base/Base.td</span></tt> for an example) is just a list of edges:</p>
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]231<pre class="literal-block">
232def CompilationGraph : CompilationGraph&lt;[
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]233 Edge&lt;&quot;root&quot;, &quot;llvm_gcc_c&quot;&gt;,
234 Edge&lt;&quot;root&quot;, &quot;llvm_gcc_assembler&quot;&gt;,
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]235 ...
236
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]237 Edge&lt;&quot;llvm_gcc_c&quot;, &quot;llc&quot;&gt;,
238 Edge&lt;&quot;llvm_gcc_cpp&quot;, &quot;llc&quot;&gt;,
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]239 ...
240
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]241 OptionalEdge&lt;&quot;llvm_gcc_c&quot;, &quot;opt&quot;, (case (switch_on &quot;opt&quot;),
242 (inc_weight))&gt;,
243 OptionalEdge&lt;&quot;llvm_gcc_cpp&quot;, &quot;opt&quot;, (case (switch_on &quot;opt&quot;),
244 (inc_weight))&gt;,
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]245 ...
246
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]247 OptionalEdge&lt;&quot;llvm_gcc_assembler&quot;, &quot;llvm_gcc_cpp_linker&quot;,
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]248 (case (input_languages_contain &quot;c++&quot;), (inc_weight),
249 (or (parameter_equals &quot;linker&quot;, &quot;g++&quot;),
250 (parameter_equals &quot;linker&quot;, &quot;c++&quot;)), (inc_weight))&gt;,
251 ...
252
253 ]&gt;;
254</pre>
255<p>As you can see, the edges can be either default or optional, where
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]256optional edges are differentiated by an additional <tt class="docutils literal"><span class="pre">case</span></tt> expression
257used to calculate the weight of this edge. Notice also that we refer
258to tools via their names (as strings). This makes it possible to add
259edges to an existing compilation graph in plugins without having to
260know about all tool definitions used in the graph.</p>
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]261<p>The default edges are assigned a weight of 1, and optional edges get a
262weight of 0 + 2*N where N is the number of tests that evaluated to
263true in the <tt class="docutils literal"><span class="pre">case</span></tt> expression. It is also possible to provide an
264integer parameter to <tt class="docutils literal"><span class="pre">inc_weight</span></tt> and <tt class="docutils literal"><span class="pre">dec_weight</span></tt> - in this case,
265the weight is increased (or decreased) by the provided value instead
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]266of the default 2. It is also possible to change the default weight of
267an optional edge by using the <tt class="docutils literal"><span class="pre">default</span></tt> clause of the <tt class="docutils literal"><span class="pre">case</span></tt>
268construct.</p>
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]269<p>When passing an input file through the graph, LLVMC picks the edge
270with the maximum weight. To avoid ambiguity, there should be only one
271default edge between two nodes (with the exception of the root node,
272which gets a special treatment - there you are allowed to specify one
273default edge <em>per language</em>).</p>
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]274<p>When multiple plugins are loaded, their compilation graphs are merged
275together. Since multiple edges that have the same end nodes are not
276allowed (i.e. the graph is not a multigraph), an edge defined in
277several plugins will be replaced by the definition from the plugin
278that was loaded last. Plugin load order can be controlled by using the
279plugin priority feature described above.</p>
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]280<p>To get a visual representation of the compilation graph (useful for
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]281debugging), run <tt class="docutils literal"><span class="pre">llvmc</span> <span class="pre">--view-graph</span></tt>. You will need <tt class="docutils literal"><span class="pre">dot</span></tt> and
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]282<tt class="docutils literal"><span class="pre">gsview</span></tt> installed for this to work properly.</p>
Reid Spencerb1254a12004-08-09 03:08:29 +0000[diff] [blame]283</div>
Mikhail Glushenkovd6d2efc2009-05-06 01:41:47 +0000[diff] [blame]284<div class="section" id="describing-options">
Mikhail Glushenkov502106a2009-06-16 00:14:20 +0000[diff] [blame]285<h1><a class="toc-backref" href="#id10">Describing options</a></h1>
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]286<p>Command-line options that the plugin supports are defined by using an
287<tt class="docutils literal"><span class="pre">OptionList</span></tt>:</p>
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]288<pre class="literal-block">
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]289def Options : OptionList&lt;[
290(switch_option &quot;E&quot;, (help &quot;Help string&quot;)),
291(alias_option &quot;quiet&quot;, &quot;q&quot;)
292...
293]&gt;;
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]294</pre>
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]295<p>As you can see, the option list is just a list of DAGs, where each DAG
296is an option description consisting of the option name and some
297properties. A plugin can define more than one option list (they are
298all merged together in the end), which can be handy if one wants to
299separate option groups syntactically.</p>
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]300<ul>
301<li><p class="first">Possible option types:</p>
302<blockquote>
303<ul class="simple">
Mikhail Glushenkov5303c752009-01-28 03:47:38 +0000[diff] [blame]304<li><tt class="docutils literal"><span class="pre">switch_option</span></tt> - a simple boolean switch without arguments, for example
305<tt class="docutils literal"><span class="pre">-O2</span></tt> or <tt class="docutils literal"><span class="pre">-time</span></tt>. At most one occurrence is allowed.</li>
306<li><tt class="docutils literal"><span class="pre">parameter_option</span></tt> - option that takes one argument, for example
307<tt class="docutils literal"><span class="pre">-std=c99</span></tt>. It is also allowed to use spaces instead of the equality
308sign: <tt class="docutils literal"><span class="pre">-std</span> <span class="pre">c99</span></tt>. At most one occurrence is allowed.</li>
309<li><tt class="docutils literal"><span class="pre">parameter_list_option</span></tt> - same as the above, but more than one option
310occurence is allowed.</li>
311<li><tt class="docutils literal"><span class="pre">prefix_option</span></tt> - same as the parameter_option, but the option name and
312argument do not have to be separated. Example: <tt class="docutils literal"><span class="pre">-ofile</span></tt>. This can be also
313specified as <tt class="docutils literal"><span class="pre">-o</span> <span class="pre">file</span></tt>; however, <tt class="docutils literal"><span class="pre">-o=file</span></tt> will be parsed incorrectly
314(<tt class="docutils literal"><span class="pre">=file</span></tt> will be interpreted as option value). At most one occurrence is
315allowed.</li>
316<li><tt class="docutils literal"><span class="pre">prefix_list_option</span></tt> - same as the above, but more than one occurence of
317the option is allowed; example: <tt class="docutils literal"><span class="pre">-lm</span> <span class="pre">-lpthread</span></tt>.</li>
318<li><tt class="docutils literal"><span class="pre">alias_option</span></tt> - a special option type for creating aliases. Unlike other
319option types, aliases are not allowed to have any properties besides the
320aliased option name. Usage example: <tt class="docutils literal"><span class="pre">(alias_option</span> <span class="pre">&quot;preprocess&quot;,</span> <span class="pre">&quot;E&quot;)</span></tt></li>
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]321</ul>
322</blockquote>
323</li>
324<li><p class="first">Possible option properties:</p>
325<blockquote>
326<ul class="simple">
Mikhail Glushenkov5303c752009-01-28 03:47:38 +0000[diff] [blame]327<li><tt class="docutils literal"><span class="pre">help</span></tt> - help string associated with this option. Used for <tt class="docutils literal"><span class="pre">--help</span></tt>
328output.</li>
329<li><tt class="docutils literal"><span class="pre">required</span></tt> - this option must be specified exactly once (or, in case of
330the list options without the <tt class="docutils literal"><span class="pre">multi_val</span></tt> property, at least
331once). Incompatible with <tt class="docutils literal"><span class="pre">zero_or_one</span></tt> and <tt class="docutils literal"><span class="pre">one_or_more</span></tt>.</li>
332<li><tt class="docutils literal"><span class="pre">one_or_more</span></tt> - the option must be specified at least one time. Useful
333only for list options in conjunction with <tt class="docutils literal"><span class="pre">multi_val</span></tt>; for ordinary lists
334it is synonymous with <tt class="docutils literal"><span class="pre">required</span></tt>. Incompatible with <tt class="docutils literal"><span class="pre">required</span></tt> and
335<tt class="docutils literal"><span class="pre">zero_or_one</span></tt>.</li>
336<li><tt class="docutils literal"><span class="pre">zero_or_one</span></tt> - the option can be specified zero or one times. Useful
337only for list options in conjunction with <tt class="docutils literal"><span class="pre">multi_val</span></tt>. Incompatible with
338<tt class="docutils literal"><span class="pre">required</span></tt> and <tt class="docutils literal"><span class="pre">one_or_more</span></tt>.</li>
Mikhail Glushenkovf9b1d792009-01-15 02:42:40 +0000[diff] [blame]339<li><tt class="docutils literal"><span class="pre">hidden</span></tt> - the description of this option will not appear in
340the <tt class="docutils literal"><span class="pre">--help</span></tt> output (but will appear in the <tt class="docutils literal"><span class="pre">--help-hidden</span></tt>
341output).</li>
342<li><tt class="docutils literal"><span class="pre">really_hidden</span></tt> - the option will not be mentioned in any help
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]343output.</li>
Mikhail Glushenkov5303c752009-01-28 03:47:38 +0000[diff] [blame]344<li><tt class="docutils literal"><span class="pre">multi_val</span> <span class="pre">n</span></tt> - this option takes <em>n</em> arguments (can be useful in some
345special cases). Usage example: <tt class="docutils literal"><span class="pre">(parameter_list_option</span> <span class="pre">&quot;foo&quot;,</span> <span class="pre">(multi_val</span>
346<span class="pre">3))</span></tt>. Only list options can have this attribute; you can, however, use
347the <tt class="docutils literal"><span class="pre">one_or_more</span></tt> and <tt class="docutils literal"><span class="pre">zero_or_one</span></tt> properties.</li>
Mikhail Glushenkov640dd262009-07-07 16:09:48 +0000[diff] [blame]348<li><tt class="docutils literal"><span class="pre">init</span></tt> - this option has a default value, either a string (if it is a
349parameter), or a boolean (if it is a switch; boolean constants are called
350<tt class="docutils literal"><span class="pre">true</span></tt> and <tt class="docutils literal"><span class="pre">false</span></tt>). List options can't have this attribute. Usage
351examples: <tt class="docutils literal"><span class="pre">(switch_option</span> <span class="pre">&quot;foo&quot;,</span> <span class="pre">(init</span> <span class="pre">true))</span></tt>; <tt class="docutils literal"><span class="pre">(prefix_option</span> <span class="pre">&quot;bar&quot;,</span>
352<span class="pre">(init</span> <span class="pre">&quot;baz&quot;))</span></tt>.</li>
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]353<li><tt class="docutils literal"><span class="pre">extern</span></tt> - this option is defined in some other plugin, see below.</li>
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]354</ul>
355</blockquote>
356</li>
357</ul>
Mikhail Glushenkovd6d2efc2009-05-06 01:41:47 +0000[diff] [blame]358<div class="section" id="external-options">
Mikhail Glushenkov502106a2009-06-16 00:14:20 +0000[diff] [blame]359<h2><a class="toc-backref" href="#id11">External options</a></h2>
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]360<p>Sometimes, when linking several plugins together, one plugin needs to
361access options defined in some other plugin. Because of the way
Mikhail Glushenkovf9b1d792009-01-15 02:42:40 +0000[diff] [blame]362options are implemented, such options must be marked as
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]363<tt class="docutils literal"><span class="pre">extern</span></tt>. This is what the <tt class="docutils literal"><span class="pre">extern</span></tt> option property is
364for. Example:</p>
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]365<pre class="literal-block">
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]366...
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]367(switch_option &quot;E&quot;, (extern))
368...
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]369</pre>
Mikhail Glushenkov15367df2009-07-07 16:44:20 +0000[diff] [blame]370<p>If an external option has additional attributes besides 'extern', they are
371ignored. See also the section on plugin <a class="reference internal" href="#priorities">priorities</a>.</p>
Reid Spencerb1254a12004-08-09 03:08:29 +0000[diff] [blame]372</div>
Reid Spencerb1254a12004-08-09 03:08:29 +0000[diff] [blame]373</div>
Mikhail Glushenkovd6d2efc2009-05-06 01:41:47 +0000[diff] [blame]374<div class="section" id="conditional-evaluation">
Mikhail Glushenkov502106a2009-06-16 00:14:20 +0000[diff] [blame]375<span id="case"></span><h1><a class="toc-backref" href="#id12">Conditional evaluation</a></h1>
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]376<p>The 'case' construct is the main means by which programmability is
377achieved in LLVMC. It can be used to calculate edge weights, program
378actions and modify the shell commands to be executed. The 'case'
379expression is designed after the similarly-named construct in
380functional languages and takes the form <tt class="docutils literal"><span class="pre">(case</span> <span class="pre">(test_1),</span> <span class="pre">statement_1,</span>
381<span class="pre">(test_2),</span> <span class="pre">statement_2,</span> <span class="pre">...</span> <span class="pre">(test_N),</span> <span class="pre">statement_N)</span></tt>. The statements
382are evaluated only if the corresponding tests evaluate to true.</p>
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]383<p>Examples:</p>
384<pre class="literal-block">
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]385// Edge weight calculation
386
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]387// Increases edge weight by 5 if &quot;-A&quot; is provided on the
388// command-line, and by 5 more if &quot;-B&quot; is also provided.
389(case
390 (switch_on &quot;A&quot;), (inc_weight 5),
391 (switch_on &quot;B&quot;), (inc_weight 5))
392
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]393
394// Tool command line specification
395
396// Evaluates to &quot;cmdline1&quot; if the option &quot;-A&quot; is provided on the
397// command line; to &quot;cmdline2&quot; if &quot;-B&quot; is provided;
398// otherwise to &quot;cmdline3&quot;.
399
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]400(case
401 (switch_on &quot;A&quot;), &quot;cmdline1&quot;,
402 (switch_on &quot;B&quot;), &quot;cmdline2&quot;,
403 (default), &quot;cmdline3&quot;)
404</pre>
405<p>Note the slight difference in 'case' expression handling in contexts
406of edge weights and command line specification - in the second example
407the value of the <tt class="docutils literal"><span class="pre">&quot;B&quot;</span></tt> switch is never checked when switch <tt class="docutils literal"><span class="pre">&quot;A&quot;</span></tt> is
408enabled, and the whole expression always evaluates to <tt class="docutils literal"><span class="pre">&quot;cmdline1&quot;</span></tt> in
409that case.</p>
410<p>Case expressions can also be nested, i.e. the following is legal:</p>
411<pre class="literal-block">
412(case (switch_on &quot;E&quot;), (case (switch_on &quot;o&quot;), ..., (default), ...)
413 (default), ...)
414</pre>
415<p>You should, however, try to avoid doing that because it hurts
416readability. It is usually better to split tool descriptions and/or
417use TableGen inheritance instead.</p>
418<ul class="simple">
419<li>Possible tests are:<ul>
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]420<li><tt class="docutils literal"><span class="pre">switch_on</span></tt> - Returns true if a given command-line switch is
421provided by the user. Example: <tt class="docutils literal"><span class="pre">(switch_on</span> <span class="pre">&quot;opt&quot;)</span></tt>.</li>
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]422<li><tt class="docutils literal"><span class="pre">parameter_equals</span></tt> - Returns true if a command-line parameter equals
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]423a given value.
424Example: <tt class="docutils literal"><span class="pre">(parameter_equals</span> <span class="pre">&quot;W&quot;,</span> <span class="pre">&quot;all&quot;)</span></tt>.</li>
425<li><tt class="docutils literal"><span class="pre">element_in_list</span></tt> - Returns true if a command-line parameter
426list contains a given value.
427Example: <tt class="docutils literal"><span class="pre">(parameter_in_list</span> <span class="pre">&quot;l&quot;,</span> <span class="pre">&quot;pthread&quot;)</span></tt>.</li>
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]428<li><tt class="docutils literal"><span class="pre">input_languages_contain</span></tt> - Returns true if a given language
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]429belongs to the current input language set.
430Example: <tt class="docutils literal"><span class="pre">(input_languages_contain</span> <span class="pre">&quot;c++&quot;)</span></tt>.</li>
431<li><tt class="docutils literal"><span class="pre">in_language</span></tt> - Evaluates to true if the input file language
432equals to the argument. At the moment works only with <tt class="docutils literal"><span class="pre">cmd_line</span></tt>
433and <tt class="docutils literal"><span class="pre">actions</span></tt> (on non-join nodes).
434Example: <tt class="docutils literal"><span class="pre">(in_language</span> <span class="pre">&quot;c++&quot;)</span></tt>.</li>
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]435<li><tt class="docutils literal"><span class="pre">not_empty</span></tt> - Returns true if a given option (which should be
436either a parameter or a parameter list) is set by the
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]437user.
438Example: <tt class="docutils literal"><span class="pre">(not_empty</span> <span class="pre">&quot;o&quot;)</span></tt>.</li>
Mikhail Glushenkov2d0484c2008-12-17 02:47:30 +0000[diff] [blame]439<li><tt class="docutils literal"><span class="pre">empty</span></tt> - The opposite of <tt class="docutils literal"><span class="pre">not_empty</span></tt>. Equivalent to <tt class="docutils literal"><span class="pre">(not</span> <span class="pre">(not_empty</span>
440<span class="pre">X))</span></tt>. Provided for convenience.</li>
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]441<li><tt class="docutils literal"><span class="pre">default</span></tt> - Always evaluates to true. Should always be the last
442test in the <tt class="docutils literal"><span class="pre">case</span></tt> expression.</li>
443<li><tt class="docutils literal"><span class="pre">and</span></tt> - A standard logical combinator that returns true iff all
444of its arguments return true. Used like this: <tt class="docutils literal"><span class="pre">(and</span> <span class="pre">(test1),</span>
445<span class="pre">(test2),</span> <span class="pre">...</span> <span class="pre">(testN))</span></tt>. Nesting of <tt class="docutils literal"><span class="pre">and</span></tt> and <tt class="docutils literal"><span class="pre">or</span></tt> is allowed,
446but not encouraged.</li>
447<li><tt class="docutils literal"><span class="pre">or</span></tt> - Another logical combinator that returns true only if any
448one of its arguments returns true. Example: <tt class="docutils literal"><span class="pre">(or</span> <span class="pre">(test1),</span>
449<span class="pre">(test2),</span> <span class="pre">...</span> <span class="pre">(testN))</span></tt>.</li>
450</ul>
451</li>
452</ul>
Reid Spencer46d21922004-08-22 18:06:59 +0000[diff] [blame]453</div>
Mikhail Glushenkovd6d2efc2009-05-06 01:41:47 +0000[diff] [blame]454<div class="section" id="writing-a-tool-description">
Mikhail Glushenkov502106a2009-06-16 00:14:20 +0000[diff] [blame]455<h1><a class="toc-backref" href="#id13">Writing a tool description</a></h1>
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]456<p>As was said earlier, nodes in the compilation graph represent tools,
457which are described separately. A tool definition looks like this
458(taken from the <tt class="docutils literal"><span class="pre">include/llvm/CompilerDriver/Tools.td</span></tt> file):</p>
459<pre class="literal-block">
460def llvm_gcc_cpp : Tool&lt;[
461 (in_language &quot;c++&quot;),
462 (out_language &quot;llvm-assembler&quot;),
463 (output_suffix &quot;bc&quot;),
464 (cmd_line &quot;llvm-g++ -c $INFILE -o $OUTFILE -emit-llvm&quot;),
465 (sink)
466 ]&gt;;
467</pre>
468<p>This defines a new tool called <tt class="docutils literal"><span class="pre">llvm_gcc_cpp</span></tt>, which is an alias for
469<tt class="docutils literal"><span class="pre">llvm-g++</span></tt>. As you can see, a tool definition is just a list of
470properties; most of them should be self-explanatory. The <tt class="docutils literal"><span class="pre">sink</span></tt>
471property means that this tool should be passed all command-line
472options that aren't mentioned in the option list.</p>
473<p>The complete list of all currently implemented tool properties follows.</p>
474<ul class="simple">
475<li>Possible tool properties:<ul>
476<li><tt class="docutils literal"><span class="pre">in_language</span></tt> - input language name. Can be either a string or a
477list, in case the tool supports multiple input languages.</li>
478<li><tt class="docutils literal"><span class="pre">out_language</span></tt> - output language name. Tools are not allowed to
479have multiple output languages.</li>
480<li><tt class="docutils literal"><span class="pre">output_suffix</span></tt> - output file suffix. Can also be changed
481dynamically, see documentation on actions.</li>
482<li><tt class="docutils literal"><span class="pre">cmd_line</span></tt> - the actual command used to run the tool. You can
483use <tt class="docutils literal"><span class="pre">$INFILE</span></tt> and <tt class="docutils literal"><span class="pre">$OUTFILE</span></tt> variables, output redirection
484with <tt class="docutils literal"><span class="pre">&gt;</span></tt>, hook invocations (<tt class="docutils literal"><span class="pre">$CALL</span></tt>), environment variables
485(via <tt class="docutils literal"><span class="pre">$ENV</span></tt>) and the <tt class="docutils literal"><span class="pre">case</span></tt> construct.</li>
486<li><tt class="docutils literal"><span class="pre">join</span></tt> - this tool is a &quot;join node&quot; in the graph, i.e. it gets a
487list of input files and joins them together. Used for linkers.</li>
488<li><tt class="docutils literal"><span class="pre">sink</span></tt> - all command-line options that are not handled by other
489tools are passed to this tool.</li>
490<li><tt class="docutils literal"><span class="pre">actions</span></tt> - A single big <tt class="docutils literal"><span class="pre">case</span></tt> expression that specifies how
491this tool reacts on command-line options (described in more detail
492below).</li>
493</ul>
494</li>
495</ul>
Mikhail Glushenkovd6d2efc2009-05-06 01:41:47 +0000[diff] [blame]496<div class="section" id="actions">
Mikhail Glushenkov502106a2009-06-16 00:14:20 +0000[diff] [blame]497<h2><a class="toc-backref" href="#id14">Actions</a></h2>
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]498<p>A tool often needs to react to command-line options, and this is
499precisely what the <tt class="docutils literal"><span class="pre">actions</span></tt> property is for. The next example
500illustrates this feature:</p>
501<pre class="literal-block">
502def llvm_gcc_linker : Tool&lt;[
503 (in_language &quot;object-code&quot;),
504 (out_language &quot;executable&quot;),
505 (output_suffix &quot;out&quot;),
506 (cmd_line &quot;llvm-gcc $INFILE -o $OUTFILE&quot;),
507 (join),
508 (actions (case (not_empty &quot;L&quot;), (forward &quot;L&quot;),
509 (not_empty &quot;l&quot;), (forward &quot;l&quot;),
510 (not_empty &quot;dummy&quot;),
511 [(append_cmd &quot;-dummy1&quot;), (append_cmd &quot;-dummy2&quot;)])
512 ]&gt;;
513</pre>
514<p>The <tt class="docutils literal"><span class="pre">actions</span></tt> tool property is implemented on top of the omnipresent
515<tt class="docutils literal"><span class="pre">case</span></tt> expression. It associates one or more different <em>actions</em>
516with given conditions - in the example, the actions are <tt class="docutils literal"><span class="pre">forward</span></tt>,
517which forwards a given option unchanged, and <tt class="docutils literal"><span class="pre">append_cmd</span></tt>, which
518appends a given string to the tool execution command. Multiple actions
519can be associated with a single condition by using a list of actions
520(used in the example to append some dummy options). The same <tt class="docutils literal"><span class="pre">case</span></tt>
521construct can also be used in the <tt class="docutils literal"><span class="pre">cmd_line</span></tt> property to modify the
522tool command line.</p>
523<p>The &quot;join&quot; property used in the example means that this tool behaves
524like a linker.</p>
525<p>The list of all possible actions follows.</p>
526<ul>
527<li><p class="first">Possible actions:</p>
528<blockquote>
529<ul class="simple">
530<li><tt class="docutils literal"><span class="pre">append_cmd</span></tt> - append a string to the tool invocation
531command.
Mikhail Glushenkov2d0484c2008-12-17 02:47:30 +0000[diff] [blame]532Example: <tt class="docutils literal"><span class="pre">(case</span> <span class="pre">(switch_on</span> <span class="pre">&quot;pthread&quot;),</span> <span class="pre">(append_cmd</span>
533<span class="pre">&quot;-lpthread&quot;))</span></tt></li>
534<li><tt class="docutils literal"><span class="pre">error`</span> <span class="pre">-</span> <span class="pre">exit</span> <span class="pre">with</span> <span class="pre">error.</span>
535<span class="pre">Example:</span> <span class="pre">``(error</span> <span class="pre">&quot;Mixing</span> <span class="pre">-c</span> <span class="pre">and</span> <span class="pre">-S</span> <span class="pre">is</span> <span class="pre">not</span> <span class="pre">allowed!&quot;)</span></tt>.</li>
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]536<li><tt class="docutils literal"><span class="pre">forward</span></tt> - forward an option unchanged.
537Example: <tt class="docutils literal"><span class="pre">(forward</span> <span class="pre">&quot;Wall&quot;)</span></tt>.</li>
538<li><tt class="docutils literal"><span class="pre">forward_as</span></tt> - Change the name of an option, but forward the
539argument unchanged.
Mikhail Glushenkovd6d2efc2009-05-06 01:41:47 +0000[diff] [blame]540Example: <tt class="docutils literal"><span class="pre">(forward_as</span> <span class="pre">&quot;O0&quot;,</span> <span class="pre">&quot;--disable-optimization&quot;)</span></tt>.</li>
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]541<li><tt class="docutils literal"><span class="pre">output_suffix</span></tt> - modify the output suffix of this
542tool.
543Example: <tt class="docutils literal"><span class="pre">(output_suffix</span> <span class="pre">&quot;i&quot;)</span></tt>.</li>
544<li><tt class="docutils literal"><span class="pre">stop_compilation</span></tt> - stop compilation after this tool processes
545its input. Used without arguments.</li>
546<li><tt class="docutils literal"><span class="pre">unpack_values</span></tt> - used for for splitting and forwarding
547comma-separated lists of options, e.g. <tt class="docutils literal"><span class="pre">-Wa,-foo=bar,-baz</span></tt> is
548converted to <tt class="docutils literal"><span class="pre">-foo=bar</span> <span class="pre">-baz</span></tt> and appended to the tool invocation
549command.
550Example: <tt class="docutils literal"><span class="pre">(unpack_values</span> <span class="pre">&quot;Wa,&quot;)</span></tt>.</li>
551</ul>
552</blockquote>
553</li>
554</ul>
555</div>
556</div>
Mikhail Glushenkovd6d2efc2009-05-06 01:41:47 +0000[diff] [blame]557<div class="section" id="language-map">
Mikhail Glushenkov502106a2009-06-16 00:14:20 +0000[diff] [blame]558<h1><a class="toc-backref" href="#id15">Language map</a></h1>
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]559<p>If you are adding support for a new language to LLVMC, you'll need to
560modify the language map, which defines mappings from file extensions
561to language names. It is used to choose the proper toolchain(s) for a
562given input file set. Language map definition looks like this:</p>
Anton Korobeynikov74120312008-06-09 04:15:49 +0000[diff] [blame]563<pre class="literal-block">
564def LanguageMap : LanguageMap&lt;
565 [LangToSuffixes&lt;&quot;c++&quot;, [&quot;cc&quot;, &quot;cp&quot;, &quot;cxx&quot;, &quot;cpp&quot;, &quot;CPP&quot;, &quot;c++&quot;, &quot;C&quot;]&gt;,
566 LangToSuffixes&lt;&quot;c&quot;, [&quot;c&quot;]&gt;,
567 ...
568 ]&gt;;
569</pre>
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]570<p>For example, without those definitions the following command wouldn't work:</p>
571<pre class="literal-block">
572$ llvmc hello.cpp
573llvmc: Unknown suffix: cpp
574</pre>
575<p>The language map entries should be added only for tools that are
576linked with the root node. Since tools are not allowed to have
577multiple output languages, for nodes &quot;inside&quot; the graph the input and
578output languages should match. This is enforced at compile-time.</p>
Reid Spencer46d21922004-08-22 18:06:59 +0000[diff] [blame]579</div>
Mikhail Glushenkovd6d2efc2009-05-06 01:41:47 +0000[diff] [blame]580<div class="section" id="more-advanced-topics">
Mikhail Glushenkov502106a2009-06-16 00:14:20 +0000[diff] [blame]581<h1><a class="toc-backref" href="#id16">More advanced topics</a></h1>
Mikhail Glushenkovd6d2efc2009-05-06 01:41:47 +0000[diff] [blame]582<div class="section" id="hooks-and-environment-variables">
Mikhail Glushenkov502106a2009-06-16 00:14:20 +0000[diff] [blame]583<span id="hooks"></span><h2><a class="toc-backref" href="#id17">Hooks and environment variables</a></h2>
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]584<p>Normally, LLVMC executes programs from the system <tt class="docutils literal"><span class="pre">PATH</span></tt>. Sometimes,
Mikhail Glushenkov5303c752009-01-28 03:47:38 +0000[diff] [blame]585this is not sufficient: for example, we may want to specify tool paths
586or names in the configuration file. This can be easily achieved via
587the hooks mechanism. To write your own hooks, just add their
588definitions to the <tt class="docutils literal"><span class="pre">PluginMain.cpp</span></tt> or drop a <tt class="docutils literal"><span class="pre">.cpp</span></tt> file into the
589your plugin directory. Hooks should live in the <tt class="docutils literal"><span class="pre">hooks</span></tt> namespace
590and have the signature <tt class="docutils literal"><span class="pre">std::string</span> <span class="pre">hooks::MyHookName</span> <span class="pre">([const</span> <span class="pre">char*</span>
591<span class="pre">Arg0</span> <span class="pre">[</span> <span class="pre">const</span> <span class="pre">char*</span> <span class="pre">Arg2</span> <span class="pre">[,</span> <span class="pre">...]]])</span></tt>. They can be used from the
592<tt class="docutils literal"><span class="pre">cmd_line</span></tt> tool property:</p>
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]593<pre class="literal-block">
594(cmd_line &quot;$CALL(MyHook)/path/to/file -o $CALL(AnotherHook)&quot;)
595</pre>
Mikhail Glushenkov5303c752009-01-28 03:47:38 +0000[diff] [blame]596<p>To pass arguments to hooks, use the following syntax:</p>
597<pre class="literal-block">
598(cmd_line &quot;$CALL(MyHook, 'Arg1', 'Arg2', 'Arg # 3')/path/to/file -o1 -o2&quot;)
599</pre>
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]600<p>It is also possible to use environment variables in the same manner:</p>
601<pre class="literal-block">
602(cmd_line &quot;$ENV(VAR1)/path/to/file -o $ENV(VAR2)&quot;)
603</pre>
604<p>To change the command line string based on user-provided options use
Mikhail Glushenkovd6d2efc2009-05-06 01:41:47 +0000[diff] [blame]605the <tt class="docutils literal"><span class="pre">case</span></tt> expression (documented <a class="reference internal" href="#case">above</a>):</p>
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]606<pre class="literal-block">
607(cmd_line
608 (case
609 (switch_on &quot;E&quot;),
610 &quot;llvm-g++ -E -x c $INFILE -o $OUTFILE&quot;,
611 (default),
612 &quot;llvm-g++ -c -x c $INFILE -o $OUTFILE -emit-llvm&quot;))
613</pre>
614</div>
Mikhail Glushenkovd6d2efc2009-05-06 01:41:47 +0000[diff] [blame]615<div class="section" id="how-plugins-are-loaded">
Mikhail Glushenkov502106a2009-06-16 00:14:20 +0000[diff] [blame]616<span id="priorities"></span><h2><a class="toc-backref" href="#id18">How plugins are loaded</a></h2>
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]617<p>It is possible for LLVMC plugins to depend on each other. For example,
618one can create edges between nodes defined in some other plugin. To
619make this work, however, that plugin should be loaded first. To
620achieve this, the concept of plugin priority was introduced. By
621default, every plugin has priority zero; to specify the priority
622explicitly, put the following line in your plugin's TableGen file:</p>
623<pre class="literal-block">
624def Priority : PluginPriority&lt;$PRIORITY_VALUE&gt;;
625# Where PRIORITY_VALUE is some integer &gt; 0
626</pre>
627<p>Plugins are loaded in order of their (increasing) priority, starting
628with 0. Therefore, the plugin with the highest priority value will be
629loaded last.</p>
630</div>
Mikhail Glushenkovd6d2efc2009-05-06 01:41:47 +0000[diff] [blame]631<div class="section" id="debugging">
Mikhail Glushenkov502106a2009-06-16 00:14:20 +0000[diff] [blame]632<h2><a class="toc-backref" href="#id19">Debugging</a></h2>
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]633<p>When writing LLVMC plugins, it can be useful to get a visual view of
634the resulting compilation graph. This can be achieved via the command
Mikhail Glushenkovd6d2efc2009-05-06 01:41:47 +0000[diff] [blame]635line option <tt class="docutils literal"><span class="pre">--view-graph</span></tt>. This command assumes that <a class="reference external" href="http://www.graphviz.org/">Graphviz</a> and
636<a class="reference external" href="http://pages.cs.wisc.edu/~ghost/">Ghostview</a> are installed. There is also a <tt class="docutils literal"><span class="pre">--write-graph</span></tt> option that
Mikhail Glushenkovd5652032008-12-13 02:28:58 +0000[diff] [blame]637creates a Graphviz source file (<tt class="docutils literal"><span class="pre">compilation-graph.dot</span></tt>) in the
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]638current directory.</p>
Mikhail Glushenkovf9b1d792009-01-15 02:42:40 +0000[diff] [blame]639<p>Another useful <tt class="docutils literal"><span class="pre">llvmc</span></tt> option is <tt class="docutils literal"><span class="pre">--check-graph</span></tt>. It checks the
640compilation graph for common errors like mismatched output/input
641language names, multiple default edges and cycles. These checks can't
642be performed at compile-time because the plugins can load code
643dynamically. When invoked with <tt class="docutils literal"><span class="pre">--check-graph</span></tt>, <tt class="docutils literal"><span class="pre">llvmc</span></tt> doesn't
644perform any compilation tasks and returns the number of encountered
645errors as its status code.</p>
Mikhail Glushenkove25b8452009-06-30 00:16:43 +0000[diff] [blame]646</div>
647<div class="section" id="conditioning-on-the-executable-name">
648<h2><a class="toc-backref" href="#id20">Conditioning on the executable name</a></h2>
649<p>For now, the executable name (the value passed to the driver in <tt class="docutils literal"><span class="pre">argv[0]</span></tt>) is
650accessible only in the C++ code (i.e. hooks). Use the following code:</p>
651<pre class="literal-block">
652namespace llvmc {
653extern const char* ProgramName;
654}
655
656std::string MyHook() {
657//...
658if (strcmp(ProgramName, &quot;mydriver&quot;) == 0) {
659 //...
660
661}
662</pre>
663<p>In general, you're encouraged not to make the behaviour dependent on the
664executable file name, and use command-line switches instead. See for example how
665the <tt class="docutils literal"><span class="pre">Base</span></tt> plugin behaves when it needs to choose the correct linker options
666(think <tt class="docutils literal"><span class="pre">g++</span></tt> vs. <tt class="docutils literal"><span class="pre">gcc</span></tt>).</p>
Mikhail Glushenkov90531542008-12-11 23:43:14 +0000[diff] [blame]667<hr />
Anton Korobeynikov28b66702008-06-09 04:17:51 +0000[diff] [blame]668<address>
Mikhail Glushenkovd5652032008-12-13 02:28:58 +0000[diff] [blame]669<a href="http://jigsaw.w3.org/css-validator/check/referer">
670<img src="http://jigsaw.w3.org/css-validator/images/vcss-blue"
671 alt="Valid CSS" /></a>
672<a href="http://validator.w3.org/check?uri=referer">
673<img src="http://www.w3.org/Icons/valid-xhtml10-blue"
674 alt="Valid XHTML 1.0 Transitional"/></a>
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]675
Mikhail Glushenkovd5652032008-12-13 02:28:58 +0000[diff] [blame]676<a href="mailto:foldr@codedgers.com">Mikhail Glushenkov</a><br />
677<a href="http://llvm.org">LLVM Compiler Infrastructure</a><br />
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]678
Mikhail Glushenkov4ad0d572009-03-27 12:58:29 +0000[diff] [blame]679Last modified: $Date: 2008-12-11 11:34:48 -0600 (Thu, 11 Dec 2008) $
Mikhail Glushenkovd5652032008-12-13 02:28:58 +0000[diff] [blame]680</address></div>
Mikhail Glushenkov68319f82008-12-11 23:24:40 +0000[diff] [blame]681</div>
682</div>
Reid Spencerb1254a12004-08-09 03:08:29 +0000[diff] [blame]683</body>
684</html>