blob: 71dc4926ac31d128db64fe8415feb2424e8e0bae [file] [log] [blame]
Misha Brukmanc5402402004-01-15 18:34:11 +00001<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
2 "http://www.w3.org/TR/html4/strict.dtd">
3<html>
4<head>
Reid Spencer7fa6d522005-01-11 05:16:23 +00005 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Misha Brukmanc5402402004-01-15 18:34:11 +00006 <title>Writing an LLVM Pass</title>
7 <link rel="stylesheet" href="llvm.css" type="text/css">
8</head>
9<body>
Chris Lattnerc6bb8242002-08-08 20:11:18 +000010
Misha Brukmanc5402402004-01-15 18:34:11 +000011<div class="doc_title">
12 Writing an LLVM Pass
13</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +000014
15<ol>
Misha Brukmanc5402402004-01-15 18:34:11 +000016 <li><a href="#introduction">Introduction - What is a pass?</a></li>
Chris Lattnerc6bb8242002-08-08 20:11:18 +000017 <li><a href="#quickstart">Quick Start - Writing hello world</a>
18 <ul>
Misha Brukmanc5402402004-01-15 18:34:11 +000019 <li><a href="#makefile">Setting up the build environment</a></li>
20 <li><a href="#basiccode">Basic code required</a></li>
Chris Lattnerc6bb8242002-08-08 20:11:18 +000021 <li><a href="#running">Running a pass with <tt>opt</tt>
Chris Lattner8fdb2462004-09-18 06:39:35 +000022 or <tt>analyze</tt></a></li>
Misha Brukmanc5402402004-01-15 18:34:11 +000023 </ul></li>
Chris Lattnerc6bb8242002-08-08 20:11:18 +000024 <li><a href="#passtype">Pass classes and requirements</a>
25 <ul>
Misha Brukmanc5402402004-01-15 18:34:11 +000026 <li><a href="#ImmutablePass">The <tt>ImmutablePass</tt> class</a></li>
Chris Lattnerf6278922004-09-20 04:36:29 +000027 <li><a href="#ModulePass">The <tt>ModulePass</tt> class</a>
Chris Lattnerc6bb8242002-08-08 20:11:18 +000028 <ul>
Chris Lattnerf6278922004-09-20 04:36:29 +000029 <li><a href="#runOnModule">The <tt>runOnModule</tt> method</a></li>
Misha Brukmanc5402402004-01-15 18:34:11 +000030 </ul></li>
Chris Lattner8fdb2462004-09-18 06:39:35 +000031 <li><a href="#CallGraphSCCPass">The <tt>CallGraphSCCPass</tt> class</a>
32 <ul>
33 <li><a href="#doInitialization_scc">The <tt>doInitialization(Module
34 &amp;)</tt> method</a></li>
35 <li><a href="#runOnSCC">The <tt>runOnSCC</tt> method</a></li>
36 <li><a href="#doFinalization_scc">The <tt>doFinalization(Module
37 &amp;)</tt> method</a></li>
38 </ul></li>
Chris Lattnerc6bb8242002-08-08 20:11:18 +000039 <li><a href="#FunctionPass">The <tt>FunctionPass</tt> class</a>
40 <ul>
Chris Lattnerd0713f92002-09-12 17:06:43 +000041 <li><a href="#doInitialization_mod">The <tt>doInitialization(Module
Misha Brukmanc5402402004-01-15 18:34:11 +000042 &amp;)</tt> method</a></li>
43 <li><a href="#runOnFunction">The <tt>runOnFunction</tt> method</a></li>
Chris Lattnerd0713f92002-09-12 17:06:43 +000044 <li><a href="#doFinalization_mod">The <tt>doFinalization(Module
Misha Brukmanc5402402004-01-15 18:34:11 +000045 &amp;)</tt> method</a></li>
46 </ul></li>
Chris Lattnerc6bb8242002-08-08 20:11:18 +000047 <li><a href="#BasicBlockPass">The <tt>BasicBlockPass</tt> class</a>
48 <ul>
Chris Lattnerd0713f92002-09-12 17:06:43 +000049 <li><a href="#doInitialization_fn">The <tt>doInitialization(Function
Misha Brukmanc5402402004-01-15 18:34:11 +000050 &amp;)</tt> method</a></li>
51 <li><a href="#runOnBasicBlock">The <tt>runOnBasicBlock</tt>
52 method</a></li>
Chris Lattnerd0713f92002-09-12 17:06:43 +000053 <li><a href="#doFinalization_fn">The <tt>doFinalization(Function
Misha Brukmanc5402402004-01-15 18:34:11 +000054 &amp;)</tt> method</a></li>
55 </ul></li>
Brian Gaekecab8b6f2003-07-17 18:53:20 +000056 <li><a href="#MachineFunctionPass">The <tt>MachineFunctionPass</tt>
57 class</a>
Brian Gaeke6a33f362003-07-22 20:53:20 +000058 <ul>
59 <li><a href="#runOnMachineFunction">The
Misha Brukmanc5402402004-01-15 18:34:11 +000060 <tt>runOnMachineFunction(MachineFunction &amp;)</tt> method</a></li>
61 </ul></li>
Chris Lattnerc6bb8242002-08-08 20:11:18 +000062 </ul>
63 <li><a href="#registration">Pass Registration</a>
64 <ul>
Misha Brukmanc5402402004-01-15 18:34:11 +000065 <li><a href="#print">The <tt>print</tt> method</a></li>
66 </ul></li>
Chris Lattnerc6bb8242002-08-08 20:11:18 +000067 <li><a href="#interaction">Specifying interactions between passes</a>
68 <ul>
Misha Brukmanc5402402004-01-15 18:34:11 +000069 <li><a href="#getAnalysisUsage">The <tt>getAnalysisUsage</tt>
70 method</a></li>
Chris Lattner89256272004-03-17 21:09:55 +000071 <li><a href="#AU::addRequired">The <tt>AnalysisUsage::addRequired&lt;&gt;</tt> and <tt>AnalysisUsage::addRequiredTransitive&lt;&gt;</tt> methods</a></li>
72 <li><a href="#AU::addPreserved">The <tt>AnalysisUsage::addPreserved&lt;&gt;</tt> method</a></li>
73 <li><a href="#AU::examples">Example implementations of <tt>getAnalysisUsage</tt></a></li>
74 <li><a href="#getAnalysis">The <tt>getAnalysis&lt;&gt;</tt> and <tt>getAnalysisToUpdate&lt;&gt;</tt> methods</a></li>
Misha Brukmanc5402402004-01-15 18:34:11 +000075 </ul></li>
Chris Lattner79910702002-08-22 19:21:04 +000076 <li><a href="#analysisgroup">Implementing Analysis Groups</a>
77 <ul>
Misha Brukmanc5402402004-01-15 18:34:11 +000078 <li><a href="#agconcepts">Analysis Group Concepts</a></li>
79 <li><a href="#registerag">Using <tt>RegisterAnalysisGroup</tt></a></li>
80 </ul></li>
Tanya Lattnerd5383652004-11-19 01:25:14 +000081 <li><a href="#passStatistics">Pass Statistics</a>
Chris Lattnerc6bb8242002-08-08 20:11:18 +000082 <li><a href="#passmanager">What PassManager does</a>
83 <ul>
Misha Brukmanc5402402004-01-15 18:34:11 +000084 <li><a href="#releaseMemory">The <tt>releaseMemory</tt> method</a></li>
85 </ul></li>
Jim Laskey5fa8fff2006-08-04 18:10:12 +000086 <li><a href="#registering">Registering dynamically loaded passes</a>
87 <ul>
88 <li><a href="#registering_existing">Using existing registries</a></li>
89 <li><a href="#registering_new">Creating new registries</a></li>
90 </ul></li>
Chris Lattner480e2ef2002-09-06 02:02:58 +000091 <li><a href="#debughints">Using GDB with dynamically loaded passes</a>
92 <ul>
Misha Brukmanc5402402004-01-15 18:34:11 +000093 <li><a href="#breakpoint">Setting a breakpoint in your pass</a></li>
94 <li><a href="#debugmisc">Miscellaneous Problems</a></li>
95 </ul></li>
Chris Lattnerc6bb8242002-08-08 20:11:18 +000096 <li><a href="#future">Future extensions planned</a>
97 <ul>
Misha Brukmanc5402402004-01-15 18:34:11 +000098 <li><a href="#SMP">Multithreaded LLVM</a></li>
Chris Lattnerf6278922004-09-20 04:36:29 +000099 <li><a href="#PassFunctionPass"><tt>ModulePass</tt>es requiring
Misha Brukmanc5402402004-01-15 18:34:11 +0000100 <tt>FunctionPass</tt>es</a></li>
101 </ul></li>
102</ol>
Chris Lattner38c633d2002-08-08 20:23:41 +0000103
Chris Lattner7911ce22004-05-23 21:07:27 +0000104<div class="doc_author">
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000105 <p>Written by <a href="mailto:sabre@nondot.org">Chris Lattner</a>,
106 <a href="mailto:jlaskey@apple.com">Jim Laskey</a></p>
Misha Brukmanc5402402004-01-15 18:34:11 +0000107</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000108
109<!-- *********************************************************************** -->
Misha Brukmanc5402402004-01-15 18:34:11 +0000110<div class="doc_section">
111 <a name="introduction">Introduction - What is a pass?</a>
112</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000113<!-- *********************************************************************** -->
114
Misha Brukmanc5402402004-01-15 18:34:11 +0000115<div class="doc_text">
116
117<p>The LLVM Pass Framework is an important part of the LLVM system, because LLVM
Chris Lattner8fdb2462004-09-18 06:39:35 +0000118passes are where most of the interesting parts of the compiler exist. Passes
119perform the transformations and optimizations that make up the compiler, they
120build the analysis results that are used by these transformations, and they are,
121above all, a structuring technique for compiler code.</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000122
Misha Brukmanc5402402004-01-15 18:34:11 +0000123<p>All LLVM passes are subclasses of the <tt><a
Reid Spencer05fe4b02006-03-14 05:39:39 +0000124href="http://llvm.org/doxygen/classllvm_1_1Pass.html">Pass</a></tt>
Misha Brukmanc5402402004-01-15 18:34:11 +0000125class, which implement functionality by overriding virtual methods inherited
Chris Lattnerf6278922004-09-20 04:36:29 +0000126from <tt>Pass</tt>. Depending on how your pass works, you should inherit from
127the <tt><a href="#ModulePass">ModulePass</a></tt>, <tt><a
128href="#CallGraphSCCPass">CallGraphSCCPass</a></tt>, <tt><a
129href="#FunctionPass">FunctionPass</a></tt>, or <tt><a
Chris Lattner8fdb2462004-09-18 06:39:35 +0000130href="#BasicBlockPass">BasicBlockPass</a></tt> classes, which gives the system
131more information about what your pass does, and how it can be combined with
132other passes. One of the main features of the LLVM Pass Framework is that it
133schedules passes to run in an efficient way based on the constraints that your
134pass meets (which are indicated by which class they derive from).</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000135
Misha Brukmanc5402402004-01-15 18:34:11 +0000136<p>We start by showing you how to construct a pass, everything from setting up
137the code, to compiling, loading, and executing it. After the basics are down,
138more advanced features are discussed.</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000139
Misha Brukmanc5402402004-01-15 18:34:11 +0000140</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000141
142<!-- *********************************************************************** -->
Misha Brukmanc5402402004-01-15 18:34:11 +0000143<div class="doc_section">
144 <a name="quickstart">Quick Start - Writing hello world</a>
145</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000146<!-- *********************************************************************** -->
147
Misha Brukmanc5402402004-01-15 18:34:11 +0000148<div class="doc_text">
149
150<p>Here we describe how to write the "hello world" of passes. The "Hello" pass
151is designed to simply print out the name of non-external functions that exist in
Chris Lattner8fdb2462004-09-18 06:39:35 +0000152the program being compiled. It does not modify the program at all, it just
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000153inspects it. The source code and files for this pass are available in the LLVM
Misha Brukmanc5402402004-01-15 18:34:11 +0000154source tree in the <tt>lib/Transforms/Hello</tt> directory.</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000155
Misha Brukmanc5402402004-01-15 18:34:11 +0000156</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000157
158<!-- ======================================================================= -->
Misha Brukmanc5402402004-01-15 18:34:11 +0000159<div class="doc_subsection">
160 <a name="makefile">Setting up the build environment</a>
161</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000162
Misha Brukmanc5402402004-01-15 18:34:11 +0000163<div class="doc_text">
164
Reid Spencer1bc19342004-12-11 05:12:57 +0000165 <p>First, you need to create a new directory somewhere in the LLVM source
166 base. For this example, we'll assume that you made
167 <tt>lib/Transforms/Hello</tt>. Next, you must set up a build script
168 (Makefile) that will compile the source code for the new pass. To do this,
169 copy the following into <tt>Makefile</tt>:</p>
170 <hr/>
Misha Brukmanc5402402004-01-15 18:34:11 +0000171
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000172<div class="doc_code"><pre>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000173# Makefile for hello pass
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000174
Chris Lattner17a4c3e2002-08-14 20:06:13 +0000175# Path to top level of LLVM heirarchy
Chris Lattner7ce83e52002-08-14 20:07:01 +0000176LEVEL = ../../..
Chris Lattner17a4c3e2002-08-14 20:06:13 +0000177
178# Name of the library to build
Reid Spencer7fa6d522005-01-11 05:16:23 +0000179LIBRARYNAME = Hello
Chris Lattner17a4c3e2002-08-14 20:06:13 +0000180
Reid Spencer7fa6d522005-01-11 05:16:23 +0000181# Build a dynamically linkable shared object
Chris Lattner17a4c3e2002-08-14 20:06:13 +0000182SHARED_LIBRARY = 1
183
Reid Spencer7fa6d522005-01-11 05:16:23 +0000184# Make the shared library become a loadable module so the tools can
185# dlopen/dlsym on the resulting library.
Robert Bocchino3cf817d2006-01-06 22:49:23 +0000186LOADABLE_MODULE = 1
Reid Spencer7fa6d522005-01-11 05:16:23 +0000187
Chris Lattner17a4c3e2002-08-14 20:06:13 +0000188# Include the makefile implementation stuff
189include $(LEVEL)/Makefile.common
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000190</pre></div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000191
Misha Brukmanc5402402004-01-15 18:34:11 +0000192<p>This makefile specifies that all of the <tt>.cpp</tt> files in the current
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000193directory are to be compiled and linked together into a
Reid Spencer7fa6d522005-01-11 05:16:23 +0000194<tt>Debug/lib/Hello.so</tt> shared object that can be dynamically loaded by
195the <tt>opt</tt> or <tt>analyze</tt> tools via their <tt>-load</tt> options.
196If your operating system uses a suffix other than .so (such as windows or
197Mac OS/X), the appropriate extension will be used.</p>
John Criswellf9c78652004-01-26 21:26:54 +0000198
Misha Brukmanc5402402004-01-15 18:34:11 +0000199<p>Now that we have the build scripts set up, we just need to write the code for
200the pass itself.</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000201
Misha Brukmanc5402402004-01-15 18:34:11 +0000202</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000203
204<!-- ======================================================================= -->
Misha Brukmanc5402402004-01-15 18:34:11 +0000205<div class="doc_subsection">
206 <a name="basiccode">Basic code required</a>
207</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000208
Misha Brukmanc5402402004-01-15 18:34:11 +0000209<div class="doc_text">
210
211<p>Now that we have a way to compile our new pass, we just have to write it.
212Start out with:</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000213
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000214<div class="doc_code"><pre>
Reid Spencer05fe4b02006-03-14 05:39:39 +0000215<b>#include</b> "<a href="http://llvm.org/doxygen/Pass_8h-source.html">llvm/Pass.h</a>"
216<b>#include</b> "<a href="http://llvm.org/doxygen/Function_8h-source.html">llvm/Function.h</a>"
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000217</pre></div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000218
Misha Brukmanc5402402004-01-15 18:34:11 +0000219<p>Which are needed because we are writing a <tt><a
Reid Spencer05fe4b02006-03-14 05:39:39 +0000220href="http://llvm.org/doxygen/classllvm_1_1Pass.html">Pass</a></tt>, and
Misha Brukmanc5402402004-01-15 18:34:11 +0000221we are operating on <tt><a
Reid Spencer05fe4b02006-03-14 05:39:39 +0000222href="http://llvm.org/doxygen/classllvm_1_1Function.html">Function</a></tt>'s.</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000223
Misha Brukmanc5402402004-01-15 18:34:11 +0000224<p>Next we have:</p>
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000225<div class="doc_code"><pre>
Jonathan Manton65acb302004-06-30 18:10:30 +0000226<b>using namespace llvm;</b>
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000227</pre></div>
Jonathan Manton65acb302004-06-30 18:10:30 +0000228<p>... which is required because the functions from the include files
229live in the llvm namespace.
230</p>
231
232<p>Next we have:</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000233
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000234<div class="doc_code"><pre>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000235<b>namespace</b> {
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000236</pre></div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000237
Misha Brukmanc5402402004-01-15 18:34:11 +0000238<p>... which starts out an anonymous namespace. Anonymous namespaces are to C++
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000239what the "<tt>static</tt>" keyword is to C (at global scope). It makes the
240things declared inside of the anonymous namespace only visible to the current
241file. If you're not familiar with them, consult a decent C++ book for more
Misha Brukmanc5402402004-01-15 18:34:11 +0000242information.</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000243
Misha Brukmanc5402402004-01-15 18:34:11 +0000244<p>Next, we declare our pass itself:</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000245
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000246<div class="doc_code"><pre>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000247 <b>struct</b> Hello : <b>public</b> <a href="#FunctionPass">FunctionPass</a> {
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000248</pre></div><p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000249
Misha Brukmanc5402402004-01-15 18:34:11 +0000250<p>This declares a "<tt>Hello</tt>" class that is a subclass of <tt><a
Reid Spencer05fe4b02006-03-14 05:39:39 +0000251href="http://llvm.org/doxygen/classllvm_1_1FunctionPass.html">FunctionPass</a></tt>.
Chris Lattnerd6ea9262002-09-09 03:48:46 +0000252The different builtin pass subclasses are described in detail <a
Misha Brukmanc5402402004-01-15 18:34:11 +0000253href="#passtype">later</a>, but for now, know that <a
254href="#FunctionPass"><tt>FunctionPass</tt></a>'s operate a function at a
255time.</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000256
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000257<div class="doc_code"><pre>
Misha Brukmanc5402402004-01-15 18:34:11 +0000258 <b>virtual bool</b> <a href="#runOnFunction">runOnFunction</a>(Function &amp;F) {
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000259 std::cerr &lt;&lt; "<i>Hello: </i>" &lt;&lt; F.getName() &lt;&lt; "\n";
260 <b>return false</b>;
261 }
262 }; <i>// end of struct Hello</i>
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000263</pre></div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000264
Misha Brukmanc5402402004-01-15 18:34:11 +0000265<p>We declare a "<a href="#runOnFunction"><tt>runOnFunction</tt></a>" method,
266which overloads an abstract virtual method inherited from <a
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000267href="#FunctionPass"><tt>FunctionPass</tt></a>. This is where we are supposed
268to do our thing, so we just print out our message with the name of each
Misha Brukmanc5402402004-01-15 18:34:11 +0000269function.</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000270
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000271<div class="doc_code"><pre>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000272 RegisterOpt&lt;Hello&gt; X("<i>hello</i>", "<i>Hello World Pass</i>");
273} <i>// end of anonymous namespace</i>
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000274</pre></div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000275
Misha Brukmanc5402402004-01-15 18:34:11 +0000276<p>Lastly, we register our class <tt>Hello</tt>, giving it a command line
277argument "<tt>hello</tt>", and a name "<tt>Hello World Pass</tt>". There are
278several different ways of <a href="#registration">registering your pass</a>,
279depending on what it is to be used for. For "optimizations" we use the
280<tt>RegisterOpt</tt> template.</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000281
Misha Brukmanc5402402004-01-15 18:34:11 +0000282<p>As a whole, the <tt>.cpp</tt> file looks like:</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000283
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000284<div class="doc_code"><pre>
Reid Spencer05fe4b02006-03-14 05:39:39 +0000285<b>#include</b> "<a href="http://llvm.org/doxygen/Pass_8h-source.html">llvm/Pass.h</a>"
286<b>#include</b> "<a href="http://llvm.org/doxygen/Function_8h-source.html">llvm/Function.h</a>"
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000287
Jonathan Manton65acb302004-06-30 18:10:30 +0000288<b>using namespace llvm;</b>
289
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000290<b>namespace</b> {
291 <b>struct Hello</b> : <b>public</b> <a href="#FunctionPass">FunctionPass</a> {
Misha Brukmanc5402402004-01-15 18:34:11 +0000292 <b>virtual bool</b> <a href="#runOnFunction">runOnFunction</a>(Function &amp;F) {
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000293 std::cerr &lt;&lt; "<i>Hello: </i>" &lt;&lt; F.getName() &lt;&lt; "\n";
294 <b>return false</b>;
295 }
296 };
297
298 RegisterOpt&lt;Hello&gt; X("<i>hello</i>", "<i>Hello World Pass</i>");
299}
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000300</pre></div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000301
Misha Brukmanc5402402004-01-15 18:34:11 +0000302<p>Now that it's all together, compile the file with a simple "<tt>gmake</tt>"
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000303command in the local directory and you should get a new
Reid Spencer7fa6d522005-01-11 05:16:23 +0000304"<tt>Debug/lib/Hello.so</tt> file. Note that everything in this file is
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000305contained in an anonymous namespace: this reflects the fact that passes are self
306contained units that do not need external interfaces (although they can have
Misha Brukmanc5402402004-01-15 18:34:11 +0000307them) to be useful.</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000308
Misha Brukmanc5402402004-01-15 18:34:11 +0000309</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000310
311<!-- ======================================================================= -->
Misha Brukmanc5402402004-01-15 18:34:11 +0000312<div class="doc_subsection">
313 <a name="running">Running a pass with <tt>opt</tt> or <tt>analyze</tt></a>
314</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000315
Misha Brukmanc5402402004-01-15 18:34:11 +0000316<div class="doc_text">
317
John Criswellf9c78652004-01-26 21:26:54 +0000318<p>Now that you have a brand new shiny shared object file, we can use the
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000319<tt>opt</tt> command to run an LLVM program through your pass. Because you
320registered your pass with the <tt>RegisterOpt</tt> template, you will be able to
Misha Brukmanc5402402004-01-15 18:34:11 +0000321use the <tt>opt</tt> tool to access it, once loaded.</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000322
Misha Brukmanc5402402004-01-15 18:34:11 +0000323<p>To test it, follow the example at the end of the <a
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000324href="GettingStarted.html">Getting Started Guide</a> to compile "Hello World" to
325LLVM. We can now run the bytecode file (<tt>hello.bc</tt>) for the program
326through our transformation like this (or course, any bytecode file will
Misha Brukmanc5402402004-01-15 18:34:11 +0000327work):</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000328
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000329<div class="doc_code"><pre>
Reid Spencer7fa6d522005-01-11 05:16:23 +0000330$ opt -load ../../../Debug/lib/Hello.so -hello &lt; hello.bc &gt; /dev/null
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000331Hello: __main
332Hello: puts
333Hello: main
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000334</pre></div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000335
Misha Brukmanc5402402004-01-15 18:34:11 +0000336<p>The '<tt>-load</tt>' option specifies that '<tt>opt</tt>' should load your
337pass as a shared object, which makes '<tt>-hello</tt>' a valid command line
338argument (which is one reason you need to <a href="#registration">register your
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000339pass</a>). Because the hello pass does not modify the program in any
340interesting way, we just throw away the result of <tt>opt</tt> (sending it to
Misha Brukmanc5402402004-01-15 18:34:11 +0000341<tt>/dev/null</tt>).</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000342
Misha Brukmanc5402402004-01-15 18:34:11 +0000343<p>To see what happened to the other string you registered, try running
344<tt>opt</tt> with the <tt>--help</tt> option:</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000345
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000346<div class="doc_code"><pre>
Reid Spencer7fa6d522005-01-11 05:16:23 +0000347$ opt -load ../../../Debug/lib/Hello.so --help
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000348OVERVIEW: llvm .bc -&gt; .bc modular optimizer
349
350USAGE: opt [options] &lt;input bytecode&gt;
351
352OPTIONS:
353 Optimizations available:
354...
355 -funcresolve - Resolve Functions
356 -gcse - Global Common Subexpression Elimination
357 -globaldce - Dead Global Elimination
358 <b>-hello - Hello World Pass</b>
Chris Lattner065a6162003-09-10 05:29:43 +0000359 -indvars - Canonicalize Induction Variables
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000360 -inline - Function Integration/Inlining
361 -instcombine - Combine redundant instructions
362...
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000363</pre></div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000364
Misha Brukmanc5402402004-01-15 18:34:11 +0000365<p>The pass name get added as the information string for your pass, giving some
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000366documentation to users of <tt>opt</tt>. Now that you have a working pass, you
367would go ahead and make it do the cool transformations you want. Once you get
368it all working and tested, it may become useful to find out how fast your pass
369is. The <a href="#passManager"><tt>PassManager</tt></a> provides a nice command
370line option (<tt>--time-passes</tt>) that allows you to get information about
371the execution time of your pass along with the other passes you queue up. For
Misha Brukmanc5402402004-01-15 18:34:11 +0000372example:</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000373
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000374<div class="doc_code"><pre>
Reid Spencer7fa6d522005-01-11 05:16:23 +0000375$ opt -load ../../../Debug/lib/Hello.so -hello -time-passes &lt; hello.bc &gt; /dev/null
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000376Hello: __main
377Hello: puts
378Hello: main
379===============================================================================
380 ... Pass execution timing report ...
381===============================================================================
382 Total Execution Time: 0.02 seconds (0.0479059 wall clock)
383
384 ---User Time--- --System Time-- --User+System-- ---Wall Time--- --- Pass Name ---
385 0.0100 (100.0%) 0.0000 ( 0.0%) 0.0100 ( 50.0%) 0.0402 ( 84.0%) Bytecode Writer
386 0.0000 ( 0.0%) 0.0100 (100.0%) 0.0100 ( 50.0%) 0.0031 ( 6.4%) Dominator Set Construction
387 0.0000 ( 0.0%) 0.0000 ( 0.0%) 0.0000 ( 0.0%) 0.0013 ( 2.7%) Module Verifier
388 <b> 0.0000 ( 0.0%) 0.0000 ( 0.0%) 0.0000 ( 0.0%) 0.0033 ( 6.9%) Hello World Pass</b>
389 0.0100 (100.0%) 0.0100 (100.0%) 0.0200 (100.0%) 0.0479 (100.0%) TOTAL
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000390</pre></div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000391
Misha Brukmanc5402402004-01-15 18:34:11 +0000392<p>As you can see, our implementation above is pretty fast :). The additional
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000393passes listed are automatically inserted by the '<tt>opt</tt>' tool to verify
394that the LLVM emitted by your pass is still valid and well formed LLVM, which
Misha Brukmanc5402402004-01-15 18:34:11 +0000395hasn't been broken somehow.</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000396
Misha Brukmanc5402402004-01-15 18:34:11 +0000397<p>Now that you have seen the basics of the mechanics behind passes, we can talk
398about some more details of how they work and how to use them.</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000399
Misha Brukmanc5402402004-01-15 18:34:11 +0000400</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000401
402<!-- *********************************************************************** -->
Misha Brukmanc5402402004-01-15 18:34:11 +0000403<div class="doc_section">
404 <a name="passtype">Pass classes and requirements</a>
405</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000406<!-- *********************************************************************** -->
407
Misha Brukmanc5402402004-01-15 18:34:11 +0000408<div class="doc_text">
409
410<p>One of the first things that you should do when designing a new pass is to
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000411decide what class you should subclass for your pass. The <a
412href="#basiccode">Hello World</a> example uses the <tt><a
413href="#FunctionPass">FunctionPass</a></tt> class for its implementation, but we
414did not discuss why or when this should occur. Here we talk about the classes
Misha Brukmanc5402402004-01-15 18:34:11 +0000415available, from the most general to the most specific.</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000416
Misha Brukmanc5402402004-01-15 18:34:11 +0000417<p>When choosing a superclass for your Pass, you should choose the <b>most
Chris Lattner79910702002-08-22 19:21:04 +0000418specific</b> class possible, while still being able to meet the requirements
Misha Brukman5560c9d2003-08-18 14:43:39 +0000419listed. This gives the LLVM Pass Infrastructure information necessary to
Chris Lattner79910702002-08-22 19:21:04 +0000420optimize how passes are run, so that the resultant compiler isn't unneccesarily
Misha Brukmanc5402402004-01-15 18:34:11 +0000421slow.</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000422
Misha Brukmanc5402402004-01-15 18:34:11 +0000423</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000424
Chris Lattnerf004f9a2002-09-25 22:31:38 +0000425<!-- ======================================================================= -->
Misha Brukmanc5402402004-01-15 18:34:11 +0000426<div class="doc_subsection">
427 <a name="ImmutablePass">The <tt>ImmutablePass</tt> class</a>
428</div>
Chris Lattnerf004f9a2002-09-25 22:31:38 +0000429
Misha Brukmanc5402402004-01-15 18:34:11 +0000430<div class="doc_text">
431
432<p>The most plain and boring type of pass is the "<tt><a
Reid Spencer05fe4b02006-03-14 05:39:39 +0000433href="http://llvm.org/doxygen/classllvm_1_1ImmutablePass.html">ImmutablePass</a></tt>"
Chris Lattnerf004f9a2002-09-25 22:31:38 +0000434class. This pass type is used for passes that do not have to be run, do not
435change state, and never need to be updated. This is not a normal type of
436transformation or analysis, but can provide information about the current
Misha Brukmanc5402402004-01-15 18:34:11 +0000437compiler configuration.</p>
Chris Lattnerf004f9a2002-09-25 22:31:38 +0000438
Misha Brukmanc5402402004-01-15 18:34:11 +0000439<p>Although this pass class is very infrequently used, it is important for
Chris Lattnerf004f9a2002-09-25 22:31:38 +0000440providing information about the current target machine being compiled for, and
Misha Brukmanc5402402004-01-15 18:34:11 +0000441other static information that can affect the various transformations.</p>
Chris Lattnerf004f9a2002-09-25 22:31:38 +0000442
Misha Brukmanc5402402004-01-15 18:34:11 +0000443<p><tt>ImmutablePass</tt>es never invalidate other transformations, are never
444invalidated, and are never "run".</p>
Chris Lattnerf004f9a2002-09-25 22:31:38 +0000445
Misha Brukmanc5402402004-01-15 18:34:11 +0000446</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000447
448<!-- ======================================================================= -->
Misha Brukmanc5402402004-01-15 18:34:11 +0000449<div class="doc_subsection">
Chris Lattnerf6278922004-09-20 04:36:29 +0000450 <a name="ModulePass">The <tt>ModulePass</tt> class</a>
Misha Brukmanc5402402004-01-15 18:34:11 +0000451</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000452
Misha Brukmanc5402402004-01-15 18:34:11 +0000453<div class="doc_text">
454
455<p>The "<tt><a
Reid Spencer05fe4b02006-03-14 05:39:39 +0000456href="http://llvm.org/doxygen/classllvm_1_1ModulePass.html">ModulePass</a></tt>"
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000457class is the most general of all superclasses that you can use. Deriving from
Chris Lattnerf6278922004-09-20 04:36:29 +0000458<tt>ModulePass</tt> indicates that your pass uses the entire program as a unit,
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000459refering to function bodies in no predictable order, or adding and removing
Chris Lattnerf6278922004-09-20 04:36:29 +0000460functions. Because nothing is known about the behavior of <tt>ModulePass</tt>
Misha Brukmanc5402402004-01-15 18:34:11 +0000461subclasses, no optimization can be done for their execution.</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000462
Chris Lattnerf6278922004-09-20 04:36:29 +0000463<p>To write a correct <tt>ModulePass</tt> subclass, derive from
464<tt>ModulePass</tt> and overload the <tt>runOnModule</tt> method with the
465following signature:</p>
Misha Brukmanc5402402004-01-15 18:34:11 +0000466
467</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000468
469<!-- _______________________________________________________________________ -->
Misha Brukmanc5402402004-01-15 18:34:11 +0000470<div class="doc_subsubsection">
Chris Lattnerf6278922004-09-20 04:36:29 +0000471 <a name="runOnModule">The <tt>runOnModule</tt> method</a>
Misha Brukmanc5402402004-01-15 18:34:11 +0000472</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000473
Misha Brukmanc5402402004-01-15 18:34:11 +0000474<div class="doc_text">
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000475
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000476<div class="doc_code"><pre>
Chris Lattnerf6278922004-09-20 04:36:29 +0000477 <b>virtual bool</b> runOnModule(Module &amp;M) = 0;
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000478</pre></div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000479
John Criswell2382ff72005-07-15 19:25:12 +0000480<p>The <tt>runOnModule</tt> method performs the interesting work of the pass.
481It should return true if the module was modified by the transformation and
482false otherwise.</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000483
Misha Brukmanc5402402004-01-15 18:34:11 +0000484</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000485
486<!-- ======================================================================= -->
Misha Brukmanc5402402004-01-15 18:34:11 +0000487<div class="doc_subsection">
Chris Lattner8fdb2462004-09-18 06:39:35 +0000488 <a name="CallGraphSCCPass">The <tt>CallGraphSCCPass</tt> class</a>
489</div>
490
491<div class="doc_text">
492
493<p>The "<tt><a
Reid Spencer05fe4b02006-03-14 05:39:39 +0000494href="http://llvm.org/doxygen/classllvm_1_1CallGraphSCCPass.html">CallGraphSCCPass</a></tt>"
Chris Lattner8fdb2462004-09-18 06:39:35 +0000495is used by passes that need to traverse the program bottom-up on the call graph
496(callees before callers). Deriving from CallGraphSCCPass provides some
497mechanics for building and traversing the CallGraph, but also allows the system
498to optimize execution of CallGraphSCCPass's. If your pass meets the
499requirements outlined below, and doesn't meet the requirements of a <tt><a
500href="#FunctionPass">FunctionPass</a></tt> or <tt><a
501href="#BasicBlockPass">BasicBlockPass</a></tt>, you should derive from
502<tt>CallGraphSCCPass</tt>.</p>
503
504<p><b>TODO</b>: explain briefly what SCC, Tarjan's algo, and B-U mean.</p>
505
506<p>To be explicit, <tt>CallGraphSCCPass</tt> subclasses are:</p>
507
508<ol>
509
510<li>... <em>not allowed</em> to modify any <tt>Function</tt>s that are not in
511the current SCC.</li>
512
513<li>... <em>allowed</em> to inspect any Function's other than those in the
514current SCC and the direct callees of the SCC.</li>
515
516<li>... <em>required</em> to preserve the current CallGraph object, updating it
517to reflect any changes made to the program.</li>
518
519<li>... <em>not allowed</em> to add or remove SCC's from the current Module,
520though they may change the contents of an SCC.</li>
521
522<li>... <em>allowed</em> to add or remove global variables from the current
523Module.</li>
524
525<li>... <em>allowed</em> to maintain state across invocations of
526 <a href="#runOnSCC"><tt>runOnSCC</tt></a> (including global data).</li>
527</ol>
528
529<p>Implementing a <tt>CallGraphSCCPass</tt> is slightly tricky in some cases
530because it has to handle SCCs with more than one node in it. All of the virtual
531methods described below should return true if they modified the program, or
532false if they didn't.</p>
533
534</div>
535
536<!-- _______________________________________________________________________ -->
537<div class="doc_subsubsection">
538 <a name="doInitialization_scc">The <tt>doInitialization(Module &amp;)</tt>
539 method</a>
540</div>
541
542<div class="doc_text">
543
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000544<div class="doc_code"><pre>
Chris Lattner8fdb2462004-09-18 06:39:35 +0000545 <b>virtual bool</b> doInitialization(Module &amp;M);
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000546</pre></div>
Chris Lattner8fdb2462004-09-18 06:39:35 +0000547
548<p>The <tt>doIninitialize</tt> method is allowed to do most of the things that
549<tt>CallGraphSCCPass</tt>'s are not allowed to do. They can add and remove
550functions, get pointers to functions, etc. The <tt>doInitialization</tt> method
551is designed to do simple initialization type of stuff that does not depend on
552the SCCs being processed. The <tt>doInitialization</tt> method call is not
553scheduled to overlap with any other pass executions (thus it should be very
554fast).</p>
555
556</div>
557
558<!-- _______________________________________________________________________ -->
559<div class="doc_subsubsection">
560 <a name="runOnSCC">The <tt>runOnSCC</tt> method</a>
561</div>
562
563<div class="doc_text">
564
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000565<div class="doc_code"><pre>
Chris Lattner8fdb2462004-09-18 06:39:35 +0000566 <b>virtual bool</b> runOnSCC(const std::vector&lt;CallGraphNode *&gt; &amp;SCCM) = 0;
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000567</pre></div>
Chris Lattner8fdb2462004-09-18 06:39:35 +0000568
569<p>The <tt>runOnSCC</tt> method performs the interesting work of the pass, and
570should return true if the module was modified by the transformation, false
571otherwise.</p>
572
573</div>
574
575<!-- _______________________________________________________________________ -->
576<div class="doc_subsubsection">
577 <a name="doFinalization_scc">The <tt>doFinalization(Module
578 &amp;)</tt> method</a>
579</div>
580
581<div class="doc_text">
582
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000583<div class="doc_code"><pre>
Chris Lattner8fdb2462004-09-18 06:39:35 +0000584 <b>virtual bool</b> doFinalization(Module &amp;M);
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000585</pre></div>
Chris Lattner8fdb2462004-09-18 06:39:35 +0000586
587<p>The <tt>doFinalization</tt> method is an infrequently used method that is
588called when the pass framework has finished calling <a
589href="#runOnFunction"><tt>runOnFunction</tt></a> for every function in the
590program being compiled.</p>
591
592</div>
593
594<!-- ======================================================================= -->
595<div class="doc_subsection">
Misha Brukmanc5402402004-01-15 18:34:11 +0000596 <a name="FunctionPass">The <tt>FunctionPass</tt> class</a>
597</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000598
Misha Brukmanc5402402004-01-15 18:34:11 +0000599<div class="doc_text">
600
Chris Lattnerf6278922004-09-20 04:36:29 +0000601<p>In contrast to <tt>ModulePass</tt> subclasses, <tt><a
Reid Spencer05fe4b02006-03-14 05:39:39 +0000602href="http://llvm.org/doxygen/classllvm_1_1Pass.html">FunctionPass</a></tt>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000603subclasses do have a predictable, local behavior that can be expected by the
604system. All <tt>FunctionPass</tt> execute on each function in the program
Misha Brukmanef6a6a62003-08-21 22:14:26 +0000605independent of all of the other functions in the program.
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000606<tt>FunctionPass</tt>'s do not require that they are executed in a particular
Misha Brukmanc5402402004-01-15 18:34:11 +0000607order, and <tt>FunctionPass</tt>'s do not modify external functions.</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000608
Misha Brukmanc5402402004-01-15 18:34:11 +0000609<p>To be explicit, <tt>FunctionPass</tt> subclasses are not allowed to:</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000610
611<ol>
Misha Brukmanc5402402004-01-15 18:34:11 +0000612<li>Modify a Function other than the one currently being processed.</li>
613<li>Add or remove Function's from the current Module.</li>
614<li>Add or remove global variables from the current Module.</li>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000615<li>Maintain state across invocations of
Misha Brukmanc5402402004-01-15 18:34:11 +0000616 <a href="#runOnFunction"><tt>runOnFunction</tt></a> (including global data)</li>
617</ol>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000618
Misha Brukmanc5402402004-01-15 18:34:11 +0000619<p>Implementing a <tt>FunctionPass</tt> is usually straightforward (See the <a
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000620href="#basiccode">Hello World</a> pass for example). <tt>FunctionPass</tt>'s
621may overload three virtual methods to do their work. All of these methods
Misha Brukmanc5402402004-01-15 18:34:11 +0000622should return true if they modified the program, or false if they didn't.</p>
623
624</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000625
626<!-- _______________________________________________________________________ -->
Chris Lattner89256272004-03-17 21:09:55 +0000627<div class="doc_subsubsection">
Misha Brukmanc5402402004-01-15 18:34:11 +0000628 <a name="doInitialization_mod">The <tt>doInitialization(Module &amp;)</tt>
629 method</a>
630</div>
631
632<div class="doc_text">
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000633
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000634<div class="doc_code"><pre>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000635 <b>virtual bool</b> doInitialization(Module &amp;M);
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000636</pre></div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000637
Misha Brukmanc5402402004-01-15 18:34:11 +0000638<p>The <tt>doIninitialize</tt> method is allowed to do most of the things that
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000639<tt>FunctionPass</tt>'s are not allowed to do. They can add and remove
Chris Lattnerd0713f92002-09-12 17:06:43 +0000640functions, get pointers to functions, etc. The <tt>doInitialization</tt> method
641is designed to do simple initialization type of stuff that does not depend on
642the functions being processed. The <tt>doInitialization</tt> method call is not
643scheduled to overlap with any other pass executions (thus it should be very
Misha Brukmanc5402402004-01-15 18:34:11 +0000644fast).</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000645
Misha Brukmanc5402402004-01-15 18:34:11 +0000646<p>A good example of how this method should be used is the <a
Reid Spencer05fe4b02006-03-14 05:39:39 +0000647href="http://llvm.org/doxygen/LowerAllocations_8cpp-source.html">LowerAllocations</a>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000648pass. This pass converts <tt>malloc</tt> and <tt>free</tt> instructions into
Misha Brukmanef6a6a62003-08-21 22:14:26 +0000649platform dependent <tt>malloc()</tt> and <tt>free()</tt> function calls. It
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000650uses the <tt>doInitialization</tt> method to get a reference to the malloc and
Misha Brukmanc5402402004-01-15 18:34:11 +0000651free functions that it needs, adding prototypes to the module if necessary.</p>
652
653</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000654
655<!-- _______________________________________________________________________ -->
Chris Lattner89256272004-03-17 21:09:55 +0000656<div class="doc_subsubsection">
Misha Brukmanc5402402004-01-15 18:34:11 +0000657 <a name="runOnFunction">The <tt>runOnFunction</tt> method</a>
658</div>
659
660<div class="doc_text">
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000661
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000662<div class="doc_code"><pre>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000663 <b>virtual bool</b> runOnFunction(Function &amp;F) = 0;
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000664</pre></div><p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000665
Misha Brukmanc5402402004-01-15 18:34:11 +0000666<p>The <tt>runOnFunction</tt> method must be implemented by your subclass to do
667the transformation or analysis work of your pass. As usual, a true value should
668be returned if the function is modified.</p>
669
670</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000671
672<!-- _______________________________________________________________________ -->
Chris Lattner89256272004-03-17 21:09:55 +0000673<div class="doc_subsubsection">
Misha Brukmanc5402402004-01-15 18:34:11 +0000674 <a name="doFinalization_mod">The <tt>doFinalization(Module
675 &amp;)</tt> method</a>
676</div>
677
678<div class="doc_text">
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000679
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000680<div class="doc_code"><pre>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000681 <b>virtual bool</b> doFinalization(Module &amp;M);
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000682</pre></div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000683
Misha Brukmanc5402402004-01-15 18:34:11 +0000684<p>The <tt>doFinalization</tt> method is an infrequently used method that is
685called when the pass framework has finished calling <a
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000686href="#runOnFunction"><tt>runOnFunction</tt></a> for every function in the
Misha Brukmanc5402402004-01-15 18:34:11 +0000687program being compiled.</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000688
Misha Brukmanc5402402004-01-15 18:34:11 +0000689</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000690
691<!-- ======================================================================= -->
Misha Brukmanc5402402004-01-15 18:34:11 +0000692<div class="doc_subsection">
693 <a name="BasicBlockPass">The <tt>BasicBlockPass</tt> class</a>
694</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000695
Misha Brukmanc5402402004-01-15 18:34:11 +0000696<div class="doc_text">
697
698<p><tt>BasicBlockPass</tt>'s are just like <a
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000699href="#FunctionPass"><tt>FunctionPass</tt></a>'s, except that they must limit
700their scope of inspection and modification to a single basic block at a time.
Misha Brukmanc5402402004-01-15 18:34:11 +0000701As such, they are <b>not</b> allowed to do any of the following:</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000702
703<ol>
Misha Brukmanc5402402004-01-15 18:34:11 +0000704<li>Modify or inspect any basic blocks outside of the current one</li>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000705<li>Maintain state across invocations of
Misha Brukmanc5402402004-01-15 18:34:11 +0000706 <a href="#runOnBasicBlock"><tt>runOnBasicBlock</tt></a></li>
Reid Spencer1bc19342004-12-11 05:12:57 +0000707<li>Modify the control flow graph (by altering terminator instructions)</li>
708<li>Any of the things forbidden for
Misha Brukmanc5402402004-01-15 18:34:11 +0000709 <a href="#FunctionPass"><tt>FunctionPass</tt></a>es.</li>
710</ol>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000711
Misha Brukmanc5402402004-01-15 18:34:11 +0000712<p><tt>BasicBlockPass</tt>es are useful for traditional local and "peephole"
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000713optimizations. They may override the same <a
Chris Lattnerd0713f92002-09-12 17:06:43 +0000714href="#doInitialization_mod"><tt>doInitialization(Module &amp;)</tt></a> and <a
715href="#doFinalization_mod"><tt>doFinalization(Module &amp;)</tt></a> methods that <a
Misha Brukmanc5402402004-01-15 18:34:11 +0000716href="#FunctionPass"><tt>FunctionPass</tt></a>'s have, but also have the following virtual methods that may also be implemented:</p>
717
718</div>
Chris Lattnerd0713f92002-09-12 17:06:43 +0000719
720<!-- _______________________________________________________________________ -->
Chris Lattner89256272004-03-17 21:09:55 +0000721<div class="doc_subsubsection">
Misha Brukmanc5402402004-01-15 18:34:11 +0000722 <a name="doInitialization_fn">The <tt>doInitialization(Function
723 &amp;)</tt> method</a>
724</div>
725
726<div class="doc_text">
Chris Lattnerd0713f92002-09-12 17:06:43 +0000727
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000728<div class="doc_code"><pre>
Chris Lattnerd0713f92002-09-12 17:06:43 +0000729 <b>virtual bool</b> doInitialization(Function &amp;F);
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000730</pre></div>
Chris Lattnerd0713f92002-09-12 17:06:43 +0000731
Misha Brukmanc5402402004-01-15 18:34:11 +0000732<p>The <tt>doIninitialize</tt> method is allowed to do most of the things that
Chris Lattnerd0713f92002-09-12 17:06:43 +0000733<tt>BasicBlockPass</tt>'s are not allowed to do, but that
734<tt>FunctionPass</tt>'s can. The <tt>doInitialization</tt> method is designed
Reid Spencer1bc19342004-12-11 05:12:57 +0000735to do simple initialization that does not depend on the
Chris Lattnerd0713f92002-09-12 17:06:43 +0000736BasicBlocks being processed. The <tt>doInitialization</tt> method call is not
737scheduled to overlap with any other pass executions (thus it should be very
Misha Brukmanc5402402004-01-15 18:34:11 +0000738fast).</p>
Chris Lattnerd0713f92002-09-12 17:06:43 +0000739
Misha Brukmanc5402402004-01-15 18:34:11 +0000740</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000741
742<!-- _______________________________________________________________________ -->
Chris Lattner89256272004-03-17 21:09:55 +0000743<div class="doc_subsubsection">
Misha Brukmanc5402402004-01-15 18:34:11 +0000744 <a name="runOnBasicBlock">The <tt>runOnBasicBlock</tt> method</a>
745</div>
746
747<div class="doc_text">
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000748
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000749<div class="doc_code"><pre>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000750 <b>virtual bool</b> runOnBasicBlock(BasicBlock &amp;BB) = 0;
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000751</pre></div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000752
Misha Brukmanc5402402004-01-15 18:34:11 +0000753<p>Override this function to do the work of the <tt>BasicBlockPass</tt>. This
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000754function is not allowed to inspect or modify basic blocks other than the
755parameter, and are not allowed to modify the CFG. A true value must be returned
Misha Brukmanc5402402004-01-15 18:34:11 +0000756if the basic block is modified.</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000757
Misha Brukmanc5402402004-01-15 18:34:11 +0000758</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000759
Chris Lattnerd0713f92002-09-12 17:06:43 +0000760<!-- _______________________________________________________________________ -->
Chris Lattner89256272004-03-17 21:09:55 +0000761<div class="doc_subsubsection">
Misha Brukmanc5402402004-01-15 18:34:11 +0000762 <a name="doFinalization_fn">The <tt>doFinalization(Function &amp;)</tt>
763 method</a>
764</div>
765
766<div class="doc_text">
Chris Lattnerd0713f92002-09-12 17:06:43 +0000767
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000768<div class="doc_code"><pre>
Chris Lattnerd0713f92002-09-12 17:06:43 +0000769 <b>virtual bool</b> doFinalization(Function &amp;F);
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000770</pre></div>
Chris Lattnerd0713f92002-09-12 17:06:43 +0000771
Misha Brukmanc5402402004-01-15 18:34:11 +0000772<p>The <tt>doFinalization</tt> method is an infrequently used method that is
773called when the pass framework has finished calling <a
Chris Lattnerd0713f92002-09-12 17:06:43 +0000774href="#runOnBasicBlock"><tt>runOnBasicBlock</tt></a> for every BasicBlock in the
775program being compiled. This can be used to perform per-function
Misha Brukmanc5402402004-01-15 18:34:11 +0000776finalization.</p>
Chris Lattnerd0713f92002-09-12 17:06:43 +0000777
Misha Brukmanc5402402004-01-15 18:34:11 +0000778</div>
Chris Lattnerd0713f92002-09-12 17:06:43 +0000779
Brian Gaekecab8b6f2003-07-17 18:53:20 +0000780<!-- ======================================================================= -->
Misha Brukmanc5402402004-01-15 18:34:11 +0000781<div class="doc_subsection">
782 <a name="MachineFunctionPass">The <tt>MachineFunctionPass</tt> class</a>
783</div>
Brian Gaekecab8b6f2003-07-17 18:53:20 +0000784
Misha Brukmanc5402402004-01-15 18:34:11 +0000785<div class="doc_text">
786
Chris Lattner89256272004-03-17 21:09:55 +0000787<p>A <tt>MachineFunctionPass</tt> is a part of the LLVM code generator that
788executes on the machine-dependent representation of each LLVM function in the
789program. A <tt>MachineFunctionPass</tt> is also a <tt>FunctionPass</tt>, so all
Brian Gaekecab8b6f2003-07-17 18:53:20 +0000790the restrictions that apply to a <tt>FunctionPass</tt> also apply to it.
Chris Lattner89256272004-03-17 21:09:55 +0000791<tt>MachineFunctionPass</tt>es also have additional restrictions. In particular,
792<tt>MachineFunctionPass</tt>es are not allowed to do any of the following:</p>
Brian Gaekecab8b6f2003-07-17 18:53:20 +0000793
794<ol>
Misha Brukmanc5402402004-01-15 18:34:11 +0000795<li>Modify any LLVM Instructions, BasicBlocks or Functions.</li>
796<li>Modify a MachineFunction other than the one currently being processed.</li>
797<li>Add or remove MachineFunctions from the current Module.</li>
798<li>Add or remove global variables from the current Module.</li>
799<li>Maintain state across invocations of <a
800href="#runOnMachineFunction"><tt>runOnMachineFunction</tt></a> (including global
801data)</li>
802</ol>
Brian Gaekecab8b6f2003-07-17 18:53:20 +0000803
Misha Brukmanc5402402004-01-15 18:34:11 +0000804</div>
Chris Lattnerd0713f92002-09-12 17:06:43 +0000805
Brian Gaeke6a33f362003-07-22 20:53:20 +0000806<!-- _______________________________________________________________________ -->
Chris Lattner89256272004-03-17 21:09:55 +0000807<div class="doc_subsubsection">
Misha Brukmanc5402402004-01-15 18:34:11 +0000808 <a name="runOnMachineFunction">The <tt>runOnMachineFunction(MachineFunction
809 &amp;MF)</tt> method</a>
810</div>
811
812<div class="doc_text">
Brian Gaeke6a33f362003-07-22 20:53:20 +0000813
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000814<div class="doc_code"><pre>
Brian Gaeke6a33f362003-07-22 20:53:20 +0000815 <b>virtual bool</b> runOnMachineFunction(MachineFunction &amp;MF) = 0;
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000816</pre></div>
Brian Gaeke6a33f362003-07-22 20:53:20 +0000817
Misha Brukmanc5402402004-01-15 18:34:11 +0000818<p><tt>runOnMachineFunction</tt> can be considered the main entry point of a
819<tt>MachineFunctionPass</tt>; that is, you should override this method to do the
820work of your <tt>MachineFunctionPass</tt>.</p>
Brian Gaeke6a33f362003-07-22 20:53:20 +0000821
Misha Brukmanc5402402004-01-15 18:34:11 +0000822<p>The <tt>runOnMachineFunction</tt> method is called on every
Brian Gaeke6a33f362003-07-22 20:53:20 +0000823<tt>MachineFunction</tt> in a <tt>Module</tt>, so that the
Misha Brukmanc5402402004-01-15 18:34:11 +0000824<tt>MachineFunctionPass</tt> may perform optimizations on the machine-dependent
825representation of the function. If you want to get at the LLVM <tt>Function</tt>
826for the <tt>MachineFunction</tt> you're working on, use
827<tt>MachineFunction</tt>'s <tt>getFunction()</tt> accessor method -- but
828remember, you may not modify the LLVM <tt>Function</tt> or its contents from a
829<tt>MachineFunctionPass</tt>.</p>
830
831</div>
Brian Gaeke6a33f362003-07-22 20:53:20 +0000832
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000833<!-- *********************************************************************** -->
Misha Brukmanc5402402004-01-15 18:34:11 +0000834<div class="doc_section">
835 <a name="registration">Pass registration</a>
836</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000837<!-- *********************************************************************** -->
838
Misha Brukmanc5402402004-01-15 18:34:11 +0000839<div class="doc_text">
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000840
Misha Brukmanc5402402004-01-15 18:34:11 +0000841<p>In the <a href="#basiccode">Hello World</a> example pass we illustrated how
842pass registration works, and discussed some of the reasons that it is used and
843what it does. Here we discuss how and why passes are registered.</p>
844
845<p>Passes can be registered in several different ways. Depending on the general
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000846classification of the pass, you should use one of the following templates to
Misha Brukmanc5402402004-01-15 18:34:11 +0000847register the pass:</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000848
849<ul>
850<li><b><tt>RegisterOpt</tt></b> - This template should be used when you are
851registering a pass that logically should be available for use in the
Misha Brukmanc5402402004-01-15 18:34:11 +0000852'<tt>opt</tt>' utility.</li>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000853
854<li><b><tt>RegisterAnalysis</tt></b> - This template should be used when you are
855registering a pass that logically should be available for use in the
Chris Lattner89256272004-03-17 21:09:55 +0000856'<tt>analyze</tt>' utility.</li>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000857
858<li><b><tt>RegisterPass</tt></b> - This is the generic form of the
859<tt>Register*</tt> templates that should be used if you want your pass listed by
860multiple or no utilities. This template takes an extra third argument that
861specifies which tools it should be listed in. See the <a
Reid Spencer05fe4b02006-03-14 05:39:39 +0000862href="http://llvm.org/doxygen/PassSupport_8h-source.html">PassSupport.h</a>
Misha Brukmanc5402402004-01-15 18:34:11 +0000863file for more information.</li>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000864
Misha Brukmanc5402402004-01-15 18:34:11 +0000865</ul>
866
867<p>Regardless of how you register your pass, you must specify at least two
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000868parameters. The first parameter is the name of the pass that is to be used on
869the command line to specify that the pass should be added to a program (for
870example <tt>opt</tt> or <tt>analyze</tt>). The second argument is the name of
871the pass, which is to be used for the <tt>--help</tt> output of programs, as
Misha Brukmanc5402402004-01-15 18:34:11 +0000872well as for debug output generated by the <tt>--debug-pass</tt> option.</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000873
Misha Brukmanc5402402004-01-15 18:34:11 +0000874<p>If a pass is registered to be used by the <tt>analyze</tt> utility, you
875should implement the virtual <tt>print</tt> method:</p>
876
877</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000878
879<!-- _______________________________________________________________________ -->
Misha Brukmanc5402402004-01-15 18:34:11 +0000880<div class="doc_subsubsection">
881 <a name="print">The <tt>print</tt> method</a>
882</div>
883
884<div class="doc_text">
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000885
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000886<div class="doc_code"><pre>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000887 <b>virtual void</b> print(std::ostream &amp;O, <b>const</b> Module *M) <b>const</b>;
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000888</pre></div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000889
Misha Brukmanc5402402004-01-15 18:34:11 +0000890<p>The <tt>print</tt> method must be implemented by "analyses" in order to print
891a human readable version of the analysis results. This is useful for debugging
892an analysis itself, as well as for other people to figure out how an analysis
893works. The <tt>analyze</tt> tool uses this method to generate its output.</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000894
Misha Brukmanc5402402004-01-15 18:34:11 +0000895<p>The <tt>ostream</tt> parameter specifies the stream to write the results on,
896and the <tt>Module</tt> parameter gives a pointer to the top level module of the
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000897program that has been analyzed. Note however that this pointer may be null in
898certain circumstances (such as calling the <tt>Pass::dump()</tt> from a
899debugger), so it should only be used to enhance debug output, it should not be
Misha Brukmanc5402402004-01-15 18:34:11 +0000900depended on.</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000901
Misha Brukmanc5402402004-01-15 18:34:11 +0000902</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000903
904<!-- *********************************************************************** -->
Misha Brukmanc5402402004-01-15 18:34:11 +0000905<div class="doc_section">
906 <a name="interaction">Specifying interactions between passes</a>
907</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000908<!-- *********************************************************************** -->
909
Misha Brukmanc5402402004-01-15 18:34:11 +0000910<div class="doc_text">
911
912<p>One of the main responsibilities of the <tt>PassManager</tt> is the make sure
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000913that passes interact with each other correctly. Because <tt>PassManager</tt>
914tries to <a href="#passmanager">optimize the execution of passes</a> it must
915know how the passes interact with each other and what dependencies exist between
916the various passes. To track this, each pass can declare the set of passes that
917are required to be executed before the current pass, and the passes which are
Misha Brukmanc5402402004-01-15 18:34:11 +0000918invalidated by the current pass.</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000919
Misha Brukmanc5402402004-01-15 18:34:11 +0000920<p>Typically this functionality is used to require that analysis results are
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000921computed before your pass is run. Running arbitrary transformation passes can
922invalidate the computed analysis results, which is what the invalidation set
923specifies. If a pass does not implement the <tt><a
924href="#getAnalysisUsage">getAnalysisUsage</a></tt> method, it defaults to not
Misha Brukmanc5402402004-01-15 18:34:11 +0000925having any prerequisite passes, and invalidating <b>all</b> other passes.</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000926
Misha Brukmanc5402402004-01-15 18:34:11 +0000927</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000928
929<!-- _______________________________________________________________________ -->
Misha Brukmanc5402402004-01-15 18:34:11 +0000930<div class="doc_subsubsection">
931 <a name="getAnalysisUsage">The <tt>getAnalysisUsage</tt> method</a>
932</div>
933
934<div class="doc_text">
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000935
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000936<div class="doc_code"><pre>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000937 <b>virtual void</b> getAnalysisUsage(AnalysisUsage &amp;Info) <b>const</b>;
Jim Laskey5fa8fff2006-08-04 18:10:12 +0000938</pre></div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000939
Misha Brukmanc5402402004-01-15 18:34:11 +0000940<p>By implementing the <tt>getAnalysisUsage</tt> method, the required and
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000941invalidated sets may be specified for your transformation. The implementation
942should fill in the <tt><a
Reid Spencer05fe4b02006-03-14 05:39:39 +0000943href="http://llvm.org/doxygen/classllvm_1_1AnalysisUsage.html">AnalysisUsage</a></tt>
Misha Brukmanc5402402004-01-15 18:34:11 +0000944object with information about which passes are required and not invalidated. To
Chris Lattner89256272004-03-17 21:09:55 +0000945do this, a pass may call any of the following methods on the AnalysisUsage
946object:</p>
947</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000948
Chris Lattner89256272004-03-17 21:09:55 +0000949<!-- _______________________________________________________________________ -->
950<div class="doc_subsubsection">
951 <a name="AU::addRequired">The <tt>AnalysisUsage::addRequired&lt;&gt;</tt> and <tt>AnalysisUsage::addRequiredTransitive&lt;&gt;</tt> methods</a>
952</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000953
Chris Lattner89256272004-03-17 21:09:55 +0000954<div class="doc_text">
955<p>
Reid Spencer1bc19342004-12-11 05:12:57 +0000956If your pass requires a previous pass to be executed (an analysis for example),
Chris Lattner89256272004-03-17 21:09:55 +0000957it can use one of these methods to arrange for it to be run before your pass.
958LLVM has many different types of analyses and passes that can be required,
Reid Spencer1bc19342004-12-11 05:12:57 +0000959spanning the range from <tt>DominatorSet</tt> to <tt>BreakCriticalEdges</tt>.
960Requiring <tt>BreakCriticalEdges</tt>, for example, guarantees that there will
Chris Lattner89256272004-03-17 21:09:55 +0000961be no critical edges in the CFG when your pass has been run.
962</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000963
Chris Lattner89256272004-03-17 21:09:55 +0000964<p>
965Some analyses chain to other analyses to do their job. For example, an <a
966href="AliasAnalysis.html">AliasAnalysis</a> implementation is required to <a
967href="AliasAnalysis.html#chaining">chain</a> to other alias analysis passes. In
968cases where analyses chain, the <tt>addRequiredTransitive</tt> method should be
969used instead of the <tt>addRequired</tt> method. This informs the PassManager
970that the transitively required pass should be alive as long as the requiring
971pass is.
972</p>
973</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000974
Chris Lattner89256272004-03-17 21:09:55 +0000975<!-- _______________________________________________________________________ -->
976<div class="doc_subsubsection">
977 <a name="AU::addPreserved">The <tt>AnalysisUsage::addPreserved&lt;&gt;</tt> method</a>
978</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +0000979
Chris Lattner89256272004-03-17 21:09:55 +0000980<div class="doc_text">
981<p>
982One of the jobs of the PassManager is to optimize how and when analyses are run.
983In particular, it attempts to avoid recomputing data unless it needs to. For
984this reason, passes are allowed to declare that they preserve (i.e., they don't
985invalidate) an existing analysis if it's available. For example, a simple
Reid Spencer1bc19342004-12-11 05:12:57 +0000986constant folding pass would not modify the CFG, so it can't possibly affect the
Chris Lattner89256272004-03-17 21:09:55 +0000987results of dominator analysis. By default, all passes are assumed to invalidate
988all others.
989</p>
990
991<p>
992The <tt>AnalysisUsage</tt> class provides several methods which are useful in
993certain circumstances that are related to <tt>addPreserved</tt>. In particular,
994the <tt>setPreservesAll</tt> method can be called to indicate that the pass does
995not modify the LLVM program at all (which is true for analyses), and the
996<tt>setPreservesCFG</tt> method can be used by transformations that change
997instructions in the program but do not modify the CFG or terminator instructions
998(note that this property is implicitly set for <a
999href="#BasicBlockPass">BasicBlockPass</a>'s).
1000</p>
1001
1002<p>
1003<tt>addPreserved</tt> is particularly useful for transformations like
1004<tt>BreakCriticalEdges</tt>. This pass knows how to update a small set of loop
1005and dominator related analyses if they exist, so it can preserve them, despite
1006the fact that it hacks on the CFG.
1007</p>
1008</div>
1009
1010<!-- _______________________________________________________________________ -->
1011<div class="doc_subsubsection">
1012 <a name="AU::examples">Example implementations of <tt>getAnalysisUsage</tt></a>
1013</div>
1014
1015<div class="doc_text">
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001016
Jim Laskey5fa8fff2006-08-04 18:10:12 +00001017<div class="doc_code"><pre>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001018 <i>// This is an example implementation from an analysis, which does not modify
1019 // the program at all, yet has a prerequisite.</i>
Reid Spencer05fe4b02006-03-14 05:39:39 +00001020 <b>void</b> <a href="http://llvm.org/doxygen/classllvm_1_1PostDominanceFrontier.html">PostDominanceFrontier</a>::getAnalysisUsage(AnalysisUsage &amp;AU) <b>const</b> {
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001021 AU.setPreservesAll();
Reid Spencer05fe4b02006-03-14 05:39:39 +00001022 AU.addRequired&lt;<a href="http://llvm.org/doxygen/classllvm_1_1PostDominatorTree.html">PostDominatorTree</a>&gt;();
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001023 }
Jim Laskey5fa8fff2006-08-04 18:10:12 +00001024</pre></div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001025
Misha Brukmanc5402402004-01-15 18:34:11 +00001026<p>and:</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001027
Jim Laskey5fa8fff2006-08-04 18:10:12 +00001028<div class="doc_code"><pre>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001029 <i>// This example modifies the program, but does not modify the CFG</i>
Reid Spencer05fe4b02006-03-14 05:39:39 +00001030 <b>void</b> <a href="http://llvm.org/doxygen/structLICM.html">LICM</a>::getAnalysisUsage(AnalysisUsage &amp;AU) <b>const</b> {
Chris Lattner8291e042002-10-21 19:57:59 +00001031 AU.setPreservesCFG();
Reid Spencer05fe4b02006-03-14 05:39:39 +00001032 AU.addRequired&lt;<a href="http://llvm.org/doxygen/classllvm_1_1LoopInfo.html">LoopInfo</a>&gt;();
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001033 }
Jim Laskey5fa8fff2006-08-04 18:10:12 +00001034</pre></div>
Misha Brukmanc5402402004-01-15 18:34:11 +00001035
1036</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001037
1038<!-- _______________________________________________________________________ -->
Misha Brukmanc5402402004-01-15 18:34:11 +00001039<div class="doc_subsubsection">
Chris Lattner89256272004-03-17 21:09:55 +00001040 <a name="getAnalysis">The <tt>getAnalysis&lt;&gt;</tt> and <tt>getAnalysisToUpdate&lt;&gt;</tt> methods</a>
Misha Brukmanc5402402004-01-15 18:34:11 +00001041</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001042
Misha Brukmanc5402402004-01-15 18:34:11 +00001043<div class="doc_text">
1044
Chris Lattner89256272004-03-17 21:09:55 +00001045<p>The <tt>Pass::getAnalysis&lt;&gt;</tt> method is automatically inherited by
1046your class, providing you with access to the passes that you declared that you
1047required with the <a href="#getAnalysisUsage"><tt>getAnalysisUsage</tt></a>
1048method. It takes a single template argument that specifies which pass class you
1049want, and returns a reference to that pass. For example:</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001050
Jim Laskey5fa8fff2006-08-04 18:10:12 +00001051<div class="doc_code"><pre>
Chris Lattnera5776302004-03-17 21:33:32 +00001052 bool LICM::runOnFunction(Function &amp;F) {
Chris Lattner89256272004-03-17 21:09:55 +00001053 LoopInfo &amp;LI = getAnalysis&lt;LoopInfo&gt;();
1054 ...
1055 }
Jim Laskey5fa8fff2006-08-04 18:10:12 +00001056</pre></div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001057
Misha Brukmanc5402402004-01-15 18:34:11 +00001058<p>This method call returns a reference to the pass desired. You may get a
1059runtime assertion failure if you attempt to get an analysis that you did not
1060declare as required in your <a
1061href="#getAnalysisUsage"><tt>getAnalysisUsage</tt></a> implementation. This
1062method can be called by your <tt>run*</tt> method implementation, or by any
1063other local method invoked by your <tt>run*</tt> method.</p>
1064
Chris Lattner89256272004-03-17 21:09:55 +00001065<p>
1066If your pass is capable of updating analyses if they exist (e.g.,
1067<tt>BreakCriticalEdges</tt>, as described above), you can use the
1068<tt>getAnalysisToUpdate</tt> method, which returns a pointer to the analysis if
1069it is active. For example:</p>
1070
Jim Laskey5fa8fff2006-08-04 18:10:12 +00001071<div class="doc_code"><pre>
Chris Lattner89256272004-03-17 21:09:55 +00001072 ...
1073 if (DominatorSet *DS = getAnalysisToUpdate&lt;DominatorSet&gt;()) {
1074 <i>// A DominatorSet is active. This code will update it.</i>
1075 }
1076 ...
Jim Laskey5fa8fff2006-08-04 18:10:12 +00001077</pre></div>
Chris Lattner89256272004-03-17 21:09:55 +00001078
Misha Brukmanc5402402004-01-15 18:34:11 +00001079</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001080
Chris Lattner79910702002-08-22 19:21:04 +00001081<!-- *********************************************************************** -->
Misha Brukmanc5402402004-01-15 18:34:11 +00001082<div class="doc_section">
1083 <a name="analysisgroup">Implementing Analysis Groups</a>
1084</div>
Chris Lattner79910702002-08-22 19:21:04 +00001085<!-- *********************************************************************** -->
1086
Misha Brukmanc5402402004-01-15 18:34:11 +00001087<div class="doc_text">
1088
1089<p>Now that we understand the basics of how passes are defined, how the are
1090used, and how they are required from other passes, it's time to get a little bit
Chris Lattner79910702002-08-22 19:21:04 +00001091fancier. All of the pass relationships that we have seen so far are very
1092simple: one pass depends on one other specific pass to be run before it can run.
1093For many applications, this is great, for others, more flexibility is
Misha Brukmanc5402402004-01-15 18:34:11 +00001094required.</p>
Chris Lattner79910702002-08-22 19:21:04 +00001095
Misha Brukmanc5402402004-01-15 18:34:11 +00001096<p>In particular, some analyses are defined such that there is a single simple
Chris Lattner79910702002-08-22 19:21:04 +00001097interface to the analysis results, but multiple ways of calculating them.
1098Consider alias analysis for example. The most trivial alias analysis returns
1099"may alias" for any alias query. The most sophisticated analysis a
1100flow-sensitive, context-sensitive interprocedural analysis that can take a
1101significant amount of time to execute (and obviously, there is a lot of room
1102between these two extremes for other implementations). To cleanly support
1103situations like this, the LLVM Pass Infrastructure supports the notion of
Misha Brukmanc5402402004-01-15 18:34:11 +00001104Analysis Groups.</p>
1105
1106</div>
Chris Lattner79910702002-08-22 19:21:04 +00001107
1108<!-- _______________________________________________________________________ -->
Chris Lattner89256272004-03-17 21:09:55 +00001109<div class="doc_subsubsection">
Misha Brukmanc5402402004-01-15 18:34:11 +00001110 <a name="agconcepts">Analysis Group Concepts</a>
1111</div>
Chris Lattner79910702002-08-22 19:21:04 +00001112
Misha Brukmanc5402402004-01-15 18:34:11 +00001113<div class="doc_text">
1114
1115<p>An Analysis Group is a single simple interface that may be implemented by
Chris Lattner79910702002-08-22 19:21:04 +00001116multiple different passes. Analysis Groups can be given human readable names
1117just like passes, but unlike passes, they need not derive from the <tt>Pass</tt>
1118class. An analysis group may have one or more implementations, one of which is
Misha Brukmanc5402402004-01-15 18:34:11 +00001119the "default" implementation.</p>
Chris Lattner79910702002-08-22 19:21:04 +00001120
Misha Brukmanc5402402004-01-15 18:34:11 +00001121<p>Analysis groups are used by client passes just like other passes are: the
Chris Lattner79910702002-08-22 19:21:04 +00001122<tt>AnalysisUsage::addRequired()</tt> and <tt>Pass::getAnalysis()</tt> methods.
1123In order to resolve this requirement, the <a href="#passmanager">PassManager</a>
1124scans the available passes to see if any implementations of the analysis group
1125are available. If none is available, the default implementation is created for
1126the pass to use. All standard rules for <A href="#interaction">interaction
Misha Brukmanc5402402004-01-15 18:34:11 +00001127between passes</a> still apply.</p>
Chris Lattner79910702002-08-22 19:21:04 +00001128
Misha Brukmanc5402402004-01-15 18:34:11 +00001129<p>Although <a href="#registration">Pass Registration</a> is optional for normal
Chris Lattner79910702002-08-22 19:21:04 +00001130passes, all analysis group implementations must be registered, and must use the
1131<A href="#registerag"><tt>RegisterAnalysisGroup</tt></a> template to join the
1132implementation pool. Also, a default implementation of the interface
1133<b>must</b> be registered with <A
Misha Brukmanc5402402004-01-15 18:34:11 +00001134href="#registerag"><tt>RegisterAnalysisGroup</tt></a>.</p>
Chris Lattner79910702002-08-22 19:21:04 +00001135
Misha Brukmanc5402402004-01-15 18:34:11 +00001136<p>As a concrete example of an Analysis Group in action, consider the <a
Reid Spencer05fe4b02006-03-14 05:39:39 +00001137href="http://llvm.org/doxygen/classllvm_1_1AliasAnalysis.html">AliasAnalysis</a>
Chris Lattner79910702002-08-22 19:21:04 +00001138analysis group. The default implementation of the alias analysis interface (the
1139<tt><a
Reid Spencer05fe4b02006-03-14 05:39:39 +00001140href="http://llvm.org/doxygen/structBasicAliasAnalysis.html">basicaa</a></tt>
Chris Lattner79910702002-08-22 19:21:04 +00001141pass) just does a few simple checks that don't require significant analysis to
1142compute (such as: two different globals can never alias each other, etc).
1143Passes that use the <tt><a
Reid Spencer05fe4b02006-03-14 05:39:39 +00001144href="http://llvm.org/doxygen/classllvm_1_1AliasAnalysis.html">AliasAnalysis</a></tt>
Chris Lattner79910702002-08-22 19:21:04 +00001145interface (for example the <tt><a
Reid Spencer05fe4b02006-03-14 05:39:39 +00001146href="http://llvm.org/doxygen/structGCSE.html">gcse</a></tt> pass), do
Misha Brukmanc5402402004-01-15 18:34:11 +00001147not care which implementation of alias analysis is actually provided, they just
1148use the designated interface.</p>
Chris Lattner79910702002-08-22 19:21:04 +00001149
Misha Brukmanc5402402004-01-15 18:34:11 +00001150<p>From the user's perspective, commands work just like normal. Issuing the
Chris Lattner79910702002-08-22 19:21:04 +00001151command '<tt>opt -gcse ...</tt>' will cause the <tt>basicaa</tt> class to be
1152instantiated and added to the pass sequence. Issuing the command '<tt>opt
1153-somefancyaa -gcse ...</tt>' will cause the <tt>gcse</tt> pass to use the
1154<tt>somefancyaa</tt> alias analysis (which doesn't actually exist, it's just a
Misha Brukmanc5402402004-01-15 18:34:11 +00001155hypothetical example) instead.</p>
Chris Lattner79910702002-08-22 19:21:04 +00001156
Misha Brukmanc5402402004-01-15 18:34:11 +00001157</div>
Chris Lattner79910702002-08-22 19:21:04 +00001158
1159<!-- _______________________________________________________________________ -->
Chris Lattner89256272004-03-17 21:09:55 +00001160<div class="doc_subsubsection">
Misha Brukmanc5402402004-01-15 18:34:11 +00001161 <a name="registerag">Using <tt>RegisterAnalysisGroup</tt></a>
1162</div>
Chris Lattner79910702002-08-22 19:21:04 +00001163
Misha Brukmanc5402402004-01-15 18:34:11 +00001164<div class="doc_text">
1165
1166<p>The <tt>RegisterAnalysisGroup</tt> template is used to register the analysis
Chris Lattner79910702002-08-22 19:21:04 +00001167group itself as well as add pass implementations to the analysis group. First,
1168an analysis should be registered, with a human readable name provided for it.
1169Unlike registration of passes, there is no command line argument to be specified
Misha Brukmanc5402402004-01-15 18:34:11 +00001170for the Analysis Group Interface itself, because it is "abstract":</p>
Chris Lattner79910702002-08-22 19:21:04 +00001171
Jim Laskey5fa8fff2006-08-04 18:10:12 +00001172<div class="doc_code"><pre>
Reid Spencer05fe4b02006-03-14 05:39:39 +00001173 <b>static</b> RegisterAnalysisGroup&lt;<a href="http://llvm.org/doxygen/classllvm_1_1AliasAnalysis.html">AliasAnalysis</a>&gt; A("<i>Alias Analysis</i>");
Jim Laskey5fa8fff2006-08-04 18:10:12 +00001174</pre></div>
Chris Lattner79910702002-08-22 19:21:04 +00001175
Misha Brukmanc5402402004-01-15 18:34:11 +00001176<p>Once the analysis is registered, passes can declare that they are valid
1177implementations of the interface by using the following code:</p>
Chris Lattner79910702002-08-22 19:21:04 +00001178
Jim Laskey5fa8fff2006-08-04 18:10:12 +00001179<div class="doc_code"><pre>
Chris Lattner79910702002-08-22 19:21:04 +00001180<b>namespace</b> {
1181 //<i> Analysis Group implementations <b>must</b> be registered normally...</i>
1182 RegisterOpt&lt;FancyAA&gt;
1183 B("<i>somefancyaa</i>", "<i>A more complex alias analysis implementation</i>");
1184
1185 //<i> Declare that we implement the AliasAnalysis interface</i>
Reid Spencer05fe4b02006-03-14 05:39:39 +00001186 RegisterAnalysisGroup&lt;<a href="http://llvm.org/doxygen/classllvm_1_1AliasAnalysis.html">AliasAnalysis</a>, FancyAA&gt; C;
Chris Lattner79910702002-08-22 19:21:04 +00001187}
Jim Laskey5fa8fff2006-08-04 18:10:12 +00001188</pre></div>
Chris Lattner79910702002-08-22 19:21:04 +00001189
Misha Brukmanc5402402004-01-15 18:34:11 +00001190<p>This just shows a class <tt>FancyAA</tt> that is registered normally, then
1191uses the <tt>RegisterAnalysisGroup</tt> template to "join" the <tt><a
Reid Spencer05fe4b02006-03-14 05:39:39 +00001192href="http://llvm.org/doxygen/classllvm_1_1AliasAnalysis.html">AliasAnalysis</a></tt>
Chris Lattner79910702002-08-22 19:21:04 +00001193analysis group. Every implementation of an analysis group should join using
1194this template. A single pass may join multiple different analysis groups with
Misha Brukmanc5402402004-01-15 18:34:11 +00001195no problem.</p>
Chris Lattner79910702002-08-22 19:21:04 +00001196
Jim Laskey5fa8fff2006-08-04 18:10:12 +00001197<div class="doc_code"><pre>
Chris Lattner79910702002-08-22 19:21:04 +00001198<b>namespace</b> {
1199 //<i> Analysis Group implementations <b>must</b> be registered normally...</i>
Reid Spencer05fe4b02006-03-14 05:39:39 +00001200 RegisterOpt&lt;<a href="http://llvm.org/doxygen/structBasicAliasAnalysis.html">BasicAliasAnalysis</a>&gt;
Chris Lattner79910702002-08-22 19:21:04 +00001201 D("<i>basicaa</i>", "<i>Basic Alias Analysis (default AA impl)</i>");
1202
1203 //<i> Declare that we implement the AliasAnalysis interface</i>
Reid Spencer05fe4b02006-03-14 05:39:39 +00001204 RegisterAnalysisGroup&lt;<a href="http://llvm.org/doxygen/classllvm_1_1AliasAnalysis.html">AliasAnalysis</a>, <a href="http://llvm.org/doxygen/structBasicAliasAnalysis.html">BasicAliasAnalysis</a>, <b>true</b>&gt; E;
Chris Lattner79910702002-08-22 19:21:04 +00001205}
Jim Laskey5fa8fff2006-08-04 18:10:12 +00001206</pre></div>
Chris Lattner79910702002-08-22 19:21:04 +00001207
Misha Brukmanc5402402004-01-15 18:34:11 +00001208<p>Here we show how the default implementation is specified (using the extra
Chris Lattner79910702002-08-22 19:21:04 +00001209argument to the <tt>RegisterAnalysisGroup</tt> template). There must be exactly
1210one default implementation available at all times for an Analysis Group to be
1211used. Here we declare that the <tt><a
Reid Spencer05fe4b02006-03-14 05:39:39 +00001212href="http://llvm.org/doxygen/structBasicAliasAnalysis.html">BasicAliasAnalysis</a></tt>
Misha Brukmanc5402402004-01-15 18:34:11 +00001213pass is the default implementation for the interface.</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001214
Misha Brukmanc5402402004-01-15 18:34:11 +00001215</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001216
1217<!-- *********************************************************************** -->
Misha Brukmanc5402402004-01-15 18:34:11 +00001218<div class="doc_section">
Tanya Lattnerd5383652004-11-19 01:25:14 +00001219 <a name="passStatistics">Pass Statistics</a>
1220</div>
1221<!-- *********************************************************************** -->
1222
1223<div class="doc_text">
Tanya Lattner05f8d5f2004-11-19 01:26:37 +00001224<p>The <a
Reid Spencer05fe4b02006-03-14 05:39:39 +00001225href="http://llvm.org/doxygen/Statistic_8h-source.html"><tt>Statistic</tt></a>
John Criswell0b1010e2005-11-28 23:25:41 +00001226class is designed to be an easy way to expose various success
Tanya Lattnerd5383652004-11-19 01:25:14 +00001227metrics from passes. These statistics are printed at the end of a
1228run, when the -stats command line option is enabled on the command
Tanya Lattner05f8d5f2004-11-19 01:26:37 +00001229line. See the <a href="http://llvm.org/docs/ProgrammersManual.html#Statistic">Statistics section</a> in the Programmer's Manual for details.
Tanya Lattnerd5383652004-11-19 01:25:14 +00001230
1231</div>
1232
1233
1234<!-- *********************************************************************** -->
1235<div class="doc_section">
Misha Brukmanc5402402004-01-15 18:34:11 +00001236 <a name="passmanager">What PassManager does</a>
1237</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001238<!-- *********************************************************************** -->
1239
Misha Brukmanc5402402004-01-15 18:34:11 +00001240<div class="doc_text">
1241
1242<p>The <a
Reid Spencer05fe4b02006-03-14 05:39:39 +00001243href="http://llvm.org/doxygen/PassManager_8h-source.html"><tt>PassManager</tt></a>
Misha Brukmanc5402402004-01-15 18:34:11 +00001244<a
Reid Spencer05fe4b02006-03-14 05:39:39 +00001245href="http://llvm.org/doxygen/classllvm_1_1PassManager.html">class</a>
Misha Brukmanc5402402004-01-15 18:34:11 +00001246takes a list of passes, ensures their <a href="#interaction">prerequisites</a>
1247are set up correctly, and then schedules passes to run efficiently. All of the
1248LLVM tools that run passes use the <tt>PassManager</tt> for execution of these
1249passes.</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001250
Misha Brukmanc5402402004-01-15 18:34:11 +00001251<p>The <tt>PassManager</tt> does two main things to try to reduce the execution
1252time of a series of passes:</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001253
1254<ol>
1255<li><b>Share analysis results</b> - The PassManager attempts to avoid
1256recomputing analysis results as much as possible. This means keeping track of
1257which analyses are available already, which analyses get invalidated, and which
1258analyses are needed to be run for a pass. An important part of work is that the
1259<tt>PassManager</tt> tracks the exact lifetime of all analysis results, allowing
1260it to <a href="#releaseMemory">free memory</a> allocated to holding analysis
Misha Brukmanc5402402004-01-15 18:34:11 +00001261results as soon as they are no longer needed.</li>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001262
1263<li><b>Pipeline the execution of passes on the program</b> - The
1264<tt>PassManager</tt> attempts to get better cache and memory usage behavior out
1265of a series of passes by pipelining the passes together. This means that, given
1266a series of consequtive <a href="#FunctionPass"><tt>FunctionPass</tt></a>'s, it
1267will execute all of the <a href="#FunctionPass"><tt>FunctionPass</tt></a>'s on
1268the first function, then all of the <a
Misha Brukmanc5402402004-01-15 18:34:11 +00001269href="#FunctionPass"><tt>FunctionPass</tt></a>es on the second function,
1270etc... until the entire program has been run through the passes.
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001271
Misha Brukmanc5402402004-01-15 18:34:11 +00001272<p>This improves the cache behavior of the compiler, because it is only touching
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001273the LLVM program representation for a single function at a time, instead of
1274traversing the entire program. It reduces the memory consumption of compiler,
1275because, for example, only one <a
Reid Spencer05fe4b02006-03-14 05:39:39 +00001276href="http://llvm.org/doxygen/classllvm_1_1DominatorSet.html"><tt>DominatorSet</tt></a>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001277needs to be calculated at a time. This also makes it possible some <a
Misha Brukmanc5402402004-01-15 18:34:11 +00001278href="#SMP">interesting enhancements</a> in the future.</p></li>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001279
Misha Brukmanc5402402004-01-15 18:34:11 +00001280</ol>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001281
Misha Brukmanc5402402004-01-15 18:34:11 +00001282<p>The effectiveness of the <tt>PassManager</tt> is influenced directly by how
1283much information it has about the behaviors of the passes it is scheduling. For
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001284example, the "preserved" set is intentionally conservative in the face of an
1285unimplemented <a href="#getAnalysisUsage"><tt>getAnalysisUsage</tt></a> method.
1286Not implementing when it should be implemented will have the effect of not
Misha Brukmanc5402402004-01-15 18:34:11 +00001287allowing any analysis results to live across the execution of your pass.</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001288
Misha Brukmanc5402402004-01-15 18:34:11 +00001289<p>The <tt>PassManager</tt> class exposes a <tt>--debug-pass</tt> command line
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001290options that is useful for debugging pass execution, seeing how things work, and
1291diagnosing when you should be preserving more analyses than you currently are
1292(To get information about all of the variants of the <tt>--debug-pass</tt>
Misha Brukmanc5402402004-01-15 18:34:11 +00001293option, just type '<tt>opt --help-hidden</tt>').</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001294
Misha Brukmanc5402402004-01-15 18:34:11 +00001295<p>By using the <tt>--debug-pass=Structure</tt> option, for example, we can see
1296how our <a href="#basiccode">Hello World</a> pass interacts with other passes.
1297Lets try it out with the <tt>gcse</tt> and <tt>licm</tt> passes:</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001298
Jim Laskey5fa8fff2006-08-04 18:10:12 +00001299<div class="doc_code"><pre>
Reid Spencer7fa6d522005-01-11 05:16:23 +00001300$ opt -load ../../../Debug/lib/Hello.so -gcse -licm --debug-pass=Structure &lt; hello.bc &gt; /dev/null
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001301Module Pass Manager
1302 Function Pass Manager
1303 Dominator Set Construction
1304 Immediate Dominators Construction
1305 Global Common Subexpression Elimination
1306-- Immediate Dominators Construction
1307-- Global Common Subexpression Elimination
1308 Natural Loop Construction
1309 Loop Invariant Code Motion
1310-- Natural Loop Construction
1311-- Loop Invariant Code Motion
1312 Module Verifier
1313-- Dominator Set Construction
1314-- Module Verifier
1315 Bytecode Writer
1316--Bytecode Writer
Jim Laskey5fa8fff2006-08-04 18:10:12 +00001317</pre></div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001318
Misha Brukmanc5402402004-01-15 18:34:11 +00001319<p>This output shows us when passes are constructed and when the analysis
1320results are known to be dead (prefixed with '<tt>--</tt>'). Here we see that
1321GCSE uses dominator and immediate dominator information to do its job. The LICM
1322pass uses natural loop information, which uses dominator sets, but not immediate
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001323dominators. Because immediate dominators are no longer useful after the GCSE
1324pass, it is immediately destroyed. The dominator sets are then reused to
Misha Brukmanc5402402004-01-15 18:34:11 +00001325compute natural loop information, which is then used by the LICM pass.</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001326
Misha Brukmanc5402402004-01-15 18:34:11 +00001327<p>After the LICM pass, the module verifier runs (which is automatically added
1328by the '<tt>opt</tt>' tool), which uses the dominator set to check that the
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001329resultant LLVM code is well formed. After it finishes, the dominator set
1330information is destroyed, after being computed once, and shared by three
Misha Brukmanc5402402004-01-15 18:34:11 +00001331passes.</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001332
Misha Brukmanc5402402004-01-15 18:34:11 +00001333<p>Lets see how this changes when we run the <a href="#basiccode">Hello
1334World</a> pass in between the two passes:</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001335
Jim Laskey5fa8fff2006-08-04 18:10:12 +00001336<div class="doc_code"><pre>
Reid Spencer7fa6d522005-01-11 05:16:23 +00001337$ opt -load ../../../Debug/lib/Hello.so -gcse -hello -licm --debug-pass=Structure &lt; hello.bc &gt; /dev/null
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001338Module Pass Manager
1339 Function Pass Manager
1340 Dominator Set Construction
1341 Immediate Dominators Construction
1342 Global Common Subexpression Elimination
1343<b>-- Dominator Set Construction</b>
1344-- Immediate Dominators Construction
1345-- Global Common Subexpression Elimination
1346<b> Hello World Pass
1347-- Hello World Pass
1348 Dominator Set Construction</b>
1349 Natural Loop Construction
1350 Loop Invariant Code Motion
1351-- Natural Loop Construction
1352-- Loop Invariant Code Motion
1353 Module Verifier
1354-- Dominator Set Construction
1355-- Module Verifier
1356 Bytecode Writer
1357--Bytecode Writer
1358Hello: __main
1359Hello: puts
1360Hello: main
Jim Laskey5fa8fff2006-08-04 18:10:12 +00001361</pre></div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001362
Misha Brukmanc5402402004-01-15 18:34:11 +00001363<p>Here we see that the <a href="#basiccode">Hello World</a> pass has killed the
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001364Dominator Set pass, even though it doesn't modify the code at all! To fix this,
1365we need to add the following <a
Misha Brukmanc5402402004-01-15 18:34:11 +00001366href="#getAnalysisUsage"><tt>getAnalysisUsage</tt></a> method to our pass:</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001367
Jim Laskey5fa8fff2006-08-04 18:10:12 +00001368<div class="doc_code"><pre>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001369 <i>// We don't modify the program, so we preserve all analyses</i>
1370 <b>virtual void</b> getAnalysisUsage(AnalysisUsage &amp;AU) <b>const</b> {
1371 AU.setPreservesAll();
1372 }
Jim Laskey5fa8fff2006-08-04 18:10:12 +00001373</pre></div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001374
Misha Brukmanc5402402004-01-15 18:34:11 +00001375<p>Now when we run our pass, we get this output:</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001376
Jim Laskey5fa8fff2006-08-04 18:10:12 +00001377<div class="doc_code"><pre>
Reid Spencer7fa6d522005-01-11 05:16:23 +00001378$ opt -load ../../../Debug/lib/Hello.so -gcse -hello -licm --debug-pass=Structure &lt; hello.bc &gt; /dev/null
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001379Pass Arguments: -gcse -hello -licm
1380Module Pass Manager
1381 Function Pass Manager
1382 Dominator Set Construction
1383 Immediate Dominators Construction
1384 Global Common Subexpression Elimination
1385-- Immediate Dominators Construction
1386-- Global Common Subexpression Elimination
1387 Hello World Pass
1388-- Hello World Pass
1389 Natural Loop Construction
1390 Loop Invariant Code Motion
1391-- Loop Invariant Code Motion
1392-- Natural Loop Construction
1393 Module Verifier
1394-- Dominator Set Construction
1395-- Module Verifier
1396 Bytecode Writer
1397--Bytecode Writer
1398Hello: __main
1399Hello: puts
1400Hello: main
Jim Laskey5fa8fff2006-08-04 18:10:12 +00001401</pre></div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001402
Misha Brukmanc5402402004-01-15 18:34:11 +00001403<p>Which shows that we don't accidentally invalidate dominator information
1404anymore, and therefore do not have to compute it twice.</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001405
Misha Brukmanc5402402004-01-15 18:34:11 +00001406</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001407
1408<!-- _______________________________________________________________________ -->
Misha Brukmanc5402402004-01-15 18:34:11 +00001409<div class="doc_subsubsection">
1410 <a name="releaseMemory">The <tt>releaseMemory</tt> method</a>
1411</div>
1412
1413<div class="doc_text">
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001414
Jim Laskey5fa8fff2006-08-04 18:10:12 +00001415<div class="doc_code"><pre>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001416 <b>virtual void</b> releaseMemory();
Jim Laskey5fa8fff2006-08-04 18:10:12 +00001417</pre></div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001418
Misha Brukmanc5402402004-01-15 18:34:11 +00001419<p>The <tt>PassManager</tt> automatically determines when to compute analysis
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001420results, and how long to keep them around for. Because the lifetime of the pass
1421object itself is effectively the entire duration of the compilation process, we
1422need some way to free analysis results when they are no longer useful. The
Misha Brukmanc5402402004-01-15 18:34:11 +00001423<tt>releaseMemory</tt> virtual method is the way to do this.</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001424
Misha Brukmanc5402402004-01-15 18:34:11 +00001425<p>If you are writing an analysis or any other pass that retains a significant
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001426amount of state (for use by another pass which "requires" your pass and uses the
1427<a href="#getAnalysis">getAnalysis</a> method) you should implement
1428<tt>releaseMEmory</tt> to, well, release the memory allocated to maintain this
1429internal state. This method is called after the <tt>run*</tt> method for the
Misha Brukmanc5402402004-01-15 18:34:11 +00001430class, before the next call of <tt>run*</tt> in your pass.</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001431
Misha Brukmanc5402402004-01-15 18:34:11 +00001432</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001433
1434<!-- *********************************************************************** -->
Misha Brukmanc5402402004-01-15 18:34:11 +00001435<div class="doc_section">
Jim Laskey5fa8fff2006-08-04 18:10:12 +00001436 <a name="registering">Registering dynamically loaded passes</a>
1437</div>
1438<!-- *********************************************************************** -->
1439
1440<div class="doc_text">
1441
1442<p><i>Size matters</i> when constructing production quality tools using llvm,
1443both for the purposes of distribution, and for regulating the resident code size
1444when running on the target system. Therefore, it becomes desirable to
1445selectively use some passes, while omitting others and maintain the flexibility
1446to change configurations later on. You want to be able to do all this, and,
1447provide feedback to the user. This is where pass registration comes into
1448play.</p>
1449
1450<p>The fundamental mechanisms for pass registration are the
1451<tt>MachinePassRegistry</tt> class and subclasses of
1452<tt>MachinePassRegistryNode</tt>.</p>
1453
1454<p>An instance of <tt>MachinePassRegistry</tt> is used to maintain a list of
1455<tt>MachinePassRegistryNode</tt> objects. This instance maintains the list and
1456communicates additions and deletions to the command line interface.</p>
1457
1458<p>An instance of <tt>MachinePassRegistryNode</tt> subclass is used to maintain
1459information provided about a particular pass. This information includes the
1460command line name, the command help string and the address of the function used
1461to create an instance of the pass. A global static constructor of one of these
1462instances <i>registers</i> with a corresponding <tt>MachinePassRegistry</tt>,
1463the static destructor <i>unregisters</i>. Thus a pass that is statically linked
1464in the tool will be registered at start up. A dynamically loaded pass will
1465register on load and unregister at unload.</p>
1466
1467</div>
1468
1469<!-- _______________________________________________________________________ -->
1470<div class="doc_subsection">
1471 <a name="registering_existing">Using existing registries</a>
1472</div>
1473
1474<div class="doc_text">
1475
1476<p>There are predefined registries to track instruction scheduling
1477(<tt>RegisterScheduler</tt>) and register allocation (<tt>RegisterRegAlloc</tt>)
1478machine passes. Here we will describe how to <i>register</i> a register
1479allocator machine pass.</p>
1480
1481<p>Implement your register allocator machine pass. In your register allocator
1482.cpp file add the following include;</p>
1483
1484<div class="doc_code"><pre>
1485 #include ""llvm/CodeGen/RegAllocRegistry.h""
1486</pre></div>
1487
1488<p>Also in your register allocator .cpp file, define a creator function in the
1489form; </p>
1490
1491<div class="doc_code"><pre>
1492 FunctionPass *createMyRegisterAllocator() {
1493 return new MyRegisterAllocator();
1494 }
1495</pre></div>
1496
1497<p>Note that the signature of this function should match the type of
1498<tt>RegisterRegAlloc::FunctionPassCtor</tt>. In the same file add the
1499"installing" declaration, in the form;</p>
1500
1501<div class="doc_code"><pre>
1502 static RegisterRegAlloc myRegAlloc("myregalloc",
1503 " my register allocator help string",
1504 createMyRegisterAllocator);
1505</pre></div>
1506
1507<p>Note the two spaces prior to the help string produces a tidy result on the
1508--help query.</p>
1509
1510<div class="doc_code"><pre>
1511$ llc --help
1512 ...
1513 -regalloc - Register allocator to use: (default = linearscan)
1514 =linearscan - linear scan register allocator
1515 =local - local register allocator
1516 =simple - simple register allocator
1517 =myregalloc - my register allocator help string
1518 ...
1519</pre></div>
1520
1521<p>And that's it. The user is now free to use <tt>-regalloc=myregalloc</tt> as
1522an option. Registering instruction schedulers is similar except use the
1523<tt>RegisterRegAlloc</tt> class. Note that the
1524<tt>RegisterRegAlloc::FunctionPassCtor</tt> is significantly different from
1525<tt>RegisterRegAlloc::FunctionPassCtor</tt>.</p>
1526
1527<p>To force the load/linking of your register allocator into the llc/lli tools,
1528add your creator function's global declaration to "Passes.h" and add a "pseudo"
1529call line to <tt>llvm/Codegen/LinkAllCodegenComponents.h</tt>.</p>
1530
1531</div>
1532
1533
1534<!-- _______________________________________________________________________ -->
1535<div class="doc_subsection">
1536 <a name="registering_new">Creating new registries</a>
1537</div>
1538
1539<div class="doc_text">
1540
1541<p>The easiest way to get started is to clone one of the existing registries; we
1542recommend <tt>llvm/CodeGen/RegAllocRegistry.h</tt>. The key things to modify
1543are the class name and the <tt>FunctionPassCtor</tt> type.</p>
1544
1545<p>Then you need to declare the registry. Example: if your pass registry is
1546<tt>RegisterMyPasses</tt> then define;</p>
1547
1548<div class="doc_code"><pre>
1549MachinePassRegistry RegisterMyPasses::Registry;
1550</pre></div>
1551
1552<p>And finally, declare the command line option for your passes. Example:</p>
1553
1554<div class="doc_code"><pre>
1555 cl::opt&lt;RegisterMyPasses::FunctionPassCtor, false,
1556 RegisterPassParser&lt;RegisterMyPasses&gt &gt
1557 MyPassOpt("mypass",
1558 cl::init(&amp;createDefaultMyPass),
1559 cl::desc("my pass option help"));
1560</pre></div>
1561
1562<p>Here the command option is "mypass", with createDefaultMyPass as the default
1563creator.</p>
1564
1565</div>
1566
1567<!-- *********************************************************************** -->
1568<div class="doc_section">
Misha Brukmanc5402402004-01-15 18:34:11 +00001569 <a name="debughints">Using GDB with dynamically loaded passes</a>
1570</div>
Chris Lattner480e2ef2002-09-06 02:02:58 +00001571<!-- *********************************************************************** -->
1572
Misha Brukmanc5402402004-01-15 18:34:11 +00001573<div class="doc_text">
1574
1575<p>Unfortunately, using GDB with dynamically loaded passes is not as easy as it
Chris Lattner480e2ef2002-09-06 02:02:58 +00001576should be. First of all, you can't set a breakpoint in a shared object that has
1577not been loaded yet, and second of all there are problems with inlined functions
1578in shared objects. Here are some suggestions to debugging your pass with
Misha Brukmanc5402402004-01-15 18:34:11 +00001579GDB.</p>
Chris Lattner480e2ef2002-09-06 02:02:58 +00001580
Misha Brukmanc5402402004-01-15 18:34:11 +00001581<p>For sake of discussion, I'm going to assume that you are debugging a
Chris Lattner480e2ef2002-09-06 02:02:58 +00001582transformation invoked by <tt>opt</tt>, although nothing described here depends
Misha Brukmanc5402402004-01-15 18:34:11 +00001583on that.</p>
1584
1585</div>
Chris Lattner480e2ef2002-09-06 02:02:58 +00001586
1587<!-- _______________________________________________________________________ -->
Misha Brukmanc5402402004-01-15 18:34:11 +00001588<div class="doc_subsubsection">
1589 <a name="breakpoint">Setting a breakpoint in your pass</a>
1590</div>
Chris Lattner480e2ef2002-09-06 02:02:58 +00001591
Misha Brukmanc5402402004-01-15 18:34:11 +00001592<div class="doc_text">
1593
1594<p>First thing you do is start <tt>gdb</tt> on the <tt>opt</tt> process:</p>
Chris Lattner480e2ef2002-09-06 02:02:58 +00001595
Jim Laskey5fa8fff2006-08-04 18:10:12 +00001596<div class="doc_code"><pre>
Chris Lattner480e2ef2002-09-06 02:02:58 +00001597$ <b>gdb opt</b>
1598GNU gdb 5.0
1599Copyright 2000 Free Software Foundation, Inc.
1600GDB is free software, covered by the GNU General Public License, and you are
1601welcome to change it and/or distribute copies of it under certain conditions.
1602Type "show copying" to see the conditions.
1603There is absolutely no warranty for GDB. Type "show warranty" for details.
1604This GDB was configured as "sparc-sun-solaris2.6"...
1605(gdb)
Jim Laskey5fa8fff2006-08-04 18:10:12 +00001606</pre></div>
Chris Lattner480e2ef2002-09-06 02:02:58 +00001607
Misha Brukmanc5402402004-01-15 18:34:11 +00001608<p>Note that <tt>opt</tt> has a lot of debugging information in it, so it takes
Chris Lattner480e2ef2002-09-06 02:02:58 +00001609time to load. Be patient. Since we cannot set a breakpoint in our pass yet
1610(the shared object isn't loaded until runtime), we must execute the process, and
1611have it stop before it invokes our pass, but after it has loaded the shared
1612object. The most foolproof way of doing this is to set a breakpoint in
1613<tt>PassManager::run</tt> and then run the process with the arguments you
Misha Brukmanc5402402004-01-15 18:34:11 +00001614want:</p>
Chris Lattner480e2ef2002-09-06 02:02:58 +00001615
Jim Laskey5fa8fff2006-08-04 18:10:12 +00001616<div class="doc_code"><pre>
Chris Lattner480e2ef2002-09-06 02:02:58 +00001617(gdb) <b>break PassManager::run</b>
1618Breakpoint 1 at 0x2413bc: file Pass.cpp, line 70.
Chris Lattner4c376ea2005-04-21 04:52:37 +00001619(gdb) <b>run test.bc -load $(LLVMTOP)/llvm/Debug/lib/[libname].so -[passoption]</b>
1620Starting program: opt test.bc -load $(LLVMTOP)/llvm/Debug/lib/[libname].so -[passoption]
Chris Lattner480e2ef2002-09-06 02:02:58 +00001621Breakpoint 1, PassManager::run (this=0xffbef174, M=@0x70b298) at Pass.cpp:70
162270 bool PassManager::run(Module &amp;M) { return PM-&gt;run(M); }
1623(gdb)
Jim Laskey5fa8fff2006-08-04 18:10:12 +00001624</pre></div>
Chris Lattner480e2ef2002-09-06 02:02:58 +00001625
Misha Brukmanc5402402004-01-15 18:34:11 +00001626<p>Once the <tt>opt</tt> stops in the <tt>PassManager::run</tt> method you are
1627now free to set breakpoints in your pass so that you can trace through execution
1628or do other standard debugging stuff.</p>
Chris Lattner480e2ef2002-09-06 02:02:58 +00001629
Misha Brukmanc5402402004-01-15 18:34:11 +00001630</div>
Chris Lattner480e2ef2002-09-06 02:02:58 +00001631
1632<!-- _______________________________________________________________________ -->
Misha Brukmanc5402402004-01-15 18:34:11 +00001633<div class="doc_subsubsection">
1634 <a name="debugmisc">Miscellaneous Problems</a>
1635</div>
Chris Lattner480e2ef2002-09-06 02:02:58 +00001636
Misha Brukmanc5402402004-01-15 18:34:11 +00001637<div class="doc_text">
1638
1639<p>Once you have the basics down, there are a couple of problems that GDB has,
1640some with solutions, some without.</p>
Chris Lattner480e2ef2002-09-06 02:02:58 +00001641
1642<ul>
1643<li>Inline functions have bogus stack information. In general, GDB does a
1644pretty good job getting stack traces and stepping through inline functions.
1645When a pass is dynamically loaded however, it somehow completely loses this
1646capability. The only solution I know of is to de-inline a function (move it
Misha Brukmanc5402402004-01-15 18:34:11 +00001647from the body of a class to a .cpp file).</li>
Chris Lattner480e2ef2002-09-06 02:02:58 +00001648
1649<li>Restarting the program breaks breakpoints. After following the information
1650above, you have succeeded in getting some breakpoints planted in your pass. Nex
1651thing you know, you restart the program (i.e., you type '<tt>run</tt>' again),
1652and you start getting errors about breakpoints being unsettable. The only way I
1653have found to "fix" this problem is to <tt>delete</tt> the breakpoints that are
1654already set in your pass, run the program, and re-set the breakpoints once
Misha Brukmanc5402402004-01-15 18:34:11 +00001655execution stops in <tt>PassManager::run</tt>.</li>
Chris Lattner480e2ef2002-09-06 02:02:58 +00001656
1657</ul>
1658
Misha Brukmanc5402402004-01-15 18:34:11 +00001659<p>Hopefully these tips will help with common case debugging situations. If
1660you'd like to contribute some tips of your own, just contact <a
1661href="mailto:sabre@nondot.org">Chris</a>.</p>
Chris Lattner480e2ef2002-09-06 02:02:58 +00001662
Misha Brukmanc5402402004-01-15 18:34:11 +00001663</div>
Chris Lattner480e2ef2002-09-06 02:02:58 +00001664
1665<!-- *********************************************************************** -->
Misha Brukmanc5402402004-01-15 18:34:11 +00001666<div class="doc_section">
1667 <a name="future">Future extensions planned</a>
1668</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001669<!-- *********************************************************************** -->
1670
Misha Brukmanc5402402004-01-15 18:34:11 +00001671<div class="doc_text">
1672
1673<p>Although the LLVM Pass Infrastructure is very capable as it stands, and does
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001674some nifty stuff, there are things we'd like to add in the future. Here is
Misha Brukmanc5402402004-01-15 18:34:11 +00001675where we are going:</p>
1676
1677</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001678
1679<!-- _______________________________________________________________________ -->
Chris Lattner89256272004-03-17 21:09:55 +00001680<div class="doc_subsubsection">
Misha Brukmanc5402402004-01-15 18:34:11 +00001681 <a name="SMP">Multithreaded LLVM</a>
1682</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001683
Misha Brukmanc5402402004-01-15 18:34:11 +00001684<div class="doc_text">
1685
1686<p>Multiple CPU machines are becoming more common and compilation can never be
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001687fast enough: obviously we should allow for a multithreaded compiler. Because of
1688the semantics defined for passes above (specifically they cannot maintain state
1689across invocations of their <tt>run*</tt> methods), a nice clean way to
1690implement a multithreaded compiler would be for the <tt>PassManager</tt> class
Misha Brukmanbc0e9982003-07-14 17:20:40 +00001691to create multiple instances of each pass object, and allow the separate
Misha Brukmanc5402402004-01-15 18:34:11 +00001692instances to be hacking on different parts of the program at the same time.</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001693
Misha Brukmanc5402402004-01-15 18:34:11 +00001694<p>This implementation would prevent each of the passes from having to implement
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001695multithreaded constructs, requiring only the LLVM core to have locking in a few
1696places (for global resources). Although this is a simple extension, we simply
1697haven't had time (or multiprocessor machines, thus a reason) to implement this.
Misha Brukmanc5402402004-01-15 18:34:11 +00001698Despite that, we have kept the LLVM passes SMP ready, and you should too.</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001699
Misha Brukmanc5402402004-01-15 18:34:11 +00001700</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001701
1702<!-- _______________________________________________________________________ -->
Chris Lattner89256272004-03-17 21:09:55 +00001703<div class="doc_subsubsection">
Chris Lattnerf6278922004-09-20 04:36:29 +00001704<a name="PassFunctionPass"><tt>ModulePass</tt>es requiring <tt>FunctionPass</tt>es</a>
Misha Brukmanc5402402004-01-15 18:34:11 +00001705</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001706
Misha Brukmanc5402402004-01-15 18:34:11 +00001707<div class="doc_text">
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001708
Chris Lattnerf6278922004-09-20 04:36:29 +00001709<p>Currently it is illegal for a <a href="#ModulePass"><tt>ModulePass</tt></a>
1710to require a <a href="#FunctionPass"><tt>FunctionPass</tt></a>. This is because
1711there is only one instance of the <a
1712href="#FunctionPass"><tt>FunctionPass</tt></a> object ever created, thus nowhere
1713to store information for all of the functions in the program at the same time.
1714Although this has come up a couple of times before, this has always been worked
1715around by factoring one big complicated pass into a global and an
1716interprocedural part, both of which are distinct. In the future, it would be
1717nice to have this though.</p>
Misha Brukmanc5402402004-01-15 18:34:11 +00001718
1719<p>Note that it is no problem for a <a
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001720href="#FunctionPass"><tt>FunctionPass</tt></a> to require the results of a <a
Chris Lattnerf6278922004-09-20 04:36:29 +00001721href="#ModulePass"><tt>ModulePass</tt></a>, only the other way around.</p>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001722
Misha Brukmanc5402402004-01-15 18:34:11 +00001723</div>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001724
1725<!-- *********************************************************************** -->
Misha Brukmanc5402402004-01-15 18:34:11 +00001726<hr>
1727<address>
1728 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
1729 src="http://jigsaw.w3.org/css-validator/images/vcss" alt="Valid CSS!"></a>
1730 <a href="http://validator.w3.org/check/referer"><img
1731 src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" /></a>
Chris Lattnerc6bb8242002-08-08 20:11:18 +00001732
Misha Brukmanc5402402004-01-15 18:34:11 +00001733 <a href="mailto:sabre@nondot.org">Chris Lattner</a><br>
Reid Spencer05fe4b02006-03-14 05:39:39 +00001734 <a href="http://llvm.org">The LLVM Compiler Infrastructure</a><br>
Misha Brukmanc5402402004-01-15 18:34:11 +00001735 Last modified: $Date$
1736</address>
1737
1738</body>
1739</html>