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="#namedtypes">Named Types</a></li>
26 <li><a href="#globalvars">Global Variables</a></li>
27 <li><a href="#functionstructure">Functions</a></li>
28 <li><a href="#aliasstructure">Aliases</a></li>
29 <li><a href="#paramattrs">Parameter Attributes</a></li>
30 <li><a href="#fnattrs">Function Attributes</a></li>
31 <li><a href="#gc">Garbage Collector Names</a></li>
32 <li><a href="#moduleasm">Module-Level Inline Assembly</a></li>
33 <li><a href="#datalayout">Data Layout</a></li>
36 <li><a href="#typesystem">Type System</a>
38 <li><a href="#t_classifications">Type Classifications</a></li>
39 <li><a href="#t_primitive">Primitive Types</a>
41 <li><a href="#t_floating">Floating Point Types</a></li>
42 <li><a href="#t_void">Void Type</a></li>
43 <li><a href="#t_label">Label Type</a></li>
46 <li><a href="#t_derived">Derived Types</a>
48 <li><a href="#t_integer">Integer Type</a></li>
49 <li><a href="#t_array">Array Type</a></li>
50 <li><a href="#t_function">Function Type</a></li>
51 <li><a href="#t_pointer">Pointer Type</a></li>
52 <li><a href="#t_struct">Structure Type</a></li>
53 <li><a href="#t_pstruct">Packed Structure Type</a></li>
54 <li><a href="#t_vector">Vector Type</a></li>
55 <li><a href="#t_opaque">Opaque Type</a></li>
58 <li><a href="#t_uprefs">Type Up-references</a></li>
61 <li><a href="#constants">Constants</a>
63 <li><a href="#simpleconstants">Simple Constants</a></li>
64 <li><a href="#aggregateconstants">Aggregate Constants</a></li>
65 <li><a href="#globalconstants">Global Variable and Function Addresses</a></li>
66 <li><a href="#undefvalues">Undefined Values</a></li>
67 <li><a href="#constantexprs">Constant Expressions</a></li>
70 <li><a href="#othervalues">Other Values</a>
72 <li><a href="#inlineasm">Inline Assembler Expressions</a></li>
75 <li><a href="#instref">Instruction Reference</a>
77 <li><a href="#terminators">Terminator Instructions</a>
79 <li><a href="#i_ret">'<tt>ret</tt>' Instruction</a></li>
80 <li><a href="#i_br">'<tt>br</tt>' Instruction</a></li>
81 <li><a href="#i_switch">'<tt>switch</tt>' Instruction</a></li>
82 <li><a href="#i_invoke">'<tt>invoke</tt>' Instruction</a></li>
83 <li><a href="#i_unwind">'<tt>unwind</tt>' Instruction</a></li>
84 <li><a href="#i_unreachable">'<tt>unreachable</tt>' Instruction</a></li>
87 <li><a href="#binaryops">Binary Operations</a>
89 <li><a href="#i_add">'<tt>add</tt>' Instruction</a></li>
90 <li><a href="#i_sub">'<tt>sub</tt>' Instruction</a></li>
91 <li><a href="#i_mul">'<tt>mul</tt>' Instruction</a></li>
92 <li><a href="#i_udiv">'<tt>udiv</tt>' Instruction</a></li>
93 <li><a href="#i_sdiv">'<tt>sdiv</tt>' Instruction</a></li>
94 <li><a href="#i_fdiv">'<tt>fdiv</tt>' Instruction</a></li>
95 <li><a href="#i_urem">'<tt>urem</tt>' Instruction</a></li>
96 <li><a href="#i_srem">'<tt>srem</tt>' Instruction</a></li>
97 <li><a href="#i_frem">'<tt>frem</tt>' Instruction</a></li>
100 <li><a href="#bitwiseops">Bitwise Binary Operations</a>
102 <li><a href="#i_shl">'<tt>shl</tt>' Instruction</a></li>
103 <li><a href="#i_lshr">'<tt>lshr</tt>' Instruction</a></li>
104 <li><a href="#i_ashr">'<tt>ashr</tt>' Instruction</a></li>
105 <li><a href="#i_and">'<tt>and</tt>' Instruction</a></li>
106 <li><a href="#i_or">'<tt>or</tt>' Instruction</a></li>
107 <li><a href="#i_xor">'<tt>xor</tt>' Instruction</a></li>
110 <li><a href="#vectorops">Vector Operations</a>
112 <li><a href="#i_extractelement">'<tt>extractelement</tt>' Instruction</a></li>
113 <li><a href="#i_insertelement">'<tt>insertelement</tt>' Instruction</a></li>
114 <li><a href="#i_shufflevector">'<tt>shufflevector</tt>' Instruction</a></li>
117 <li><a href="#aggregateops">Aggregate Operations</a>
119 <li><a href="#i_extractvalue">'<tt>extractvalue</tt>' Instruction</a></li>
120 <li><a href="#i_insertvalue">'<tt>insertvalue</tt>' Instruction</a></li>
123 <li><a href="#memoryops">Memory Access and Addressing Operations</a>
125 <li><a href="#i_malloc">'<tt>malloc</tt>' Instruction</a></li>
126 <li><a href="#i_free">'<tt>free</tt>' Instruction</a></li>
127 <li><a href="#i_alloca">'<tt>alloca</tt>' Instruction</a></li>
128 <li><a href="#i_load">'<tt>load</tt>' Instruction</a></li>
129 <li><a href="#i_store">'<tt>store</tt>' Instruction</a></li>
130 <li><a href="#i_getelementptr">'<tt>getelementptr</tt>' Instruction</a></li>
133 <li><a href="#convertops">Conversion Operations</a>
135 <li><a href="#i_trunc">'<tt>trunc .. to</tt>' Instruction</a></li>
136 <li><a href="#i_zext">'<tt>zext .. to</tt>' Instruction</a></li>
137 <li><a href="#i_sext">'<tt>sext .. to</tt>' Instruction</a></li>
138 <li><a href="#i_fptrunc">'<tt>fptrunc .. to</tt>' Instruction</a></li>
139 <li><a href="#i_fpext">'<tt>fpext .. to</tt>' Instruction</a></li>
140 <li><a href="#i_fptoui">'<tt>fptoui .. to</tt>' Instruction</a></li>
141 <li><a href="#i_fptosi">'<tt>fptosi .. to</tt>' Instruction</a></li>
142 <li><a href="#i_uitofp">'<tt>uitofp .. to</tt>' Instruction</a></li>
143 <li><a href="#i_sitofp">'<tt>sitofp .. to</tt>' Instruction</a></li>
144 <li><a href="#i_ptrtoint">'<tt>ptrtoint .. to</tt>' Instruction</a></li>
145 <li><a href="#i_inttoptr">'<tt>inttoptr .. to</tt>' Instruction</a></li>
146 <li><a href="#i_bitcast">'<tt>bitcast .. to</tt>' Instruction</a></li>
149 <li><a href="#otherops">Other Operations</a>
151 <li><a href="#i_icmp">'<tt>icmp</tt>' Instruction</a></li>
152 <li><a href="#i_fcmp">'<tt>fcmp</tt>' Instruction</a></li>
153 <li><a href="#i_vicmp">'<tt>vicmp</tt>' Instruction</a></li>
154 <li><a href="#i_vfcmp">'<tt>vfcmp</tt>' Instruction</a></li>
155 <li><a href="#i_phi">'<tt>phi</tt>' Instruction</a></li>
156 <li><a href="#i_select">'<tt>select</tt>' Instruction</a></li>
157 <li><a href="#i_call">'<tt>call</tt>' Instruction</a></li>
158 <li><a href="#i_va_arg">'<tt>va_arg</tt>' Instruction</a></li>
163 <li><a href="#intrinsics">Intrinsic Functions</a>
165 <li><a href="#int_varargs">Variable Argument Handling Intrinsics</a>
167 <li><a href="#int_va_start">'<tt>llvm.va_start</tt>' Intrinsic</a></li>
168 <li><a href="#int_va_end">'<tt>llvm.va_end</tt>' Intrinsic</a></li>
169 <li><a href="#int_va_copy">'<tt>llvm.va_copy</tt>' Intrinsic</a></li>
172 <li><a href="#int_gc">Accurate Garbage Collection Intrinsics</a>
174 <li><a href="#int_gcroot">'<tt>llvm.gcroot</tt>' Intrinsic</a></li>
175 <li><a href="#int_gcread">'<tt>llvm.gcread</tt>' Intrinsic</a></li>
176 <li><a href="#int_gcwrite">'<tt>llvm.gcwrite</tt>' Intrinsic</a></li>
179 <li><a href="#int_codegen">Code Generator Intrinsics</a>
181 <li><a href="#int_returnaddress">'<tt>llvm.returnaddress</tt>' Intrinsic</a></li>
182 <li><a href="#int_frameaddress">'<tt>llvm.frameaddress</tt>' Intrinsic</a></li>
183 <li><a href="#int_stacksave">'<tt>llvm.stacksave</tt>' Intrinsic</a></li>
184 <li><a href="#int_stackrestore">'<tt>llvm.stackrestore</tt>' Intrinsic</a></li>
185 <li><a href="#int_prefetch">'<tt>llvm.prefetch</tt>' Intrinsic</a></li>
186 <li><a href="#int_pcmarker">'<tt>llvm.pcmarker</tt>' Intrinsic</a></li>
187 <li><a href="#int_readcyclecounter"><tt>llvm.readcyclecounter</tt>' Intrinsic</a></li>
190 <li><a href="#int_libc">Standard C Library Intrinsics</a>
192 <li><a href="#int_memcpy">'<tt>llvm.memcpy.*</tt>' Intrinsic</a></li>
193 <li><a href="#int_memmove">'<tt>llvm.memmove.*</tt>' Intrinsic</a></li>
194 <li><a href="#int_memset">'<tt>llvm.memset.*</tt>' Intrinsic</a></li>
195 <li><a href="#int_sqrt">'<tt>llvm.sqrt.*</tt>' Intrinsic</a></li>
196 <li><a href="#int_powi">'<tt>llvm.powi.*</tt>' Intrinsic</a></li>
197 <li><a href="#int_sin">'<tt>llvm.sin.*</tt>' Intrinsic</a></li>
198 <li><a href="#int_cos">'<tt>llvm.cos.*</tt>' Intrinsic</a></li>
199 <li><a href="#int_pow">'<tt>llvm.pow.*</tt>' Intrinsic</a></li>
202 <li><a href="#int_manip">Bit Manipulation Intrinsics</a>
204 <li><a href="#int_bswap">'<tt>llvm.bswap.*</tt>' Intrinsics</a></li>
205 <li><a href="#int_ctpop">'<tt>llvm.ctpop.*</tt>' Intrinsic </a></li>
206 <li><a href="#int_ctlz">'<tt>llvm.ctlz.*</tt>' Intrinsic </a></li>
207 <li><a href="#int_cttz">'<tt>llvm.cttz.*</tt>' Intrinsic </a></li>
208 <li><a href="#int_part_select">'<tt>llvm.part.select.*</tt>' Intrinsic </a></li>
209 <li><a href="#int_part_set">'<tt>llvm.part.set.*</tt>' Intrinsic </a></li>
212 <li><a href="#int_overflow">Arithmetic with Overflow Intrinsics</a>
214 <li><a href="#int_sadd_overflow">'<tt>llvm.sadd.with.overflow.*</tt> Intrinsics</a></li>
215 <li><a href="#int_uadd_overflow">'<tt>llvm.uadd.with.overflow.*</tt> Intrinsics</a></li>
216 <li><a href="#int_ssub_overflow">'<tt>llvm.ssub.with.overflow.*</tt> Intrinsics</a></li>
217 <li><a href="#int_usub_overflow">'<tt>llvm.usub.with.overflow.*</tt> Intrinsics</a></li>
218 <li><a href="#int_smul_overflow">'<tt>llvm.smul.with.overflow.*</tt> Intrinsics</a></li>
219 <li><a href="#int_umul_overflow">'<tt>llvm.umul.with.overflow.*</tt> Intrinsics</a></li>
222 <li><a href="#int_debugger">Debugger intrinsics</a></li>
223 <li><a href="#int_eh">Exception Handling intrinsics</a></li>
224 <li><a href="#int_trampoline">Trampoline Intrinsic</a>
226 <li><a href="#int_it">'<tt>llvm.init.trampoline</tt>' Intrinsic</a></li>
229 <li><a href="#int_atomics">Atomic intrinsics</a>
231 <li><a href="#int_memory_barrier"><tt>llvm.memory_barrier</tt></a></li>
232 <li><a href="#int_atomic_cmp_swap"><tt>llvm.atomic.cmp.swap</tt></a></li>
233 <li><a href="#int_atomic_swap"><tt>llvm.atomic.swap</tt></a></li>
234 <li><a href="#int_atomic_load_add"><tt>llvm.atomic.load.add</tt></a></li>
235 <li><a href="#int_atomic_load_sub"><tt>llvm.atomic.load.sub</tt></a></li>
236 <li><a href="#int_atomic_load_and"><tt>llvm.atomic.load.and</tt></a></li>
237 <li><a href="#int_atomic_load_nand"><tt>llvm.atomic.load.nand</tt></a></li>
238 <li><a href="#int_atomic_load_or"><tt>llvm.atomic.load.or</tt></a></li>
239 <li><a href="#int_atomic_load_xor"><tt>llvm.atomic.load.xor</tt></a></li>
240 <li><a href="#int_atomic_load_max"><tt>llvm.atomic.load.max</tt></a></li>
241 <li><a href="#int_atomic_load_min"><tt>llvm.atomic.load.min</tt></a></li>
242 <li><a href="#int_atomic_load_umax"><tt>llvm.atomic.load.umax</tt></a></li>
243 <li><a href="#int_atomic_load_umin"><tt>llvm.atomic.load.umin</tt></a></li>
246 <li><a href="#int_general">General intrinsics</a>
248 <li><a href="#int_var_annotation">
249 '<tt>llvm.var.annotation</tt>' Intrinsic</a></li>
250 <li><a href="#int_annotation">
251 '<tt>llvm.annotation.*</tt>' Intrinsic</a></li>
252 <li><a href="#int_trap">
253 '<tt>llvm.trap</tt>' Intrinsic</a></li>
254 <li><a href="#int_stackprotector">
255 '<tt>llvm.stackprotector</tt>' Intrinsic</a></li>
262 <div class="doc_author">
263 <p>Written by <a href="mailto:sabre@nondot.org">Chris Lattner</a>
264 and <a href="mailto:vadve@cs.uiuc.edu">Vikram Adve</a></p>
267 <!-- *********************************************************************** -->
268 <div class="doc_section"> <a name="abstract">Abstract </a></div>
269 <!-- *********************************************************************** -->
271 <div class="doc_text">
272 <p>This document is a reference manual for the LLVM assembly language.
273 LLVM is a Static Single Assignment (SSA) based representation that provides
274 type safety, low-level operations, flexibility, and the capability of
275 representing 'all' high-level languages cleanly. It is the common code
276 representation used throughout all phases of the LLVM compilation
280 <!-- *********************************************************************** -->
281 <div class="doc_section"> <a name="introduction">Introduction</a> </div>
282 <!-- *********************************************************************** -->
284 <div class="doc_text">
286 <p>The LLVM code representation is designed to be used in three
287 different forms: as an in-memory compiler IR, as an on-disk bitcode
288 representation (suitable for fast loading by a Just-In-Time compiler),
289 and as a human readable assembly language representation. This allows
290 LLVM to provide a powerful intermediate representation for efficient
291 compiler transformations and analysis, while providing a natural means
292 to debug and visualize the transformations. The three different forms
293 of LLVM are all equivalent. This document describes the human readable
294 representation and notation.</p>
296 <p>The LLVM representation aims to be light-weight and low-level
297 while being expressive, typed, and extensible at the same time. It
298 aims to be a "universal IR" of sorts, by being at a low enough level
299 that high-level ideas may be cleanly mapped to it (similar to how
300 microprocessors are "universal IR's", allowing many source languages to
301 be mapped to them). By providing type information, LLVM can be used as
302 the target of optimizations: for example, through pointer analysis, it
303 can be proven that a C automatic variable is never accessed outside of
304 the current function... allowing it to be promoted to a simple SSA
305 value instead of a memory location.</p>
309 <!-- _______________________________________________________________________ -->
310 <div class="doc_subsubsection"> <a name="wellformed">Well-Formedness</a> </div>
312 <div class="doc_text">
314 <p>It is important to note that this document describes 'well formed'
315 LLVM assembly language. There is a difference between what the parser
316 accepts and what is considered 'well formed'. For example, the
317 following instruction is syntactically okay, but not well formed:</p>
319 <div class="doc_code">
321 %x = <a href="#i_add">add</a> i32 1, %x
325 <p>...because the definition of <tt>%x</tt> does not dominate all of
326 its uses. The LLVM infrastructure provides a verification pass that may
327 be used to verify that an LLVM module is well formed. This pass is
328 automatically run by the parser after parsing input assembly and by
329 the optimizer before it outputs bitcode. The violations pointed out
330 by the verifier pass indicate bugs in transformation passes or input to
334 <!-- Describe the typesetting conventions here. -->
336 <!-- *********************************************************************** -->
337 <div class="doc_section"> <a name="identifiers">Identifiers</a> </div>
338 <!-- *********************************************************************** -->
340 <div class="doc_text">
342 <p>LLVM identifiers come in two basic types: global and local. Global
343 identifiers (functions, global variables) begin with the @ character. Local
344 identifiers (register names, types) begin with the % character. Additionally,
345 there are three different formats for identifiers, for different purposes:</p>
348 <li>Named values are represented as a string of characters with their prefix.
349 For example, %foo, @DivisionByZero, %a.really.long.identifier. The actual
350 regular expression used is '<tt>[%@][a-zA-Z$._][a-zA-Z$._0-9]*</tt>'.
351 Identifiers which require other characters in their names can be surrounded
352 with quotes. Special characters may be escaped using "\xx" where xx is the
353 ASCII code for the character in hexadecimal. In this way, any character can
354 be used in a name value, even quotes themselves.
356 <li>Unnamed values are represented as an unsigned numeric value with their
357 prefix. For example, %12, @2, %44.</li>
359 <li>Constants, which are described in a <a href="#constants">section about
360 constants</a>, below.</li>
363 <p>LLVM requires that values start with a prefix for two reasons: Compilers
364 don't need to worry about name clashes with reserved words, and the set of
365 reserved words may be expanded in the future without penalty. Additionally,
366 unnamed identifiers allow a compiler to quickly come up with a temporary
367 variable without having to avoid symbol table conflicts.</p>
369 <p>Reserved words in LLVM are very similar to reserved words in other
370 languages. There are keywords for different opcodes
371 ('<tt><a href="#i_add">add</a></tt>',
372 '<tt><a href="#i_bitcast">bitcast</a></tt>',
373 '<tt><a href="#i_ret">ret</a></tt>', etc...), for primitive type names ('<tt><a
374 href="#t_void">void</a></tt>', '<tt><a href="#t_primitive">i32</a></tt>', etc...),
375 and others. These reserved words cannot conflict with variable names, because
376 none of them start with a prefix character ('%' or '@').</p>
378 <p>Here is an example of LLVM code to multiply the integer variable
379 '<tt>%X</tt>' by 8:</p>
383 <div class="doc_code">
385 %result = <a href="#i_mul">mul</a> i32 %X, 8
389 <p>After strength reduction:</p>
391 <div class="doc_code">
393 %result = <a href="#i_shl">shl</a> i32 %X, i8 3
397 <p>And the hard way:</p>
399 <div class="doc_code">
401 <a href="#i_add">add</a> i32 %X, %X <i>; yields {i32}:%0</i>
402 <a href="#i_add">add</a> i32 %0, %0 <i>; yields {i32}:%1</i>
403 %result = <a href="#i_add">add</a> i32 %1, %1
407 <p>This last way of multiplying <tt>%X</tt> by 8 illustrates several
408 important lexical features of LLVM:</p>
412 <li>Comments are delimited with a '<tt>;</tt>' and go until the end of
415 <li>Unnamed temporaries are created when the result of a computation is not
416 assigned to a named value.</li>
418 <li>Unnamed temporaries are numbered sequentially</li>
422 <p>...and it also shows a convention that we follow in this document. When
423 demonstrating instructions, we will follow an instruction with a comment that
424 defines the type and name of value produced. Comments are shown in italic
429 <!-- *********************************************************************** -->
430 <div class="doc_section"> <a name="highlevel">High Level Structure</a> </div>
431 <!-- *********************************************************************** -->
433 <!-- ======================================================================= -->
434 <div class="doc_subsection"> <a name="modulestructure">Module Structure</a>
437 <div class="doc_text">
439 <p>LLVM programs are composed of "Module"s, each of which is a
440 translation unit of the input programs. Each module consists of
441 functions, global variables, and symbol table entries. Modules may be
442 combined together with the LLVM linker, which merges function (and
443 global variable) definitions, resolves forward declarations, and merges
444 symbol table entries. Here is an example of the "hello world" module:</p>
446 <div class="doc_code">
447 <pre><i>; Declare the string constant as a global constant...</i>
448 <a href="#identifiers">@.LC0</a> = <a href="#linkage_internal">internal</a> <a
449 href="#globalvars">constant</a> <a href="#t_array">[13 x i8]</a> c"hello world\0A\00" <i>; [13 x i8]*</i>
451 <i>; External declaration of the puts function</i>
452 <a href="#functionstructure">declare</a> i32 @puts(i8 *) <i>; i32(i8 *)* </i>
454 <i>; Definition of main function</i>
455 define i32 @main() { <i>; i32()* </i>
456 <i>; Convert [13 x i8]* to i8 *...</i>
458 href="#i_getelementptr">getelementptr</a> [13 x i8]* @.LC0, i64 0, i64 0 <i>; i8 *</i>
460 <i>; Call puts function to write out the string to stdout...</i>
462 href="#i_call">call</a> i32 @puts(i8 * %cast210) <i>; i32</i>
464 href="#i_ret">ret</a> i32 0<br>}<br>
468 <p>This example is made up of a <a href="#globalvars">global variable</a>
469 named "<tt>.LC0</tt>", an external declaration of the "<tt>puts</tt>"
470 function, and a <a href="#functionstructure">function definition</a>
471 for "<tt>main</tt>".</p>
473 <p>In general, a module is made up of a list of global values,
474 where both functions and global variables are global values. Global values are
475 represented by a pointer to a memory location (in this case, a pointer to an
476 array of char, and a pointer to a function), and have one of the following <a
477 href="#linkage">linkage types</a>.</p>
481 <!-- ======================================================================= -->
482 <div class="doc_subsection">
483 <a name="linkage">Linkage Types</a>
486 <div class="doc_text">
489 All Global Variables and Functions have one of the following types of linkage:
494 <dt><tt><b><a name="linkage_private">private</a></b></tt>: </dt>
496 <dd>Global values with private linkage are only directly accessible by
497 objects in the current module. In particular, linking code into a module with
498 an private global value may cause the private to be renamed as necessary to
499 avoid collisions. Because the symbol is private to the module, all
500 references can be updated. This doesn't show up in any symbol table in the
504 <dt><tt><b><a name="linkage_internal">internal</a></b></tt>: </dt>
506 <dd> Similar to private, but the value shows as a local symbol (STB_LOCAL in
507 the case of ELF) in the object file. This corresponds to the notion of the
508 '<tt>static</tt>' keyword in C.
511 <dt><tt><b><a name="linkage_linkonce">linkonce</a></b></tt>: </dt>
513 <dd>Globals with "<tt>linkonce</tt>" linkage are merged with other globals of
514 the same name when linkage occurs. This is typically used to implement
515 inline functions, templates, or other code which must be generated in each
516 translation unit that uses it. Unreferenced <tt>linkonce</tt> globals are
517 allowed to be discarded.
520 <dt><tt><b><a name="linkage_common">common</a></b></tt>: </dt>
522 <dd>"<tt>common</tt>" linkage is exactly the same as <tt>linkonce</tt>
523 linkage, except that unreferenced <tt>common</tt> globals may not be
524 discarded. This is used for globals that may be emitted in multiple
525 translation units, but that are not guaranteed to be emitted into every
526 translation unit that uses them. One example of this is tentative
527 definitions in C, such as "<tt>int X;</tt>" at global scope.
530 <dt><tt><b><a name="linkage_weak">weak</a></b></tt>: </dt>
532 <dd>"<tt>weak</tt>" linkage is the same as <tt>common</tt> linkage, except
533 that some targets may choose to emit different assembly sequences for them
534 for target-dependent reasons. This is used for globals that are declared
535 "weak" in C source code.
538 <dt><tt><b><a name="linkage_appending">appending</a></b></tt>: </dt>
540 <dd>"<tt>appending</tt>" linkage may only be applied to global variables of
541 pointer to array type. When two global variables with appending linkage are
542 linked together, the two global arrays are appended together. This is the
543 LLVM, typesafe, equivalent of having the system linker append together
544 "sections" with identical names when .o files are linked.
547 <dt><tt><b><a name="linkage_externweak">extern_weak</a></b></tt>: </dt>
548 <dd>The semantics of this linkage follow the ELF object file model: the
549 symbol is weak until linked, if not linked, the symbol becomes null instead
550 of being an undefined reference.
553 <dt><tt><b><a name="linkage_external">externally visible</a></b></tt>:</dt>
555 <dd>If none of the above identifiers are used, the global is externally
556 visible, meaning that it participates in linkage and can be used to resolve
557 external symbol references.
562 The next two types of linkage are targeted for Microsoft Windows platform
563 only. They are designed to support importing (exporting) symbols from (to)
564 DLLs (Dynamic Link Libraries).
568 <dt><tt><b><a name="linkage_dllimport">dllimport</a></b></tt>: </dt>
570 <dd>"<tt>dllimport</tt>" linkage causes the compiler to reference a function
571 or variable via a global pointer to a pointer that is set up by the DLL
572 exporting the symbol. On Microsoft Windows targets, the pointer name is
573 formed by combining <code>__imp_</code> and the function or variable name.
576 <dt><tt><b><a name="linkage_dllexport">dllexport</a></b></tt>: </dt>
578 <dd>"<tt>dllexport</tt>" linkage causes the compiler to provide a global
579 pointer to a pointer in a DLL, so that it can be referenced with the
580 <tt>dllimport</tt> attribute. On Microsoft Windows targets, the pointer
581 name is formed by combining <code>__imp_</code> and the function or variable
587 <p>For example, since the "<tt>.LC0</tt>"
588 variable is defined to be internal, if another module defined a "<tt>.LC0</tt>"
589 variable and was linked with this one, one of the two would be renamed,
590 preventing a collision. Since "<tt>main</tt>" and "<tt>puts</tt>" are
591 external (i.e., lacking any linkage declarations), they are accessible
592 outside of the current module.</p>
593 <p>It is illegal for a function <i>declaration</i>
594 to have any linkage type other than "externally visible", <tt>dllimport</tt>,
595 or <tt>extern_weak</tt>.</p>
596 <p>Aliases can have only <tt>external</tt>, <tt>internal</tt> and <tt>weak</tt>
600 <!-- ======================================================================= -->
601 <div class="doc_subsection">
602 <a name="callingconv">Calling Conventions</a>
605 <div class="doc_text">
607 <p>LLVM <a href="#functionstructure">functions</a>, <a href="#i_call">calls</a>
608 and <a href="#i_invoke">invokes</a> can all have an optional calling convention
609 specified for the call. The calling convention of any pair of dynamic
610 caller/callee must match, or the behavior of the program is undefined. The
611 following calling conventions are supported by LLVM, and more may be added in
615 <dt><b>"<tt>ccc</tt>" - The C calling convention</b>:</dt>
617 <dd>This calling convention (the default if no other calling convention is
618 specified) matches the target C calling conventions. This calling convention
619 supports varargs function calls and tolerates some mismatch in the declared
620 prototype and implemented declaration of the function (as does normal C).
623 <dt><b>"<tt>fastcc</tt>" - The fast calling convention</b>:</dt>
625 <dd>This calling convention attempts to make calls as fast as possible
626 (e.g. by passing things in registers). This calling convention allows the
627 target to use whatever tricks it wants to produce fast code for the target,
628 without having to conform to an externally specified ABI (Application Binary
629 Interface). Implementations of this convention should allow arbitrary
630 <a href="CodeGenerator.html#tailcallopt">tail call optimization</a> to be
631 supported. This calling convention does not support varargs and requires the
632 prototype of all callees to exactly match the prototype of the function
636 <dt><b>"<tt>coldcc</tt>" - The cold calling convention</b>:</dt>
638 <dd>This calling convention attempts to make code in the caller as efficient
639 as possible under the assumption that the call is not commonly executed. As
640 such, these calls often preserve all registers so that the call does not break
641 any live ranges in the caller side. This calling convention does not support
642 varargs and requires the prototype of all callees to exactly match the
643 prototype of the function definition.
646 <dt><b>"<tt>cc <<em>n</em>></tt>" - Numbered convention</b>:</dt>
648 <dd>Any calling convention may be specified by number, allowing
649 target-specific calling conventions to be used. Target specific calling
650 conventions start at 64.
654 <p>More calling conventions can be added/defined on an as-needed basis, to
655 support pascal conventions or any other well-known target-independent
660 <!-- ======================================================================= -->
661 <div class="doc_subsection">
662 <a name="visibility">Visibility Styles</a>
665 <div class="doc_text">
668 All Global Variables and Functions have one of the following visibility styles:
672 <dt><b>"<tt>default</tt>" - Default style</b>:</dt>
674 <dd>On targets that use the ELF object file format, default visibility means
675 that the declaration is visible to other
676 modules and, in shared libraries, means that the declared entity may be
677 overridden. On Darwin, default visibility means that the declaration is
678 visible to other modules. Default visibility corresponds to "external
679 linkage" in the language.
682 <dt><b>"<tt>hidden</tt>" - Hidden style</b>:</dt>
684 <dd>Two declarations of an object with hidden visibility refer to the same
685 object if they are in the same shared object. Usually, hidden visibility
686 indicates that the symbol will not be placed into the dynamic symbol table,
687 so no other module (executable or shared library) can reference it
691 <dt><b>"<tt>protected</tt>" - Protected style</b>:</dt>
693 <dd>On ELF, protected visibility indicates that the symbol will be placed in
694 the dynamic symbol table, but that references within the defining module will
695 bind to the local symbol. That is, the symbol cannot be overridden by another
702 <!-- ======================================================================= -->
703 <div class="doc_subsection">
704 <a name="namedtypes">Named Types</a>
707 <div class="doc_text">
709 <p>LLVM IR allows you to specify name aliases for certain types. This can make
710 it easier to read the IR and make the IR more condensed (particularly when
711 recursive types are involved). An example of a name specification is:
714 <div class="doc_code">
716 %mytype = type { %mytype*, i32 }
720 <p>You may give a name to any <a href="#typesystem">type</a> except "<a
721 href="t_void">void</a>". Type name aliases may be used anywhere a type is
722 expected with the syntax "%mytype".</p>
724 <p>Note that type names are aliases for the structural type that they indicate,
725 and that you can therefore specify multiple names for the same type. This often
726 leads to confusing behavior when dumping out a .ll file. Since LLVM IR uses
727 structural typing, the name is not part of the type. When printing out LLVM IR,
728 the printer will pick <em>one name</em> to render all types of a particular
729 shape. This means that if you have code where two different source types end up
730 having the same LLVM type, that the dumper will sometimes print the "wrong" or
731 unexpected type. This is an important design point and isn't going to
736 <!-- ======================================================================= -->
737 <div class="doc_subsection">
738 <a name="globalvars">Global Variables</a>
741 <div class="doc_text">
743 <p>Global variables define regions of memory allocated at compilation time
744 instead of run-time. Global variables may optionally be initialized, may have
745 an explicit section to be placed in, and may have an optional explicit alignment
746 specified. A variable may be defined as "thread_local", which means that it
747 will not be shared by threads (each thread will have a separated copy of the
748 variable). A variable may be defined as a global "constant," which indicates
749 that the contents of the variable will <b>never</b> be modified (enabling better
750 optimization, allowing the global data to be placed in the read-only section of
751 an executable, etc). Note that variables that need runtime initialization
752 cannot be marked "constant" as there is a store to the variable.</p>
755 LLVM explicitly allows <em>declarations</em> of global variables to be marked
756 constant, even if the final definition of the global is not. This capability
757 can be used to enable slightly better optimization of the program, but requires
758 the language definition to guarantee that optimizations based on the
759 'constantness' are valid for the translation units that do not include the
763 <p>As SSA values, global variables define pointer values that are in
764 scope (i.e. they dominate) all basic blocks in the program. Global
765 variables always define a pointer to their "content" type because they
766 describe a region of memory, and all memory objects in LLVM are
767 accessed through pointers.</p>
769 <p>A global variable may be declared to reside in a target-specifc numbered
770 address space. For targets that support them, address spaces may affect how
771 optimizations are performed and/or what target instructions are used to access
772 the variable. The default address space is zero. The address space qualifier
773 must precede any other attributes.</p>
775 <p>LLVM allows an explicit section to be specified for globals. If the target
776 supports it, it will emit globals to the section specified.</p>
778 <p>An explicit alignment may be specified for a global. If not present, or if
779 the alignment is set to zero, the alignment of the global is set by the target
780 to whatever it feels convenient. If an explicit alignment is specified, the
781 global is forced to have at least that much alignment. All alignments must be
784 <p>For example, the following defines a global in a numbered address space with
785 an initializer, section, and alignment:</p>
787 <div class="doc_code">
789 @G = addrspace(5) constant float 1.0, section "foo", align 4
796 <!-- ======================================================================= -->
797 <div class="doc_subsection">
798 <a name="functionstructure">Functions</a>
801 <div class="doc_text">
803 <p>LLVM function definitions consist of the "<tt>define</tt>" keyord,
804 an optional <a href="#linkage">linkage type</a>, an optional
805 <a href="#visibility">visibility style</a>, an optional
806 <a href="#callingconv">calling convention</a>, a return type, an optional
807 <a href="#paramattrs">parameter attribute</a> for the return type, a function
808 name, a (possibly empty) argument list (each with optional
809 <a href="#paramattrs">parameter attributes</a>), optional
810 <a href="#fnattrs">function attributes</a>, an optional section,
811 an optional alignment, an optional <a href="#gc">garbage collector name</a>,
812 an opening curly brace, a list of basic blocks, and a closing curly brace.
814 LLVM function declarations consist of the "<tt>declare</tt>" keyword, an
815 optional <a href="#linkage">linkage type</a>, an optional
816 <a href="#visibility">visibility style</a>, an optional
817 <a href="#callingconv">calling convention</a>, a return type, an optional
818 <a href="#paramattrs">parameter attribute</a> for the return type, a function
819 name, a possibly empty list of arguments, an optional alignment, and an optional
820 <a href="#gc">garbage collector name</a>.</p>
822 <p>A function definition contains a list of basic blocks, forming the CFG
823 (Control Flow Graph) for
824 the function. Each basic block may optionally start with a label (giving the
825 basic block a symbol table entry), contains a list of instructions, and ends
826 with a <a href="#terminators">terminator</a> instruction (such as a branch or
827 function return).</p>
829 <p>The first basic block in a function is special in two ways: it is immediately
830 executed on entrance to the function, and it is not allowed to have predecessor
831 basic blocks (i.e. there can not be any branches to the entry block of a
832 function). Because the block can have no predecessors, it also cannot have any
833 <a href="#i_phi">PHI nodes</a>.</p>
835 <p>LLVM allows an explicit section to be specified for functions. If the target
836 supports it, it will emit functions to the section specified.</p>
838 <p>An explicit alignment may be specified for a function. If not present, or if
839 the alignment is set to zero, the alignment of the function is set by the target
840 to whatever it feels convenient. If an explicit alignment is specified, the
841 function is forced to have at least that much alignment. All alignments must be
846 <div class="doc_code">
848 define [<a href="#linkage">linkage</a>] [<a href="#visibility">visibility</a>]
849 [<a href="#callingconv">cconv</a>] [<a href="#paramattrs">ret attrs</a>]
850 <ResultType> @<FunctionName> ([argument list])
851 [<a href="#fnattrs">fn Attrs</a>] [section "name"] [align N]
852 [<a href="#gc">gc</a>] { ... }
859 <!-- ======================================================================= -->
860 <div class="doc_subsection">
861 <a name="aliasstructure">Aliases</a>
863 <div class="doc_text">
864 <p>Aliases act as "second name" for the aliasee value (which can be either
865 function, global variable, another alias or bitcast of global value). Aliases
866 may have an optional <a href="#linkage">linkage type</a>, and an
867 optional <a href="#visibility">visibility style</a>.</p>
871 <div class="doc_code">
873 @<Name> = alias [Linkage] [Visibility] <AliaseeTy> @<Aliasee>
881 <!-- ======================================================================= -->
882 <div class="doc_subsection"><a name="paramattrs">Parameter Attributes</a></div>
883 <div class="doc_text">
884 <p>The return type and each parameter of a function type may have a set of
885 <i>parameter attributes</i> associated with them. Parameter attributes are
886 used to communicate additional information about the result or parameters of
887 a function. Parameter attributes are considered to be part of the function,
888 not of the function type, so functions with different parameter attributes
889 can have the same function type.</p>
891 <p>Parameter attributes are simple keywords that follow the type specified. If
892 multiple parameter attributes are needed, they are space separated. For
895 <div class="doc_code">
897 declare i32 @printf(i8* noalias nocapture, ...)
898 declare i32 @atoi(i8 zeroext)
899 declare signext i8 @returns_signed_char()
903 <p>Note that any attributes for the function result (<tt>nounwind</tt>,
904 <tt>readonly</tt>) come immediately after the argument list.</p>
906 <p>Currently, only the following parameter attributes are defined:</p>
908 <dt><tt>zeroext</tt></dt>
909 <dd>This indicates to the code generator that the parameter or return value
910 should be zero-extended to a 32-bit value by the caller (for a parameter)
911 or the callee (for a return value).</dd>
913 <dt><tt>signext</tt></dt>
914 <dd>This indicates to the code generator that the parameter or return value
915 should be sign-extended to a 32-bit value by the caller (for a parameter)
916 or the callee (for a return value).</dd>
918 <dt><tt>inreg</tt></dt>
919 <dd>This indicates that this parameter or return value should be treated
920 in a special target-dependent fashion during while emitting code for a
921 function call or return (usually, by putting it in a register as opposed
922 to memory, though some targets use it to distinguish between two different
923 kinds of registers). Use of this attribute is target-specific.</dd>
925 <dt><tt><a name="byval">byval</a></tt></dt>
926 <dd>This indicates that the pointer parameter should really be passed by
927 value to the function. The attribute implies that a hidden copy of the
928 pointee is made between the caller and the callee, so the callee is unable
929 to modify the value in the callee. This attribute is only valid on LLVM
930 pointer arguments. It is generally used to pass structs and arrays by
931 value, but is also valid on pointers to scalars. The copy is considered to
932 belong to the caller not the callee (for example,
933 <tt><a href="#readonly">readonly</a></tt> functions should not write to
934 <tt>byval</tt> parameters). This is not a valid attribute for return
935 values. The byval attribute also supports specifying an alignment with the
936 align attribute. This has a target-specific effect on the code generator
937 that usually indicates a desired alignment for the synthesized stack
940 <dt><tt>sret</tt></dt>
941 <dd>This indicates that the pointer parameter specifies the address of a
942 structure that is the return value of the function in the source program.
943 This pointer must be guaranteed by the caller to be valid: loads and stores
944 to the structure may be assumed by the callee to not to trap. This may only
945 be applied to the first parameter. This is not a valid attribute for
948 <dt><tt>noalias</tt></dt>
949 <dd>This indicates that the pointer does not alias any global or any other
950 parameter. The caller is responsible for ensuring that this is the
951 case. On a function return value, <tt>noalias</tt> additionally indicates
952 that the pointer does not alias any other pointers visible to the
953 caller. For further details, please see the discussion of the NoAlias
955 <a href="http://llvm.org/docs/AliasAnalysis.html#MustMayNo">alias
958 <dt><tt>nocapture</tt></dt>
959 <dd>This indicates that the callee does not make any copies of the pointer
960 that outlive the callee itself. This is not a valid attribute for return
963 <dt><tt>nest</tt></dt>
964 <dd>This indicates that the pointer parameter can be excised using the
965 <a href="#int_trampoline">trampoline intrinsics</a>. This is not a valid
966 attribute for return values.</dd>
971 <!-- ======================================================================= -->
972 <div class="doc_subsection">
973 <a name="gc">Garbage Collector Names</a>
976 <div class="doc_text">
977 <p>Each function may specify a garbage collector name, which is simply a
980 <div class="doc_code"><pre
981 >define void @f() gc "name" { ...</pre></div>
983 <p>The compiler declares the supported values of <i>name</i>. Specifying a
984 collector which will cause the compiler to alter its output in order to support
985 the named garbage collection algorithm.</p>
988 <!-- ======================================================================= -->
989 <div class="doc_subsection">
990 <a name="fnattrs">Function Attributes</a>
993 <div class="doc_text">
995 <p>Function attributes are set to communicate additional information about
996 a function. Function attributes are considered to be part of the function,
997 not of the function type, so functions with different parameter attributes
998 can have the same function type.</p>
1000 <p>Function attributes are simple keywords that follow the type specified. If
1001 multiple attributes are needed, they are space separated. For
1004 <div class="doc_code">
1006 define void @f() noinline { ... }
1007 define void @f() alwaysinline { ... }
1008 define void @f() alwaysinline optsize { ... }
1009 define void @f() optsize
1014 <dt><tt>alwaysinline</tt></dt>
1015 <dd>This attribute indicates that the inliner should attempt to inline this
1016 function into callers whenever possible, ignoring any active inlining size
1017 threshold for this caller.</dd>
1019 <dt><tt>noinline</tt></dt>
1020 <dd>This attribute indicates that the inliner should never inline this function
1021 in any situation. This attribute may not be used together with the
1022 <tt>alwaysinline</tt> attribute.</dd>
1024 <dt><tt>optsize</tt></dt>
1025 <dd>This attribute suggests that optimization passes and code generator passes
1026 make choices that keep the code size of this function low, and otherwise do
1027 optimizations specifically to reduce code size.</dd>
1029 <dt><tt>noreturn</tt></dt>
1030 <dd>This function attribute indicates that the function never returns normally.
1031 This produces undefined behavior at runtime if the function ever does
1032 dynamically return.</dd>
1034 <dt><tt>nounwind</tt></dt>
1035 <dd>This function attribute indicates that the function never returns with an
1036 unwind or exceptional control flow. If the function does unwind, its runtime
1037 behavior is undefined.</dd>
1039 <dt><tt>readnone</tt></dt>
1040 <dd>This attribute indicates that the function computes its result (or the
1041 exception it throws) based strictly on its arguments, without dereferencing any
1042 pointer arguments or otherwise accessing any mutable state (e.g. memory, control
1043 registers, etc) visible to caller functions. It does not write through any
1044 pointer arguments (including <tt><a href="#byval">byval</a></tt> arguments) and
1045 never changes any state visible to callers.</dd>
1047 <dt><tt><a name="readonly">readonly</a></tt></dt>
1048 <dd>This attribute indicates that the function does not write through any
1049 pointer arguments (including <tt><a href="#byval">byval</a></tt> arguments)
1050 or otherwise modify any state (e.g. memory, control registers, etc) visible to
1051 caller functions. It may dereference pointer arguments and read state that may
1052 be set in the caller. A readonly function always returns the same value (or
1053 throws the same exception) when called with the same set of arguments and global
1056 <dt><tt><a name="ssp">ssp</a></tt></dt>
1057 <dd>This attribute indicates that the function should emit a stack smashing
1058 protector. It is in the form of a "canary"—a random value placed on the
1059 stack before the local variables that's checked upon return from the function to
1060 see if it has been overwritten. A heuristic is used to determine if a function
1061 needs stack protectors or not.
1063 <p>If a function that has an <tt>ssp</tt> attribute is inlined into a function
1064 that doesn't have an <tt>ssp</tt> attribute, then the resulting function will
1065 have an <tt>ssp</tt> attribute.</p></dd>
1067 <dt><tt>sspreq</tt></dt>
1068 <dd>This attribute indicates that the function should <em>always</em> emit a
1069 stack smashing protector. This overrides the <tt><a href="#ssp">ssp</a></tt>
1072 <p>If a function that has an <tt>sspreq</tt> attribute is inlined into a
1073 function that doesn't have an <tt>sspreq</tt> attribute or which has
1074 an <tt>ssp</tt> attribute, then the resulting function will have
1075 an <tt>sspreq</tt> attribute.</p></dd>
1080 <!-- ======================================================================= -->
1081 <div class="doc_subsection">
1082 <a name="moduleasm">Module-Level Inline Assembly</a>
1085 <div class="doc_text">
1087 Modules may contain "module-level inline asm" blocks, which corresponds to the
1088 GCC "file scope inline asm" blocks. These blocks are internally concatenated by
1089 LLVM and treated as a single unit, but may be separated in the .ll file if
1090 desired. The syntax is very simple:
1093 <div class="doc_code">
1095 module asm "inline asm code goes here"
1096 module asm "more can go here"
1100 <p>The strings can contain any character by escaping non-printable characters.
1101 The escape sequence used is simply "\xx" where "xx" is the two digit hex code
1106 The inline asm code is simply printed to the machine code .s file when
1107 assembly code is generated.
1111 <!-- ======================================================================= -->
1112 <div class="doc_subsection">
1113 <a name="datalayout">Data Layout</a>
1116 <div class="doc_text">
1117 <p>A module may specify a target specific data layout string that specifies how
1118 data is to be laid out in memory. The syntax for the data layout is simply:</p>
1119 <pre> target datalayout = "<i>layout specification</i>"</pre>
1120 <p>The <i>layout specification</i> consists of a list of specifications
1121 separated by the minus sign character ('-'). Each specification starts with a
1122 letter and may include other information after the letter to define some
1123 aspect of the data layout. The specifications accepted are as follows: </p>
1126 <dd>Specifies that the target lays out data in big-endian form. That is, the
1127 bits with the most significance have the lowest address location.</dd>
1129 <dd>Specifies that the target lays out data in little-endian form. That is,
1130 the bits with the least significance have the lowest address location.</dd>
1131 <dt><tt>p:<i>size</i>:<i>abi</i>:<i>pref</i></tt></dt>
1132 <dd>This specifies the <i>size</i> of a pointer and its <i>abi</i> and
1133 <i>preferred</i> alignments. All sizes are in bits. Specifying the <i>pref</i>
1134 alignment is optional. If omitted, the preceding <tt>:</tt> should be omitted
1136 <dt><tt>i<i>size</i>:<i>abi</i>:<i>pref</i></tt></dt>
1137 <dd>This specifies the alignment for an integer type of a given bit
1138 <i>size</i>. The value of <i>size</i> must be in the range [1,2^23).</dd>
1139 <dt><tt>v<i>size</i>:<i>abi</i>:<i>pref</i></tt></dt>
1140 <dd>This specifies the alignment for a vector type of a given bit
1142 <dt><tt>f<i>size</i>:<i>abi</i>:<i>pref</i></tt></dt>
1143 <dd>This specifies the alignment for a floating point type of a given bit
1144 <i>size</i>. The value of <i>size</i> must be either 32 (float) or 64
1146 <dt><tt>a<i>size</i>:<i>abi</i>:<i>pref</i></tt></dt>
1147 <dd>This specifies the alignment for an aggregate type of a given bit
1150 <p>When constructing the data layout for a given target, LLVM starts with a
1151 default set of specifications which are then (possibly) overriden by the
1152 specifications in the <tt>datalayout</tt> keyword. The default specifications
1153 are given in this list:</p>
1155 <li><tt>E</tt> - big endian</li>
1156 <li><tt>p:32:64:64</tt> - 32-bit pointers with 64-bit alignment</li>
1157 <li><tt>i1:8:8</tt> - i1 is 8-bit (byte) aligned</li>
1158 <li><tt>i8:8:8</tt> - i8 is 8-bit (byte) aligned</li>
1159 <li><tt>i16:16:16</tt> - i16 is 16-bit aligned</li>
1160 <li><tt>i32:32:32</tt> - i32 is 32-bit aligned</li>
1161 <li><tt>i64:32:64</tt> - i64 has ABI alignment of 32-bits but preferred
1162 alignment of 64-bits</li>
1163 <li><tt>f32:32:32</tt> - float is 32-bit aligned</li>
1164 <li><tt>f64:64:64</tt> - double is 64-bit aligned</li>
1165 <li><tt>v64:64:64</tt> - 64-bit vector is 64-bit aligned</li>
1166 <li><tt>v128:128:128</tt> - 128-bit vector is 128-bit aligned</li>
1167 <li><tt>a0:0:1</tt> - aggregates are 8-bit aligned</li>
1169 <p>When LLVM is determining the alignment for a given type, it uses the
1170 following rules:</p>
1172 <li>If the type sought is an exact match for one of the specifications, that
1173 specification is used.</li>
1174 <li>If no match is found, and the type sought is an integer type, then the
1175 smallest integer type that is larger than the bitwidth of the sought type is
1176 used. If none of the specifications are larger than the bitwidth then the the
1177 largest integer type is used. For example, given the default specifications
1178 above, the i7 type will use the alignment of i8 (next largest) while both
1179 i65 and i256 will use the alignment of i64 (largest specified).</li>
1180 <li>If no match is found, and the type sought is a vector type, then the
1181 largest vector type that is smaller than the sought vector type will be used
1182 as a fall back. This happens because <128 x double> can be implemented
1183 in terms of 64 <2 x double>, for example.</li>
1187 <!-- *********************************************************************** -->
1188 <div class="doc_section"> <a name="typesystem">Type System</a> </div>
1189 <!-- *********************************************************************** -->
1191 <div class="doc_text">
1193 <p>The LLVM type system is one of the most important features of the
1194 intermediate representation. Being typed enables a number of
1195 optimizations to be performed on the intermediate representation directly,
1196 without having to do
1197 extra analyses on the side before the transformation. A strong type
1198 system makes it easier to read the generated code and enables novel
1199 analyses and transformations that are not feasible to perform on normal
1200 three address code representations.</p>
1204 <!-- ======================================================================= -->
1205 <div class="doc_subsection"> <a name="t_classifications">Type
1206 Classifications</a> </div>
1207 <div class="doc_text">
1208 <p>The types fall into a few useful
1209 classifications:</p>
1211 <table border="1" cellspacing="0" cellpadding="4">
1213 <tr><th>Classification</th><th>Types</th></tr>
1215 <td><a href="#t_integer">integer</a></td>
1216 <td><tt>i1, i2, i3, ... i8, ... i16, ... i32, ... i64, ... </tt></td>
1219 <td><a href="#t_floating">floating point</a></td>
1220 <td><tt>float, double, x86_fp80, fp128, ppc_fp128</tt></td>
1223 <td><a name="t_firstclass">first class</a></td>
1224 <td><a href="#t_integer">integer</a>,
1225 <a href="#t_floating">floating point</a>,
1226 <a href="#t_pointer">pointer</a>,
1227 <a href="#t_vector">vector</a>,
1228 <a href="#t_struct">structure</a>,
1229 <a href="#t_array">array</a>,
1230 <a href="#t_label">label</a>.
1234 <td><a href="#t_primitive">primitive</a></td>
1235 <td><a href="#t_label">label</a>,
1236 <a href="#t_void">void</a>,
1237 <a href="#t_floating">floating point</a>.</td>
1240 <td><a href="#t_derived">derived</a></td>
1241 <td><a href="#t_integer">integer</a>,
1242 <a href="#t_array">array</a>,
1243 <a href="#t_function">function</a>,
1244 <a href="#t_pointer">pointer</a>,
1245 <a href="#t_struct">structure</a>,
1246 <a href="#t_pstruct">packed structure</a>,
1247 <a href="#t_vector">vector</a>,
1248 <a href="#t_opaque">opaque</a>.
1254 <p>The <a href="#t_firstclass">first class</a> types are perhaps the
1255 most important. Values of these types are the only ones which can be
1256 produced by instructions, passed as arguments, or used as operands to
1260 <!-- ======================================================================= -->
1261 <div class="doc_subsection"> <a name="t_primitive">Primitive Types</a> </div>
1263 <div class="doc_text">
1264 <p>The primitive types are the fundamental building blocks of the LLVM
1269 <!-- _______________________________________________________________________ -->
1270 <div class="doc_subsubsection"> <a name="t_floating">Floating Point Types</a> </div>
1272 <div class="doc_text">
1275 <tr><th>Type</th><th>Description</th></tr>
1276 <tr><td><tt>float</tt></td><td>32-bit floating point value</td></tr>
1277 <tr><td><tt>double</tt></td><td>64-bit floating point value</td></tr>
1278 <tr><td><tt>fp128</tt></td><td>128-bit floating point value (112-bit mantissa)</td></tr>
1279 <tr><td><tt>x86_fp80</tt></td><td>80-bit floating point value (X87)</td></tr>
1280 <tr><td><tt>ppc_fp128</tt></td><td>128-bit floating point value (two 64-bits)</td></tr>
1285 <!-- _______________________________________________________________________ -->
1286 <div class="doc_subsubsection"> <a name="t_void">Void Type</a> </div>
1288 <div class="doc_text">
1290 <p>The void type does not represent any value and has no size.</p>
1299 <!-- _______________________________________________________________________ -->
1300 <div class="doc_subsubsection"> <a name="t_label">Label Type</a> </div>
1302 <div class="doc_text">
1304 <p>The label type represents code labels.</p>
1314 <!-- ======================================================================= -->
1315 <div class="doc_subsection"> <a name="t_derived">Derived Types</a> </div>
1317 <div class="doc_text">
1319 <p>The real power in LLVM comes from the derived types in the system.
1320 This is what allows a programmer to represent arrays, functions,
1321 pointers, and other useful types. Note that these derived types may be
1322 recursive: For example, it is possible to have a two dimensional array.</p>
1326 <!-- _______________________________________________________________________ -->
1327 <div class="doc_subsubsection"> <a name="t_integer">Integer Type</a> </div>
1329 <div class="doc_text">
1332 <p>The integer type is a very simple derived type that simply specifies an
1333 arbitrary bit width for the integer type desired. Any bit width from 1 bit to
1334 2^23-1 (about 8 million) can be specified.</p>
1342 <p>The number of bits the integer will occupy is specified by the <tt>N</tt>
1346 <table class="layout">
1349 <td><tt>i1</tt></td>
1350 <td>a single-bit integer.</td>
1352 <td><tt>i32</tt></td>
1353 <td>a 32-bit integer.</td>
1355 <td><tt>i1942652</tt></td>
1356 <td>a really big integer of over 1 million bits.</td>
1361 <p>Note that the code generator does not yet support large integer types
1362 to be used as function return types. The specific limit on how large a
1363 return type the code generator can currently handle is target-dependent;
1364 currently it's often 64 bits for 32-bit targets and 128 bits for 64-bit
1369 <!-- _______________________________________________________________________ -->
1370 <div class="doc_subsubsection"> <a name="t_array">Array Type</a> </div>
1372 <div class="doc_text">
1376 <p>The array type is a very simple derived type that arranges elements
1377 sequentially in memory. The array type requires a size (number of
1378 elements) and an underlying data type.</p>
1383 [<# elements> x <elementtype>]
1386 <p>The number of elements is a constant integer value; elementtype may
1387 be any type with a size.</p>
1390 <table class="layout">
1392 <td class="left"><tt>[40 x i32]</tt></td>
1393 <td class="left">Array of 40 32-bit integer values.</td>
1396 <td class="left"><tt>[41 x i32]</tt></td>
1397 <td class="left">Array of 41 32-bit integer values.</td>
1400 <td class="left"><tt>[4 x i8]</tt></td>
1401 <td class="left">Array of 4 8-bit integer values.</td>
1404 <p>Here are some examples of multidimensional arrays:</p>
1405 <table class="layout">
1407 <td class="left"><tt>[3 x [4 x i32]]</tt></td>
1408 <td class="left">3x4 array of 32-bit integer values.</td>
1411 <td class="left"><tt>[12 x [10 x float]]</tt></td>
1412 <td class="left">12x10 array of single precision floating point values.</td>
1415 <td class="left"><tt>[2 x [3 x [4 x i16]]]</tt></td>
1416 <td class="left">2x3x4 array of 16-bit integer values.</td>
1420 <p>Note that 'variable sized arrays' can be implemented in LLVM with a zero
1421 length array. Normally, accesses past the end of an array are undefined in
1422 LLVM (e.g. it is illegal to access the 5th element of a 3 element array).
1423 As a special case, however, zero length arrays are recognized to be variable
1424 length. This allows implementation of 'pascal style arrays' with the LLVM
1425 type "{ i32, [0 x float]}", for example.</p>
1427 <p>Note that the code generator does not yet support large aggregate types
1428 to be used as function return types. The specific limit on how large an
1429 aggregate return type the code generator can currently handle is
1430 target-dependent, and also dependent on the aggregate element types.</p>
1434 <!-- _______________________________________________________________________ -->
1435 <div class="doc_subsubsection"> <a name="t_function">Function Type</a> </div>
1436 <div class="doc_text">
1440 <p>The function type can be thought of as a function signature. It
1441 consists of a return type and a list of formal parameter types. The
1442 return type of a function type is a scalar type, a void type, or a struct type.
1443 If the return type is a struct type then all struct elements must be of first
1444 class types, and the struct must have at least one element.</p>
1449 <returntype list> (<parameter list>)
1452 <p>...where '<tt><parameter list></tt>' is a comma-separated list of type
1453 specifiers. Optionally, the parameter list may include a type <tt>...</tt>,
1454 which indicates that the function takes a variable number of arguments.
1455 Variable argument functions can access their arguments with the <a
1456 href="#int_varargs">variable argument handling intrinsic</a> functions.
1457 '<tt><returntype list></tt>' is a comma-separated list of
1458 <a href="#t_firstclass">first class</a> type specifiers.</p>
1461 <table class="layout">
1463 <td class="left"><tt>i32 (i32)</tt></td>
1464 <td class="left">function taking an <tt>i32</tt>, returning an <tt>i32</tt>
1466 </tr><tr class="layout">
1467 <td class="left"><tt>float (i16 signext, i32 *) *
1469 <td class="left"><a href="#t_pointer">Pointer</a> to a function that takes
1470 an <tt>i16</tt> that should be sign extended and a
1471 <a href="#t_pointer">pointer</a> to <tt>i32</tt>, returning
1474 </tr><tr class="layout">
1475 <td class="left"><tt>i32 (i8*, ...)</tt></td>
1476 <td class="left">A vararg function that takes at least one
1477 <a href="#t_pointer">pointer</a> to <tt>i8 </tt> (char in C),
1478 which returns an integer. This is the signature for <tt>printf</tt> in
1481 </tr><tr class="layout">
1482 <td class="left"><tt>{i32, i32} (i32)</tt></td>
1483 <td class="left">A function taking an <tt>i32</tt>, returning two
1484 <tt>i32</tt> values as an aggregate of type <tt>{ i32, i32 }</tt>
1490 <!-- _______________________________________________________________________ -->
1491 <div class="doc_subsubsection"> <a name="t_struct">Structure Type</a> </div>
1492 <div class="doc_text">
1494 <p>The structure type is used to represent a collection of data members
1495 together in memory. The packing of the field types is defined to match
1496 the ABI of the underlying processor. The elements of a structure may
1497 be any type that has a size.</p>
1498 <p>Structures are accessed using '<tt><a href="#i_load">load</a></tt>
1499 and '<tt><a href="#i_store">store</a></tt>' by getting a pointer to a
1500 field with the '<tt><a href="#i_getelementptr">getelementptr</a></tt>'
1503 <pre> { <type list> }<br></pre>
1505 <table class="layout">
1507 <td class="left"><tt>{ i32, i32, i32 }</tt></td>
1508 <td class="left">A triple of three <tt>i32</tt> values</td>
1509 </tr><tr class="layout">
1510 <td class="left"><tt>{ float, i32 (i32) * }</tt></td>
1511 <td class="left">A pair, where the first element is a <tt>float</tt> and the
1512 second element is a <a href="#t_pointer">pointer</a> to a
1513 <a href="#t_function">function</a> that takes an <tt>i32</tt>, returning
1514 an <tt>i32</tt>.</td>
1518 <p>Note that the code generator does not yet support large aggregate types
1519 to be used as function return types. The specific limit on how large an
1520 aggregate return type the code generator can currently handle is
1521 target-dependent, and also dependent on the aggregate element types.</p>
1525 <!-- _______________________________________________________________________ -->
1526 <div class="doc_subsubsection"> <a name="t_pstruct">Packed Structure Type</a>
1528 <div class="doc_text">
1530 <p>The packed structure type is used to represent a collection of data members
1531 together in memory. There is no padding between fields. Further, the alignment
1532 of a packed structure is 1 byte. The elements of a packed structure may
1533 be any type that has a size.</p>
1534 <p>Structures are accessed using '<tt><a href="#i_load">load</a></tt>
1535 and '<tt><a href="#i_store">store</a></tt>' by getting a pointer to a
1536 field with the '<tt><a href="#i_getelementptr">getelementptr</a></tt>'
1539 <pre> < { <type list> } > <br></pre>
1541 <table class="layout">
1543 <td class="left"><tt>< { i32, i32, i32 } ></tt></td>
1544 <td class="left">A triple of three <tt>i32</tt> values</td>
1545 </tr><tr class="layout">
1547 <tt>< { float, i32 (i32)* } ></tt></td>
1548 <td class="left">A pair, where the first element is a <tt>float</tt> and the
1549 second element is a <a href="#t_pointer">pointer</a> to a
1550 <a href="#t_function">function</a> that takes an <tt>i32</tt>, returning
1551 an <tt>i32</tt>.</td>
1556 <!-- _______________________________________________________________________ -->
1557 <div class="doc_subsubsection"> <a name="t_pointer">Pointer Type</a> </div>
1558 <div class="doc_text">
1560 <p>As in many languages, the pointer type represents a pointer or
1561 reference to another object, which must live in memory. Pointer types may have
1562 an optional address space attribute defining the target-specific numbered
1563 address space where the pointed-to object resides. The default address space is
1566 <p>Note that LLVM does not permit pointers to void (<tt>void*</tt>) nor does
1567 it permit pointers to labels (<tt>label*</tt>). Use <tt>i8*</tt> instead.</p>
1570 <pre> <type> *<br></pre>
1572 <table class="layout">
1574 <td class="left"><tt>[4 x i32]*</tt></td>
1575 <td class="left">A <a href="#t_pointer">pointer</a> to <a
1576 href="#t_array">array</a> of four <tt>i32</tt> values.</td>
1579 <td class="left"><tt>i32 (i32 *) *</tt></td>
1580 <td class="left"> A <a href="#t_pointer">pointer</a> to a <a
1581 href="#t_function">function</a> that takes an <tt>i32*</tt>, returning an
1585 <td class="left"><tt>i32 addrspace(5)*</tt></td>
1586 <td class="left">A <a href="#t_pointer">pointer</a> to an <tt>i32</tt> value
1587 that resides in address space #5.</td>
1592 <!-- _______________________________________________________________________ -->
1593 <div class="doc_subsubsection"> <a name="t_vector">Vector Type</a> </div>
1594 <div class="doc_text">
1598 <p>A vector type is a simple derived type that represents a vector
1599 of elements. Vector types are used when multiple primitive data
1600 are operated in parallel using a single instruction (SIMD).
1601 A vector type requires a size (number of
1602 elements) and an underlying primitive data type. Vectors must have a power
1603 of two length (1, 2, 4, 8, 16 ...). Vector types are
1604 considered <a href="#t_firstclass">first class</a>.</p>
1609 < <# elements> x <elementtype> >
1612 <p>The number of elements is a constant integer value; elementtype may
1613 be any integer or floating point type.</p>
1617 <table class="layout">
1619 <td class="left"><tt><4 x i32></tt></td>
1620 <td class="left">Vector of 4 32-bit integer values.</td>
1623 <td class="left"><tt><8 x float></tt></td>
1624 <td class="left">Vector of 8 32-bit floating-point values.</td>
1627 <td class="left"><tt><2 x i64></tt></td>
1628 <td class="left">Vector of 2 64-bit integer values.</td>
1632 <p>Note that the code generator does not yet support large vector types
1633 to be used as function return types. The specific limit on how large a
1634 vector return type codegen can currently handle is target-dependent;
1635 currently it's often a few times longer than a hardware vector register.</p>
1639 <!-- _______________________________________________________________________ -->
1640 <div class="doc_subsubsection"> <a name="t_opaque">Opaque Type</a> </div>
1641 <div class="doc_text">
1645 <p>Opaque types are used to represent unknown types in the system. This
1646 corresponds (for example) to the C notion of a forward declared structure type.
1647 In LLVM, opaque types can eventually be resolved to any type (not just a
1648 structure type).</p>
1658 <table class="layout">
1660 <td class="left"><tt>opaque</tt></td>
1661 <td class="left">An opaque type.</td>
1666 <!-- ======================================================================= -->
1667 <div class="doc_subsection">
1668 <a name="t_uprefs">Type Up-references</a>
1671 <div class="doc_text">
1674 An "up reference" allows you to refer to a lexically enclosing type without
1675 requiring it to have a name. For instance, a structure declaration may contain a
1676 pointer to any of the types it is lexically a member of. Example of up
1677 references (with their equivalent as named type declarations) include:</p>
1680 { \2 * } %x = type { %x* }
1681 { \2 }* %y = type { %y }*
1686 An up reference is needed by the asmprinter for printing out cyclic types when
1687 there is no declared name for a type in the cycle. Because the asmprinter does
1688 not want to print out an infinite type string, it needs a syntax to handle
1689 recursive types that have no names (all names are optional in llvm IR).
1698 The level is the count of the lexical type that is being referred to.
1703 <table class="layout">
1705 <td class="left"><tt>\1*</tt></td>
1706 <td class="left">Self-referential pointer.</td>
1709 <td class="left"><tt>{ { \3*, i8 }, i32 }</tt></td>
1710 <td class="left">Recursive structure where the upref refers to the out-most
1717 <!-- *********************************************************************** -->
1718 <div class="doc_section"> <a name="constants">Constants</a> </div>
1719 <!-- *********************************************************************** -->
1721 <div class="doc_text">
1723 <p>LLVM has several different basic types of constants. This section describes
1724 them all and their syntax.</p>
1728 <!-- ======================================================================= -->
1729 <div class="doc_subsection"><a name="simpleconstants">Simple Constants</a></div>
1731 <div class="doc_text">
1734 <dt><b>Boolean constants</b></dt>
1736 <dd>The two strings '<tt>true</tt>' and '<tt>false</tt>' are both valid
1737 constants of the <tt><a href="#t_primitive">i1</a></tt> type.
1740 <dt><b>Integer constants</b></dt>
1742 <dd>Standard integers (such as '4') are constants of the <a
1743 href="#t_integer">integer</a> type. Negative numbers may be used with
1747 <dt><b>Floating point constants</b></dt>
1749 <dd>Floating point constants use standard decimal notation (e.g. 123.421),
1750 exponential notation (e.g. 1.23421e+2), or a more precise hexadecimal
1751 notation (see below). The assembler requires the exact decimal value of
1752 a floating-point constant. For example, the assembler accepts 1.25 but
1753 rejects 1.3 because 1.3 is a repeating decimal in binary. Floating point
1754 constants must have a <a href="#t_floating">floating point</a> type. </dd>
1756 <dt><b>Null pointer constants</b></dt>
1758 <dd>The identifier '<tt>null</tt>' is recognized as a null pointer constant
1759 and must be of <a href="#t_pointer">pointer type</a>.</dd>
1763 <p>The one non-intuitive notation for constants is the hexadecimal form
1764 of floating point constants. For example, the form '<tt>double
1765 0x432ff973cafa8000</tt>' is equivalent to (but harder to read than) '<tt>double
1766 4.5e+15</tt>'. The only time hexadecimal floating point constants are required
1767 (and the only time that they are generated by the disassembler) is when a
1768 floating point constant must be emitted but it cannot be represented as a
1769 decimal floating point number in a reasonable number of digits. For example,
1770 NaN's, infinities, and other
1771 special values are represented in their IEEE hexadecimal format so that
1772 assembly and disassembly do not cause any bits to change in the constants.</p>
1773 <p>When using the hexadecimal form, constants of types float and double are
1774 represented using the 16-digit form shown above (which matches the IEEE754
1775 representation for double); float values must, however, be exactly representable
1776 as IEE754 single precision.
1777 Hexadecimal format is always used for long
1778 double, and there are three forms of long double. The 80-bit
1779 format used by x86 is represented as <tt>0xK</tt>
1780 followed by 20 hexadecimal digits.
1781 The 128-bit format used by PowerPC (two adjacent doubles) is represented
1782 by <tt>0xM</tt> followed by 32 hexadecimal digits. The IEEE 128-bit
1783 format is represented
1784 by <tt>0xL</tt> followed by 32 hexadecimal digits; no currently supported
1785 target uses this format. Long doubles will only work if they match
1786 the long double format on your target. All hexadecimal formats are big-endian
1787 (sign bit at the left).</p>
1790 <!-- ======================================================================= -->
1791 <div class="doc_subsection"><a name="aggregateconstants">Aggregate Constants</a>
1794 <div class="doc_text">
1795 <p>Aggregate constants arise from aggregation of simple constants
1796 and smaller aggregate constants.</p>
1799 <dt><b>Structure constants</b></dt>
1801 <dd>Structure constants are represented with notation similar to structure
1802 type definitions (a comma separated list of elements, surrounded by braces
1803 (<tt>{}</tt>)). For example: "<tt>{ i32 4, float 17.0, i32* @G }</tt>",
1804 where "<tt>@G</tt>" is declared as "<tt>@G = external global i32</tt>". Structure constants
1805 must have <a href="#t_struct">structure type</a>, and the number and
1806 types of elements must match those specified by the type.
1809 <dt><b>Array constants</b></dt>
1811 <dd>Array constants are represented with notation similar to array type
1812 definitions (a comma separated list of elements, surrounded by square brackets
1813 (<tt>[]</tt>)). For example: "<tt>[ i32 42, i32 11, i32 74 ]</tt>". Array
1814 constants must have <a href="#t_array">array type</a>, and the number and
1815 types of elements must match those specified by the type.
1818 <dt><b>Vector constants</b></dt>
1820 <dd>Vector constants are represented with notation similar to vector type
1821 definitions (a comma separated list of elements, surrounded by
1822 less-than/greater-than's (<tt><></tt>)). For example: "<tt>< i32 42,
1823 i32 11, i32 74, i32 100 ></tt>". Vector constants must have <a
1824 href="#t_vector">vector type</a>, and the number and types of elements must
1825 match those specified by the type.
1828 <dt><b>Zero initialization</b></dt>
1830 <dd>The string '<tt>zeroinitializer</tt>' can be used to zero initialize a
1831 value to zero of <em>any</em> type, including scalar and aggregate types.
1832 This is often used to avoid having to print large zero initializers (e.g. for
1833 large arrays) and is always exactly equivalent to using explicit zero
1840 <!-- ======================================================================= -->
1841 <div class="doc_subsection">
1842 <a name="globalconstants">Global Variable and Function Addresses</a>
1845 <div class="doc_text">
1847 <p>The addresses of <a href="#globalvars">global variables</a> and <a
1848 href="#functionstructure">functions</a> are always implicitly valid (link-time)
1849 constants. These constants are explicitly referenced when the <a
1850 href="#identifiers">identifier for the global</a> is used and always have <a
1851 href="#t_pointer">pointer</a> type. For example, the following is a legal LLVM
1854 <div class="doc_code">
1858 @Z = global [2 x i32*] [ i32* @X, i32* @Y ]
1864 <!-- ======================================================================= -->
1865 <div class="doc_subsection"><a name="undefvalues">Undefined Values</a></div>
1866 <div class="doc_text">
1867 <p>The string '<tt>undef</tt>' is recognized as a type-less constant that has
1868 no specific value. Undefined values may be of any type and be used anywhere
1869 a constant is permitted.</p>
1871 <p>Undefined values indicate to the compiler that the program is well defined
1872 no matter what value is used, giving the compiler more freedom to optimize.
1876 <!-- ======================================================================= -->
1877 <div class="doc_subsection"><a name="constantexprs">Constant Expressions</a>
1880 <div class="doc_text">
1882 <p>Constant expressions are used to allow expressions involving other constants
1883 to be used as constants. Constant expressions may be of any <a
1884 href="#t_firstclass">first class</a> type and may involve any LLVM operation
1885 that does not have side effects (e.g. load and call are not supported). The
1886 following is the syntax for constant expressions:</p>
1889 <dt><b><tt>trunc ( CST to TYPE )</tt></b></dt>
1890 <dd>Truncate a constant to another type. The bit size of CST must be larger
1891 than the bit size of TYPE. Both types must be integers.</dd>
1893 <dt><b><tt>zext ( CST to TYPE )</tt></b></dt>
1894 <dd>Zero extend a constant to another type. The bit size of CST must be
1895 smaller or equal to the bit size of TYPE. Both types must be integers.</dd>
1897 <dt><b><tt>sext ( CST to TYPE )</tt></b></dt>
1898 <dd>Sign extend a constant to another type. The bit size of CST must be
1899 smaller or equal to the bit size of TYPE. Both types must be integers.</dd>
1901 <dt><b><tt>fptrunc ( CST to TYPE )</tt></b></dt>
1902 <dd>Truncate a floating point constant to another floating point type. The
1903 size of CST must be larger than the size of TYPE. Both types must be
1904 floating point.</dd>
1906 <dt><b><tt>fpext ( CST to TYPE )</tt></b></dt>
1907 <dd>Floating point extend a constant to another type. The size of CST must be
1908 smaller or equal to the size of TYPE. Both types must be floating point.</dd>
1910 <dt><b><tt>fptoui ( CST to TYPE )</tt></b></dt>
1911 <dd>Convert a floating point constant to the corresponding unsigned integer
1912 constant. TYPE must be a scalar or vector integer type. CST must be of scalar
1913 or vector floating point type. Both CST and TYPE must be scalars, or vectors
1914 of the same number of elements. If the value won't fit in the integer type,
1915 the results are undefined.</dd>
1917 <dt><b><tt>fptosi ( CST to TYPE )</tt></b></dt>
1918 <dd>Convert a floating point constant to the corresponding signed integer
1919 constant. TYPE must be a scalar or vector integer type. CST must be of scalar
1920 or vector floating point type. Both CST and TYPE must be scalars, or vectors
1921 of the same number of elements. If the value won't fit in the integer type,
1922 the results are undefined.</dd>
1924 <dt><b><tt>uitofp ( CST to TYPE )</tt></b></dt>
1925 <dd>Convert an unsigned integer constant to the corresponding floating point
1926 constant. TYPE must be a scalar or vector floating point type. CST must be of
1927 scalar or vector integer type. Both CST and TYPE must be scalars, or vectors
1928 of the same number of elements. If the value won't fit in the floating point
1929 type, the results are undefined.</dd>
1931 <dt><b><tt>sitofp ( CST to TYPE )</tt></b></dt>
1932 <dd>Convert a signed integer constant to the corresponding floating point
1933 constant. TYPE must be a scalar or vector floating point type. CST must be of
1934 scalar or vector integer type. Both CST and TYPE must be scalars, or vectors
1935 of the same number of elements. If the value won't fit in the floating point
1936 type, the results are undefined.</dd>
1938 <dt><b><tt>ptrtoint ( CST to TYPE )</tt></b></dt>
1939 <dd>Convert a pointer typed constant to the corresponding integer constant
1940 TYPE must be an integer type. CST must be of pointer type. The CST value is
1941 zero extended, truncated, or unchanged to make it fit in TYPE.</dd>
1943 <dt><b><tt>inttoptr ( CST to TYPE )</tt></b></dt>
1944 <dd>Convert a integer constant to a pointer constant. TYPE must be a
1945 pointer type. CST must be of integer type. The CST value is zero extended,
1946 truncated, or unchanged to make it fit in a pointer size. This one is
1947 <i>really</i> dangerous!</dd>
1949 <dt><b><tt>bitcast ( CST to TYPE )</tt></b></dt>
1950 <dd>Convert a constant, CST, to another TYPE. The size of CST and TYPE must be
1951 identical (same number of bits). The conversion is done as if the CST value
1952 was stored to memory and read back as TYPE. In other words, no bits change
1953 with this operator, just the type. This can be used for conversion of
1954 vector types to any other type, as long as they have the same bit width. For
1955 pointers it is only valid to cast to another pointer type. It is not valid
1956 to bitcast to or from an aggregate type.
1959 <dt><b><tt>getelementptr ( CSTPTR, IDX0, IDX1, ... )</tt></b></dt>
1961 <dd>Perform the <a href="#i_getelementptr">getelementptr operation</a> on
1962 constants. As with the <a href="#i_getelementptr">getelementptr</a>
1963 instruction, the index list may have zero or more indexes, which are required
1964 to make sense for the type of "CSTPTR".</dd>
1966 <dt><b><tt>select ( COND, VAL1, VAL2 )</tt></b></dt>
1968 <dd>Perform the <a href="#i_select">select operation</a> on
1971 <dt><b><tt>icmp COND ( VAL1, VAL2 )</tt></b></dt>
1972 <dd>Performs the <a href="#i_icmp">icmp operation</a> on constants.</dd>
1974 <dt><b><tt>fcmp COND ( VAL1, VAL2 )</tt></b></dt>
1975 <dd>Performs the <a href="#i_fcmp">fcmp operation</a> on constants.</dd>
1977 <dt><b><tt>vicmp COND ( VAL1, VAL2 )</tt></b></dt>
1978 <dd>Performs the <a href="#i_vicmp">vicmp operation</a> on constants.</dd>
1980 <dt><b><tt>vfcmp COND ( VAL1, VAL2 )</tt></b></dt>
1981 <dd>Performs the <a href="#i_vfcmp">vfcmp operation</a> on constants.</dd>
1983 <dt><b><tt>extractelement ( VAL, IDX )</tt></b></dt>
1985 <dd>Perform the <a href="#i_extractelement">extractelement
1986 operation</a> on constants.</dd>
1988 <dt><b><tt>insertelement ( VAL, ELT, IDX )</tt></b></dt>
1990 <dd>Perform the <a href="#i_insertelement">insertelement
1991 operation</a> on constants.</dd>
1994 <dt><b><tt>shufflevector ( VEC1, VEC2, IDXMASK )</tt></b></dt>
1996 <dd>Perform the <a href="#i_shufflevector">shufflevector
1997 operation</a> on constants.</dd>
1999 <dt><b><tt>OPCODE ( LHS, RHS )</tt></b></dt>
2001 <dd>Perform the specified operation of the LHS and RHS constants. OPCODE may
2002 be any of the <a href="#binaryops">binary</a> or <a href="#bitwiseops">bitwise
2003 binary</a> operations. The constraints on operands are the same as those for
2004 the corresponding instruction (e.g. no bitwise operations on floating point
2005 values are allowed).</dd>
2009 <!-- *********************************************************************** -->
2010 <div class="doc_section"> <a name="othervalues">Other Values</a> </div>
2011 <!-- *********************************************************************** -->
2013 <!-- ======================================================================= -->
2014 <div class="doc_subsection">
2015 <a name="inlineasm">Inline Assembler Expressions</a>
2018 <div class="doc_text">
2021 LLVM supports inline assembler expressions (as opposed to <a href="#moduleasm">
2022 Module-Level Inline Assembly</a>) through the use of a special value. This
2023 value represents the inline assembler as a string (containing the instructions
2024 to emit), a list of operand constraints (stored as a string), and a flag that
2025 indicates whether or not the inline asm expression has side effects. An example
2026 inline assembler expression is:
2029 <div class="doc_code">
2031 i32 (i32) asm "bswap $0", "=r,r"
2036 Inline assembler expressions may <b>only</b> be used as the callee operand of
2037 a <a href="#i_call"><tt>call</tt> instruction</a>. Thus, typically we have:
2040 <div class="doc_code">
2042 %X = call i32 asm "<a href="#int_bswap">bswap</a> $0", "=r,r"(i32 %Y)
2047 Inline asms with side effects not visible in the constraint list must be marked
2048 as having side effects. This is done through the use of the
2049 '<tt>sideeffect</tt>' keyword, like so:
2052 <div class="doc_code">
2054 call void asm sideeffect "eieio", ""()
2058 <p>TODO: The format of the asm and constraints string still need to be
2059 documented here. Constraints on what can be done (e.g. duplication, moving, etc
2060 need to be documented). This is probably best done by reference to another
2061 document that covers inline asm from a holistic perspective.
2066 <!-- *********************************************************************** -->
2067 <div class="doc_section"> <a name="instref">Instruction Reference</a> </div>
2068 <!-- *********************************************************************** -->
2070 <div class="doc_text">
2072 <p>The LLVM instruction set consists of several different
2073 classifications of instructions: <a href="#terminators">terminator
2074 instructions</a>, <a href="#binaryops">binary instructions</a>,
2075 <a href="#bitwiseops">bitwise binary instructions</a>, <a
2076 href="#memoryops">memory instructions</a>, and <a href="#otherops">other
2077 instructions</a>.</p>
2081 <!-- ======================================================================= -->
2082 <div class="doc_subsection"> <a name="terminators">Terminator
2083 Instructions</a> </div>
2085 <div class="doc_text">
2087 <p>As mentioned <a href="#functionstructure">previously</a>, every
2088 basic block in a program ends with a "Terminator" instruction, which
2089 indicates which block should be executed after the current block is
2090 finished. These terminator instructions typically yield a '<tt>void</tt>'
2091 value: they produce control flow, not values (the one exception being
2092 the '<a href="#i_invoke"><tt>invoke</tt></a>' instruction).</p>
2093 <p>There are six different terminator instructions: the '<a
2094 href="#i_ret"><tt>ret</tt></a>' instruction, the '<a href="#i_br"><tt>br</tt></a>'
2095 instruction, the '<a href="#i_switch"><tt>switch</tt></a>' instruction,
2096 the '<a href="#i_invoke"><tt>invoke</tt></a>' instruction, the '<a
2097 href="#i_unwind"><tt>unwind</tt></a>' instruction, and the '<a
2098 href="#i_unreachable"><tt>unreachable</tt></a>' instruction.</p>
2102 <!-- _______________________________________________________________________ -->
2103 <div class="doc_subsubsection"> <a name="i_ret">'<tt>ret</tt>'
2104 Instruction</a> </div>
2105 <div class="doc_text">
2108 ret <type> <value> <i>; Return a value from a non-void function</i>
2109 ret void <i>; Return from void function</i>
2114 <p>The '<tt>ret</tt>' instruction is used to return control flow (and
2115 optionally a value) from a function back to the caller.</p>
2116 <p>There are two forms of the '<tt>ret</tt>' instruction: one that
2117 returns a value and then causes control flow, and one that just causes
2118 control flow to occur.</p>
2122 <p>The '<tt>ret</tt>' instruction optionally accepts a single argument,
2123 the return value. The type of the return value must be a
2124 '<a href="#t_firstclass">first class</a>' type.</p>
2126 <p>A function is not <a href="#wellformed">well formed</a> if
2127 it it has a non-void return type and contains a '<tt>ret</tt>'
2128 instruction with no return value or a return value with a type that
2129 does not match its type, or if it has a void return type and contains
2130 a '<tt>ret</tt>' instruction with a return value.</p>
2134 <p>When the '<tt>ret</tt>' instruction is executed, control flow
2135 returns back to the calling function's context. If the caller is a "<a
2136 href="#i_call"><tt>call</tt></a>" instruction, execution continues at
2137 the instruction after the call. If the caller was an "<a
2138 href="#i_invoke"><tt>invoke</tt></a>" instruction, execution continues
2139 at the beginning of the "normal" destination block. If the instruction
2140 returns a value, that value shall set the call or invoke instruction's
2146 ret i32 5 <i>; Return an integer value of 5</i>
2147 ret void <i>; Return from a void function</i>
2148 ret { i32, i8 } { i32 4, i8 2 } <i>; Return an aggregate of values 4 and 2</i>
2151 <p>Note that the code generator does not yet fully support large
2152 return values. The specific sizes that are currently supported are
2153 dependent on the target. For integers, on 32-bit targets the limit
2154 is often 64 bits, and on 64-bit targets the limit is often 128 bits.
2155 For aggregate types, the current limits are dependent on the element
2156 types; for example targets are often limited to 2 total integer
2157 elements and 2 total floating-point elements.</p>
2160 <!-- _______________________________________________________________________ -->
2161 <div class="doc_subsubsection"> <a name="i_br">'<tt>br</tt>' Instruction</a> </div>
2162 <div class="doc_text">
2164 <pre> br i1 <cond>, label <iftrue>, label <iffalse><br> br label <dest> <i>; Unconditional branch</i>
2167 <p>The '<tt>br</tt>' instruction is used to cause control flow to
2168 transfer to a different basic block in the current function. There are
2169 two forms of this instruction, corresponding to a conditional branch
2170 and an unconditional branch.</p>
2172 <p>The conditional branch form of the '<tt>br</tt>' instruction takes a
2173 single '<tt>i1</tt>' value and two '<tt>label</tt>' values. The
2174 unconditional form of the '<tt>br</tt>' instruction takes a single
2175 '<tt>label</tt>' value as a target.</p>
2177 <p>Upon execution of a conditional '<tt>br</tt>' instruction, the '<tt>i1</tt>'
2178 argument is evaluated. If the value is <tt>true</tt>, control flows
2179 to the '<tt>iftrue</tt>' <tt>label</tt> argument. If "cond" is <tt>false</tt>,
2180 control flows to the '<tt>iffalse</tt>' <tt>label</tt> argument.</p>
2182 <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
2183 href="#i_ret">ret</a> i32 1<br>IfUnequal:<br> <a href="#i_ret">ret</a> i32 0<br></pre>
2185 <!-- _______________________________________________________________________ -->
2186 <div class="doc_subsubsection">
2187 <a name="i_switch">'<tt>switch</tt>' Instruction</a>
2190 <div class="doc_text">
2194 switch <intty> <value>, label <defaultdest> [ <intty> <val>, label <dest> ... ]
2199 <p>The '<tt>switch</tt>' instruction is used to transfer control flow to one of
2200 several different places. It is a generalization of the '<tt>br</tt>'
2201 instruction, allowing a branch to occur to one of many possible
2207 <p>The '<tt>switch</tt>' instruction uses three parameters: an integer
2208 comparison value '<tt>value</tt>', a default '<tt>label</tt>' destination, and
2209 an array of pairs of comparison value constants and '<tt>label</tt>'s. The
2210 table is not allowed to contain duplicate constant entries.</p>
2214 <p>The <tt>switch</tt> instruction specifies a table of values and
2215 destinations. When the '<tt>switch</tt>' instruction is executed, this
2216 table is searched for the given value. If the value is found, control flow is
2217 transfered to the corresponding destination; otherwise, control flow is
2218 transfered to the default destination.</p>
2220 <h5>Implementation:</h5>
2222 <p>Depending on properties of the target machine and the particular
2223 <tt>switch</tt> instruction, this instruction may be code generated in different
2224 ways. For example, it could be generated as a series of chained conditional
2225 branches or with a lookup table.</p>
2230 <i>; Emulate a conditional br instruction</i>
2231 %Val = <a href="#i_zext">zext</a> i1 %value to i32
2232 switch i32 %Val, label %truedest [ i32 0, label %falsedest ]
2234 <i>; Emulate an unconditional br instruction</i>
2235 switch i32 0, label %dest [ ]
2237 <i>; Implement a jump table:</i>
2238 switch i32 %val, label %otherwise [ i32 0, label %onzero
2240 i32 2, label %ontwo ]
2244 <!-- _______________________________________________________________________ -->
2245 <div class="doc_subsubsection">
2246 <a name="i_invoke">'<tt>invoke</tt>' Instruction</a>
2249 <div class="doc_text">
2254 <result> = invoke [<a href="#callingconv">cconv</a>] [<a href="#paramattrs">ret attrs</a>] <ptr to function ty> <function ptr val>(<function args>) [<a href="#fnattrs">fn attrs</a>]
2255 to label <normal label> unwind label <exception label>
2260 <p>The '<tt>invoke</tt>' instruction causes control to transfer to a specified
2261 function, with the possibility of control flow transfer to either the
2262 '<tt>normal</tt>' label or the
2263 '<tt>exception</tt>' label. If the callee function returns with the
2264 "<tt><a href="#i_ret">ret</a></tt>" instruction, control flow will return to the
2265 "normal" label. If the callee (or any indirect callees) returns with the "<a
2266 href="#i_unwind"><tt>unwind</tt></a>" instruction, control is interrupted and
2267 continued at the dynamically nearest "exception" label.</p>
2271 <p>This instruction requires several arguments:</p>
2275 The optional "cconv" marker indicates which <a href="#callingconv">calling
2276 convention</a> the call should use. If none is specified, the call defaults
2277 to using C calling conventions.
2280 <li>The optional <a href="#paramattrs">Parameter Attributes</a> list for
2281 return values. Only '<tt>zeroext</tt>', '<tt>signext</tt>',
2282 and '<tt>inreg</tt>' attributes are valid here.</li>
2284 <li>'<tt>ptr to function ty</tt>': shall be the signature of the pointer to
2285 function value being invoked. In most cases, this is a direct function
2286 invocation, but indirect <tt>invoke</tt>s are just as possible, branching off
2287 an arbitrary pointer to function value.
2290 <li>'<tt>function ptr val</tt>': An LLVM value containing a pointer to a
2291 function to be invoked. </li>
2293 <li>'<tt>function args</tt>': argument list whose types match the function
2294 signature argument types. If the function signature indicates the function
2295 accepts a variable number of arguments, the extra arguments can be
2298 <li>'<tt>normal label</tt>': the label reached when the called function
2299 executes a '<tt><a href="#i_ret">ret</a></tt>' instruction. </li>
2301 <li>'<tt>exception label</tt>': the label reached when a callee returns with
2302 the <a href="#i_unwind"><tt>unwind</tt></a> instruction. </li>
2304 <li>The optional <a href="#fnattrs">function attributes</a> list. Only
2305 '<tt>noreturn</tt>', '<tt>nounwind</tt>', '<tt>readonly</tt>' and
2306 '<tt>readnone</tt>' attributes are valid here.</li>
2311 <p>This instruction is designed to operate as a standard '<tt><a
2312 href="#i_call">call</a></tt>' instruction in most regards. The primary
2313 difference is that it establishes an association with a label, which is used by
2314 the runtime library to unwind the stack.</p>
2316 <p>This instruction is used in languages with destructors to ensure that proper
2317 cleanup is performed in the case of either a <tt>longjmp</tt> or a thrown
2318 exception. Additionally, this is important for implementation of
2319 '<tt>catch</tt>' clauses in high-level languages that support them.</p>
2323 %retval = invoke i32 @Test(i32 15) to label %Continue
2324 unwind label %TestCleanup <i>; {i32}:retval set</i>
2325 %retval = invoke <a href="#callingconv">coldcc</a> i32 %Testfnptr(i32 15) to label %Continue
2326 unwind label %TestCleanup <i>; {i32}:retval set</i>
2331 <!-- _______________________________________________________________________ -->
2333 <div class="doc_subsubsection"> <a name="i_unwind">'<tt>unwind</tt>'
2334 Instruction</a> </div>
2336 <div class="doc_text">
2345 <p>The '<tt>unwind</tt>' instruction unwinds the stack, continuing control flow
2346 at the first callee in the dynamic call stack which used an <a
2347 href="#i_invoke"><tt>invoke</tt></a> instruction to perform the call. This is
2348 primarily used to implement exception handling.</p>
2352 <p>The '<tt>unwind</tt>' instruction causes execution of the current function to
2353 immediately halt. The dynamic call stack is then searched for the first <a
2354 href="#i_invoke"><tt>invoke</tt></a> instruction on the call stack. Once found,
2355 execution continues at the "exceptional" destination block specified by the
2356 <tt>invoke</tt> instruction. If there is no <tt>invoke</tt> instruction in the
2357 dynamic call chain, undefined behavior results.</p>
2360 <!-- _______________________________________________________________________ -->
2362 <div class="doc_subsubsection"> <a name="i_unreachable">'<tt>unreachable</tt>'
2363 Instruction</a> </div>
2365 <div class="doc_text">
2374 <p>The '<tt>unreachable</tt>' instruction has no defined semantics. This
2375 instruction is used to inform the optimizer that a particular portion of the
2376 code is not reachable. This can be used to indicate that the code after a
2377 no-return function cannot be reached, and other facts.</p>
2381 <p>The '<tt>unreachable</tt>' instruction has no defined semantics.</p>
2386 <!-- ======================================================================= -->
2387 <div class="doc_subsection"> <a name="binaryops">Binary Operations</a> </div>
2388 <div class="doc_text">
2389 <p>Binary operators are used to do most of the computation in a
2390 program. They require two operands of the same type, execute an operation on them, and
2391 produce a single value. The operands might represent
2392 multiple data, as is the case with the <a href="#t_vector">vector</a> data type.
2393 The result value has the same type as its operands.</p>
2394 <p>There are several different binary operators:</p>
2396 <!-- _______________________________________________________________________ -->
2397 <div class="doc_subsubsection">
2398 <a name="i_add">'<tt>add</tt>' Instruction</a>
2401 <div class="doc_text">
2406 <result> = add <ty> <op1>, <op2> <i>; yields {ty}:result</i>
2411 <p>The '<tt>add</tt>' instruction returns the sum of its two operands.</p>
2415 <p>The two arguments to the '<tt>add</tt>' instruction must be <a
2416 href="#t_integer">integer</a>, <a href="#t_floating">floating point</a>, or
2417 <a href="#t_vector">vector</a> values. Both arguments must have identical
2422 <p>The value produced is the integer or floating point sum of the two
2425 <p>If an integer sum has unsigned overflow, the result returned is the
2426 mathematical result modulo 2<sup>n</sup>, where n is the bit width of
2429 <p>Because LLVM integers use a two's complement representation, this
2430 instruction is appropriate for both signed and unsigned integers.</p>
2435 <result> = add i32 4, %var <i>; yields {i32}:result = 4 + %var</i>
2438 <!-- _______________________________________________________________________ -->
2439 <div class="doc_subsubsection">
2440 <a name="i_sub">'<tt>sub</tt>' Instruction</a>
2443 <div class="doc_text">
2448 <result> = sub <ty> <op1>, <op2> <i>; yields {ty}:result</i>
2453 <p>The '<tt>sub</tt>' instruction returns the difference of its two
2456 <p>Note that the '<tt>sub</tt>' instruction is used to represent the
2457 '<tt>neg</tt>' instruction present in most other intermediate
2458 representations.</p>
2462 <p>The two arguments to the '<tt>sub</tt>' instruction must be <a
2463 href="#t_integer">integer</a>, <a href="#t_floating">floating point</a>,
2464 or <a href="#t_vector">vector</a> values. Both arguments must have identical
2469 <p>The value produced is the integer or floating point difference of
2470 the two operands.</p>
2472 <p>If an integer difference has unsigned overflow, the result returned is the
2473 mathematical result modulo 2<sup>n</sup>, where n is the bit width of
2476 <p>Because LLVM integers use a two's complement representation, this
2477 instruction is appropriate for both signed and unsigned integers.</p>
2481 <result> = sub i32 4, %var <i>; yields {i32}:result = 4 - %var</i>
2482 <result> = sub i32 0, %val <i>; yields {i32}:result = -%var</i>
2486 <!-- _______________________________________________________________________ -->
2487 <div class="doc_subsubsection">
2488 <a name="i_mul">'<tt>mul</tt>' Instruction</a>
2491 <div class="doc_text">
2494 <pre> <result> = mul <ty> <op1>, <op2> <i>; yields {ty}:result</i>
2497 <p>The '<tt>mul</tt>' instruction returns the product of its two
2502 <p>The two arguments to the '<tt>mul</tt>' instruction must be <a
2503 href="#t_integer">integer</a>, <a href="#t_floating">floating point</a>,
2504 or <a href="#t_vector">vector</a> values. Both arguments must have identical
2509 <p>The value produced is the integer or floating point product of the
2512 <p>If the result of an integer multiplication has unsigned overflow,
2513 the result returned is the mathematical result modulo
2514 2<sup>n</sup>, where n is the bit width of the result.</p>
2515 <p>Because LLVM integers use a two's complement representation, and the
2516 result is the same width as the operands, this instruction returns the
2517 correct result for both signed and unsigned integers. If a full product
2518 (e.g. <tt>i32</tt>x<tt>i32</tt>-><tt>i64</tt>) is needed, the operands
2519 should be sign-extended or zero-extended as appropriate to the
2520 width of the full product.</p>
2522 <pre> <result> = mul i32 4, %var <i>; yields {i32}:result = 4 * %var</i>
2526 <!-- _______________________________________________________________________ -->
2527 <div class="doc_subsubsection"> <a name="i_udiv">'<tt>udiv</tt>' Instruction
2529 <div class="doc_text">
2531 <pre> <result> = udiv <ty> <op1>, <op2> <i>; yields {ty}:result</i>
2534 <p>The '<tt>udiv</tt>' instruction returns the quotient of its two
2539 <p>The two arguments to the '<tt>udiv</tt>' instruction must be
2540 <a href="#t_integer">integer</a> or <a href="#t_vector">vector</a> of integer
2541 values. Both arguments must have identical types.</p>
2545 <p>The value produced is the unsigned integer quotient of the two operands.</p>
2546 <p>Note that unsigned integer division and signed integer division are distinct
2547 operations; for signed integer division, use '<tt>sdiv</tt>'.</p>
2548 <p>Division by zero leads to undefined behavior.</p>
2550 <pre> <result> = udiv i32 4, %var <i>; yields {i32}:result = 4 / %var</i>
2553 <!-- _______________________________________________________________________ -->
2554 <div class="doc_subsubsection"> <a name="i_sdiv">'<tt>sdiv</tt>' Instruction
2556 <div class="doc_text">
2559 <result> = sdiv <ty> <op1>, <op2> <i>; yields {ty}:result</i>
2564 <p>The '<tt>sdiv</tt>' instruction returns the quotient of its two
2569 <p>The two arguments to the '<tt>sdiv</tt>' instruction must be
2570 <a href="#t_integer">integer</a> or <a href="#t_vector">vector</a> of integer
2571 values. Both arguments must have identical types.</p>
2574 <p>The value produced is the signed integer quotient of the two operands rounded towards zero.</p>
2575 <p>Note that signed integer division and unsigned integer division are distinct
2576 operations; for unsigned integer division, use '<tt>udiv</tt>'.</p>
2577 <p>Division by zero leads to undefined behavior. Overflow also leads to
2578 undefined behavior; this is a rare case, but can occur, for example,
2579 by doing a 32-bit division of -2147483648 by -1.</p>
2581 <pre> <result> = sdiv i32 4, %var <i>; yields {i32}:result = 4 / %var</i>
2584 <!-- _______________________________________________________________________ -->
2585 <div class="doc_subsubsection"> <a name="i_fdiv">'<tt>fdiv</tt>'
2586 Instruction</a> </div>
2587 <div class="doc_text">
2590 <result> = fdiv <ty> <op1>, <op2> <i>; yields {ty}:result</i>
2594 <p>The '<tt>fdiv</tt>' instruction returns the quotient of its two
2599 <p>The two arguments to the '<tt>fdiv</tt>' instruction must be
2600 <a href="#t_floating">floating point</a> or <a href="#t_vector">vector</a>
2601 of floating point values. Both arguments must have identical types.</p>
2605 <p>The value produced is the floating point quotient of the two operands.</p>
2610 <result> = fdiv float 4.0, %var <i>; yields {float}:result = 4.0 / %var</i>
2614 <!-- _______________________________________________________________________ -->
2615 <div class="doc_subsubsection"> <a name="i_urem">'<tt>urem</tt>' Instruction</a>
2617 <div class="doc_text">
2619 <pre> <result> = urem <ty> <op1>, <op2> <i>; yields {ty}:result</i>
2622 <p>The '<tt>urem</tt>' instruction returns the remainder from the
2623 unsigned division of its two arguments.</p>
2625 <p>The two arguments to the '<tt>urem</tt>' instruction must be
2626 <a href="#t_integer">integer</a> or <a href="#t_vector">vector</a> of integer
2627 values. Both arguments must have identical types.</p>
2629 <p>This instruction returns the unsigned integer <i>remainder</i> of a division.
2630 This instruction always performs an unsigned division to get the remainder.</p>
2631 <p>Note that unsigned integer remainder and signed integer remainder are
2632 distinct operations; for signed integer remainder, use '<tt>srem</tt>'.</p>
2633 <p>Taking the remainder of a division by zero leads to undefined behavior.</p>
2635 <pre> <result> = urem i32 4, %var <i>; yields {i32}:result = 4 % %var</i>
2639 <!-- _______________________________________________________________________ -->
2640 <div class="doc_subsubsection">
2641 <a name="i_srem">'<tt>srem</tt>' Instruction</a>
2644 <div class="doc_text">
2649 <result> = srem <ty> <op1>, <op2> <i>; yields {ty}:result</i>
2654 <p>The '<tt>srem</tt>' instruction returns the remainder from the
2655 signed division of its two operands. This instruction can also take
2656 <a href="#t_vector">vector</a> versions of the values in which case
2657 the elements must be integers.</p>
2661 <p>The two arguments to the '<tt>srem</tt>' instruction must be
2662 <a href="#t_integer">integer</a> or <a href="#t_vector">vector</a> of integer
2663 values. Both arguments must have identical types.</p>
2667 <p>This instruction returns the <i>remainder</i> of a division (where the result
2668 has the same sign as the dividend, <tt>op1</tt>), not the <i>modulo</i>
2669 operator (where the result has the same sign as the divisor, <tt>op2</tt>) of
2670 a value. For more information about the difference, see <a
2671 href="http://mathforum.org/dr.math/problems/anne.4.28.99.html">The
2672 Math Forum</a>. For a table of how this is implemented in various languages,
2673 please see <a href="http://en.wikipedia.org/wiki/Modulo_operation">
2674 Wikipedia: modulo operation</a>.</p>
2675 <p>Note that signed integer remainder and unsigned integer remainder are
2676 distinct operations; for unsigned integer remainder, use '<tt>urem</tt>'.</p>
2677 <p>Taking the remainder of a division by zero leads to undefined behavior.
2678 Overflow also leads to undefined behavior; this is a rare case, but can occur,
2679 for example, by taking the remainder of a 32-bit division of -2147483648 by -1.
2680 (The remainder doesn't actually overflow, but this rule lets srem be
2681 implemented using instructions that return both the result of the division
2682 and the remainder.)</p>
2684 <pre> <result> = srem i32 4, %var <i>; yields {i32}:result = 4 % %var</i>
2688 <!-- _______________________________________________________________________ -->
2689 <div class="doc_subsubsection">
2690 <a name="i_frem">'<tt>frem</tt>' Instruction</a> </div>
2692 <div class="doc_text">
2695 <pre> <result> = frem <ty> <op1>, <op2> <i>; yields {ty}:result</i>
2698 <p>The '<tt>frem</tt>' instruction returns the remainder from the
2699 division of its two operands.</p>
2701 <p>The two arguments to the '<tt>frem</tt>' instruction must be
2702 <a href="#t_floating">floating point</a> or <a href="#t_vector">vector</a>
2703 of floating point values. Both arguments must have identical types.</p>
2707 <p>This instruction returns the <i>remainder</i> of a division.
2708 The remainder has the same sign as the dividend.</p>
2713 <result> = frem float 4.0, %var <i>; yields {float}:result = 4.0 % %var</i>
2717 <!-- ======================================================================= -->
2718 <div class="doc_subsection"> <a name="bitwiseops">Bitwise Binary
2719 Operations</a> </div>
2720 <div class="doc_text">
2721 <p>Bitwise binary operators are used to do various forms of
2722 bit-twiddling in a program. They are generally very efficient
2723 instructions and can commonly be strength reduced from other
2724 instructions. They require two operands of the same type, execute an operation on them,
2725 and produce a single value. The resulting value is the same type as its operands.</p>
2728 <!-- _______________________________________________________________________ -->
2729 <div class="doc_subsubsection"> <a name="i_shl">'<tt>shl</tt>'
2730 Instruction</a> </div>
2731 <div class="doc_text">
2733 <pre> <result> = shl <ty> <op1>, <op2> <i>; yields {ty}:result</i>
2738 <p>The '<tt>shl</tt>' instruction returns the first operand shifted to
2739 the left a specified number of bits.</p>
2743 <p>Both arguments to the '<tt>shl</tt>' instruction must be the same <a
2744 href="#t_integer">integer</a> or <a href="#t_vector">vector</a> of integer
2745 type. '<tt>op2</tt>' is treated as an unsigned value.</p>
2749 <p>The value produced is <tt>op1</tt> * 2<sup><tt>op2</tt></sup> mod 2<sup>n</sup>,
2750 where n is the width of the result. If <tt>op2</tt> is (statically or dynamically) negative or
2751 equal to or larger than the number of bits in <tt>op1</tt>, the result is undefined.
2752 If the arguments are vectors, each vector element of <tt>op1</tt> is shifted by the
2753 corresponding shift amount in <tt>op2</tt>.</p>
2755 <h5>Example:</h5><pre>
2756 <result> = shl i32 4, %var <i>; yields {i32}: 4 << %var</i>
2757 <result> = shl i32 4, 2 <i>; yields {i32}: 16</i>
2758 <result> = shl i32 1, 10 <i>; yields {i32}: 1024</i>
2759 <result> = shl i32 1, 32 <i>; undefined</i>
2760 <result> = shl <2 x i32> < i32 1, i32 1>, < i32 1, i32 2> <i>; yields: result=<2 x i32> < i32 2, i32 4></i>
2763 <!-- _______________________________________________________________________ -->
2764 <div class="doc_subsubsection"> <a name="i_lshr">'<tt>lshr</tt>'
2765 Instruction</a> </div>
2766 <div class="doc_text">
2768 <pre> <result> = lshr <ty> <op1>, <op2> <i>; yields {ty}:result</i>
2772 <p>The '<tt>lshr</tt>' instruction (logical shift right) returns the first
2773 operand shifted to the right a specified number of bits with zero fill.</p>
2776 <p>Both arguments to the '<tt>lshr</tt>' instruction must be the same
2777 <a href="#t_integer">integer</a> or <a href="#t_vector">vector</a> of integer
2778 type. '<tt>op2</tt>' is treated as an unsigned value.</p>
2782 <p>This instruction always performs a logical shift right operation. The most
2783 significant bits of the result will be filled with zero bits after the
2784 shift. If <tt>op2</tt> is (statically or dynamically) equal to or larger than
2785 the number of bits in <tt>op1</tt>, the result is undefined. If the arguments are
2786 vectors, each vector element of <tt>op1</tt> is shifted by the corresponding shift
2787 amount in <tt>op2</tt>.</p>
2791 <result> = lshr i32 4, 1 <i>; yields {i32}:result = 2</i>
2792 <result> = lshr i32 4, 2 <i>; yields {i32}:result = 1</i>
2793 <result> = lshr i8 4, 3 <i>; yields {i8}:result = 0</i>
2794 <result> = lshr i8 -2, 1 <i>; yields {i8}:result = 0x7FFFFFFF </i>
2795 <result> = lshr i32 1, 32 <i>; undefined</i>
2796 <result> = lshr <2 x i32> < i32 -2, i32 4>, < i32 1, i32 2> <i>; yields: result=<2 x i32> < i32 0x7FFFFFFF, i32 1></i>
2800 <!-- _______________________________________________________________________ -->
2801 <div class="doc_subsubsection"> <a name="i_ashr">'<tt>ashr</tt>'
2802 Instruction</a> </div>
2803 <div class="doc_text">
2806 <pre> <result> = ashr <ty> <op1>, <op2> <i>; yields {ty}:result</i>
2810 <p>The '<tt>ashr</tt>' instruction (arithmetic shift right) returns the first
2811 operand shifted to the right a specified number of bits with sign extension.</p>
2814 <p>Both arguments to the '<tt>ashr</tt>' instruction must be the same
2815 <a href="#t_integer">integer</a> or <a href="#t_vector">vector</a> of integer
2816 type. '<tt>op2</tt>' is treated as an unsigned value.</p>
2819 <p>This instruction always performs an arithmetic shift right operation,
2820 The most significant bits of the result will be filled with the sign bit
2821 of <tt>op1</tt>. If <tt>op2</tt> is (statically or dynamically) equal to or
2822 larger than the number of bits in <tt>op1</tt>, the result is undefined. If the
2823 arguments are vectors, each vector element of <tt>op1</tt> is shifted by the
2824 corresponding shift amount in <tt>op2</tt>.</p>
2828 <result> = ashr i32 4, 1 <i>; yields {i32}:result = 2</i>
2829 <result> = ashr i32 4, 2 <i>; yields {i32}:result = 1</i>
2830 <result> = ashr i8 4, 3 <i>; yields {i8}:result = 0</i>
2831 <result> = ashr i8 -2, 1 <i>; yields {i8}:result = -1</i>
2832 <result> = ashr i32 1, 32 <i>; undefined</i>
2833 <result> = ashr <2 x i32> < i32 -2, i32 4>, < i32 1, i32 3> <i>; yields: result=<2 x i32> < i32 -1, i32 0></i>
2837 <!-- _______________________________________________________________________ -->
2838 <div class="doc_subsubsection"> <a name="i_and">'<tt>and</tt>'
2839 Instruction</a> </div>
2841 <div class="doc_text">
2846 <result> = and <ty> <op1>, <op2> <i>; yields {ty}:result</i>
2851 <p>The '<tt>and</tt>' instruction returns the bitwise logical and of
2852 its two operands.</p>
2856 <p>The two arguments to the '<tt>and</tt>' instruction must be
2857 <a href="#t_integer">integer</a> or <a href="#t_vector">vector</a> of integer
2858 values. Both arguments must have identical types.</p>
2861 <p>The truth table used for the '<tt>and</tt>' instruction is:</p>
2864 <table border="1" cellspacing="0" cellpadding="4">
2896 <result> = and i32 4, %var <i>; yields {i32}:result = 4 & %var</i>
2897 <result> = and i32 15, 40 <i>; yields {i32}:result = 8</i>
2898 <result> = and i32 4, 8 <i>; yields {i32}:result = 0</i>
2901 <!-- _______________________________________________________________________ -->
2902 <div class="doc_subsubsection"> <a name="i_or">'<tt>or</tt>' Instruction</a> </div>
2903 <div class="doc_text">
2905 <pre> <result> = or <ty> <op1>, <op2> <i>; yields {ty}:result</i>
2908 <p>The '<tt>or</tt>' instruction returns the bitwise logical inclusive
2909 or of its two operands.</p>
2912 <p>The two arguments to the '<tt>or</tt>' instruction must be
2913 <a href="#t_integer">integer</a> or <a href="#t_vector">vector</a> of integer
2914 values. Both arguments must have identical types.</p>
2916 <p>The truth table used for the '<tt>or</tt>' instruction is:</p>
2919 <table border="1" cellspacing="0" cellpadding="4">
2950 <pre> <result> = or i32 4, %var <i>; yields {i32}:result = 4 | %var</i>
2951 <result> = or i32 15, 40 <i>; yields {i32}:result = 47</i>
2952 <result> = or i32 4, 8 <i>; yields {i32}:result = 12</i>
2955 <!-- _______________________________________________________________________ -->
2956 <div class="doc_subsubsection"> <a name="i_xor">'<tt>xor</tt>'
2957 Instruction</a> </div>
2958 <div class="doc_text">
2960 <pre> <result> = xor <ty> <op1>, <op2> <i>; yields {ty}:result</i>
2963 <p>The '<tt>xor</tt>' instruction returns the bitwise logical exclusive
2964 or of its two operands. The <tt>xor</tt> is used to implement the
2965 "one's complement" operation, which is the "~" operator in C.</p>
2967 <p>The two arguments to the '<tt>xor</tt>' instruction must be
2968 <a href="#t_integer">integer</a> or <a href="#t_vector">vector</a> of integer
2969 values. Both arguments must have identical types.</p>
2973 <p>The truth table used for the '<tt>xor</tt>' instruction is:</p>
2976 <table border="1" cellspacing="0" cellpadding="4">
3008 <pre> <result> = xor i32 4, %var <i>; yields {i32}:result = 4 ^ %var</i>
3009 <result> = xor i32 15, 40 <i>; yields {i32}:result = 39</i>
3010 <result> = xor i32 4, 8 <i>; yields {i32}:result = 12</i>
3011 <result> = xor i32 %V, -1 <i>; yields {i32}:result = ~%V</i>
3015 <!-- ======================================================================= -->
3016 <div class="doc_subsection">
3017 <a name="vectorops">Vector Operations</a>
3020 <div class="doc_text">
3022 <p>LLVM supports several instructions to represent vector operations in a
3023 target-independent manner. These instructions cover the element-access and
3024 vector-specific operations needed to process vectors effectively. While LLVM
3025 does directly support these vector operations, many sophisticated algorithms
3026 will want to use target-specific intrinsics to take full advantage of a specific
3031 <!-- _______________________________________________________________________ -->
3032 <div class="doc_subsubsection">
3033 <a name="i_extractelement">'<tt>extractelement</tt>' Instruction</a>
3036 <div class="doc_text">
3041 <result> = extractelement <n x <ty>> <val>, i32 <idx> <i>; yields <ty></i>
3047 The '<tt>extractelement</tt>' instruction extracts a single scalar
3048 element from a vector at a specified index.
3055 The first operand of an '<tt>extractelement</tt>' instruction is a
3056 value of <a href="#t_vector">vector</a> type. The second operand is
3057 an index indicating the position from which to extract the element.
3058 The index may be a variable.</p>
3063 The result is a scalar of the same type as the element type of
3064 <tt>val</tt>. Its value is the value at position <tt>idx</tt> of
3065 <tt>val</tt>. If <tt>idx</tt> exceeds the length of <tt>val</tt>, the
3066 results are undefined.
3072 %result = extractelement <4 x i32> %vec, i32 0 <i>; yields i32</i>
3077 <!-- _______________________________________________________________________ -->
3078 <div class="doc_subsubsection">
3079 <a name="i_insertelement">'<tt>insertelement</tt>' Instruction</a>
3082 <div class="doc_text">
3087 <result> = insertelement <n x <ty>> <val>, <ty> <elt>, i32 <idx> <i>; yields <n x <ty>></i>
3093 The '<tt>insertelement</tt>' instruction inserts a scalar
3094 element into a vector at a specified index.
3101 The first operand of an '<tt>insertelement</tt>' instruction is a
3102 value of <a href="#t_vector">vector</a> type. The second operand is a
3103 scalar value whose type must equal the element type of the first
3104 operand. The third operand is an index indicating the position at
3105 which to insert the value. The index may be a variable.</p>
3110 The result is a vector of the same type as <tt>val</tt>. Its
3111 element values are those of <tt>val</tt> except at position
3112 <tt>idx</tt>, where it gets the value <tt>elt</tt>. If <tt>idx</tt>
3113 exceeds the length of <tt>val</tt>, the results are undefined.
3119 %result = insertelement <4 x i32> %vec, i32 1, i32 0 <i>; yields <4 x i32></i>
3123 <!-- _______________________________________________________________________ -->
3124 <div class="doc_subsubsection">
3125 <a name="i_shufflevector">'<tt>shufflevector</tt>' Instruction</a>
3128 <div class="doc_text">
3133 <result> = shufflevector <n x <ty>> <v1>, <n x <ty>> <v2>, <m x i32> <mask> <i>; yields <m x <ty>></i>
3139 The '<tt>shufflevector</tt>' instruction constructs a permutation of elements
3140 from two input vectors, returning a vector with the same element type as
3141 the input and length that is the same as the shuffle mask.
3147 The first two operands of a '<tt>shufflevector</tt>' instruction are vectors
3148 with types that match each other. The third argument is a shuffle mask whose
3149 element type is always 'i32'. The result of the instruction is a vector whose
3150 length is the same as the shuffle mask and whose element type is the same as
3151 the element type of the first two operands.
3155 The shuffle mask operand is required to be a constant vector with either
3156 constant integer or undef values.
3162 The elements of the two input vectors are numbered from left to right across
3163 both of the vectors. The shuffle mask operand specifies, for each element of
3164 the result vector, which element of the two input vectors the result element
3165 gets. The element selector may be undef (meaning "don't care") and the second
3166 operand may be undef if performing a shuffle from only one vector.
3172 %result = shufflevector <4 x i32> %v1, <4 x i32> %v2,
3173 <4 x i32> <i32 0, i32 4, i32 1, i32 5> <i>; yields <4 x i32></i>
3174 %result = shufflevector <4 x i32> %v1, <4 x i32> undef,
3175 <4 x i32> <i32 0, i32 1, i32 2, i32 3> <i>; yields <4 x i32></i> - Identity shuffle.
3176 %result = shufflevector <8 x i32> %v1, <8 x i32> undef,
3177 <4 x i32> <i32 0, i32 1, i32 2, i32 3> <i>; yields <4 x i32></i>
3178 %result = shufflevector <4 x i32> %v1, <4 x i32> %v2,
3179 <8 x i32> <i32 0, i32 1, i32 2, i32 3, i32 4, i32 5, i32 6, i32 7 > <i>; yields <8 x i32></i>
3184 <!-- ======================================================================= -->
3185 <div class="doc_subsection">
3186 <a name="aggregateops">Aggregate Operations</a>
3189 <div class="doc_text">
3191 <p>LLVM supports several instructions for working with aggregate values.
3196 <!-- _______________________________________________________________________ -->
3197 <div class="doc_subsubsection">
3198 <a name="i_extractvalue">'<tt>extractvalue</tt>' Instruction</a>
3201 <div class="doc_text">
3206 <result> = extractvalue <aggregate type> <val>, <idx>{, <idx>}*
3212 The '<tt>extractvalue</tt>' instruction extracts the value of a struct field
3213 or array element from an aggregate value.
3220 The first operand of an '<tt>extractvalue</tt>' instruction is a
3221 value of <a href="#t_struct">struct</a> or <a href="#t_array">array</a>
3222 type. The operands are constant indices to specify which value to extract
3223 in a similar manner as indices in a
3224 '<tt><a href="#i_getelementptr">getelementptr</a></tt>' instruction.
3230 The result is the value at the position in the aggregate specified by
3237 %result = extractvalue {i32, float} %agg, 0 <i>; yields i32</i>
3242 <!-- _______________________________________________________________________ -->
3243 <div class="doc_subsubsection">
3244 <a name="i_insertvalue">'<tt>insertvalue</tt>' Instruction</a>
3247 <div class="doc_text">
3252 <result> = insertvalue <aggregate type> <val>, <ty> <val>, <idx> <i>; yields <n x <ty>></i>
3258 The '<tt>insertvalue</tt>' instruction inserts a value
3259 into a struct field or array element in an aggregate.
3266 The first operand of an '<tt>insertvalue</tt>' instruction is a
3267 value of <a href="#t_struct">struct</a> or <a href="#t_array">array</a> type.
3268 The second operand is a first-class value to insert.
3269 The following operands are constant indices
3270 indicating the position at which to insert the value in a similar manner as
3272 '<tt><a href="#i_getelementptr">getelementptr</a></tt>' instruction.
3273 The value to insert must have the same type as the value identified
3280 The result is an aggregate of the same type as <tt>val</tt>. Its
3281 value is that of <tt>val</tt> except that the value at the position
3282 specified by the indices is that of <tt>elt</tt>.
3288 %result = insertvalue {i32, float} %agg, i32 1, 0 <i>; yields {i32, float}</i>
3293 <!-- ======================================================================= -->
3294 <div class="doc_subsection">
3295 <a name="memoryops">Memory Access and Addressing Operations</a>
3298 <div class="doc_text">
3300 <p>A key design point of an SSA-based representation is how it
3301 represents memory. In LLVM, no memory locations are in SSA form, which
3302 makes things very simple. This section describes how to read, write,
3303 allocate, and free memory in LLVM.</p>
3307 <!-- _______________________________________________________________________ -->
3308 <div class="doc_subsubsection">
3309 <a name="i_malloc">'<tt>malloc</tt>' Instruction</a>
3312 <div class="doc_text">
3317 <result> = malloc <type>[, i32 <NumElements>][, align <alignment>] <i>; yields {type*}:result</i>
3322 <p>The '<tt>malloc</tt>' instruction allocates memory from the system
3323 heap and returns a pointer to it. The object is always allocated in the generic
3324 address space (address space zero).</p>
3328 <p>The '<tt>malloc</tt>' instruction allocates
3329 <tt>sizeof(<type>)*NumElements</tt>
3330 bytes of memory from the operating system and returns a pointer of the
3331 appropriate type to the program. If "NumElements" is specified, it is the
3332 number of elements allocated, otherwise "NumElements" is defaulted to be one.
3333 If a constant alignment is specified, the value result of the allocation is guaranteed to
3334 be aligned to at least that boundary. If not specified, or if zero, the target can
3335 choose to align the allocation on any convenient boundary.</p>
3337 <p>'<tt>type</tt>' must be a sized type.</p>
3341 <p>Memory is allocated using the system "<tt>malloc</tt>" function, and
3342 a pointer is returned. The result of a zero byte allocation is undefined. The
3343 result is null if there is insufficient memory available.</p>
3348 %array = malloc [4 x i8] <i>; yields {[%4 x i8]*}:array</i>
3350 %size = <a href="#i_add">add</a> i32 2, 2 <i>; yields {i32}:size = i32 4</i>
3351 %array1 = malloc i8, i32 4 <i>; yields {i8*}:array1</i>
3352 %array2 = malloc [12 x i8], i32 %size <i>; yields {[12 x i8]*}:array2</i>
3353 %array3 = malloc i32, i32 4, align 1024 <i>; yields {i32*}:array3</i>
3354 %array4 = malloc i32, align 1024 <i>; yields {i32*}:array4</i>
3357 <p>Note that the code generator does not yet respect the
3358 alignment value.</p>
3362 <!-- _______________________________________________________________________ -->
3363 <div class="doc_subsubsection">
3364 <a name="i_free">'<tt>free</tt>' Instruction</a>
3367 <div class="doc_text">
3372 free <type> <value> <i>; yields {void}</i>
3377 <p>The '<tt>free</tt>' instruction returns memory back to the unused
3378 memory heap to be reallocated in the future.</p>
3382 <p>'<tt>value</tt>' shall be a pointer value that points to a value
3383 that was allocated with the '<tt><a href="#i_malloc">malloc</a></tt>'
3388 <p>Access to the memory pointed to by the pointer is no longer defined
3389 after this instruction executes. If the pointer is null, the operation
3395 %array = <a href="#i_malloc">malloc</a> [4 x i8] <i>; yields {[4 x i8]*}:array</i>
3396 free [4 x i8]* %array
3400 <!-- _______________________________________________________________________ -->
3401 <div class="doc_subsubsection">
3402 <a name="i_alloca">'<tt>alloca</tt>' Instruction</a>
3405 <div class="doc_text">
3410 <result> = alloca <type>[, i32 <NumElements>][, align <alignment>] <i>; yields {type*}:result</i>
3415 <p>The '<tt>alloca</tt>' instruction allocates memory on the stack frame of the
3416 currently executing function, to be automatically released when this function
3417 returns to its caller. The object is always allocated in the generic address
3418 space (address space zero).</p>
3422 <p>The '<tt>alloca</tt>' instruction allocates <tt>sizeof(<type>)*NumElements</tt>
3423 bytes of memory on the runtime stack, returning a pointer of the
3424 appropriate type to the program. If "NumElements" is specified, it is the
3425 number of elements allocated, otherwise "NumElements" is defaulted to be one.
3426 If a constant alignment is specified, the value result of the allocation is guaranteed
3427 to be aligned to at least that boundary. If not specified, or if zero, the target
3428 can choose to align the allocation on any convenient boundary.</p>
3430 <p>'<tt>type</tt>' may be any sized type.</p>
3434 <p>Memory is allocated; a pointer is returned. The operation is undefiend if
3435 there is insufficient stack space for the allocation. '<tt>alloca</tt>'d
3436 memory is automatically released when the function returns. The '<tt>alloca</tt>'
3437 instruction is commonly used to represent automatic variables that must
3438 have an address available. When the function returns (either with the <tt><a
3439 href="#i_ret">ret</a></tt> or <tt><a href="#i_unwind">unwind</a></tt>
3440 instructions), the memory is reclaimed. Allocating zero bytes
3441 is legal, but the result is undefined.</p>
3446 %ptr = alloca i32 <i>; yields {i32*}:ptr</i>
3447 %ptr = alloca i32, i32 4 <i>; yields {i32*}:ptr</i>
3448 %ptr = alloca i32, i32 4, align 1024 <i>; yields {i32*}:ptr</i>
3449 %ptr = alloca i32, align 1024 <i>; yields {i32*}:ptr</i>
3453 <!-- _______________________________________________________________________ -->
3454 <div class="doc_subsubsection"> <a name="i_load">'<tt>load</tt>'
3455 Instruction</a> </div>
3456 <div class="doc_text">
3458 <pre> <result> = load <ty>* <pointer>[, align <alignment>]<br> <result> = volatile load <ty>* <pointer>[, align <alignment>]<br></pre>
3460 <p>The '<tt>load</tt>' instruction is used to read from memory.</p>
3462 <p>The argument to the '<tt>load</tt>' instruction specifies the memory
3463 address from which to load. The pointer must point to a <a
3464 href="#t_firstclass">first class</a> type. If the <tt>load</tt> is
3465 marked as <tt>volatile</tt>, then the optimizer is not allowed to modify
3466 the number or order of execution of this <tt>load</tt> with other
3467 volatile <tt>load</tt> and <tt><a href="#i_store">store</a></tt>
3470 The optional constant "align" argument specifies the alignment of the operation
3471 (that is, the alignment of the memory address). A value of 0 or an
3472 omitted "align" argument means that the operation has the preferential
3473 alignment for the target. It is the responsibility of the code emitter
3474 to ensure that the alignment information is correct. Overestimating
3475 the alignment results in an undefined behavior. Underestimating the
3476 alignment may produce less efficient code. An alignment of 1 is always
3480 <p>The location of memory pointed to is loaded.</p>
3482 <pre> %ptr = <a href="#i_alloca">alloca</a> i32 <i>; yields {i32*}:ptr</i>
3484 href="#i_store">store</a> i32 3, i32* %ptr <i>; yields {void}</i>
3485 %val = load i32* %ptr <i>; yields {i32}:val = i32 3</i>
3488 <!-- _______________________________________________________________________ -->
3489 <div class="doc_subsubsection"> <a name="i_store">'<tt>store</tt>'
3490 Instruction</a> </div>
3491 <div class="doc_text">
3493 <pre> store <ty> <value>, <ty>* <pointer>[, align <alignment>] <i>; yields {void}</i>
3494 volatile store <ty> <value>, <ty>* <pointer>[, align <alignment>] <i>; yields {void}</i>
3497 <p>The '<tt>store</tt>' instruction is used to write to memory.</p>
3499 <p>There are two arguments to the '<tt>store</tt>' instruction: a value
3500 to store and an address at which to store it. The type of the '<tt><pointer></tt>'
3501 operand must be a pointer to the <a href="#t_firstclass">first class</a> type
3502 of the '<tt><value></tt>'
3503 operand. If the <tt>store</tt> is marked as <tt>volatile</tt>, then the
3504 optimizer is not allowed to modify the number or order of execution of
3505 this <tt>store</tt> with other volatile <tt>load</tt> and <tt><a
3506 href="#i_store">store</a></tt> instructions.</p>
3508 The optional constant "align" argument specifies the alignment of the operation
3509 (that is, the alignment of the memory address). A value of 0 or an
3510 omitted "align" argument means that the operation has the preferential
3511 alignment for the target. It is the responsibility of the code emitter
3512 to ensure that the alignment information is correct. Overestimating
3513 the alignment results in an undefined behavior. Underestimating the
3514 alignment may produce less efficient code. An alignment of 1 is always
3518 <p>The contents of memory are updated to contain '<tt><value></tt>'
3519 at the location specified by the '<tt><pointer></tt>' operand.</p>
3521 <pre> %ptr = <a href="#i_alloca">alloca</a> i32 <i>; yields {i32*}:ptr</i>
3522 store i32 3, i32* %ptr <i>; yields {void}</i>
3523 %val = <a href="#i_load">load</a> i32* %ptr <i>; yields {i32}:val = i32 3</i>
3527 <!-- _______________________________________________________________________ -->
3528 <div class="doc_subsubsection">
3529 <a name="i_getelementptr">'<tt>getelementptr</tt>' Instruction</a>
3532 <div class="doc_text">
3535 <result> = getelementptr <pty>* <ptrval>{, <ty> <idx>}*
3541 The '<tt>getelementptr</tt>' instruction is used to get the address of a
3542 subelement of an aggregate data structure. It performs address calculation only
3543 and does not access memory.</p>
3547 <p>The first argument is always a pointer, and forms the basis of the
3548 calculation. The remaining arguments are indices, that indicate which of the
3549 elements of the aggregate object are indexed. The interpretation of each index
3550 is dependent on the type being indexed into. The first index always indexes the
3551 pointer value given as the first argument, the second index indexes a value of
3552 the type pointed to (not necessarily the value directly pointed to, since the
3553 first index can be non-zero), etc. The first type indexed into must be a pointer
3554 value, subsequent types can be arrays, vectors and structs. Note that subsequent
3555 types being indexed into can never be pointers, since that would require loading
3556 the pointer before continuing calculation.</p>
3558 <p>The type of each index argument depends on the type it is indexing into.
3559 When indexing into a (packed) structure, only <tt>i32</tt> integer
3560 <b>constants</b> are allowed. When indexing into an array, pointer or vector,
3561 only integers of 32 or 64 bits are allowed (also non-constants). 32-bit values
3562 will be sign extended to 64-bits if required.</p>
3564 <p>For example, let's consider a C code fragment and how it gets
3565 compiled to LLVM:</p>
3567 <div class="doc_code">
3580 int *foo(struct ST *s) {
3581 return &s[1].Z.B[5][13];
3586 <p>The LLVM code generated by the GCC frontend is:</p>
3588 <div class="doc_code">
3590 %RT = <a href="#namedtypes">type</a> { i8 , [10 x [20 x i32]], i8 }
3591 %ST = <a href="#namedtypes">type</a> { i32, double, %RT }
3593 define i32* %foo(%ST* %s) {
3595 %reg = getelementptr %ST* %s, i32 1, i32 2, i32 1, i32 5, i32 13
3603 <p>In the example above, the first index is indexing into the '<tt>%ST*</tt>'
3604 type, which is a pointer, yielding a '<tt>%ST</tt>' = '<tt>{ i32, double, %RT
3605 }</tt>' type, a structure. The second index indexes into the third element of
3606 the structure, yielding a '<tt>%RT</tt>' = '<tt>{ i8 , [10 x [20 x i32]],
3607 i8 }</tt>' type, another structure. The third index indexes into the second
3608 element of the structure, yielding a '<tt>[10 x [20 x i32]]</tt>' type, an
3609 array. The two dimensions of the array are subscripted into, yielding an
3610 '<tt>i32</tt>' type. The '<tt>getelementptr</tt>' instruction returns a pointer
3611 to this element, thus computing a value of '<tt>i32*</tt>' type.</p>
3613 <p>Note that it is perfectly legal to index partially through a
3614 structure, returning a pointer to an inner element. Because of this,
3615 the LLVM code for the given testcase is equivalent to:</p>
3618 define i32* %foo(%ST* %s) {
3619 %t1 = getelementptr %ST* %s, i32 1 <i>; yields %ST*:%t1</i>
3620 %t2 = getelementptr %ST* %t1, i32 0, i32 2 <i>; yields %RT*:%t2</i>
3621 %t3 = getelementptr %RT* %t2, i32 0, i32 1 <i>; yields [10 x [20 x i32]]*:%t3</i>
3622 %t4 = getelementptr [10 x [20 x i32]]* %t3, i32 0, i32 5 <i>; yields [20 x i32]*:%t4</i>
3623 %t5 = getelementptr [20 x i32]* %t4, i32 0, i32 13 <i>; yields i32*:%t5</i>
3628 <p>Note that it is undefined to access an array out of bounds: array and
3629 pointer indexes must always be within the defined bounds of the array type.
3630 The one exception for this rule is zero length arrays. These arrays are
3631 defined to be accessible as variable length arrays, which requires access
3632 beyond the zero'th element.</p>
3634 <p>The getelementptr instruction is often confusing. For some more insight
3635 into how it works, see <a href="GetElementPtr.html">the getelementptr
3641 <i>; yields [12 x i8]*:aptr</i>
3642 %aptr = getelementptr {i32, [12 x i8]}* %saptr, i64 0, i32 1
3643 <i>; yields i8*:vptr</i>
3644 %vptr = getelementptr {i32, <2 x i8>}* %svptr, i64 0, i32 1, i32 1
3645 <i>; yields i8*:eptr</i>
3646 %eptr = getelementptr [12 x i8]* %aptr, i64 0, i32 1
3650 <!-- ======================================================================= -->
3651 <div class="doc_subsection"> <a name="convertops">Conversion Operations</a>
3653 <div class="doc_text">
3654 <p>The instructions in this category are the conversion instructions (casting)
3655 which all take a single operand and a type. They perform various bit conversions
3659 <!-- _______________________________________________________________________ -->
3660 <div class="doc_subsubsection">
3661 <a name="i_trunc">'<tt>trunc .. to</tt>' Instruction</a>
3663 <div class="doc_text">
3667 <result> = trunc <ty> <value> to <ty2> <i>; yields ty2</i>
3672 The '<tt>trunc</tt>' instruction truncates its operand to the type <tt>ty2</tt>.
3677 The '<tt>trunc</tt>' instruction takes a <tt>value</tt> to trunc, which must
3678 be an <a href="#t_integer">integer</a> type, and a type that specifies the size
3679 and type of the result, which must be an <a href="#t_integer">integer</a>
3680 type. The bit size of <tt>value</tt> must be larger than the bit size of
3681 <tt>ty2</tt>. Equal sized types are not allowed.</p>
3685 The '<tt>trunc</tt>' instruction truncates the high order bits in <tt>value</tt>
3686 and converts the remaining bits to <tt>ty2</tt>. Since the source size must be
3687 larger than the destination size, <tt>trunc</tt> cannot be a <i>no-op cast</i>.
3688 It will always truncate bits.</p>
3692 %X = trunc i32 257 to i8 <i>; yields i8:1</i>
3693 %Y = trunc i32 123 to i1 <i>; yields i1:true</i>
3694 %Y = trunc i32 122 to i1 <i>; yields i1:false</i>
3698 <!-- _______________________________________________________________________ -->
3699 <div class="doc_subsubsection">
3700 <a name="i_zext">'<tt>zext .. to</tt>' Instruction</a>
3702 <div class="doc_text">
3706 <result> = zext <ty> <value> to <ty2> <i>; yields ty2</i>
3710 <p>The '<tt>zext</tt>' instruction zero extends its operand to type
3715 <p>The '<tt>zext</tt>' instruction takes a value to cast, which must be of
3716 <a href="#t_integer">integer</a> type, and a type to cast it to, which must
3717 also be of <a href="#t_integer">integer</a> type. The bit size of the
3718 <tt>value</tt> must be smaller than the bit size of the destination type,
3722 <p>The <tt>zext</tt> fills the high order bits of the <tt>value</tt> with zero
3723 bits until it reaches the size of the destination type, <tt>ty2</tt>.</p>
3725 <p>When zero extending from i1, the result will always be either 0 or 1.</p>
3729 %X = zext i32 257 to i64 <i>; yields i64:257</i>
3730 %Y = zext i1 true to i32 <i>; yields i32:1</i>
3734 <!-- _______________________________________________________________________ -->
3735 <div class="doc_subsubsection">
3736 <a name="i_sext">'<tt>sext .. to</tt>' Instruction</a>
3738 <div class="doc_text">
3742 <result> = sext <ty> <value> to <ty2> <i>; yields ty2</i>
3746 <p>The '<tt>sext</tt>' sign extends <tt>value</tt> to the type <tt>ty2</tt>.</p>
3750 The '<tt>sext</tt>' instruction takes a value to cast, which must be of
3751 <a href="#t_integer">integer</a> type, and a type to cast it to, which must
3752 also be of <a href="#t_integer">integer</a> type. The bit size of the
3753 <tt>value</tt> must be smaller than the bit size of the destination type,
3758 The '<tt>sext</tt>' instruction performs a sign extension by copying the sign
3759 bit (highest order bit) of the <tt>value</tt> until it reaches the bit size of
3760 the type <tt>ty2</tt>.</p>
3762 <p>When sign extending from i1, the extension always results in -1 or 0.</p>
3766 %X = sext i8 -1 to i16 <i>; yields i16 :65535</i>
3767 %Y = sext i1 true to i32 <i>; yields i32:-1</i>
3771 <!-- _______________________________________________________________________ -->
3772 <div class="doc_subsubsection">
3773 <a name="i_fptrunc">'<tt>fptrunc .. to</tt>' Instruction</a>
3776 <div class="doc_text">
3781 <result> = fptrunc <ty> <value> to <ty2> <i>; yields ty2</i>
3785 <p>The '<tt>fptrunc</tt>' instruction truncates <tt>value</tt> to type
3790 <p>The '<tt>fptrunc</tt>' instruction takes a <a href="#t_floating">floating
3791 point</a> value to cast and a <a href="#t_floating">floating point</a> type to
3792 cast it to. The size of <tt>value</tt> must be larger than the size of
3793 <tt>ty2</tt>. This implies that <tt>fptrunc</tt> cannot be used to make a
3794 <i>no-op cast</i>.</p>
3797 <p> The '<tt>fptrunc</tt>' instruction truncates a <tt>value</tt> from a larger
3798 <a href="#t_floating">floating point</a> type to a smaller
3799 <a href="#t_floating">floating point</a> type. If the value cannot fit within
3800 the destination type, <tt>ty2</tt>, then the results are undefined.</p>
3804 %X = fptrunc double 123.0 to float <i>; yields float:123.0</i>
3805 %Y = fptrunc double 1.0E+300 to float <i>; yields undefined</i>
3809 <!-- _______________________________________________________________________ -->
3810 <div class="doc_subsubsection">
3811 <a name="i_fpext">'<tt>fpext .. to</tt>' Instruction</a>
3813 <div class="doc_text">
3817 <result> = fpext <ty> <value> to <ty2> <i>; yields ty2</i>
3821 <p>The '<tt>fpext</tt>' extends a floating point <tt>value</tt> to a larger
3822 floating point value.</p>
3825 <p>The '<tt>fpext</tt>' instruction takes a
3826 <a href="#t_floating">floating point</a> <tt>value</tt> to cast,
3827 and a <a href="#t_floating">floating point</a> type to cast it to. The source
3828 type must be smaller than the destination type.</p>
3831 <p>The '<tt>fpext</tt>' instruction extends the <tt>value</tt> from a smaller
3832 <a href="#t_floating">floating point</a> type to a larger
3833 <a href="#t_floating">floating point</a> type. The <tt>fpext</tt> cannot be
3834 used to make a <i>no-op cast</i> because it always changes bits. Use
3835 <tt>bitcast</tt> to make a <i>no-op cast</i> for a floating point cast.</p>
3839 %X = fpext float 3.1415 to double <i>; yields double:3.1415</i>
3840 %Y = fpext float 1.0 to float <i>; yields float:1.0 (no-op)</i>
3844 <!-- _______________________________________________________________________ -->
3845 <div class="doc_subsubsection">
3846 <a name="i_fptoui">'<tt>fptoui .. to</tt>' Instruction</a>
3848 <div class="doc_text">
3852 <result> = fptoui <ty> <value> to <ty2> <i>; yields ty2</i>
3856 <p>The '<tt>fptoui</tt>' converts a floating point <tt>value</tt> to its
3857 unsigned integer equivalent of type <tt>ty2</tt>.
3861 <p>The '<tt>fptoui</tt>' instruction takes a value to cast, which must be a
3862 scalar or vector <a href="#t_floating">floating point</a> value, and a type
3863 to cast it to <tt>ty2</tt>, which must be an <a href="#t_integer">integer</a>
3864 type. If <tt>ty</tt> is a vector floating point type, <tt>ty2</tt> must be a
3865 vector integer type with the same number of elements as <tt>ty</tt></p>
3868 <p> The '<tt>fptoui</tt>' instruction converts its
3869 <a href="#t_floating">floating point</a> operand into the nearest (rounding
3870 towards zero) unsigned integer value. If the value cannot fit in <tt>ty2</tt>,
3871 the results are undefined.</p>
3875 %X = fptoui double 123.0 to i32 <i>; yields i32:123</i>
3876 %Y = fptoui float 1.0E+300 to i1 <i>; yields undefined:1</i>
3877 %X = fptoui float 1.04E+17 to i8 <i>; yields undefined:1</i>
3881 <!-- _______________________________________________________________________ -->
3882 <div class="doc_subsubsection">
3883 <a name="i_fptosi">'<tt>fptosi .. to</tt>' Instruction</a>
3885 <div class="doc_text">
3889 <result> = fptosi <ty> <value> to <ty2> <i>; yields ty2</i>
3893 <p>The '<tt>fptosi</tt>' instruction converts
3894 <a href="#t_floating">floating point</a> <tt>value</tt> to type <tt>ty2</tt>.
3898 <p> The '<tt>fptosi</tt>' instruction takes a value to cast, which must be a
3899 scalar or vector <a href="#t_floating">floating point</a> value, and a type
3900 to cast it to <tt>ty2</tt>, which must be an <a href="#t_integer">integer</a>
3901 type. If <tt>ty</tt> is a vector floating point type, <tt>ty2</tt> must be a
3902 vector integer type with the same number of elements as <tt>ty</tt></p>
3905 <p>The '<tt>fptosi</tt>' instruction converts its
3906 <a href="#t_floating">floating point</a> operand into the nearest (rounding
3907 towards zero) signed integer value. If the value cannot fit in <tt>ty2</tt>,
3908 the results are undefined.</p>
3912 %X = fptosi double -123.0 to i32 <i>; yields i32:-123</i>
3913 %Y = fptosi float 1.0E-247 to i1 <i>; yields undefined:1</i>
3914 %X = fptosi float 1.04E+17 to i8 <i>; yields undefined:1</i>
3918 <!-- _______________________________________________________________________ -->
3919 <div class="doc_subsubsection">
3920 <a name="i_uitofp">'<tt>uitofp .. to</tt>' Instruction</a>
3922 <div class="doc_text">
3926 <result> = uitofp <ty> <value> to <ty2> <i>; yields ty2</i>
3930 <p>The '<tt>uitofp</tt>' instruction regards <tt>value</tt> as an unsigned
3931 integer and converts that value to the <tt>ty2</tt> type.</p>
3934 <p>The '<tt>uitofp</tt>' instruction takes a value to cast, which must be a
3935 scalar or vector <a href="#t_integer">integer</a> value, and a type to cast it
3936 to <tt>ty2</tt>, which must be an <a href="#t_floating">floating point</a>
3937 type. If <tt>ty</tt> is a vector integer type, <tt>ty2</tt> must be a vector
3938 floating point type with the same number of elements as <tt>ty</tt></p>
3941 <p>The '<tt>uitofp</tt>' instruction interprets its operand as an unsigned
3942 integer quantity and converts it to the corresponding floating point value. If
3943 the value cannot fit in the floating point value, the results are undefined.</p>
3947 %X = uitofp i32 257 to float <i>; yields float:257.0</i>
3948 %Y = uitofp i8 -1 to double <i>; yields double:255.0</i>
3952 <!-- _______________________________________________________________________ -->
3953 <div class="doc_subsubsection">
3954 <a name="i_sitofp">'<tt>sitofp .. to</tt>' Instruction</a>
3956 <div class="doc_text">
3960 <result> = sitofp <ty> <value> to <ty2> <i>; yields ty2</i>
3964 <p>The '<tt>sitofp</tt>' instruction regards <tt>value</tt> as a signed
3965 integer and converts that value to the <tt>ty2</tt> type.</p>
3968 <p>The '<tt>sitofp</tt>' instruction takes a value to cast, which must be a
3969 scalar or vector <a href="#t_integer">integer</a> value, and a type to cast it
3970 to <tt>ty2</tt>, which must be an <a href="#t_floating">floating point</a>
3971 type. If <tt>ty</tt> is a vector integer type, <tt>ty2</tt> must be a vector
3972 floating point type with the same number of elements as <tt>ty</tt></p>
3975 <p>The '<tt>sitofp</tt>' instruction interprets its operand as a signed
3976 integer quantity and converts it to the corresponding floating point value. If
3977 the value cannot fit in the floating point value, the results are undefined.</p>
3981 %X = sitofp i32 257 to float <i>; yields float:257.0</i>
3982 %Y = sitofp i8 -1 to double <i>; yields double:-1.0</i>
3986 <!-- _______________________________________________________________________ -->
3987 <div class="doc_subsubsection">
3988 <a name="i_ptrtoint">'<tt>ptrtoint .. to</tt>' Instruction</a>
3990 <div class="doc_text">
3994 <result> = ptrtoint <ty> <value> to <ty2> <i>; yields ty2</i>
3998 <p>The '<tt>ptrtoint</tt>' instruction converts the pointer <tt>value</tt> to
3999 the integer type <tt>ty2</tt>.</p>
4002 <p>The '<tt>ptrtoint</tt>' instruction takes a <tt>value</tt> to cast, which
4003 must be a <a href="#t_pointer">pointer</a> value, and a type to cast it to
4004 <tt>ty2</tt>, which must be an <a href="#t_integer">integer</a> type.</p>
4007 <p>The '<tt>ptrtoint</tt>' instruction converts <tt>value</tt> to integer type
4008 <tt>ty2</tt> by interpreting the pointer value as an integer and either
4009 truncating or zero extending that value to the size of the integer type. If
4010 <tt>value</tt> is smaller than <tt>ty2</tt> then a zero extension is done. If
4011 <tt>value</tt> is larger than <tt>ty2</tt> then a truncation is done. If they
4012 are the same size, then nothing is done (<i>no-op cast</i>) other than a type
4017 %X = ptrtoint i32* %X to i8 <i>; yields truncation on 32-bit architecture</i>
4018 %Y = ptrtoint i32* %x to i64 <i>; yields zero extension on 32-bit architecture</i>
4022 <!-- _______________________________________________________________________ -->
4023 <div class="doc_subsubsection">
4024 <a name="i_inttoptr">'<tt>inttoptr .. to</tt>' Instruction</a>
4026 <div class="doc_text">
4030 <result> = inttoptr <ty> <value> to <ty2> <i>; yields ty2</i>
4034 <p>The '<tt>inttoptr</tt>' instruction converts an integer <tt>value</tt> to
4035 a pointer type, <tt>ty2</tt>.</p>
4038 <p>The '<tt>inttoptr</tt>' instruction takes an <a href="#t_integer">integer</a>
4039 value to cast, and a type to cast it to, which must be a
4040 <a href="#t_pointer">pointer</a> type.</p>
4043 <p>The '<tt>inttoptr</tt>' instruction converts <tt>value</tt> to type
4044 <tt>ty2</tt> by applying either a zero extension or a truncation depending on
4045 the size of the integer <tt>value</tt>. If <tt>value</tt> is larger than the
4046 size of a pointer then a truncation is done. If <tt>value</tt> is smaller than
4047 the size of a pointer then a zero extension is done. If they are the same size,
4048 nothing is done (<i>no-op cast</i>).</p>
4052 %X = inttoptr i32 255 to i32* <i>; yields zero extension on 64-bit architecture</i>
4053 %X = inttoptr i32 255 to i32* <i>; yields no-op on 32-bit architecture</i>
4054 %Y = inttoptr i64 0 to i32* <i>; yields truncation on 32-bit architecture</i>
4058 <!-- _______________________________________________________________________ -->
4059 <div class="doc_subsubsection">
4060 <a name="i_bitcast">'<tt>bitcast .. to</tt>' Instruction</a>
4062 <div class="doc_text">
4066 <result> = bitcast <ty> <value> to <ty2> <i>; yields ty2</i>
4071 <p>The '<tt>bitcast</tt>' instruction converts <tt>value</tt> to type
4072 <tt>ty2</tt> without changing any bits.</p>
4076 <p>The '<tt>bitcast</tt>' instruction takes a value to cast, which must be
4077 a non-aggregate first class value, and a type to cast it to, which must also be
4078 a non-aggregate <a href="#t_firstclass">first class</a> type. The bit sizes of
4080 and the destination type, <tt>ty2</tt>, must be identical. If the source
4081 type is a pointer, the destination type must also be a pointer. This
4082 instruction supports bitwise conversion of vectors to integers and to vectors
4083 of other types (as long as they have the same size).</p>
4086 <p>The '<tt>bitcast</tt>' instruction converts <tt>value</tt> to type
4087 <tt>ty2</tt>. It is always a <i>no-op cast</i> because no bits change with
4088 this conversion. The conversion is done as if the <tt>value</tt> had been
4089 stored to memory and read back as type <tt>ty2</tt>. Pointer types may only be
4090 converted to other pointer types with this instruction. To convert pointers to
4091 other types, use the <a href="#i_inttoptr">inttoptr</a> or
4092 <a href="#i_ptrtoint">ptrtoint</a> instructions first.</p>
4096 %X = bitcast i8 255 to i8 <i>; yields i8 :-1</i>
4097 %Y = bitcast i32* %x to sint* <i>; yields sint*:%x</i>
4098 %Z = bitcast <2 x int> %V to i64; <i>; yields i64: %V</i>
4102 <!-- ======================================================================= -->
4103 <div class="doc_subsection"> <a name="otherops">Other Operations</a> </div>
4104 <div class="doc_text">
4105 <p>The instructions in this category are the "miscellaneous"
4106 instructions, which defy better classification.</p>
4109 <!-- _______________________________________________________________________ -->
4110 <div class="doc_subsubsection"><a name="i_icmp">'<tt>icmp</tt>' Instruction</a>
4112 <div class="doc_text">
4114 <pre> <result> = icmp <cond> <ty> <op1>, <op2> <i>; yields {i1} or {<N x i1>}:result</i>
4117 <p>The '<tt>icmp</tt>' instruction returns a boolean value or
4118 a vector of boolean values based on comparison
4119 of its two integer, integer vector, or pointer operands.</p>
4121 <p>The '<tt>icmp</tt>' instruction takes three operands. The first operand is
4122 the condition code indicating the kind of comparison to perform. It is not
4123 a value, just a keyword. The possible condition code are:
4126 <li><tt>eq</tt>: equal</li>
4127 <li><tt>ne</tt>: not equal </li>
4128 <li><tt>ugt</tt>: unsigned greater than</li>
4129 <li><tt>uge</tt>: unsigned greater or equal</li>
4130 <li><tt>ult</tt>: unsigned less than</li>
4131 <li><tt>ule</tt>: unsigned less or equal</li>
4132 <li><tt>sgt</tt>: signed greater than</li>
4133 <li><tt>sge</tt>: signed greater or equal</li>
4134 <li><tt>slt</tt>: signed less than</li>
4135 <li><tt>sle</tt>: signed less or equal</li>
4137 <p>The remaining two arguments must be <a href="#t_integer">integer</a> or
4138 <a href="#t_pointer">pointer</a>
4139 or integer <a href="#t_vector">vector</a> typed.
4140 They must also be identical types.</p>
4142 <p>The '<tt>icmp</tt>' compares <tt>op1</tt> and <tt>op2</tt> according to
4143 the condition code given as <tt>cond</tt>. The comparison performed always
4144 yields either an <a href="#t_primitive"><tt>i1</tt></a> or vector of <tt>i1</tt> result, as follows:
4147 <li><tt>eq</tt>: yields <tt>true</tt> if the operands are equal,
4148 <tt>false</tt> otherwise. No sign interpretation is necessary or performed.
4150 <li><tt>ne</tt>: yields <tt>true</tt> if the operands are unequal,
4151 <tt>false</tt> otherwise. No sign interpretation is necessary or performed.</li>
4152 <li><tt>ugt</tt>: interprets the operands as unsigned values and yields
4153 <tt>true</tt> if <tt>op1</tt> is greater than <tt>op2</tt>.</li>
4154 <li><tt>uge</tt>: interprets the operands as unsigned values and yields
4155 <tt>true</tt> if <tt>op1</tt> is greater than or equal to <tt>op2</tt>.</li>
4156 <li><tt>ult</tt>: interprets the operands as unsigned values and yields
4157 <tt>true</tt> if <tt>op1</tt> is less than <tt>op2</tt>.</li>
4158 <li><tt>ule</tt>: interprets the operands as unsigned values and yields
4159 <tt>true</tt> if <tt>op1</tt> is less than or equal to <tt>op2</tt>.</li>
4160 <li><tt>sgt</tt>: interprets the operands as signed values and yields
4161 <tt>true</tt> if <tt>op1</tt> is greater than <tt>op2</tt>.</li>
4162 <li><tt>sge</tt>: interprets the operands as signed values and yields
4163 <tt>true</tt> if <tt>op1</tt> is greater than or equal to <tt>op2</tt>.</li>
4164 <li><tt>slt</tt>: interprets the operands as signed values and yields
4165 <tt>true</tt> if <tt>op1</tt> is less than <tt>op2</tt>.</li>
4166 <li><tt>sle</tt>: interprets the operands as signed values and yields
4167 <tt>true</tt> if <tt>op1</tt> is less than or equal to <tt>op2</tt>.</li>
4169 <p>If the operands are <a href="#t_pointer">pointer</a> typed, the pointer
4170 values are compared as if they were integers.</p>
4171 <p>If the operands are integer vectors, then they are compared
4172 element by element. The result is an <tt>i1</tt> vector with
4173 the same number of elements as the values being compared.
4174 Otherwise, the result is an <tt>i1</tt>.
4178 <pre> <result> = icmp eq i32 4, 5 <i>; yields: result=false</i>
4179 <result> = icmp ne float* %X, %X <i>; yields: result=false</i>
4180 <result> = icmp ult i16 4, 5 <i>; yields: result=true</i>
4181 <result> = icmp sgt i16 4, 5 <i>; yields: result=false</i>
4182 <result> = icmp ule i16 -4, 5 <i>; yields: result=false</i>
4183 <result> = icmp sge i16 4, 5 <i>; yields: result=false</i>
4186 <p>Note that the code generator does not yet support vector types with
4187 the <tt>icmp</tt> instruction.</p>
4191 <!-- _______________________________________________________________________ -->
4192 <div class="doc_subsubsection"><a name="i_fcmp">'<tt>fcmp</tt>' Instruction</a>
4194 <div class="doc_text">
4196 <pre> <result> = fcmp <cond> <ty> <op1>, <op2> <i>; yields {i1} or {<N x i1>}:result</i>
4199 <p>The '<tt>fcmp</tt>' instruction returns a boolean value
4200 or vector of boolean values based on comparison
4201 of its operands.</p>
4203 If the operands are floating point scalars, then the result
4204 type is a boolean (<a href="#t_primitive"><tt>i1</tt></a>).
4206 <p>If the operands are floating point vectors, then the result type
4207 is a vector of boolean with the same number of elements as the
4208 operands being compared.</p>
4210 <p>The '<tt>fcmp</tt>' instruction takes three operands. The first operand is
4211 the condition code indicating the kind of comparison to perform. It is not
4212 a value, just a keyword. The possible condition code are:</p>
4214 <li><tt>false</tt>: no comparison, always returns false</li>
4215 <li><tt>oeq</tt>: ordered and equal</li>
4216 <li><tt>ogt</tt>: ordered and greater than </li>
4217 <li><tt>oge</tt>: ordered and greater than or equal</li>
4218 <li><tt>olt</tt>: ordered and less than </li>
4219 <li><tt>ole</tt>: ordered and less than or equal</li>
4220 <li><tt>one</tt>: ordered and not equal</li>
4221 <li><tt>ord</tt>: ordered (no nans)</li>
4222 <li><tt>ueq</tt>: unordered or equal</li>
4223 <li><tt>ugt</tt>: unordered or greater than </li>
4224 <li><tt>uge</tt>: unordered or greater than or equal</li>
4225 <li><tt>ult</tt>: unordered or less than </li>
4226 <li><tt>ule</tt>: unordered or less than or equal</li>
4227 <li><tt>une</tt>: unordered or not equal</li>
4228 <li><tt>uno</tt>: unordered (either nans)</li>
4229 <li><tt>true</tt>: no comparison, always returns true</li>
4231 <p><i>Ordered</i> means that neither operand is a QNAN while
4232 <i>unordered</i> means that either operand may be a QNAN.</p>
4233 <p>Each of <tt>val1</tt> and <tt>val2</tt> arguments must be
4234 either a <a href="#t_floating">floating point</a> type
4235 or a <a href="#t_vector">vector</a> of floating point type.
4236 They must have identical types.</p>
4238 <p>The '<tt>fcmp</tt>' instruction compares <tt>op1</tt> and <tt>op2</tt>
4239 according to the condition code given as <tt>cond</tt>.
4240 If the operands are vectors, then the vectors are compared
4242 Each comparison performed
4243 always yields an <a href="#t_primitive">i1</a> result, as follows:</p>
4245 <li><tt>false</tt>: always yields <tt>false</tt>, regardless of operands.</li>
4246 <li><tt>oeq</tt>: yields <tt>true</tt> if both operands are not a QNAN and
4247 <tt>op1</tt> is equal to <tt>op2</tt>.</li>
4248 <li><tt>ogt</tt>: yields <tt>true</tt> if both operands are not a QNAN and
4249 <tt>op1</tt> is greather than <tt>op2</tt>.</li>
4250 <li><tt>oge</tt>: yields <tt>true</tt> if both operands are not a QNAN and
4251 <tt>op1</tt> is greater than or equal to <tt>op2</tt>.</li>
4252 <li><tt>olt</tt>: yields <tt>true</tt> if both operands are not a QNAN and
4253 <tt>op1</tt> is less than <tt>op2</tt>.</li>
4254 <li><tt>ole</tt>: yields <tt>true</tt> if both operands are not a QNAN and
4255 <tt>op1</tt> is less than or equal to <tt>op2</tt>.</li>
4256 <li><tt>one</tt>: yields <tt>true</tt> if both operands are not a QNAN and
4257 <tt>op1</tt> is not equal to <tt>op2</tt>.</li>
4258 <li><tt>ord</tt>: yields <tt>true</tt> if both operands are not a QNAN.</li>
4259 <li><tt>ueq</tt>: yields <tt>true</tt> if either operand is a QNAN or
4260 <tt>op1</tt> is equal to <tt>op2</tt>.</li>
4261 <li><tt>ugt</tt>: yields <tt>true</tt> if either operand is a QNAN or
4262 <tt>op1</tt> is greater than <tt>op2</tt>.</li>
4263 <li><tt>uge</tt>: yields <tt>true</tt> if either operand is a QNAN or
4264 <tt>op1</tt> is greater than or equal to <tt>op2</tt>.</li>
4265 <li><tt>ult</tt>: yields <tt>true</tt> if either operand is a QNAN or
4266 <tt>op1</tt> is less than <tt>op2</tt>.</li>
4267 <li><tt>ule</tt>: yields <tt>true</tt> if either operand is a QNAN or
4268 <tt>op1</tt> is less than or equal to <tt>op2</tt>.</li>
4269 <li><tt>une</tt>: yields <tt>true</tt> if either operand is a QNAN or
4270 <tt>op1</tt> is not equal to <tt>op2</tt>.</li>
4271 <li><tt>uno</tt>: yields <tt>true</tt> if either operand is a QNAN.</li>
4272 <li><tt>true</tt>: always yields <tt>true</tt>, regardless of operands.</li>
4276 <pre> <result> = fcmp oeq float 4.0, 5.0 <i>; yields: result=false</i>
4277 <result> = fcmp one float 4.0, 5.0 <i>; yields: result=true</i>
4278 <result> = fcmp olt float 4.0, 5.0 <i>; yields: result=true</i>
4279 <result> = fcmp ueq double 1.0, 2.0 <i>; yields: result=false</i>
4282 <p>Note that the code generator does not yet support vector types with
4283 the <tt>fcmp</tt> instruction.</p>
4287 <!-- _______________________________________________________________________ -->
4288 <div class="doc_subsubsection">
4289 <a name="i_vicmp">'<tt>vicmp</tt>' Instruction</a>
4291 <div class="doc_text">
4293 <pre> <result> = vicmp <cond> <ty> <op1>, <op2> <i>; yields {ty}:result</i>
4296 <p>The '<tt>vicmp</tt>' instruction returns an integer vector value based on
4297 element-wise comparison of its two integer vector operands.</p>
4299 <p>The '<tt>vicmp</tt>' instruction takes three operands. The first operand is
4300 the condition code indicating the kind of comparison to perform. It is not
4301 a value, just a keyword. The possible condition code are:</p>
4303 <li><tt>eq</tt>: equal</li>
4304 <li><tt>ne</tt>: not equal </li>
4305 <li><tt>ugt</tt>: unsigned greater than</li>
4306 <li><tt>uge</tt>: unsigned greater or equal</li>
4307 <li><tt>ult</tt>: unsigned less than</li>
4308 <li><tt>ule</tt>: unsigned less or equal</li>
4309 <li><tt>sgt</tt>: signed greater than</li>
4310 <li><tt>sge</tt>: signed greater or equal</li>
4311 <li><tt>slt</tt>: signed less than</li>
4312 <li><tt>sle</tt>: signed less or equal</li>
4314 <p>The remaining two arguments must be <a href="#t_vector">vector</a> or
4315 <a href="#t_integer">integer</a> typed. They must also be identical types.</p>
4317 <p>The '<tt>vicmp</tt>' instruction compares <tt>op1</tt> and <tt>op2</tt>
4318 according to the condition code given as <tt>cond</tt>. The comparison yields a
4319 <a href="#t_vector">vector</a> of <a href="#t_integer">integer</a> result, of
4320 identical type as the values being compared. The most significant bit in each
4321 element is 1 if the element-wise comparison evaluates to true, and is 0
4322 otherwise. All other bits of the result are undefined. The condition codes
4323 are evaluated identically to the <a href="#i_icmp">'<tt>icmp</tt>'
4324 instruction</a>.</p>
4328 <result> = vicmp eq <2 x i32> < i32 4, i32 0>, < i32 5, i32 0> <i>; yields: result=<2 x i32> < i32 0, i32 -1 ></i>
4329 <result> = vicmp ult <2 x i8 > < i8 1, i8 2>, < i8 2, i8 2 > <i>; yields: result=<2 x i8> < i8 -1, i8 0 ></i>
4333 <!-- _______________________________________________________________________ -->
4334 <div class="doc_subsubsection">
4335 <a name="i_vfcmp">'<tt>vfcmp</tt>' Instruction</a>
4337 <div class="doc_text">
4339 <pre> <result> = vfcmp <cond> <ty> <op1>, <op2></pre>
4341 <p>The '<tt>vfcmp</tt>' instruction returns an integer vector value based on
4342 element-wise comparison of its two floating point vector operands. The output
4343 elements have the same width as the input elements.</p>
4345 <p>The '<tt>vfcmp</tt>' instruction takes three operands. The first operand is
4346 the condition code indicating the kind of comparison to perform. It is not
4347 a value, just a keyword. The possible condition code are:</p>
4349 <li><tt>false</tt>: no comparison, always returns false</li>
4350 <li><tt>oeq</tt>: ordered and equal</li>
4351 <li><tt>ogt</tt>: ordered and greater than </li>
4352 <li><tt>oge</tt>: ordered and greater than or equal</li>
4353 <li><tt>olt</tt>: ordered and less than </li>
4354 <li><tt>ole</tt>: ordered and less than or equal</li>
4355 <li><tt>one</tt>: ordered and not equal</li>
4356 <li><tt>ord</tt>: ordered (no nans)</li>
4357 <li><tt>ueq</tt>: unordered or equal</li>
4358 <li><tt>ugt</tt>: unordered or greater than </li>
4359 <li><tt>uge</tt>: unordered or greater than or equal</li>
4360 <li><tt>ult</tt>: unordered or less than </li>
4361 <li><tt>ule</tt>: unordered or less than or equal</li>
4362 <li><tt>une</tt>: unordered or not equal</li>
4363 <li><tt>uno</tt>: unordered (either nans)</li>
4364 <li><tt>true</tt>: no comparison, always returns true</li>
4366 <p>The remaining two arguments must be <a href="#t_vector">vector</a> of
4367 <a href="#t_floating">floating point</a> typed. They must also be identical
4370 <p>The '<tt>vfcmp</tt>' instruction compares <tt>op1</tt> and <tt>op2</tt>
4371 according to the condition code given as <tt>cond</tt>. The comparison yields a
4372 <a href="#t_vector">vector</a> of <a href="#t_integer">integer</a> result, with
4373 an identical number of elements as the values being compared, and each element
4374 having identical with to the width of the floating point elements. The most
4375 significant bit in each element is 1 if the element-wise comparison evaluates to
4376 true, and is 0 otherwise. All other bits of the result are undefined. The
4377 condition codes are evaluated identically to the
4378 <a href="#i_fcmp">'<tt>fcmp</tt>' instruction</a>.</p>
4382 <i>; yields: result=<2 x i32> < i32 0, i32 -1 ></i>
4383 <result> = vfcmp oeq <2 x float> < float 4, float 0 >, < float 5, float 0 >
4385 <i>; yields: result=<2 x i64> < i64 -1, i64 0 ></i>
4386 <result> = vfcmp ult <2 x double> < double 1, double 2 >, < double 2, double 2>
4390 <!-- _______________________________________________________________________ -->
4391 <div class="doc_subsubsection">
4392 <a name="i_phi">'<tt>phi</tt>' Instruction</a>
4395 <div class="doc_text">
4399 <pre> <result> = phi <ty> [ <val0>, <label0>], ...<br></pre>
4401 <p>The '<tt>phi</tt>' instruction is used to implement the φ node in
4402 the SSA graph representing the function.</p>
4405 <p>The type of the incoming values is specified with the first type
4406 field. After this, the '<tt>phi</tt>' instruction takes a list of pairs
4407 as arguments, with one pair for each predecessor basic block of the
4408 current block. Only values of <a href="#t_firstclass">first class</a>
4409 type may be used as the value arguments to the PHI node. Only labels
4410 may be used as the label arguments.</p>
4412 <p>There must be no non-phi instructions between the start of a basic
4413 block and the PHI instructions: i.e. PHI instructions must be first in
4418 <p>At runtime, the '<tt>phi</tt>' instruction logically takes on the value
4419 specified by the pair corresponding to the predecessor basic block that executed
4420 just prior to the current block.</p>
4424 Loop: ; Infinite loop that counts from 0 on up...
4425 %indvar = phi i32 [ 0, %LoopHeader ], [ %nextindvar, %Loop ]
4426 %nextindvar = add i32 %indvar, 1
4431 <!-- _______________________________________________________________________ -->
4432 <div class="doc_subsubsection">
4433 <a name="i_select">'<tt>select</tt>' Instruction</a>
4436 <div class="doc_text">
4441 <result> = select <i>selty</i> <cond>, <ty> <val1>, <ty> <val2> <i>; yields ty</i>
4443 <i>selty</i> is either i1 or {<N x i1>}
4449 The '<tt>select</tt>' instruction is used to choose one value based on a
4450 condition, without branching.
4457 The '<tt>select</tt>' instruction requires an 'i1' value or
4458 a vector of 'i1' values indicating the
4459 condition, and two values of the same <a href="#t_firstclass">first class</a>
4460 type. If the val1/val2 are vectors and
4461 the condition is a scalar, then entire vectors are selected, not
4462 individual elements.
4468 If the condition is an i1 and it evaluates to 1, the instruction returns the first
4469 value argument; otherwise, it returns the second value argument.
4472 If the condition is a vector of i1, then the value arguments must
4473 be vectors of the same size, and the selection is done element
4480 %X = select i1 true, i8 17, i8 42 <i>; yields i8:17</i>
4483 <p>Note that the code generator does not yet support conditions
4484 with vector type.</p>
4489 <!-- _______________________________________________________________________ -->
4490 <div class="doc_subsubsection">
4491 <a name="i_call">'<tt>call</tt>' Instruction</a>
4494 <div class="doc_text">
4498 <result> = [tail] call [<a href="#callingconv">cconv</a>] [<a href="#paramattrs">ret attrs</a>] <ty> [<fnty>*] <fnptrval>(<function args>) [<a href="#fnattrs">fn attrs</a>]
4503 <p>The '<tt>call</tt>' instruction represents a simple function call.</p>
4507 <p>This instruction requires several arguments:</p>
4511 <p>The optional "tail" marker indicates whether the callee function accesses
4512 any allocas or varargs in the caller. If the "tail" marker is present, the
4513 function call is eligible for tail call optimization. Note that calls may
4514 be marked "tail" even if they do not occur before a <a
4515 href="#i_ret"><tt>ret</tt></a> instruction.</p>
4518 <p>The optional "cconv" marker indicates which <a href="#callingconv">calling
4519 convention</a> the call should use. If none is specified, the call defaults
4520 to using C calling conventions.</p>
4524 <p>The optional <a href="#paramattrs">Parameter Attributes</a> list for
4525 return values. Only '<tt>zeroext</tt>', '<tt>signext</tt>',
4526 and '<tt>inreg</tt>' attributes are valid here.</p>
4530 <p>'<tt>ty</tt>': the type of the call instruction itself which is also
4531 the type of the return value. Functions that return no value are marked
4532 <tt><a href="#t_void">void</a></tt>.</p>
4535 <p>'<tt>fnty</tt>': shall be the signature of the pointer to function
4536 value being invoked. The argument types must match the types implied by
4537 this signature. This type can be omitted if the function is not varargs
4538 and if the function type does not return a pointer to a function.</p>
4541 <p>'<tt>fnptrval</tt>': An LLVM value containing a pointer to a function to
4542 be invoked. In most cases, this is a direct function invocation, but
4543 indirect <tt>call</tt>s are just as possible, calling an arbitrary pointer
4544 to function value.</p>
4547 <p>'<tt>function args</tt>': argument list whose types match the
4548 function signature argument types. All arguments must be of
4549 <a href="#t_firstclass">first class</a> type. If the function signature
4550 indicates the function accepts a variable number of arguments, the extra
4551 arguments can be specified.</p>
4554 <p>The optional <a href="#fnattrs">function attributes</a> list. Only
4555 '<tt>noreturn</tt>', '<tt>nounwind</tt>', '<tt>readonly</tt>' and
4556 '<tt>readnone</tt>' attributes are valid here.</p>
4562 <p>The '<tt>call</tt>' instruction is used to cause control flow to
4563 transfer to a specified function, with its incoming arguments bound to
4564 the specified values. Upon a '<tt><a href="#i_ret">ret</a></tt>'
4565 instruction in the called function, control flow continues with the
4566 instruction after the function call, and the return value of the
4567 function is bound to the result argument.</p>
4572 %retval = call i32 @test(i32 %argc)
4573 call i32 (i8 *, ...)* @printf(i8 * %msg, i32 12, i8 42) <i>; yields i32</i>
4574 %X = tail call i32 @foo() <i>; yields i32</i>
4575 %Y = tail call <a href="#callingconv">fastcc</a> i32 @foo() <i>; yields i32</i>
4576 call void %foo(i8 97 signext)
4578 %struct.A = type { i32, i8 }
4579 %r = call %struct.A @foo() <i>; yields { 32, i8 }</i>
4580 %gr = extractvalue %struct.A %r, 0 <i>; yields i32</i>
4581 %gr1 = extractvalue %struct.A %r, 1 <i>; yields i8</i>
4582 %Z = call void @foo() noreturn <i>; indicates that %foo never returns normally</i>
4583 %ZZ = call zeroext i32 @bar() <i>; Return value is %zero extended</i>
4588 <!-- _______________________________________________________________________ -->
4589 <div class="doc_subsubsection">
4590 <a name="i_va_arg">'<tt>va_arg</tt>' Instruction</a>
4593 <div class="doc_text">
4598 <resultval> = va_arg <va_list*> <arglist>, <argty>
4603 <p>The '<tt>va_arg</tt>' instruction is used to access arguments passed through
4604 the "variable argument" area of a function call. It is used to implement the
4605 <tt>va_arg</tt> macro in C.</p>
4609 <p>This instruction takes a <tt>va_list*</tt> value and the type of
4610 the argument. It returns a value of the specified argument type and
4611 increments the <tt>va_list</tt> to point to the next argument. The
4612 actual type of <tt>va_list</tt> is target specific.</p>
4616 <p>The '<tt>va_arg</tt>' instruction loads an argument of the specified
4617 type from the specified <tt>va_list</tt> and causes the
4618 <tt>va_list</tt> to point to the next argument. For more information,
4619 see the variable argument handling <a href="#int_varargs">Intrinsic
4622 <p>It is legal for this instruction to be called in a function which does not
4623 take a variable number of arguments, for example, the <tt>vfprintf</tt>
4626 <p><tt>va_arg</tt> is an LLVM instruction instead of an <a
4627 href="#intrinsics">intrinsic function</a> because it takes a type as an
4632 <p>See the <a href="#int_varargs">variable argument processing</a> section.</p>
4634 <p>Note that the code generator does not yet fully support va_arg
4635 on many targets. Also, it does not currently support va_arg with
4636 aggregate types on any target.</p>
4640 <!-- *********************************************************************** -->
4641 <div class="doc_section"> <a name="intrinsics">Intrinsic Functions</a> </div>
4642 <!-- *********************************************************************** -->
4644 <div class="doc_text">
4646 <p>LLVM supports the notion of an "intrinsic function". These functions have
4647 well known names and semantics and are required to follow certain restrictions.
4648 Overall, these intrinsics represent an extension mechanism for the LLVM
4649 language that does not require changing all of the transformations in LLVM when
4650 adding to the language (or the bitcode reader/writer, the parser, etc...).</p>
4652 <p>Intrinsic function names must all start with an "<tt>llvm.</tt>" prefix. This
4653 prefix is reserved in LLVM for intrinsic names; thus, function names may not
4654 begin with this prefix. Intrinsic functions must always be external functions:
4655 you cannot define the body of intrinsic functions. Intrinsic functions may
4656 only be used in call or invoke instructions: it is illegal to take the address
4657 of an intrinsic function. Additionally, because intrinsic functions are part
4658 of the LLVM language, it is required if any are added that they be documented
4661 <p>Some intrinsic functions can be overloaded, i.e., the intrinsic represents
4662 a family of functions that perform the same operation but on different data
4663 types. Because LLVM can represent over 8 million different integer types,
4664 overloading is used commonly to allow an intrinsic function to operate on any
4665 integer type. One or more of the argument types or the result type can be
4666 overloaded to accept any integer type. Argument types may also be defined as
4667 exactly matching a previous argument's type or the result type. This allows an
4668 intrinsic function which accepts multiple arguments, but needs all of them to
4669 be of the same type, to only be overloaded with respect to a single argument or
4672 <p>Overloaded intrinsics will have the names of its overloaded argument types
4673 encoded into its function name, each preceded by a period. Only those types
4674 which are overloaded result in a name suffix. Arguments whose type is matched
4675 against another type do not. For example, the <tt>llvm.ctpop</tt> function can
4676 take an integer of any width and returns an integer of exactly the same integer
4677 width. This leads to a family of functions such as
4678 <tt>i8 @llvm.ctpop.i8(i8 %val)</tt> and <tt>i29 @llvm.ctpop.i29(i29 %val)</tt>.
4679 Only one type, the return type, is overloaded, and only one type suffix is
4680 required. Because the argument's type is matched against the return type, it
4681 does not require its own name suffix.</p>
4683 <p>To learn how to add an intrinsic function, please see the
4684 <a href="ExtendingLLVM.html">Extending LLVM Guide</a>.
4689 <!-- ======================================================================= -->
4690 <div class="doc_subsection">
4691 <a name="int_varargs">Variable Argument Handling Intrinsics</a>
4694 <div class="doc_text">
4696 <p>Variable argument support is defined in LLVM with the <a
4697 href="#i_va_arg"><tt>va_arg</tt></a> instruction and these three
4698 intrinsic functions. These functions are related to the similarly
4699 named macros defined in the <tt><stdarg.h></tt> header file.</p>
4701 <p>All of these functions operate on arguments that use a
4702 target-specific value type "<tt>va_list</tt>". The LLVM assembly
4703 language reference manual does not define what this type is, so all
4704 transformations should be prepared to handle these functions regardless of
4707 <p>This example shows how the <a href="#i_va_arg"><tt>va_arg</tt></a>
4708 instruction and the variable argument handling intrinsic functions are
4711 <div class="doc_code">
4713 define i32 @test(i32 %X, ...) {
4714 ; Initialize variable argument processing
4716 %ap2 = bitcast i8** %ap to i8*
4717 call void @llvm.va_start(i8* %ap2)
4719 ; Read a single integer argument
4720 %tmp = va_arg i8** %ap, i32
4722 ; Demonstrate usage of llvm.va_copy and llvm.va_end
4724 %aq2 = bitcast i8** %aq to i8*
4725 call void @llvm.va_copy(i8* %aq2, i8* %ap2)
4726 call void @llvm.va_end(i8* %aq2)
4728 ; Stop processing of arguments.
4729 call void @llvm.va_end(i8* %ap2)
4733 declare void @llvm.va_start(i8*)
4734 declare void @llvm.va_copy(i8*, i8*)
4735 declare void @llvm.va_end(i8*)
4741 <!-- _______________________________________________________________________ -->
4742 <div class="doc_subsubsection">
4743 <a name="int_va_start">'<tt>llvm.va_start</tt>' Intrinsic</a>
4747 <div class="doc_text">
4749 <pre> declare void %llvm.va_start(i8* <arglist>)<br></pre>
4751 <p>The '<tt>llvm.va_start</tt>' intrinsic initializes
4752 <tt>*<arglist></tt> for subsequent use by <tt><a
4753 href="#i_va_arg">va_arg</a></tt>.</p>
4757 <p>The argument is a pointer to a <tt>va_list</tt> element to initialize.</p>
4761 <p>The '<tt>llvm.va_start</tt>' intrinsic works just like the <tt>va_start</tt>
4762 macro available in C. In a target-dependent way, it initializes the
4763 <tt>va_list</tt> element to which the argument points, so that the next call to
4764 <tt>va_arg</tt> will produce the first variable argument passed to the function.
4765 Unlike the C <tt>va_start</tt> macro, this intrinsic does not need to know the
4766 last argument of the function as the compiler can figure that out.</p>
4770 <!-- _______________________________________________________________________ -->
4771 <div class="doc_subsubsection">
4772 <a name="int_va_end">'<tt>llvm.va_end</tt>' Intrinsic</a>
4775 <div class="doc_text">
4777 <pre> declare void @llvm.va_end(i8* <arglist>)<br></pre>
4780 <p>The '<tt>llvm.va_end</tt>' intrinsic destroys <tt>*<arglist></tt>,
4781 which has been initialized previously with <tt><a href="#int_va_start">llvm.va_start</a></tt>
4782 or <tt><a href="#i_va_copy">llvm.va_copy</a></tt>.</p>
4786 <p>The argument is a pointer to a <tt>va_list</tt> to destroy.</p>
4790 <p>The '<tt>llvm.va_end</tt>' intrinsic works just like the <tt>va_end</tt>
4791 macro available in C. In a target-dependent way, it destroys the
4792 <tt>va_list</tt> element to which the argument points. Calls to <a
4793 href="#int_va_start"><tt>llvm.va_start</tt></a> and <a href="#int_va_copy">
4794 <tt>llvm.va_copy</tt></a> must be matched exactly with calls to
4795 <tt>llvm.va_end</tt>.</p>
4799 <!-- _______________________________________________________________________ -->
4800 <div class="doc_subsubsection">
4801 <a name="int_va_copy">'<tt>llvm.va_copy</tt>' Intrinsic</a>
4804 <div class="doc_text">
4809 declare void @llvm.va_copy(i8* <destarglist>, i8* <srcarglist>)
4814 <p>The '<tt>llvm.va_copy</tt>' intrinsic copies the current argument position
4815 from the source argument list to the destination argument list.</p>
4819 <p>The first argument is a pointer to a <tt>va_list</tt> element to initialize.
4820 The second argument is a pointer to a <tt>va_list</tt> element to copy from.</p>
4825 <p>The '<tt>llvm.va_copy</tt>' intrinsic works just like the <tt>va_copy</tt>
4826 macro available in C. In a target-dependent way, it copies the source
4827 <tt>va_list</tt> element into the destination <tt>va_list</tt> element. This
4828 intrinsic is necessary because the <tt><a href="#int_va_start">
4829 llvm.va_start</a></tt> intrinsic may be arbitrarily complex and require, for
4830 example, memory allocation.</p>
4834 <!-- ======================================================================= -->
4835 <div class="doc_subsection">
4836 <a name="int_gc">Accurate Garbage Collection Intrinsics</a>
4839 <div class="doc_text">
4842 LLVM support for <a href="GarbageCollection.html">Accurate Garbage
4843 Collection</a> (GC) requires the implementation and generation of these
4845 These intrinsics allow identification of <a href="#int_gcroot">GC roots on the
4846 stack</a>, as well as garbage collector implementations that require <a
4847 href="#int_gcread">read</a> and <a href="#int_gcwrite">write</a> barriers.
4848 Front-ends for type-safe garbage collected languages should generate these
4849 intrinsics to make use of the LLVM garbage collectors. For more details, see <a
4850 href="GarbageCollection.html">Accurate Garbage Collection with LLVM</a>.
4853 <p>The garbage collection intrinsics only operate on objects in the generic
4854 address space (address space zero).</p>
4858 <!-- _______________________________________________________________________ -->
4859 <div class="doc_subsubsection">
4860 <a name="int_gcroot">'<tt>llvm.gcroot</tt>' Intrinsic</a>
4863 <div class="doc_text">
4868 declare void @llvm.gcroot(i8** %ptrloc, i8* %metadata)
4873 <p>The '<tt>llvm.gcroot</tt>' intrinsic declares the existence of a GC root to
4874 the code generator, and allows some metadata to be associated with it.</p>
4878 <p>The first argument specifies the address of a stack object that contains the
4879 root pointer. The second pointer (which must be either a constant or a global
4880 value address) contains the meta-data to be associated with the root.</p>
4884 <p>At runtime, a call to this intrinsic stores a null pointer into the "ptrloc"
4885 location. At compile-time, the code generator generates information to allow
4886 the runtime to find the pointer at GC safe points. The '<tt>llvm.gcroot</tt>'
4887 intrinsic may only be used in a function which <a href="#gc">specifies a GC
4893 <!-- _______________________________________________________________________ -->
4894 <div class="doc_subsubsection">
4895 <a name="int_gcread">'<tt>llvm.gcread</tt>' Intrinsic</a>
4898 <div class="doc_text">
4903 declare i8* @llvm.gcread(i8* %ObjPtr, i8** %Ptr)
4908 <p>The '<tt>llvm.gcread</tt>' intrinsic identifies reads of references from heap
4909 locations, allowing garbage collector implementations that require read
4914 <p>The second argument is the address to read from, which should be an address
4915 allocated from the garbage collector. The first object is a pointer to the
4916 start of the referenced object, if needed by the language runtime (otherwise
4921 <p>The '<tt>llvm.gcread</tt>' intrinsic has the same semantics as a load
4922 instruction, but may be replaced with substantially more complex code by the
4923 garbage collector runtime, as needed. The '<tt>llvm.gcread</tt>' intrinsic
4924 may only be used in a function which <a href="#gc">specifies a GC
4930 <!-- _______________________________________________________________________ -->
4931 <div class="doc_subsubsection">
4932 <a name="int_gcwrite">'<tt>llvm.gcwrite</tt>' Intrinsic</a>
4935 <div class="doc_text">
4940 declare void @llvm.gcwrite(i8* %P1, i8* %Obj, i8** %P2)
4945 <p>The '<tt>llvm.gcwrite</tt>' intrinsic identifies writes of references to heap
4946 locations, allowing garbage collector implementations that require write
4947 barriers (such as generational or reference counting collectors).</p>
4951 <p>The first argument is the reference to store, the second is the start of the
4952 object to store it to, and the third is the address of the field of Obj to
4953 store to. If the runtime does not require a pointer to the object, Obj may be
4958 <p>The '<tt>llvm.gcwrite</tt>' intrinsic has the same semantics as a store
4959 instruction, but may be replaced with substantially more complex code by the
4960 garbage collector runtime, as needed. The '<tt>llvm.gcwrite</tt>' intrinsic
4961 may only be used in a function which <a href="#gc">specifies a GC
4968 <!-- ======================================================================= -->
4969 <div class="doc_subsection">
4970 <a name="int_codegen">Code Generator Intrinsics</a>
4973 <div class="doc_text">
4975 These intrinsics are provided by LLVM to expose special features that may only
4976 be implemented with code generator support.
4981 <!-- _______________________________________________________________________ -->
4982 <div class="doc_subsubsection">
4983 <a name="int_returnaddress">'<tt>llvm.returnaddress</tt>' Intrinsic</a>
4986 <div class="doc_text">
4990 declare i8 *@llvm.returnaddress(i32 <level>)
4996 The '<tt>llvm.returnaddress</tt>' intrinsic attempts to compute a
4997 target-specific value indicating the return address of the current function
4998 or one of its callers.
5004 The argument to this intrinsic indicates which function to return the address
5005 for. Zero indicates the calling function, one indicates its caller, etc. The
5006 argument is <b>required</b> to be a constant integer value.
5012 The '<tt>llvm.returnaddress</tt>' intrinsic either returns a pointer indicating
5013 the return address of the specified call frame, or zero if it cannot be
5014 identified. The value returned by this intrinsic is likely to be incorrect or 0
5015 for arguments other than zero, so it should only be used for debugging purposes.
5019 Note that calling this intrinsic does not prevent function inlining or other
5020 aggressive transformations, so the value returned may not be that of the obvious
5021 source-language caller.
5026 <!-- _______________________________________________________________________ -->
5027 <div class="doc_subsubsection">
5028 <a name="int_frameaddress">'<tt>llvm.frameaddress</tt>' Intrinsic</a>
5031 <div class="doc_text">
5035 declare i8 *@llvm.frameaddress(i32 <level>)
5041 The '<tt>llvm.frameaddress</tt>' intrinsic attempts to return the
5042 target-specific frame pointer value for the specified stack frame.
5048 The argument to this intrinsic indicates which function to return the frame
5049 pointer for. Zero indicates the calling function, one indicates its caller,
5050 etc. The argument is <b>required</b> to be a constant integer value.
5056 The '<tt>llvm.frameaddress</tt>' intrinsic either returns a pointer indicating
5057 the frame address of the specified call frame, or zero if it cannot be
5058 identified. The value returned by this intrinsic is likely to be incorrect or 0
5059 for arguments other than zero, so it should only be used for debugging purposes.
5063 Note that calling this intrinsic does not prevent function inlining or other
5064 aggressive transformations, so the value returned may not be that of the obvious
5065 source-language caller.
5069 <!-- _______________________________________________________________________ -->
5070 <div class="doc_subsubsection">
5071 <a name="int_stacksave">'<tt>llvm.stacksave</tt>' Intrinsic</a>
5074 <div class="doc_text">
5078 declare i8 *@llvm.stacksave()
5084 The '<tt>llvm.stacksave</tt>' intrinsic is used to remember the current state of
5085 the function stack, for use with <a href="#int_stackrestore">
5086 <tt>llvm.stackrestore</tt></a>. This is useful for implementing language
5087 features like scoped automatic variable sized arrays in C99.
5093 This intrinsic returns a opaque pointer value that can be passed to <a
5094 href="#int_stackrestore"><tt>llvm.stackrestore</tt></a>. When an
5095 <tt>llvm.stackrestore</tt> intrinsic is executed with a value saved from
5096 <tt>llvm.stacksave</tt>, it effectively restores the state of the stack to the
5097 state it was in when the <tt>llvm.stacksave</tt> intrinsic executed. In
5098 practice, this pops any <a href="#i_alloca">alloca</a> blocks from the stack
5099 that were allocated after the <tt>llvm.stacksave</tt> was executed.
5104 <!-- _______________________________________________________________________ -->
5105 <div class="doc_subsubsection">
5106 <a name="int_stackrestore">'<tt>llvm.stackrestore</tt>' Intrinsic</a>
5109 <div class="doc_text">
5113 declare void @llvm.stackrestore(i8 * %ptr)
5119 The '<tt>llvm.stackrestore</tt>' intrinsic is used to restore the state of
5120 the function stack to the state it was in when the corresponding <a
5121 href="#int_stacksave"><tt>llvm.stacksave</tt></a> intrinsic executed. This is
5122 useful for implementing language features like scoped automatic variable sized
5129 See the description for <a href="#int_stacksave"><tt>llvm.stacksave</tt></a>.
5135 <!-- _______________________________________________________________________ -->
5136 <div class="doc_subsubsection">
5137 <a name="int_prefetch">'<tt>llvm.prefetch</tt>' Intrinsic</a>
5140 <div class="doc_text">
5144 declare void @llvm.prefetch(i8* <address>, i32 <rw>, i32 <locality>)
5151 The '<tt>llvm.prefetch</tt>' intrinsic is a hint to the code generator to insert
5152 a prefetch instruction if supported; otherwise, it is a noop. Prefetches have
5154 effect on the behavior of the program but can change its performance
5161 <tt>address</tt> is the address to be prefetched, <tt>rw</tt> is the specifier
5162 determining if the fetch should be for a read (0) or write (1), and
5163 <tt>locality</tt> is a temporal locality specifier ranging from (0) - no
5164 locality, to (3) - extremely local keep in cache. The <tt>rw</tt> and
5165 <tt>locality</tt> arguments must be constant integers.
5171 This intrinsic does not modify the behavior of the program. In particular,
5172 prefetches cannot trap and do not produce a value. On targets that support this
5173 intrinsic, the prefetch can provide hints to the processor cache for better
5179 <!-- _______________________________________________________________________ -->
5180 <div class="doc_subsubsection">
5181 <a name="int_pcmarker">'<tt>llvm.pcmarker</tt>' Intrinsic</a>
5184 <div class="doc_text">
5188 declare void @llvm.pcmarker(i32 <id>)
5195 The '<tt>llvm.pcmarker</tt>' intrinsic is a method to export a Program Counter
5197 code to simulators and other tools. The method is target specific, but it is
5198 expected that the marker will use exported symbols to transmit the PC of the
5200 The marker makes no guarantees that it will remain with any specific instruction
5201 after optimizations. It is possible that the presence of a marker will inhibit
5202 optimizations. The intended use is to be inserted after optimizations to allow
5203 correlations of simulation runs.
5209 <tt>id</tt> is a numerical id identifying the marker.
5215 This intrinsic does not modify the behavior of the program. Backends that do not
5216 support this intrinisic may ignore it.
5221 <!-- _______________________________________________________________________ -->
5222 <div class="doc_subsubsection">
5223 <a name="int_readcyclecounter">'<tt>llvm.readcyclecounter</tt>' Intrinsic</a>
5226 <div class="doc_text">
5230 declare i64 @llvm.readcyclecounter( )
5237 The '<tt>llvm.readcyclecounter</tt>' intrinsic provides access to the cycle
5238 counter register (or similar low latency, high accuracy clocks) on those targets
5239 that support it. On X86, it should map to RDTSC. On Alpha, it should map to RPCC.
5240 As the backing counters overflow quickly (on the order of 9 seconds on alpha), this
5241 should only be used for small timings.
5247 When directly supported, reading the cycle counter should not modify any memory.
5248 Implementations are allowed to either return a application specific value or a
5249 system wide value. On backends without support, this is lowered to a constant 0.
5254 <!-- ======================================================================= -->
5255 <div class="doc_subsection">
5256 <a name="int_libc">Standard C Library Intrinsics</a>
5259 <div class="doc_text">
5261 LLVM provides intrinsics for a few important standard C library functions.
5262 These intrinsics allow source-language front-ends to pass information about the
5263 alignment of the pointer arguments to the code generator, providing opportunity
5264 for more efficient code generation.
5269 <!-- _______________________________________________________________________ -->
5270 <div class="doc_subsubsection">
5271 <a name="int_memcpy">'<tt>llvm.memcpy</tt>' Intrinsic</a>
5274 <div class="doc_text">
5277 <p>This is an overloaded intrinsic. You can use llvm.memcpy on any integer bit
5278 width. Not all targets support all bit widths however.</p>
5280 declare void @llvm.memcpy.i8(i8 * <dest>, i8 * <src>,
5281 i8 <len>, i32 <align>)
5282 declare void @llvm.memcpy.i16(i8 * <dest>, i8 * <src>,
5283 i16 <len>, i32 <align>)
5284 declare void @llvm.memcpy.i32(i8 * <dest>, i8 * <src>,
5285 i32 <len>, i32 <align>)
5286 declare void @llvm.memcpy.i64(i8 * <dest>, i8 * <src>,
5287 i64 <len>, i32 <align>)
5293 The '<tt>llvm.memcpy.*</tt>' intrinsics copy a block of memory from the source
5294 location to the destination location.
5298 Note that, unlike the standard libc function, the <tt>llvm.memcpy.*</tt>
5299 intrinsics do not return a value, and takes an extra alignment argument.
5305 The first argument is a pointer to the destination, the second is a pointer to
5306 the source. The third argument is an integer argument
5307 specifying the number of bytes to copy, and the fourth argument is the alignment
5308 of the source and destination locations.
5312 If the call to this intrinisic has an alignment value that is not 0 or 1, then
5313 the caller guarantees that both the source and destination pointers are aligned
5320 The '<tt>llvm.memcpy.*</tt>' intrinsics copy a block of memory from the source
5321 location to the destination location, which are not allowed to overlap. It
5322 copies "len" bytes of memory over. If the argument is known to be aligned to
5323 some boundary, this can be specified as the fourth argument, otherwise it should
5329 <!-- _______________________________________________________________________ -->
5330 <div class="doc_subsubsection">
5331 <a name="int_memmove">'<tt>llvm.memmove</tt>' Intrinsic</a>
5334 <div class="doc_text">
5337 <p>This is an overloaded intrinsic. You can use llvm.memmove on any integer bit
5338 width. Not all targets support all bit widths however.</p>
5340 declare void @llvm.memmove.i8(i8 * <dest>, i8 * <src>,
5341 i8 <len>, i32 <align>)
5342 declare void @llvm.memmove.i16(i8 * <dest>, i8 * <src>,
5343 i16 <len>, i32 <align>)
5344 declare void @llvm.memmove.i32(i8 * <dest>, i8 * <src>,
5345 i32 <len>, i32 <align>)
5346 declare void @llvm.memmove.i64(i8 * <dest>, i8 * <src>,
5347 i64 <len>, i32 <align>)
5353 The '<tt>llvm.memmove.*</tt>' intrinsics move a block of memory from the source
5354 location to the destination location. It is similar to the
5355 '<tt>llvm.memcpy</tt>' intrinsic but allows the two memory locations to overlap.
5359 Note that, unlike the standard libc function, the <tt>llvm.memmove.*</tt>
5360 intrinsics do not return a value, and takes an extra alignment argument.
5366 The first argument is a pointer to the destination, the second is a pointer to
5367 the source. The third argument is an integer argument
5368 specifying the number of bytes to copy, and the fourth argument is the alignment
5369 of the source and destination locations.
5373 If the call to this intrinisic has an alignment value that is not 0 or 1, then
5374 the caller guarantees that the source and destination pointers are aligned to
5381 The '<tt>llvm.memmove.*</tt>' intrinsics copy a block of memory from the source
5382 location to the destination location, which may overlap. It
5383 copies "len" bytes of memory over. If the argument is known to be aligned to
5384 some boundary, this can be specified as the fourth argument, otherwise it should
5390 <!-- _______________________________________________________________________ -->
5391 <div class="doc_subsubsection">
5392 <a name="int_memset">'<tt>llvm.memset.*</tt>' Intrinsics</a>
5395 <div class="doc_text">
5398 <p>This is an overloaded intrinsic. You can use llvm.memset on any integer bit
5399 width. Not all targets support all bit widths however.</p>
5401 declare void @llvm.memset.i8(i8 * <dest>, i8 <val>,
5402 i8 <len>, i32 <align>)
5403 declare void @llvm.memset.i16(i8 * <dest>, i8 <val>,
5404 i16 <len>, i32 <align>)
5405 declare void @llvm.memset.i32(i8 * <dest>, i8 <val>,
5406 i32 <len>, i32 <align>)
5407 declare void @llvm.memset.i64(i8 * <dest>, i8 <val>,
5408 i64 <len>, i32 <align>)
5414 The '<tt>llvm.memset.*</tt>' intrinsics fill a block of memory with a particular
5419 Note that, unlike the standard libc function, the <tt>llvm.memset</tt> intrinsic
5420 does not return a value, and takes an extra alignment argument.
5426 The first argument is a pointer to the destination to fill, the second is the
5427 byte value to fill it with, the third argument is an integer
5428 argument specifying the number of bytes to fill, and the fourth argument is the
5429 known alignment of destination location.
5433 If the call to this intrinisic has an alignment value that is not 0 or 1, then
5434 the caller guarantees that the destination pointer is aligned to that boundary.
5440 The '<tt>llvm.memset.*</tt>' intrinsics fill "len" bytes of memory starting at
5442 destination location. If the argument is known to be aligned to some boundary,
5443 this can be specified as the fourth argument, otherwise it should be set to 0 or
5449 <!-- _______________________________________________________________________ -->
5450 <div class="doc_subsubsection">
5451 <a name="int_sqrt">'<tt>llvm.sqrt.*</tt>' Intrinsic</a>
5454 <div class="doc_text">
5457 <p>This is an overloaded intrinsic. You can use <tt>llvm.sqrt</tt> on any
5458 floating point or vector of floating point type. Not all targets support all
5461 declare float @llvm.sqrt.f32(float %Val)
5462 declare double @llvm.sqrt.f64(double %Val)
5463 declare x86_fp80 @llvm.sqrt.f80(x86_fp80 %Val)
5464 declare fp128 @llvm.sqrt.f128(fp128 %Val)
5465 declare ppc_fp128 @llvm.sqrt.ppcf128(ppc_fp128 %Val)
5471 The '<tt>llvm.sqrt</tt>' intrinsics return the sqrt of the specified operand,
5472 returning the same value as the libm '<tt>sqrt</tt>' functions would. Unlike
5473 <tt>sqrt</tt> in libm, however, <tt>llvm.sqrt</tt> has undefined behavior for
5474 negative numbers other than -0.0 (which allows for better optimization, because
5475 there is no need to worry about errno being set). <tt>llvm.sqrt(-0.0)</tt> is
5476 defined to return -0.0 like IEEE sqrt.
5482 The argument and return value are floating point numbers of the same type.
5488 This function returns the sqrt of the specified operand if it is a nonnegative
5489 floating point number.
5493 <!-- _______________________________________________________________________ -->
5494 <div class="doc_subsubsection">
5495 <a name="int_powi">'<tt>llvm.powi.*</tt>' Intrinsic</a>
5498 <div class="doc_text">
5501 <p>This is an overloaded intrinsic. You can use <tt>llvm.powi</tt> on any
5502 floating point or vector of floating point type. Not all targets support all
5505 declare float @llvm.powi.f32(float %Val, i32 %power)
5506 declare double @llvm.powi.f64(double %Val, i32 %power)
5507 declare x86_fp80 @llvm.powi.f80(x86_fp80 %Val, i32 %power)
5508 declare fp128 @llvm.powi.f128(fp128 %Val, i32 %power)
5509 declare ppc_fp128 @llvm.powi.ppcf128(ppc_fp128 %Val, i32 %power)
5515 The '<tt>llvm.powi.*</tt>' intrinsics return the first operand raised to the
5516 specified (positive or negative) power. The order of evaluation of
5517 multiplications is not defined. When a vector of floating point type is
5518 used, the second argument remains a scalar integer value.
5524 The second argument is an integer power, and the first is a value to raise to
5531 This function returns the first value raised to the second power with an
5532 unspecified sequence of rounding operations.</p>
5535 <!-- _______________________________________________________________________ -->
5536 <div class="doc_subsubsection">
5537 <a name="int_sin">'<tt>llvm.sin.*</tt>' Intrinsic</a>
5540 <div class="doc_text">
5543 <p>This is an overloaded intrinsic. You can use <tt>llvm.sin</tt> on any
5544 floating point or vector of floating point type. Not all targets support all
5547 declare float @llvm.sin.f32(float %Val)
5548 declare double @llvm.sin.f64(double %Val)
5549 declare x86_fp80 @llvm.sin.f80(x86_fp80 %Val)
5550 declare fp128 @llvm.sin.f128(fp128 %Val)
5551 declare ppc_fp128 @llvm.sin.ppcf128(ppc_fp128 %Val)
5557 The '<tt>llvm.sin.*</tt>' intrinsics return the sine of the operand.
5563 The argument and return value are floating point numbers of the same type.
5569 This function returns the sine of the specified operand, returning the
5570 same values as the libm <tt>sin</tt> functions would, and handles error
5571 conditions in the same way.</p>
5574 <!-- _______________________________________________________________________ -->
5575 <div class="doc_subsubsection">
5576 <a name="int_cos">'<tt>llvm.cos.*</tt>' Intrinsic</a>
5579 <div class="doc_text">
5582 <p>This is an overloaded intrinsic. You can use <tt>llvm.cos</tt> on any
5583 floating point or vector of floating point type. Not all targets support all
5586 declare float @llvm.cos.f32(float %Val)
5587 declare double @llvm.cos.f64(double %Val)
5588 declare x86_fp80 @llvm.cos.f80(x86_fp80 %Val)
5589 declare fp128 @llvm.cos.f128(fp128 %Val)
5590 declare ppc_fp128 @llvm.cos.ppcf128(ppc_fp128 %Val)
5596 The '<tt>llvm.cos.*</tt>' intrinsics return the cosine of the operand.
5602 The argument and return value are floating point numbers of the same type.
5608 This function returns the cosine of the specified operand, returning the
5609 same values as the libm <tt>cos</tt> functions would, and handles error
5610 conditions in the same way.</p>
5613 <!-- _______________________________________________________________________ -->
5614 <div class="doc_subsubsection">
5615 <a name="int_pow">'<tt>llvm.pow.*</tt>' Intrinsic</a>
5618 <div class="doc_text">
5621 <p>This is an overloaded intrinsic. You can use <tt>llvm.pow</tt> on any
5622 floating point or vector of floating point type. Not all targets support all
5625 declare float @llvm.pow.f32(float %Val, float %Power)
5626 declare double @llvm.pow.f64(double %Val, double %Power)
5627 declare x86_fp80 @llvm.pow.f80(x86_fp80 %Val, x86_fp80 %Power)
5628 declare fp128 @llvm.pow.f128(fp128 %Val, fp128 %Power)
5629 declare ppc_fp128 @llvm.pow.ppcf128(ppc_fp128 %Val, ppc_fp128 Power)
5635 The '<tt>llvm.pow.*</tt>' intrinsics return the first operand raised to the
5636 specified (positive or negative) power.
5642 The second argument is a floating point power, and the first is a value to
5643 raise to that power.
5649 This function returns the first value raised to the second power,
5651 same values as the libm <tt>pow</tt> functions would, and handles error
5652 conditions in the same way.</p>
5656 <!-- ======================================================================= -->
5657 <div class="doc_subsection">
5658 <a name="int_manip">Bit Manipulation Intrinsics</a>
5661 <div class="doc_text">
5663 LLVM provides intrinsics for a few important bit manipulation operations.
5664 These allow efficient code generation for some algorithms.
5669 <!-- _______________________________________________________________________ -->
5670 <div class="doc_subsubsection">
5671 <a name="int_bswap">'<tt>llvm.bswap.*</tt>' Intrinsics</a>
5674 <div class="doc_text">
5677 <p>This is an overloaded intrinsic function. You can use bswap on any integer
5678 type that is an even number of bytes (i.e. BitWidth % 16 == 0).</p>
5680 declare i16 @llvm.bswap.i16(i16 <id>)
5681 declare i32 @llvm.bswap.i32(i32 <id>)
5682 declare i64 @llvm.bswap.i64(i64 <id>)
5688 The '<tt>llvm.bswap</tt>' family of intrinsics is used to byte swap integer
5689 values with an even number of bytes (positive multiple of 16 bits). These are
5690 useful for performing operations on data that is not in the target's native
5697 The <tt>llvm.bswap.i16</tt> intrinsic returns an i16 value that has the high
5698 and low byte of the input i16 swapped. Similarly, the <tt>llvm.bswap.i32</tt>
5699 intrinsic returns an i32 value that has the four bytes of the input i32
5700 swapped, so that if the input bytes are numbered 0, 1, 2, 3 then the returned
5701 i32 will have its bytes in 3, 2, 1, 0 order. The <tt>llvm.bswap.i48</tt>,
5702 <tt>llvm.bswap.i64</tt> and other intrinsics extend this concept to
5703 additional even-byte lengths (6 bytes, 8 bytes and more, respectively).
5708 <!-- _______________________________________________________________________ -->
5709 <div class="doc_subsubsection">
5710 <a name="int_ctpop">'<tt>llvm.ctpop.*</tt>' Intrinsic</a>
5713 <div class="doc_text">
5716 <p>This is an overloaded intrinsic. You can use llvm.ctpop on any integer bit
5717 width. Not all targets support all bit widths however.</p>
5719 declare i8 @llvm.ctpop.i8(i8 <src>)
5720 declare i16 @llvm.ctpop.i16(i16 <src>)
5721 declare i32 @llvm.ctpop.i32(i32 <src>)
5722 declare i64 @llvm.ctpop.i64(i64 <src>)
5723 declare i256 @llvm.ctpop.i256(i256 <src>)
5729 The '<tt>llvm.ctpop</tt>' family of intrinsics counts the number of bits set in a
5736 The only argument is the value to be counted. The argument may be of any
5737 integer type. The return type must match the argument type.
5743 The '<tt>llvm.ctpop</tt>' intrinsic counts the 1's in a variable.
5747 <!-- _______________________________________________________________________ -->
5748 <div class="doc_subsubsection">
5749 <a name="int_ctlz">'<tt>llvm.ctlz.*</tt>' Intrinsic</a>
5752 <div class="doc_text">
5755 <p>This is an overloaded intrinsic. You can use <tt>llvm.ctlz</tt> on any
5756 integer bit width. Not all targets support all bit widths however.</p>
5758 declare i8 @llvm.ctlz.i8 (i8 <src>)
5759 declare i16 @llvm.ctlz.i16(i16 <src>)
5760 declare i32 @llvm.ctlz.i32(i32 <src>)
5761 declare i64 @llvm.ctlz.i64(i64 <src>)
5762 declare i256 @llvm.ctlz.i256(i256 <src>)
5768 The '<tt>llvm.ctlz</tt>' family of intrinsic functions counts the number of
5769 leading zeros in a variable.
5775 The only argument is the value to be counted. The argument may be of any
5776 integer type. The return type must match the argument type.
5782 The '<tt>llvm.ctlz</tt>' intrinsic counts the leading (most significant) zeros
5783 in a variable. If the src == 0 then the result is the size in bits of the type
5784 of src. For example, <tt>llvm.ctlz(i32 2) = 30</tt>.
5790 <!-- _______________________________________________________________________ -->
5791 <div class="doc_subsubsection">
5792 <a name="int_cttz">'<tt>llvm.cttz.*</tt>' Intrinsic</a>
5795 <div class="doc_text">
5798 <p>This is an overloaded intrinsic. You can use <tt>llvm.cttz</tt> on any
5799 integer bit width. Not all targets support all bit widths however.</p>
5801 declare i8 @llvm.cttz.i8 (i8 <src>)
5802 declare i16 @llvm.cttz.i16(i16 <src>)
5803 declare i32 @llvm.cttz.i32(i32 <src>)
5804 declare i64 @llvm.cttz.i64(i64 <src>)
5805 declare i256 @llvm.cttz.i256(i256 <src>)
5811 The '<tt>llvm.cttz</tt>' family of intrinsic functions counts the number of
5818 The only argument is the value to be counted. The argument may be of any
5819 integer type. The return type must match the argument type.
5825 The '<tt>llvm.cttz</tt>' intrinsic counts the trailing (least significant) zeros
5826 in a variable. If the src == 0 then the result is the size in bits of the type
5827 of src. For example, <tt>llvm.cttz(2) = 1</tt>.
5831 <!-- _______________________________________________________________________ -->
5832 <div class="doc_subsubsection">
5833 <a name="int_part_select">'<tt>llvm.part.select.*</tt>' Intrinsic</a>
5836 <div class="doc_text">
5839 <p>This is an overloaded intrinsic. You can use <tt>llvm.part.select</tt>
5840 on any integer bit width.</p>
5842 declare i17 @llvm.part.select.i17 (i17 %val, i32 %loBit, i32 %hiBit)
5843 declare i29 @llvm.part.select.i29 (i29 %val, i32 %loBit, i32 %hiBit)
5847 <p>The '<tt>llvm.part.select</tt>' family of intrinsic functions selects a
5848 range of bits from an integer value and returns them in the same bit width as
5849 the original value.</p>
5852 <p>The first argument, <tt>%val</tt> and the result may be integer types of
5853 any bit width but they must have the same bit width. The second and third
5854 arguments must be <tt>i32</tt> type since they specify only a bit index.</p>
5857 <p>The operation of the '<tt>llvm.part.select</tt>' intrinsic has two modes
5858 of operation: forwards and reverse. If <tt>%loBit</tt> is greater than
5859 <tt>%hiBits</tt> then the intrinsic operates in reverse mode. Otherwise it
5860 operates in forward mode.</p>
5861 <p>In forward mode, this intrinsic is the equivalent of shifting <tt>%val</tt>
5862 right by <tt>%loBit</tt> bits and then ANDing it with a mask with
5863 only the <tt>%hiBit - %loBit</tt> bits set, as follows:</p>
5865 <li>The <tt>%val</tt> is shifted right (LSHR) by the number of bits specified
5866 by <tt>%loBits</tt>. This normalizes the value to the low order bits.</li>
5867 <li>The <tt>%loBits</tt> value is subtracted from the <tt>%hiBits</tt> value
5868 to determine the number of bits to retain.</li>
5869 <li>A mask of the retained bits is created by shifting a -1 value.</li>
5870 <li>The mask is ANDed with <tt>%val</tt> to produce the result.</li>
5872 <p>In reverse mode, a similar computation is made except that the bits are
5873 returned in the reverse order. So, for example, if <tt>X</tt> has the value
5874 <tt>i16 0x0ACF (101011001111)</tt> and we apply
5875 <tt>part.select(i16 X, 8, 3)</tt> to it, we get back the value
5876 <tt>i16 0x0026 (000000100110)</tt>.</p>
5879 <div class="doc_subsubsection">
5880 <a name="int_part_set">'<tt>llvm.part.set.*</tt>' Intrinsic</a>
5883 <div class="doc_text">
5886 <p>This is an overloaded intrinsic. You can use <tt>llvm.part.set</tt>
5887 on any integer bit width.</p>
5889 declare i17 @llvm.part.set.i17.i9 (i17 %val, i9 %repl, i32 %lo, i32 %hi)
5890 declare i29 @llvm.part.set.i29.i9 (i29 %val, i9 %repl, i32 %lo, i32 %hi)
5894 <p>The '<tt>llvm.part.set</tt>' family of intrinsic functions replaces a range
5895 of bits in an integer value with another integer value. It returns the integer
5896 with the replaced bits.</p>
5899 <p>The first argument, <tt>%val</tt>, and the result may be integer types of
5900 any bit width, but they must have the same bit width. <tt>%val</tt> is the value
5901 whose bits will be replaced. The second argument, <tt>%repl</tt> may be an
5902 integer of any bit width. The third and fourth arguments must be <tt>i32</tt>
5903 type since they specify only a bit index.</p>
5906 <p>The operation of the '<tt>llvm.part.set</tt>' intrinsic has two modes
5907 of operation: forwards and reverse. If <tt>%lo</tt> is greater than
5908 <tt>%hi</tt> then the intrinsic operates in reverse mode. Otherwise it
5909 operates in forward mode.</p>
5911 <p>For both modes, the <tt>%repl</tt> value is prepared for use by either
5912 truncating it down to the size of the replacement area or zero extending it
5913 up to that size.</p>
5915 <p>In forward mode, the bits between <tt>%lo</tt> and <tt>%hi</tt> (inclusive)
5916 are replaced with corresponding bits from <tt>%repl</tt>. That is the 0th bit
5917 in <tt>%repl</tt> replaces the <tt>%lo</tt>th bit in <tt>%val</tt> and etc. up
5918 to the <tt>%hi</tt>th bit.</p>
5920 <p>In reverse mode, a similar computation is made except that the bits are
5921 reversed. That is, the <tt>0</tt>th bit in <tt>%repl</tt> replaces the
5922 <tt>%hi</tt> bit in <tt>%val</tt> and etc. down to the <tt>%lo</tt>th bit.</p>
5927 llvm.part.set(0xFFFF, 0, 4, 7) -> 0xFF0F
5928 llvm.part.set(0xFFFF, 0, 7, 4) -> 0xFF0F
5929 llvm.part.set(0xFFFF, 1, 7, 4) -> 0xFF8F
5930 llvm.part.set(0xFFFF, F, 8, 3) -> 0xFFE7
5931 llvm.part.set(0xFFFF, 0, 3, 8) -> 0xFE07
5936 <!-- ======================================================================= -->
5937 <div class="doc_subsection">
5938 <a name="int_overflow">Arithmetic with Overflow Intrinsics</a>
5941 <div class="doc_text">
5943 LLVM provides intrinsics for some arithmetic with overflow operations.
5948 <!-- _______________________________________________________________________ -->
5949 <div class="doc_subsubsection">
5950 <a name="int_sadd_overflow">'<tt>llvm.sadd.with.overflow.*</tt>' Intrinsics</a>
5953 <div class="doc_text">
5957 <p>This is an overloaded intrinsic. You can use <tt>llvm.sadd.with.overflow</tt>
5958 on any integer bit width.</p>
5961 declare {i16, i1} @llvm.sadd.with.overflow.i16(i16 %a, i16 %b)
5962 declare {i32, i1} @llvm.sadd.with.overflow.i32(i32 %a, i32 %b)
5963 declare {i64, i1} @llvm.sadd.with.overflow.i64(i64 %a, i64 %b)
5968 <p>The '<tt>llvm.sadd.with.overflow</tt>' family of intrinsic functions perform
5969 a signed addition of the two arguments, and indicate whether an overflow
5970 occurred during the signed summation.</p>
5974 <p>The arguments (%a and %b) and the first element of the result structure may
5975 be of integer types of any bit width, but they must have the same bit width. The
5976 second element of the result structure must be of type <tt>i1</tt>. <tt>%a</tt>
5977 and <tt>%b</tt> are the two values that will undergo signed addition.</p>
5981 <p>The '<tt>llvm.sadd.with.overflow</tt>' family of intrinsic functions perform
5982 a signed addition of the two variables. They return a structure — the
5983 first element of which is the signed summation, and the second element of which
5984 is a bit specifying if the signed summation resulted in an overflow.</p>
5988 %res = call {i32, i1} @llvm.sadd.with.overflow.i32(i32 %a, i32 %b)
5989 %sum = extractvalue {i32, i1} %res, 0
5990 %obit = extractvalue {i32, i1} %res, 1
5991 br i1 %obit, label %overflow, label %normal
5996 <!-- _______________________________________________________________________ -->
5997 <div class="doc_subsubsection">
5998 <a name="int_uadd_overflow">'<tt>llvm.uadd.with.overflow.*</tt>' Intrinsics</a>
6001 <div class="doc_text">
6005 <p>This is an overloaded intrinsic. You can use <tt>llvm.uadd.with.overflow</tt>
6006 on any integer bit width.</p>
6009 declare {i16, i1} @llvm.uadd.with.overflow.i16(i16 %a, i16 %b)
6010 declare {i32, i1} @llvm.uadd.with.overflow.i32(i32 %a, i32 %b)
6011 declare {i64, i1} @llvm.uadd.with.overflow.i64(i64 %a, i64 %b)
6016 <p>The '<tt>llvm.uadd.with.overflow</tt>' family of intrinsic functions perform
6017 an unsigned addition of the two arguments, and indicate whether a carry occurred
6018 during the unsigned summation.</p>
6022 <p>The arguments (%a and %b) and the first element of the result structure may
6023 be of integer types of any bit width, but they must have the same bit width. The
6024 second element of the result structure must be of type <tt>i1</tt>. <tt>%a</tt>
6025 and <tt>%b</tt> are the two values that will undergo unsigned addition.</p>
6029 <p>The '<tt>llvm.uadd.with.overflow</tt>' family of intrinsic functions perform
6030 an unsigned addition of the two arguments. They return a structure — the
6031 first element of which is the sum, and the second element of which is a bit
6032 specifying if the unsigned summation resulted in a carry.</p>
6036 %res = call {i32, i1} @llvm.uadd.with.overflow.i32(i32 %a, i32 %b)
6037 %sum = extractvalue {i32, i1} %res, 0
6038 %obit = extractvalue {i32, i1} %res, 1
6039 br i1 %obit, label %carry, label %normal
6044 <!-- _______________________________________________________________________ -->
6045 <div class="doc_subsubsection">
6046 <a name="int_ssub_overflow">'<tt>llvm.ssub.with.overflow.*</tt>' Intrinsics</a>
6049 <div class="doc_text">
6053 <p>This is an overloaded intrinsic. You can use <tt>llvm.ssub.with.overflow</tt>
6054 on any integer bit width.</p>
6057 declare {i16, i1} @llvm.ssub.with.overflow.i16(i16 %a, i16 %b)
6058 declare {i32, i1} @llvm.ssub.with.overflow.i32(i32 %a, i32 %b)
6059 declare {i64, i1} @llvm.ssub.with.overflow.i64(i64 %a, i64 %b)
6064 <p>The '<tt>llvm.ssub.with.overflow</tt>' family of intrinsic functions perform
6065 a signed subtraction of the two arguments, and indicate whether an overflow
6066 occurred during the signed subtraction.</p>
6070 <p>The arguments (%a and %b) and the first element of the result structure may
6071 be of integer types of any bit width, but they must have the same bit width. The
6072 second element of the result structure must be of type <tt>i1</tt>. <tt>%a</tt>
6073 and <tt>%b</tt> are the two values that will undergo signed subtraction.</p>
6077 <p>The '<tt>llvm.ssub.with.overflow</tt>' family of intrinsic functions perform
6078 a signed subtraction of the two arguments. They return a structure — the
6079 first element of which is the subtraction, and the second element of which is a bit
6080 specifying if the signed subtraction resulted in an overflow.</p>
6084 %res = call {i32, i1} @llvm.ssub.with.overflow.i32(i32 %a, i32 %b)
6085 %sum = extractvalue {i32, i1} %res, 0
6086 %obit = extractvalue {i32, i1} %res, 1
6087 br i1 %obit, label %overflow, label %normal
6092 <!-- _______________________________________________________________________ -->
6093 <div class="doc_subsubsection">
6094 <a name="int_usub_overflow">'<tt>llvm.usub.with.overflow.*</tt>' Intrinsics</a>
6097 <div class="doc_text">
6101 <p>This is an overloaded intrinsic. You can use <tt>llvm.usub.with.overflow</tt>
6102 on any integer bit width.</p>
6105 declare {i16, i1} @llvm.usub.with.overflow.i16(i16 %a, i16 %b)
6106 declare {i32, i1} @llvm.usub.with.overflow.i32(i32 %a, i32 %b)
6107 declare {i64, i1} @llvm.usub.with.overflow.i64(i64 %a, i64 %b)
6112 <p>The '<tt>llvm.usub.with.overflow</tt>' family of intrinsic functions perform
6113 an unsigned subtraction of the two arguments, and indicate whether an overflow
6114 occurred during the unsigned subtraction.</p>
6118 <p>The arguments (%a and %b) and the first element of the result structure may
6119 be of integer types of any bit width, but they must have the same bit width. The
6120 second element of the result structure must be of type <tt>i1</tt>. <tt>%a</tt>
6121 and <tt>%b</tt> are the two values that will undergo unsigned subtraction.</p>
6125 <p>The '<tt>llvm.usub.with.overflow</tt>' family of intrinsic functions perform
6126 an unsigned subtraction of the two arguments. They return a structure — the
6127 first element of which is the subtraction, and the second element of which is a bit
6128 specifying if the unsigned subtraction resulted in an overflow.</p>
6132 %res = call {i32, i1} @llvm.usub.with.overflow.i32(i32 %a, i32 %b)
6133 %sum = extractvalue {i32, i1} %res, 0
6134 %obit = extractvalue {i32, i1} %res, 1
6135 br i1 %obit, label %overflow, label %normal
6140 <!-- _______________________________________________________________________ -->
6141 <div class="doc_subsubsection">
6142 <a name="int_smul_overflow">'<tt>llvm.smul.with.overflow.*</tt>' Intrinsics</a>
6145 <div class="doc_text">
6149 <p>This is an overloaded intrinsic. You can use <tt>llvm.smul.with.overflow</tt>
6150 on any integer bit width.</p>
6153 declare {i16, i1} @llvm.smul.with.overflow.i16(i16 %a, i16 %b)
6154 declare {i32, i1} @llvm.smul.with.overflow.i32(i32 %a, i32 %b)
6155 declare {i64, i1} @llvm.smul.with.overflow.i64(i64 %a, i64 %b)
6160 <p>The '<tt>llvm.smul.with.overflow</tt>' family of intrinsic functions perform
6161 a signed multiplication of the two arguments, and indicate whether an overflow
6162 occurred during the signed multiplication.</p>
6166 <p>The arguments (%a and %b) and the first element of the result structure may
6167 be of integer types of any bit width, but they must have the same bit width. The
6168 second element of the result structure must be of type <tt>i1</tt>. <tt>%a</tt>
6169 and <tt>%b</tt> are the two values that will undergo signed multiplication.</p>
6173 <p>The '<tt>llvm.smul.with.overflow</tt>' family of intrinsic functions perform
6174 a signed multiplication of the two arguments. They return a structure —
6175 the first element of which is the multiplication, and the second element of
6176 which is a bit specifying if the signed multiplication resulted in an
6181 %res = call {i32, i1} @llvm.smul.with.overflow.i32(i32 %a, i32 %b)
6182 %sum = extractvalue {i32, i1} %res, 0
6183 %obit = extractvalue {i32, i1} %res, 1
6184 br i1 %obit, label %overflow, label %normal
6189 <!-- _______________________________________________________________________ -->
6190 <div class="doc_subsubsection">
6191 <a name="int_umul_overflow">'<tt>llvm.umul.with.overflow.*</tt>' Intrinsics</a>
6194 <div class="doc_text">
6198 <p>This is an overloaded intrinsic. You can use <tt>llvm.umul.with.overflow</tt>
6199 on any integer bit width.</p>
6202 declare {i16, i1} @llvm.umul.with.overflow.i16(i16 %a, i16 %b)
6203 declare {i32, i1} @llvm.umul.with.overflow.i32(i32 %a, i32 %b)
6204 declare {i64, i1} @llvm.umul.with.overflow.i64(i64 %a, i64 %b)
6209 <p><i><b>Warning:</b> '<tt>llvm.umul.with.overflow</tt>' is badly broken. It is
6210 actively being fixed, but it should not currently be used!</i></p>
6212 <p>The '<tt>llvm.umul.with.overflow</tt>' family of intrinsic functions perform
6213 a unsigned multiplication of the two arguments, and indicate whether an overflow
6214 occurred during the unsigned multiplication.</p>
6218 <p>The arguments (%a and %b) and the first element of the result structure may
6219 be of integer types of any bit width, but they must have the same bit width. The
6220 second element of the result structure must be of type <tt>i1</tt>. <tt>%a</tt>
6221 and <tt>%b</tt> are the two values that will undergo unsigned
6226 <p>The '<tt>llvm.umul.with.overflow</tt>' family of intrinsic functions perform
6227 an unsigned multiplication of the two arguments. They return a structure —
6228 the first element of which is the multiplication, and the second element of
6229 which is a bit specifying if the unsigned multiplication resulted in an
6234 %res = call {i32, i1} @llvm.umul.with.overflow.i32(i32 %a, i32 %b)
6235 %sum = extractvalue {i32, i1} %res, 0
6236 %obit = extractvalue {i32, i1} %res, 1
6237 br i1 %obit, label %overflow, label %normal
6242 <!-- ======================================================================= -->
6243 <div class="doc_subsection">
6244 <a name="int_debugger">Debugger Intrinsics</a>
6247 <div class="doc_text">
6249 The LLVM debugger intrinsics (which all start with <tt>llvm.dbg.</tt> prefix),
6250 are described in the <a
6251 href="SourceLevelDebugging.html#format_common_intrinsics">LLVM Source Level
6252 Debugging</a> document.
6257 <!-- ======================================================================= -->
6258 <div class="doc_subsection">
6259 <a name="int_eh">Exception Handling Intrinsics</a>
6262 <div class="doc_text">
6263 <p> The LLVM exception handling intrinsics (which all start with
6264 <tt>llvm.eh.</tt> prefix), are described in the <a
6265 href="ExceptionHandling.html#format_common_intrinsics">LLVM Exception
6266 Handling</a> document. </p>
6269 <!-- ======================================================================= -->
6270 <div class="doc_subsection">
6271 <a name="int_trampoline">Trampoline Intrinsic</a>
6274 <div class="doc_text">
6276 This intrinsic makes it possible to excise one parameter, marked with
6277 the <tt>nest</tt> attribute, from a function. The result is a callable
6278 function pointer lacking the nest parameter - the caller does not need
6279 to provide a value for it. Instead, the value to use is stored in
6280 advance in a "trampoline", a block of memory usually allocated
6281 on the stack, which also contains code to splice the nest value into the
6282 argument list. This is used to implement the GCC nested function address
6286 For example, if the function is
6287 <tt>i32 f(i8* nest %c, i32 %x, i32 %y)</tt> then the resulting function
6288 pointer has signature <tt>i32 (i32, i32)*</tt>. It can be created as follows:</p>
6290 %tramp = alloca [10 x i8], align 4 ; size and alignment only correct for X86
6291 %tramp1 = getelementptr [10 x i8]* %tramp, i32 0, i32 0
6292 %p = call i8* @llvm.init.trampoline( i8* %tramp1, i8* bitcast (i32 (i8* nest , i32, i32)* @f to i8*), i8* %nval )
6293 %fp = bitcast i8* %p to i32 (i32, i32)*
6295 <p>The call <tt>%val = call i32 %fp( i32 %x, i32 %y )</tt> is then equivalent
6296 to <tt>%val = call i32 %f( i8* %nval, i32 %x, i32 %y )</tt>.</p>
6299 <!-- _______________________________________________________________________ -->
6300 <div class="doc_subsubsection">
6301 <a name="int_it">'<tt>llvm.init.trampoline</tt>' Intrinsic</a>
6303 <div class="doc_text">
6306 declare i8* @llvm.init.trampoline(i8* <tramp>, i8* <func>, i8* <nval>)
6310 This fills the memory pointed to by <tt>tramp</tt> with code
6311 and returns a function pointer suitable for executing it.
6315 The <tt>llvm.init.trampoline</tt> intrinsic takes three arguments, all
6316 pointers. The <tt>tramp</tt> argument must point to a sufficiently large
6317 and sufficiently aligned block of memory; this memory is written to by the
6318 intrinsic. Note that the size and the alignment are target-specific - LLVM
6319 currently provides no portable way of determining them, so a front-end that
6320 generates this intrinsic needs to have some target-specific knowledge.
6321 The <tt>func</tt> argument must hold a function bitcast to an <tt>i8*</tt>.
6325 The block of memory pointed to by <tt>tramp</tt> is filled with target
6326 dependent code, turning it into a function. A pointer to this function is
6327 returned, but needs to be bitcast to an
6328 <a href="#int_trampoline">appropriate function pointer type</a>
6329 before being called. The new function's signature is the same as that of
6330 <tt>func</tt> with any arguments marked with the <tt>nest</tt> attribute
6331 removed. At most one such <tt>nest</tt> argument is allowed, and it must be
6332 of pointer type. Calling the new function is equivalent to calling
6333 <tt>func</tt> with the same argument list, but with <tt>nval</tt> used for the
6334 missing <tt>nest</tt> argument. If, after calling
6335 <tt>llvm.init.trampoline</tt>, the memory pointed to by <tt>tramp</tt> is
6336 modified, then the effect of any later call to the returned function pointer is
6341 <!-- ======================================================================= -->
6342 <div class="doc_subsection">
6343 <a name="int_atomics">Atomic Operations and Synchronization Intrinsics</a>
6346 <div class="doc_text">
6348 These intrinsic functions expand the "universal IR" of LLVM to represent
6349 hardware constructs for atomic operations and memory synchronization. This
6350 provides an interface to the hardware, not an interface to the programmer. It
6351 is aimed at a low enough level to allow any programming models or APIs
6352 (Application Programming Interfaces) which
6353 need atomic behaviors to map cleanly onto it. It is also modeled primarily on
6354 hardware behavior. Just as hardware provides a "universal IR" for source
6355 languages, it also provides a starting point for developing a "universal"
6356 atomic operation and synchronization IR.
6359 These do <em>not</em> form an API such as high-level threading libraries,
6360 software transaction memory systems, atomic primitives, and intrinsic
6361 functions as found in BSD, GNU libc, atomic_ops, APR, and other system and
6362 application libraries. The hardware interface provided by LLVM should allow
6363 a clean implementation of all of these APIs and parallel programming models.
6364 No one model or paradigm should be selected above others unless the hardware
6365 itself ubiquitously does so.
6370 <!-- _______________________________________________________________________ -->
6371 <div class="doc_subsubsection">
6372 <a name="int_memory_barrier">'<tt>llvm.memory.barrier</tt>' Intrinsic</a>
6374 <div class="doc_text">
6377 declare void @llvm.memory.barrier( i1 <ll>, i1 <ls>, i1 <sl>, i1 <ss>,
6383 The <tt>llvm.memory.barrier</tt> intrinsic guarantees ordering between
6384 specific pairs of memory access types.
6388 The <tt>llvm.memory.barrier</tt> intrinsic requires five boolean arguments.
6389 The first four arguments enables a specific barrier as listed below. The fith
6390 argument specifies that the barrier applies to io or device or uncached memory.
6394 <li><tt>ll</tt>: load-load barrier</li>
6395 <li><tt>ls</tt>: load-store barrier</li>
6396 <li><tt>sl</tt>: store-load barrier</li>
6397 <li><tt>ss</tt>: store-store barrier</li>
6398 <li><tt>device</tt>: barrier applies to device and uncached memory also.</li>
6402 This intrinsic causes the system to enforce some ordering constraints upon
6403 the loads and stores of the program. This barrier does not indicate
6404 <em>when</em> any events will occur, it only enforces an <em>order</em> in
6405 which they occur. For any of the specified pairs of load and store operations
6406 (f.ex. load-load, or store-load), all of the first operations preceding the
6407 barrier will complete before any of the second operations succeeding the
6408 barrier begin. Specifically the semantics for each pairing is as follows:
6411 <li><tt>ll</tt>: All loads before the barrier must complete before any load
6412 after the barrier begins.</li>
6414 <li><tt>ls</tt>: All loads before the barrier must complete before any
6415 store after the barrier begins.</li>
6416 <li><tt>ss</tt>: All stores before the barrier must complete before any
6417 store after the barrier begins.</li>
6418 <li><tt>sl</tt>: All stores before the barrier must complete before any
6419 load after the barrier begins.</li>
6422 These semantics are applied with a logical "and" behavior when more than one
6423 is enabled in a single memory barrier intrinsic.
6426 Backends may implement stronger barriers than those requested when they do not
6427 support as fine grained a barrier as requested. Some architectures do not
6428 need all types of barriers and on such architectures, these become noops.
6435 %result1 = load i32* %ptr <i>; yields {i32}:result1 = 4</i>
6436 call void @llvm.memory.barrier( i1 false, i1 true, i1 false, i1 false )
6437 <i>; guarantee the above finishes</i>
6438 store i32 8, %ptr <i>; before this begins</i>
6442 <!-- _______________________________________________________________________ -->
6443 <div class="doc_subsubsection">
6444 <a name="int_atomic_cmp_swap">'<tt>llvm.atomic.cmp.swap.*</tt>' Intrinsic</a>
6446 <div class="doc_text">
6449 This is an overloaded intrinsic. You can use <tt>llvm.atomic.cmp.swap</tt> on
6450 any integer bit width and for different address spaces. Not all targets
6451 support all bit widths however.</p>
6454 declare i8 @llvm.atomic.cmp.swap.i8.p0i8( i8* <ptr>, i8 <cmp>, i8 <val> )
6455 declare i16 @llvm.atomic.cmp.swap.i16.p0i16( i16* <ptr>, i16 <cmp>, i16 <val> )
6456 declare i32 @llvm.atomic.cmp.swap.i32.p0i32( i32* <ptr>, i32 <cmp>, i32 <val> )
6457 declare i64 @llvm.atomic.cmp.swap.i64.p0i64( i64* <ptr>, i64 <cmp>, i64 <val> )
6462 This loads a value in memory and compares it to a given value. If they are
6463 equal, it stores a new value into the memory.
6467 The <tt>llvm.atomic.cmp.swap</tt> intrinsic takes three arguments. The result as
6468 well as both <tt>cmp</tt> and <tt>val</tt> must be integer values with the
6469 same bit width. The <tt>ptr</tt> argument must be a pointer to a value of
6470 this integer type. While any bit width integer may be used, targets may only
6471 lower representations they support in hardware.
6476 This entire intrinsic must be executed atomically. It first loads the value
6477 in memory pointed to by <tt>ptr</tt> and compares it with the value
6478 <tt>cmp</tt>. If they are equal, <tt>val</tt> is stored into the memory. The
6479 loaded value is yielded in all cases. This provides the equivalent of an
6480 atomic compare-and-swap operation within the SSA framework.
6488 %val1 = add i32 4, 4
6489 %result1 = call i32 @llvm.atomic.cmp.swap.i32.p0i32( i32* %ptr, i32 4, %val1 )
6490 <i>; yields {i32}:result1 = 4</i>
6491 %stored1 = icmp eq i32 %result1, 4 <i>; yields {i1}:stored1 = true</i>
6492 %memval1 = load i32* %ptr <i>; yields {i32}:memval1 = 8</i>
6494 %val2 = add i32 1, 1
6495 %result2 = call i32 @llvm.atomic.cmp.swap.i32.p0i32( i32* %ptr, i32 5, %val2 )
6496 <i>; yields {i32}:result2 = 8</i>
6497 %stored2 = icmp eq i32 %result2, 5 <i>; yields {i1}:stored2 = false</i>
6499 %memval2 = load i32* %ptr <i>; yields {i32}:memval2 = 8</i>
6503 <!-- _______________________________________________________________________ -->
6504 <div class="doc_subsubsection">
6505 <a name="int_atomic_swap">'<tt>llvm.atomic.swap.*</tt>' Intrinsic</a>
6507 <div class="doc_text">
6511 This is an overloaded intrinsic. You can use <tt>llvm.atomic.swap</tt> on any
6512 integer bit width. Not all targets support all bit widths however.</p>
6514 declare i8 @llvm.atomic.swap.i8.p0i8( i8* <ptr>, i8 <val> )
6515 declare i16 @llvm.atomic.swap.i16.p0i16( i16* <ptr>, i16 <val> )
6516 declare i32 @llvm.atomic.swap.i32.p0i32( i32* <ptr>, i32 <val> )
6517 declare i64 @llvm.atomic.swap.i64.p0i64( i64* <ptr>, i64 <val> )
6522 This intrinsic loads the value stored in memory at <tt>ptr</tt> and yields
6523 the value from memory. It then stores the value in <tt>val</tt> in the memory
6529 The <tt>llvm.atomic.swap</tt> intrinsic takes two arguments. Both the
6530 <tt>val</tt> argument and the result must be integers of the same bit width.
6531 The first argument, <tt>ptr</tt>, must be a pointer to a value of this
6532 integer type. The targets may only lower integer representations they
6537 This intrinsic loads the value pointed to by <tt>ptr</tt>, yields it, and
6538 stores <tt>val</tt> back into <tt>ptr</tt> atomically. This provides the
6539 equivalent of an atomic swap operation within the SSA framework.
6547 %val1 = add i32 4, 4
6548 %result1 = call i32 @llvm.atomic.swap.i32.p0i32( i32* %ptr, i32 %val1 )
6549 <i>; yields {i32}:result1 = 4</i>
6550 %stored1 = icmp eq i32 %result1, 4 <i>; yields {i1}:stored1 = true</i>
6551 %memval1 = load i32* %ptr <i>; yields {i32}:memval1 = 8</i>
6553 %val2 = add i32 1, 1
6554 %result2 = call i32 @llvm.atomic.swap.i32.p0i32( i32* %ptr, i32 %val2 )
6555 <i>; yields {i32}:result2 = 8</i>
6557 %stored2 = icmp eq i32 %result2, 8 <i>; yields {i1}:stored2 = true</i>
6558 %memval2 = load i32* %ptr <i>; yields {i32}:memval2 = 2</i>
6562 <!-- _______________________________________________________________________ -->
6563 <div class="doc_subsubsection">
6564 <a name="int_atomic_load_add">'<tt>llvm.atomic.load.add.*</tt>' Intrinsic</a>
6567 <div class="doc_text">
6570 This is an overloaded intrinsic. You can use <tt>llvm.atomic.load.add</tt> on any
6571 integer bit width. Not all targets support all bit widths however.</p>
6573 declare i8 @llvm.atomic.load.add.i8..p0i8( i8* <ptr>, i8 <delta> )
6574 declare i16 @llvm.atomic.load.add.i16..p0i16( i16* <ptr>, i16 <delta> )
6575 declare i32 @llvm.atomic.load.add.i32..p0i32( i32* <ptr>, i32 <delta> )
6576 declare i64 @llvm.atomic.load.add.i64..p0i64( i64* <ptr>, i64 <delta> )
6581 This intrinsic adds <tt>delta</tt> to the value stored in memory at
6582 <tt>ptr</tt>. It yields the original value at <tt>ptr</tt>.
6587 The intrinsic takes two arguments, the first a pointer to an integer value
6588 and the second an integer value. The result is also an integer value. These
6589 integer types can have any bit width, but they must all have the same bit
6590 width. The targets may only lower integer representations they support.
6594 This intrinsic does a series of operations atomically. It first loads the
6595 value stored at <tt>ptr</tt>. It then adds <tt>delta</tt>, stores the result
6596 to <tt>ptr</tt>. It yields the original value stored at <tt>ptr</tt>.
6603 %result1 = call i32 @llvm.atomic.load.add.i32.p0i32( i32* %ptr, i32 4 )
6604 <i>; yields {i32}:result1 = 4</i>
6605 %result2 = call i32 @llvm.atomic.load.add.i32.p0i32( i32* %ptr, i32 2 )
6606 <i>; yields {i32}:result2 = 8</i>
6607 %result3 = call i32 @llvm.atomic.load.add.i32.p0i32( i32* %ptr, i32 5 )
6608 <i>; yields {i32}:result3 = 10</i>
6609 %memval1 = load i32* %ptr <i>; yields {i32}:memval1 = 15</i>
6613 <!-- _______________________________________________________________________ -->
6614 <div class="doc_subsubsection">
6615 <a name="int_atomic_load_sub">'<tt>llvm.atomic.load.sub.*</tt>' Intrinsic</a>
6618 <div class="doc_text">
6621 This is an overloaded intrinsic. You can use <tt>llvm.atomic.load.sub</tt> on
6622 any integer bit width and for different address spaces. Not all targets
6623 support all bit widths however.</p>
6625 declare i8 @llvm.atomic.load.sub.i8.p0i32( i8* <ptr>, i8 <delta> )
6626 declare i16 @llvm.atomic.load.sub.i16.p0i32( i16* <ptr>, i16 <delta> )
6627 declare i32 @llvm.atomic.load.sub.i32.p0i32( i32* <ptr>, i32 <delta> )
6628 declare i64 @llvm.atomic.load.sub.i64.p0i32( i64* <ptr>, i64 <delta> )
6633 This intrinsic subtracts <tt>delta</tt> to the value stored in memory at
6634 <tt>ptr</tt>. It yields the original value at <tt>ptr</tt>.
6639 The intrinsic takes two arguments, the first a pointer to an integer value
6640 and the second an integer value. The result is also an integer value. These
6641 integer types can have any bit width, but they must all have the same bit
6642 width. The targets may only lower integer representations they support.
6646 This intrinsic does a series of operations atomically. It first loads the
6647 value stored at <tt>ptr</tt>. It then subtracts <tt>delta</tt>, stores the
6648 result to <tt>ptr</tt>. It yields the original value stored at <tt>ptr</tt>.
6655 %result1 = call i32 @llvm.atomic.load.sub.i32.p0i32( i32* %ptr, i32 4 )
6656 <i>; yields {i32}:result1 = 8</i>
6657 %result2 = call i32 @llvm.atomic.load.sub.i32.p0i32( i32* %ptr, i32 2 )
6658 <i>; yields {i32}:result2 = 4</i>
6659 %result3 = call i32 @llvm.atomic.load.sub.i32.p0i32( i32* %ptr, i32 5 )
6660 <i>; yields {i32}:result3 = 2</i>
6661 %memval1 = load i32* %ptr <i>; yields {i32}:memval1 = -3</i>
6665 <!-- _______________________________________________________________________ -->
6666 <div class="doc_subsubsection">
6667 <a name="int_atomic_load_and">'<tt>llvm.atomic.load.and.*</tt>' Intrinsic</a><br>
6668 <a name="int_atomic_load_nand">'<tt>llvm.atomic.load.nand.*</tt>' Intrinsic</a><br>
6669 <a name="int_atomic_load_or">'<tt>llvm.atomic.load.or.*</tt>' Intrinsic</a><br>
6670 <a name="int_atomic_load_xor">'<tt>llvm.atomic.load.xor.*</tt>' Intrinsic</a><br>
6673 <div class="doc_text">
6676 These are overloaded intrinsics. You can use <tt>llvm.atomic.load_and</tt>,
6677 <tt>llvm.atomic.load_nand</tt>, <tt>llvm.atomic.load_or</tt>, and
6678 <tt>llvm.atomic.load_xor</tt> on any integer bit width and for different
6679 address spaces. Not all targets support all bit widths however.</p>
6681 declare i8 @llvm.atomic.load.and.i8.p0i8( i8* <ptr>, i8 <delta> )
6682 declare i16 @llvm.atomic.load.and.i16.p0i16( i16* <ptr>, i16 <delta> )
6683 declare i32 @llvm.atomic.load.and.i32.p0i32( i32* <ptr>, i32 <delta> )
6684 declare i64 @llvm.atomic.load.and.i64.p0i64( i64* <ptr>, i64 <delta> )
6689 declare i8 @llvm.atomic.load.or.i8.p0i8( i8* <ptr>, i8 <delta> )
6690 declare i16 @llvm.atomic.load.or.i16.p0i16( i16* <ptr>, i16 <delta> )
6691 declare i32 @llvm.atomic.load.or.i32.p0i32( i32* <ptr>, i32 <delta> )
6692 declare i64 @llvm.atomic.load.or.i64.p0i64( i64* <ptr>, i64 <delta> )
6697 declare i8 @llvm.atomic.load.nand.i8.p0i32( i8* <ptr>, i8 <delta> )
6698 declare i16 @llvm.atomic.load.nand.i16.p0i32( i16* <ptr>, i16 <delta> )
6699 declare i32 @llvm.atomic.load.nand.i32.p0i32( i32* <ptr>, i32 <delta> )
6700 declare i64 @llvm.atomic.load.nand.i64.p0i32( i64* <ptr>, i64 <delta> )
6705 declare i8 @llvm.atomic.load.xor.i8.p0i32( i8* <ptr>, i8 <delta> )
6706 declare i16 @llvm.atomic.load.xor.i16.p0i32( i16* <ptr>, i16 <delta> )
6707 declare i32 @llvm.atomic.load.xor.i32.p0i32( i32* <ptr>, i32 <delta> )
6708 declare i64 @llvm.atomic.load.xor.i64.p0i32( i64* <ptr>, i64 <delta> )
6713 These intrinsics bitwise the operation (and, nand, or, xor) <tt>delta</tt> to
6714 the value stored in memory at <tt>ptr</tt>. It yields the original value
6720 These intrinsics take two arguments, the first a pointer to an integer value
6721 and the second an integer value. The result is also an integer value. These
6722 integer types can have any bit width, but they must all have the same bit
6723 width. The targets may only lower integer representations they support.
6727 These intrinsics does a series of operations atomically. They first load the
6728 value stored at <tt>ptr</tt>. They then do the bitwise operation
6729 <tt>delta</tt>, store the result to <tt>ptr</tt>. They yield the original
6730 value stored at <tt>ptr</tt>.
6736 store i32 0x0F0F, %ptr
6737 %result0 = call i32 @llvm.atomic.load.nand.i32.p0i32( i32* %ptr, i32 0xFF )
6738 <i>; yields {i32}:result0 = 0x0F0F</i>
6739 %result1 = call i32 @llvm.atomic.load.and.i32.p0i32( i32* %ptr, i32 0xFF )
6740 <i>; yields {i32}:result1 = 0xFFFFFFF0</i>
6741 %result2 = call i32 @llvm.atomic.load.or.i32.p0i32( i32* %ptr, i32 0F )
6742 <i>; yields {i32}:result2 = 0xF0</i>
6743 %result3 = call i32 @llvm.atomic.load.xor.i32.p0i32( i32* %ptr, i32 0F )
6744 <i>; yields {i32}:result3 = FF</i>
6745 %memval1 = load i32* %ptr <i>; yields {i32}:memval1 = F0</i>
6750 <!-- _______________________________________________________________________ -->
6751 <div class="doc_subsubsection">
6752 <a name="int_atomic_load_max">'<tt>llvm.atomic.load.max.*</tt>' Intrinsic</a><br>
6753 <a name="int_atomic_load_min">'<tt>llvm.atomic.load.min.*</tt>' Intrinsic</a><br>
6754 <a name="int_atomic_load_umax">'<tt>llvm.atomic.load.umax.*</tt>' Intrinsic</a><br>
6755 <a name="int_atomic_load_umin">'<tt>llvm.atomic.load.umin.*</tt>' Intrinsic</a><br>
6758 <div class="doc_text">
6761 These are overloaded intrinsics. You can use <tt>llvm.atomic.load_max</tt>,
6762 <tt>llvm.atomic.load_min</tt>, <tt>llvm.atomic.load_umax</tt>, and
6763 <tt>llvm.atomic.load_umin</tt> on any integer bit width and for different
6764 address spaces. Not all targets
6765 support all bit widths however.</p>
6767 declare i8 @llvm.atomic.load.max.i8.p0i8( i8* <ptr>, i8 <delta> )
6768 declare i16 @llvm.atomic.load.max.i16.p0i16( i16* <ptr>, i16 <delta> )
6769 declare i32 @llvm.atomic.load.max.i32.p0i32( i32* <ptr>, i32 <delta> )
6770 declare i64 @llvm.atomic.load.max.i64.p0i64( i64* <ptr>, i64 <delta> )
6775 declare i8 @llvm.atomic.load.min.i8.p0i8( i8* <ptr>, i8 <delta> )
6776 declare i16 @llvm.atomic.load.min.i16.p0i16( i16* <ptr>, i16 <delta> )
6777 declare i32 @llvm.atomic.load.min.i32..p0i32( i32* <ptr>, i32 <delta> )
6778 declare i64 @llvm.atomic.load.min.i64..p0i64( i64* <ptr>, i64 <delta> )
6783 declare i8 @llvm.atomic.load.umax.i8.p0i8( i8* <ptr>, i8 <delta> )
6784 declare i16 @llvm.atomic.load.umax.i16.p0i16( i16* <ptr>, i16 <delta> )
6785 declare i32 @llvm.atomic.load.umax.i32.p0i32( i32* <ptr>, i32 <delta> )
6786 declare i64 @llvm.atomic.load.umax.i64.p0i64( i64* <ptr>, i64 <delta> )
6791 declare i8 @llvm.atomic.load.umin.i8..p0i8( i8* <ptr>, i8 <delta> )
6792 declare i16 @llvm.atomic.load.umin.i16.p0i16( i16* <ptr>, i16 <delta> )
6793 declare i32 @llvm.atomic.load.umin.i32..p0i32( i32* <ptr>, i32 <delta> )
6794 declare i64 @llvm.atomic.load.umin.i64..p0i64( i64* <ptr>, i64 <delta> )
6799 These intrinsics takes the signed or unsigned minimum or maximum of
6800 <tt>delta</tt> and the value stored in memory at <tt>ptr</tt>. It yields the
6801 original value at <tt>ptr</tt>.
6806 These intrinsics take two arguments, the first a pointer to an integer value
6807 and the second an integer value. The result is also an integer value. These
6808 integer types can have any bit width, but they must all have the same bit
6809 width. The targets may only lower integer representations they support.
6813 These intrinsics does a series of operations atomically. They first load the
6814 value stored at <tt>ptr</tt>. They then do the signed or unsigned min or max
6815 <tt>delta</tt> and the value, store the result to <tt>ptr</tt>. They yield
6816 the original value stored at <tt>ptr</tt>.
6823 %result0 = call i32 @llvm.atomic.load.min.i32.p0i32( i32* %ptr, i32 -2 )
6824 <i>; yields {i32}:result0 = 7</i>
6825 %result1 = call i32 @llvm.atomic.load.max.i32.p0i32( i32* %ptr, i32 8 )
6826 <i>; yields {i32}:result1 = -2</i>
6827 %result2 = call i32 @llvm.atomic.load.umin.i32.p0i32( i32* %ptr, i32 10 )
6828 <i>; yields {i32}:result2 = 8</i>
6829 %result3 = call i32 @llvm.atomic.load.umax.i32.p0i32( i32* %ptr, i32 30 )
6830 <i>; yields {i32}:result3 = 8</i>
6831 %memval1 = load i32* %ptr <i>; yields {i32}:memval1 = 30</i>
6835 <!-- ======================================================================= -->
6836 <div class="doc_subsection">
6837 <a name="int_general">General Intrinsics</a>
6840 <div class="doc_text">
6841 <p> This class of intrinsics is designed to be generic and has
6842 no specific purpose. </p>
6845 <!-- _______________________________________________________________________ -->
6846 <div class="doc_subsubsection">
6847 <a name="int_var_annotation">'<tt>llvm.var.annotation</tt>' Intrinsic</a>
6850 <div class="doc_text">
6854 declare void @llvm.var.annotation(i8* <val>, i8* <str>, i8* <str>, i32 <int> )
6860 The '<tt>llvm.var.annotation</tt>' intrinsic
6866 The first argument is a pointer to a value, the second is a pointer to a
6867 global string, the third is a pointer to a global string which is the source
6868 file name, and the last argument is the line number.
6874 This intrinsic allows annotation of local variables with arbitrary strings.
6875 This can be useful for special purpose optimizations that want to look for these
6876 annotations. These have no other defined use, they are ignored by code
6877 generation and optimization.
6881 <!-- _______________________________________________________________________ -->
6882 <div class="doc_subsubsection">
6883 <a name="int_annotation">'<tt>llvm.annotation.*</tt>' Intrinsic</a>
6886 <div class="doc_text">
6889 <p>This is an overloaded intrinsic. You can use '<tt>llvm.annotation</tt>' on
6890 any integer bit width.
6893 declare i8 @llvm.annotation.i8(i8 <val>, i8* <str>, i8* <str>, i32 <int> )
6894 declare i16 @llvm.annotation.i16(i16 <val>, i8* <str>, i8* <str>, i32 <int> )
6895 declare i32 @llvm.annotation.i32(i32 <val>, i8* <str>, i8* <str>, i32 <int> )
6896 declare i64 @llvm.annotation.i64(i64 <val>, i8* <str>, i8* <str>, i32 <int> )
6897 declare i256 @llvm.annotation.i256(i256 <val>, i8* <str>, i8* <str>, i32 <int> )
6903 The '<tt>llvm.annotation</tt>' intrinsic.
6909 The first argument is an integer value (result of some expression),
6910 the second is a pointer to a global string, the third is a pointer to a global
6911 string which is the source file name, and the last argument is the line number.
6912 It returns the value of the first argument.
6918 This intrinsic allows annotations to be put on arbitrary expressions
6919 with arbitrary strings. This can be useful for special purpose optimizations
6920 that want to look for these annotations. These have no other defined use, they
6921 are ignored by code generation and optimization.
6925 <!-- _______________________________________________________________________ -->
6926 <div class="doc_subsubsection">
6927 <a name="int_trap">'<tt>llvm.trap</tt>' Intrinsic</a>
6930 <div class="doc_text">
6934 declare void @llvm.trap()
6940 The '<tt>llvm.trap</tt>' intrinsic
6952 This intrinsics is lowered to the target dependent trap instruction. If the
6953 target does not have a trap instruction, this intrinsic will be lowered to the
6954 call of the abort() function.
6958 <!-- _______________________________________________________________________ -->
6959 <div class="doc_subsubsection">
6960 <a name="int_stackprotector">'<tt>llvm.stackprotector</tt>' Intrinsic</a>
6962 <div class="doc_text">
6965 declare void @llvm.stackprotector( i8* <guard>, i8** <slot> )
6970 The <tt>llvm.stackprotector</tt> intrinsic takes the <tt>guard</tt> and stores
6971 it onto the stack at <tt>slot</tt>. The stack slot is adjusted to ensure that
6972 it is placed on the stack before local variables.
6976 The <tt>llvm.stackprotector</tt> intrinsic requires two pointer arguments. The
6977 first argument is the value loaded from the stack guard
6978 <tt>@__stack_chk_guard</tt>. The second variable is an <tt>alloca</tt> that
6979 has enough space to hold the value of the guard.
6983 This intrinsic causes the prologue/epilogue inserter to force the position of
6984 the <tt>AllocaInst</tt> stack slot to be before local variables on the
6985 stack. This is to ensure that if a local variable on the stack is overwritten,
6986 it will destroy the value of the guard. When the function exits, the guard on
6987 the stack is checked against the original guard. If they're different, then
6988 the program aborts by calling the <tt>__stack_chk_fail()</tt> function.
6992 <!-- *********************************************************************** -->
6995 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
6996 src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS"></a>
6997 <a href="http://validator.w3.org/check/referer"><img
6998 src="http://www.w3.org/Icons/valid-html401-blue" alt="Valid HTML 4.01"></a>
7000 <a href="mailto:sabre@nondot.org">Chris Lattner</a><br>
7001 <a href="http://llvm.org">The LLVM Compiler Infrastructure</a><br>
7002 Last modified: $Date$