| blob | e8d81a25061daa2db8d873767113226f2c1b5b2e |
3 <html>
4 <head>
8 </head>
9 <body>
12 LLVM Programmer's Manual
13 </div>
15 <ol>
18 <ul>
20 <!--
21 <li>The <tt>-time-passes</tt> option</li>
22 <li>How to use the LLVM Makefile system</li>
23 <li>How to write a regression test</li>
25 -->
26 </ul>
27 </li>
29 <ul>
34 <ul>
37 </ul>
38 </li>
40 option</a>
41 <ul>
44 </ul>
45 </li>
47 option</a></li>
48 <!--
49 <li>The <tt>InstVisitor</tt> template
50 <li>The general graph API
51 -->
53 </ul>
54 </li>
56 <ul>
58 <ul>
67 </ul></li>
69 <ul>
79 </ul></li>
81 <ul>
89 </ul></li>
91 <!--<ul>
92 todo
95 <ul>
99 </ul></li>
100 </ul>
101 </li>
103 <ul>
105 <ul>
113 class pointer</a> </li>
115 complex example</a> </li>
117 the same way</a> </li>
119 use-def chains</a> </li>
121 successors of blocks</a></li>
122 </ul>
123 </li>
125 <ul>
132 </ul>
133 </li>
135 <!--
136 <li>Working with the Control Flow Graph
137 <ul>
138 <li>Accessing predecessors and successors of a <tt>BasicBlock</tt>
139 <li>
140 <li>
141 </ul>
142 -->
143 </ul>
144 </li>
147 <ul>
149 </a></li>
154 </ul>
155 </li>
158 <ul>
160 <ul>
165 </ul></li>
167 <li><a href="#SymbolTable">The <tt>ValueSymbolTable</tt> and <tt>TypeSymbolTable</tt> classes</a></li>
168 <li><a href="#UserLayout">The <tt>User</tt> and owned <tt>Use</tt> classes' memory layout</a></li>
169 </ul></li>
172 <ul>
176 <ul>
178 <ul>
181 <ul>
183 <ul>
186 </ul>
187 </li>
188 </ul>
189 </li>
190 </ul>
191 </li>
194 </ul>
195 </li>
196 </ul>
197 </li>
198 </ol>
207 </div>
209 <!-- *********************************************************************** -->
212 </div>
213 <!-- *********************************************************************** -->
217 <p>This document is meant to highlight some of the important classes and
218 interfaces available in the LLVM source-base. This manual is not
219 intended to explain what LLVM is, how it works, and what LLVM code looks
220 like. It assumes that you know the basics of LLVM and are interested
221 in writing transformations or otherwise analyzing or manipulating the
222 code.</p>
224 <p>This document should get you oriented so that you can find your
225 way in the continuously growing source code that makes up the LLVM
226 infrastructure. Note that this manual is not intended to serve as a
227 replacement for reading the source code, so if you think there should be
228 a method in one of these classes to do something, but it's not listed,
230 are provided to make this as easy as possible.</p>
232 <p>The first section of this document describes general information that is
233 useful to know when working in the LLVM infrastructure, and the second describes
234 the Core LLVM classes. In the future this manual will be extended with
235 information describing how to use extension libraries, such as dominator
236 information, CFG traversal routines, and useful utilities like the <tt><a
239 </div>
241 <!-- *********************************************************************** -->
244 </div>
245 <!-- *********************************************************************** -->
249 <p>This section contains general information that is useful if you are working
250 in the LLVM source-base, but that isn't specific to any particular API.</p>
252 </div>
254 <!-- ======================================================================= -->
257 </div>
261 <p>LLVM makes heavy use of the C++ Standard Template Library (STL),
262 perhaps much more than you are used to, or have seen before. Because of
263 this, you might want to do a little background reading in the
264 techniques used and capabilities of the library. There are many good
265 pages that discuss the STL, and several books on the subject that you
266 can get, so it will not be discussed in this document.</p>
270 <ol>
273 C++ Library reference</a> - an excellent reference for the STL and other parts
274 of the standard C++ library.</li>
277 O'Reilly book in the making. It has a decent Standard Library
278 Reference that rivals Dinkumware's, and is unfortunately no longer free since the
279 book has been published.</li>
282 Questions</a></li>
285 Contains a useful <a
290 Page</a></li>
294 the book).</a></li>
296 </ol>
300 to write maintainable code more than where to put your curly braces.</p>
302 </div>
304 <!-- ======================================================================= -->
307 </div>
311 <ol>
313 static and shared libraries across platforms</a></li>
314 </ol>
316 </div>
318 <!-- *********************************************************************** -->
321 </div>
322 <!-- *********************************************************************** -->
326 <p>Here we highlight some LLVM APIs that are generally useful and good to
327 know about when writing transformations.</p>
329 </div>
331 <!-- ======================================================================= -->
335 </div>
339 <p>The LLVM source-base makes extensive use of a custom form of RTTI.
341 operator, but they don't have some drawbacks (primarily stemming from
343 have a v-table). Because they are used so often, you must know what they
344 do and how they work. All of these templates are defined in the <a
346 file (note that you very rarely have to include this file directly).</p>
348 <dl>
352 "<tt>instanceof</tt>" operator. It returns true or false depending on whether
353 a reference or pointer points to an instance of the specified class. This can
354 be very useful for constraint checking of various sorts (example below).</p>
355 </dd>
360 converts a pointer or reference from a base class to a derived class, causing
361 an assertion failure if it is not really an instance of the right type. This
362 should be used in cases where you have some information that makes you believe
367 <pre>
369 if (isa<<a href="#Constant">Constant</a>>(V) || isa<<a href="#Argument">Argument</a>>(V) || isa<<a href="#GlobalValue">GlobalValue</a>>(V))
370 return true;
374 }
375 </pre>
376 </div>
380 operator.</p>
382 </dd>
387 It checks to see if the operand is of the specified type, and if so, returns a
388 pointer to it (this operator does not work with references). If the operand is
389 not of the correct type, a null pointer is returned. Thus, this works very
393 statement like this:</p>
396 <pre>
397 if (<a href="#AllocationInst">AllocationInst</a> *AI = dyn_cast<<a href="#AllocationInst">AllocationInst</a>>(Val)) {
399 }
400 </pre>
401 </div>
405 statement, which is very convenient.</p>
410 blocks to check for lots of different variants of classes. If you find
411 yourself wanting to do this, it is much cleaner and more efficient to use the
414 </dd>
420 argument (which it then propagates). This can sometimes be useful, allowing
421 you to combine several null checks into one.</p></dd>
427 as an argument (which it then propagates). This can sometimes be useful,
428 allowing you to combine several null checks into one.</p></dd>
430 </dl>
432 <p>These five templates can be used with any classes, whether they have a
433 v-table or not. To add support for these templates, you simply need to add
435 to. Describing this is currently outside the scope of this document, but there
436 are lots of examples in the LLVM source base.</p>
438 </div>
441 <!-- ======================================================================= -->
445 </div>
449 <p>Although LLVM generally does not do much string manipulation, we do have
450 several important APIs which take strings. Two important examples are the
451 Value class -- which has names for instructions, functions, etc. -- and the
452 StringMap class which is used extensively in LLVM and Clang.</p>
454 <p>These are generic classes, and they need to be able to accept strings which
455 may have embedded null characters. Therefore, they cannot simply take
457 clients to perform a heap allocation which is usually unnecessary. Instead,
459 passing strings efficiently.</p>
461 </div>
463 <!-- _______________________________________________________________________ -->
466 </div>
471 (a character array and a length) and supports the common operations available
474 <p>It can be implicitly constructed using a C style null-terminated string,
479 iterator find(StringRef Key);
480 </pre>
488 </pre>
494 for more information.</p>
497 pointers to external memory it is not generally safe to store an instance of the
498 class (unless you know that the external storage will not be freed). StringRef is
499 small and pervasive enough in LLVM that it should always be passed by value.</p>
501 </div>
503 <!-- _______________________________________________________________________ -->
506 </div>
511 strings. For example, a common LLVM paradigm is to name one instruction based on
512 the name of another instruction with a suffix, for example:</p>
515 <pre>
517 </pre>
518 </div>
522 which points to temporary (stack allocated) objects. Twines can be implicitly
523 constructed as the result of the plus operator applied to strings (i.e., a C
525 actual concatenation of strings until it is actually required, at which point
526 it can be efficiently rendered directly into a character array. This avoids
527 unnecessary heap allocation involved in constructing the temporary results of
528 string concatenation. See
530 for more information.</p>
533 and should almost never be stored or mentioned directly. They are intended
534 solely for use when defining a function which should be able to efficiently
535 accept concatenated strings.</p>
537 </div>
540 <!-- ======================================================================= -->
543 </div>
547 <p>Often when working on your pass you will put a bunch of debugging printouts
548 and other code into your pass. After you get it working, you want to remove
549 it, but you may need it again in the future (to work out new bugs that you run
550 across).</p>
552 <p> Naturally, because of this, you don't want to delete the debug printouts,
553 but you don't want them to always be noisy. A standard compromise is to comment
554 them out, allowing you to enable them if you need them in the future.</p>
558 this problem. Basically, you can put arbitrary code into the argument of the
563 <pre>
565 </pre>
566 </div>
571 <pre>
575 I am here!
576 </pre>
577 </div>
580 to not have to create "yet another" command line option for the debug output for
582 so they do not cause a performance impact at all (for the same reason, they
583 should also not contain side-effects!).</p>
586 enable or disable it directly in gdb. Just use "<tt>set DebugFlag=0</tt>" or
587 "<tt>set DebugFlag=1</tt>" from the gdb if the program is running. If the
588 program hasn't been started yet, you can always just run it with
591 </div>
593 <!-- _______________________________________________________________________ -->
597 </div>
603 generator). If you want to enable debug information with more fine-grained
605 option as follows:</p>
608 <pre>
609 #undef DEBUG_TYPE
611 #define DEBUG_TYPE "foo"
613 #undef DEBUG_TYPE
614 #define DEBUG_TYPE "bar"
616 #undef DEBUG_TYPE
617 #define DEBUG_TYPE ""
619 </pre>
620 </div>
625 <pre>
629 No debug type
630 'foo' debug type
631 'bar' debug type
632 No debug type (2)
634 'foo' debug type
636 'bar' debug type
637 </pre>
638 </div>
641 a file, to specify the debug type for the entire module (if you do this before
644 "bar", because there is no system in place to ensure that names do not
645 conflict. If two different modules use the same string, they will all be turned
646 on when the name is specified. This allows, for example, all debug information
648 even if the source lives in multiple files.</p>
652 statement. It takes an additional first parameter, which is the type to use. For
653 example, the preceding example could be written as:</p>
657 <pre>
662 </pre>
663 </div>
665 </div>
667 <!-- ======================================================================= -->
670 option</a>
671 </div>
678 keep track of what the LLVM compiler is doing and how effective various
679 optimizations are. It is useful to see what optimizations are contributing to
680 making a particular program run faster.</p>
682 <p>Often you may run your pass on some big program, and you're interested to see
683 how many times it makes a certain transformation. Although you can do this with
684 hand inspection, or some ad-hoc method, this is a real pain and not very useful
686 keep track of this information, and the calculated information is presented in a
687 uniform manner with the rest of the passes being executed.</p>
690 it are as follows:</p>
692 <ol>
696 <pre>
697 #define <a href="#DEBUG_TYPE">DEBUG_TYPE</a> "mypassname" <i>// This goes before any #includes.</i>
698 STATISTIC(NumXForms, "The # of times I did stuff");
699 </pre>
700 </div>
703 specified by the first argument. The pass name is taken from the DEBUG_TYPE
704 macro, and the description is taken from the second argument. The variable
710 <pre>
712 </pre>
713 </div>
715 </li>
716 </ol>
722 <pre>
725 </pre>
726 </div>
729 suite, it gives a report that looks like this:</p>
732 <pre>
733 7646 bitcodewriter - Number of normal instructions
734 725 bitcodewriter - Number of oversized instructions
735 129996 bitcodewriter - Number of bitcode bytes written
736 2817 raise - Number of insts DCEd or constprop'd
737 3213 raise - Number of cast-of-self removed
738 5046 raise - Number of expression trees converted
739 75 raise - Number of other getelementptr's formed
740 138 raise - Number of load/store peepholes
741 42 deadtypeelim - Number of unused typenames removed from symtab
742 392 funcresolve - Number of varargs functions resolved
743 27 globaldce - Number of global variables removed
744 2 adce - Number of basic blocks removed
745 134 cee - Number of branches revectored
746 49 cee - Number of setcc instruction eliminated
747 532 gcse - Number of loads removed
748 2919 gcse - Number of instructions removed
749 86 indvars - Number of canonical indvars added
750 87 indvars - Number of aux indvars removed
751 25 instcombine - Number of dead inst eliminate
752 434 instcombine - Number of insts combined
753 248 licm - Number of load insts hoisted
754 1298 licm - Number of insts hoisted to a loop pre-header
755 3 licm - Number of insts hoisted to multiple loop preds (bad, no loop pre-header)
756 75 mem2reg - Number of alloca's promoted
757 1444 cfgsimplify - Number of blocks simplified
758 </pre>
759 </div>
761 <p>Obviously, with so many optimizations, having a unified framework for this
762 stuff is very nice. Making your pass fit well into the framework makes it more
763 maintainable and useful.</p>
765 </div>
767 <!-- ======================================================================= -->
770 </div>
774 <p>Several of the important data structures in LLVM are graphs: for example
778 DAGs</a>. In many cases, while debugging various parts of the compiler, it is
779 nice to instantly visualize these graphs.</p>
781 <p>LLVM provides several callbacks that are available in a debug build to do
783 the current LLVM tool will pop up a window containing the CFG for the function
784 where each basic block is a node in the graph, and each node contains the
785 instructions in the block. Similarly, there also exists
790 up a window. Alternatively, you can sprinkle calls to these functions in your
791 code in places you want to debug.</p>
793 <p>Getting this to work requires a small amount of configuration. On Unix
795 toolkit, and make sure 'dot' and 'gv' are in your path. If you are running on
796 Mac OS/X, download and install the Mac OS/X <a
799 it) to your path. Once in your system and path are set up, rerun the LLVM
800 configure script and rebuild LLVM to enable this functionality.</p>
806 specified color (choices of colors can be found at <a
808 complex node attributes can be provided with <tt>call
811 Attributes</a>.) If you want to restart and clear all the current graph
814 </div>
816 <!-- *********************************************************************** -->
819 </div>
820 <!-- *********************************************************************** -->
825 and we commonly use STL data structures. This section describes the trade-offs
826 you should consider when you pick one.</p>
828 <p>
829 The first step is a choose your own adventure: do you want a sequential
830 container, a set-like container, or a map-like container? The most important
831 thing when choosing a container is the algorithmic properties of how you plan to
832 access the container. Based on that, you should use:</p>
834 <ul>
836 of an value based on another value. Map-like containers also support
837 efficient queries for containment (whether a key is in the map). Map-like
838 containers generally do not support efficient reverse mapping (values to
839 keys). If you need that, use two maps. Some map-like containers also
840 support efficient iteration through the keys in sorted order. Map-like
841 containers are the most expensive sort, only use them if you need one of
842 these capabilities.</li>
845 stuff into a container that automatically eliminates duplicates. Some
846 set-like containers support efficient iteration through the elements in
847 sorted order. Set-like containers are more expensive than sequential
848 containers.
849 </li>
852 the most efficient way to add elements and keeps track of the order they are
853 added to the collection. They permit duplicates and support efficient
854 iteration, but do not support efficient look-up based on a key.
855 </li>
858 container or reference structure that is used for character or byte
859 arrays.</li>
862 perform set operations on sets of numeric id's, while automatically
863 eliminating duplicates. Bit containers require a maximum of 1 bit for each
864 identifier you want to store.
865 </li>
866 </ul>
868 <p>
869 Once the proper category of container is determined, you can fine tune the
870 memory use, constant factors, and cache behaviors of access by intelligently
871 picking a member of the category. Note that constant factors and cache behavior
872 can be a big deal. If you have a vector that usually only contains a few
873 elements (but could contain many), for example, it's much better to use
875 . Doing so avoids (relatively) expensive malloc/free calls, which dwarf the
876 cost of adding the elements to the container. </p>
878 </div>
880 <!-- ======================================================================= -->
883 </div>
886 There are a variety of sequential containers available for you, based on your
887 needs. Pick the first in this section that will do what you want.
888 </div>
890 <!-- _______________________________________________________________________ -->
893 </div>
896 <p>Fixed size arrays are very simple and very fast. They are good if you know
897 exactly how many elements you have, or you have a (low) upper bound on how many
898 you have.</p>
899 </div>
901 <!-- _______________________________________________________________________ -->
904 </div>
907 <p>Heap allocated arrays (new[] + delete[]) are also simple. They are good if
908 the number of elements is variable, if you know how many elements you will need
909 before the array is allocated, and if the array is usually large (if not,
911 allocated array is the cost of the new/delete (aka malloc/free). Also note that
912 if you are allocating an array of a type with a constructor, the constructor and
913 destructors will be run for every element in the array (re-sizable vectors only
914 construct those elements actually used).</p>
915 </div>
917 <!-- _______________________________________________________________________ -->
920 </div>
925 it supports efficient iteration, lays out elements in memory order (so you can
926 do pointer arithmetic between elements), supports efficient push_back/pop_back
927 operations, supports efficient random access to its elements, etc.</p>
929 <p>The advantage of SmallVector is that it allocates space for
931 the SmallVector is dynamically smaller than N, no malloc is performed. This can
932 be a big win in cases where the malloc/free call is far more expensive than the
933 code that fiddles around with the elements.</p>
936 predecessors/successors of a block is usually less than 8). On the other hand,
937 this makes the size of the SmallVector itself large, so you don't want to
938 allocate lots of them (doing so will waste a lot of space). As such,
939 SmallVectors are most useful when on the stack.</p>
941 <p>SmallVector also provides a nice portable and efficient replacement for
944 </div>
946 <!-- _______________________________________________________________________ -->
949 </div>
952 <p>
953 std::vector is well loved and respected. It is useful when SmallVector isn't:
954 when the size of the vector is often large (thus the small optimization will
955 rarely be a benefit) or if you will be allocating many instances of the vector
956 itself (which would waste space for elements that aren't in the container).
957 vector is also useful when interfacing with code that expects vectors :).
958 </p>
963 <pre>
964 for ( ... ) {
966 use V;
967 }
968 </pre>
969 </div>
974 <pre>
976 for ( ... ) {
977 use V;
978 V.clear();
979 }
980 </pre>
981 </div>
983 <p>Doing so will save (at least) one heap allocation and free per iteration of
984 the loop.</p>
986 </div>
988 <!-- _______________________________________________________________________ -->
991 </div>
994 <p>std::deque is, in some senses, a generalized version of std::vector. Like
995 std::vector, it provides constant time random access and other similar
996 properties, but it also provides efficient access to the front of the list. It
997 does not guarantee continuity of elements within memory.</p>
999 <p>In exchange for this extra flexibility, std::deque has significantly higher
1000 constant factor costs than std::vector. If possible, use std::vector or
1001 something cheaper.</p>
1002 </div>
1004 <!-- _______________________________________________________________________ -->
1007 </div>
1010 <p>std::list is an extremely inefficient class that is rarely useful.
1011 It performs a heap allocation for every element inserted into it, thus having an
1012 extremely high constant factor, particularly for small data types. std::list
1013 also only supports bidirectional iteration, not random access iteration.</p>
1015 <p>In exchange for this high cost, std::list supports efficient access to both
1016 ends of the list (like std::deque, but unlike std::vector or SmallVector). In
1017 addition, the iterator invalidation characteristics of std::list are stronger
1018 than that of a vector class: inserting or removing an element into the list does
1019 not invalidate iterator or pointers to other elements in the list.</p>
1020 </div>
1022 <!-- _______________________________________________________________________ -->
1025 </div>
1029 intrusive, because it requires the element to store and provide access to the
1030 prev/next pointers for the list.</p>
1034 provides some novel characteristics. In particular, it can efficiently store
1035 polymorphic objects, the traits class is informed when an element is inserted or
1037 constant-time splice operation.</p>
1039 <p>These properties are exactly what we want for things like
1043 Related classes of interest are explained in the following subsections:
1044 <ul>
1049 </ul>
1050 </div>
1052 <!-- _______________________________________________________________________ -->
1055 </div>
1060 publicly derive from this traits class.</p>
1061 </div>
1063 <!-- _______________________________________________________________________ -->
1066 </div>
1070 supports a slightly narrower interface. Notably, inserters from
1074 used for a wide variety of customizations.</p>
1075 </div>
1077 <!-- _______________________________________________________________________ -->
1080 </div>
1085 in the default manner.</p>
1090 </div>
1092 <!-- _______________________________________________________________________ -->
1095 </div>
1099 citizen in the C++ ecosystem, it needs to support the standard container
1104 <p>The only sensible solution to this problem is to allocate a so-called
1106 iterator, providing the back-link to the last element. However conforming to the
1108 also must not be dereferenced.</p>
1111 how to allocate and store the sentinel. The corresponding policy is dictated
1113 whenever the need for a sentinel arises.</p>
1115 <p>While the default policy is sufficient in most cases, it may break down when
1118 is wasted. To alleviate the situation with numerous and voluminous
1124 arithmetic is used to obtain the sentinel, which is relative to the
1126 extra pointer, which serves as the back-link of the sentinel. This is the only
1127 field in the ghostly sentinel which can be legally accessed.</p>
1128 </div>
1130 <!-- _______________________________________________________________________ -->
1133 </div>
1138 <p>There are also various STL adapter classes such as std::queue,
1139 std::priority_queue, std::stack, etc. These provide simplified access to an
1140 underlying container but don't affect the cost of the container itself.</p>
1142 </div>
1145 <!-- ======================================================================= -->
1148 </div>
1152 <p>Set-like containers are useful when you need to canonicalize multiple values
1153 into a single representation. There are several different choices for how to do
1154 this, providing various trade-offs.</p>
1156 </div>
1159 <!-- _______________________________________________________________________ -->
1162 </div>
1166 <p>If you intend to insert a lot of elements, then do a lot of queries, a
1167 great approach is to use a vector (or other sequential container) with
1168 std::sort+std::unique to remove duplicates. This approach works really well if
1169 your usage pattern has these two distinct phases (insert then query), and can be
1171 </p>
1173 <p>
1174 This combination provides the several nice properties: the result data is
1175 contiguous in memory (good for cache locality), has few allocations, is easy to
1176 address (iterators in the final vector are just indices or pointers), and can be
1177 efficiently queried with a standard binary or radix search.</p>
1179 </div>
1181 <!-- _______________________________________________________________________ -->
1184 </div>
1188 <p>If you have a set-like data structure that is usually small and whose elements
1190 has space for N elements in place (thus, if the set is dynamically smaller than
1191 N, no malloc traffic is required) and accesses them with a simple linear search.
1192 When the set grows beyond 'N' elements, it allocates a more expensive representation that
1193 guarantees efficient access (for most types, it falls back to std::set, but for
1194 pointers it uses something far better, <a
1197 <p>The magic of this class is that it handles small sets extremely efficiently,
1198 but gracefully handles extremely large sets without loss of efficiency. The
1199 drawback is that the interface is quite small: it supports insertion, queries
1200 and erasing, but does not support iteration.</p>
1202 </div>
1204 <!-- _______________________________________________________________________ -->
1207 </div>
1211 <p>SmallPtrSet has all the advantages of <tt>SmallSet</tt> (and a <tt>SmallSet</tt> of pointers is
1213 more than 'N' insertions are performed, a single quadratically
1214 probed hash table is allocated and grows as needed, providing extremely
1215 efficient access (constant time insertion/deleting/queries with low constant
1216 factors) and is very stingy with malloc traffic.</p>
1219 whenever an insertion occurs. Also, the values visited by the iterators are not
1220 visited in sorted order.</p>
1222 </div>
1224 <!-- _______________________________________________________________________ -->
1227 </div>
1231 <p>
1232 DenseSet is a simple quadratically probed hash table. It excels at supporting
1233 small values: it uses a single allocation to hold all of the pairs that
1234 are currently inserted in the set. DenseSet is a great way to unique small
1235 values that are not simple pointers (use <a
1237 the same requirements for the value type that <a
1239 </p>
1241 </div>
1243 <!-- _______________________________________________________________________ -->
1246 </div>
1250 <p>
1251 FoldingSet is an aggregate class that is really good at uniquing
1252 expensive-to-create or polymorphic objects. It is a combination of a chained
1253 hash table with intrusive links (uniqued objects are required to inherit from
1255 its ID process.</p>
1258 a complex object (for example, a node in the code generator). The client has a
1259 description of *what* it wants to generate (it knows the opcode and all the
1260 operands), but we don't want to 'new' a node, then try inserting it into a set
1261 only to find out it already exists, at which point we would have to delete it
1262 and return the node that already exists.
1263 </p>
1265 <p>To support this style of client, FoldingSet perform a query with a
1266 FoldingSetNodeID (which wraps SmallVector) that can be used to describe the
1267 element that we want to query for. The query either returns the element
1268 matching the ID or it returns an opaque ID that indicates where insertion should
1269 take place. Construction of the ID usually does not require heap traffic.</p>
1271 <p>Because FoldingSet uses intrusive links, it can support polymorphic objects
1272 in the set (for example, you can have SDNode instances mixed with LoadSDNodes).
1273 Because the elements are individually allocated, pointers to the elements are
1274 stable: inserting or removing elements does not invalidate any pointers to other
1275 elements.
1276 </p>
1278 </div>
1280 <!-- _______________________________________________________________________ -->
1283 </div>
1288 many things but great at nothing. std::set allocates memory for each element
1289 inserted (thus it is very malloc intensive) and typically stores three pointers
1290 per element in the set (thus adding a large amount of per-element space
1291 overhead). It offers guaranteed log(n) performance, which is not particularly
1292 fast from a complexity standpoint (particularly if the elements of the set are
1293 expensive to compare, like strings), and has extremely high constant factors for
1294 lookup, insertion and removal.</p>
1296 <p>The advantages of std::set are that its iterators are stable (deleting or
1297 inserting an element from the set does not affect iterators or pointers to other
1298 elements) and that iteration over the set is guaranteed to be in sorted order.
1299 If the elements in the set are large, then the relative overhead of the pointers
1300 and malloc traffic is not a big deal, but if the elements of the set are small,
1301 std::set is almost never a good choice.</p>
1303 </div>
1305 <!-- _______________________________________________________________________ -->
1308 </div>
1313 Container</a>. The important property
1314 that this provides is efficient insertion with uniquing (duplicate elements are
1315 ignored) with iteration support. It implements this by inserting elements into
1316 both a set-like container and the sequential container, using the set-like
1317 container for uniquing and the sequential container for iteration.
1318 </p>
1320 <p>The difference between SetVector and other sets is that the order of
1321 iteration is guaranteed to match the order of insertion into the SetVector.
1322 This property is really important for things like sets of pointers. Because
1323 pointer values are non-deterministic (e.g. vary across runs of the program on
1324 different machines), iterating over the pointers in the set will
1325 not be in a well-defined order.</p>
1327 <p>
1328 The drawback of SetVector is that it requires twice as much space as a normal
1329 set and has the sum of constant factors from the set-like container and the
1330 sequential container that it uses. Use it *only* if you need to iterate over
1331 the elements in a deterministic order. SetVector is also expensive to delete
1332 elements out of (linear time), unless you use it's "pop_back" method, which is
1333 faster.
1334 </p>
1336 <p>SetVector is an adapter class that defaults to using std::vector and std::set
1337 for the underlying containers, so it is quite expensive. However,
1339 defaults to using a SmallVector and SmallSet of a specified size. If you use
1340 this, and if your sets are dynamically smaller than N, you will save a lot of
1341 heap traffic.</p>
1343 </div>
1345 <!-- _______________________________________________________________________ -->
1348 </div>
1352 <p>
1354 retains a unique ID for each element inserted into the set. It internally
1355 contains a map and a vector, and it assigns a unique ID for each value inserted
1356 into the set.</p>
1358 <p>UniqueVector is very expensive: its cost is the sum of the cost of
1359 maintaining both the map and vector, it has high complexity, high constant
1360 factors, and produces a lot of malloc traffic. It should be avoided.</p>
1362 </div>
1365 <!-- _______________________________________________________________________ -->
1368 </div>
1372 <p>
1373 The STL provides several other options, such as std::multiset and the various
1374 "hash_set" like containers (whether from C++ TR1 or from the SGI library). We
1375 never use hash_set and unordered_set because they are generally very expensive
1376 (each insertion requires a malloc) and very non-portable.
1377 </p>
1379 <p>std::multiset is useful if you're not interested in elimination of
1380 duplicates, but has all the drawbacks of std::set. A sorted vector (where you
1381 don't delete duplicate entries) or some other approach is almost always
1382 better.</p>
1384 </div>
1386 <!-- ======================================================================= -->
1389 </div>
1392 Map-like containers are useful when you want to associate data to a key. As
1393 usual, there are a lot of different ways to do this. :)
1394 </div>
1396 <!-- _______________________________________________________________________ -->
1399 </div>
1403 <p>
1404 If your usage pattern follows a strict insert-then-query approach, you can
1406 for set-like containers</a>. The only difference is that your query function
1407 (which uses std::lower_bound to get efficient log(n) lookup) should only compare
1408 the key, not both the key and value. This yields the same advantages as sorted
1409 vectors for sets.
1410 </p>
1411 </div>
1413 <!-- _______________________________________________________________________ -->
1416 </div>
1420 <p>
1421 Strings are commonly used as keys in maps, and they are difficult to support
1422 efficiently: they are variable length, inefficient to hash and compare when
1423 long, expensive to copy, etc. StringMap is a specialized container designed to
1424 cope with these issues. It supports mapping an arbitrary range of bytes to an
1425 arbitrary other object.</p>
1427 <p>The StringMap implementation uses a quadratically-probed hash table, where
1428 the buckets store a pointer to the heap allocated entries (and some other
1429 stuff). The entries in the map must be heap allocated because the strings are
1430 variable length. The string data (key) and the element object (value) are
1431 stored in the same allocation with the string data immediately after the element
1432 object. This container guarantees the "<tt>(char*)(&Value+1)</tt>" points
1433 to the key string for a value.</p>
1435 <p>The StringMap is very fast for several reasons: quadratic probing is very
1436 cache efficient for lookups, the hash value of strings in buckets is not
1437 recomputed when looking up an element, StringMap rarely has to touch the
1438 memory for unrelated objects when looking up a value (even when hash collisions
1439 happen), hash table growth does not recompute the hash values for strings
1440 already in the table, and each pair in the map is store in a single allocation
1441 (the string data is stored in the same allocation as the Value of a pair).</p>
1443 <p>StringMap also provides query methods that take byte ranges, so it only ever
1444 copies a string if a value is inserted into the table.</p>
1445 </div>
1447 <!-- _______________________________________________________________________ -->
1450 </div>
1453 <p>
1454 IndexedMap is a specialized container for mapping small dense integers (or
1455 values that can be mapped to small dense integers) to some other type. It is
1456 internally implemented as a vector with a mapping function that maps the keys to
1457 the dense integer range.
1458 </p>
1460 <p>
1461 This is useful for cases like virtual registers in the LLVM code generator: they
1462 have a dense mapping that is offset by a compile-time constant (the first
1463 virtual register ID).</p>
1465 </div>
1467 <!-- _______________________________________________________________________ -->
1470 </div>
1474 <p>
1475 DenseMap is a simple quadratically probed hash table. It excels at supporting
1476 small keys and values: it uses a single allocation to hold all of the pairs that
1477 are currently inserted in the map. DenseMap is a great way to map pointers to
1478 pointers, or map other small types to each other.
1479 </p>
1481 <p>
1482 There are several aspects of DenseMap that you should be aware of, however. The
1483 iterators in a densemap are invalidated whenever an insertion occurs, unlike
1484 map. Also, because DenseMap allocates space for a large number of key/value
1485 pairs (it starts with 64 by default), it will waste a lot of space if your keys
1486 or values are large. Finally, you must implement a partial specialization of
1487 DenseMapInfo for the key that you want, if it isn't already supported. This
1488 is required to tell DenseMap about two special marker values (which can never be
1489 inserted into the map) that it needs internally.</p>
1491 </div>
1493 <!-- _______________________________________________________________________ -->
1496 </div>
1500 <p>
1502 Value*s (or subclasses) to another type. When a Value is deleted or RAUW'ed,
1503 ValueMap will update itself so the new version of the key is mapped to the same
1504 value, just as if the key were a WeakVH. You can configure exactly how this
1505 happens, and what else happens on these two events, by passing
1508 </div>
1510 <!-- _______________________________________________________________________ -->
1513 </div>
1517 <p>
1519 a single allocation per pair inserted into the map, it offers log(n) lookup with
1520 an extremely large constant factor, imposes a space penalty of 3 pointers per
1521 pair in the map, etc.</p>
1523 <p>std::map is most useful when your keys or values are very large, if you need
1524 to iterate over the collection in sorted order, or if you need stable iterators
1525 into the map (i.e. they don't get invalidated if an insertion or deletion of
1526 another element takes place).</p>
1528 </div>
1530 <!-- _______________________________________________________________________ -->
1533 </div>
1537 <p>
1538 The STL provides several other options, such as std::multimap and the various
1539 "hash_map" like containers (whether from C++ TR1 or from the SGI library). We
1540 never use hash_set and unordered_set because they are generally very expensive
1541 (each insertion requires a malloc) and very non-portable.</p>
1543 <p>std::multimap is useful if you want to map a key to multiple values, but has
1544 all the drawbacks of std::map. A sorted vector or some other approach is almost
1545 always better.</p>
1547 </div>
1549 <!-- ======================================================================= -->
1552 </div>
1556 <p>
1557 TODO: const char* vs stringref vs smallstring vs std::string. Describe twine,
1558 xref to #string_apis.
1559 </p>
1561 </div>
1563 <!-- ======================================================================= -->
1566 </div>
1569 <p>Unlike the other containers, there are only two bit storage containers, and
1570 choosing when to use each is relatively straightforward.</p>
1572 <p>One additional option is
1574 implementation in many common compilers (e.g. commonly available versions of
1575 GCC) is extremely inefficient and 2) the C++ standards committee is likely to
1576 deprecate this container and/or change it significantly somehow. In any case,
1577 please don't use it.</p>
1578 </div>
1580 <!-- _______________________________________________________________________ -->
1583 </div>
1586 <p> The BitVector container provides a dynamic size set of bits for manipulation.
1587 It supports individual bit setting/testing, as well as set operations. The set
1588 operations take time O(size of bitvector), but operations are performed one word
1589 at a time, instead of one bit at a time. This makes the BitVector very fast for
1590 set operations compared to other containers. Use the BitVector when you expect
1591 the number of set bits to be high (IE a dense set).
1592 </p>
1593 </div>
1595 <!-- _______________________________________________________________________ -->
1598 </div>
1601 <p> The SmallBitVector container provides the same interface as BitVector, but
1602 it is optimized for the case where only a small number of bits, less than
1603 25 or so, are needed. It also transparently supports larger bit counts, but
1604 slightly less efficiently than a plain BitVector, so SmallBitVector should
1605 only be used when larger counts are rare.
1606 </p>
1608 <p>
1609 At this time, SmallBitVector does not support set operations (and, or, xor),
1610 and its operator[] does not provide an assignable lvalue.
1611 </p>
1612 </div>
1614 <!-- _______________________________________________________________________ -->
1617 </div>
1620 <p> The SparseBitVector container is much like BitVector, with one major
1621 difference: Only the bits that are set, are stored. This makes the
1622 SparseBitVector much more space efficient than BitVector when the set is sparse,
1623 as well as making set operations O(number of set bits) instead of O(size of
1624 universe). The downside to the SparseBitVector is that setting and testing of random bits is O(N), and on large SparseBitVectors, this can be slower than BitVector. In our implementation, setting or testing bits in sorted order
1625 (either forwards or reverse) is O(1) worst case. Testing and setting bits within 128 bits (depends on size) of the current bit is also O(1). As a general statement, testing/setting bits in a SparseBitVector is O(distance away from last set bit).
1626 </p>
1627 </div>
1629 <!-- *********************************************************************** -->
1632 </div>
1633 <!-- *********************************************************************** -->
1637 <p>This section describes how to perform some very simple transformations of
1638 LLVM code. This is meant to give examples of common idioms used, showing the
1640 you should also read about the main classes that you will be working with. The
1642 and descriptions of the main classes that you should know about.</p>
1644 </div>
1646 <!-- NOTE: this section should be heavy on example code -->
1647 <!-- ======================================================================= -->
1650 </div>
1654 <p>The LLVM compiler infrastructure have many different data structures that may
1655 be traversed. Following the example of the C++ standard template library, the
1656 techniques used to traverse these various data structures are all basically the
1659 function returns an iterator pointing to one past the last valid element of the
1661 between the two operations.</p>
1663 <p>Because the pattern for iteration is common across many different aspects of
1664 the program representation, the standard template library algorithms may be used
1665 on them, and it is easier to remember how to iterate. First we show a few common
1666 examples of the data structures that need to be traversed. Other data
1667 structures are traversed in very similar ways.</p>
1669 </div>
1671 <!-- _______________________________________________________________________ -->
1676 </div>
1681 transform in some way; in particular, you'd like to manipulate its
1688 <pre>
1695 </pre>
1696 </div>
1698 <p>Note that i can be used as if it were a pointer for the purposes of
1700 because the indirection operator is overloaded for the iterator
1704 </div>
1706 <!-- _______________________________________________________________________ -->
1711 </div>
1716 easy to iterate over the individual instructions that make up
1721 <pre>
1727 </pre>
1728 </div>
1730 <p>However, this isn't really the best way to print out the contents of a
1732 anything you'll care about, you could have just invoked the print routine on the
1735 </div>
1737 <!-- _______________________________________________________________________ -->
1742 </div>
1751 small example that shows how to dump all instructions in a function to the standard error stream:<p>
1754 <pre>
1758 for (inst_iterator I = inst_begin(F), E = inst_end(F); I != E; ++I)
1760 </pre>
1761 </div>
1764 work list with its initial contents. For example, if you wanted to
1766 F, all you would need to do is something like:</p>
1769 <pre>
1773 for (inst_iterator I = inst_begin(F), E = inst_end(F); I != E; ++I)
1774 worklist.insert(&*I);
1775 </pre>
1776 </div>
1781 </div>
1783 <!-- _______________________________________________________________________ -->
1786 vice-versa)</a>
1787 </div>
1791 <p>Sometimes, it'll be useful to grab a reference (or pointer) to a class
1792 instance when all you've got at hand is an iterator. Well, extracting
1793 a reference or a pointer from an iterator is very straight-forward.
1798 <pre>
1801 const Instruction& inst = *j;
1802 </pre>
1803 </div>
1805 <p>However, the iterators you'll be working with in the LLVM framework are
1806 special: they will automatically convert to a ptr-to-instance type whenever they
1807 need to. Instead of dereferencing the iterator and then taking the address of
1808 the result, you can simply assign the iterator to the proper pointer type and
1809 you get the dereference and address-of operation as a result of the assignment
1810 (behind the scenes, this is a result of overloading casting mechanisms). Thus
1811 the last line of the last example,</p>
1814 <pre>
1815 Instruction *pinst = &*i;
1816 </pre>
1817 </div>
1822 <pre>
1823 Instruction *pinst = i;
1824 </pre>
1825 </div>
1827 <p>It's also possible to turn a class pointer into the corresponding iterator,
1828 and this is a constant time operation (very efficient). The following code
1829 snippet illustrates use of the conversion constructors provided by LLVM
1830 iterators. By using these, you can explicitly grab the iterator of something
1831 without actually obtaining it via iteration over some structure:</p>
1834 <pre>
1835 void printNextInstruction(Instruction* inst) {
1836 BasicBlock::iterator it(inst);
1839 }
1840 </pre>
1841 </div>
1843 <p>Unfortunately, these implicit conversions come at a cost; they prevent
1844 these iterators from conforming to standard iterator conventions, and thus
1845 from being usable with standard algorithms and containers. For example, they
1847 from compiling:</p>
1850 <pre>
1852 </pre>
1853 </div>
1855 <p>Because of this, these implicit conversions may be removed some day,
1858 </div>
1860 <!--_______________________________________________________________________-->
1863 example</a>
1864 </div>
1868 <p>Say that you're writing a FunctionPass and would like to count all the
1872 much more straight-forward manner, but this example will allow us to explore how
1874 is what we want to do:</p>
1877 <pre>
1878 initialize callCounter to zero
1879 for each Function f in the Module
1880 for each BasicBlock b in f
1881 for each Instruction i in b
1882 if (i is a CallInst and calls the given function)
1883 increment callCounter
1884 </pre>
1885 </div>
1887 <p>And the actual code is (remember, because we're writing a
1892 <pre>
1893 Function* targetFunc = ...;
1895 class OurFunctionPass : public FunctionPass {
1896 public:
1897 OurFunctionPass(): callCounter(0) { }
1899 virtual runOnFunction(Function& F) {
1900 for (Function::iterator b = F.begin(), be = F.end(); b != be; ++b) {
1907 if (callInst->getCalledFunction() == targetFunc)
1908 ++callCounter;
1909 }
1910 }
1911 }
1912 }
1914 private:
1915 unsigned callCounter;
1916 };
1917 </pre>
1918 </div>
1920 </div>
1922 <!--_______________________________________________________________________-->
1925 </div>
1929 <p>You may have noticed that the previous example was a bit oversimplified in
1930 that it did not deal with call sites generated by 'invoke' instructions. In
1931 this, and in other situations, you may find that you want to treat
1934 less closely-related things. For these cases, LLVM provides a handy wrapper
1935 class called <a
1942 reference and it should not be dynamically allocated or deallocated using
1944 assignable and constructable, with costs equivalents to that of a bare pointer.
1945 If you look at its definition, it has only a single pointer member.</p>
1947 </div>
1949 <!--_______________________________________________________________________-->
1952 </div>
1966 <pre>
1967 Function *F = ...;
1973 }
1974 </pre>
1975 </div>
1979 doing it only once in the loop body and reusing its result.</p>
1986 all of the values that a particular instruction uses (that is, the operands of
1990 <pre>
1991 Instruction *pi = ...;
1994 Value *v = *i;
1996 }
1997 </pre>
1998 </div>
2001 mutation free algorithms (such as analyses, etc.). For this purpose above
2008 </div>
2010 <!--_______________________________________________________________________-->
2013 successors of blocks</a>
2014 </div>
2018 <p>Iterating over the predecessors and successors of a block is quite easy
2020 this to iterate over all predecessors of BB:</p>
2023 <pre>
2024 #include "llvm/Support/CFG.h"
2025 BasicBlock *BB = ...;
2027 for (pred_iterator PI = pred_begin(BB), E = pred_end(BB); PI != E; ++PI) {
2028 BasicBlock *Pred = *PI;
2030 }
2031 </pre>
2032 </div>
2034 <p>Similarly, to iterate over successors use
2035 succ_iterator/succ_begin/succ_end.</p>
2037 </div>
2040 <!-- ======================================================================= -->
2043 </div>
2047 <p>There are some primitive transformation operations present in the LLVM
2048 infrastructure that are worth knowing about. When performing
2049 transformations, it's fairly common to manipulate the contents of basic
2050 blocks. This section describes some of the common methods for doing so
2051 and gives example code.</p>
2053 </div>
2055 <!--_______________________________________________________________________-->
2059 </div>
2066 constructor for the kind of instruction to instantiate and provide the necessary
2071 <pre>
2072 AllocaInst* ai = new AllocaInst(Type::Int32Ty);
2073 </pre>
2074 </div>
2078 subclass is likely to have varying default parameters which change the semantics
2079 of the instruction, so refer to the <a
2085 <p>It is very useful to name the values of instructions when you're able to, as
2086 this facilitates the debugging of your transformations. If you end up looking
2087 at generated LLVM machine code, you definitely want to have logical names
2088 associated with the results of instructions! By supplying a value for the
2090 associate a logical name with the result of the instruction's execution at
2091 run time. For example, say that I'm writing a transformation that dynamically
2092 allocates space for an integer on the stack, and that integer is going to be
2093 used as some kind of index by some other code. To accomplish this, I place an
2099 <pre>
2101 </pre>
2102 </div>
2105 execution value, which is a pointer to an integer on the run time stack.</p>
2112 <ul>
2113 <li>Insertion into an explicit instruction list
2120 <pre>
2121 BasicBlock *pb = ...;
2122 Instruction *pi = ...;
2123 Instruction *newInst = new Instruction(...);
2126 </pre>
2127 </div>
2131 classes provide constructors which take a pointer to a
2133 looked like: </p>
2136 <pre>
2137 BasicBlock *pb = ...;
2138 Instruction *newInst = new Instruction(...);
2141 </pre>
2142 </div>
2147 <pre>
2148 BasicBlock *pb = ...;
2149 Instruction *newInst = new Instruction(..., pb);
2150 </pre>
2151 </div>
2153 <p>which is much cleaner, especially if you are creating
2154 long instruction streams.</p></li>
2156 <li>Insertion into an implicit instruction list
2159 are implicitly associated with an existing instruction list: the instruction
2160 list of the enclosing basic block. Thus, we could have accomplished the same
2162 </p>
2165 <pre>
2166 Instruction *pi = ...;
2167 Instruction *newInst = new Instruction(...);
2170 </pre>
2171 </div>
2173 <p>In fact, this sequence of steps occurs so frequently that the
2175 constructors which take (as a default parameter) a pointer to an
2179 provided instruction, immediately before that instruction. Using an
2181 parameter, the above code becomes:</p>
2184 <pre>
2185 Instruction* pi = ...;
2186 Instruction* newInst = new Instruction(..., pi);
2187 </pre>
2188 </div>
2190 <p>which is much cleaner, especially if you're creating a lot of
2192 </ul>
2194 </div>
2196 <!--_______________________________________________________________________-->
2199 </div>
2203 <p>Deleting an instruction from an existing sequence of instructions that form a
2205 you must have a pointer to the instruction that you wish to delete. Second, you
2206 need to obtain the pointer to that instruction's basic block. You use the
2207 pointer to the basic block to get its list of instructions and then use the
2208 erase function to remove your instruction. For example:</p>
2211 <pre>
2213 I->eraseFromParent();
2214 </pre>
2215 </div>
2217 </div>
2219 <!--_______________________________________________________________________-->
2223 </div>
2229 <p>Including "<a href="/doxygen/BasicBlockUtils_8h-source.html">llvm/Transforms/Utils/BasicBlockUtils.h</a>"
2235 <ul>
2238 <p>This function replaces all uses of a given instruction with a value,
2239 and then removes the original instruction. The following example
2240 illustrates the replacement of the result of a particular
2242 pointer to an integer.</p>
2245 <pre>
2246 AllocaInst* instToReplace = ...;
2247 BasicBlock::iterator ii(instToReplace);
2250 Constant::getNullValue(PointerType::getUnqual(Type::Int32Ty)));
2251 </pre></div></li>
2255 <p>This function replaces a particular instruction with another
2256 instruction, inserting the new instruction into the basic block at the
2257 location where the old instruction was, and replacing any uses of the old
2258 instruction with the new instruction. The following example illustrates
2262 <pre>
2263 AllocaInst* instToReplace = ...;
2264 BasicBlock::iterator ii(instToReplace);
2268 </pre></div></li>
2269 </ul>
2277 information.</p>
2279 <!-- Value::replaceAllUsesWith User::replaceUsesOfWith Point out:
2280 include/llvm/Transforms/Utils/ especially BasicBlockUtils.h with:
2281 ReplaceInstWithValue, ReplaceInstWithInst -->
2283 </div>
2285 <!--_______________________________________________________________________-->
2288 </div>
2292 <p>Deleting a global variable from a module is just as easy as deleting an
2293 Instruction. First, you must have a pointer to the global variable that you wish
2294 to delete. You use this pointer to erase it from its parent, the module.
2295 For example:</p>
2298 <pre>
2301 GV->eraseFromParent();
2302 </pre>
2303 </div>
2305 </div>
2307 <!-- ======================================================================= -->
2310 </div>
2314 <p>In generating IR, you may need some complex types. If you know these types
2317 has two forms depending on whether you're building types for cross-compilation
2320 out of types from
2322 namespace and pointers, functions, arrays, etc. built of
2324 whose size may depend on the host compiler. For example,</p>
2327 <pre>
2329 </pre>
2330 </div>
2335 <pre>
2337 params.push_back(PointerType::getUnqual(Type::Int32Ty));
2338 FunctionType *ft = FunctionType::get(Type::Int8Ty, params, false);
2339 </pre>
2340 </div>
2345 </div>
2347 <!-- *********************************************************************** -->
2350 </div>
2351 <!-- *********************************************************************** -->
2354 <p>
2355 This section describes the interaction of the LLVM APIs with multithreading,
2356 both on the part of client applications, and in the JIT, in the hosted
2357 application.
2358 </p>
2360 <p>
2361 Note that LLVM's support for multithreading is still relatively young. Up
2362 through version 2.5, the execution of threaded hosted applications was
2363 supported, but not threaded client access to the APIs. While this use case is
2365 ensure proper operation in multithreaded mode.
2366 </p>
2368 <p>
2369 Note that, on Unix-like platforms, LLVM requires the presence of GCC's atomic
2370 intrinsics in order to support threaded operation. If you need a
2371 multhreading-capable LLVM on a platform without a suitably modern system
2372 compiler, consider compiling LLVM and LLVM-GCC in single-threaded mode, and
2373 using the resultant compiler to build a copy of LLVM with multithreading
2374 support.
2375 </p>
2376 </div>
2378 <!-- ======================================================================= -->
2381 </div>
2385 <p>
2386 In order to properly protect its internal data structures while avoiding
2387 excessive locking overhead in the single-threaded case, the LLVM must intialize
2388 certain data structures necessary to provide guards around its internals. To do
2390 making any concurrent LLVM API calls. To subsequently tear down these
2393 mode.
2394 </p>
2396 <p>
2398 say that no other LLVM API calls may be executing at any time during the
2400 </tt>. It's is the client's responsibility to enforce this isolation.
2401 </p>
2403 <p>
2405 failure of the initialization. Failure typically indicates that your copy of
2406 LLVM was built without multithreading support, typically because GCC atomic
2407 intrinsics were not found in your system compiler. In this case, the LLVM API
2410 must be taken</a> to ensure that side exits and the like do not accidentally
2411 result in concurrent LLVM API calls.
2412 </p>
2413 </div>
2415 <!-- ======================================================================= -->
2418 </div>
2421 <p>
2423 to deallocate memory used for internal structures. This will also invoke
2427 </p>
2429 <p>
2430 Note that, if you use scope-based shutdown, you can use the
2432 destructor.
2433 </div>
2435 <!-- ======================================================================= -->
2438 </div>
2441 <p>
2443 initialization of static resources, such as the global type tables. Before the
2446 however, it uses double-checked locking to implement thread-safe lazy
2447 initialization.
2448 </p>
2450 <p>
2451 Note that, because no other threads are allowed to issue LLVM API calls before
2454 </p>
2456 <p>
2458 APIs provide access to the global lock used to implement the double-checked
2459 locking for lazy initialization. These should only be used internally to LLVM,
2460 and only if you know what you're doing!
2461 </p>
2462 </div>
2464 <!-- ======================================================================= -->
2467 </div>
2470 <p>
2472 to operate multiple, isolated instances of LLVM concurrently within the same
2473 address space. For instance, in a hypothetical compile-server, the compilation
2474 of an individual translation unit is conceptually independent from all the
2475 others, and it would be desirable to be able to compile incoming translation
2476 units concurrently on independent server threads. Fortunately,
2478 </p>
2480 <p>
2487 safe to compile on multiple threads simultaneously, as long as no two threads
2488 operate on entities within the same context.
2489 </p>
2491 <p>
2492 In practice, very few places in the API require the explicit specification of a
2495 other entities can determine what context they belong to by looking at their
2497 maintain this interface design.
2498 </p>
2500 <p>
2504 isolation is not a concern.
2505 </p>
2506 </div>
2508 <!-- ======================================================================= -->
2511 </div>
2514 <p>
2515 LLVM's "eager" JIT compiler is safe to use in threaded programs. Multiple
2518 run code output by the JIT concurrently. The user must still ensure that only
2520 might be modifying it. One way to do that is to always hold the JIT lock while
2524 </p>
2526 <p>When the JIT is configured to compile lazily (using
2529 updating call sites after a function is lazily-jitted. It's still possible to
2530 use the lazy JIT in a threaded program if you ensure that only one thread at a
2531 time can call any particular lazy stub and that the JIT lock guards any IR
2532 access, but we suggest using only the eager JIT in threaded programs.
2533 </p>
2534 </div>
2536 <!-- *********************************************************************** -->
2539 </div>
2540 <!-- *********************************************************************** -->
2543 <p>
2544 This section describes some of the advanced or obscure API's that most clients
2545 do not need to be aware of. These API's tend manage the inner workings of the
2546 LLVM system, and only need to be accessed in unusual circumstances.
2547 </p>
2548 </div>
2550 <!-- ======================================================================= -->
2553 </div>
2557 <p>
2558 The LLVM type system has a very simple goal: allow clients to compare types for
2559 structural equality with a simple pointer comparison (aka a shallow compare).
2560 This goal makes clients much simpler and faster, and is used throughout the LLVM
2561 system.
2562 </p>
2564 <p>
2565 Unfortunately achieving this goal is not a simple matter. In particular,
2566 recursive types and late resolution of opaque types makes the situation very
2567 difficult to handle. Fortunately, for the most part, our implementation makes
2568 most clients able to be completely unaware of the nasty internal details. The
2569 primary case where clients are exposed to the inner workings of it are when
2570 building a recursive type. In addition to this case, the LLVM bitcode reader,
2571 assembly parser, and linker also have to be aware of the inner workings of this
2572 system.
2573 </p>
2575 <p>
2576 For our purposes below, we need three concepts. First, an "Opaque Type" is
2579 opaque type as part of its type graph (for example "<tt>{ opaque, i32 }</tt>").
2580 Third, a concrete type is a type that is not an abstract type (e.g. "<tt>{ i32,
2581 float }</tt>").
2582 </p>
2584 </div>
2586 <!-- ______________________________________________________________________ -->
2589 </div>
2593 <p>
2594 Because the most common question is "how do I build a recursive type with LLVM",
2595 we answer it now and explain it as we go. Here we include enough to cause this
2596 to be emitted to an output .ll file:
2597 </p>
2600 <pre>
2601 %mylist = type { %mylist*, i32 }
2602 </pre>
2603 </div>
2605 <p>
2606 To build this, use the following LLVM APIs:
2607 </p>
2610 <pre>
2614 Elts.push_back(PointerType::getUnqual(StructTy));
2615 Elts.push_back(Type::Int32Ty);
2616 StructType *NewSTy = StructType::get(Elts);
2620 cast<OpaqueType>(StructTy.get())-><a href="#refineAbstractTypeTo">refineAbstractTypeTo</a>(NewSTy);
2622 // <i>NewSTy is potentially invalidated, but StructTy (a <a href="#PATypeHolder">PATypeHolder</a>) is</i>
2628 </pre>
2629 </div>
2631 <p>
2632 This code shows the basic approach used to build recursive types: build a
2633 non-recursive type using 'opaque', then use type unification to close the cycle.
2634 The type unification step is performed by the <tt><a
2636 described next. After that, we describe the <a
2638 </p>
2640 </div>
2642 <!-- ______________________________________________________________________ -->
2645 </div>
2648 <p>
2650 While this method is actually a member of the DerivedType class, it is most
2651 often used on OpaqueType instances. Type unification is actually a recursive
2652 process. After unification, types can become structurally isomorphic to
2653 existing types, and all duplicates are deleted (to preserve pointer equality).
2654 </p>
2656 <p>
2657 In the example above, the OpaqueType object is definitely deleted.
2658 Additionally, if there is an "{ \2*, i32}" type already created in the system,
2660 a type is deleted, any "Type*" pointers in the program are invalidated. As
2663 types can never move or be deleted). To deal with this, the <a
2665 reference to a possibly refined type, and the <a
2667 complex datastructures.
2668 </p>
2670 </div>
2672 <!-- ______________________________________________________________________ -->
2675 </div>
2678 <p>
2679 PATypeHolder is a form of a "smart pointer" for Type objects. When VMCore
2680 happily goes about nuking types that become isomorphic to existing types, it
2681 automatically updates all PATypeHolder objects to point to the new type. In the
2682 example above, this allows the code to maintain a pointer to the resultant
2683 resolved recursive type, even though the Type*'s are potentially invalidated.
2684 </p>
2686 <p>
2687 PATypeHolder is an extremely light-weight object that uses a lazy union-find
2688 implementation to update pointers. For example the pointer from a Value to its
2689 Type is maintained by PATypeHolder objects.
2690 </p>
2692 </div>
2694 <!-- ______________________________________________________________________ -->
2697 </div>
2701 <p>
2702 Some data structures need more to perform more complex updates when types get
2703 resolved. To support this, a class can derive from the AbstractTypeUser class.
2704 This class
2705 allows it to get callbacks when certain types are resolved. To register to get
2706 callbacks for a particular type, the DerivedType::{add/remove}AbstractTypeUser
2707 methods can be called on a type. Note that these methods only work for <i>
2708 abstract</i> types. Concrete types (those that do not include any opaque
2709 objects) can never be refined.
2710 </p>
2711 </div>
2714 <!-- ======================================================================= -->
2718 </div>
2728 names for types.</p>
2731 by most clients. It should only be used when iteration over the symbol table
2732 names themselves are required, which is very special purpose. Note that not
2733 all LLVM
2735 an empty name) do not exist in the symbol table.
2736 </p>
2738 <p>These symbol tables support iteration over the values/types in the symbol
2743 appropriate symbol table. For types, use the Module::addTypeName method to
2744 insert entries into the symbol table.</p>
2746 </div>
2750 <!-- ======================================================================= -->
2753 </div>
2761 addition and removal.</p>
2763 <!-- ______________________________________________________________________ -->
2765 <a name="Use2User">Interaction and relationship between <tt>User</tt> and <tt>Use</tt> objects</a>
2766 </div>
2769 <p>
2771 or refer to them out-of-line by means of a pointer. A mixed variant
2774 </p>
2775 </div>
2777 <p>
2779 <ul>
2780 <li><p>Layout a)
2782 object and there are a fixed number of them.</p>
2784 <li><p>Layout b)
2787 number of them.</p>
2788 </ul>
2789 <p>
2790 As of v2.4 each layout still possesses a direct pointer to the
2792 we stick to this redundancy for the sake of simplicity.
2794 has. (Theoretically this information can also be calculated
2795 given the scheme presented below.)</p>
2796 <p>
2798 enforce the following memory layouts:</p>
2800 <ul>
2801 <li><p>Layout a) is modelled by prepending the <tt>User</tt> object by the <tt>Use[]</tt> array.</p>
2803 <pre>
2804 ...---.---.---.---.-------...
2805 | P | P | P | P | User
2806 '''---'---'---'---'-------'''
2807 </pre>
2810 <pre>
2811 .-------...
2812 | User
2813 '-------'''
2814 |
2815 v
2816 .---.---.---.---...
2817 | P | P | P | P |
2818 '---'---'---'---'''
2819 </pre>
2820 </ul>
2824 <!-- ______________________________________________________________________ -->
2827 </div>
2830 <p>
2833 recover it. This is accomplished by the following scheme:</p>
2834 </div>
2836 A bit-encoding in the 2 LSBits (least significant bits) of the <tt>Use::Prev</tt> allows to find the
2838 <ul>
2843 </ul>
2844 <p>
2847 we have to walk to the next stop picking up digits
2848 and calculating the offset:</p>
2849 <pre>
2850 .---.---.---.---.---.---.---.---.---.---.---.---.---.---.---.---.----------------
2852 '---'---'---'---'---'---'---'---'---'---'---'---'---'---'---'---'----------------
2854 | | | | |__>
2855 | | | |__________>
2856 | | |______________________>
2857 | |______________________________________>
2858 |__________________________________________________________>
2859 </pre>
2860 <p>
2861 Only the significant number of bits need to be stored between the
2865 <!-- ______________________________________________________________________ -->
2868 </div>
2871 <p>
2872 The following literate Haskell fragment demonstrates the concept:</p>
2873 </div>
2876 <pre>
2877 > import Test.QuickCheck
2878 >
2883 >
2889 >
2890 > takeLast n ss = reverse $ take n $ reverse ss
2891 >
2893 >
2894 </pre>
2895 </div>
2896 <p>
2898 <p>
2899 The reverse algorithm computes the length of the string just by examining
2900 a certain prefix:</p>
2903 <pre>
2908 >
2911 > decode walk acc _ = walk + acc
2912 >
2913 </pre>
2914 </div>
2915 <p>
2917 <p>
2921 <pre>
2923 > testcaseLength = length testcase
2924 >
2926 > where arr = takeLast n testcase
2927 >
2928 </pre>
2929 </div>
2930 <p>
2933 <pre>
2934 *Main> quickCheck identityProp
2935 OK, passed 100 tests.
2936 </pre>
2937 <p>
2938 Let's be a bit more exhaustive:</p>
2941 <pre>
2942 >
2944 >
2945 </pre>
2946 </div>
2947 <p>
2950 <pre>
2951 *Main> deepCheck identityProp
2952 OK, passed 500 tests.
2953 </pre>
2955 <!-- ______________________________________________________________________ -->
2958 </div>
2960 <p>
2964 tag bits.</p>
2965 <p>
2969 the LSBit set. (Portability is relying on the fact that all known compilers place the
2972 </div>
2974 <!-- *********************************************************************** -->
2977 </div>
2978 <!-- *********************************************************************** -->
2984 <p>The Core LLVM classes are the primary means of representing the program
2985 being inspected or transformed. The core LLVM classes are defined in
2989 </div>
2991 <!-- ======================================================================= -->
2994 </div>
3002 subclasses. They are hidden because they offer no useful functionality beyond
3006 named, but this is not a requirement. There exists exactly
3007 one instance of a given shape at any one time. This allows type equality to
3008 be performed with address equality of the Type Instance. That is, given two
3010 </p>
3011 </div>
3013 <!-- _______________________________________________________________________ -->
3016 </div>
3020 <ul>
3024 floating point types.</li>
3027 an OpaqueType anywhere in its definition).</li>
3030 that don't have a size are abstract types, labels and void.</li>
3032 </ul>
3033 </div>
3035 <!-- _______________________________________________________________________ -->
3038 </div>
3040 <dl>
3042 <dd>Subclass of DerivedType that represents integer types of any bit width.
3045 <ul>
3047 type of a specific bit width.</li>
3049 type.</li>
3050 </ul>
3051 </dd>
3053 <dd>This is subclassed by ArrayType and PointerType
3054 <ul>
3056 of the elements in the sequential type. </li>
3057 </ul>
3058 </dd>
3060 <dd>This is a subclass of SequentialType and defines the interface for array
3061 types.
3062 <ul>
3064 elements in the array. </li>
3065 </ul>
3066 </dd>
3070 <dd>Subclass of SequentialType for vector types. A
3071 vector type is similar to an ArrayType but is distinguished because it is
3072 a first class type whereas ArrayType is not. Vector types are used for
3073 vector operations and are usually small vectors of of an integer or floating
3074 point type.</dd>
3078 <dd>Subclass of DerivedTypes for function types.
3079 <ul>
3081 function</li>
3083 return type of the function.</li>
3085 the type of the ith parameter.</li>
3087 number of formal parameters.</li>
3088 </ul>
3089 </dd>
3091 <dd>Sublcass of DerivedType for abstract types. This class
3092 defines no content and is used as a placeholder for some other type. Note
3093 that OpaqueType is used (temporarily) during type resolution for forward
3094 references of types. Once the referenced type is resolved, the OpaqueType
3095 is replaced with the actual type. OpaqueType can also be used for data
3096 abstraction. At link time opaque types can be resolved to actual types
3097 of the same name.</dd>
3098 </dl>
3099 </div>
3103 <!-- ======================================================================= -->
3106 </div>
3115 programs. An LLVM module is effectively either a translation unit of the
3116 original program or a combination of several translation units merged by the
3121 helpful member functions that try to make common operations easy.</p>
3123 </div>
3125 <!-- _______________________________________________________________________ -->
3128 </div>
3132 <ul>
3134 </ul>
3137 provide a name for it (probably based on the name of the translation unit).</p>
3139 <ul>
3146 <p>These are forwarding methods that make it easy to access the contents of
3148 list.</p></li>
3153 necessary to use when you need to update the list or perform a complex
3154 action that doesn't have a forwarding method.</p>
3157 </ul>
3159 <hr>
3161 <ul>
3169 <p> These are forwarding methods that make it easy to access the contents of
3177 use when you need to update the list or perform a complex action that
3178 doesn't have a forwarding method.</p>
3181 </ul>
3183 <hr>
3185 <ul>
3192 </ul>
3194 <hr>
3196 <ul>
3209 external declaration for the function and return it.</p></li>
3216 string.</p></li>
3223 name, true is returned and the <a
3225 </ul>
3227 </div>
3230 <!-- ======================================================================= -->
3233 </div>
3238 <br>
3242 base. It represents a typed value that may be used (among other things) as an
3250 for a program. For example, an incoming argument to a function (represented
3252 every instruction in the function that references the argument. To keep track
3258 methods, shown below.</p>
3262 method. In addition, all LLVM values can be named. The "name" of the
3266 <pre>
3268 </pre>
3269 </div>
3272 that the name of any value may be missing (an empty string), so names should
3274 debugging printouts), they should not be used to keep track of values or map
3278 <p>One important aspect of LLVM is that there is no distinction between an SSA
3279 variable and the operation that produces it. Because of this, any reference to
3280 the value produced by an instruction (or the value available as an incoming
3281 argument, for example) is represented as a direct pointer to the instance of
3282 the class that
3283 represents this value. Although this may take some getting used to, it
3284 simplifies the representation and makes it easier to manipulate.</p>
3286 </div>
3288 <!-- _______________________________________________________________________ -->
3291 </div>
3295 <ul>
3297 use-list<br>
3299 the use-list<br>
3301 value.<br>
3304 the use-list.<br>
3306 use-list.<br>
3308 element in the list.
3309 <p> These methods are the interface to access the def-use
3310 information in LLVM. As with all other iterators in LLVM, the naming
3312 </li>
3315 </li>
3321 </li>
3326 "<tt>V</tt>" instead. For example, if you detect that an instruction always
3327 produces a constant value (for example through constant folding), you can
3328 replace all uses of the instruction with the constant like this:</p>
3331 <pre>
3332 Inst->replaceAllUsesWith(ConstVal);
3333 </pre>
3334 </div>
3336 </ul>
3338 </div>
3340 <!-- ======================================================================= -->
3343 </div>
3347 <p>
3360 Single Assignment (SSA) form, there can only be one definition referred to,
3361 allowing this direct connection. This connection provides the use-def
3362 information in LLVM.</p>
3364 </div>
3366 <!-- _______________________________________________________________________ -->
3369 </div>
3374 an index access interface and through an iterator based interface.</p>
3376 <ul>
3380 convenient form for direct access.</p></li>
3383 list<br>
3385 the operand list.<br>
3387 operand list.
3388 <p> Together, these methods make up the iterator based interface to
3390 </ul>
3392 </div>
3394 <!-- ======================================================================= -->
3397 </div>
3408 instructions. It provides only a few methods, but is a very commonly used
3410 opcode (instruction type) and the parent <a
3412 into. To represent a specific type of instruction, one of many subclasses of
3421 file contains some meta-data about the various different types of instructions
3422 in LLVM. It describes the enum values that are used as opcodes (for example
3427 this file confuses doxygen, so these enum values don't show up correctly in the
3430 </div>
3432 <!-- _______________________________________________________________________ -->
3435 class</a>
3436 </div>
3438 <ul>
3440 <p>This subclasses represents all two operand instructions whose operands
3441 must be the same type, except for the comparison instructions.</p></li>
3444 common operations on cast instructions.</p>
3446 <p>This subclass respresents the two comparison instructions,
3450 <p>This subclass is the parent of all terminator instructions (those which
3451 can terminate a block).</p>
3452 </ul>
3453 </div>
3455 <!-- _______________________________________________________________________ -->
3458 class</a>
3459 </div>
3463 <ul>
3468 <p>Returns true if the instruction writes to memory, i.e. it is a
3473 <p>Returns another instance of the specified instruction, identical
3474 in all ways to the original except that the instruction has no parent
3476 and it has no name</p></li>
3477 </ul>
3479 </div>
3481 <!-- ======================================================================= -->
3484 </div>
3488 <p>Constant represents a base class for different types of constants. It
3489 is subclassed by ConstantInt, ConstantArray, etc. for representing
3491 a subclass, which represents the address of a global variable or function.
3492 </p>
3494 </div>
3496 <!-- _______________________________________________________________________ -->
3499 <ul>
3500 <li>ConstantInt : This subclass of Constant represents an integer constant of
3501 any width.
3502 <ul>
3504 value of this constant, an APInt value.</li>
3506 value to an int64_t via sign extension. If the value (not the bit width)
3507 of the APInt is too large to fit in an int64_t, an assertion will result.
3508 For this reason, use of this method is discouraged.</li>
3510 value to a uint64_t via zero extension. IF the value (not the bit width)
3511 of the APInt is too large to fit in a uint64_t, an assertion will result.
3512 For this reason, use of this method is discouraged.</li>
3515 The type is implied as the IntegerType that corresponds to the bit width
3518 Returns the ConstantInt object that represents the value provided by
3520 </ul>
3521 </li>
3522 <li>ConstantFP : This class represents a floating point constant.
3523 <ul>
3525 this constant. </li>
3526 </ul>
3527 </li>
3528 <li>ConstantArray : This represents a constant array.
3529 <ul>
3531 a vector of component constants that makeup this array. </li>
3532 </ul>
3533 </li>
3534 <li>ConstantStruct : This represents a constant struct.
3535 <ul>
3537 a vector of component constants that makeup this array. </li>
3538 </ul>
3539 </li>
3540 <li>GlobalValue : This represents either a global variable or a function. In
3541 either case, the value is a constant fixed address (after linking).
3542 </li>
3543 </ul>
3544 </div>
3547 <!-- ======================================================================= -->
3550 </div>
3557 Class</a><br>
3564 Because they are visible at global scope, they are also subject to linking with
3565 other globals defined in different translation units. To control the linking
3572 unit, and does not participate in linking. If it has external linkage, it is
3573 visible to external code, and does participate in linking. In addition to
3579 global is always a pointer to its contents. It is important to remember this
3584 the address of the first element of this array and the value of the
3592 </div>
3594 <!-- _______________________________________________________________________ -->
3597 class</a>
3598 </div>
3602 <ul>
3607 <p> </p>
3608 </li>
3611 GlobalValue is currently embedded into.</p></li>
3612 </ul>
3614 </div>
3616 <!-- ======================================================================= -->
3619 </div>
3632 actually one of the more complex classes in the LLVM hierarchy because it must
3640 ordering of the blocks in the function, which indicate how the code will be
3641 laid out by the backend. Additionally, the first <a
3644 block. There are no implicit exit nodes, and in fact there may be multiple exit
3648 function hasn't been linked in yet.</p>
3658 LLVM feature that is only used when you have to look up a value by name. Aside
3660 internally to make sure that there are not conflicts between the names of <a
3667 is its address (after linking) which is guaranteed to be constant.</p>
3668 </div>
3670 <!-- _______________________________________________________________________ -->
3673 class</a>
3674 </div>
3678 <ul>
3683 the the program. The constructor must specify the type of the function to
3684 create and what type of linkage the function should have. The <a
3686 specifies the formal arguments and return value for the function. The same
3689 in which the function is defined. If this argument is provided, the function
3690 will automatically be inserted into that module's list of
3691 functions.</p></li>
3696 function is "external", it does not have a body, and thus must be resolved
3697 by linking with a function defined in a different translation unit.</p></li>
3705 <p>These are forwarding methods that make it easy to access the contents of
3707 list.</p></li>
3712 is necessary to use when you need to update the list or perform a complex
3713 action that doesn't have a forwarding method.</p></li>
3716 iterator<br>
3722 <p>These are forwarding methods that make it easy to access the contents of
3724 list.</p></li>
3729 necessary to use when you need to update the list or perform a complex
3730 action that doesn't have a forwarding method.</p></li>
3735 function. Because the entry block for the function is always the first
3744 function.</p></li>
3750 </ul>
3752 </div>
3754 <!-- ======================================================================= -->
3757 </div>
3763 <br>
3765 Class</a><br>
3771 <p>Global variables are represented with the (surprise surprise)
3774 always referenced by their address (global values must live in memory, so their
3775 "name" refers to their constant address). See
3777 variables may have an initial value (which must be a
3779 they may be marked as "constant" themselves (indicating that their contents
3780 never change at runtime).</p>
3781 </div>
3783 <!-- _______________________________________________________________________ -->
3787 </div>
3791 <ul>
3796 <p>Create a new global variable of the specified type. If
3798 unchanging for the program. The Linkage parameter specifies the type of
3799 linkage (internal, external, weak, linkonce, appending) for the variable.
3800 If the linkage is InternalLinkage, WeakAnyLinkage, WeakODRLinkage,
3801 LinkOnceAnyLinkage or LinkOnceODRLinkage, then the resultant
3802 global variable will have internal linkage. AppendingLinkage concatenates
3803 together all instances (in different translation units) of the variable
3804 into a single variable but is only applicable to arrays. See
3806 further details on linkage types. Optionally an initializer, a name, and the
3807 module to put the variable into may be specified for the global variable as
3808 well.</p></li>
3812 <p>Returns true if this is a global variable that is known not to
3813 be modified at runtime.</p></li>
3822 to call this method if there is no initializer.</p></li>
3823 </ul>
3825 </div>
3828 <!-- ======================================================================= -->
3831 </div>
3838 Class</a><br>
3841 <p>This class represents a single entry multiple exit section of the code,
3842 commonly known as a basic block by the compiler community. The
3845 Matching the language definition, the last element of this list of instructions
3846 is always a terminator instruction (a subclass of the <a
3849 <p>In addition to tracking the list of instructions that make up the block, the
3858 </div>
3860 <!-- _______________________________________________________________________ -->
3863 class</a>
3864 </div>
3867 <ul>
3873 insertion into a function. The constructor optionally takes a name for the new
3876 automatically inserted at the end of the specified <a
3884 STL-style functions for accessing the instruction list.
3886 <p>These methods and typedefs are forwarding functions that have the same
3887 semantics as the standard library methods of the same names. These methods
3888 expose the underlying instruction list of a basic block in a way that is easy to
3889 manipulate. To get the full complement of container operations (including
3891 method.</p></li>
3895 <p>This method is used to get access to the underlying container that actually
3896 holds the Instructions. This method must be used when there isn't a forwarding
3898 to perform. Because there are no forwarding functions for "updating"
3899 operations, you need to use this if you want to update the contents of a
3905 embedded into, or a null pointer if it is homeless.</p></li>
3909 <p> Returns a pointer to the terminator instruction that appears at the end of
3911 instruction in the block is not a terminator, then a null pointer is
3912 returned.</p></li>
3914 </ul>
3916 </div>
3919 <!-- ======================================================================= -->
3922 </div>
3926 <p>This subclass of Value defines the interface for incoming formal
3927 arguments to a function. A Function maintains a list of its formal
3928 arguments. An argument has a pointer to the parent Function.</p>
3930 </div>
3932 <!-- *********************************************************************** -->
3933 <hr>
3934 <address>
3943 Last modified: $Date$
3944 </address>
3946 </body>
3947 </html>