| blob | 136f8fbd55713c6aac76fdad5988697ea3fb9544 |
3 <html>
4 <head>
8 </head>
9 <body>
11 <h1>
12 Writing an LLVM Pass
13 </h1>
15 <ol>
18 <ul>
22 </ul></li>
24 <ul>
27 <ul>
29 </ul></li>
31 <ul>
37 </ul></li>
39 <ul>
45 </ul></li>
47 <ul>
53 </ul></li>
55 <ul>
61 </ul></li>
63 <ul>
67 method</a></li>
70 </ul></li>
72 class</a>
73 <ul>
76 </ul></li>
77 </ul>
79 <ul>
81 </ul></li>
83 <ul>
85 method</a></li>
86 <li><a href="#AU::addRequired">The <tt>AnalysisUsage::addRequired<></tt> and <tt>AnalysisUsage::addRequiredTransitive<></tt> methods</a></li>
91 </ul></li>
93 <ul>
96 </ul></li>
99 <ul>
101 </ul></li>
103 <ul>
106 </ul></li>
108 <ul>
111 </ul></li>
113 <ul>
115 </ul></li>
116 </ol>
121 </div>
123 <!-- *********************************************************************** -->
124 <h2>
126 </h2>
127 <!-- *********************************************************************** -->
129 <div>
131 <p>The LLVM Pass Framework is an important part of the LLVM system, because LLVM
132 passes are where most of the interesting parts of the compiler exist. Passes
133 perform the transformations and optimizations that make up the compiler, they
134 build the analysis results that are used by these transformations, and they are,
135 above all, a structuring technique for compiler code.</p>
139 class, which implement functionality by overriding virtual methods inherited
147 more information about what your pass does, and how it can be combined with
148 other passes. One of the main features of the LLVM Pass Framework is that it
149 schedules passes to run in an efficient way based on the constraints that your
150 pass meets (which are indicated by which class they derive from).</p>
152 <p>We start by showing you how to construct a pass, everything from setting up
153 the code, to compiling, loading, and executing it. After the basics are down,
154 more advanced features are discussed.</p>
156 </div>
158 <!-- *********************************************************************** -->
159 <h2>
161 </h2>
162 <!-- *********************************************************************** -->
164 <div>
167 is designed to simply print out the name of non-external functions that exist in
168 the program being compiled. It does not modify the program at all, it just
169 inspects it. The source code and files for this pass are available in the LLVM
172 <!-- ======================================================================= -->
173 <h3>
175 </h3>
177 <div>
179 <p>First, configure and build LLVM. This needs to be done directly inside the
180 LLVM source tree rather than in a separate objects directory.
181 Next, you need to create a new directory somewhere in the LLVM source
182 base. For this example, we'll assume that you made
184 (Makefile) that will compile the source code for the new pass. To do this,
186 <hr>
189 # Makefile for hello pass
191 # Path to top level of LLVM hierarchy
192 LEVEL = ../../..
194 # Name of the library to build
195 LIBRARYNAME = Hello
197 # Make the shared library become a loadable module so the tools can
198 # dlopen/dlsym on the resulting library.
199 LOADABLE_MODULE = 1
201 # Include the makefile implementation stuff
202 include $(LEVEL)/Makefile.common
203 </pre></div>
206 directory are to be compiled and linked together into a shared object
209 If your operating system uses a suffix other than .so (such as windows or
210 Mac OS/X), the appropriate extension will be used.</p>
212 <p>If you are used CMake to build LLVM, see
215 <p>Now that we have the build scripts set up, we just need to write the code for
216 the pass itself.</p>
218 </div>
220 <!-- ======================================================================= -->
221 <h3>
223 </h3>
225 <div>
227 <p>Now that we have a way to compile our new pass, we just have to write it.
228 Start out with:</p>
233 <b>#include</b> "<a href="http://llvm.org/doxygen/raw__ostream_8h.html">llvm/Support/raw_ostream.h</a>"
234 </pre></div>
238 we are operating on <tt><a
240 and we will be doing some printing.</p>
245 </pre></div>
246 <p>... which is required because the functions from the include files
247 live in the llvm namespace.
248 </p>
254 </pre></div>
256 <p>... which starts out an anonymous namespace. Anonymous namespaces are to C++
257 what the "<tt>static</tt>" keyword is to C (at global scope). It makes the
258 things declared inside of the anonymous namespace only visible to the current
259 file. If you're not familiar with them, consult a decent C++ book for more
260 information.</p>
266 </pre></div><p>
270 The different builtin pass subclasses are described in detail <a
273 time.</p>
276 static char ID;
277 Hello() : FunctionPass(ID) {}
278 </pre></div><p>
280 <p> This declares pass identifier used by LLVM to identify pass. This allows LLVM to
281 avoid using expensive C++ runtime information.</p>
287 }
289 </pre></div>
292 which overloads an abstract virtual method inherited from <a
294 to do our thing, so we just print out our message with the name of each
295 function.</p>
298 char Hello::ID = 0;
299 </pre></div>
301 <p> We initialize pass ID here. LLVM uses ID's address to identify pass so
302 initialization value is not important.</p>
306 false /* Only looks at CFG */,
307 false /* Analysis Pass */);
309 </pre></div>
312 giving it a command line
314 Last two arguments describe its behavior.
315 If a pass walks CFG without modifying it then third argument is set to true.
316 If a pass is an analysis pass, for example dominator tree pass, then true
317 is supplied as fourth argument. </p>
324 <b>#include</b> "<a href="http://llvm.org/doxygen/raw__ostream_8h.html">llvm/Support/raw_ostream.h</a>"
331 static char ID;
332 Hello() : FunctionPass(ID) {}
337 }
338 };
340 char Hello::ID = 0;
342 }
344 </pre></div>
347 command in the local directory and you should get a new file
348 "<tt>Debug+Asserts/lib/Hello.so</tt>" under the top level directory of the LLVM
349 source tree (not in the local directory). Note that everything in this file is
350 contained in an anonymous namespace: this reflects the fact that passes are self
351 contained units that do not need external interfaces (although they can have
352 them) to be useful.</p>
354 </div>
356 <!-- ======================================================================= -->
357 <h3>
359 </h3>
361 <div>
363 <p>Now that you have a brand new shiny shared object file, we can use the
371 through our transformation like this (or course, any bitcode file will
372 work):</p>
376 Hello: __main
377 Hello: puts
378 Hello: main
379 </pre></div>
384 pass</a>). Because the hello pass does not modify the program in any
388 <p>To see what happened to the other string you registered, try running
392 $ opt -load ../../../Debug+Asserts/lib/Hello.so -help
393 OVERVIEW: llvm .bc -> .bc modular optimizer
397 OPTIONS:
398 Optimizations available:
399 ...
400 -funcresolve - Resolve Functions
401 -gcse - Global Common Subexpression Elimination
402 -globaldce - Dead Global Elimination
404 -indvars - Canonicalize Induction Variables
405 -inline - Function Integration/Inlining
406 -instcombine - Combine redundant instructions
407 ...
408 </pre></div>
410 <p>The pass name get added as the information string for your pass, giving some
412 would go ahead and make it do the cool transformations you want. Once you get
413 it all working and tested, it may become useful to find out how fast your pass
416 the execution time of your pass along with the other passes you queue up. For
417 example:</p>
420 $ opt -load ../../../Debug+Asserts/lib/Hello.so -hello -time-passes < hello.bc > /dev/null
421 Hello: __main
422 Hello: puts
423 Hello: main
424 ===============================================================================
425 ... Pass execution timing report ...
426 ===============================================================================
429 ---User Time--- --System Time-- --User+System-- ---Wall Time--- --- Pass Name ---
435 </pre></div>
437 <p>As you can see, our implementation above is pretty fast :). The additional
439 that the LLVM emitted by your pass is still valid and well formed LLVM, which
440 hasn't been broken somehow.</p>
442 <p>Now that you have seen the basics of the mechanics behind passes, we can talk
443 about some more details of how they work and how to use them.</p>
445 </div>
447 </div>
449 <!-- *********************************************************************** -->
450 <h2>
452 </h2>
453 <!-- *********************************************************************** -->
455 <div>
457 <p>One of the first things that you should do when designing a new pass is to
458 decide what class you should subclass for your pass. The <a
461 did not discuss why or when this should occur. Here we talk about the classes
462 available, from the most general to the most specific.</p>
465 specific</b> class possible, while still being able to meet the requirements
466 listed. This gives the LLVM Pass Infrastructure information necessary to
467 optimize how passes are run, so that the resultant compiler isn't unnecessarily
468 slow.</p>
470 <!-- ======================================================================= -->
471 <h3>
473 </h3>
475 <div>
479 class. This pass type is used for passes that do not have to be run, do not
480 change state, and never need to be updated. This is not a normal type of
481 transformation or analysis, but can provide information about the current
482 compiler configuration.</p>
484 <p>Although this pass class is very infrequently used, it is important for
485 providing information about the current target machine being compiled for, and
486 other static information that can affect the various transformations.</p>
491 </div>
493 <!-- ======================================================================= -->
494 <h3>
496 </h3>
498 <div>
502 class is the most general of all superclasses that you can use. Deriving from
504 referring to function bodies in no predictable order, or adding and removing
506 subclasses, no optimization can be done for their execution.</p>
508 <p>A module pass can use function level passes (e.g. dominators) using
509 the getAnalysis interface
511 function to retrieve analysis result for, if the function pass does not require
512 any module or immutable passes. Note that this can only be done for functions for which the
513 analysis ran, e.g. in the case of dominators you should only ask for the
514 DominatorTree for function definitions, not declarations.</p>
518 following signature:</p>
520 <!-- _______________________________________________________________________ -->
521 <h4>
523 </h4>
525 <div>
529 </pre></div>
532 It should return true if the module was modified by the transformation and
533 false otherwise.</p>
535 </div>
537 </div>
539 <!-- ======================================================================= -->
540 <h3>
542 </h3>
544 <div>
548 is used by passes that need to traverse the program bottom-up on the call graph
549 (callees before callers). Deriving from CallGraphSCCPass provides some
550 mechanics for building and traversing the CallGraph, but also allows the system
551 to optimize execution of CallGraphSCCPass's. If your pass meets the
552 requirements outlined below, and doesn't meet the requirements of a <tt><a
561 <ol>
564 than those in the current SCC and the direct callers and direct callees of the
565 SCC.</li>
568 to reflect any changes made to the program.</li>
571 though they may change the contents of an SCC.</li>
574 Module.</li>
578 </ol>
581 because it has to handle SCCs with more than one node in it. All of the virtual
582 methods described below should return true if they modified the program, or
583 false if they didn't.</p>
585 <!-- _______________________________________________________________________ -->
586 <h4>
589 </a>
590 </h4>
592 <div>
596 </pre></div>
601 is designed to do simple initialization type of stuff that does not depend on
603 scheduled to overlap with any other pass executions (thus it should be very
604 fast).</p>
606 </div>
608 <!-- _______________________________________________________________________ -->
609 <h4>
611 </h4>
613 <div>
617 </pre></div>
620 should return true if the module was modified by the transformation, false
621 otherwise.</p>
623 </div>
625 <!-- _______________________________________________________________________ -->
626 <h4>
629 </a>
630 </h4>
632 <div>
636 </pre></div>
639 called when the pass framework has finished calling <a
641 program being compiled.</p>
643 </div>
645 </div>
647 <!-- ======================================================================= -->
648 <h3>
650 </h3>
652 <div>
656 subclasses do have a predictable, local behavior that can be expected by the
658 independent of all of the other functions in the program.
664 <ol>
668 <li>Maintain state across invocations of
670 </ol>
674 may overload three virtual methods to do their work. All of these methods
675 should return true if they modified the program, or false if they didn't.</p>
677 <!-- _______________________________________________________________________ -->
678 <h4>
681 </a>
682 </h4>
684 <div>
688 </pre></div>
693 is designed to do simple initialization type of stuff that does not depend on
695 scheduled to overlap with any other pass executions (thus it should be very
696 fast).</p>
703 free functions that it needs, adding prototypes to the module if necessary.</p>
705 </div>
707 <!-- _______________________________________________________________________ -->
708 <h4>
710 </h4>
712 <div>
716 </pre></div><p>
719 the transformation or analysis work of your pass. As usual, a true value should
720 be returned if the function is modified.</p>
722 </div>
724 <!-- _______________________________________________________________________ -->
725 <h4>
728 </a>
729 </h4>
731 <div>
735 </pre></div>
738 called when the pass framework has finished calling <a
740 program being compiled.</p>
742 </div>
744 </div>
746 <!-- ======================================================================= -->
747 <h3>
749 </h3>
751 <div>
755 loop nest order such that outer most loop is processed last. </p>
760 do their work. All these methods should return true if they modified the
761 program, or false if they didn't. </p>
763 <!-- _______________________________________________________________________ -->
764 <h4>
767 </a>
768 </h4>
770 <div>
774 </pre></div>
777 type of stuff that does not depend on the functions being processed. The
779 other pass executions (thus it should be very fast). LPPassManager
780 interface should be used to access Function or Module level analysis
781 information.</p>
783 </div>
786 <!-- _______________________________________________________________________ -->
787 <h4>
789 </h4>
791 <div>
795 </pre></div><p>
798 the transformation or analysis work of your pass. As usual, a true value should
800 should be used to update loop nest.</p>
802 </div>
804 <!-- _______________________________________________________________________ -->
805 <h4>
807 </h4>
809 <div>
813 </pre></div>
816 called when the pass framework has finished calling <a
818 program being compiled. </p>
820 </div>
822 </div>
824 <!-- ======================================================================= -->
825 <h3>
827 </h3>
829 <div>
832 but executes on each single entry single exit region in the function.
834 region is processed last. </p>
839 methods should return true if they modified the program, or false if they didn not.
840 </p>
842 <!-- _______________________________________________________________________ -->
843 <h4>
846 </a>
847 </h4>
849 <div>
853 </pre></div>
856 type of stuff that does not depend on the functions being processed. The
858 other pass executions (thus it should be very fast). RPPassManager
859 interface should be used to access Function or Module level analysis
860 information.</p>
862 </div>
865 <!-- _______________________________________________________________________ -->
866 <h4>
868 </h4>
870 <div>
874 </pre></div><p>
877 the transformation or analysis work of your pass. As usual, a true value should
879 should be used to update region tree.</p>
881 </div>
883 <!-- _______________________________________________________________________ -->
884 <h4>
886 </h4>
888 <div>
892 </pre></div>
895 called when the pass framework has finished calling <a
897 program being compiled. </p>
899 </div>
901 </div>
903 <!-- ======================================================================= -->
904 <h3>
906 </h3>
908 <div>
912 their scope of inspection and modification to a single basic block at a time.
915 <ol>
917 <li>Maintain state across invocations of
920 <li>Any of the things forbidden for
922 </ol>
925 optimizations. They may override the same <a
928 href="#FunctionPass"><tt>FunctionPass</tt></a>'s have, but also have the following virtual methods that may also be implemented:</p>
930 <!-- _______________________________________________________________________ -->
931 <h4>
934 </a>
935 </h4>
937 <div>
941 </pre></div>
946 to do simple initialization that does not depend on the
948 scheduled to overlap with any other pass executions (thus it should be very
949 fast).</p>
951 </div>
953 <!-- _______________________________________________________________________ -->
954 <h4>
956 </h4>
958 <div>
962 </pre></div>
965 function is not allowed to inspect or modify basic blocks other than the
966 parameter, and are not allowed to modify the CFG. A true value must be returned
967 if the basic block is modified.</p>
969 </div>
971 <!-- _______________________________________________________________________ -->
972 <h4>
975 </a>
976 </h4>
978 <div>
982 </pre></div>
985 called when the pass framework has finished calling <a
987 program being compiled. This can be used to perform per-function
988 finalization.</p>
990 </div>
992 </div>
994 <!-- ======================================================================= -->
995 <h3>
997 </h3>
999 <div>
1002 executes on the machine-dependent representation of each LLVM function in the
1003 program.</p>
1005 <p>Code generator passes are registered and initialized specially by
1008 commands.</p>
1015 <ol>
1016 <li>Modify or create any LLVM IR Instructions, BasicBlocks, Arguments,
1017 Functions, GlobalVariables, GlobalAliases, or Modules.</li>
1021 data)</li>
1022 </ol>
1024 <!-- _______________________________________________________________________ -->
1025 <h4>
1028 </a>
1029 </h4>
1031 <div>
1035 </pre></div>
1050 </div>
1052 </div>
1054 </div>
1056 <!-- *********************************************************************** -->
1057 <h2>
1059 </h2>
1060 <!-- *********************************************************************** -->
1062 <div>
1065 pass registration works, and discussed some of the reasons that it is used and
1066 what it does. Here we discuss how and why passes are registered.</p>
1069 template. The template parameter is the name of the pass that is to be used on
1070 the command line to specify that the pass should be added to a program (for
1073 programs, as
1076 <p>If you want your pass to be easily dumpable, you should
1079 <!-- _______________________________________________________________________ -->
1080 <h4>
1082 </h4>
1084 <div>
1088 </pre></div>
1091 a human readable version of the analysis results. This is useful for debugging
1092 an analysis itself, as well as for other people to figure out how an analysis
1097 program that has been analyzed. Note however that this pointer may be null in
1099 debugger), so it should only be used to enhance debug output, it should not be
1100 depended on.</p>
1102 </div>
1104 </div>
1106 <!-- *********************************************************************** -->
1107 <h2>
1109 </h2>
1110 <!-- *********************************************************************** -->
1112 <div>
1117 know how the passes interact with each other and what dependencies exist between
1118 the various passes. To track this, each pass can declare the set of passes that
1119 are required to be executed before the current pass, and the passes which are
1120 invalidated by the current pass.</p>
1122 <p>Typically this functionality is used to require that analysis results are
1123 computed before your pass is run. Running arbitrary transformation passes can
1124 invalidate the computed analysis results, which is what the invalidation set
1125 specifies. If a pass does not implement the <tt><a
1129 <!-- _______________________________________________________________________ -->
1130 <h4>
1132 </h4>
1134 <div>
1138 </pre></div>
1141 invalidated sets may be specified for your transformation. The implementation
1142 should fill in the <tt><a
1144 object with information about which passes are required and not invalidated. To
1145 do this, a pass may call any of the following methods on the AnalysisUsage
1146 object:</p>
1147 </div>
1149 <!-- _______________________________________________________________________ -->
1150 <h4>
1154 </a>
1155 </h4>
1157 <div>
1158 <p>
1159 If your pass requires a previous pass to be executed (an analysis for example),
1160 it can use one of these methods to arrange for it to be run before your pass.
1161 LLVM has many different types of analyses and passes that can be required,
1164 be no critical edges in the CFG when your pass has been run.
1165 </p>
1167 <p>
1168 Some analyses chain to other analyses to do their job. For example, an <a
1173 that the transitively required pass should be alive as long as the requiring
1174 pass is.
1175 </p>
1176 </div>
1178 <!-- _______________________________________________________________________ -->
1179 <h4>
1182 </a>
1183 </h4>
1185 <div>
1186 <p>
1187 One of the jobs of the PassManager is to optimize how and when analyses are run.
1188 In particular, it attempts to avoid recomputing data unless it needs to. For
1189 this reason, passes are allowed to declare that they preserve (i.e., they don't
1190 invalidate) an existing analysis if it's available. For example, a simple
1191 constant folding pass would not modify the CFG, so it can't possibly affect the
1192 results of dominator analysis. By default, all passes are assumed to invalidate
1193 all others.
1194 </p>
1196 <p>
1200 not modify the LLVM program at all (which is true for analyses), and the
1202 instructions in the program but do not modify the CFG or terminator instructions
1203 (note that this property is implicitly set for <a
1205 </p>
1207 <p>
1210 and dominator related analyses if they exist, so it can preserve them, despite
1211 the fact that it hacks on the CFG.
1212 </p>
1213 </div>
1215 <!-- _______________________________________________________________________ -->
1216 <h4>
1219 </a>
1220 </h4>
1222 <div>
1226 <b>void</b> <a href="http://llvm.org/doxygen/structLICM.html">LICM</a>::getAnalysisUsage(AnalysisUsage &AU) <b>const</b> {
1227 AU.setPreservesCFG();
1228 AU.addRequired<<a href="http://llvm.org/doxygen/classllvm_1_1LoopInfo.html">LoopInfo</a>>();
1229 }
1230 </pre></div>
1232 </div>
1234 <!-- _______________________________________________________________________ -->
1235 <h4>
1239 </a>
1240 </h4>
1242 <div>
1245 your class, providing you with access to the passes that you declared that you
1247 method. It takes a single template argument that specifies which pass class you
1248 want, and returns a reference to that pass. For example:</p>
1251 bool LICM::runOnFunction(Function &F) {
1253 ...
1254 }
1255 </pre></div>
1257 <p>This method call returns a reference to the pass desired. You may get a
1258 runtime assertion failure if you attempt to get an analysis that you did not
1259 declare as required in your <a
1264 A module level pass can use function level analysis info using this interface.
1265 For example:</p>
1268 bool ModuleLevelPass::runOnModule(Module &M) {
1269 ...
1271 ...
1272 }
1273 </pre></div>
1275 <p>In above example, runOnFunction for DominatorTree is called by pass manager
1276 before returning a reference to the desired pass.</p>
1278 <p>
1279 If your pass is capable of updating analyses if they exist (e.g.,
1282 if it is active. For example:</p>
1285 ...
1288 }
1289 ...
1290 </pre></div>
1292 </div>
1294 </div>
1296 <!-- *********************************************************************** -->
1297 <h2>
1299 </h2>
1300 <!-- *********************************************************************** -->
1302 <div>
1304 <p>Now that we understand the basics of how passes are defined, how they are
1305 used, and how they are required from other passes, it's time to get a little bit
1306 fancier. All of the pass relationships that we have seen so far are very
1307 simple: one pass depends on one other specific pass to be run before it can run.
1308 For many applications, this is great, for others, more flexibility is
1309 required.</p>
1311 <p>In particular, some analyses are defined such that there is a single simple
1312 interface to the analysis results, but multiple ways of calculating them.
1313 Consider alias analysis for example. The most trivial alias analysis returns
1314 "may alias" for any alias query. The most sophisticated analysis a
1315 flow-sensitive, context-sensitive interprocedural analysis that can take a
1316 significant amount of time to execute (and obviously, there is a lot of room
1317 between these two extremes for other implementations). To cleanly support
1318 situations like this, the LLVM Pass Infrastructure supports the notion of
1319 Analysis Groups.</p>
1321 <!-- _______________________________________________________________________ -->
1322 <h4>
1324 </h4>
1326 <div>
1328 <p>An Analysis Group is a single simple interface that may be implemented by
1329 multiple different passes. Analysis Groups can be given human readable names
1331 class. An analysis group may have one or more implementations, one of which is
1334 <p>Analysis groups are used by client passes just like other passes are: the
1337 scans the available passes to see if any implementations of the analysis group
1338 are available. If none is available, the default implementation is created for
1343 passes, all analysis group implementations must be registered, and must use the
1345 implementation pool. Also, a default implementation of the interface
1351 analysis group. The default implementation of the alias analysis interface (the
1352 <tt><a
1354 pass) just does a few simple checks that don't require significant analysis to
1355 compute (such as: two different globals can never alias each other, etc).
1356 Passes that use the <tt><a
1358 interface (for example the <tt><a
1360 not care which implementation of alias analysis is actually provided, they just
1361 use the designated interface.</p>
1363 <p>From the user's perspective, commands work just like normal. Issuing the
1365 instantiated and added to the pass sequence. Issuing the command '<tt>opt
1368 hypothetical example) instead.</p>
1370 </div>
1372 <!-- _______________________________________________________________________ -->
1373 <h4>
1375 </h4>
1377 <div>
1381 implementations to the analysis group. First,
1382 an analysis group should be registered, with a human readable name
1383 provided for it.
1384 Unlike registration of passes, there is no command line argument to be specified
1388 <b>static</b> RegisterAnalysisGroup<<a href="http://llvm.org/doxygen/classllvm_1_1AliasAnalysis.html">AliasAnalysis</a>> A("<i>Alias Analysis</i>");
1389 </pre></div>
1391 <p>Once the analysis is registered, passes can declare that they are valid
1392 implementations of the interface by using the following code:</p>
1397 INITIALIZE_AG_PASS(FancyAA, <a href="http://llvm.org/doxygen/classllvm_1_1AliasAnalysis.html">AliasAnalysis</a>, "<i>somefancyaa</i>",
1398 "<i>A more complex alias analysis implementation</i>",
1402 );
1403 }
1404 </pre></div>
1408 to "join" the <tt><a href="http://llvm.org/doxygen/classllvm_1_1AliasAnalysis.html">AliasAnalysis</a></tt>
1409 analysis group. Every implementation of an analysis group should join using
1410 this macro.</p>
1415 INITIALIZE_AG_PASS(BasicAA, <a href="http://llvm.org/doxygen/classllvm_1_1AliasAnalysis.html">AliasAnalysis</a>, "<i>basicaa</i>",
1416 "<i>Basic Alias Analysis (default AA impl)</i>",
1420 );
1421 }
1422 </pre></div>
1424 <p>Here we show how the default implementation is specified (using the final
1426 one default implementation available at all times for an Analysis Group to be
1428 Here we declare that the
1429 <tt><a href="http://llvm.org/doxygen/structBasicAliasAnalysis.html">BasicAliasAnalysis</a></tt>
1430 pass is the default implementation for the interface.</p>
1432 </div>
1434 </div>
1436 <!-- *********************************************************************** -->
1437 <h2>
1439 </h2>
1440 <!-- *********************************************************************** -->
1442 <div>
1445 class is designed to be an easy way to expose various success
1446 metrics from passes. These statistics are printed at the end of a
1447 run, when the -stats command line option is enabled on the command
1448 line. See the <a href="http://llvm.org/docs/ProgrammersManual.html#Statistic">Statistics section</a> in the Programmer's Manual for details.
1450 </div>
1453 <!-- *********************************************************************** -->
1454 <h2>
1456 </h2>
1457 <!-- *********************************************************************** -->
1459 <div>
1463 <a
1466 are set up correctly, and then schedules passes to run efficiently. All of the
1468 passes.</p>
1471 time of a series of passes:</p>
1473 <ol>
1475 recomputing analysis results as much as possible. This means keeping track of
1476 which analyses are available already, which analyses get invalidated, and which
1477 analyses are needed to be run for a pass. An important part of work is that the
1480 results as soon as they are no longer needed.</li>
1484 of a series of passes by pipelining the passes together. This means that, given
1487 the first function, then all of the <a
1489 etc... until the entire program has been run through the passes.
1491 <p>This improves the cache behavior of the compiler, because it is only touching
1492 the LLVM program representation for a single function at a time, instead of
1493 traversing the entire program. It reduces the memory consumption of compiler,
1494 because, for example, only one <a
1496 needs to be calculated at a time. This also makes it possible to implement
1497 some <a
1500 </ol>
1503 much information it has about the behaviors of the passes it is scheduling. For
1504 example, the "preserved" set is intentionally conservative in the face of an
1506 Not implementing when it should be implemented will have the effect of not
1507 allowing any analysis results to live across the execution of your pass.</p>
1510 options that is useful for debugging pass execution, seeing how things work, and
1511 diagnosing when you should be preserving more analyses than you currently are
1520 $ opt -load ../../../Debug+Asserts/lib/Hello.so -gcse -licm --debug-pass=Structure < hello.bc > /dev/null
1521 Module Pass Manager
1522 Function Pass Manager
1523 Dominator Set Construction
1524 Immediate Dominators Construction
1525 Global Common Subexpression Elimination
1526 -- Immediate Dominators Construction
1527 -- Global Common Subexpression Elimination
1528 Natural Loop Construction
1529 Loop Invariant Code Motion
1530 -- Natural Loop Construction
1531 -- Loop Invariant Code Motion
1532 Module Verifier
1533 -- Dominator Set Construction
1534 -- Module Verifier
1535 Bitcode Writer
1536 --Bitcode Writer
1537 </pre></div>
1539 <p>This output shows us when passes are constructed and when the analysis
1541 GCSE uses dominator and immediate dominator information to do its job. The LICM
1542 pass uses natural loop information, which uses dominator sets, but not immediate
1543 dominators. Because immediate dominators are no longer useful after the GCSE
1544 pass, it is immediately destroyed. The dominator sets are then reused to
1545 compute natural loop information, which is then used by the LICM pass.</p>
1547 <p>After the LICM pass, the module verifier runs (which is automatically added
1549 resultant LLVM code is well formed. After it finishes, the dominator set
1550 information is destroyed, after being computed once, and shared by three
1551 passes.</p>
1557 $ opt -load ../../../Debug+Asserts/lib/Hello.so -gcse -hello -licm --debug-pass=Structure < hello.bc > /dev/null
1558 Module Pass Manager
1559 Function Pass Manager
1560 Dominator Set Construction
1561 Immediate Dominators Construction
1562 Global Common Subexpression Elimination
1564 -- Immediate Dominators Construction
1565 -- Global Common Subexpression Elimination
1566 <b> Hello World Pass
1567 -- Hello World Pass
1568 Dominator Set Construction</b>
1569 Natural Loop Construction
1570 Loop Invariant Code Motion
1571 -- Natural Loop Construction
1572 -- Loop Invariant Code Motion
1573 Module Verifier
1574 -- Dominator Set Construction
1575 -- Module Verifier
1576 Bitcode Writer
1577 --Bitcode Writer
1578 Hello: __main
1579 Hello: puts
1580 Hello: main
1581 </pre></div>
1584 Dominator Set pass, even though it doesn't modify the code at all! To fix this,
1585 we need to add the following <a
1591 AU.setPreservesAll();
1592 }
1593 </pre></div>
1598 $ opt -load ../../../Debug+Asserts/lib/Hello.so -gcse -hello -licm --debug-pass=Structure < hello.bc > /dev/null
1599 Pass Arguments: -gcse -hello -licm
1600 Module Pass Manager
1601 Function Pass Manager
1602 Dominator Set Construction
1603 Immediate Dominators Construction
1604 Global Common Subexpression Elimination
1605 -- Immediate Dominators Construction
1606 -- Global Common Subexpression Elimination
1607 Hello World Pass
1608 -- Hello World Pass
1609 Natural Loop Construction
1610 Loop Invariant Code Motion
1611 -- Loop Invariant Code Motion
1612 -- Natural Loop Construction
1613 Module Verifier
1614 -- Dominator Set Construction
1615 -- Module Verifier
1616 Bitcode Writer
1617 --Bitcode Writer
1618 Hello: __main
1619 Hello: puts
1620 Hello: main
1621 </pre></div>
1623 <p>Which shows that we don't accidentally invalidate dominator information
1624 anymore, and therefore do not have to compute it twice.</p>
1626 <!-- _______________________________________________________________________ -->
1627 <h4>
1629 </h4>
1631 <div>
1635 </pre></div>
1638 results, and how long to keep them around for. Because the lifetime of the pass
1639 object itself is effectively the entire duration of the compilation process, we
1640 need some way to free analysis results when they are no longer useful. The
1643 <p>If you are writing an analysis or any other pass that retains a significant
1644 amount of state (for use by another pass which "requires" your pass and uses the
1650 </div>
1652 </div>
1654 <!-- *********************************************************************** -->
1655 <h2>
1657 </h2>
1658 <!-- *********************************************************************** -->
1660 <div>
1663 both for the purposes of distribution, and for regulating the resident code size
1664 when running on the target system. Therefore, it becomes desirable to
1665 selectively use some passes, while omitting others and maintain the flexibility
1666 to change configurations later on. You want to be able to do all this, and,
1667 provide feedback to the user. This is where pass registration comes into
1668 play.</p>
1670 <p>The fundamental mechanisms for pass registration are the
1676 communicates additions and deletions to the command line interface.</p>
1679 information provided about a particular pass. This information includes the
1680 command line name, the command help string and the address of the function used
1681 to create an instance of the pass. A global static constructor of one of these
1684 in the tool will be registered at start up. A dynamically loaded pass will
1685 register on load and unregister at unload.</p>
1687 <!-- _______________________________________________________________________ -->
1688 <h3>
1690 </h3>
1692 <div>
1694 <p>There are predefined registries to track instruction scheduling
1697 allocator machine pass.</p>
1699 <p>Implement your register allocator machine pass. In your register allocator
1700 .cpp file add the following include;</p>
1703 #include "llvm/CodeGen/RegAllocRegistry.h"
1704 </pre></div>
1706 <p>Also in your register allocator .cpp file, define a creator function in the
1707 form; </p>
1710 FunctionPass *createMyRegisterAllocator() {
1711 return new MyRegisterAllocator();
1712 }
1713 </pre></div>
1715 <p>Note that the signature of this function should match the type of
1720 static RegisterRegAlloc myRegAlloc("myregalloc",
1721 " my register allocator help string",
1722 createMyRegisterAllocator);
1723 </pre></div>
1725 <p>Note the two spaces prior to the help string produces a tidy result on the
1726 -help query.</p>
1729 $ llc -help
1730 ...
1731 -regalloc - Register allocator to use (default=linearscan)
1732 =linearscan - linear scan register allocator
1733 =local - local register allocator
1734 =simple - simple register allocator
1735 =myregalloc - my register allocator help string
1736 ...
1737 </pre></div>
1740 an option. Registering instruction schedulers is similar except use the
1745 <p>To force the load/linking of your register allocator into the llc/lli tools,
1749 </div>
1752 <!-- _______________________________________________________________________ -->
1753 <h3>
1755 </h3>
1757 <div>
1759 <p>The easiest way to get started is to clone one of the existing registries; we
1763 <p>Then you need to declare the registry. Example: if your pass registry is
1767 MachinePassRegistry RegisterMyPasses::Registry;
1768 </pre></div>
1773 cl::opt<RegisterMyPasses::FunctionPassCtor, false,
1775 MyPassOpt("mypass",
1776 cl::init(&createDefaultMyPass),
1777 cl::desc("my pass option help"));
1778 </pre></div>
1781 creator.</p>
1783 </div>
1785 </div>
1787 <!-- *********************************************************************** -->
1788 <h2>
1790 </h2>
1791 <!-- *********************************************************************** -->
1793 <div>
1795 <p>Unfortunately, using GDB with dynamically loaded passes is not as easy as it
1796 should be. First of all, you can't set a breakpoint in a shared object that has
1797 not been loaded yet, and second of all there are problems with inlined functions
1798 in shared objects. Here are some suggestions to debugging your pass with
1799 GDB.</p>
1801 <p>For sake of discussion, I'm going to assume that you are debugging a
1803 on that.</p>
1805 <!-- _______________________________________________________________________ -->
1806 <h4>
1808 </h4>
1810 <div>
1816 GNU gdb 5.0
1817 Copyright 2000 Free Software Foundation, Inc.
1818 GDB is free software, covered by the GNU General Public License, and you are
1819 welcome to change it and/or distribute copies of it under certain conditions.
1820 Type "show copying" to see the conditions.
1821 There is absolutely no warranty for GDB. Type "show warranty" for details.
1822 This GDB was configured as "sparc-sun-solaris2.6"...
1823 (gdb)
1824 </pre></div>
1827 time to load. Be patient. Since we cannot set a breakpoint in our pass yet
1828 (the shared object isn't loaded until runtime), we must execute the process, and
1829 have it stop before it invokes our pass, but after it has loaded the shared
1830 object. The most foolproof way of doing this is to set a breakpoint in
1832 want:</p>
1838 Starting program: opt test.bc -load $(LLVMTOP)/llvm/Debug+Asserts/lib/[libname].so -[passoption]
1841 (gdb)
1842 </pre></div>
1845 now free to set breakpoints in your pass so that you can trace through execution
1846 or do other standard debugging stuff.</p>
1848 </div>
1850 <!-- _______________________________________________________________________ -->
1851 <h4>
1853 </h4>
1855 <div>
1857 <p>Once you have the basics down, there are a couple of problems that GDB has,
1858 some with solutions, some without.</p>
1860 <ul>
1861 <li>Inline functions have bogus stack information. In general, GDB does a
1862 pretty good job getting stack traces and stepping through inline functions.
1863 When a pass is dynamically loaded however, it somehow completely loses this
1864 capability. The only solution I know of is to de-inline a function (move it
1865 from the body of a class to a .cpp file).</li>
1867 <li>Restarting the program breaks breakpoints. After following the information
1868 above, you have succeeded in getting some breakpoints planted in your pass. Nex
1870 and you start getting errors about breakpoints being unsettable. The only way I
1872 already set in your pass, run the program, and re-set the breakpoints once
1875 </ul>
1877 <p>Hopefully these tips will help with common case debugging situations. If
1878 you'd like to contribute some tips of your own, just contact <a
1881 </div>
1883 </div>
1885 <!-- *********************************************************************** -->
1886 <h2>
1888 </h2>
1889 <!-- *********************************************************************** -->
1891 <div>
1893 <p>Although the LLVM Pass Infrastructure is very capable as it stands, and does
1894 some nifty stuff, there are things we'd like to add in the future. Here is
1895 where we are going:</p>
1897 <!-- _______________________________________________________________________ -->
1898 <h4>
1900 </h4>
1902 <div>
1904 <p>Multiple CPU machines are becoming more common and compilation can never be
1905 fast enough: obviously we should allow for a multithreaded compiler. Because of
1906 the semantics defined for passes above (specifically they cannot maintain state
1909 to create multiple instances of each pass object, and allow the separate
1910 instances to be hacking on different parts of the program at the same time.</p>
1912 <p>This implementation would prevent each of the passes from having to implement
1913 multithreaded constructs, requiring only the LLVM core to have locking in a few
1914 places (for global resources). Although this is a simple extension, we simply
1915 haven't had time (or multiprocessor machines, thus a reason) to implement this.
1916 Despite that, we have kept the LLVM passes SMP ready, and you should too.</p>
1918 </div>
1920 </div>
1922 <!-- *********************************************************************** -->
1923 <hr>
1924 <address>
1932 Last modified: $Date$
1933 </address>
1935 </body>
1936 </html>