1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
2 "http://www.w3.org/TR/html4/strict.dtd">
5 <title>LLVM Assembly Language Reference Manual</title>
6 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
7 <meta name="author" content="Chris Lattner">
8 <meta name="description"
9 content="LLVM Assembly Language Reference Manual.">
10 <link rel="stylesheet" href="llvm.css" type="text/css">
15 <div class="doc_title"> LLVM Language Reference Manual </div>
17 <li><a href="#abstract">Abstract</a></li>
18 <li><a href="#introduction">Introduction</a></li>
19 <li><a href="#identifiers">Identifiers</a></li>
20 <li><a href="#highlevel">High Level Structure</a>
22 <li><a href="#modulestructure">Module Structure</a></li>
23 <li><a href="#linkage">Linkage Types</a></li>
24 <li><a href="#callingconv">Calling Conventions</a></li>
25 <li><a href="#globalvars">Global Variables</a></li>
26 <li><a href="#functionstructure">Functions</a></li>
27 <li><a href="#aliasstructure">Aliases</a>
28 <li><a href="#paramattrs">Parameter Attributes</a></li>
29 <li><a href="#gc">Garbage Collector Names</a></li>
30 <li><a href="#moduleasm">Module-Level Inline Assembly</a></li>
31 <li><a href="#datalayout">Data Layout</a></li>
34 <li><a href="#typesystem">Type System</a>
36 <li><a href="#t_classifications">Type Classifications</a></li>
37 <li><a href="#t_primitive">Primitive Types</a>
39 <li><a href="#t_floating">Floating Point Types</a></li>
40 <li><a href="#t_void">Void Type</a></li>
41 <li><a href="#t_label">Label Type</a></li>
44 <li><a href="#t_derived">Derived Types</a>
46 <li><a href="#t_integer">Integer Type</a></li>
47 <li><a href="#t_array">Array Type</a></li>
48 <li><a href="#t_function">Function Type</a></li>
49 <li><a href="#t_pointer">Pointer Type</a></li>
50 <li><a href="#t_struct">Structure Type</a></li>
51 <li><a href="#t_pstruct">Packed Structure Type</a></li>
52 <li><a href="#t_vector">Vector Type</a></li>
53 <li><a href="#t_opaque">Opaque Type</a></li>
58 <li><a href="#constants">Constants</a>
60 <li><a href="#simpleconstants">Simple Constants</a>
61 <li><a href="#aggregateconstants">Aggregate Constants</a>
62 <li><a href="#globalconstants">Global Variable and Function Addresses</a>
63 <li><a href="#undefvalues">Undefined Values</a>
64 <li><a href="#constantexprs">Constant Expressions</a>
67 <li><a href="#othervalues">Other Values</a>
69 <li><a href="#inlineasm">Inline Assembler Expressions</a>
72 <li><a href="#instref">Instruction Reference</a>
74 <li><a href="#terminators">Terminator Instructions</a>
76 <li><a href="#i_ret">'<tt>ret</tt>' Instruction</a></li>
77 <li><a href="#i_br">'<tt>br</tt>' Instruction</a></li>
78 <li><a href="#i_switch">'<tt>switch</tt>' Instruction</a></li>
79 <li><a href="#i_invoke">'<tt>invoke</tt>' Instruction</a></li>
80 <li><a href="#i_unwind">'<tt>unwind</tt>' Instruction</a></li>
81 <li><a href="#i_unreachable">'<tt>unreachable</tt>' Instruction</a></li>
84 <li><a href="#binaryops">Binary Operations</a>
86 <li><a href="#i_add">'<tt>add</tt>' Instruction</a></li>
87 <li><a href="#i_sub">'<tt>sub</tt>' Instruction</a></li>
88 <li><a href="#i_mul">'<tt>mul</tt>' Instruction</a></li>
89 <li><a href="#i_udiv">'<tt>udiv</tt>' Instruction</a></li>
90 <li><a href="#i_sdiv">'<tt>sdiv</tt>' Instruction</a></li>
91 <li><a href="#i_fdiv">'<tt>fdiv</tt>' Instruction</a></li>
92 <li><a href="#i_urem">'<tt>urem</tt>' Instruction</a></li>
93 <li><a href="#i_srem">'<tt>srem</tt>' Instruction</a></li>
94 <li><a href="#i_frem">'<tt>frem</tt>' Instruction</a></li>
97 <li><a href="#bitwiseops">Bitwise Binary Operations</a>
99 <li><a href="#i_shl">'<tt>shl</tt>' Instruction</a></li>
100 <li><a href="#i_lshr">'<tt>lshr</tt>' Instruction</a></li>
101 <li><a href="#i_ashr">'<tt>ashr</tt>' Instruction</a></li>
102 <li><a href="#i_and">'<tt>and</tt>' Instruction</a></li>
103 <li><a href="#i_or">'<tt>or</tt>' Instruction</a></li>
104 <li><a href="#i_xor">'<tt>xor</tt>' Instruction</a></li>
107 <li><a href="#vectorops">Vector Operations</a>
109 <li><a href="#i_extractelement">'<tt>extractelement</tt>' Instruction</a></li>
110 <li><a href="#i_insertelement">'<tt>insertelement</tt>' Instruction</a></li>
111 <li><a href="#i_shufflevector">'<tt>shufflevector</tt>' Instruction</a></li>
114 <li><a href="#memoryops">Memory Access and Addressing Operations</a>
116 <li><a href="#i_malloc">'<tt>malloc</tt>' Instruction</a></li>
117 <li><a href="#i_free">'<tt>free</tt>' Instruction</a></li>
118 <li><a href="#i_alloca">'<tt>alloca</tt>' Instruction</a></li>
119 <li><a href="#i_load">'<tt>load</tt>' Instruction</a></li>
120 <li><a href="#i_store">'<tt>store</tt>' Instruction</a></li>
121 <li><a href="#i_getelementptr">'<tt>getelementptr</tt>' Instruction</a></li>
124 <li><a href="#convertops">Conversion Operations</a>
126 <li><a href="#i_trunc">'<tt>trunc .. to</tt>' Instruction</a></li>
127 <li><a href="#i_zext">'<tt>zext .. to</tt>' Instruction</a></li>
128 <li><a href="#i_sext">'<tt>sext .. to</tt>' Instruction</a></li>
129 <li><a href="#i_fptrunc">'<tt>fptrunc .. to</tt>' Instruction</a></li>
130 <li><a href="#i_fpext">'<tt>fpext .. to</tt>' Instruction</a></li>
131 <li><a href="#i_fptoui">'<tt>fptoui .. to</tt>' Instruction</a></li>
132 <li><a href="#i_fptosi">'<tt>fptosi .. to</tt>' Instruction</a></li>
133 <li><a href="#i_uitofp">'<tt>uitofp .. to</tt>' Instruction</a></li>
134 <li><a href="#i_sitofp">'<tt>sitofp .. to</tt>' Instruction</a></li>
135 <li><a href="#i_ptrtoint">'<tt>ptrtoint .. to</tt>' Instruction</a></li>
136 <li><a href="#i_inttoptr">'<tt>inttoptr .. to</tt>' Instruction</a></li>
137 <li><a href="#i_bitcast">'<tt>bitcast .. to</tt>' Instruction</a></li>
139 <li><a href="#otherops">Other Operations</a>
141 <li><a href="#i_icmp">'<tt>icmp</tt>' Instruction</a></li>
142 <li><a href="#i_fcmp">'<tt>fcmp</tt>' Instruction</a></li>
143 <li><a href="#i_phi">'<tt>phi</tt>' Instruction</a></li>
144 <li><a href="#i_select">'<tt>select</tt>' Instruction</a></li>
145 <li><a href="#i_call">'<tt>call</tt>' Instruction</a></li>
146 <li><a href="#i_va_arg">'<tt>va_arg</tt>' Instruction</a></li>
151 <li><a href="#intrinsics">Intrinsic Functions</a>
153 <li><a href="#int_varargs">Variable Argument Handling Intrinsics</a>
155 <li><a href="#int_va_start">'<tt>llvm.va_start</tt>' Intrinsic</a></li>
156 <li><a href="#int_va_end">'<tt>llvm.va_end</tt>' Intrinsic</a></li>
157 <li><a href="#int_va_copy">'<tt>llvm.va_copy</tt>' Intrinsic</a></li>
160 <li><a href="#int_gc">Accurate Garbage Collection Intrinsics</a>
162 <li><a href="#int_gcroot">'<tt>llvm.gcroot</tt>' Intrinsic</a></li>
163 <li><a href="#int_gcread">'<tt>llvm.gcread</tt>' Intrinsic</a></li>
164 <li><a href="#int_gcwrite">'<tt>llvm.gcwrite</tt>' Intrinsic</a></li>
167 <li><a href="#int_codegen">Code Generator Intrinsics</a>
169 <li><a href="#int_returnaddress">'<tt>llvm.returnaddress</tt>' Intrinsic</a></li>
170 <li><a href="#int_frameaddress">'<tt>llvm.frameaddress</tt>' Intrinsic</a></li>
171 <li><a href="#int_stacksave">'<tt>llvm.stacksave</tt>' Intrinsic</a></li>
172 <li><a href="#int_stackrestore">'<tt>llvm.stackrestore</tt>' Intrinsic</a></li>
173 <li><a href="#int_prefetch">'<tt>llvm.prefetch</tt>' Intrinsic</a></li>
174 <li><a href="#int_pcmarker">'<tt>llvm.pcmarker</tt>' Intrinsic</a></li>
175 <li><a href="#int_readcyclecounter"><tt>llvm.readcyclecounter</tt>' Intrinsic</a></li>
178 <li><a href="#int_libc">Standard C Library Intrinsics</a>
180 <li><a href="#int_memcpy">'<tt>llvm.memcpy.*</tt>' Intrinsic</a></li>
181 <li><a href="#int_memmove">'<tt>llvm.memmove.*</tt>' Intrinsic</a></li>
182 <li><a href="#int_memset">'<tt>llvm.memset.*</tt>' Intrinsic</a></li>
183 <li><a href="#int_sqrt">'<tt>llvm.sqrt.*</tt>' Intrinsic</a></li>
184 <li><a href="#int_powi">'<tt>llvm.powi.*</tt>' Intrinsic</a></li>
185 <li><a href="#int_sin">'<tt>llvm.sin.*</tt>' Intrinsic</a></li>
186 <li><a href="#int_cos">'<tt>llvm.cos.*</tt>' Intrinsic</a></li>
187 <li><a href="#int_pow">'<tt>llvm.pow.*</tt>' Intrinsic</a></li>
190 <li><a href="#int_manip">Bit Manipulation Intrinsics</a>
192 <li><a href="#int_bswap">'<tt>llvm.bswap.*</tt>' Intrinsics</a></li>
193 <li><a href="#int_ctpop">'<tt>llvm.ctpop.*</tt>' Intrinsic </a></li>
194 <li><a href="#int_ctlz">'<tt>llvm.ctlz.*</tt>' Intrinsic </a></li>
195 <li><a href="#int_cttz">'<tt>llvm.cttz.*</tt>' Intrinsic </a></li>
196 <li><a href="#int_part_select">'<tt>llvm.part.select.*</tt>' Intrinsic </a></li>
197 <li><a href="#int_part_set">'<tt>llvm.part.set.*</tt>' Intrinsic </a></li>
200 <li><a href="#int_debugger">Debugger intrinsics</a></li>
201 <li><a href="#int_eh">Exception Handling intrinsics</a></li>
202 <li><a href="#int_trampoline">Trampoline Intrinsic</a>
204 <li><a href="#int_it">'<tt>llvm.init.trampoline</tt>' Intrinsic</a></li>
207 <li><a href="#int_general">General intrinsics</a>
209 <li><a href="#int_var_annotation">
210 <tt>llvm.var.annotation</tt>' Intrinsic</a></li>
213 <li><a href="#int_annotation">
214 <tt>llvm.annotation.*</tt>' Intrinsic</a></li>
221 <div class="doc_author">
222 <p>Written by <a href="mailto:sabre@nondot.org">Chris Lattner</a>
223 and <a href="mailto:vadve@cs.uiuc.edu">Vikram Adve</a></p>
226 <!-- *********************************************************************** -->
227 <div class="doc_section"> <a name="abstract">Abstract </a></div>
228 <!-- *********************************************************************** -->
230 <div class="doc_text">
231 <p>This document is a reference manual for the LLVM assembly language.
232 LLVM is an SSA based representation that provides type safety,
233 low-level operations, flexibility, and the capability of representing
234 'all' high-level languages cleanly. It is the common code
235 representation used throughout all phases of the LLVM compilation
239 <!-- *********************************************************************** -->
240 <div class="doc_section"> <a name="introduction">Introduction</a> </div>
241 <!-- *********************************************************************** -->
243 <div class="doc_text">
245 <p>The LLVM code representation is designed to be used in three
246 different forms: as an in-memory compiler IR, as an on-disk bitcode
247 representation (suitable for fast loading by a Just-In-Time compiler),
248 and as a human readable assembly language representation. This allows
249 LLVM to provide a powerful intermediate representation for efficient
250 compiler transformations and analysis, while providing a natural means
251 to debug and visualize the transformations. The three different forms
252 of LLVM are all equivalent. This document describes the human readable
253 representation and notation.</p>
255 <p>The LLVM representation aims to be light-weight and low-level
256 while being expressive, typed, and extensible at the same time. It
257 aims to be a "universal IR" of sorts, by being at a low enough level
258 that high-level ideas may be cleanly mapped to it (similar to how
259 microprocessors are "universal IR's", allowing many source languages to
260 be mapped to them). By providing type information, LLVM can be used as
261 the target of optimizations: for example, through pointer analysis, it
262 can be proven that a C automatic variable is never accessed outside of
263 the current function... allowing it to be promoted to a simple SSA
264 value instead of a memory location.</p>
268 <!-- _______________________________________________________________________ -->
269 <div class="doc_subsubsection"> <a name="wellformed">Well-Formedness</a> </div>
271 <div class="doc_text">
273 <p>It is important to note that this document describes 'well formed'
274 LLVM assembly language. There is a difference between what the parser
275 accepts and what is considered 'well formed'. For example, the
276 following instruction is syntactically okay, but not well formed:</p>
278 <div class="doc_code">
280 %x = <a href="#i_add">add</a> i32 1, %x
284 <p>...because the definition of <tt>%x</tt> does not dominate all of
285 its uses. The LLVM infrastructure provides a verification pass that may
286 be used to verify that an LLVM module is well formed. This pass is
287 automatically run by the parser after parsing input assembly and by
288 the optimizer before it outputs bitcode. The violations pointed out
289 by the verifier pass indicate bugs in transformation passes or input to
293 <!-- Describe the typesetting conventions here. -->
295 <!-- *********************************************************************** -->
296 <div class="doc_section"> <a name="identifiers">Identifiers</a> </div>
297 <!-- *********************************************************************** -->
299 <div class="doc_text">
301 <p>LLVM identifiers come in two basic types: global and local. Global
302 identifiers (functions, global variables) begin with the @ character. Local
303 identifiers (register names, types) begin with the % character. Additionally,
304 there are three different formats for identifiers, for different purposes:
307 <li>Named values are represented as a string of characters with their prefix.
308 For example, %foo, @DivisionByZero, %a.really.long.identifier. The actual
309 regular expression used is '<tt>[%@][a-zA-Z$._][a-zA-Z$._0-9]*</tt>'.
310 Identifiers which require other characters in their names can be surrounded
311 with quotes. In this way, anything except a <tt>"</tt> character can
312 be used in a named value.</li>
314 <li>Unnamed values are represented as an unsigned numeric value with their
315 prefix. For example, %12, @2, %44.</li>
317 <li>Constants, which are described in a <a href="#constants">section about
318 constants</a>, below.</li>
321 <p>LLVM requires that values start with a prefix for two reasons: Compilers
322 don't need to worry about name clashes with reserved words, and the set of
323 reserved words may be expanded in the future without penalty. Additionally,
324 unnamed identifiers allow a compiler to quickly come up with a temporary
325 variable without having to avoid symbol table conflicts.</p>
327 <p>Reserved words in LLVM are very similar to reserved words in other
328 languages. There are keywords for different opcodes
329 ('<tt><a href="#i_add">add</a></tt>',
330 '<tt><a href="#i_bitcast">bitcast</a></tt>',
331 '<tt><a href="#i_ret">ret</a></tt>', etc...), for primitive type names ('<tt><a
332 href="#t_void">void</a></tt>', '<tt><a href="#t_primitive">i32</a></tt>', etc...),
333 and others. These reserved words cannot conflict with variable names, because
334 none of them start with a prefix character ('%' or '@').</p>
336 <p>Here is an example of LLVM code to multiply the integer variable
337 '<tt>%X</tt>' by 8:</p>
341 <div class="doc_code">
343 %result = <a href="#i_mul">mul</a> i32 %X, 8
347 <p>After strength reduction:</p>
349 <div class="doc_code">
351 %result = <a href="#i_shl">shl</a> i32 %X, i8 3
355 <p>And the hard way:</p>
357 <div class="doc_code">
359 <a href="#i_add">add</a> i32 %X, %X <i>; yields {i32}:%0</i>
360 <a href="#i_add">add</a> i32 %0, %0 <i>; yields {i32}:%1</i>
361 %result = <a href="#i_add">add</a> i32 %1, %1
365 <p>This last way of multiplying <tt>%X</tt> by 8 illustrates several
366 important lexical features of LLVM:</p>
370 <li>Comments are delimited with a '<tt>;</tt>' and go until the end of
373 <li>Unnamed temporaries are created when the result of a computation is not
374 assigned to a named value.</li>
376 <li>Unnamed temporaries are numbered sequentially</li>
380 <p>...and it also shows a convention that we follow in this document. When
381 demonstrating instructions, we will follow an instruction with a comment that
382 defines the type and name of value produced. Comments are shown in italic
387 <!-- *********************************************************************** -->
388 <div class="doc_section"> <a name="highlevel">High Level Structure</a> </div>
389 <!-- *********************************************************************** -->
391 <!-- ======================================================================= -->
392 <div class="doc_subsection"> <a name="modulestructure">Module Structure</a>
395 <div class="doc_text">
397 <p>LLVM programs are composed of "Module"s, each of which is a
398 translation unit of the input programs. Each module consists of
399 functions, global variables, and symbol table entries. Modules may be
400 combined together with the LLVM linker, which merges function (and
401 global variable) definitions, resolves forward declarations, and merges
402 symbol table entries. Here is an example of the "hello world" module:</p>
404 <div class="doc_code">
405 <pre><i>; Declare the string constant as a global constant...</i>
406 <a href="#identifiers">@.LC0</a> = <a href="#linkage_internal">internal</a> <a
407 href="#globalvars">constant</a> <a href="#t_array">[13 x i8]</a> c"hello world\0A\00" <i>; [13 x i8]*</i>
409 <i>; External declaration of the puts function</i>
410 <a href="#functionstructure">declare</a> i32 @puts(i8 *) <i>; i32(i8 *)* </i>
412 <i>; Definition of main function</i>
413 define i32 @main() { <i>; i32()* </i>
414 <i>; Convert [13x i8 ]* to i8 *...</i>
416 href="#i_getelementptr">getelementptr</a> [13 x i8 ]* @.LC0, i64 0, i64 0 <i>; i8 *</i>
418 <i>; Call puts function to write out the string to stdout...</i>
420 href="#i_call">call</a> i32 @puts(i8 * %cast210) <i>; i32</i>
422 href="#i_ret">ret</a> i32 0<br>}<br>
426 <p>This example is made up of a <a href="#globalvars">global variable</a>
427 named "<tt>.LC0</tt>", an external declaration of the "<tt>puts</tt>"
428 function, and a <a href="#functionstructure">function definition</a>
429 for "<tt>main</tt>".</p>
431 <p>In general, a module is made up of a list of global values,
432 where both functions and global variables are global values. Global values are
433 represented by a pointer to a memory location (in this case, a pointer to an
434 array of char, and a pointer to a function), and have one of the following <a
435 href="#linkage">linkage types</a>.</p>
439 <!-- ======================================================================= -->
440 <div class="doc_subsection">
441 <a name="linkage">Linkage Types</a>
444 <div class="doc_text">
447 All Global Variables and Functions have one of the following types of linkage:
452 <dt><tt><b><a name="linkage_internal">internal</a></b></tt> </dt>
454 <dd>Global values with internal linkage are only directly accessible by
455 objects in the current module. In particular, linking code into a module with
456 an internal global value may cause the internal to be renamed as necessary to
457 avoid collisions. Because the symbol is internal to the module, all
458 references can be updated. This corresponds to the notion of the
459 '<tt>static</tt>' keyword in C.
462 <dt><tt><b><a name="linkage_linkonce">linkonce</a></b></tt>: </dt>
464 <dd>Globals with "<tt>linkonce</tt>" linkage are merged with other globals of
465 the same name when linkage occurs. This is typically used to implement
466 inline functions, templates, or other code which must be generated in each
467 translation unit that uses it. Unreferenced <tt>linkonce</tt> globals are
468 allowed to be discarded.
471 <dt><tt><b><a name="linkage_weak">weak</a></b></tt>: </dt>
473 <dd>"<tt>weak</tt>" linkage is exactly the same as <tt>linkonce</tt> linkage,
474 except that unreferenced <tt>weak</tt> globals may not be discarded. This is
475 used for globals that may be emitted in multiple translation units, but that
476 are not guaranteed to be emitted into every translation unit that uses them.
477 One example of this are common globals in C, such as "<tt>int X;</tt>" at
481 <dt><tt><b><a name="linkage_appending">appending</a></b></tt>: </dt>
483 <dd>"<tt>appending</tt>" linkage may only be applied to global variables of
484 pointer to array type. When two global variables with appending linkage are
485 linked together, the two global arrays are appended together. This is the
486 LLVM, typesafe, equivalent of having the system linker append together
487 "sections" with identical names when .o files are linked.
490 <dt><tt><b><a name="linkage_externweak">extern_weak</a></b></tt>: </dt>
491 <dd>The semantics of this linkage follow the ELF model: the symbol is weak
492 until linked, if not linked, the symbol becomes null instead of being an
496 <dt><tt><b><a name="linkage_external">externally visible</a></b></tt>:</dt>
498 <dd>If none of the above identifiers are used, the global is externally
499 visible, meaning that it participates in linkage and can be used to resolve
500 external symbol references.
505 The next two types of linkage are targeted for Microsoft Windows platform
506 only. They are designed to support importing (exporting) symbols from (to)
511 <dt><tt><b><a name="linkage_dllimport">dllimport</a></b></tt>: </dt>
513 <dd>"<tt>dllimport</tt>" linkage causes the compiler to reference a function
514 or variable via a global pointer to a pointer that is set up by the DLL
515 exporting the symbol. On Microsoft Windows targets, the pointer name is
516 formed by combining <code>_imp__</code> and the function or variable name.
519 <dt><tt><b><a name="linkage_dllexport">dllexport</a></b></tt>: </dt>
521 <dd>"<tt>dllexport</tt>" linkage causes the compiler to provide a global
522 pointer to a pointer in a DLL, so that it can be referenced with the
523 <tt>dllimport</tt> attribute. On Microsoft Windows targets, the pointer
524 name is formed by combining <code>_imp__</code> and the function or variable
530 <p><a name="linkage_external"></a>For example, since the "<tt>.LC0</tt>"
531 variable is defined to be internal, if another module defined a "<tt>.LC0</tt>"
532 variable and was linked with this one, one of the two would be renamed,
533 preventing a collision. Since "<tt>main</tt>" and "<tt>puts</tt>" are
534 external (i.e., lacking any linkage declarations), they are accessible
535 outside of the current module.</p>
536 <p>It is illegal for a function <i>declaration</i>
537 to have any linkage type other than "externally visible", <tt>dllimport</tt>,
538 or <tt>extern_weak</tt>.</p>
539 <p>Aliases can have only <tt>external</tt>, <tt>internal</tt> and <tt>weak</tt>
543 <!-- ======================================================================= -->
544 <div class="doc_subsection">
545 <a name="callingconv">Calling Conventions</a>
548 <div class="doc_text">
550 <p>LLVM <a href="#functionstructure">functions</a>, <a href="#i_call">calls</a>
551 and <a href="#i_invoke">invokes</a> can all have an optional calling convention
552 specified for the call. The calling convention of any pair of dynamic
553 caller/callee must match, or the behavior of the program is undefined. The
554 following calling conventions are supported by LLVM, and more may be added in
558 <dt><b>"<tt>ccc</tt>" - The C calling convention</b>:</dt>
560 <dd>This calling convention (the default if no other calling convention is
561 specified) matches the target C calling conventions. This calling convention
562 supports varargs function calls and tolerates some mismatch in the declared
563 prototype and implemented declaration of the function (as does normal C).
566 <dt><b>"<tt>fastcc</tt>" - The fast calling convention</b>:</dt>
568 <dd>This calling convention attempts to make calls as fast as possible
569 (e.g. by passing things in registers). This calling convention allows the
570 target to use whatever tricks it wants to produce fast code for the target,
571 without having to conform to an externally specified ABI. Implementations of
572 this convention should allow arbitrary tail call optimization to be supported.
573 This calling convention does not support varargs and requires the prototype of
574 all callees to exactly match the prototype of the function definition.
577 <dt><b>"<tt>coldcc</tt>" - The cold calling convention</b>:</dt>
579 <dd>This calling convention attempts to make code in the caller as efficient
580 as possible under the assumption that the call is not commonly executed. As
581 such, these calls often preserve all registers so that the call does not break
582 any live ranges in the caller side. This calling convention does not support
583 varargs and requires the prototype of all callees to exactly match the
584 prototype of the function definition.
587 <dt><b>"<tt>cc <<em>n</em>></tt>" - Numbered convention</b>:</dt>
589 <dd>Any calling convention may be specified by number, allowing
590 target-specific calling conventions to be used. Target specific calling
591 conventions start at 64.
595 <p>More calling conventions can be added/defined on an as-needed basis, to
596 support pascal conventions or any other well-known target-independent
601 <!-- ======================================================================= -->
602 <div class="doc_subsection">
603 <a name="visibility">Visibility Styles</a>
606 <div class="doc_text">
609 All Global Variables and Functions have one of the following visibility styles:
613 <dt><b>"<tt>default</tt>" - Default style</b>:</dt>
615 <dd>On ELF, default visibility means that the declaration is visible to other
616 modules and, in shared libraries, means that the declared entity may be
617 overridden. On Darwin, default visibility means that the declaration is
618 visible to other modules. Default visibility corresponds to "external
619 linkage" in the language.
622 <dt><b>"<tt>hidden</tt>" - Hidden style</b>:</dt>
624 <dd>Two declarations of an object with hidden visibility refer to the same
625 object if they are in the same shared object. Usually, hidden visibility
626 indicates that the symbol will not be placed into the dynamic symbol table,
627 so no other module (executable or shared library) can reference it
631 <dt><b>"<tt>protected</tt>" - Protected style</b>:</dt>
633 <dd>On ELF, protected visibility indicates that the symbol will be placed in
634 the dynamic symbol table, but that references within the defining module will
635 bind to the local symbol. That is, the symbol cannot be overridden by another
642 <!-- ======================================================================= -->
643 <div class="doc_subsection">
644 <a name="globalvars">Global Variables</a>
647 <div class="doc_text">
649 <p>Global variables define regions of memory allocated at compilation time
650 instead of run-time. Global variables may optionally be initialized, may have
651 an explicit section to be placed in, and may have an optional explicit alignment
652 specified. A variable may be defined as "thread_local", which means that it
653 will not be shared by threads (each thread will have a separated copy of the
654 variable). A variable may be defined as a global "constant," which indicates
655 that the contents of the variable will <b>never</b> be modified (enabling better
656 optimization, allowing the global data to be placed in the read-only section of
657 an executable, etc). Note that variables that need runtime initialization
658 cannot be marked "constant" as there is a store to the variable.</p>
661 LLVM explicitly allows <em>declarations</em> of global variables to be marked
662 constant, even if the final definition of the global is not. This capability
663 can be used to enable slightly better optimization of the program, but requires
664 the language definition to guarantee that optimizations based on the
665 'constantness' are valid for the translation units that do not include the
669 <p>As SSA values, global variables define pointer values that are in
670 scope (i.e. they dominate) all basic blocks in the program. Global
671 variables always define a pointer to their "content" type because they
672 describe a region of memory, and all memory objects in LLVM are
673 accessed through pointers.</p>
675 <p>A global variable may be declared to reside in a target-specifc numbered
676 address space. For targets that support them, address spaces may affect how
677 optimizations are performed and/or what target instructions are used to access
678 the variable. The default address space is zero. The address space qualifier
679 must precede any other attributes.</p>
681 <p>LLVM allows an explicit section to be specified for globals. If the target
682 supports it, it will emit globals to the section specified.</p>
684 <p>An explicit alignment may be specified for a global. If not present, or if
685 the alignment is set to zero, the alignment of the global is set by the target
686 to whatever it feels convenient. If an explicit alignment is specified, the
687 global is forced to have at least that much alignment. All alignments must be
690 <p>For example, the following defines a global in a numbered address space with
691 an initializer, section, and alignment:</p>
693 <div class="doc_code">
695 @G = constant float 1.0 addrspace(5), section "foo", align 4
702 <!-- ======================================================================= -->
703 <div class="doc_subsection">
704 <a name="functionstructure">Functions</a>
707 <div class="doc_text">
709 <p>LLVM function definitions consist of the "<tt>define</tt>" keyord,
710 an optional <a href="#linkage">linkage type</a>, an optional
711 <a href="#visibility">visibility style</a>, an optional
712 <a href="#callingconv">calling convention</a>, a return type, an optional
713 <a href="#paramattrs">parameter attribute</a> for the return type, a function
714 name, a (possibly empty) argument list (each with optional
715 <a href="#paramattrs">parameter attributes</a>), an optional section, an
716 optional alignment, an optional <a href="#gc">garbage collector name</a>, an
717 opening curly brace, a list of basic blocks, and a closing curly brace.
719 LLVM function declarations consist of the "<tt>declare</tt>" keyword, an
720 optional <a href="#linkage">linkage type</a>, an optional
721 <a href="#visibility">visibility style</a>, an optional
722 <a href="#callingconv">calling convention</a>, a return type, an optional
723 <a href="#paramattrs">parameter attribute</a> for the return type, a function
724 name, a possibly empty list of arguments, an optional alignment, and an optional
725 <a href="#gc">garbage collector name</a>.</p>
727 <p>A function definition contains a list of basic blocks, forming the CFG for
728 the function. Each basic block may optionally start with a label (giving the
729 basic block a symbol table entry), contains a list of instructions, and ends
730 with a <a href="#terminators">terminator</a> instruction (such as a branch or
731 function return).</p>
733 <p>The first basic block in a function is special in two ways: it is immediately
734 executed on entrance to the function, and it is not allowed to have predecessor
735 basic blocks (i.e. there can not be any branches to the entry block of a
736 function). Because the block can have no predecessors, it also cannot have any
737 <a href="#i_phi">PHI nodes</a>.</p>
739 <p>LLVM allows an explicit section to be specified for functions. If the target
740 supports it, it will emit functions to the section specified.</p>
742 <p>An explicit alignment may be specified for a function. If not present, or if
743 the alignment is set to zero, the alignment of the function is set by the target
744 to whatever it feels convenient. If an explicit alignment is specified, the
745 function is forced to have at least that much alignment. All alignments must be
751 <!-- ======================================================================= -->
752 <div class="doc_subsection">
753 <a name="aliasstructure">Aliases</a>
755 <div class="doc_text">
756 <p>Aliases act as "second name" for the aliasee value (which can be either
757 function or global variable or bitcast of global value). Aliases may have an
758 optional <a href="#linkage">linkage type</a>, and an
759 optional <a href="#visibility">visibility style</a>.</p>
763 <div class="doc_code">
765 @<Name> = [Linkage] [Visibility] alias <AliaseeTy> @<Aliasee>
773 <!-- ======================================================================= -->
774 <div class="doc_subsection"><a name="paramattrs">Parameter Attributes</a></div>
775 <div class="doc_text">
776 <p>The return type and each parameter of a function type may have a set of
777 <i>parameter attributes</i> associated with them. Parameter attributes are
778 used to communicate additional information about the result or parameters of
779 a function. Parameter attributes are considered to be part of the function,
780 not of the function type, so functions with different parameter attributes
781 can have the same function type.</p>
783 <p>Parameter attributes are simple keywords that follow the type specified. If
784 multiple parameter attributes are needed, they are space separated. For
787 <div class="doc_code">
789 declare i32 @printf(i8* noalias , ...) nounwind
790 declare i32 @atoi(i8*) nounwind readonly
794 <p>Note that any attributes for the function result (<tt>nounwind</tt>,
795 <tt>readonly</tt>) come immediately after the argument list.</p>
797 <p>Currently, only the following parameter attributes are defined:</p>
799 <dt><tt>zeroext</tt></dt>
800 <dd>This indicates that the parameter should be zero extended just before
801 a call to this function.</dd>
803 <dt><tt>signext</tt></dt>
804 <dd>This indicates that the parameter should be sign extended just before
805 a call to this function.</dd>
807 <dt><tt>inreg</tt></dt>
808 <dd>This indicates that the parameter should be placed in register (if
809 possible) during assembling function call. Support for this attribute is
812 <dt><tt>byval</tt></dt>
813 <dd>This indicates that the pointer parameter is really an aggregate that
814 was passed by value to the function. The attribute implies that a hidden
815 copy of the struct is made between the caller and the callee, so the
816 callee is unable to modify the struct in the callee. This attribute is only
817 valid on llvm pointer arguments.</dd>
819 <dt><tt>sret</tt></dt>
820 <dd>This indicates that the parameter specifies the address of a structure
821 that is the return value of the function in the source program.</dd>
823 <dt><tt>noalias</tt></dt>
824 <dd>This indicates that the parameter not alias any other object or any
825 other "noalias" objects during the function call.
827 <dt><tt>noreturn</tt></dt>
828 <dd>This function attribute indicates that the function never returns. This
829 indicates to LLVM that every call to this function should be treated as if
830 an <tt>unreachable</tt> instruction immediately followed the call.</dd>
832 <dt><tt>nounwind</tt></dt>
833 <dd>This function attribute indicates that the function type does not use
834 the unwind instruction and does not allow stack unwinding to propagate
837 <dt><tt>nest</tt></dt>
838 <dd>This indicates that the parameter can be excised using the
839 <a href="#int_trampoline">trampoline intrinsics</a>.</dd>
840 <dt><tt>readonly</tt></dt>
841 <dd>This function attribute indicates that the function has no side-effects
842 except for producing a return value or throwing an exception. The value
843 returned must only depend on the function arguments and/or global variables.
844 It may use values obtained by dereferencing pointers.</dd>
845 <dt><tt>readnone</tt></dt>
846 <dd>A <tt>readnone</tt> function has the same restrictions as a <tt>readonly</tt>
847 function, but in addition it is not allowed to dereference any pointer arguments
853 <!-- ======================================================================= -->
854 <div class="doc_subsection">
855 <a name="gc">Garbage Collector Names</a>
858 <div class="doc_text">
859 <p>Each function may specify a garbage collector name, which is simply a
862 <div class="doc_code"><pre
863 >define void @f() gc "name" { ...</pre></div>
865 <p>The compiler declares the supported values of <i>name</i>. Specifying a
866 collector which will cause the compiler to alter its output in order to support
867 the named garbage collection algorithm.</p>
870 <!-- ======================================================================= -->
871 <div class="doc_subsection">
872 <a name="moduleasm">Module-Level Inline Assembly</a>
875 <div class="doc_text">
877 Modules may contain "module-level inline asm" blocks, which corresponds to the
878 GCC "file scope inline asm" blocks. These blocks are internally concatenated by
879 LLVM and treated as a single unit, but may be separated in the .ll file if
880 desired. The syntax is very simple:
883 <div class="doc_code">
885 module asm "inline asm code goes here"
886 module asm "more can go here"
890 <p>The strings can contain any character by escaping non-printable characters.
891 The escape sequence used is simply "\xx" where "xx" is the two digit hex code
896 The inline asm code is simply printed to the machine code .s file when
897 assembly code is generated.
901 <!-- ======================================================================= -->
902 <div class="doc_subsection">
903 <a name="datalayout">Data Layout</a>
906 <div class="doc_text">
907 <p>A module may specify a target specific data layout string that specifies how
908 data is to be laid out in memory. The syntax for the data layout is simply:</p>
909 <pre> target datalayout = "<i>layout specification</i>"</pre>
910 <p>The <i>layout specification</i> consists of a list of specifications
911 separated by the minus sign character ('-'). Each specification starts with a
912 letter and may include other information after the letter to define some
913 aspect of the data layout. The specifications accepted are as follows: </p>
916 <dd>Specifies that the target lays out data in big-endian form. That is, the
917 bits with the most significance have the lowest address location.</dd>
919 <dd>Specifies that hte target lays out data in little-endian form. That is,
920 the bits with the least significance have the lowest address location.</dd>
921 <dt><tt>p:<i>size</i>:<i>abi</i>:<i>pref</i></tt></dt>
922 <dd>This specifies the <i>size</i> of a pointer and its <i>abi</i> and
923 <i>preferred</i> alignments. All sizes are in bits. Specifying the <i>pref</i>
924 alignment is optional. If omitted, the preceding <tt>:</tt> should be omitted
926 <dt><tt>i<i>size</i>:<i>abi</i>:<i>pref</i></tt></dt>
927 <dd>This specifies the alignment for an integer type of a given bit
928 <i>size</i>. The value of <i>size</i> must be in the range [1,2^23).</dd>
929 <dt><tt>v<i>size</i>:<i>abi</i>:<i>pref</i></tt></dt>
930 <dd>This specifies the alignment for a vector type of a given bit
932 <dt><tt>f<i>size</i>:<i>abi</i>:<i>pref</i></tt></dt>
933 <dd>This specifies the alignment for a floating point type of a given bit
934 <i>size</i>. The value of <i>size</i> must be either 32 (float) or 64
936 <dt><tt>a<i>size</i>:<i>abi</i>:<i>pref</i></tt></dt>
937 <dd>This specifies the alignment for an aggregate type of a given bit
940 <p>When constructing the data layout for a given target, LLVM starts with a
941 default set of specifications which are then (possibly) overriden by the
942 specifications in the <tt>datalayout</tt> keyword. The default specifications
943 are given in this list:</p>
945 <li><tt>E</tt> - big endian</li>
946 <li><tt>p:32:64:64</tt> - 32-bit pointers with 64-bit alignment</li>
947 <li><tt>i1:8:8</tt> - i1 is 8-bit (byte) aligned</li>
948 <li><tt>i8:8:8</tt> - i8 is 8-bit (byte) aligned</li>
949 <li><tt>i16:16:16</tt> - i16 is 16-bit aligned</li>
950 <li><tt>i32:32:32</tt> - i32 is 32-bit aligned</li>
951 <li><tt>i64:32:64</tt> - i64 has abi alignment of 32-bits but preferred
952 alignment of 64-bits</li>
953 <li><tt>f32:32:32</tt> - float is 32-bit aligned</li>
954 <li><tt>f64:64:64</tt> - double is 64-bit aligned</li>
955 <li><tt>v64:64:64</tt> - 64-bit vector is 64-bit aligned</li>
956 <li><tt>v128:128:128</tt> - 128-bit vector is 128-bit aligned</li>
957 <li><tt>a0:0:1</tt> - aggregates are 8-bit aligned</li>
959 <p>When llvm is determining the alignment for a given type, it uses the
962 <li>If the type sought is an exact match for one of the specifications, that
963 specification is used.</li>
964 <li>If no match is found, and the type sought is an integer type, then the
965 smallest integer type that is larger than the bitwidth of the sought type is
966 used. If none of the specifications are larger than the bitwidth then the the
967 largest integer type is used. For example, given the default specifications
968 above, the i7 type will use the alignment of i8 (next largest) while both
969 i65 and i256 will use the alignment of i64 (largest specified).</li>
970 <li>If no match is found, and the type sought is a vector type, then the
971 largest vector type that is smaller than the sought vector type will be used
972 as a fall back. This happens because <128 x double> can be implemented in
973 terms of 64 <2 x double>, for example.</li>
977 <!-- *********************************************************************** -->
978 <div class="doc_section"> <a name="typesystem">Type System</a> </div>
979 <!-- *********************************************************************** -->
981 <div class="doc_text">
983 <p>The LLVM type system is one of the most important features of the
984 intermediate representation. Being typed enables a number of
985 optimizations to be performed on the IR directly, without having to do
986 extra analyses on the side before the transformation. A strong type
987 system makes it easier to read the generated code and enables novel
988 analyses and transformations that are not feasible to perform on normal
989 three address code representations.</p>
993 <!-- ======================================================================= -->
994 <div class="doc_subsection"> <a name="t_classifications">Type
995 Classifications</a> </div>
996 <div class="doc_text">
997 <p>The types fall into a few useful
1000 <table border="1" cellspacing="0" cellpadding="4">
1002 <tr><th>Classification</th><th>Types</th></tr>
1004 <td><a href="#t_integer">integer</a></td>
1005 <td><tt>i1, i2, i3, ... i8, ... i16, ... i32, ... i64, ... </tt></td>
1008 <td><a href="#t_floating">floating point</a></td>
1009 <td><tt>float, double, x86_fp80, fp128, ppc_fp128</tt></td>
1012 <td><a name="t_firstclass">first class</a></td>
1013 <td><a href="#t_integer">integer</a>,
1014 <a href="#t_floating">floating point</a>,
1015 <a href="#t_pointer">pointer</a>,
1016 <a href="#t_vector">vector</a>
1020 <td><a href="#t_primitive">primitive</a></td>
1021 <td><a href="#t_label">label</a>,
1022 <a href="#t_void">void</a>,
1023 <a href="#t_integer">integer</a>,
1024 <a href="#t_floating">floating point</a>.</td>
1027 <td><a href="#t_derived">derived</a></td>
1028 <td><a href="#t_integer">integer</a>,
1029 <a href="#t_array">array</a>,
1030 <a href="#t_function">function</a>,
1031 <a href="#t_pointer">pointer</a>,
1032 <a href="#t_struct">structure</a>,
1033 <a href="#t_pstruct">packed structure</a>,
1034 <a href="#t_vector">vector</a>,
1035 <a href="#t_opaque">opaque</a>.
1040 <p>The <a href="#t_firstclass">first class</a> types are perhaps the
1041 most important. Values of these types are the only ones which can be
1042 produced by instructions, passed as arguments, or used as operands to
1043 instructions. This means that all structures and arrays must be
1044 manipulated either by pointer or by component.</p>
1047 <!-- ======================================================================= -->
1048 <div class="doc_subsection"> <a name="t_primitive">Primitive Types</a> </div>
1050 <div class="doc_text">
1051 <p>The primitive types are the fundamental building blocks of the LLVM
1056 <!-- _______________________________________________________________________ -->
1057 <div class="doc_subsubsection"> <a name="t_floating">Floating Point Types</a> </div>
1059 <div class="doc_text">
1062 <tr><th>Type</th><th>Description</th></tr>
1063 <tr><td><tt>float</tt></td><td>32-bit floating point value</td></tr>
1064 <tr><td><tt>double</tt></td><td>64-bit floating point value</td></tr>
1065 <tr><td><tt>fp128</tt></td><td>128-bit floating point value (112-bit mantissa)</td></tr>
1066 <tr><td><tt>x86_fp80</tt></td><td>80-bit floating point value (X87)</td></tr>
1067 <tr><td><tt>ppc_fp128</tt></td><td>128-bit floating point value (two 64-bits)</td></tr>
1072 <!-- _______________________________________________________________________ -->
1073 <div class="doc_subsubsection"> <a name="t_void">Void Type</a> </div>
1075 <div class="doc_text">
1077 <p>The void type does not represent any value and has no size.</p>
1086 <!-- _______________________________________________________________________ -->
1087 <div class="doc_subsubsection"> <a name="t_label">Label Type</a> </div>
1089 <div class="doc_text">
1091 <p>The label type represents code labels.</p>
1101 <!-- ======================================================================= -->
1102 <div class="doc_subsection"> <a name="t_derived">Derived Types</a> </div>
1104 <div class="doc_text">
1106 <p>The real power in LLVM comes from the derived types in the system.
1107 This is what allows a programmer to represent arrays, functions,
1108 pointers, and other useful types. Note that these derived types may be
1109 recursive: For example, it is possible to have a two dimensional array.</p>
1113 <!-- _______________________________________________________________________ -->
1114 <div class="doc_subsubsection"> <a name="t_integer">Integer Type</a> </div>
1116 <div class="doc_text">
1119 <p>The integer type is a very simple derived type that simply specifies an
1120 arbitrary bit width for the integer type desired. Any bit width from 1 bit to
1121 2^23-1 (about 8 million) can be specified.</p>
1129 <p>The number of bits the integer will occupy is specified by the <tt>N</tt>
1133 <table class="layout">
1136 <td><tt>i1</tt></td>
1137 <td>a single-bit integer.</td>
1139 <td><tt>i32</tt></td>
1140 <td>a 32-bit integer.</td>
1142 <td><tt>i1942652</tt></td>
1143 <td>a really big integer of over 1 million bits.</td>
1149 <!-- _______________________________________________________________________ -->
1150 <div class="doc_subsubsection"> <a name="t_array">Array Type</a> </div>
1152 <div class="doc_text">
1156 <p>The array type is a very simple derived type that arranges elements
1157 sequentially in memory. The array type requires a size (number of
1158 elements) and an underlying data type.</p>
1163 [<# elements> x <elementtype>]
1166 <p>The number of elements is a constant integer value; elementtype may
1167 be any type with a size.</p>
1170 <table class="layout">
1172 <td class="left"><tt>[40 x i32]</tt></td>
1173 <td class="left">Array of 40 32-bit integer values.</td>
1176 <td class="left"><tt>[41 x i32]</tt></td>
1177 <td class="left">Array of 41 32-bit integer values.</td>
1180 <td class="left"><tt>[4 x i8]</tt></td>
1181 <td class="left">Array of 4 8-bit integer values.</td>
1184 <p>Here are some examples of multidimensional arrays:</p>
1185 <table class="layout">
1187 <td class="left"><tt>[3 x [4 x i32]]</tt></td>
1188 <td class="left">3x4 array of 32-bit integer values.</td>
1191 <td class="left"><tt>[12 x [10 x float]]</tt></td>
1192 <td class="left">12x10 array of single precision floating point values.</td>
1195 <td class="left"><tt>[2 x [3 x [4 x i16]]]</tt></td>
1196 <td class="left">2x3x4 array of 16-bit integer values.</td>
1200 <p>Note that 'variable sized arrays' can be implemented in LLVM with a zero
1201 length array. Normally, accesses past the end of an array are undefined in
1202 LLVM (e.g. it is illegal to access the 5th element of a 3 element array).
1203 As a special case, however, zero length arrays are recognized to be variable
1204 length. This allows implementation of 'pascal style arrays' with the LLVM
1205 type "{ i32, [0 x float]}", for example.</p>
1209 <!-- _______________________________________________________________________ -->
1210 <div class="doc_subsubsection"> <a name="t_function">Function Type</a> </div>
1211 <div class="doc_text">
1213 <p>The function type can be thought of as a function signature. It
1214 consists of a return type and a list of formal parameter types.
1215 Function types are usually used to build virtual function tables
1216 (which are structures of pointers to functions), for indirect function
1217 calls, and when defining a function.</p>
1219 The return type of a function type cannot be an aggregate type.
1222 <pre> <returntype> (<parameter list>)<br></pre>
1223 <p>...where '<tt><parameter list></tt>' is a comma-separated list of type
1224 specifiers. Optionally, the parameter list may include a type <tt>...</tt>,
1225 which indicates that the function takes a variable number of arguments.
1226 Variable argument functions can access their arguments with the <a
1227 href="#int_varargs">variable argument handling intrinsic</a> functions.</p>
1229 <table class="layout">
1231 <td class="left"><tt>i32 (i32)</tt></td>
1232 <td class="left">function taking an <tt>i32</tt>, returning an <tt>i32</tt>
1234 </tr><tr class="layout">
1235 <td class="left"><tt>float (i16 signext, i32 *) *
1237 <td class="left"><a href="#t_pointer">Pointer</a> to a function that takes
1238 an <tt>i16</tt> that should be sign extended and a
1239 <a href="#t_pointer">pointer</a> to <tt>i32</tt>, returning
1242 </tr><tr class="layout">
1243 <td class="left"><tt>i32 (i8*, ...)</tt></td>
1244 <td class="left">A vararg function that takes at least one
1245 <a href="#t_pointer">pointer</a> to <tt>i8 </tt> (char in C),
1246 which returns an integer. This is the signature for <tt>printf</tt> in
1253 <!-- _______________________________________________________________________ -->
1254 <div class="doc_subsubsection"> <a name="t_struct">Structure Type</a> </div>
1255 <div class="doc_text">
1257 <p>The structure type is used to represent a collection of data members
1258 together in memory. The packing of the field types is defined to match
1259 the ABI of the underlying processor. The elements of a structure may
1260 be any type that has a size.</p>
1261 <p>Structures are accessed using '<tt><a href="#i_load">load</a></tt>
1262 and '<tt><a href="#i_store">store</a></tt>' by getting a pointer to a
1263 field with the '<tt><a href="#i_getelementptr">getelementptr</a></tt>'
1266 <pre> { <type list> }<br></pre>
1268 <table class="layout">
1270 <td class="left"><tt>{ i32, i32, i32 }</tt></td>
1271 <td class="left">A triple of three <tt>i32</tt> values</td>
1272 </tr><tr class="layout">
1273 <td class="left"><tt>{ float, i32 (i32) * }</tt></td>
1274 <td class="left">A pair, where the first element is a <tt>float</tt> and the
1275 second element is a <a href="#t_pointer">pointer</a> to a
1276 <a href="#t_function">function</a> that takes an <tt>i32</tt>, returning
1277 an <tt>i32</tt>.</td>
1282 <!-- _______________________________________________________________________ -->
1283 <div class="doc_subsubsection"> <a name="t_pstruct">Packed Structure Type</a>
1285 <div class="doc_text">
1287 <p>The packed structure type is used to represent a collection of data members
1288 together in memory. There is no padding between fields. Further, the alignment
1289 of a packed structure is 1 byte. The elements of a packed structure may
1290 be any type that has a size.</p>
1291 <p>Structures are accessed using '<tt><a href="#i_load">load</a></tt>
1292 and '<tt><a href="#i_store">store</a></tt>' by getting a pointer to a
1293 field with the '<tt><a href="#i_getelementptr">getelementptr</a></tt>'
1296 <pre> < { <type list> } > <br></pre>
1298 <table class="layout">
1300 <td class="left"><tt>< { i32, i32, i32 } ></tt></td>
1301 <td class="left">A triple of three <tt>i32</tt> values</td>
1302 </tr><tr class="layout">
1303 <td class="left"><tt>< { float, i32 (i32)* } ></tt></td>
1304 <td class="left">A pair, where the first element is a <tt>float</tt> and the
1305 second element is a <a href="#t_pointer">pointer</a> to a
1306 <a href="#t_function">function</a> that takes an <tt>i32</tt>, returning
1307 an <tt>i32</tt>.</td>
1312 <!-- _______________________________________________________________________ -->
1313 <div class="doc_subsubsection"> <a name="t_pointer">Pointer Type</a> </div>
1314 <div class="doc_text">
1316 <p>As in many languages, the pointer type represents a pointer or
1317 reference to another object, which must live in memory. Pointer types may have
1318 an optional address space attribute defining the target-specific numbered
1319 address space where the pointed-to object resides. The default address space is
1322 <pre> <type> *<br></pre>
1324 <table class="layout">
1326 <td class="left"><tt>[4x i32]*</tt></td>
1327 <td class="left">A <a href="#t_pointer">pointer</a> to <a
1328 href="#t_array">array</a> of four <tt>i32</tt> values.</td>
1331 <td class="left"><tt>i32 (i32 *) *</tt></td>
1332 <td class="left"> A <a href="#t_pointer">pointer</a> to a <a
1333 href="#t_function">function</a> that takes an <tt>i32*</tt>, returning an
1337 <td class="left"><tt>i32 addrspace(5)*</tt></td>
1338 <td class="left">A <a href="#t_pointer">pointer</a> to an <tt>i32</tt> value
1339 that resides in address space #5.</td>
1344 <!-- _______________________________________________________________________ -->
1345 <div class="doc_subsubsection"> <a name="t_vector">Vector Type</a> </div>
1346 <div class="doc_text">
1350 <p>A vector type is a simple derived type that represents a vector
1351 of elements. Vector types are used when multiple primitive data
1352 are operated in parallel using a single instruction (SIMD).
1353 A vector type requires a size (number of
1354 elements) and an underlying primitive data type. Vectors must have a power
1355 of two length (1, 2, 4, 8, 16 ...). Vector types are
1356 considered <a href="#t_firstclass">first class</a>.</p>
1361 < <# elements> x <elementtype> >
1364 <p>The number of elements is a constant integer value; elementtype may
1365 be any integer or floating point type.</p>
1369 <table class="layout">
1371 <td class="left"><tt><4 x i32></tt></td>
1372 <td class="left">Vector of 4 32-bit integer values.</td>
1375 <td class="left"><tt><8 x float></tt></td>
1376 <td class="left">Vector of 8 32-bit floating-point values.</td>
1379 <td class="left"><tt><2 x i64></tt></td>
1380 <td class="left">Vector of 2 64-bit integer values.</td>
1385 <!-- _______________________________________________________________________ -->
1386 <div class="doc_subsubsection"> <a name="t_opaque">Opaque Type</a> </div>
1387 <div class="doc_text">
1391 <p>Opaque types are used to represent unknown types in the system. This
1392 corresponds (for example) to the C notion of a forward declared structure type.
1393 In LLVM, opaque types can eventually be resolved to any type (not just a
1394 structure type).</p>
1404 <table class="layout">
1406 <td class="left"><tt>opaque</tt></td>
1407 <td class="left">An opaque type.</td>
1413 <!-- *********************************************************************** -->
1414 <div class="doc_section"> <a name="constants">Constants</a> </div>
1415 <!-- *********************************************************************** -->
1417 <div class="doc_text">
1419 <p>LLVM has several different basic types of constants. This section describes
1420 them all and their syntax.</p>
1424 <!-- ======================================================================= -->
1425 <div class="doc_subsection"><a name="simpleconstants">Simple Constants</a></div>
1427 <div class="doc_text">
1430 <dt><b>Boolean constants</b></dt>
1432 <dd>The two strings '<tt>true</tt>' and '<tt>false</tt>' are both valid
1433 constants of the <tt><a href="#t_primitive">i1</a></tt> type.
1436 <dt><b>Integer constants</b></dt>
1438 <dd>Standard integers (such as '4') are constants of the <a
1439 href="#t_integer">integer</a> type. Negative numbers may be used with
1443 <dt><b>Floating point constants</b></dt>
1445 <dd>Floating point constants use standard decimal notation (e.g. 123.421),
1446 exponential notation (e.g. 1.23421e+2), or a more precise hexadecimal
1447 notation (see below). Floating point constants must have a <a
1448 href="#t_floating">floating point</a> type. </dd>
1450 <dt><b>Null pointer constants</b></dt>
1452 <dd>The identifier '<tt>null</tt>' is recognized as a null pointer constant
1453 and must be of <a href="#t_pointer">pointer type</a>.</dd>
1457 <p>The one non-intuitive notation for constants is the optional hexadecimal form
1458 of floating point constants. For example, the form '<tt>double
1459 0x432ff973cafa8000</tt>' is equivalent to (but harder to read than) '<tt>double
1460 4.5e+15</tt>'. The only time hexadecimal floating point constants are required
1461 (and the only time that they are generated by the disassembler) is when a
1462 floating point constant must be emitted but it cannot be represented as a
1463 decimal floating point number. For example, NaN's, infinities, and other
1464 special values are represented in their IEEE hexadecimal format so that
1465 assembly and disassembly do not cause any bits to change in the constants.</p>
1469 <!-- ======================================================================= -->
1470 <div class="doc_subsection"><a name="aggregateconstants">Aggregate Constants</a>
1473 <div class="doc_text">
1474 <p>Aggregate constants arise from aggregation of simple constants
1475 and smaller aggregate constants.</p>
1478 <dt><b>Structure constants</b></dt>
1480 <dd>Structure constants are represented with notation similar to structure
1481 type definitions (a comma separated list of elements, surrounded by braces
1482 (<tt>{}</tt>)). For example: "<tt>{ i32 4, float 17.0, i32* @G }</tt>",
1483 where "<tt>@G</tt>" is declared as "<tt>@G = external global i32</tt>". Structure constants
1484 must have <a href="#t_struct">structure type</a>, and the number and
1485 types of elements must match those specified by the type.
1488 <dt><b>Array constants</b></dt>
1490 <dd>Array constants are represented with notation similar to array type
1491 definitions (a comma separated list of elements, surrounded by square brackets
1492 (<tt>[]</tt>)). For example: "<tt>[ i32 42, i32 11, i32 74 ]</tt>". Array
1493 constants must have <a href="#t_array">array type</a>, and the number and
1494 types of elements must match those specified by the type.
1497 <dt><b>Vector constants</b></dt>
1499 <dd>Vector constants are represented with notation similar to vector type
1500 definitions (a comma separated list of elements, surrounded by
1501 less-than/greater-than's (<tt><></tt>)). For example: "<tt>< i32 42,
1502 i32 11, i32 74, i32 100 ></tt>". Vector constants must have <a
1503 href="#t_vector">vector type</a>, and the number and types of elements must
1504 match those specified by the type.
1507 <dt><b>Zero initialization</b></dt>
1509 <dd>The string '<tt>zeroinitializer</tt>' can be used to zero initialize a
1510 value to zero of <em>any</em> type, including scalar and aggregate types.
1511 This is often used to avoid having to print large zero initializers (e.g. for
1512 large arrays) and is always exactly equivalent to using explicit zero
1519 <!-- ======================================================================= -->
1520 <div class="doc_subsection">
1521 <a name="globalconstants">Global Variable and Function Addresses</a>
1524 <div class="doc_text">
1526 <p>The addresses of <a href="#globalvars">global variables</a> and <a
1527 href="#functionstructure">functions</a> are always implicitly valid (link-time)
1528 constants. These constants are explicitly referenced when the <a
1529 href="#identifiers">identifier for the global</a> is used and always have <a
1530 href="#t_pointer">pointer</a> type. For example, the following is a legal LLVM
1533 <div class="doc_code">
1537 @Z = global [2 x i32*] [ i32* @X, i32* @Y ]
1543 <!-- ======================================================================= -->
1544 <div class="doc_subsection"><a name="undefvalues">Undefined Values</a></div>
1545 <div class="doc_text">
1546 <p>The string '<tt>undef</tt>' is recognized as a type-less constant that has
1547 no specific value. Undefined values may be of any type and be used anywhere
1548 a constant is permitted.</p>
1550 <p>Undefined values indicate to the compiler that the program is well defined
1551 no matter what value is used, giving the compiler more freedom to optimize.
1555 <!-- ======================================================================= -->
1556 <div class="doc_subsection"><a name="constantexprs">Constant Expressions</a>
1559 <div class="doc_text">
1561 <p>Constant expressions are used to allow expressions involving other constants
1562 to be used as constants. Constant expressions may be of any <a
1563 href="#t_firstclass">first class</a> type and may involve any LLVM operation
1564 that does not have side effects (e.g. load and call are not supported). The
1565 following is the syntax for constant expressions:</p>
1568 <dt><b><tt>trunc ( CST to TYPE )</tt></b></dt>
1569 <dd>Truncate a constant to another type. The bit size of CST must be larger
1570 than the bit size of TYPE. Both types must be integers.</dd>
1572 <dt><b><tt>zext ( CST to TYPE )</tt></b></dt>
1573 <dd>Zero extend a constant to another type. The bit size of CST must be
1574 smaller or equal to the bit size of TYPE. Both types must be integers.</dd>
1576 <dt><b><tt>sext ( CST to TYPE )</tt></b></dt>
1577 <dd>Sign extend a constant to another type. The bit size of CST must be
1578 smaller or equal to the bit size of TYPE. Both types must be integers.</dd>
1580 <dt><b><tt>fptrunc ( CST to TYPE )</tt></b></dt>
1581 <dd>Truncate a floating point constant to another floating point type. The
1582 size of CST must be larger than the size of TYPE. Both types must be
1583 floating point.</dd>
1585 <dt><b><tt>fpext ( CST to TYPE )</tt></b></dt>
1586 <dd>Floating point extend a constant to another type. The size of CST must be
1587 smaller or equal to the size of TYPE. Both types must be floating point.</dd>
1589 <dt><b><tt>fptoui ( CST to TYPE )</tt></b></dt>
1590 <dd>Convert a floating point constant to the corresponding unsigned integer
1591 constant. TYPE must be a scalar or vector integer type. CST must be of scalar
1592 or vector floating point type. Both CST and TYPE must be scalars, or vectors
1593 of the same number of elements. If the value won't fit in the integer type,
1594 the results are undefined.</dd>
1596 <dt><b><tt>fptosi ( CST to TYPE )</tt></b></dt>
1597 <dd>Convert a floating point constant to the corresponding signed integer
1598 constant. TYPE must be a scalar or vector integer type. CST must be of scalar
1599 or vector floating point type. Both CST and TYPE must be scalars, or vectors
1600 of the same number of elements. If the value won't fit in the integer type,
1601 the results are undefined.</dd>
1603 <dt><b><tt>uitofp ( CST to TYPE )</tt></b></dt>
1604 <dd>Convert an unsigned integer constant to the corresponding floating point
1605 constant. TYPE must be a scalar or vector floating point type. CST must be of
1606 scalar or vector integer type. Both CST and TYPE must be scalars, or vectors
1607 of the same number of elements. If the value won't fit in the floating point
1608 type, the results are undefined.</dd>
1610 <dt><b><tt>sitofp ( CST to TYPE )</tt></b></dt>
1611 <dd>Convert a signed integer constant to the corresponding floating point
1612 constant. TYPE must be a scalar or vector floating point type. CST must be of
1613 scalar or vector integer type. Both CST and TYPE must be scalars, or vectors
1614 of the same number of elements. If the value won't fit in the floating point
1615 type, the results are undefined.</dd>
1617 <dt><b><tt>ptrtoint ( CST to TYPE )</tt></b></dt>
1618 <dd>Convert a pointer typed constant to the corresponding integer constant
1619 TYPE must be an integer type. CST must be of pointer type. The CST value is
1620 zero extended, truncated, or unchanged to make it fit in TYPE.</dd>
1622 <dt><b><tt>inttoptr ( CST to TYPE )</tt></b></dt>
1623 <dd>Convert a integer constant to a pointer constant. TYPE must be a
1624 pointer type. CST must be of integer type. The CST value is zero extended,
1625 truncated, or unchanged to make it fit in a pointer size. This one is
1626 <i>really</i> dangerous!</dd>
1628 <dt><b><tt>bitcast ( CST to TYPE )</tt></b></dt>
1629 <dd>Convert a constant, CST, to another TYPE. The size of CST and TYPE must be
1630 identical (same number of bits). The conversion is done as if the CST value
1631 was stored to memory and read back as TYPE. In other words, no bits change
1632 with this operator, just the type. This can be used for conversion of
1633 vector types to any other type, as long as they have the same bit width. For
1634 pointers it is only valid to cast to another pointer type.
1637 <dt><b><tt>getelementptr ( CSTPTR, IDX0, IDX1, ... )</tt></b></dt>
1639 <dd>Perform the <a href="#i_getelementptr">getelementptr operation</a> on
1640 constants. As with the <a href="#i_getelementptr">getelementptr</a>
1641 instruction, the index list may have zero or more indexes, which are required
1642 to make sense for the type of "CSTPTR".</dd>
1644 <dt><b><tt>select ( COND, VAL1, VAL2 )</tt></b></dt>
1646 <dd>Perform the <a href="#i_select">select operation</a> on
1649 <dt><b><tt>icmp COND ( VAL1, VAL2 )</tt></b></dt>
1650 <dd>Performs the <a href="#i_icmp">icmp operation</a> on constants.</dd>
1652 <dt><b><tt>fcmp COND ( VAL1, VAL2 )</tt></b></dt>
1653 <dd>Performs the <a href="#i_fcmp">fcmp operation</a> on constants.</dd>
1655 <dt><b><tt>extractelement ( VAL, IDX )</tt></b></dt>
1657 <dd>Perform the <a href="#i_extractelement">extractelement
1658 operation</a> on constants.
1660 <dt><b><tt>insertelement ( VAL, ELT, IDX )</tt></b></dt>
1662 <dd>Perform the <a href="#i_insertelement">insertelement
1663 operation</a> on constants.</dd>
1666 <dt><b><tt>shufflevector ( VEC1, VEC2, IDXMASK )</tt></b></dt>
1668 <dd>Perform the <a href="#i_shufflevector">shufflevector
1669 operation</a> on constants.</dd>
1671 <dt><b><tt>OPCODE ( LHS, RHS )</tt></b></dt>
1673 <dd>Perform the specified operation of the LHS and RHS constants. OPCODE may
1674 be any of the <a href="#binaryops">binary</a> or <a href="#bitwiseops">bitwise
1675 binary</a> operations. The constraints on operands are the same as those for
1676 the corresponding instruction (e.g. no bitwise operations on floating point
1677 values are allowed).</dd>
1681 <!-- *********************************************************************** -->
1682 <div class="doc_section"> <a name="othervalues">Other Values</a> </div>
1683 <!-- *********************************************************************** -->
1685 <!-- ======================================================================= -->
1686 <div class="doc_subsection">
1687 <a name="inlineasm">Inline Assembler Expressions</a>
1690 <div class="doc_text">
1693 LLVM supports inline assembler expressions (as opposed to <a href="#moduleasm">
1694 Module-Level Inline Assembly</a>) through the use of a special value. This
1695 value represents the inline assembler as a string (containing the instructions
1696 to emit), a list of operand constraints (stored as a string), and a flag that
1697 indicates whether or not the inline asm expression has side effects. An example
1698 inline assembler expression is:
1701 <div class="doc_code">
1703 i32 (i32) asm "bswap $0", "=r,r"
1708 Inline assembler expressions may <b>only</b> be used as the callee operand of
1709 a <a href="#i_call"><tt>call</tt> instruction</a>. Thus, typically we have:
1712 <div class="doc_code">
1714 %X = call i32 asm "<a href="#int_bswap">bswap</a> $0", "=r,r"(i32 %Y)
1719 Inline asms with side effects not visible in the constraint list must be marked
1720 as having side effects. This is done through the use of the
1721 '<tt>sideeffect</tt>' keyword, like so:
1724 <div class="doc_code">
1726 call void asm sideeffect "eieio", ""()
1730 <p>TODO: The format of the asm and constraints string still need to be
1731 documented here. Constraints on what can be done (e.g. duplication, moving, etc
1732 need to be documented).
1737 <!-- *********************************************************************** -->
1738 <div class="doc_section"> <a name="instref">Instruction Reference</a> </div>
1739 <!-- *********************************************************************** -->
1741 <div class="doc_text">
1743 <p>The LLVM instruction set consists of several different
1744 classifications of instructions: <a href="#terminators">terminator
1745 instructions</a>, <a href="#binaryops">binary instructions</a>,
1746 <a href="#bitwiseops">bitwise binary instructions</a>, <a
1747 href="#memoryops">memory instructions</a>, and <a href="#otherops">other
1748 instructions</a>.</p>
1752 <!-- ======================================================================= -->
1753 <div class="doc_subsection"> <a name="terminators">Terminator
1754 Instructions</a> </div>
1756 <div class="doc_text">
1758 <p>As mentioned <a href="#functionstructure">previously</a>, every
1759 basic block in a program ends with a "Terminator" instruction, which
1760 indicates which block should be executed after the current block is
1761 finished. These terminator instructions typically yield a '<tt>void</tt>'
1762 value: they produce control flow, not values (the one exception being
1763 the '<a href="#i_invoke"><tt>invoke</tt></a>' instruction).</p>
1764 <p>There are six different terminator instructions: the '<a
1765 href="#i_ret"><tt>ret</tt></a>' instruction, the '<a href="#i_br"><tt>br</tt></a>'
1766 instruction, the '<a href="#i_switch"><tt>switch</tt></a>' instruction,
1767 the '<a href="#i_invoke"><tt>invoke</tt></a>' instruction, the '<a
1768 href="#i_unwind"><tt>unwind</tt></a>' instruction, and the '<a
1769 href="#i_unreachable"><tt>unreachable</tt></a>' instruction.</p>
1773 <!-- _______________________________________________________________________ -->
1774 <div class="doc_subsubsection"> <a name="i_ret">'<tt>ret</tt>'
1775 Instruction</a> </div>
1776 <div class="doc_text">
1778 <pre> ret <type> <value> <i>; Return a value from a non-void function</i>
1779 ret void <i>; Return from void function</i>
1782 <p>The '<tt>ret</tt>' instruction is used to return control flow (and a
1783 value) from a function back to the caller.</p>
1784 <p>There are two forms of the '<tt>ret</tt>' instruction: one that
1785 returns a value and then causes control flow, and one that just causes
1786 control flow to occur.</p>
1788 <p>The '<tt>ret</tt>' instruction may return any '<a
1789 href="#t_firstclass">first class</a>' type. Notice that a function is
1790 not <a href="#wellformed">well formed</a> if there exists a '<tt>ret</tt>'
1791 instruction inside of the function that returns a value that does not
1792 match the return type of the function.</p>
1794 <p>When the '<tt>ret</tt>' instruction is executed, control flow
1795 returns back to the calling function's context. If the caller is a "<a
1796 href="#i_call"><tt>call</tt></a>" instruction, execution continues at
1797 the instruction after the call. If the caller was an "<a
1798 href="#i_invoke"><tt>invoke</tt></a>" instruction, execution continues
1799 at the beginning of the "normal" destination block. If the instruction
1800 returns a value, that value shall set the call or invoke instruction's
1803 <pre> ret i32 5 <i>; Return an integer value of 5</i>
1804 ret void <i>; Return from a void function</i>
1807 <!-- _______________________________________________________________________ -->
1808 <div class="doc_subsubsection"> <a name="i_br">'<tt>br</tt>' Instruction</a> </div>
1809 <div class="doc_text">
1811 <pre> br i1 <cond>, label <iftrue>, label <iffalse><br> br label <dest> <i>; Unconditional branch</i>
1814 <p>The '<tt>br</tt>' instruction is used to cause control flow to
1815 transfer to a different basic block in the current function. There are
1816 two forms of this instruction, corresponding to a conditional branch
1817 and an unconditional branch.</p>
1819 <p>The conditional branch form of the '<tt>br</tt>' instruction takes a
1820 single '<tt>i1</tt>' value and two '<tt>label</tt>' values. The
1821 unconditional form of the '<tt>br</tt>' instruction takes a single
1822 '<tt>label</tt>' value as a target.</p>
1824 <p>Upon execution of a conditional '<tt>br</tt>' instruction, the '<tt>i1</tt>'
1825 argument is evaluated. If the value is <tt>true</tt>, control flows
1826 to the '<tt>iftrue</tt>' <tt>label</tt> argument. If "cond" is <tt>false</tt>,
1827 control flows to the '<tt>iffalse</tt>' <tt>label</tt> argument.</p>
1829 <pre>Test:<br> %cond = <a href="#i_icmp">icmp</a> eq, i32 %a, %b<br> br i1 %cond, label %IfEqual, label %IfUnequal<br>IfEqual:<br> <a
1830 href="#i_ret">ret</a> i32 1<br>IfUnequal:<br> <a href="#i_ret">ret</a> i32 0<br></pre>
1832 <!-- _______________________________________________________________________ -->
1833 <div class="doc_subsubsection">
1834 <a name="i_switch">'<tt>switch</tt>' Instruction</a>
1837 <div class="doc_text">
1841 switch <intty> <value>, label <defaultdest> [ <intty> <val>, label <dest> ... ]
1846 <p>The '<tt>switch</tt>' instruction is used to transfer control flow to one of
1847 several different places. It is a generalization of the '<tt>br</tt>'
1848 instruction, allowing a branch to occur to one of many possible
1854 <p>The '<tt>switch</tt>' instruction uses three parameters: an integer
1855 comparison value '<tt>value</tt>', a default '<tt>label</tt>' destination, and
1856 an array of pairs of comparison value constants and '<tt>label</tt>'s. The
1857 table is not allowed to contain duplicate constant entries.</p>
1861 <p>The <tt>switch</tt> instruction specifies a table of values and
1862 destinations. When the '<tt>switch</tt>' instruction is executed, this
1863 table is searched for the given value. If the value is found, control flow is
1864 transfered to the corresponding destination; otherwise, control flow is
1865 transfered to the default destination.</p>
1867 <h5>Implementation:</h5>
1869 <p>Depending on properties of the target machine and the particular
1870 <tt>switch</tt> instruction, this instruction may be code generated in different
1871 ways. For example, it could be generated as a series of chained conditional
1872 branches or with a lookup table.</p>
1877 <i>; Emulate a conditional br instruction</i>
1878 %Val = <a href="#i_zext">zext</a> i1 %value to i32
1879 switch i32 %Val, label %truedest [i32 0, label %falsedest ]
1881 <i>; Emulate an unconditional br instruction</i>
1882 switch i32 0, label %dest [ ]
1884 <i>; Implement a jump table:</i>
1885 switch i32 %val, label %otherwise [ i32 0, label %onzero
1887 i32 2, label %ontwo ]
1891 <!-- _______________________________________________________________________ -->
1892 <div class="doc_subsubsection">
1893 <a name="i_invoke">'<tt>invoke</tt>' Instruction</a>
1896 <div class="doc_text">
1901 <result> = invoke [<a href="#callingconv">cconv</a>] <ptr to function ty> %<function ptr val>(<function args>)
1902 to label <normal label> unwind label <exception label>
1907 <p>The '<tt>invoke</tt>' instruction causes control to transfer to a specified
1908 function, with the possibility of control flow transfer to either the
1909 '<tt>normal</tt>' label or the
1910 '<tt>exception</tt>' label. If the callee function returns with the
1911 "<tt><a href="#i_ret">ret</a></tt>" instruction, control flow will return to the
1912 "normal" label. If the callee (or any indirect callees) returns with the "<a
1913 href="#i_unwind"><tt>unwind</tt></a>" instruction, control is interrupted and
1914 continued at the dynamically nearest "exception" label.</p>
1918 <p>This instruction requires several arguments:</p>
1922 The optional "cconv" marker indicates which <a href="#callingconv">calling
1923 convention</a> the call should use. If none is specified, the call defaults
1924 to using C calling conventions.
1926 <li>'<tt>ptr to function ty</tt>': shall be the signature of the pointer to
1927 function value being invoked. In most cases, this is a direct function
1928 invocation, but indirect <tt>invoke</tt>s are just as possible, branching off
1929 an arbitrary pointer to function value.
1932 <li>'<tt>function ptr val</tt>': An LLVM value containing a pointer to a
1933 function to be invoked. </li>
1935 <li>'<tt>function args</tt>': argument list whose types match the function
1936 signature argument types. If the function signature indicates the function
1937 accepts a variable number of arguments, the extra arguments can be
1940 <li>'<tt>normal label</tt>': the label reached when the called function
1941 executes a '<tt><a href="#i_ret">ret</a></tt>' instruction. </li>
1943 <li>'<tt>exception label</tt>': the label reached when a callee returns with
1944 the <a href="#i_unwind"><tt>unwind</tt></a> instruction. </li>
1950 <p>This instruction is designed to operate as a standard '<tt><a
1951 href="#i_call">call</a></tt>' instruction in most regards. The primary
1952 difference is that it establishes an association with a label, which is used by
1953 the runtime library to unwind the stack.</p>
1955 <p>This instruction is used in languages with destructors to ensure that proper
1956 cleanup is performed in the case of either a <tt>longjmp</tt> or a thrown
1957 exception. Additionally, this is important for implementation of
1958 '<tt>catch</tt>' clauses in high-level languages that support them.</p>
1962 %retval = invoke i32 %Test(i32 15) to label %Continue
1963 unwind label %TestCleanup <i>; {i32}:retval set</i>
1964 %retval = invoke <a href="#callingconv">coldcc</a> i32 %Test(i32 15) to label %Continue
1965 unwind label %TestCleanup <i>; {i32}:retval set</i>
1970 <!-- _______________________________________________________________________ -->
1972 <div class="doc_subsubsection"> <a name="i_unwind">'<tt>unwind</tt>'
1973 Instruction</a> </div>
1975 <div class="doc_text">
1984 <p>The '<tt>unwind</tt>' instruction unwinds the stack, continuing control flow
1985 at the first callee in the dynamic call stack which used an <a
1986 href="#i_invoke"><tt>invoke</tt></a> instruction to perform the call. This is
1987 primarily used to implement exception handling.</p>
1991 <p>The '<tt>unwind</tt>' intrinsic causes execution of the current function to
1992 immediately halt. The dynamic call stack is then searched for the first <a
1993 href="#i_invoke"><tt>invoke</tt></a> instruction on the call stack. Once found,
1994 execution continues at the "exceptional" destination block specified by the
1995 <tt>invoke</tt> instruction. If there is no <tt>invoke</tt> instruction in the
1996 dynamic call chain, undefined behavior results.</p>
1999 <!-- _______________________________________________________________________ -->
2001 <div class="doc_subsubsection"> <a name="i_unreachable">'<tt>unreachable</tt>'
2002 Instruction</a> </div>
2004 <div class="doc_text">
2013 <p>The '<tt>unreachable</tt>' instruction has no defined semantics. This
2014 instruction is used to inform the optimizer that a particular portion of the
2015 code is not reachable. This can be used to indicate that the code after a
2016 no-return function cannot be reached, and other facts.</p>
2020 <p>The '<tt>unreachable</tt>' instruction has no defined semantics.</p>
2025 <!-- ======================================================================= -->
2026 <div class="doc_subsection"> <a name="binaryops">Binary Operations</a> </div>
2027 <div class="doc_text">
2028 <p>Binary operators are used to do most of the computation in a
2029 program. They require two operands, execute an operation on them, and
2030 produce a single value. The operands might represent
2031 multiple data, as is the case with the <a href="#t_vector">vector</a> data type.
2032 The result value of a binary operator is not
2033 necessarily the same type as its operands.</p>
2034 <p>There are several different binary operators:</p>
2036 <!-- _______________________________________________________________________ -->
2037 <div class="doc_subsubsection"> <a name="i_add">'<tt>add</tt>'
2038 Instruction</a> </div>
2039 <div class="doc_text">
2041 <pre> <result> = add <ty> <var1>, <var2> <i>; yields {ty}:result</i>
2044 <p>The '<tt>add</tt>' instruction returns the sum of its two operands.</p>
2046 <p>The two arguments to the '<tt>add</tt>' instruction must be either <a
2047 href="#t_integer">integer</a> or <a href="#t_floating">floating point</a> values.
2048 This instruction can also take <a href="#t_vector">vector</a> versions of the values.
2049 Both arguments must have identical types.</p>
2051 <p>The value produced is the integer or floating point sum of the two
2054 <pre> <result> = add i32 4, %var <i>; yields {i32}:result = 4 + %var</i>
2057 <!-- _______________________________________________________________________ -->
2058 <div class="doc_subsubsection"> <a name="i_sub">'<tt>sub</tt>'
2059 Instruction</a> </div>
2060 <div class="doc_text">
2062 <pre> <result> = sub <ty> <var1>, <var2> <i>; yields {ty}:result</i>
2065 <p>The '<tt>sub</tt>' instruction returns the difference of its two
2067 <p>Note that the '<tt>sub</tt>' instruction is used to represent the '<tt>neg</tt>'
2068 instruction present in most other intermediate representations.</p>
2070 <p>The two arguments to the '<tt>sub</tt>' instruction must be either <a
2071 href="#t_integer">integer</a> or <a href="#t_floating">floating point</a>
2073 This instruction can also take <a href="#t_vector">vector</a> versions of the values.
2074 Both arguments must have identical types.</p>
2076 <p>The value produced is the integer or floating point difference of
2077 the two operands.</p>
2080 <result> = sub i32 4, %var <i>; yields {i32}:result = 4 - %var</i>
2081 <result> = sub i32 0, %val <i>; yields {i32}:result = -%var</i>
2084 <!-- _______________________________________________________________________ -->
2085 <div class="doc_subsubsection"> <a name="i_mul">'<tt>mul</tt>'
2086 Instruction</a> </div>
2087 <div class="doc_text">
2089 <pre> <result> = mul <ty> <var1>, <var2> <i>; yields {ty}:result</i>
2092 <p>The '<tt>mul</tt>' instruction returns the product of its two
2095 <p>The two arguments to the '<tt>mul</tt>' instruction must be either <a
2096 href="#t_integer">integer</a> or <a href="#t_floating">floating point</a>
2098 This instruction can also take <a href="#t_vector">vector</a> versions of the values.
2099 Both arguments must have identical types.</p>
2101 <p>The value produced is the integer or floating point product of the
2103 <p>Because the operands are the same width, the result of an integer
2104 multiplication is the same whether the operands should be deemed unsigned or
2107 <pre> <result> = mul i32 4, %var <i>; yields {i32}:result = 4 * %var</i>
2110 <!-- _______________________________________________________________________ -->
2111 <div class="doc_subsubsection"> <a name="i_udiv">'<tt>udiv</tt>' Instruction
2113 <div class="doc_text">
2115 <pre> <result> = udiv <ty> <var1>, <var2> <i>; yields {ty}:result</i>
2118 <p>The '<tt>udiv</tt>' instruction returns the quotient of its two
2121 <p>The two arguments to the '<tt>udiv</tt>' instruction must be
2122 <a href="#t_integer">integer</a> values. Both arguments must have identical
2123 types. This instruction can also take <a href="#t_vector">vector</a> versions
2124 of the values in which case the elements must be integers.</p>
2126 <p>The value produced is the unsigned integer quotient of the two operands. This
2127 instruction always performs an unsigned division operation, regardless of
2128 whether the arguments are unsigned or not.</p>
2130 <pre> <result> = udiv i32 4, %var <i>; yields {i32}:result = 4 / %var</i>
2133 <!-- _______________________________________________________________________ -->
2134 <div class="doc_subsubsection"> <a name="i_sdiv">'<tt>sdiv</tt>' Instruction
2136 <div class="doc_text">
2138 <pre> <result> = sdiv <ty> <var1>, <var2> <i>; yields {ty}:result</i>
2141 <p>The '<tt>sdiv</tt>' instruction returns the quotient of its two
2144 <p>The two arguments to the '<tt>sdiv</tt>' instruction must be
2145 <a href="#t_integer">integer</a> values. Both arguments must have identical
2146 types. This instruction can also take <a href="#t_vector">vector</a> versions
2147 of the values in which case the elements must be integers.</p>
2149 <p>The value produced is the signed integer quotient of the two operands. This
2150 instruction always performs a signed division operation, regardless of whether
2151 the arguments are signed or not.</p>
2153 <pre> <result> = sdiv i32 4, %var <i>; yields {i32}:result = 4 / %var</i>
2156 <!-- _______________________________________________________________________ -->
2157 <div class="doc_subsubsection"> <a name="i_fdiv">'<tt>fdiv</tt>'
2158 Instruction</a> </div>
2159 <div class="doc_text">
2161 <pre> <result> = fdiv <ty> <var1>, <var2> <i>; yields {ty}:result</i>
2164 <p>The '<tt>fdiv</tt>' instruction returns the quotient of its two
2167 <p>The two arguments to the '<tt>fdiv</tt>' instruction must be
2168 <a href="#t_floating">floating point</a> values. Both arguments must have
2169 identical types. This instruction can also take <a href="#t_vector">vector</a>
2170 versions of floating point values.</p>
2172 <p>The value produced is the floating point quotient of the two operands.</p>
2174 <pre> <result> = fdiv float 4.0, %var <i>; yields {float}:result = 4.0 / %var</i>
2177 <!-- _______________________________________________________________________ -->
2178 <div class="doc_subsubsection"> <a name="i_urem">'<tt>urem</tt>' Instruction</a>
2180 <div class="doc_text">
2182 <pre> <result> = urem <ty> <var1>, <var2> <i>; yields {ty}:result</i>
2185 <p>The '<tt>urem</tt>' instruction returns the remainder from the
2186 unsigned division of its two arguments.</p>
2188 <p>The two arguments to the '<tt>urem</tt>' instruction must be
2189 <a href="#t_integer">integer</a> values. Both arguments must have identical
2190 types. This instruction can also take <a href="#t_vector">vector</a> versions
2191 of the values in which case the elements must be integers.</p>
2193 <p>This instruction returns the unsigned integer <i>remainder</i> of a division.
2194 This instruction always performs an unsigned division to get the remainder,
2195 regardless of whether the arguments are unsigned or not.</p>
2197 <pre> <result> = urem i32 4, %var <i>; yields {i32}:result = 4 % %var</i>
2201 <!-- _______________________________________________________________________ -->
2202 <div class="doc_subsubsection"> <a name="i_srem">'<tt>srem</tt>'
2203 Instruction</a> </div>
2204 <div class="doc_text">
2206 <pre> <result> = srem <ty> <var1>, <var2> <i>; yields {ty}:result</i>
2209 <p>The '<tt>srem</tt>' instruction returns the remainder from the
2210 signed division of its two operands. This instruction can also take
2211 <a href="#t_vector">vector</a> versions of the values in which case
2212 the elements must be integers.</p>
2215 <p>The two arguments to the '<tt>srem</tt>' instruction must be
2216 <a href="#t_integer">integer</a> values. Both arguments must have identical
2219 <p>This instruction returns the <i>remainder</i> of a division (where the result
2220 has the same sign as the dividend, <tt>var1</tt>), not the <i>modulo</i>
2221 operator (where the result has the same sign as the divisor, <tt>var2</tt>) of
2222 a value. For more information about the difference, see <a
2223 href="http://mathforum.org/dr.math/problems/anne.4.28.99.html">The
2224 Math Forum</a>. For a table of how this is implemented in various languages,
2225 please see <a href="http://en.wikipedia.org/wiki/Modulo_operation">
2226 Wikipedia: modulo operation</a>.</p>
2228 <pre> <result> = srem i32 4, %var <i>; yields {i32}:result = 4 % %var</i>
2232 <!-- _______________________________________________________________________ -->
2233 <div class="doc_subsubsection"> <a name="i_frem">'<tt>frem</tt>'
2234 Instruction</a> </div>
2235 <div class="doc_text">
2237 <pre> <result> = frem <ty> <var1>, <var2> <i>; yields {ty}:result</i>
2240 <p>The '<tt>frem</tt>' instruction returns the remainder from the
2241 division of its two operands.</p>
2243 <p>The two arguments to the '<tt>frem</tt>' instruction must be
2244 <a href="#t_floating">floating point</a> values. Both arguments must have
2245 identical types. This instruction can also take <a href="#t_vector">vector</a>
2246 versions of floating point values.</p>
2248 <p>This instruction returns the <i>remainder</i> of a division.</p>
2250 <pre> <result> = frem float 4.0, %var <i>; yields {float}:result = 4.0 % %var</i>
2254 <!-- ======================================================================= -->
2255 <div class="doc_subsection"> <a name="bitwiseops">Bitwise Binary
2256 Operations</a> </div>
2257 <div class="doc_text">
2258 <p>Bitwise binary operators are used to do various forms of
2259 bit-twiddling in a program. They are generally very efficient
2260 instructions and can commonly be strength reduced from other
2261 instructions. They require two operands, execute an operation on them,
2262 and produce a single value. The resulting value of the bitwise binary
2263 operators is always the same type as its first operand.</p>
2266 <!-- _______________________________________________________________________ -->
2267 <div class="doc_subsubsection"> <a name="i_shl">'<tt>shl</tt>'
2268 Instruction</a> </div>
2269 <div class="doc_text">
2271 <pre> <result> = shl <ty> <var1>, <var2> <i>; yields {ty}:result</i>
2276 <p>The '<tt>shl</tt>' instruction returns the first operand shifted to
2277 the left a specified number of bits.</p>
2281 <p>Both arguments to the '<tt>shl</tt>' instruction must be the same <a
2282 href="#t_integer">integer</a> type.</p>
2286 <p>The value produced is <tt>var1</tt> * 2<sup><tt>var2</tt></sup>. If
2287 <tt>var2</tt> is (statically or dynamically) equal to or larger than the number
2288 of bits in <tt>var1</tt>, the result is undefined.</p>
2290 <h5>Example:</h5><pre>
2291 <result> = shl i32 4, %var <i>; yields {i32}: 4 << %var</i>
2292 <result> = shl i32 4, 2 <i>; yields {i32}: 16</i>
2293 <result> = shl i32 1, 10 <i>; yields {i32}: 1024</i>
2294 <result> = shl i32 1, 32 <i>; undefined</i>
2297 <!-- _______________________________________________________________________ -->
2298 <div class="doc_subsubsection"> <a name="i_lshr">'<tt>lshr</tt>'
2299 Instruction</a> </div>
2300 <div class="doc_text">
2302 <pre> <result> = lshr <ty> <var1>, <var2> <i>; yields {ty}:result</i>
2306 <p>The '<tt>lshr</tt>' instruction (logical shift right) returns the first
2307 operand shifted to the right a specified number of bits with zero fill.</p>
2310 <p>Both arguments to the '<tt>lshr</tt>' instruction must be the same
2311 <a href="#t_integer">integer</a> type.</p>
2315 <p>This instruction always performs a logical shift right operation. The most
2316 significant bits of the result will be filled with zero bits after the
2317 shift. If <tt>var2</tt> is (statically or dynamically) equal to or larger than
2318 the number of bits in <tt>var1</tt>, the result is undefined.</p>
2322 <result> = lshr i32 4, 1 <i>; yields {i32}:result = 2</i>
2323 <result> = lshr i32 4, 2 <i>; yields {i32}:result = 1</i>
2324 <result> = lshr i8 4, 3 <i>; yields {i8}:result = 0</i>
2325 <result> = lshr i8 -2, 1 <i>; yields {i8}:result = 0x7FFFFFFF </i>
2326 <result> = lshr i32 1, 32 <i>; undefined</i>
2330 <!-- _______________________________________________________________________ -->
2331 <div class="doc_subsubsection"> <a name="i_ashr">'<tt>ashr</tt>'
2332 Instruction</a> </div>
2333 <div class="doc_text">
2336 <pre> <result> = ashr <ty> <var1>, <var2> <i>; yields {ty}:result</i>
2340 <p>The '<tt>ashr</tt>' instruction (arithmetic shift right) returns the first
2341 operand shifted to the right a specified number of bits with sign extension.</p>
2344 <p>Both arguments to the '<tt>ashr</tt>' instruction must be the same
2345 <a href="#t_integer">integer</a> type.</p>
2348 <p>This instruction always performs an arithmetic shift right operation,
2349 The most significant bits of the result will be filled with the sign bit
2350 of <tt>var1</tt>. If <tt>var2</tt> is (statically or dynamically) equal to or
2351 larger than the number of bits in <tt>var1</tt>, the result is undefined.
2356 <result> = ashr i32 4, 1 <i>; yields {i32}:result = 2</i>
2357 <result> = ashr i32 4, 2 <i>; yields {i32}:result = 1</i>
2358 <result> = ashr i8 4, 3 <i>; yields {i8}:result = 0</i>
2359 <result> = ashr i8 -2, 1 <i>; yields {i8}:result = -1</i>
2360 <result> = ashr i32 1, 32 <i>; undefined</i>
2364 <!-- _______________________________________________________________________ -->
2365 <div class="doc_subsubsection"> <a name="i_and">'<tt>and</tt>'
2366 Instruction</a> </div>
2367 <div class="doc_text">
2369 <pre> <result> = and <ty> <var1>, <var2> <i>; yields {ty}:result</i>
2372 <p>The '<tt>and</tt>' instruction returns the bitwise logical and of
2373 its two operands.</p>
2375 <p>The two arguments to the '<tt>and</tt>' instruction must be <a
2376 href="#t_integer">integer</a> values. Both arguments must have
2377 identical types.</p>
2379 <p>The truth table used for the '<tt>and</tt>' instruction is:</p>
2381 <div style="align: center">
2382 <table border="1" cellspacing="0" cellpadding="4">
2413 <pre> <result> = and i32 4, %var <i>; yields {i32}:result = 4 & %var</i>
2414 <result> = and i32 15, 40 <i>; yields {i32}:result = 8</i>
2415 <result> = and i32 4, 8 <i>; yields {i32}:result = 0</i>
2418 <!-- _______________________________________________________________________ -->
2419 <div class="doc_subsubsection"> <a name="i_or">'<tt>or</tt>' Instruction</a> </div>
2420 <div class="doc_text">
2422 <pre> <result> = or <ty> <var1>, <var2> <i>; yields {ty}:result</i>
2425 <p>The '<tt>or</tt>' instruction returns the bitwise logical inclusive
2426 or of its two operands.</p>
2428 <p>The two arguments to the '<tt>or</tt>' instruction must be <a
2429 href="#t_integer">integer</a> values. Both arguments must have
2430 identical types.</p>
2432 <p>The truth table used for the '<tt>or</tt>' instruction is:</p>
2434 <div style="align: center">
2435 <table border="1" cellspacing="0" cellpadding="4">
2466 <pre> <result> = or i32 4, %var <i>; yields {i32}:result = 4 | %var</i>
2467 <result> = or i32 15, 40 <i>; yields {i32}:result = 47</i>
2468 <result> = or i32 4, 8 <i>; yields {i32}:result = 12</i>
2471 <!-- _______________________________________________________________________ -->
2472 <div class="doc_subsubsection"> <a name="i_xor">'<tt>xor</tt>'
2473 Instruction</a> </div>
2474 <div class="doc_text">
2476 <pre> <result> = xor <ty> <var1>, <var2> <i>; yields {ty}:result</i>
2479 <p>The '<tt>xor</tt>' instruction returns the bitwise logical exclusive
2480 or of its two operands. The <tt>xor</tt> is used to implement the
2481 "one's complement" operation, which is the "~" operator in C.</p>
2483 <p>The two arguments to the '<tt>xor</tt>' instruction must be <a
2484 href="#t_integer">integer</a> values. Both arguments must have
2485 identical types.</p>
2487 <p>The truth table used for the '<tt>xor</tt>' instruction is:</p>
2489 <div style="align: center">
2490 <table border="1" cellspacing="0" cellpadding="4">
2522 <pre> <result> = xor i32 4, %var <i>; yields {i32}:result = 4 ^ %var</i>
2523 <result> = xor i32 15, 40 <i>; yields {i32}:result = 39</i>
2524 <result> = xor i32 4, 8 <i>; yields {i32}:result = 12</i>
2525 <result> = xor i32 %V, -1 <i>; yields {i32}:result = ~%V</i>
2529 <!-- ======================================================================= -->
2530 <div class="doc_subsection">
2531 <a name="vectorops">Vector Operations</a>
2534 <div class="doc_text">
2536 <p>LLVM supports several instructions to represent vector operations in a
2537 target-independent manner. These instructions cover the element-access and
2538 vector-specific operations needed to process vectors effectively. While LLVM
2539 does directly support these vector operations, many sophisticated algorithms
2540 will want to use target-specific intrinsics to take full advantage of a specific
2545 <!-- _______________________________________________________________________ -->
2546 <div class="doc_subsubsection">
2547 <a name="i_extractelement">'<tt>extractelement</tt>' Instruction</a>
2550 <div class="doc_text">
2555 <result> = extractelement <n x <ty>> <val>, i32 <idx> <i>; yields <ty></i>
2561 The '<tt>extractelement</tt>' instruction extracts a single scalar
2562 element from a vector at a specified index.
2569 The first operand of an '<tt>extractelement</tt>' instruction is a
2570 value of <a href="#t_vector">vector</a> type. The second operand is
2571 an index indicating the position from which to extract the element.
2572 The index may be a variable.</p>
2577 The result is a scalar of the same type as the element type of
2578 <tt>val</tt>. Its value is the value at position <tt>idx</tt> of
2579 <tt>val</tt>. If <tt>idx</tt> exceeds the length of <tt>val</tt>, the
2580 results are undefined.
2586 %result = extractelement <4 x i32> %vec, i32 0 <i>; yields i32</i>
2591 <!-- _______________________________________________________________________ -->
2592 <div class="doc_subsubsection">
2593 <a name="i_insertelement">'<tt>insertelement</tt>' Instruction</a>
2596 <div class="doc_text">
2601 <result> = insertelement <n x <ty>> <val>, <ty> <elt>, i32 <idx> <i>; yields <n x <ty>></i>
2607 The '<tt>insertelement</tt>' instruction inserts a scalar
2608 element into a vector at a specified index.
2615 The first operand of an '<tt>insertelement</tt>' instruction is a
2616 value of <a href="#t_vector">vector</a> type. The second operand is a
2617 scalar value whose type must equal the element type of the first
2618 operand. The third operand is an index indicating the position at
2619 which to insert the value. The index may be a variable.</p>
2624 The result is a vector of the same type as <tt>val</tt>. Its
2625 element values are those of <tt>val</tt> except at position
2626 <tt>idx</tt>, where it gets the value <tt>elt</tt>. If <tt>idx</tt>
2627 exceeds the length of <tt>val</tt>, the results are undefined.
2633 %result = insertelement <4 x i32> %vec, i32 1, i32 0 <i>; yields <4 x i32></i>
2637 <!-- _______________________________________________________________________ -->
2638 <div class="doc_subsubsection">
2639 <a name="i_shufflevector">'<tt>shufflevector</tt>' Instruction</a>
2642 <div class="doc_text">
2647 <result> = shufflevector <n x <ty>> <v1>, <n x <ty>> <v2>, <n x i32> <mask> <i>; yields <n x <ty>></i>
2653 The '<tt>shufflevector</tt>' instruction constructs a permutation of elements
2654 from two input vectors, returning a vector of the same type.
2660 The first two operands of a '<tt>shufflevector</tt>' instruction are vectors
2661 with types that match each other and types that match the result of the
2662 instruction. The third argument is a shuffle mask, which has the same number
2663 of elements as the other vector type, but whose element type is always 'i32'.
2667 The shuffle mask operand is required to be a constant vector with either
2668 constant integer or undef values.
2674 The elements of the two input vectors are numbered from left to right across
2675 both of the vectors. The shuffle mask operand specifies, for each element of
2676 the result vector, which element of the two input registers the result element
2677 gets. The element selector may be undef (meaning "don't care") and the second
2678 operand may be undef if performing a shuffle from only one vector.
2684 %result = shufflevector <4 x i32> %v1, <4 x i32> %v2,
2685 <4 x i32> <i32 0, i32 4, i32 1, i32 5> <i>; yields <4 x i32></i>
2686 %result = shufflevector <4 x i32> %v1, <4 x i32> undef,
2687 <4 x i32> <i32 0, i32 1, i32 2, i32 3> <i>; yields <4 x i32></i> - Identity shuffle.
2692 <!-- ======================================================================= -->
2693 <div class="doc_subsection">
2694 <a name="memoryops">Memory Access and Addressing Operations</a>
2697 <div class="doc_text">
2699 <p>A key design point of an SSA-based representation is how it
2700 represents memory. In LLVM, no memory locations are in SSA form, which
2701 makes things very simple. This section describes how to read, write,
2702 allocate, and free memory in LLVM.</p>
2706 <!-- _______________________________________________________________________ -->
2707 <div class="doc_subsubsection">
2708 <a name="i_malloc">'<tt>malloc</tt>' Instruction</a>
2711 <div class="doc_text">
2716 <result> = malloc <type>[, i32 <NumElements>][, align <alignment>] <i>; yields {type*}:result</i>
2721 <p>The '<tt>malloc</tt>' instruction allocates memory from the system
2722 heap and returns a pointer to it. The object is always allocated in the generic
2723 address space (address space zero).</p>
2727 <p>The '<tt>malloc</tt>' instruction allocates
2728 <tt>sizeof(<type>)*NumElements</tt>
2729 bytes of memory from the operating system and returns a pointer of the
2730 appropriate type to the program. If "NumElements" is specified, it is the
2731 number of elements allocated. If an alignment is specified, the value result
2732 of the allocation is guaranteed to be aligned to at least that boundary. If
2733 not specified, or if zero, the target can choose to align the allocation on any
2734 convenient boundary.</p>
2736 <p>'<tt>type</tt>' must be a sized type.</p>
2740 <p>Memory is allocated using the system "<tt>malloc</tt>" function, and
2741 a pointer is returned.</p>
2746 %array = malloc [4 x i8 ] <i>; yields {[%4 x i8]*}:array</i>
2748 %size = <a href="#i_add">add</a> i32 2, 2 <i>; yields {i32}:size = i32 4</i>
2749 %array1 = malloc i8, i32 4 <i>; yields {i8*}:array1</i>
2750 %array2 = malloc [12 x i8], i32 %size <i>; yields {[12 x i8]*}:array2</i>
2751 %array3 = malloc i32, i32 4, align 1024 <i>; yields {i32*}:array3</i>
2752 %array4 = malloc i32, align 1024 <i>; yields {i32*}:array4</i>
2756 <!-- _______________________________________________________________________ -->
2757 <div class="doc_subsubsection">
2758 <a name="i_free">'<tt>free</tt>' Instruction</a>
2761 <div class="doc_text">
2766 free <type> <value> <i>; yields {void}</i>
2771 <p>The '<tt>free</tt>' instruction returns memory back to the unused
2772 memory heap to be reallocated in the future.</p>
2776 <p>'<tt>value</tt>' shall be a pointer value that points to a value
2777 that was allocated with the '<tt><a href="#i_malloc">malloc</a></tt>'
2782 <p>Access to the memory pointed to by the pointer is no longer defined
2783 after this instruction executes.</p>
2788 %array = <a href="#i_malloc">malloc</a> [4 x i8] <i>; yields {[4 x i8]*}:array</i>
2789 free [4 x i8]* %array
2793 <!-- _______________________________________________________________________ -->
2794 <div class="doc_subsubsection">
2795 <a name="i_alloca">'<tt>alloca</tt>' Instruction</a>
2798 <div class="doc_text">
2803 <result> = alloca <type>[, i32 <NumElements>][, align <alignment>] <i>; yields {type*}:result</i>
2808 <p>The '<tt>alloca</tt>' instruction allocates memory on the stack frame of the
2809 currently executing function, to be automatically released when this function
2810 returns to its caller. The object is always allocated in the generic address
2811 space (address space zero).</p>
2815 <p>The '<tt>alloca</tt>' instruction allocates <tt>sizeof(<type>)*NumElements</tt>
2816 bytes of memory on the runtime stack, returning a pointer of the
2817 appropriate type to the program. If "NumElements" is specified, it is the
2818 number of elements allocated. If an alignment is specified, the value result
2819 of the allocation is guaranteed to be aligned to at least that boundary. If
2820 not specified, or if zero, the target can choose to align the allocation on any
2821 convenient boundary.</p>
2823 <p>'<tt>type</tt>' may be any sized type.</p>
2827 <p>Memory is allocated; a pointer is returned. '<tt>alloca</tt>'d
2828 memory is automatically released when the function returns. The '<tt>alloca</tt>'
2829 instruction is commonly used to represent automatic variables that must
2830 have an address available. When the function returns (either with the <tt><a
2831 href="#i_ret">ret</a></tt> or <tt><a href="#i_unwind">unwind</a></tt>
2832 instructions), the memory is reclaimed.</p>
2837 %ptr = alloca i32 <i>; yields {i32*}:ptr</i>
2838 %ptr = alloca i32, i32 4 <i>; yields {i32*}:ptr</i>
2839 %ptr = alloca i32, i32 4, align 1024 <i>; yields {i32*}:ptr</i>
2840 %ptr = alloca i32, align 1024 <i>; yields {i32*}:ptr</i>
2844 <!-- _______________________________________________________________________ -->
2845 <div class="doc_subsubsection"> <a name="i_load">'<tt>load</tt>'
2846 Instruction</a> </div>
2847 <div class="doc_text">
2849 <pre> <result> = load <ty>* <pointer>[, align <alignment>]<br> <result> = volatile load <ty>* <pointer>[, align <alignment>]<br></pre>
2851 <p>The '<tt>load</tt>' instruction is used to read from memory.</p>
2853 <p>The argument to the '<tt>load</tt>' instruction specifies the memory
2854 address from which to load. The pointer must point to a <a
2855 href="#t_firstclass">first class</a> type. If the <tt>load</tt> is
2856 marked as <tt>volatile</tt>, then the optimizer is not allowed to modify
2857 the number or order of execution of this <tt>load</tt> with other
2858 volatile <tt>load</tt> and <tt><a href="#i_store">store</a></tt>
2861 The optional "align" argument specifies the alignment of the operation
2862 (that is, the alignment of the memory address). A value of 0 or an
2863 omitted "align" argument means that the operation has the preferential
2864 alignment for the target. It is the responsibility of the code emitter
2865 to ensure that the alignment information is correct. Overestimating
2866 the alignment results in an undefined behavior. Underestimating the
2867 alignment may produce less efficient code. An alignment of 1 is always
2871 <p>The location of memory pointed to is loaded.</p>
2873 <pre> %ptr = <a href="#i_alloca">alloca</a> i32 <i>; yields {i32*}:ptr</i>
2875 href="#i_store">store</a> i32 3, i32* %ptr <i>; yields {void}</i>
2876 %val = load i32* %ptr <i>; yields {i32}:val = i32 3</i>
2879 <!-- _______________________________________________________________________ -->
2880 <div class="doc_subsubsection"> <a name="i_store">'<tt>store</tt>'
2881 Instruction</a> </div>
2882 <div class="doc_text">
2884 <pre> store <ty> <value>, <ty>* <pointer>[, align <alignment>] <i>; yields {void}</i>
2885 volatile store <ty> <value>, <ty>* <pointer>[, align <alignment>] <i>; yields {void}</i>
2888 <p>The '<tt>store</tt>' instruction is used to write to memory.</p>
2890 <p>There are two arguments to the '<tt>store</tt>' instruction: a value
2891 to store and an address at which to store it. The type of the '<tt><pointer></tt>'
2892 operand must be a pointer to the type of the '<tt><value></tt>'
2893 operand. If the <tt>store</tt> is marked as <tt>volatile</tt>, then the
2894 optimizer is not allowed to modify the number or order of execution of
2895 this <tt>store</tt> with other volatile <tt>load</tt> and <tt><a
2896 href="#i_store">store</a></tt> instructions.</p>
2898 The optional "align" argument specifies the alignment of the operation
2899 (that is, the alignment of the memory address). A value of 0 or an
2900 omitted "align" argument means that the operation has the preferential
2901 alignment for the target. It is the responsibility of the code emitter
2902 to ensure that the alignment information is correct. Overestimating
2903 the alignment results in an undefined behavior. Underestimating the
2904 alignment may produce less efficient code. An alignment of 1 is always
2908 <p>The contents of memory are updated to contain '<tt><value></tt>'
2909 at the location specified by the '<tt><pointer></tt>' operand.</p>
2911 <pre> %ptr = <a href="#i_alloca">alloca</a> i32 <i>; yields {i32*}:ptr</i>
2912 store i32 3, i32* %ptr <i>; yields {void}</i>
2913 %val = <a href="#i_load">load</a> i32* %ptr <i>; yields {i32}:val = i32 3</i>
2917 <!-- _______________________________________________________________________ -->
2918 <div class="doc_subsubsection">
2919 <a name="i_getelementptr">'<tt>getelementptr</tt>' Instruction</a>
2922 <div class="doc_text">
2925 <result> = getelementptr <ty>* <ptrval>{, <ty> <idx>}*
2931 The '<tt>getelementptr</tt>' instruction is used to get the address of a
2932 subelement of an aggregate data structure.</p>
2936 <p>This instruction takes a list of integer operands that indicate what
2937 elements of the aggregate object to index to. The actual types of the arguments
2938 provided depend on the type of the first pointer argument. The
2939 '<tt>getelementptr</tt>' instruction is used to index down through the type
2940 levels of a structure or to a specific index in an array. When indexing into a
2941 structure, only <tt>i32</tt> integer constants are allowed. When indexing
2942 into an array or pointer, only integers of 32 or 64 bits are allowed, and will
2943 be sign extended to 64-bit values.</p>
2945 <p>For example, let's consider a C code fragment and how it gets
2946 compiled to LLVM:</p>
2948 <div class="doc_code">
2961 int *foo(struct ST *s) {
2962 return &s[1].Z.B[5][13];
2967 <p>The LLVM code generated by the GCC frontend is:</p>
2969 <div class="doc_code">
2971 %RT = type { i8 , [10 x [20 x i32]], i8 }
2972 %ST = type { i32, double, %RT }
2974 define i32* %foo(%ST* %s) {
2976 %reg = getelementptr %ST* %s, i32 1, i32 2, i32 1, i32 5, i32 13
2984 <p>The index types specified for the '<tt>getelementptr</tt>' instruction depend
2985 on the pointer type that is being indexed into. <a href="#t_pointer">Pointer</a>
2986 and <a href="#t_array">array</a> types can use a 32-bit or 64-bit
2987 <a href="#t_integer">integer</a> type but the value will always be sign extended
2988 to 64-bits. <a href="#t_struct">Structure</a> types require <tt>i32</tt>
2989 <b>constants</b>.</p>
2991 <p>In the example above, the first index is indexing into the '<tt>%ST*</tt>'
2992 type, which is a pointer, yielding a '<tt>%ST</tt>' = '<tt>{ i32, double, %RT
2993 }</tt>' type, a structure. The second index indexes into the third element of
2994 the structure, yielding a '<tt>%RT</tt>' = '<tt>{ i8 , [10 x [20 x i32]],
2995 i8 }</tt>' type, another structure. The third index indexes into the second
2996 element of the structure, yielding a '<tt>[10 x [20 x i32]]</tt>' type, an
2997 array. The two dimensions of the array are subscripted into, yielding an
2998 '<tt>i32</tt>' type. The '<tt>getelementptr</tt>' instruction returns a pointer
2999 to this element, thus computing a value of '<tt>i32*</tt>' type.</p>
3001 <p>Note that it is perfectly legal to index partially through a
3002 structure, returning a pointer to an inner element. Because of this,
3003 the LLVM code for the given testcase is equivalent to:</p>
3006 define i32* %foo(%ST* %s) {
3007 %t1 = getelementptr %ST* %s, i32 1 <i>; yields %ST*:%t1</i>
3008 %t2 = getelementptr %ST* %t1, i32 0, i32 2 <i>; yields %RT*:%t2</i>
3009 %t3 = getelementptr %RT* %t2, i32 0, i32 1 <i>; yields [10 x [20 x i32]]*:%t3</i>
3010 %t4 = getelementptr [10 x [20 x i32]]* %t3, i32 0, i32 5 <i>; yields [20 x i32]*:%t4</i>
3011 %t5 = getelementptr [20 x i32]* %t4, i32 0, i32 13 <i>; yields i32*:%t5</i>
3016 <p>Note that it is undefined to access an array out of bounds: array and
3017 pointer indexes must always be within the defined bounds of the array type.
3018 The one exception for this rules is zero length arrays. These arrays are
3019 defined to be accessible as variable length arrays, which requires access
3020 beyond the zero'th element.</p>
3022 <p>The getelementptr instruction is often confusing. For some more insight
3023 into how it works, see <a href="GetElementPtr.html">the getelementptr
3029 <i>; yields [12 x i8]*:aptr</i>
3030 %aptr = getelementptr {i32, [12 x i8]}* %sptr, i64 0, i32 1
3034 <!-- ======================================================================= -->
3035 <div class="doc_subsection"> <a name="convertops">Conversion Operations</a>
3037 <div class="doc_text">
3038 <p>The instructions in this category are the conversion instructions (casting)
3039 which all take a single operand and a type. They perform various bit conversions
3043 <!-- _______________________________________________________________________ -->
3044 <div class="doc_subsubsection">
3045 <a name="i_trunc">'<tt>trunc .. to</tt>' Instruction</a>
3047 <div class="doc_text">
3051 <result> = trunc <ty> <value> to <ty2> <i>; yields ty2</i>
3056 The '<tt>trunc</tt>' instruction truncates its operand to the type <tt>ty2</tt>.
3061 The '<tt>trunc</tt>' instruction takes a <tt>value</tt> to trunc, which must
3062 be an <a href="#t_integer">integer</a> type, and a type that specifies the size
3063 and type of the result, which must be an <a href="#t_integer">integer</a>
3064 type. The bit size of <tt>value</tt> must be larger than the bit size of
3065 <tt>ty2</tt>. Equal sized types are not allowed.</p>
3069 The '<tt>trunc</tt>' instruction truncates the high order bits in <tt>value</tt>
3070 and converts the remaining bits to <tt>ty2</tt>. Since the source size must be
3071 larger than the destination size, <tt>trunc</tt> cannot be a <i>no-op cast</i>.
3072 It will always truncate bits.</p>
3076 %X = trunc i32 257 to i8 <i>; yields i8:1</i>
3077 %Y = trunc i32 123 to i1 <i>; yields i1:true</i>
3078 %Y = trunc i32 122 to i1 <i>; yields i1:false</i>
3082 <!-- _______________________________________________________________________ -->
3083 <div class="doc_subsubsection">
3084 <a name="i_zext">'<tt>zext .. to</tt>' Instruction</a>
3086 <div class="doc_text">
3090 <result> = zext <ty> <value> to <ty2> <i>; yields ty2</i>
3094 <p>The '<tt>zext</tt>' instruction zero extends its operand to type
3099 <p>The '<tt>zext</tt>' instruction takes a value to cast, which must be of
3100 <a href="#t_integer">integer</a> type, and a type to cast it to, which must
3101 also be of <a href="#t_integer">integer</a> type. The bit size of the
3102 <tt>value</tt> must be smaller than the bit size of the destination type,
3106 <p>The <tt>zext</tt> fills the high order bits of the <tt>value</tt> with zero
3107 bits until it reaches the size of the destination type, <tt>ty2</tt>.</p>
3109 <p>When zero extending from i1, the result will always be either 0 or 1.</p>
3113 %X = zext i32 257 to i64 <i>; yields i64:257</i>
3114 %Y = zext i1 true to i32 <i>; yields i32:1</i>
3118 <!-- _______________________________________________________________________ -->
3119 <div class="doc_subsubsection">
3120 <a name="i_sext">'<tt>sext .. to</tt>' Instruction</a>
3122 <div class="doc_text">
3126 <result> = sext <ty> <value> to <ty2> <i>; yields ty2</i>
3130 <p>The '<tt>sext</tt>' sign extends <tt>value</tt> to the type <tt>ty2</tt>.</p>
3134 The '<tt>sext</tt>' instruction takes a value to cast, which must be of
3135 <a href="#t_integer">integer</a> type, and a type to cast it to, which must
3136 also be of <a href="#t_integer">integer</a> type. The bit size of the
3137 <tt>value</tt> must be smaller than the bit size of the destination type,
3142 The '<tt>sext</tt>' instruction performs a sign extension by copying the sign
3143 bit (highest order bit) of the <tt>value</tt> until it reaches the bit size of
3144 the type <tt>ty2</tt>.</p>
3146 <p>When sign extending from i1, the extension always results in -1 or 0.</p>
3150 %X = sext i8 -1 to i16 <i>; yields i16 :65535</i>
3151 %Y = sext i1 true to i32 <i>; yields i32:-1</i>
3155 <!-- _______________________________________________________________________ -->
3156 <div class="doc_subsubsection">
3157 <a name="i_fptrunc">'<tt>fptrunc .. to</tt>' Instruction</a>
3160 <div class="doc_text">
3165 <result> = fptrunc <ty> <value> to <ty2> <i>; yields ty2</i>
3169 <p>The '<tt>fptrunc</tt>' instruction truncates <tt>value</tt> to type
3174 <p>The '<tt>fptrunc</tt>' instruction takes a <a href="#t_floating">floating
3175 point</a> value to cast and a <a href="#t_floating">floating point</a> type to
3176 cast it to. The size of <tt>value</tt> must be larger than the size of
3177 <tt>ty2</tt>. This implies that <tt>fptrunc</tt> cannot be used to make a
3178 <i>no-op cast</i>.</p>
3181 <p> The '<tt>fptrunc</tt>' instruction truncates a <tt>value</tt> from a larger
3182 <a href="#t_floating">floating point</a> type to a smaller
3183 <a href="#t_floating">floating point</a> type. If the value cannot fit within
3184 the destination type, <tt>ty2</tt>, then the results are undefined.</p>
3188 %X = fptrunc double 123.0 to float <i>; yields float:123.0</i>
3189 %Y = fptrunc double 1.0E+300 to float <i>; yields undefined</i>
3193 <!-- _______________________________________________________________________ -->
3194 <div class="doc_subsubsection">
3195 <a name="i_fpext">'<tt>fpext .. to</tt>' Instruction</a>
3197 <div class="doc_text">
3201 <result> = fpext <ty> <value> to <ty2> <i>; yields ty2</i>
3205 <p>The '<tt>fpext</tt>' extends a floating point <tt>value</tt> to a larger
3206 floating point value.</p>
3209 <p>The '<tt>fpext</tt>' instruction takes a
3210 <a href="#t_floating">floating point</a> <tt>value</tt> to cast,
3211 and a <a href="#t_floating">floating point</a> type to cast it to. The source
3212 type must be smaller than the destination type.</p>
3215 <p>The '<tt>fpext</tt>' instruction extends the <tt>value</tt> from a smaller
3216 <a href="#t_floating">floating point</a> type to a larger
3217 <a href="#t_floating">floating point</a> type. The <tt>fpext</tt> cannot be
3218 used to make a <i>no-op cast</i> because it always changes bits. Use
3219 <tt>bitcast</tt> to make a <i>no-op cast</i> for a floating point cast.</p>
3223 %X = fpext float 3.1415 to double <i>; yields double:3.1415</i>
3224 %Y = fpext float 1.0 to float <i>; yields float:1.0 (no-op)</i>
3228 <!-- _______________________________________________________________________ -->
3229 <div class="doc_subsubsection">
3230 <a name="i_fptoui">'<tt>fptoui .. to</tt>' Instruction</a>
3232 <div class="doc_text">
3236 <result> = fptoui <ty> <value> to <ty2> <i>; yields ty2</i>
3240 <p>The '<tt>fptoui</tt>' converts a floating point <tt>value</tt> to its
3241 unsigned integer equivalent of type <tt>ty2</tt>.
3245 <p>The '<tt>fptoui</tt>' instruction takes a value to cast, which must be a
3246 scalar or vector <a href="#t_floating">floating point</a> value, and a type
3247 to cast it to <tt>ty2</tt>, which must be an <a href="#t_integer">integer</a>
3248 type. If <tt>ty</tt> is a vector floating point type, <tt>ty2</tt> must be a
3249 vector integer type with the same number of elements as <tt>ty</tt></p>
3252 <p> The '<tt>fptoui</tt>' instruction converts its
3253 <a href="#t_floating">floating point</a> operand into the nearest (rounding
3254 towards zero) unsigned integer value. If the value cannot fit in <tt>ty2</tt>,
3255 the results are undefined.</p>
3259 %X = fptoui double 123.0 to i32 <i>; yields i32:123</i>
3260 %Y = fptoui float 1.0E+300 to i1 <i>; yields undefined:1</i>
3261 %X = fptoui float 1.04E+17 to i8 <i>; yields undefined:1</i>
3265 <!-- _______________________________________________________________________ -->
3266 <div class="doc_subsubsection">
3267 <a name="i_fptosi">'<tt>fptosi .. to</tt>' Instruction</a>
3269 <div class="doc_text">
3273 <result> = fptosi <ty> <value> to <ty2> <i>; yields ty2</i>
3277 <p>The '<tt>fptosi</tt>' instruction converts
3278 <a href="#t_floating">floating point</a> <tt>value</tt> to type <tt>ty2</tt>.
3282 <p> The '<tt>fptosi</tt>' instruction takes a value to cast, which must be a
3283 scalar or vector <a href="#t_floating">floating point</a> value, and a type
3284 to cast it to <tt>ty2</tt>, which must be an <a href="#t_integer">integer</a>
3285 type. If <tt>ty</tt> is a vector floating point type, <tt>ty2</tt> must be a
3286 vector integer type with the same number of elements as <tt>ty</tt></p>
3289 <p>The '<tt>fptosi</tt>' instruction converts its
3290 <a href="#t_floating">floating point</a> operand into the nearest (rounding
3291 towards zero) signed integer value. If the value cannot fit in <tt>ty2</tt>,
3292 the results are undefined.</p>
3296 %X = fptosi double -123.0 to i32 <i>; yields i32:-123</i>
3297 %Y = fptosi float 1.0E-247 to i1 <i>; yields undefined:1</i>
3298 %X = fptosi float 1.04E+17 to i8 <i>; yields undefined:1</i>
3302 <!-- _______________________________________________________________________ -->
3303 <div class="doc_subsubsection">
3304 <a name="i_uitofp">'<tt>uitofp .. to</tt>' Instruction</a>
3306 <div class="doc_text">
3310 <result> = uitofp <ty> <value> to <ty2> <i>; yields ty2</i>
3314 <p>The '<tt>uitofp</tt>' instruction regards <tt>value</tt> as an unsigned
3315 integer and converts that value to the <tt>ty2</tt> type.</p>
3318 <p>The '<tt>uitofp</tt>' instruction takes a value to cast, which must be a
3319 scalar or vector <a href="#t_integer">integer</a> value, and a type to cast it
3320 to <tt>ty2</tt>, which must be an <a href="#t_floating">floating point</a>
3321 type. If <tt>ty</tt> is a vector integer type, <tt>ty2</tt> must be a vector
3322 floating point type with the same number of elements as <tt>ty</tt></p>
3325 <p>The '<tt>uitofp</tt>' instruction interprets its operand as an unsigned
3326 integer quantity and converts it to the corresponding floating point value. If
3327 the value cannot fit in the floating point value, the results are undefined.</p>
3331 %X = uitofp i32 257 to float <i>; yields float:257.0</i>
3332 %Y = uitofp i8 -1 to double <i>; yields double:255.0</i>
3336 <!-- _______________________________________________________________________ -->
3337 <div class="doc_subsubsection">
3338 <a name="i_sitofp">'<tt>sitofp .. to</tt>' Instruction</a>
3340 <div class="doc_text">
3344 <result> = sitofp <ty> <value> to <ty2> <i>; yields ty2</i>
3348 <p>The '<tt>sitofp</tt>' instruction regards <tt>value</tt> as a signed
3349 integer and converts that value to the <tt>ty2</tt> type.</p>
3352 <p>The '<tt>sitofp</tt>' instruction takes a value to cast, which must be a
3353 scalar or vector <a href="#t_integer">integer</a> value, and a type to cast it
3354 to <tt>ty2</tt>, which must be an <a href="#t_floating">floating point</a>
3355 type. If <tt>ty</tt> is a vector integer type, <tt>ty2</tt> must be a vector
3356 floating point type with the same number of elements as <tt>ty</tt></p>
3359 <p>The '<tt>sitofp</tt>' instruction interprets its operand as a signed
3360 integer quantity and converts it to the corresponding floating point value. If
3361 the value cannot fit in the floating point value, the results are undefined.</p>
3365 %X = sitofp i32 257 to float <i>; yields float:257.0</i>
3366 %Y = sitofp i8 -1 to double <i>; yields double:-1.0</i>
3370 <!-- _______________________________________________________________________ -->
3371 <div class="doc_subsubsection">
3372 <a name="i_ptrtoint">'<tt>ptrtoint .. to</tt>' Instruction</a>
3374 <div class="doc_text">
3378 <result> = ptrtoint <ty> <value> to <ty2> <i>; yields ty2</i>
3382 <p>The '<tt>ptrtoint</tt>' instruction converts the pointer <tt>value</tt> to
3383 the integer type <tt>ty2</tt>.</p>
3386 <p>The '<tt>ptrtoint</tt>' instruction takes a <tt>value</tt> to cast, which
3387 must be a <a href="#t_pointer">pointer</a> value, and a type to cast it to
3388 <tt>ty2</tt>, which must be an <a href="#t_integer">integer</a> type.
3391 <p>The '<tt>ptrtoint</tt>' instruction converts <tt>value</tt> to integer type
3392 <tt>ty2</tt> by interpreting the pointer value as an integer and either
3393 truncating or zero extending that value to the size of the integer type. If
3394 <tt>value</tt> is smaller than <tt>ty2</tt> then a zero extension is done. If
3395 <tt>value</tt> is larger than <tt>ty2</tt> then a truncation is done. If they
3396 are the same size, then nothing is done (<i>no-op cast</i>) other than a type
3401 %X = ptrtoint i32* %X to i8 <i>; yields truncation on 32-bit architecture</i>
3402 %Y = ptrtoint i32* %x to i64 <i>; yields zero extension on 32-bit architecture</i>
3406 <!-- _______________________________________________________________________ -->
3407 <div class="doc_subsubsection">
3408 <a name="i_inttoptr">'<tt>inttoptr .. to</tt>' Instruction</a>
3410 <div class="doc_text">
3414 <result> = inttoptr <ty> <value> to <ty2> <i>; yields ty2</i>
3418 <p>The '<tt>inttoptr</tt>' instruction converts an integer <tt>value</tt> to
3419 a pointer type, <tt>ty2</tt>.</p>
3422 <p>The '<tt>inttoptr</tt>' instruction takes an <a href="#t_integer">integer</a>
3423 value to cast, and a type to cast it to, which must be a
3424 <a href="#t_pointer">pointer</a> type.
3427 <p>The '<tt>inttoptr</tt>' instruction converts <tt>value</tt> to type
3428 <tt>ty2</tt> by applying either a zero extension or a truncation depending on
3429 the size of the integer <tt>value</tt>. If <tt>value</tt> is larger than the
3430 size of a pointer then a truncation is done. If <tt>value</tt> is smaller than
3431 the size of a pointer then a zero extension is done. If they are the same size,
3432 nothing is done (<i>no-op cast</i>).</p>
3436 %X = inttoptr i32 255 to i32* <i>; yields zero extension on 64-bit architecture</i>
3437 %X = inttoptr i32 255 to i32* <i>; yields no-op on 32-bit architecture</i>
3438 %Y = inttoptr i64 0 to i32* <i>; yields truncation on 32-bit architecture</i>
3442 <!-- _______________________________________________________________________ -->
3443 <div class="doc_subsubsection">
3444 <a name="i_bitcast">'<tt>bitcast .. to</tt>' Instruction</a>
3446 <div class="doc_text">
3450 <result> = bitcast <ty> <value> to <ty2> <i>; yields ty2</i>
3454 <p>The '<tt>bitcast</tt>' instruction converts <tt>value</tt> to type
3455 <tt>ty2</tt> without changing any bits.</p>
3458 <p>The '<tt>bitcast</tt>' instruction takes a value to cast, which must be
3459 a first class value, and a type to cast it to, which must also be a <a
3460 href="#t_firstclass">first class</a> type. The bit sizes of <tt>value</tt>
3461 and the destination type, <tt>ty2</tt>, must be identical. If the source
3462 type is a pointer, the destination type must also be a pointer.</p>
3465 <p>The '<tt>bitcast</tt>' instruction converts <tt>value</tt> to type
3466 <tt>ty2</tt>. It is always a <i>no-op cast</i> because no bits change with
3467 this conversion. The conversion is done as if the <tt>value</tt> had been
3468 stored to memory and read back as type <tt>ty2</tt>. Pointer types may only be
3469 converted to other pointer types with this instruction. To convert pointers to
3470 other types, use the <a href="#i_inttoptr">inttoptr</a> or
3471 <a href="#i_ptrtoint">ptrtoint</a> instructions first.</p>
3475 %X = bitcast i8 255 to i8 <i>; yields i8 :-1</i>
3476 %Y = bitcast i32* %x to sint* <i>; yields sint*:%x</i>
3477 %Z = bitcast <2xint> %V to i64; <i>; yields i64: %V</i>
3481 <!-- ======================================================================= -->
3482 <div class="doc_subsection"> <a name="otherops">Other Operations</a> </div>
3483 <div class="doc_text">
3484 <p>The instructions in this category are the "miscellaneous"
3485 instructions, which defy better classification.</p>
3488 <!-- _______________________________________________________________________ -->
3489 <div class="doc_subsubsection"><a name="i_icmp">'<tt>icmp</tt>' Instruction</a>
3491 <div class="doc_text">
3493 <pre> <result> = icmp <cond> <ty> <var1>, <var2> <i>; yields {i1}:result</i>
3496 <p>The '<tt>icmp</tt>' instruction returns a boolean value based on comparison
3497 of its two integer operands.</p>
3499 <p>The '<tt>icmp</tt>' instruction takes three operands. The first operand is
3500 the condition code indicating the kind of comparison to perform. It is not
3501 a value, just a keyword. The possible condition code are:
3503 <li><tt>eq</tt>: equal</li>
3504 <li><tt>ne</tt>: not equal </li>
3505 <li><tt>ugt</tt>: unsigned greater than</li>
3506 <li><tt>uge</tt>: unsigned greater or equal</li>
3507 <li><tt>ult</tt>: unsigned less than</li>
3508 <li><tt>ule</tt>: unsigned less or equal</li>
3509 <li><tt>sgt</tt>: signed greater than</li>
3510 <li><tt>sge</tt>: signed greater or equal</li>
3511 <li><tt>slt</tt>: signed less than</li>
3512 <li><tt>sle</tt>: signed less or equal</li>
3514 <p>The remaining two arguments must be <a href="#t_integer">integer</a> or
3515 <a href="#t_pointer">pointer</a> typed. They must also be identical types.</p>
3517 <p>The '<tt>icmp</tt>' compares <tt>var1</tt> and <tt>var2</tt> according to
3518 the condition code given as <tt>cond</tt>. The comparison performed always
3519 yields a <a href="#t_primitive">i1</a> result, as follows:
3521 <li><tt>eq</tt>: yields <tt>true</tt> if the operands are equal,
3522 <tt>false</tt> otherwise. No sign interpretation is necessary or performed.
3524 <li><tt>ne</tt>: yields <tt>true</tt> if the operands are unequal,
3525 <tt>false</tt> otherwise. No sign interpretation is necessary or performed.
3526 <li><tt>ugt</tt>: interprets the operands as unsigned values and yields
3527 <tt>true</tt> if <tt>var1</tt> is greater than <tt>var2</tt>.</li>
3528 <li><tt>uge</tt>: interprets the operands as unsigned values and yields
3529 <tt>true</tt> if <tt>var1</tt> is greater than or equal to <tt>var2</tt>.</li>
3530 <li><tt>ult</tt>: interprets the operands as unsigned values and yields
3531 <tt>true</tt> if <tt>var1</tt> is less than <tt>var2</tt>.</li>
3532 <li><tt>ule</tt>: interprets the operands as unsigned values and yields
3533 <tt>true</tt> if <tt>var1</tt> is less than or equal to <tt>var2</tt>.</li>
3534 <li><tt>sgt</tt>: interprets the operands as signed values and yields
3535 <tt>true</tt> if <tt>var1</tt> is greater than <tt>var2</tt>.</li>
3536 <li><tt>sge</tt>: interprets the operands as signed values and yields
3537 <tt>true</tt> if <tt>var1</tt> is greater than or equal to <tt>var2</tt>.</li>
3538 <li><tt>slt</tt>: interprets the operands as signed values and yields
3539 <tt>true</tt> if <tt>var1</tt> is less than <tt>var2</tt>.</li>
3540 <li><tt>sle</tt>: interprets the operands as signed values and yields
3541 <tt>true</tt> if <tt>var1</tt> is less than or equal to <tt>var2</tt>.</li>
3543 <p>If the operands are <a href="#t_pointer">pointer</a> typed, the pointer
3544 values are compared as if they were integers.</p>
3547 <pre> <result> = icmp eq i32 4, 5 <i>; yields: result=false</i>
3548 <result> = icmp ne float* %X, %X <i>; yields: result=false</i>
3549 <result> = icmp ult i16 4, 5 <i>; yields: result=true</i>
3550 <result> = icmp sgt i16 4, 5 <i>; yields: result=false</i>
3551 <result> = icmp ule i16 -4, 5 <i>; yields: result=false</i>
3552 <result> = icmp sge i16 4, 5 <i>; yields: result=false</i>
3556 <!-- _______________________________________________________________________ -->
3557 <div class="doc_subsubsection"><a name="i_fcmp">'<tt>fcmp</tt>' Instruction</a>
3559 <div class="doc_text">
3561 <pre> <result> = fcmp <cond> <ty> <var1>, <var2> <i>; yields {i1}:result</i>
3564 <p>The '<tt>fcmp</tt>' instruction returns a boolean value based on comparison
3565 of its floating point operands.</p>
3567 <p>The '<tt>fcmp</tt>' instruction takes three operands. The first operand is
3568 the condition code indicating the kind of comparison to perform. It is not
3569 a value, just a keyword. The possible condition code are:
3571 <li><tt>false</tt>: no comparison, always returns false</li>
3572 <li><tt>oeq</tt>: ordered and equal</li>
3573 <li><tt>ogt</tt>: ordered and greater than </li>
3574 <li><tt>oge</tt>: ordered and greater than or equal</li>
3575 <li><tt>olt</tt>: ordered and less than </li>
3576 <li><tt>ole</tt>: ordered and less than or equal</li>
3577 <li><tt>one</tt>: ordered and not equal</li>
3578 <li><tt>ord</tt>: ordered (no nans)</li>
3579 <li><tt>ueq</tt>: unordered or equal</li>
3580 <li><tt>ugt</tt>: unordered or greater than </li>
3581 <li><tt>uge</tt>: unordered or greater than or equal</li>
3582 <li><tt>ult</tt>: unordered or less than </li>
3583 <li><tt>ule</tt>: unordered or less than or equal</li>
3584 <li><tt>une</tt>: unordered or not equal</li>
3585 <li><tt>uno</tt>: unordered (either nans)</li>
3586 <li><tt>true</tt>: no comparison, always returns true</li>
3588 <p><i>Ordered</i> means that neither operand is a QNAN while
3589 <i>unordered</i> means that either operand may be a QNAN.</p>
3590 <p>The <tt>val1</tt> and <tt>val2</tt> arguments must be
3591 <a href="#t_floating">floating point</a> typed. They must have identical
3594 <p>The '<tt>fcmp</tt>' compares <tt>var1</tt> and <tt>var2</tt> according to
3595 the condition code given as <tt>cond</tt>. The comparison performed always
3596 yields a <a href="#t_primitive">i1</a> result, as follows:
3598 <li><tt>false</tt>: always yields <tt>false</tt>, regardless of operands.</li>
3599 <li><tt>oeq</tt>: yields <tt>true</tt> if both operands are not a QNAN and
3600 <tt>var1</tt> is equal to <tt>var2</tt>.</li>
3601 <li><tt>ogt</tt>: yields <tt>true</tt> if both operands are not a QNAN and
3602 <tt>var1</tt> is greather than <tt>var2</tt>.</li>
3603 <li><tt>oge</tt>: yields <tt>true</tt> if both operands are not a QNAN and
3604 <tt>var1</tt> is greater than or equal to <tt>var2</tt>.</li>
3605 <li><tt>olt</tt>: yields <tt>true</tt> if both operands are not a QNAN and
3606 <tt>var1</tt> is less than <tt>var2</tt>.</li>
3607 <li><tt>ole</tt>: yields <tt>true</tt> if both operands are not a QNAN and
3608 <tt>var1</tt> is less than or equal to <tt>var2</tt>.</li>
3609 <li><tt>one</tt>: yields <tt>true</tt> if both operands are not a QNAN and
3610 <tt>var1</tt> is not equal to <tt>var2</tt>.</li>
3611 <li><tt>ord</tt>: yields <tt>true</tt> if both operands are not a QNAN.</li>
3612 <li><tt>ueq</tt>: yields <tt>true</tt> if either operand is a QNAN or
3613 <tt>var1</tt> is equal to <tt>var2</tt>.</li>
3614 <li><tt>ugt</tt>: yields <tt>true</tt> if either operand is a QNAN or
3615 <tt>var1</tt> is greater than <tt>var2</tt>.</li>
3616 <li><tt>uge</tt>: yields <tt>true</tt> if either operand is a QNAN or
3617 <tt>var1</tt> is greater than or equal to <tt>var2</tt>.</li>
3618 <li><tt>ult</tt>: yields <tt>true</tt> if either operand is a QNAN or
3619 <tt>var1</tt> is less than <tt>var2</tt>.</li>
3620 <li><tt>ule</tt>: yields <tt>true</tt> if either operand is a QNAN or
3621 <tt>var1</tt> is less than or equal to <tt>var2</tt>.</li>
3622 <li><tt>une</tt>: yields <tt>true</tt> if either operand is a QNAN or
3623 <tt>var1</tt> is not equal to <tt>var2</tt>.</li>
3624 <li><tt>uno</tt>: yields <tt>true</tt> if either operand is a QNAN.</li>
3625 <li><tt>true</tt>: always yields <tt>true</tt>, regardless of operands.</li>
3629 <pre> <result> = fcmp oeq float 4.0, 5.0 <i>; yields: result=false</i>
3630 <result> = icmp one float 4.0, 5.0 <i>; yields: result=true</i>
3631 <result> = icmp olt float 4.0, 5.0 <i>; yields: result=true</i>
3632 <result> = icmp ueq double 1.0, 2.0 <i>; yields: result=false</i>
3636 <!-- _______________________________________________________________________ -->
3637 <div class="doc_subsubsection"> <a name="i_phi">'<tt>phi</tt>'
3638 Instruction</a> </div>
3639 <div class="doc_text">
3641 <pre> <result> = phi <ty> [ <val0>, <label0>], ...<br></pre>
3643 <p>The '<tt>phi</tt>' instruction is used to implement the φ node in
3644 the SSA graph representing the function.</p>
3646 <p>The type of the incoming values is specified with the first type
3647 field. After this, the '<tt>phi</tt>' instruction takes a list of pairs
3648 as arguments, with one pair for each predecessor basic block of the
3649 current block. Only values of <a href="#t_firstclass">first class</a>
3650 type may be used as the value arguments to the PHI node. Only labels
3651 may be used as the label arguments.</p>
3652 <p>There must be no non-phi instructions between the start of a basic
3653 block and the PHI instructions: i.e. PHI instructions must be first in
3656 <p>At runtime, the '<tt>phi</tt>' instruction logically takes on the value
3657 specified by the pair corresponding to the predecessor basic block that executed
3658 just prior to the current block.</p>
3660 <pre>Loop: ; Infinite loop that counts from 0 on up...<br> %indvar = phi i32 [ 0, %LoopHeader ], [ %nextindvar, %Loop ]<br> %nextindvar = add i32 %indvar, 1<br> br label %Loop<br></pre>
3663 <!-- _______________________________________________________________________ -->
3664 <div class="doc_subsubsection">
3665 <a name="i_select">'<tt>select</tt>' Instruction</a>
3668 <div class="doc_text">
3673 <result> = select i1 <cond>, <ty> <val1>, <ty> <val2> <i>; yields ty</i>
3679 The '<tt>select</tt>' instruction is used to choose one value based on a
3680 condition, without branching.
3687 The '<tt>select</tt>' instruction requires a boolean value indicating the condition, and two values of the same <a href="#t_firstclass">first class</a> type.
3693 If the boolean condition evaluates to true, the instruction returns the first
3694 value argument; otherwise, it returns the second value argument.
3700 %X = select i1 true, i8 17, i8 42 <i>; yields i8:17</i>
3705 <!-- _______________________________________________________________________ -->
3706 <div class="doc_subsubsection">
3707 <a name="i_call">'<tt>call</tt>' Instruction</a>
3710 <div class="doc_text">
3714 <result> = [tail] call [<a href="#callingconv">cconv</a>] <ty> [<fnty>*] <fnptrval>(<param list>)
3719 <p>The '<tt>call</tt>' instruction represents a simple function call.</p>
3723 <p>This instruction requires several arguments:</p>
3727 <p>The optional "tail" marker indicates whether the callee function accesses
3728 any allocas or varargs in the caller. If the "tail" marker is present, the
3729 function call is eligible for tail call optimization. Note that calls may
3730 be marked "tail" even if they do not occur before a <a
3731 href="#i_ret"><tt>ret</tt></a> instruction.
3734 <p>The optional "cconv" marker indicates which <a href="#callingconv">calling
3735 convention</a> the call should use. If none is specified, the call defaults
3736 to using C calling conventions.
3739 <p>'<tt>ty</tt>': the type of the call instruction itself which is also
3740 the type of the return value. Functions that return no value are marked
3741 <tt><a href="#t_void">void</a></tt>.</p>
3744 <p>'<tt>fnty</tt>': shall be the signature of the pointer to function
3745 value being invoked. The argument types must match the types implied by
3746 this signature. This type can be omitted if the function is not varargs
3747 and if the function type does not return a pointer to a function.</p>
3750 <p>'<tt>fnptrval</tt>': An LLVM value containing a pointer to a function to
3751 be invoked. In most cases, this is a direct function invocation, but
3752 indirect <tt>call</tt>s are just as possible, calling an arbitrary pointer
3753 to function value.</p>
3756 <p>'<tt>function args</tt>': argument list whose types match the
3757 function signature argument types. All arguments must be of
3758 <a href="#t_firstclass">first class</a> type. If the function signature
3759 indicates the function accepts a variable number of arguments, the extra
3760 arguments can be specified.</p>
3766 <p>The '<tt>call</tt>' instruction is used to cause control flow to
3767 transfer to a specified function, with its incoming arguments bound to
3768 the specified values. Upon a '<tt><a href="#i_ret">ret</a></tt>'
3769 instruction in the called function, control flow continues with the
3770 instruction after the function call, and the return value of the
3771 function is bound to the result argument. This is a simpler case of
3772 the <a href="#i_invoke">invoke</a> instruction.</p>
3777 %retval = call i32 @test(i32 %argc)
3778 call i32 (i8 *, ...)* @printf(i8 * %msg, i32 12, i8 42);
3779 %X = tail call i32 @foo()
3780 %Y = tail call <a href="#callingconv">fastcc</a> i32 @foo()
3781 %Z = call void %foo(i8 97 signext)
3786 <!-- _______________________________________________________________________ -->
3787 <div class="doc_subsubsection">
3788 <a name="i_va_arg">'<tt>va_arg</tt>' Instruction</a>
3791 <div class="doc_text">
3796 <resultval> = va_arg <va_list*> <arglist>, <argty>
3801 <p>The '<tt>va_arg</tt>' instruction is used to access arguments passed through
3802 the "variable argument" area of a function call. It is used to implement the
3803 <tt>va_arg</tt> macro in C.</p>
3807 <p>This instruction takes a <tt>va_list*</tt> value and the type of
3808 the argument. It returns a value of the specified argument type and
3809 increments the <tt>va_list</tt> to point to the next argument. The
3810 actual type of <tt>va_list</tt> is target specific.</p>
3814 <p>The '<tt>va_arg</tt>' instruction loads an argument of the specified
3815 type from the specified <tt>va_list</tt> and causes the
3816 <tt>va_list</tt> to point to the next argument. For more information,
3817 see the variable argument handling <a href="#int_varargs">Intrinsic
3820 <p>It is legal for this instruction to be called in a function which does not
3821 take a variable number of arguments, for example, the <tt>vfprintf</tt>
3824 <p><tt>va_arg</tt> is an LLVM instruction instead of an <a
3825 href="#intrinsics">intrinsic function</a> because it takes a type as an
3830 <p>See the <a href="#int_varargs">variable argument processing</a> section.</p>
3834 <!-- *********************************************************************** -->
3835 <div class="doc_section"> <a name="intrinsics">Intrinsic Functions</a> </div>
3836 <!-- *********************************************************************** -->
3838 <div class="doc_text">
3840 <p>LLVM supports the notion of an "intrinsic function". These functions have
3841 well known names and semantics and are required to follow certain restrictions.
3842 Overall, these intrinsics represent an extension mechanism for the LLVM
3843 language that does not require changing all of the transformations in LLVM when
3844 adding to the language (or the bitcode reader/writer, the parser, etc...).</p>
3846 <p>Intrinsic function names must all start with an "<tt>llvm.</tt>" prefix. This
3847 prefix is reserved in LLVM for intrinsic names; thus, function names may not
3848 begin with this prefix. Intrinsic functions must always be external functions:
3849 you cannot define the body of intrinsic functions. Intrinsic functions may
3850 only be used in call or invoke instructions: it is illegal to take the address
3851 of an intrinsic function. Additionally, because intrinsic functions are part
3852 of the LLVM language, it is required if any are added that they be documented
3855 <p>Some intrinsic functions can be overloaded, i.e., the intrinsic represents
3856 a family of functions that perform the same operation but on different data
3857 types. Because LLVM can represent over 8 million different integer types,
3858 overloading is used commonly to allow an intrinsic function to operate on any
3859 integer type. One or more of the argument types or the result type can be
3860 overloaded to accept any integer type. Argument types may also be defined as
3861 exactly matching a previous argument's type or the result type. This allows an
3862 intrinsic function which accepts multiple arguments, but needs all of them to
3863 be of the same type, to only be overloaded with respect to a single argument or
3866 <p>Overloaded intrinsics will have the names of its overloaded argument types
3867 encoded into its function name, each preceded by a period. Only those types
3868 which are overloaded result in a name suffix. Arguments whose type is matched
3869 against another type do not. For example, the <tt>llvm.ctpop</tt> function can
3870 take an integer of any width and returns an integer of exactly the same integer
3871 width. This leads to a family of functions such as
3872 <tt>i8 @llvm.ctpop.i8(i8 %val)</tt> and <tt>i29 @llvm.ctpop.i29(i29 %val)</tt>.
3873 Only one type, the return type, is overloaded, and only one type suffix is
3874 required. Because the argument's type is matched against the return type, it
3875 does not require its own name suffix.</p>
3877 <p>To learn how to add an intrinsic function, please see the
3878 <a href="ExtendingLLVM.html">Extending LLVM Guide</a>.
3883 <!-- ======================================================================= -->
3884 <div class="doc_subsection">
3885 <a name="int_varargs">Variable Argument Handling Intrinsics</a>
3888 <div class="doc_text">
3890 <p>Variable argument support is defined in LLVM with the <a
3891 href="#i_va_arg"><tt>va_arg</tt></a> instruction and these three
3892 intrinsic functions. These functions are related to the similarly
3893 named macros defined in the <tt><stdarg.h></tt> header file.</p>
3895 <p>All of these functions operate on arguments that use a
3896 target-specific value type "<tt>va_list</tt>". The LLVM assembly
3897 language reference manual does not define what this type is, so all
3898 transformations should be prepared to handle these functions regardless of
3901 <p>This example shows how the <a href="#i_va_arg"><tt>va_arg</tt></a>
3902 instruction and the variable argument handling intrinsic functions are
3905 <div class="doc_code">
3907 define i32 @test(i32 %X, ...) {
3908 ; Initialize variable argument processing
3910 %ap2 = bitcast i8** %ap to i8*
3911 call void @llvm.va_start(i8* %ap2)
3913 ; Read a single integer argument
3914 %tmp = va_arg i8** %ap, i32
3916 ; Demonstrate usage of llvm.va_copy and llvm.va_end
3918 %aq2 = bitcast i8** %aq to i8*
3919 call void @llvm.va_copy(i8* %aq2, i8* %ap2)
3920 call void @llvm.va_end(i8* %aq2)
3922 ; Stop processing of arguments.
3923 call void @llvm.va_end(i8* %ap2)
3927 declare void @llvm.va_start(i8*)
3928 declare void @llvm.va_copy(i8*, i8*)
3929 declare void @llvm.va_end(i8*)
3935 <!-- _______________________________________________________________________ -->
3936 <div class="doc_subsubsection">
3937 <a name="int_va_start">'<tt>llvm.va_start</tt>' Intrinsic</a>
3941 <div class="doc_text">
3943 <pre> declare void %llvm.va_start(i8* <arglist>)<br></pre>
3945 <P>The '<tt>llvm.va_start</tt>' intrinsic initializes
3946 <tt>*<arglist></tt> for subsequent use by <tt><a
3947 href="#i_va_arg">va_arg</a></tt>.</p>
3951 <P>The argument is a pointer to a <tt>va_list</tt> element to initialize.</p>
3955 <P>The '<tt>llvm.va_start</tt>' intrinsic works just like the <tt>va_start</tt>
3956 macro available in C. In a target-dependent way, it initializes the
3957 <tt>va_list</tt> element to which the argument points, so that the next call to
3958 <tt>va_arg</tt> will produce the first variable argument passed to the function.
3959 Unlike the C <tt>va_start</tt> macro, this intrinsic does not need to know the
3960 last argument of the function as the compiler can figure that out.</p>
3964 <!-- _______________________________________________________________________ -->
3965 <div class="doc_subsubsection">
3966 <a name="int_va_end">'<tt>llvm.va_end</tt>' Intrinsic</a>
3969 <div class="doc_text">
3971 <pre> declare void @llvm.va_end(i8* <arglist>)<br></pre>
3974 <p>The '<tt>llvm.va_end</tt>' intrinsic destroys <tt>*<arglist></tt>,
3975 which has been initialized previously with <tt><a href="#int_va_start">llvm.va_start</a></tt>
3976 or <tt><a href="#i_va_copy">llvm.va_copy</a></tt>.</p>
3980 <p>The argument is a pointer to a <tt>va_list</tt> to destroy.</p>
3984 <p>The '<tt>llvm.va_end</tt>' intrinsic works just like the <tt>va_end</tt>
3985 macro available in C. In a target-dependent way, it destroys the
3986 <tt>va_list</tt> element to which the argument points. Calls to <a
3987 href="#int_va_start"><tt>llvm.va_start</tt></a> and <a href="#int_va_copy">
3988 <tt>llvm.va_copy</tt></a> must be matched exactly with calls to
3989 <tt>llvm.va_end</tt>.</p>
3993 <!-- _______________________________________________________________________ -->
3994 <div class="doc_subsubsection">
3995 <a name="int_va_copy">'<tt>llvm.va_copy</tt>' Intrinsic</a>
3998 <div class="doc_text">
4003 declare void @llvm.va_copy(i8* <destarglist>, i8* <srcarglist>)
4008 <p>The '<tt>llvm.va_copy</tt>' intrinsic copies the current argument position
4009 from the source argument list to the destination argument list.</p>
4013 <p>The first argument is a pointer to a <tt>va_list</tt> element to initialize.
4014 The second argument is a pointer to a <tt>va_list</tt> element to copy from.</p>
4019 <p>The '<tt>llvm.va_copy</tt>' intrinsic works just like the <tt>va_copy</tt>
4020 macro available in C. In a target-dependent way, it copies the source
4021 <tt>va_list</tt> element into the destination <tt>va_list</tt> element. This
4022 intrinsic is necessary because the <tt><a href="#int_va_start">
4023 llvm.va_start</a></tt> intrinsic may be arbitrarily complex and require, for
4024 example, memory allocation.</p>
4028 <!-- ======================================================================= -->
4029 <div class="doc_subsection">
4030 <a name="int_gc">Accurate Garbage Collection Intrinsics</a>
4033 <div class="doc_text">
4036 LLVM support for <a href="GarbageCollection.html">Accurate Garbage
4037 Collection</a> requires the implementation and generation of these intrinsics.
4038 These intrinsics allow identification of <a href="#int_gcroot">GC roots on the
4039 stack</a>, as well as garbage collector implementations that require <a
4040 href="#int_gcread">read</a> and <a href="#int_gcwrite">write</a> barriers.
4041 Front-ends for type-safe garbage collected languages should generate these
4042 intrinsics to make use of the LLVM garbage collectors. For more details, see <a
4043 href="GarbageCollection.html">Accurate Garbage Collection with LLVM</a>.
4046 <p>The garbage collection intrinsics only operate on objects in the generic
4047 address space (address space zero).</p>
4051 <!-- _______________________________________________________________________ -->
4052 <div class="doc_subsubsection">
4053 <a name="int_gcroot">'<tt>llvm.gcroot</tt>' Intrinsic</a>
4056 <div class="doc_text">
4061 declare void @llvm.gcroot(i8** %ptrloc, i8* %metadata)
4066 <p>The '<tt>llvm.gcroot</tt>' intrinsic declares the existence of a GC root to
4067 the code generator, and allows some metadata to be associated with it.</p>
4071 <p>The first argument specifies the address of a stack object that contains the
4072 root pointer. The second pointer (which must be either a constant or a global
4073 value address) contains the meta-data to be associated with the root.</p>
4077 <p>At runtime, a call to this intrinsics stores a null pointer into the "ptrloc"
4078 location. At compile-time, the code generator generates information to allow
4079 the runtime to find the pointer at GC safe points. The '<tt>llvm.gcroot</tt>'
4080 intrinsic may only be used in a function which <a href="#gc">specifies a GC
4086 <!-- _______________________________________________________________________ -->
4087 <div class="doc_subsubsection">
4088 <a name="int_gcread">'<tt>llvm.gcread</tt>' Intrinsic</a>
4091 <div class="doc_text">
4096 declare i8* @llvm.gcread(i8* %ObjPtr, i8** %Ptr)
4101 <p>The '<tt>llvm.gcread</tt>' intrinsic identifies reads of references from heap
4102 locations, allowing garbage collector implementations that require read
4107 <p>The second argument is the address to read from, which should be an address
4108 allocated from the garbage collector. The first object is a pointer to the
4109 start of the referenced object, if needed by the language runtime (otherwise
4114 <p>The '<tt>llvm.gcread</tt>' intrinsic has the same semantics as a load
4115 instruction, but may be replaced with substantially more complex code by the
4116 garbage collector runtime, as needed. The '<tt>llvm.gcread</tt>' intrinsic
4117 may only be used in a function which <a href="#gc">specifies a GC
4123 <!-- _______________________________________________________________________ -->
4124 <div class="doc_subsubsection">
4125 <a name="int_gcwrite">'<tt>llvm.gcwrite</tt>' Intrinsic</a>
4128 <div class="doc_text">
4133 declare void @llvm.gcwrite(i8* %P1, i8* %Obj, i8** %P2)
4138 <p>The '<tt>llvm.gcwrite</tt>' intrinsic identifies writes of references to heap
4139 locations, allowing garbage collector implementations that require write
4140 barriers (such as generational or reference counting collectors).</p>
4144 <p>The first argument is the reference to store, the second is the start of the
4145 object to store it to, and the third is the address of the field of Obj to
4146 store to. If the runtime does not require a pointer to the object, Obj may be
4151 <p>The '<tt>llvm.gcwrite</tt>' intrinsic has the same semantics as a store
4152 instruction, but may be replaced with substantially more complex code by the
4153 garbage collector runtime, as needed. The '<tt>llvm.gcwrite</tt>' intrinsic
4154 may only be used in a function which <a href="#gc">specifies a GC
4161 <!-- ======================================================================= -->
4162 <div class="doc_subsection">
4163 <a name="int_codegen">Code Generator Intrinsics</a>
4166 <div class="doc_text">
4168 These intrinsics are provided by LLVM to expose special features that may only
4169 be implemented with code generator support.
4174 <!-- _______________________________________________________________________ -->
4175 <div class="doc_subsubsection">
4176 <a name="int_returnaddress">'<tt>llvm.returnaddress</tt>' Intrinsic</a>
4179 <div class="doc_text">
4183 declare i8 *@llvm.returnaddress(i32 <level>)
4189 The '<tt>llvm.returnaddress</tt>' intrinsic attempts to compute a
4190 target-specific value indicating the return address of the current function
4191 or one of its callers.
4197 The argument to this intrinsic indicates which function to return the address
4198 for. Zero indicates the calling function, one indicates its caller, etc. The
4199 argument is <b>required</b> to be a constant integer value.
4205 The '<tt>llvm.returnaddress</tt>' intrinsic either returns a pointer indicating
4206 the return address of the specified call frame, or zero if it cannot be
4207 identified. The value returned by this intrinsic is likely to be incorrect or 0
4208 for arguments other than zero, so it should only be used for debugging purposes.
4212 Note that calling this intrinsic does not prevent function inlining or other
4213 aggressive transformations, so the value returned may not be that of the obvious
4214 source-language caller.
4219 <!-- _______________________________________________________________________ -->
4220 <div class="doc_subsubsection">
4221 <a name="int_frameaddress">'<tt>llvm.frameaddress</tt>' Intrinsic</a>
4224 <div class="doc_text">
4228 declare i8 *@llvm.frameaddress(i32 <level>)
4234 The '<tt>llvm.frameaddress</tt>' intrinsic attempts to return the
4235 target-specific frame pointer value for the specified stack frame.
4241 The argument to this intrinsic indicates which function to return the frame
4242 pointer for. Zero indicates the calling function, one indicates its caller,
4243 etc. The argument is <b>required</b> to be a constant integer value.
4249 The '<tt>llvm.frameaddress</tt>' intrinsic either returns a pointer indicating
4250 the frame address of the specified call frame, or zero if it cannot be
4251 identified. The value returned by this intrinsic is likely to be incorrect or 0
4252 for arguments other than zero, so it should only be used for debugging purposes.
4256 Note that calling this intrinsic does not prevent function inlining or other
4257 aggressive transformations, so the value returned may not be that of the obvious
4258 source-language caller.
4262 <!-- _______________________________________________________________________ -->
4263 <div class="doc_subsubsection">
4264 <a name="int_stacksave">'<tt>llvm.stacksave</tt>' Intrinsic</a>
4267 <div class="doc_text">
4271 declare i8 *@llvm.stacksave()
4277 The '<tt>llvm.stacksave</tt>' intrinsic is used to remember the current state of
4278 the function stack, for use with <a href="#int_stackrestore">
4279 <tt>llvm.stackrestore</tt></a>. This is useful for implementing language
4280 features like scoped automatic variable sized arrays in C99.
4286 This intrinsic returns a opaque pointer value that can be passed to <a
4287 href="#int_stackrestore"><tt>llvm.stackrestore</tt></a>. When an
4288 <tt>llvm.stackrestore</tt> intrinsic is executed with a value saved from
4289 <tt>llvm.stacksave</tt>, it effectively restores the state of the stack to the
4290 state it was in when the <tt>llvm.stacksave</tt> intrinsic executed. In
4291 practice, this pops any <a href="#i_alloca">alloca</a> blocks from the stack
4292 that were allocated after the <tt>llvm.stacksave</tt> was executed.
4297 <!-- _______________________________________________________________________ -->
4298 <div class="doc_subsubsection">
4299 <a name="int_stackrestore">'<tt>llvm.stackrestore</tt>' Intrinsic</a>
4302 <div class="doc_text">
4306 declare void @llvm.stackrestore(i8 * %ptr)
4312 The '<tt>llvm.stackrestore</tt>' intrinsic is used to restore the state of
4313 the function stack to the state it was in when the corresponding <a
4314 href="#int_stacksave"><tt>llvm.stacksave</tt></a> intrinsic executed. This is
4315 useful for implementing language features like scoped automatic variable sized
4322 See the description for <a href="#int_stacksave"><tt>llvm.stacksave</tt></a>.
4328 <!-- _______________________________________________________________________ -->
4329 <div class="doc_subsubsection">
4330 <a name="int_prefetch">'<tt>llvm.prefetch</tt>' Intrinsic</a>
4333 <div class="doc_text">
4337 declare void @llvm.prefetch(i8* <address>, i32 <rw>, i32 <locality>)
4344 The '<tt>llvm.prefetch</tt>' intrinsic is a hint to the code generator to insert
4345 a prefetch instruction if supported; otherwise, it is a noop. Prefetches have
4347 effect on the behavior of the program but can change its performance
4354 <tt>address</tt> is the address to be prefetched, <tt>rw</tt> is the specifier
4355 determining if the fetch should be for a read (0) or write (1), and
4356 <tt>locality</tt> is a temporal locality specifier ranging from (0) - no
4357 locality, to (3) - extremely local keep in cache. The <tt>rw</tt> and
4358 <tt>locality</tt> arguments must be constant integers.
4364 This intrinsic does not modify the behavior of the program. In particular,
4365 prefetches cannot trap and do not produce a value. On targets that support this
4366 intrinsic, the prefetch can provide hints to the processor cache for better
4372 <!-- _______________________________________________________________________ -->
4373 <div class="doc_subsubsection">
4374 <a name="int_pcmarker">'<tt>llvm.pcmarker</tt>' Intrinsic</a>
4377 <div class="doc_text">
4381 declare void @llvm.pcmarker(i32 <id>)
4388 The '<tt>llvm.pcmarker</tt>' intrinsic is a method to export a Program Counter
4390 code to simulators and other tools. The method is target specific, but it is
4391 expected that the marker will use exported symbols to transmit the PC of the marker.
4392 The marker makes no guarantees that it will remain with any specific instruction
4393 after optimizations. It is possible that the presence of a marker will inhibit
4394 optimizations. The intended use is to be inserted after optimizations to allow
4395 correlations of simulation runs.
4401 <tt>id</tt> is a numerical id identifying the marker.
4407 This intrinsic does not modify the behavior of the program. Backends that do not
4408 support this intrinisic may ignore it.
4413 <!-- _______________________________________________________________________ -->
4414 <div class="doc_subsubsection">
4415 <a name="int_readcyclecounter">'<tt>llvm.readcyclecounter</tt>' Intrinsic</a>
4418 <div class="doc_text">
4422 declare i64 @llvm.readcyclecounter( )
4429 The '<tt>llvm.readcyclecounter</tt>' intrinsic provides access to the cycle
4430 counter register (or similar low latency, high accuracy clocks) on those targets
4431 that support it. On X86, it should map to RDTSC. On Alpha, it should map to RPCC.
4432 As the backing counters overflow quickly (on the order of 9 seconds on alpha), this
4433 should only be used for small timings.
4439 When directly supported, reading the cycle counter should not modify any memory.
4440 Implementations are allowed to either return a application specific value or a
4441 system wide value. On backends without support, this is lowered to a constant 0.
4446 <!-- ======================================================================= -->
4447 <div class="doc_subsection">
4448 <a name="int_libc">Standard C Library Intrinsics</a>
4451 <div class="doc_text">
4453 LLVM provides intrinsics for a few important standard C library functions.
4454 These intrinsics allow source-language front-ends to pass information about the
4455 alignment of the pointer arguments to the code generator, providing opportunity
4456 for more efficient code generation.
4461 <!-- _______________________________________________________________________ -->
4462 <div class="doc_subsubsection">
4463 <a name="int_memcpy">'<tt>llvm.memcpy</tt>' Intrinsic</a>
4466 <div class="doc_text">
4470 declare void @llvm.memcpy.i32(i8 * <dest>, i8 * <src>,
4471 i32 <len>, i32 <align>)
4472 declare void @llvm.memcpy.i64(i8 * <dest>, i8 * <src>,
4473 i64 <len>, i32 <align>)
4479 The '<tt>llvm.memcpy.*</tt>' intrinsics copy a block of memory from the source
4480 location to the destination location.
4484 Note that, unlike the standard libc function, the <tt>llvm.memcpy.*</tt>
4485 intrinsics do not return a value, and takes an extra alignment argument.
4491 The first argument is a pointer to the destination, the second is a pointer to
4492 the source. The third argument is an integer argument
4493 specifying the number of bytes to copy, and the fourth argument is the alignment
4494 of the source and destination locations.
4498 If the call to this intrinisic has an alignment value that is not 0 or 1, then
4499 the caller guarantees that both the source and destination pointers are aligned
4506 The '<tt>llvm.memcpy.*</tt>' intrinsics copy a block of memory from the source
4507 location to the destination location, which are not allowed to overlap. It
4508 copies "len" bytes of memory over. If the argument is known to be aligned to
4509 some boundary, this can be specified as the fourth argument, otherwise it should
4515 <!-- _______________________________________________________________________ -->
4516 <div class="doc_subsubsection">
4517 <a name="int_memmove">'<tt>llvm.memmove</tt>' Intrinsic</a>
4520 <div class="doc_text">
4524 declare void @llvm.memmove.i32(i8 * <dest>, i8 * <src>,
4525 i32 <len>, i32 <align>)
4526 declare void @llvm.memmove.i64(i8 * <dest>, i8 * <src>,
4527 i64 <len>, i32 <align>)
4533 The '<tt>llvm.memmove.*</tt>' intrinsics move a block of memory from the source
4534 location to the destination location. It is similar to the
4535 '<tt>llvm.memcpy</tt>' intrinsic but allows the two memory locations to overlap.
4539 Note that, unlike the standard libc function, the <tt>llvm.memmove.*</tt>
4540 intrinsics do not return a value, and takes an extra alignment argument.
4546 The first argument is a pointer to the destination, the second is a pointer to
4547 the source. The third argument is an integer argument
4548 specifying the number of bytes to copy, and the fourth argument is the alignment
4549 of the source and destination locations.
4553 If the call to this intrinisic has an alignment value that is not 0 or 1, then
4554 the caller guarantees that the source and destination pointers are aligned to
4561 The '<tt>llvm.memmove.*</tt>' intrinsics copy a block of memory from the source
4562 location to the destination location, which may overlap. It
4563 copies "len" bytes of memory over. If the argument is known to be aligned to
4564 some boundary, this can be specified as the fourth argument, otherwise it should
4570 <!-- _______________________________________________________________________ -->
4571 <div class="doc_subsubsection">
4572 <a name="int_memset">'<tt>llvm.memset.*</tt>' Intrinsics</a>
4575 <div class="doc_text">
4579 declare void @llvm.memset.i32(i8 * <dest>, i8 <val>,
4580 i32 <len>, i32 <align>)
4581 declare void @llvm.memset.i64(i8 * <dest>, i8 <val>,
4582 i64 <len>, i32 <align>)
4588 The '<tt>llvm.memset.*</tt>' intrinsics fill a block of memory with a particular
4593 Note that, unlike the standard libc function, the <tt>llvm.memset</tt> intrinsic
4594 does not return a value, and takes an extra alignment argument.
4600 The first argument is a pointer to the destination to fill, the second is the
4601 byte value to fill it with, the third argument is an integer
4602 argument specifying the number of bytes to fill, and the fourth argument is the
4603 known alignment of destination location.
4607 If the call to this intrinisic has an alignment value that is not 0 or 1, then
4608 the caller guarantees that the destination pointer is aligned to that boundary.
4614 The '<tt>llvm.memset.*</tt>' intrinsics fill "len" bytes of memory starting at
4616 destination location. If the argument is known to be aligned to some boundary,
4617 this can be specified as the fourth argument, otherwise it should be set to 0 or
4623 <!-- _______________________________________________________________________ -->
4624 <div class="doc_subsubsection">
4625 <a name="int_sqrt">'<tt>llvm.sqrt.*</tt>' Intrinsic</a>
4628 <div class="doc_text">
4631 <p>This is an overloaded intrinsic. You can use <tt>llvm.sqrt</tt> on any
4632 floating point or vector of floating point type. Not all targets support all
4635 declare float @llvm.sqrt.f32(float %Val)
4636 declare double @llvm.sqrt.f64(double %Val)
4637 declare x86_fp80 @llvm.sqrt.f80(x86_fp80 %Val)
4638 declare fp128 @llvm.sqrt.f128(fp128 %Val)
4639 declare ppc_fp128 @llvm.sqrt.ppcf128(ppc_fp128 %Val)
4645 The '<tt>llvm.sqrt</tt>' intrinsics return the sqrt of the specified operand,
4646 returning the same value as the libm '<tt>sqrt</tt>' functions would. Unlike
4647 <tt>sqrt</tt> in libm, however, <tt>llvm.sqrt</tt> has undefined behavior for
4648 negative numbers (which allows for better optimization).
4654 The argument and return value are floating point numbers of the same type.
4660 This function returns the sqrt of the specified operand if it is a nonnegative
4661 floating point number.
4665 <!-- _______________________________________________________________________ -->
4666 <div class="doc_subsubsection">
4667 <a name="int_powi">'<tt>llvm.powi.*</tt>' Intrinsic</a>
4670 <div class="doc_text">
4673 <p>This is an overloaded intrinsic. You can use <tt>llvm.powi</tt> on any
4674 floating point or vector of floating point type. Not all targets support all
4677 declare float @llvm.powi.f32(float %Val, i32 %power)
4678 declare double @llvm.powi.f64(double %Val, i32 %power)
4679 declare x86_fp80 @llvm.powi.f80(x86_fp80 %Val, i32 %power)
4680 declare fp128 @llvm.powi.f128(fp128 %Val, i32 %power)
4681 declare ppc_fp128 @llvm.powi.ppcf128(ppc_fp128 %Val, i32 %power)
4687 The '<tt>llvm.powi.*</tt>' intrinsics return the first operand raised to the
4688 specified (positive or negative) power. The order of evaluation of
4689 multiplications is not defined. When a vector of floating point type is
4690 used, the second argument remains a scalar integer value.
4696 The second argument is an integer power, and the first is a value to raise to
4703 This function returns the first value raised to the second power with an
4704 unspecified sequence of rounding operations.</p>
4707 <!-- _______________________________________________________________________ -->
4708 <div class="doc_subsubsection">
4709 <a name="int_sin">'<tt>llvm.sin.*</tt>' Intrinsic</a>
4712 <div class="doc_text">
4715 <p>This is an overloaded intrinsic. You can use <tt>llvm.sin</tt> on any
4716 floating point or vector of floating point type. Not all targets support all
4719 declare float @llvm.sin.f32(float %Val)
4720 declare double @llvm.sin.f64(double %Val)
4721 declare x86_fp80 @llvm.sin.f80(x86_fp80 %Val)
4722 declare fp128 @llvm.sin.f128(fp128 %Val)
4723 declare ppc_fp128 @llvm.sin.ppcf128(ppc_fp128 %Val)
4729 The '<tt>llvm.sin.*</tt>' intrinsics return the sine of the operand.
4735 The argument and return value are floating point numbers of the same type.
4741 This function returns the sine of the specified operand, returning the
4742 same values as the libm <tt>sin</tt> functions would, and handles error
4743 conditions in the same way.</p>
4746 <!-- _______________________________________________________________________ -->
4747 <div class="doc_subsubsection">
4748 <a name="int_cos">'<tt>llvm.cos.*</tt>' Intrinsic</a>
4751 <div class="doc_text">
4754 <p>This is an overloaded intrinsic. You can use <tt>llvm.cos</tt> on any
4755 floating point or vector of floating point type. Not all targets support all
4758 declare float @llvm.cos.f32(float %Val)
4759 declare double @llvm.cos.f64(double %Val)
4760 declare x86_fp80 @llvm.cos.f80(x86_fp80 %Val)
4761 declare fp128 @llvm.cos.f128(fp128 %Val)
4762 declare ppc_fp128 @llvm.cos.ppcf128(ppc_fp128 %Val)
4768 The '<tt>llvm.cos.*</tt>' intrinsics return the cosine of the operand.
4774 The argument and return value are floating point numbers of the same type.
4780 This function returns the cosine of the specified operand, returning the
4781 same values as the libm <tt>cos</tt> functions would, and handles error
4782 conditions in the same way.</p>
4785 <!-- _______________________________________________________________________ -->
4786 <div class="doc_subsubsection">
4787 <a name="int_pow">'<tt>llvm.pow.*</tt>' Intrinsic</a>
4790 <div class="doc_text">
4793 <p>This is an overloaded intrinsic. You can use <tt>llvm.pow</tt> on any
4794 floating point or vector of floating point type. Not all targets support all
4797 declare float @llvm.pow.f32(float %Val, float %Power)
4798 declare double @llvm.pow.f64(double %Val, double %Power)
4799 declare x86_fp80 @llvm.pow.f80(x86_fp80 %Val, x86_fp80 %Power)
4800 declare fp128 @llvm.pow.f128(fp128 %Val, fp128 %Power)
4801 declare ppc_fp128 @llvm.pow.ppcf128(ppc_fp128 %Val, ppc_fp128 Power)
4807 The '<tt>llvm.pow.*</tt>' intrinsics return the first operand raised to the
4808 specified (positive or negative) power.
4814 The second argument is a floating point power, and the first is a value to
4815 raise to that power.
4821 This function returns the first value raised to the second power,
4823 same values as the libm <tt>pow</tt> functions would, and handles error
4824 conditions in the same way.</p>
4828 <!-- ======================================================================= -->
4829 <div class="doc_subsection">
4830 <a name="int_manip">Bit Manipulation Intrinsics</a>
4833 <div class="doc_text">
4835 LLVM provides intrinsics for a few important bit manipulation operations.
4836 These allow efficient code generation for some algorithms.
4841 <!-- _______________________________________________________________________ -->
4842 <div class="doc_subsubsection">
4843 <a name="int_bswap">'<tt>llvm.bswap.*</tt>' Intrinsics</a>
4846 <div class="doc_text">
4849 <p>This is an overloaded intrinsic function. You can use bswap on any integer
4850 type that is an even number of bytes (i.e. BitWidth % 16 == 0).
4852 declare i16 @llvm.bswap.i16(i16 <id>)
4853 declare i32 @llvm.bswap.i32(i32 <id>)
4854 declare i64 @llvm.bswap.i64(i64 <id>)
4860 The '<tt>llvm.bswap</tt>' family of intrinsics is used to byte swap integer
4861 values with an even number of bytes (positive multiple of 16 bits). These are
4862 useful for performing operations on data that is not in the target's native
4869 The <tt>llvm.bswap.i16</tt> intrinsic returns an i16 value that has the high
4870 and low byte of the input i16 swapped. Similarly, the <tt>llvm.bswap.i32</tt>
4871 intrinsic returns an i32 value that has the four bytes of the input i32
4872 swapped, so that if the input bytes are numbered 0, 1, 2, 3 then the returned
4873 i32 will have its bytes in 3, 2, 1, 0 order. The <tt>llvm.bswap.i48</tt>,
4874 <tt>llvm.bswap.i64</tt> and other intrinsics extend this concept to
4875 additional even-byte lengths (6 bytes, 8 bytes and more, respectively).
4880 <!-- _______________________________________________________________________ -->
4881 <div class="doc_subsubsection">
4882 <a name="int_ctpop">'<tt>llvm.ctpop.*</tt>' Intrinsic</a>
4885 <div class="doc_text">
4888 <p>This is an overloaded intrinsic. You can use llvm.ctpop on any integer bit
4889 width. Not all targets support all bit widths however.
4891 declare i8 @llvm.ctpop.i8 (i8 <src>)
4892 declare i16 @llvm.ctpop.i16(i16 <src>)
4893 declare i32 @llvm.ctpop.i32(i32 <src>)
4894 declare i64 @llvm.ctpop.i64(i64 <src>)
4895 declare i256 @llvm.ctpop.i256(i256 <src>)
4901 The '<tt>llvm.ctpop</tt>' family of intrinsics counts the number of bits set in a
4908 The only argument is the value to be counted. The argument may be of any
4909 integer type. The return type must match the argument type.
4915 The '<tt>llvm.ctpop</tt>' intrinsic counts the 1's in a variable.
4919 <!-- _______________________________________________________________________ -->
4920 <div class="doc_subsubsection">
4921 <a name="int_ctlz">'<tt>llvm.ctlz.*</tt>' Intrinsic</a>
4924 <div class="doc_text">
4927 <p>This is an overloaded intrinsic. You can use <tt>llvm.ctlz</tt> on any
4928 integer bit width. Not all targets support all bit widths however.
4930 declare i8 @llvm.ctlz.i8 (i8 <src>)
4931 declare i16 @llvm.ctlz.i16(i16 <src>)
4932 declare i32 @llvm.ctlz.i32(i32 <src>)
4933 declare i64 @llvm.ctlz.i64(i64 <src>)
4934 declare i256 @llvm.ctlz.i256(i256 <src>)
4940 The '<tt>llvm.ctlz</tt>' family of intrinsic functions counts the number of
4941 leading zeros in a variable.
4947 The only argument is the value to be counted. The argument may be of any
4948 integer type. The return type must match the argument type.
4954 The '<tt>llvm.ctlz</tt>' intrinsic counts the leading (most significant) zeros
4955 in a variable. If the src == 0 then the result is the size in bits of the type
4956 of src. For example, <tt>llvm.ctlz(i32 2) = 30</tt>.
4962 <!-- _______________________________________________________________________ -->
4963 <div class="doc_subsubsection">
4964 <a name="int_cttz">'<tt>llvm.cttz.*</tt>' Intrinsic</a>
4967 <div class="doc_text">
4970 <p>This is an overloaded intrinsic. You can use <tt>llvm.cttz</tt> on any
4971 integer bit width. Not all targets support all bit widths however.
4973 declare i8 @llvm.cttz.i8 (i8 <src>)
4974 declare i16 @llvm.cttz.i16(i16 <src>)
4975 declare i32 @llvm.cttz.i32(i32 <src>)
4976 declare i64 @llvm.cttz.i64(i64 <src>)
4977 declare i256 @llvm.cttz.i256(i256 <src>)
4983 The '<tt>llvm.cttz</tt>' family of intrinsic functions counts the number of
4990 The only argument is the value to be counted. The argument may be of any
4991 integer type. The return type must match the argument type.
4997 The '<tt>llvm.cttz</tt>' intrinsic counts the trailing (least significant) zeros
4998 in a variable. If the src == 0 then the result is the size in bits of the type
4999 of src. For example, <tt>llvm.cttz(2) = 1</tt>.
5003 <!-- _______________________________________________________________________ -->
5004 <div class="doc_subsubsection">
5005 <a name="int_part_select">'<tt>llvm.part.select.*</tt>' Intrinsic</a>
5008 <div class="doc_text">
5011 <p>This is an overloaded intrinsic. You can use <tt>llvm.part.select</tt>
5012 on any integer bit width.
5014 declare i17 @llvm.part.select.i17 (i17 %val, i32 %loBit, i32 %hiBit)
5015 declare i29 @llvm.part.select.i29 (i29 %val, i32 %loBit, i32 %hiBit)
5019 <p>The '<tt>llvm.part.select</tt>' family of intrinsic functions selects a
5020 range of bits from an integer value and returns them in the same bit width as
5021 the original value.</p>
5024 <p>The first argument, <tt>%val</tt> and the result may be integer types of
5025 any bit width but they must have the same bit width. The second and third
5026 arguments must be <tt>i32</tt> type since they specify only a bit index.</p>
5029 <p>The operation of the '<tt>llvm.part.select</tt>' intrinsic has two modes
5030 of operation: forwards and reverse. If <tt>%loBit</tt> is greater than
5031 <tt>%hiBits</tt> then the intrinsic operates in reverse mode. Otherwise it
5032 operates in forward mode.</p>
5033 <p>In forward mode, this intrinsic is the equivalent of shifting <tt>%val</tt>
5034 right by <tt>%loBit</tt> bits and then ANDing it with a mask with
5035 only the <tt>%hiBit - %loBit</tt> bits set, as follows:</p>
5037 <li>The <tt>%val</tt> is shifted right (LSHR) by the number of bits specified
5038 by <tt>%loBits</tt>. This normalizes the value to the low order bits.</li>
5039 <li>The <tt>%loBits</tt> value is subtracted from the <tt>%hiBits</tt> value
5040 to determine the number of bits to retain.</li>
5041 <li>A mask of the retained bits is created by shifting a -1 value.</li>
5042 <li>The mask is ANDed with <tt>%val</tt> to produce the result.
5044 <p>In reverse mode, a similar computation is made except that the bits are
5045 returned in the reverse order. So, for example, if <tt>X</tt> has the value
5046 <tt>i16 0x0ACF (101011001111)</tt> and we apply
5047 <tt>part.select(i16 X, 8, 3)</tt> to it, we get back the value
5048 <tt>i16 0x0026 (000000100110)</tt>.</p>
5051 <div class="doc_subsubsection">
5052 <a name="int_part_set">'<tt>llvm.part.set.*</tt>' Intrinsic</a>
5055 <div class="doc_text">
5058 <p>This is an overloaded intrinsic. You can use <tt>llvm.part.set</tt>
5059 on any integer bit width.
5061 declare i17 @llvm.part.set.i17.i9 (i17 %val, i9 %repl, i32 %lo, i32 %hi)
5062 declare i29 @llvm.part.set.i29.i9 (i29 %val, i9 %repl, i32 %lo, i32 %hi)
5066 <p>The '<tt>llvm.part.set</tt>' family of intrinsic functions replaces a range
5067 of bits in an integer value with another integer value. It returns the integer
5068 with the replaced bits.</p>
5071 <p>The first argument, <tt>%val</tt> and the result may be integer types of
5072 any bit width but they must have the same bit width. <tt>%val</tt> is the value
5073 whose bits will be replaced. The second argument, <tt>%repl</tt> may be an
5074 integer of any bit width. The third and fourth arguments must be <tt>i32</tt>
5075 type since they specify only a bit index.</p>
5078 <p>The operation of the '<tt>llvm.part.set</tt>' intrinsic has two modes
5079 of operation: forwards and reverse. If <tt>%lo</tt> is greater than
5080 <tt>%hi</tt> then the intrinsic operates in reverse mode. Otherwise it
5081 operates in forward mode.</p>
5082 <p>For both modes, the <tt>%repl</tt> value is prepared for use by either
5083 truncating it down to the size of the replacement area or zero extending it
5084 up to that size.</p>
5085 <p>In forward mode, the bits between <tt>%lo</tt> and <tt>%hi</tt> (inclusive)
5086 are replaced with corresponding bits from <tt>%repl</tt>. That is the 0th bit
5087 in <tt>%repl</tt> replaces the <tt>%lo</tt>th bit in <tt>%val</tt> and etc. up
5088 to the <tt>%hi</tt>th bit.
5089 <p>In reverse mode, a similar computation is made except that the bits are
5090 reversed. That is, the <tt>0</tt>th bit in <tt>%repl</tt> replaces the
5091 <tt>%hi</tt> bit in <tt>%val</tt> and etc. down to the <tt>%lo</tt>th bit.
5094 llvm.part.set(0xFFFF, 0, 4, 7) -> 0xFF0F
5095 llvm.part.set(0xFFFF, 0, 7, 4) -> 0xFF0F
5096 llvm.part.set(0xFFFF, 1, 7, 4) -> 0xFF8F
5097 llvm.part.set(0xFFFF, F, 8, 3) -> 0xFFE7
5098 llvm.part.set(0xFFFF, 0, 3, 8) -> 0xFE07
5102 <!-- ======================================================================= -->
5103 <div class="doc_subsection">
5104 <a name="int_debugger">Debugger Intrinsics</a>
5107 <div class="doc_text">
5109 The LLVM debugger intrinsics (which all start with <tt>llvm.dbg.</tt> prefix),
5110 are described in the <a
5111 href="SourceLevelDebugging.html#format_common_intrinsics">LLVM Source Level
5112 Debugging</a> document.
5117 <!-- ======================================================================= -->
5118 <div class="doc_subsection">
5119 <a name="int_eh">Exception Handling Intrinsics</a>
5122 <div class="doc_text">
5123 <p> The LLVM exception handling intrinsics (which all start with
5124 <tt>llvm.eh.</tt> prefix), are described in the <a
5125 href="ExceptionHandling.html#format_common_intrinsics">LLVM Exception
5126 Handling</a> document. </p>
5129 <!-- ======================================================================= -->
5130 <div class="doc_subsection">
5131 <a name="int_trampoline">Trampoline Intrinsic</a>
5134 <div class="doc_text">
5136 This intrinsic makes it possible to excise one parameter, marked with
5137 the <tt>nest</tt> attribute, from a function. The result is a callable
5138 function pointer lacking the nest parameter - the caller does not need
5139 to provide a value for it. Instead, the value to use is stored in
5140 advance in a "trampoline", a block of memory usually allocated
5141 on the stack, which also contains code to splice the nest value into the
5142 argument list. This is used to implement the GCC nested function address
5146 For example, if the function is
5147 <tt>i32 f(i8* nest %c, i32 %x, i32 %y)</tt> then the resulting function
5148 pointer has signature <tt>i32 (i32, i32)*</tt>. It can be created as follows:</p>
5150 %tramp = alloca [10 x i8], align 4 ; size and alignment only correct for X86
5151 %tramp1 = getelementptr [10 x i8]* %tramp, i32 0, i32 0
5152 %p = call i8* @llvm.init.trampoline( i8* %tramp1, i8* bitcast (i32 (i8* nest , i32, i32)* @f to i8*), i8* %nval )
5153 %fp = bitcast i8* %p to i32 (i32, i32)*
5155 <p>The call <tt>%val = call i32 %fp( i32 %x, i32 %y )</tt> is then equivalent
5156 to <tt>%val = call i32 %f( i8* %nval, i32 %x, i32 %y )</tt>.</p>
5159 <!-- _______________________________________________________________________ -->
5160 <div class="doc_subsubsection">
5161 <a name="int_it">'<tt>llvm.init.trampoline</tt>' Intrinsic</a>
5163 <div class="doc_text">
5166 declare i8* @llvm.init.trampoline(i8* <tramp>, i8* <func>, i8* <nval>)
5170 This fills the memory pointed to by <tt>tramp</tt> with code
5171 and returns a function pointer suitable for executing it.
5175 The <tt>llvm.init.trampoline</tt> intrinsic takes three arguments, all
5176 pointers. The <tt>tramp</tt> argument must point to a sufficiently large
5177 and sufficiently aligned block of memory; this memory is written to by the
5178 intrinsic. Note that the size and the alignment are target-specific - LLVM
5179 currently provides no portable way of determining them, so a front-end that
5180 generates this intrinsic needs to have some target-specific knowledge.
5181 The <tt>func</tt> argument must hold a function bitcast to an <tt>i8*</tt>.
5185 The block of memory pointed to by <tt>tramp</tt> is filled with target
5186 dependent code, turning it into a function. A pointer to this function is
5187 returned, but needs to be bitcast to an
5188 <a href="#int_trampoline">appropriate function pointer type</a>
5189 before being called. The new function's signature is the same as that of
5190 <tt>func</tt> with any arguments marked with the <tt>nest</tt> attribute
5191 removed. At most one such <tt>nest</tt> argument is allowed, and it must be
5192 of pointer type. Calling the new function is equivalent to calling
5193 <tt>func</tt> with the same argument list, but with <tt>nval</tt> used for the
5194 missing <tt>nest</tt> argument. If, after calling
5195 <tt>llvm.init.trampoline</tt>, the memory pointed to by <tt>tramp</tt> is
5196 modified, then the effect of any later call to the returned function pointer is
5201 <!-- ======================================================================= -->
5202 <div class="doc_subsection">
5203 <a name="int_general">General Intrinsics</a>
5206 <div class="doc_text">
5207 <p> This class of intrinsics is designed to be generic and has
5208 no specific purpose. </p>
5211 <!-- _______________________________________________________________________ -->
5212 <div class="doc_subsubsection">
5213 <a name="int_var_annotation">'<tt>llvm.var.annotation</tt>' Intrinsic</a>
5216 <div class="doc_text">
5220 declare void @llvm.var.annotation(i8* <val>, i8* <str>, i8* <str>, i32 <int> )
5226 The '<tt>llvm.var.annotation</tt>' intrinsic
5232 The first argument is a pointer to a value, the second is a pointer to a
5233 global string, the third is a pointer to a global string which is the source
5234 file name, and the last argument is the line number.
5240 This intrinsic allows annotation of local variables with arbitrary strings.
5241 This can be useful for special purpose optimizations that want to look for these
5242 annotations. These have no other defined use, they are ignored by code
5243 generation and optimization.
5246 <!-- _______________________________________________________________________ -->
5247 <div class="doc_subsubsection">
5248 <a name="int_annotation">'<tt>llvm.annotation.*</tt>' Intrinsic</a>
5251 <div class="doc_text">
5254 <p>This is an overloaded intrinsic. You can use '<tt>llvm.annotation</tt>' on
5255 any integer bit width.
5258 declare i8 @llvm.annotation.i8(i8 <val>, i8* <str>, i8* <str>, i32 <int> )
5259 declare i16 @llvm.annotation.i16(i16 <val>, i8* <str>, i8* <str>, i32 <int> )
5260 declare i32 @llvm.annotation.i32(i32 <val>, i8* <str>, i8* <str>, i32 <int> )
5261 declare i64 @llvm.annotation.i64(i64 <val>, i8* <str>, i8* <str>, i32 <int> )
5262 declare i256 @llvm.annotation.i256(i256 <val>, i8* <str>, i8* <str>, i32 <int> )
5268 The '<tt>llvm.annotation</tt>' intrinsic.
5274 The first argument is an integer value (result of some expression),
5275 the second is a pointer to a global string, the third is a pointer to a global
5276 string which is the source file name, and the last argument is the line number.
5277 It returns the value of the first argument.
5283 This intrinsic allows annotations to be put on arbitrary expressions
5284 with arbitrary strings. This can be useful for special purpose optimizations
5285 that want to look for these annotations. These have no other defined use, they
5286 are ignored by code generation and optimization.
5289 <!-- *********************************************************************** -->
5292 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
5293 src="http://jigsaw.w3.org/css-validator/images/vcss" alt="Valid CSS!"></a>
5294 <a href="http://validator.w3.org/check/referer"><img
5295 src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!"></a>
5297 <a href="mailto:sabre@nondot.org">Chris Lattner</a><br>
5298 <a href="http://llvm.org">The LLVM Compiler Infrastructure</a><br>
5299 Last modified: $Date$