Gitiles
Code Review Sign In
gerrit-public.fairphone.software / fp2-dev / platform / external / llvm / 569f2fa7f131be0a1c1f12a59e621506ce7744c1 / . / docs / LangRef.html
blob: 677e625661901698dab98471ceed23200b1bde9d [file] [log] [blame]
Misha Brukmandaa4cb02004-03-01 17:47:27 +0000[diff] [blame]1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
2 "http://www.w3.org/TR/html4/strict.dtd">
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]3<html>
4<head>
5 <title>LLVM Assembly Language Reference Manual</title>
Reid Spencer3921c742004-08-26 20:44:00 +0000[diff] [blame]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.">
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]10 <link rel="stylesheet" href="llvm.css" type="text/css">
11</head>
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]12
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]13<body>
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]14
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]15<div class="doc_title"> LLVM Language Reference Manual </div>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]16<ol>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]17 <li><a href="#abstract">Abstract</a></li>
18 <li><a href="#introduction">Introduction</a></li>
19 <li><a href="#identifiers">Identifiers</a></li>
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]20 <li><a href="#highlevel">High Level Structure</a>
21 <ol>
22 <li><a href="#modulestructure">Module Structure</a></li>
Chris Lattnere5d947b2004-12-09 16:36:40 +0000[diff] [blame]23 <li><a href="#linkage">Linkage Types</a></li>
Chris Lattnerbad10ee2005-05-06 22:57:40 +0000[diff] [blame]24 <li><a href="#callingconv">Calling Conventions</a></li>
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]25 <li><a href="#globalvars">Global Variables</a></li>
Chris Lattner4e9aba72006-01-23 23:23:47 +0000[diff] [blame]26 <li><a href="#functionstructure">Functions</a></li>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]27 <li><a href="#paramattrs">Parameter Attributes</a></li>
Chris Lattner4e9aba72006-01-23 23:23:47 +0000[diff] [blame]28 <li><a href="#moduleasm">Module-Level Inline Assembly</a></li>
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]29 </ol>
30 </li>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]31 <li><a href="#typesystem">Type System</a>
32 <ol>
Robert Bocchino7b81c752006-02-17 21:18:08 +0000[diff] [blame]33 <li><a href="#t_primitive">Primitive Types</a>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]34 <ol>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]35 <li><a href="#t_classifications">Type Classifications</a></li>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]36 </ol>
37 </li>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]38 <li><a href="#t_derived">Derived Types</a>
39 <ol>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]40 <li><a href="#t_array">Array Type</a></li>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]41 <li><a href="#t_function">Function Type</a></li>
42 <li><a href="#t_pointer">Pointer Type</a></li>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]43 <li><a href="#t_struct">Structure Type</a></li>
Andrew Lenharth75e10682006-12-08 17:13:00 +0000[diff] [blame]44 <li><a href="#t_pstruct">Packed Structure Type</a></li>
Chris Lattnera58561b2004-08-12 19:12:28 +0000[diff] [blame]45 <li><a href="#t_packed">Packed Type</a></li>
Chris Lattner69c11bb2005-04-25 17:34:15 +0000[diff] [blame]46 <li><a href="#t_opaque">Opaque Type</a></li>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]47 </ol>
48 </li>
49 </ol>
50 </li>
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]51 <li><a href="#constants">Constants</a>
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]52 <ol>
53 <li><a href="#simpleconstants">Simple Constants</a>
54 <li><a href="#aggregateconstants">Aggregate Constants</a>
55 <li><a href="#globalconstants">Global Variable and Function Addresses</a>
56 <li><a href="#undefvalues">Undefined Values</a>
57 <li><a href="#constantexprs">Constant Expressions</a>
58 </ol>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]59 </li>
Chris Lattnere87d6532006-01-25 23:47:57 +0000[diff] [blame]60 <li><a href="#othervalues">Other Values</a>
61 <ol>
62 <li><a href="#inlineasm">Inline Assembler Expressions</a>
63 </ol>
64 </li>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]65 <li><a href="#instref">Instruction Reference</a>
66 <ol>
67 <li><a href="#terminators">Terminator Instructions</a>
68 <ol>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]69 <li><a href="#i_ret">'<tt>ret</tt>' Instruction</a></li>
70 <li><a href="#i_br">'<tt>br</tt>' Instruction</a></li>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]71 <li><a href="#i_switch">'<tt>switch</tt>' Instruction</a></li>
72 <li><a href="#i_invoke">'<tt>invoke</tt>' Instruction</a></li>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]73 <li><a href="#i_unwind">'<tt>unwind</tt>' Instruction</a></li>
Chris Lattner35eca582004-10-16 18:04:13 +0000[diff] [blame]74 <li><a href="#i_unreachable">'<tt>unreachable</tt>' Instruction</a></li>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]75 </ol>
76 </li>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]77 <li><a href="#binaryops">Binary Operations</a>
78 <ol>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]79 <li><a href="#i_add">'<tt>add</tt>' Instruction</a></li>
80 <li><a href="#i_sub">'<tt>sub</tt>' Instruction</a></li>
81 <li><a href="#i_mul">'<tt>mul</tt>' Instruction</a></li>
Reid Spencer1628cec2006-10-26 06:15:43 +0000[diff] [blame]82 <li><a href="#i_udiv">'<tt>udiv</tt>' Instruction</a></li>
83 <li><a href="#i_sdiv">'<tt>sdiv</tt>' Instruction</a></li>
84 <li><a href="#i_fdiv">'<tt>fdiv</tt>' Instruction</a></li>
Reid Spencer0a783f72006-11-02 01:53:59 +0000[diff] [blame]85 <li><a href="#i_urem">'<tt>urem</tt>' Instruction</a></li>
86 <li><a href="#i_srem">'<tt>srem</tt>' Instruction</a></li>
87 <li><a href="#i_frem">'<tt>frem</tt>' Instruction</a></li>
Reid Spencer569f2fa2007-01-31 21:39:12 +0000[diff] [blame^]88 <li><a href="#i_shl">'<tt>shl</tt>' Instruction</a></li>
89 <li><a href="#i_lshr">'<tt>lshr</tt>' Instruction</a></li>
90 <li><a href="#i_ashr">'<tt>ashr</tt>' Instruction</a></li>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]91 </ol>
92 </li>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]93 <li><a href="#bitwiseops">Bitwise Binary Operations</a>
94 <ol>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]95 <li><a href="#i_and">'<tt>and</tt>' Instruction</a></li>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]96 <li><a href="#i_or">'<tt>or</tt>' Instruction</a></li>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]97 <li><a href="#i_xor">'<tt>xor</tt>' Instruction</a></li>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]98 </ol>
99 </li>
Chris Lattner3df241e2006-04-08 23:07:04 +0000[diff] [blame]100 <li><a href="#vectorops">Vector Operations</a>
101 <ol>
102 <li><a href="#i_extractelement">'<tt>extractelement</tt>' Instruction</a></li>
103 <li><a href="#i_insertelement">'<tt>insertelement</tt>' Instruction</a></li>
104 <li><a href="#i_shufflevector">'<tt>shufflevector</tt>' Instruction</a></li>
Chris Lattner3df241e2006-04-08 23:07:04 +0000[diff] [blame]105 </ol>
106 </li>
Chris Lattner884a9702006-08-15 00:45:58 +0000[diff] [blame]107 <li><a href="#memoryops">Memory Access and Addressing Operations</a>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]108 <ol>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]109 <li><a href="#i_malloc">'<tt>malloc</tt>' Instruction</a></li>
110 <li><a href="#i_free">'<tt>free</tt>' Instruction</a></li>
111 <li><a href="#i_alloca">'<tt>alloca</tt>' Instruction</a></li>
Robert Bocchino7b81c752006-02-17 21:18:08 +0000[diff] [blame]112 <li><a href="#i_load">'<tt>load</tt>' Instruction</a></li>
113 <li><a href="#i_store">'<tt>store</tt>' Instruction</a></li>
114 <li><a href="#i_getelementptr">'<tt>getelementptr</tt>' Instruction</a></li>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]115 </ol>
116 </li>
Reid Spencer2fd21e62006-11-08 01:18:52 +0000[diff] [blame]117 <li><a href="#convertops">Conversion Operations</a>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]118 <ol>
119 <li><a href="#i_trunc">'<tt>trunc .. to</tt>' Instruction</a></li>
120 <li><a href="#i_zext">'<tt>zext .. to</tt>' Instruction</a></li>
121 <li><a href="#i_sext">'<tt>sext .. to</tt>' Instruction</a></li>
122 <li><a href="#i_fptrunc">'<tt>fptrunc .. to</tt>' Instruction</a></li>
123 <li><a href="#i_fpext">'<tt>fpext .. to</tt>' Instruction</a></li>
Reid Spencerd4448792006-11-09 23:03:26 +0000[diff] [blame]124 <li><a href="#i_fptoui">'<tt>fptoui .. to</tt>' Instruction</a></li>
125 <li><a href="#i_fptosi">'<tt>fptosi .. to</tt>' Instruction</a></li>
126 <li><a href="#i_uitofp">'<tt>uitofp .. to</tt>' Instruction</a></li>
127 <li><a href="#i_sitofp">'<tt>sitofp .. to</tt>' Instruction</a></li>
Reid Spencer72679252006-11-11 21:00:47 +0000[diff] [blame]128 <li><a href="#i_ptrtoint">'<tt>ptrtoint .. to</tt>' Instruction</a></li>
129 <li><a href="#i_inttoptr">'<tt>inttoptr .. to</tt>' Instruction</a></li>
Reid Spencer5c0ef472006-11-11 23:08:07 +0000[diff] [blame]130 <li><a href="#i_bitcast">'<tt>bitcast .. to</tt>' Instruction</a></li>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]131 </ol>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]132 <li><a href="#otherops">Other Operations</a>
133 <ol>
Reid Spencerf3a70a62006-11-18 21:50:54 +0000[diff] [blame]134 <li><a href="#i_icmp">'<tt>icmp</tt>' Instruction</a></li>
135 <li><a href="#i_fcmp">'<tt>fcmp</tt>' Instruction</a></li>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]136 <li><a href="#i_phi">'<tt>phi</tt>' Instruction</a></li>
Chris Lattnercc37aae2004-03-12 05:50:16 +0000[diff] [blame]137 <li><a href="#i_select">'<tt>select</tt>' Instruction</a></li>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]138 <li><a href="#i_call">'<tt>call</tt>' Instruction</a></li>
Chris Lattnerfb6977d2006-01-13 23:26:01 +0000[diff] [blame]139 <li><a href="#i_va_arg">'<tt>va_arg</tt>' Instruction</a></li>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]140 </ol>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]141 </li>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]142 </ol>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]143 </li>
Chris Lattnerd9ad5b32003-05-08 04:57:36 +0000[diff] [blame]144 <li><a href="#intrinsics">Intrinsic Functions</a>
Chris Lattnerd9ad5b32003-05-08 04:57:36 +0000[diff] [blame]145 <ol>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]146 <li><a href="#int_varargs">Variable Argument Handling Intrinsics</a>
147 <ol>
148 <li><a href="#i_va_start">'<tt>llvm.va_start</tt>' Intrinsic</a></li>
149 <li><a href="#i_va_end">'<tt>llvm.va_end</tt>' Intrinsic</a></li>
150 <li><a href="#i_va_copy">'<tt>llvm.va_copy</tt>' Intrinsic</a></li>
151 </ol>
152 </li>
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]153 <li><a href="#int_gc">Accurate Garbage Collection Intrinsics</a>
154 <ol>
155 <li><a href="#i_gcroot">'<tt>llvm.gcroot</tt>' Intrinsic</a></li>
156 <li><a href="#i_gcread">'<tt>llvm.gcread</tt>' Intrinsic</a></li>
157 <li><a href="#i_gcwrite">'<tt>llvm.gcwrite</tt>' Intrinsic</a></li>
158 </ol>
159 </li>
Chris Lattner10610642004-02-14 04:08:35 +0000[diff] [blame]160 <li><a href="#int_codegen">Code Generator Intrinsics</a>
161 <ol>
162 <li><a href="#i_returnaddress">'<tt>llvm.returnaddress</tt>' Intrinsic</a></li>
163 <li><a href="#i_frameaddress">'<tt>llvm.frameaddress</tt>' Intrinsic</a></li>
Chris Lattner57e1f392006-01-13 02:03:13 +0000[diff] [blame]164 <li><a href="#i_stacksave">'<tt>llvm.stacksave</tt>' Intrinsic</a></li>
165 <li><a href="#i_stackrestore">'<tt>llvm.stackrestore</tt>' Intrinsic</a></li>
Chris Lattner9a9d7ac2005-02-28 19:24:19 +0000[diff] [blame]166 <li><a href="#i_prefetch">'<tt>llvm.prefetch</tt>' Intrinsic</a></li>
Andrew Lenharth7f4ec3b2005-03-28 20:05:49 +0000[diff] [blame]167 <li><a href="#i_pcmarker">'<tt>llvm.pcmarker</tt>' Intrinsic</a></li>
Andrew Lenharth51b8d542005-11-11 16:47:30 +0000[diff] [blame]168 <li><a href="#i_readcyclecounter"><tt>llvm.readcyclecounter</tt>' Intrinsic</a></li>
John Criswell7123e272004-04-09 16:43:20 +0000[diff] [blame]169 </ol>
170 </li>
Chris Lattner33aec9e2004-02-12 17:01:32 +0000[diff] [blame]171 <li><a href="#int_libc">Standard C Library Intrinsics</a>
172 <ol>
Chris Lattner5b310c32006-03-03 00:07:20 +0000[diff] [blame]173 <li><a href="#i_memcpy">'<tt>llvm.memcpy.*</tt>' Intrinsic</a></li>
174 <li><a href="#i_memmove">'<tt>llvm.memmove.*</tt>' Intrinsic</a></li>
175 <li><a href="#i_memset">'<tt>llvm.memset.*</tt>' Intrinsic</a></li>
Chris Lattnerec6cb612006-01-16 22:38:59 +0000[diff] [blame]176 <li><a href="#i_sqrt">'<tt>llvm.sqrt.*</tt>' Intrinsic</a></li>
Chris Lattnerf4d252d2006-09-08 06:34:02 +0000[diff] [blame]177 <li><a href="#i_powi">'<tt>llvm.powi.*</tt>' Intrinsic</a></li>
Chris Lattner33aec9e2004-02-12 17:01:32 +0000[diff] [blame]178 </ol>
179 </li>
Nate Begeman7e36c472006-01-13 23:26:38 +0000[diff] [blame]180 <li><a href="#int_manip">Bit Manipulation Intrinsics</a>
Andrew Lenharthec370fd2005-05-03 18:01:48 +0000[diff] [blame]181 <ol>
Nate Begeman7e36c472006-01-13 23:26:38 +0000[diff] [blame]182 <li><a href="#i_bswap">'<tt>llvm.bswap.*</tt>' Intrinsics</a></li>
Chris Lattner8a886be2006-01-16 22:34:14 +0000[diff] [blame]183 <li><a href="#int_ctpop">'<tt>llvm.ctpop.*</tt>' Intrinsic </a></li>
184 <li><a href="#int_ctlz">'<tt>llvm.ctlz.*</tt>' Intrinsic </a></li>
185 <li><a href="#int_cttz">'<tt>llvm.cttz.*</tt>' Intrinsic </a></li>
Andrew Lenharthec370fd2005-05-03 18:01:48 +0000[diff] [blame]186 </ol>
187 </li>
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]188 <li><a href="#int_debugger">Debugger intrinsics</a></li>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]189 </ol>
190 </li>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]191</ol>
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]192
193<div class="doc_author">
194 <p>Written by <a href="mailto:sabre@nondot.org">Chris Lattner</a>
195 and <a href="mailto:vadve@cs.uiuc.edu">Vikram Adve</a></p>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]196</div>
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]197
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]198<!-- *********************************************************************** -->
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]199<div class="doc_section"> <a name="abstract">Abstract </a></div>
200<!-- *********************************************************************** -->
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]201
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]202<div class="doc_text">
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]203<p>This document is a reference manual for the LLVM assembly language.
204LLVM is an SSA based representation that provides type safety,
205low-level operations, flexibility, and the capability of representing
206'all' high-level languages cleanly. It is the common code
207representation used throughout all phases of the LLVM compilation
208strategy.</p>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]209</div>
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]210
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]211<!-- *********************************************************************** -->
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]212<div class="doc_section"> <a name="introduction">Introduction</a> </div>
213<!-- *********************************************************************** -->
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]214
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]215<div class="doc_text">
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]216
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]217<p>The LLVM code representation is designed to be used in three
218different forms: as an in-memory compiler IR, as an on-disk bytecode
219representation (suitable for fast loading by a Just-In-Time compiler),
220and as a human readable assembly language representation. This allows
221LLVM to provide a powerful intermediate representation for efficient
222compiler transformations and analysis, while providing a natural means
223to debug and visualize the transformations. The three different forms
224of LLVM are all equivalent. This document describes the human readable
225representation and notation.</p>
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]226
John Criswellc1f786c2005-05-13 22:25:59 +0000[diff] [blame]227<p>The LLVM representation aims to be light-weight and low-level
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]228while being expressive, typed, and extensible at the same time. It
229aims to be a "universal IR" of sorts, by being at a low enough level
230that high-level ideas may be cleanly mapped to it (similar to how
231microprocessors are "universal IR's", allowing many source languages to
232be mapped to them). By providing type information, LLVM can be used as
233the target of optimizations: for example, through pointer analysis, it
234can be proven that a C automatic variable is never accessed outside of
235the current function... allowing it to be promoted to a simple SSA
236value instead of a memory location.</p>
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]237
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]238</div>
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]239
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]240<!-- _______________________________________________________________________ -->
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]241<div class="doc_subsubsection"> <a name="wellformed">Well-Formedness</a> </div>
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]242
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]243<div class="doc_text">
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]244
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]245<p>It is important to note that this document describes 'well formed'
246LLVM assembly language. There is a difference between what the parser
247accepts and what is considered 'well formed'. For example, the
248following instruction is syntactically okay, but not well formed:</p>
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]249
250<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]251 %x = <a href="#i_add">add</a> i32 1, %x
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]252</pre>
253
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]254<p>...because the definition of <tt>%x</tt> does not dominate all of
255its uses. The LLVM infrastructure provides a verification pass that may
256be used to verify that an LLVM module is well formed. This pass is
John Criswellc1f786c2005-05-13 22:25:59 +0000[diff] [blame]257automatically run by the parser after parsing input assembly and by
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]258the optimizer before it outputs bytecode. The violations pointed out
259by the verifier pass indicate bugs in transformation passes or input to
260the parser.</p>
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]261
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]262<!-- Describe the typesetting conventions here. --> </div>
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]263
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]264<!-- *********************************************************************** -->
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]265<div class="doc_section"> <a name="identifiers">Identifiers</a> </div>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]266<!-- *********************************************************************** -->
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]267
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]268<div class="doc_text">
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]269
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]270<p>LLVM uses three different forms of identifiers, for different
271purposes:</p>
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]272
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]273<ol>
Chris Lattnere5d947b2004-12-09 16:36:40 +0000[diff] [blame]274 <li>Named values are represented as a string of characters with a '%' prefix.
275 For example, %foo, %DivisionByZero, %a.really.long.identifier. The actual
276 regular expression used is '<tt>%[a-zA-Z$._][a-zA-Z$._0-9]*</tt>'.
277 Identifiers which require other characters in their names can be surrounded
Anton Korobeynikov7f705592007-01-12 19:20:47 +0000[diff] [blame]278 with quotes. In this way, anything except a <tt>&quot;</tt> character can be used
Chris Lattnere5d947b2004-12-09 16:36:40 +0000[diff] [blame]279 in a name.</li>
280
281 <li>Unnamed values are represented as an unsigned numeric value with a '%'
282 prefix. For example, %12, %2, %44.</li>
283
Reid Spencercc16dc32004-12-09 18:02:53 +0000[diff] [blame]284 <li>Constants, which are described in a <a href="#constants">section about
285 constants</a>, below.</li>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]286</ol>
Chris Lattnere5d947b2004-12-09 16:36:40 +0000[diff] [blame]287
288<p>LLVM requires that values start with a '%' sign for two reasons: Compilers
289don't need to worry about name clashes with reserved words, and the set of
290reserved words may be expanded in the future without penalty. Additionally,
291unnamed identifiers allow a compiler to quickly come up with a temporary
292variable without having to avoid symbol table conflicts.</p>
293
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]294<p>Reserved words in LLVM are very similar to reserved words in other
Reid Spencer5c0ef472006-11-11 23:08:07 +0000[diff] [blame]295languages. There are keywords for different opcodes
296('<tt><a href="#i_add">add</a></tt>',
297 '<tt><a href="#i_bitcast">bitcast</a></tt>',
298 '<tt><a href="#i_ret">ret</a></tt>', etc...), for primitive type names ('<tt><a
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]299href="#t_void">void</a></tt>', '<tt><a href="#t_primitive">i32</a></tt>', etc...),
Chris Lattnere5d947b2004-12-09 16:36:40 +0000[diff] [blame]300and others. These reserved words cannot conflict with variable names, because
301none of them start with a '%' character.</p>
302
303<p>Here is an example of LLVM code to multiply the integer variable
304'<tt>%X</tt>' by 8:</p>
305
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]306<p>The easy way:</p>
Chris Lattnere5d947b2004-12-09 16:36:40 +0000[diff] [blame]307
308<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]309 %result = <a href="#i_mul">mul</a> i32 %X, 8
Chris Lattnere5d947b2004-12-09 16:36:40 +0000[diff] [blame]310</pre>
311
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]312<p>After strength reduction:</p>
Chris Lattnere5d947b2004-12-09 16:36:40 +0000[diff] [blame]313
314<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]315 %result = <a href="#i_shl">shl</a> i32 %X, i8 3
Chris Lattnere5d947b2004-12-09 16:36:40 +0000[diff] [blame]316</pre>
317
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]318<p>And the hard way:</p>
Chris Lattnere5d947b2004-12-09 16:36:40 +0000[diff] [blame]319
320<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]321 <a href="#i_add">add</a> i32 %X, %X <i>; yields {i32}:%0</i>
322 <a href="#i_add">add</a> i32 %0, %0 <i>; yields {i32}:%1</i>
323 %result = <a href="#i_add">add</a> i32 %1, %1
Chris Lattnere5d947b2004-12-09 16:36:40 +0000[diff] [blame]324</pre>
325
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]326<p>This last way of multiplying <tt>%X</tt> by 8 illustrates several
327important lexical features of LLVM:</p>
Chris Lattnere5d947b2004-12-09 16:36:40 +0000[diff] [blame]328
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]329<ol>
Chris Lattnere5d947b2004-12-09 16:36:40 +0000[diff] [blame]330
331 <li>Comments are delimited with a '<tt>;</tt>' and go until the end of
332 line.</li>
333
334 <li>Unnamed temporaries are created when the result of a computation is not
335 assigned to a named value.</li>
336
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]337 <li>Unnamed temporaries are numbered sequentially</li>
Chris Lattnere5d947b2004-12-09 16:36:40 +0000[diff] [blame]338
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]339</ol>
Chris Lattnere5d947b2004-12-09 16:36:40 +0000[diff] [blame]340
John Criswelle4c57cc2005-05-12 16:52:32 +0000[diff] [blame]341<p>...and it also shows a convention that we follow in this document. When
Chris Lattnere5d947b2004-12-09 16:36:40 +0000[diff] [blame]342demonstrating instructions, we will follow an instruction with a comment that
343defines the type and name of value produced. Comments are shown in italic
344text.</p>
345
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]346</div>
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]347
348<!-- *********************************************************************** -->
349<div class="doc_section"> <a name="highlevel">High Level Structure</a> </div>
350<!-- *********************************************************************** -->
351
352<!-- ======================================================================= -->
353<div class="doc_subsection"> <a name="modulestructure">Module Structure</a>
354</div>
355
356<div class="doc_text">
357
358<p>LLVM programs are composed of "Module"s, each of which is a
359translation unit of the input programs. Each module consists of
360functions, global variables, and symbol table entries. Modules may be
361combined together with the LLVM linker, which merges function (and
362global variable) definitions, resolves forward declarations, and merges
363symbol table entries. Here is an example of the "hello world" module:</p>
364
365<pre><i>; Declare the string constant as a global constant...</i>
366<a href="#identifiers">%.LC0</a> = <a href="#linkage_internal">internal</a> <a
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]367 href="#globalvars">constant</a> <a href="#t_array">[13 x i8 ]</a> c"hello world\0A\00" <i>; [13 x i8 ]*</i>
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]368
369<i>; External declaration of the puts function</i>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]370<a href="#functionstructure">declare</a> i32 %puts(i8 *) <i>; i32(i8 *)* </i>
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]371
Chris Lattner81c01f02006-06-13 03:05:47 +0000[diff] [blame]372<i>; Global variable / Function body section separator</i>
373implementation
374
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]375<i>; Definition of main function</i>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]376define i32 %main() { <i>; i32()* </i>
377 <i>; Convert [13x i8 ]* to i8 *...</i>
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]378 %cast210 = <a
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]379 href="#i_getelementptr">getelementptr</a> [13 x i8 ]* %.LC0, i64 0, i64 0 <i>; i8 *</i>
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]380
381 <i>; Call puts function to write out the string to stdout...</i>
382 <a
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]383 href="#i_call">call</a> i32 %puts(i8 * %cast210) <i>; i32</i>
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]384 <a
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]385 href="#i_ret">ret</a> i32 0<br>}<br></pre>
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]386
387<p>This example is made up of a <a href="#globalvars">global variable</a>
388named "<tt>.LC0</tt>", an external declaration of the "<tt>puts</tt>"
389function, and a <a href="#functionstructure">function definition</a>
390for "<tt>main</tt>".</p>
391
Chris Lattnere5d947b2004-12-09 16:36:40 +0000[diff] [blame]392<p>In general, a module is made up of a list of global values,
393where both functions and global variables are global values. Global values are
394represented by a pointer to a memory location (in this case, a pointer to an
395array of char, and a pointer to a function), and have one of the following <a
396href="#linkage">linkage types</a>.</p>
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]397
Chris Lattner81c01f02006-06-13 03:05:47 +0000[diff] [blame]398<p>Due to a limitation in the current LLVM assembly parser (it is limited by
399one-token lookahead), modules are split into two pieces by the "implementation"
400keyword. Global variable prototypes and definitions must occur before the
401keyword, and function definitions must occur after it. Function prototypes may
402occur either before or after it. In the future, the implementation keyword may
403become a noop, if the parser gets smarter.</p>
404
Chris Lattnere5d947b2004-12-09 16:36:40 +0000[diff] [blame]405</div>
406
407<!-- ======================================================================= -->
408<div class="doc_subsection">
409 <a name="linkage">Linkage Types</a>
410</div>
411
412<div class="doc_text">
413
414<p>
415All Global Variables and Functions have one of the following types of linkage:
416</p>
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]417
418<dl>
Chris Lattnere5d947b2004-12-09 16:36:40 +0000[diff] [blame]419
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]420 <dt><tt><b><a name="linkage_internal">internal</a></b></tt> </dt>
Chris Lattnere5d947b2004-12-09 16:36:40 +0000[diff] [blame]421
422 <dd>Global values with internal linkage are only directly accessible by
423 objects in the current module. In particular, linking code into a module with
424 an internal global value may cause the internal to be renamed as necessary to
425 avoid collisions. Because the symbol is internal to the module, all
426 references can be updated. This corresponds to the notion of the
Chris Lattner4887bd82007-01-14 06:51:48 +0000[diff] [blame]427 '<tt>static</tt>' keyword in C.
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]428 </dd>
Chris Lattnere5d947b2004-12-09 16:36:40 +0000[diff] [blame]429
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]430 <dt><tt><b><a name="linkage_linkonce">linkonce</a></b></tt>: </dt>
Chris Lattnere5d947b2004-12-09 16:36:40 +0000[diff] [blame]431
Chris Lattner4887bd82007-01-14 06:51:48 +0000[diff] [blame]432 <dd>Globals with "<tt>linkonce</tt>" linkage are merged with other globals of
433 the same name when linkage occurs. This is typically used to implement
434 inline functions, templates, or other code which must be generated in each
435 translation unit that uses it. Unreferenced <tt>linkonce</tt> globals are
436 allowed to be discarded.
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]437 </dd>
Chris Lattnere5d947b2004-12-09 16:36:40 +0000[diff] [blame]438
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]439 <dt><tt><b><a name="linkage_weak">weak</a></b></tt>: </dt>
Chris Lattnere5d947b2004-12-09 16:36:40 +0000[diff] [blame]440
441 <dd>"<tt>weak</tt>" linkage is exactly the same as <tt>linkonce</tt> linkage,
442 except that unreferenced <tt>weak</tt> globals may not be discarded. This is
Chris Lattner4887bd82007-01-14 06:51:48 +0000[diff] [blame]443 used for globals that may be emitted in multiple translation units, but that
444 are not guaranteed to be emitted into every translation unit that uses them.
445 One example of this are common globals in C, such as "<tt>int X;</tt>" at
446 global scope.
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]447 </dd>
Chris Lattnere5d947b2004-12-09 16:36:40 +0000[diff] [blame]448
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]449 <dt><tt><b><a name="linkage_appending">appending</a></b></tt>: </dt>
Chris Lattnere5d947b2004-12-09 16:36:40 +0000[diff] [blame]450
451 <dd>"<tt>appending</tt>" linkage may only be applied to global variables of
452 pointer to array type. When two global variables with appending linkage are
453 linked together, the two global arrays are appended together. This is the
454 LLVM, typesafe, equivalent of having the system linker append together
455 "sections" with identical names when .o files are linked.
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]456 </dd>
Chris Lattnere5d947b2004-12-09 16:36:40 +0000[diff] [blame]457
Anton Korobeynikov7f705592007-01-12 19:20:47 +0000[diff] [blame]458 <dt><tt><b><a name="linkage_externweak">extern_weak</a></b></tt>: </dt>
459 <dd>The semantics of this linkage follow the ELF model: the symbol is weak
460 until linked, if not linked, the symbol becomes null instead of being an
461 undefined reference.
462 </dd>
463</dl>
464
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]465 <dt><tt><b><a name="linkage_external">externally visible</a></b></tt>:</dt>
Chris Lattnere5d947b2004-12-09 16:36:40 +0000[diff] [blame]466
467 <dd>If none of the above identifiers are used, the global is externally
468 visible, meaning that it participates in linkage and can be used to resolve
469 external symbol references.
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]470 </dd>
Anton Korobeynikovb74ed072006-09-14 18:23:27 +0000[diff] [blame]471
Anton Korobeynikovb74ed072006-09-14 18:23:27 +0000[diff] [blame]472 <p>
473 The next two types of linkage are targeted for Microsoft Windows platform
474 only. They are designed to support importing (exporting) symbols from (to)
475 DLLs.
476 </p>
477
Anton Korobeynikov7f705592007-01-12 19:20:47 +0000[diff] [blame]478 <dl>
Anton Korobeynikovb74ed072006-09-14 18:23:27 +0000[diff] [blame]479 <dt><tt><b><a name="linkage_dllimport">dllimport</a></b></tt>: </dt>
480
481 <dd>"<tt>dllimport</tt>" linkage causes the compiler to reference a function
482 or variable via a global pointer to a pointer that is set up by the DLL
483 exporting the symbol. On Microsoft Windows targets, the pointer name is
484 formed by combining <code>_imp__</code> and the function or variable name.
485 </dd>
486
487 <dt><tt><b><a name="linkage_dllexport">dllexport</a></b></tt>: </dt>
488
489 <dd>"<tt>dllexport</tt>" linkage causes the compiler to provide a global
490 pointer to a pointer in a DLL, so that it can be referenced with the
491 <tt>dllimport</tt> attribute. On Microsoft Windows targets, the pointer
492 name is formed by combining <code>_imp__</code> and the function or variable
493 name.
494 </dd>
495
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]496</dl>
497
Anton Korobeynikov7f705592007-01-12 19:20:47 +0000[diff] [blame]498<p><a name="linkage_external"></a>For example, since the "<tt>.LC0</tt>"
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]499variable is defined to be internal, if another module defined a "<tt>.LC0</tt>"
500variable and was linked with this one, one of the two would be renamed,
501preventing a collision. Since "<tt>main</tt>" and "<tt>puts</tt>" are
502external (i.e., lacking any linkage declarations), they are accessible
Reid Spencerac8d2762007-01-05 00:59:10 +0000[diff] [blame]503outside of the current module.</p>
504<p>It is illegal for a function <i>declaration</i>
505to have any linkage type other than "externally visible", <tt>dllimport</tt>,
Anton Korobeynikov7f705592007-01-12 19:20:47 +0000[diff] [blame]506or <tt>extern_weak</tt>.</p>
Chris Lattnere5d947b2004-12-09 16:36:40 +0000[diff] [blame]507
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]508</div>
509
510<!-- ======================================================================= -->
511<div class="doc_subsection">
Chris Lattnerbad10ee2005-05-06 22:57:40 +0000[diff] [blame]512 <a name="callingconv">Calling Conventions</a>
513</div>
514
515<div class="doc_text">
516
517<p>LLVM <a href="#functionstructure">functions</a>, <a href="#i_call">calls</a>
518and <a href="#i_invoke">invokes</a> can all have an optional calling convention
519specified for the call. The calling convention of any pair of dynamic
520caller/callee must match, or the behavior of the program is undefined. The
521following calling conventions are supported by LLVM, and more may be added in
522the future:</p>
523
524<dl>
525 <dt><b>"<tt>ccc</tt>" - The C calling convention</b>:</dt>
526
527 <dd>This calling convention (the default if no other calling convention is
528 specified) matches the target C calling conventions. This calling convention
John Criswelle4c57cc2005-05-12 16:52:32 +0000[diff] [blame]529 supports varargs function calls and tolerates some mismatch in the declared
Reid Spencerc28d2bc2006-12-31 21:30:18 +0000[diff] [blame]530 prototype and implemented declaration of the function (as does normal C).
Chris Lattnerbad10ee2005-05-06 22:57:40 +0000[diff] [blame]531 </dd>
532
533 <dt><b>"<tt>fastcc</tt>" - The fast calling convention</b>:</dt>
534
535 <dd>This calling convention attempts to make calls as fast as possible
536 (e.g. by passing things in registers). This calling convention allows the
537 target to use whatever tricks it wants to produce fast code for the target,
Chris Lattner8cdc5bc2005-05-06 23:08:23 +0000[diff] [blame]538 without having to conform to an externally specified ABI. Implementations of
539 this convention should allow arbitrary tail call optimization to be supported.
540 This calling convention does not support varargs and requires the prototype of
541 all callees to exactly match the prototype of the function definition.
Chris Lattnerbad10ee2005-05-06 22:57:40 +0000[diff] [blame]542 </dd>
543
544 <dt><b>"<tt>coldcc</tt>" - The cold calling convention</b>:</dt>
545
546 <dd>This calling convention attempts to make code in the caller as efficient
547 as possible under the assumption that the call is not commonly executed. As
548 such, these calls often preserve all registers so that the call does not break
549 any live ranges in the caller side. This calling convention does not support
550 varargs and requires the prototype of all callees to exactly match the
551 prototype of the function definition.
552 </dd>
553
Chris Lattnercfe6b372005-05-07 01:46:40 +0000[diff] [blame]554 <dt><b>"<tt>cc &lt;<em>n</em>&gt;</tt>" - Numbered convention</b>:</dt>
Chris Lattnerbad10ee2005-05-06 22:57:40 +0000[diff] [blame]555
556 <dd>Any calling convention may be specified by number, allowing
557 target-specific calling conventions to be used. Target specific calling
558 conventions start at 64.
559 </dd>
Chris Lattnercfe6b372005-05-07 01:46:40 +0000[diff] [blame]560</dl>
Chris Lattnerbad10ee2005-05-06 22:57:40 +0000[diff] [blame]561
562<p>More calling conventions can be added/defined on an as-needed basis, to
563support pascal conventions or any other well-known target-independent
564convention.</p>
565
566</div>
567
568<!-- ======================================================================= -->
569<div class="doc_subsection">
Anton Korobeynikov8cea37b2007-01-23 12:35:46 +0000[diff] [blame]570 <a name="visibility">Visibility Styles</a>
571</div>
572
573<div class="doc_text">
574
575<p>
576All Global Variables and Functions have one of the following visibility styles:
577</p>
578
579<dl>
580 <dt><b>"<tt>default</tt>" - Default style</b>:</dt>
581
582 <dd>On ELF, default visibility means that the declaration is visible to other
583 modules and, in shared libraries, means that the declared entity may be
584 overridden. On Darwin, default visibility means that the declaration is
585 visible to other modules. Default visibility corresponds to "external
586 linkage" in the language.
587 </dd>
588
589 <dt><b>"<tt>hidden</tt>" - Hidden style</b>:</dt>
590
591 <dd>Two declarations of an object with hidden visibility refer to the same
592 object if they are in the same shared object. Usually, hidden visibility
593 indicates that the symbol will not be placed into the dynamic symbol table,
594 so no other module (executable or shared library) can reference it
595 directly.
596 </dd>
597
598</dl>
599
600</div>
601
602<!-- ======================================================================= -->
603<div class="doc_subsection">
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]604 <a name="globalvars">Global Variables</a>
605</div>
606
607<div class="doc_text">
608
Chris Lattner3689a342005-02-12 19:30:21 +0000[diff] [blame]609<p>Global variables define regions of memory allocated at compilation time
Chris Lattner88f6c462005-11-12 00:45:07 +0000[diff] [blame]610instead of run-time. Global variables may optionally be initialized, may have
611an explicit section to be placed in, and may
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]612have an optional explicit alignment specified. A
John Criswell0ec250c2005-10-24 16:17:18 +0000[diff] [blame]613variable may be defined as a global "constant," which indicates that the
Chris Lattner3689a342005-02-12 19:30:21 +0000[diff] [blame]614contents of the variable will <b>never</b> be modified (enabling better
615optimization, allowing the global data to be placed in the read-only section of
616an executable, etc). Note that variables that need runtime initialization
John Criswell0ec250c2005-10-24 16:17:18 +0000[diff] [blame]617cannot be marked "constant" as there is a store to the variable.</p>
Chris Lattner3689a342005-02-12 19:30:21 +0000[diff] [blame]618
619<p>
620LLVM explicitly allows <em>declarations</em> of global variables to be marked
621constant, even if the final definition of the global is not. This capability
622can be used to enable slightly better optimization of the program, but requires
623the language definition to guarantee that optimizations based on the
624'constantness' are valid for the translation units that do not include the
625definition.
626</p>
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]627
628<p>As SSA values, global variables define pointer values that are in
629scope (i.e. they dominate) all basic blocks in the program. Global
630variables always define a pointer to their "content" type because they
631describe a region of memory, and all memory objects in LLVM are
632accessed through pointers.</p>
633
Chris Lattner88f6c462005-11-12 00:45:07 +0000[diff] [blame]634<p>LLVM allows an explicit section to be specified for globals. If the target
635supports it, it will emit globals to the section specified.</p>
636
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]637<p>An explicit alignment may be specified for a global. If not present, or if
638the alignment is set to zero, the alignment of the global is set by the target
639to whatever it feels convenient. If an explicit alignment is specified, the
640global is forced to have at least that much alignment. All alignments must be
641a power of 2.</p>
642
Chris Lattner68027ea2007-01-14 00:27:09 +0000[diff] [blame]643<p>For example, the following defines a global with an initializer, section,
644 and alignment:</p>
645
646<pre>
647 %G = constant float 1.0, section "foo", align 4
648</pre>
649
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]650</div>
651
652
653<!-- ======================================================================= -->
654<div class="doc_subsection">
655 <a name="functionstructure">Functions</a>
656</div>
657
658<div class="doc_text">
659
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]660<p>LLVM function definitions consist of the "<tt>define</tt>" keyord,
661an optional <a href="#linkage">linkage type</a>, an optional
Anton Korobeynikov8cea37b2007-01-23 12:35:46 +0000[diff] [blame]662<a href="#visibility">visibility style</a>, an optional
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]663<a href="#callingconv">calling convention</a>, a return type, an optional
664<a href="#paramattrs">parameter attribute</a> for the return type, a function
665name, a (possibly empty) argument list (each with optional
Anton Korobeynikov8cea37b2007-01-23 12:35:46 +0000[diff] [blame]666<a href="#paramattrs">parameter attributes</a>), an optional section, an
667optional alignment, an opening curly brace, a list of basic blocks, and a
668closing curly brace.
669
670LLVM function declarations consist of the "<tt>declare</tt>" keyword, an
671optional <a href="#linkage">linkage type</a>, an optional
672<a href="#visibility">visibility style</a>, an optional
673<a href="#callingconv">calling convention</a>, a return type, an optional
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]674<a href="#paramattrs">parameter attribute</a> for the return type, a function
675name, a possibly empty list of arguments, and an optional alignment.</p>
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]676
677<p>A function definition contains a list of basic blocks, forming the CFG for
678the function. Each basic block may optionally start with a label (giving the
679basic block a symbol table entry), contains a list of instructions, and ends
680with a <a href="#terminators">terminator</a> instruction (such as a branch or
681function return).</p>
682
John Criswelle4c57cc2005-05-12 16:52:32 +0000[diff] [blame]683<p>The first basic block in a program is special in two ways: it is immediately
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]684executed on entrance to the function, and it is not allowed to have predecessor
685basic blocks (i.e. there can not be any branches to the entry block of a
686function). Because the block can have no predecessors, it also cannot have any
687<a href="#i_phi">PHI nodes</a>.</p>
688
689<p>LLVM functions are identified by their name and type signature. Hence, two
690functions with the same name but different parameter lists or return values are
Chris Lattnerd4f6b172005-03-07 22:13:59 +0000[diff] [blame]691considered different functions, and LLVM will resolve references to each
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]692appropriately.</p>
693
Chris Lattner88f6c462005-11-12 00:45:07 +0000[diff] [blame]694<p>LLVM allows an explicit section to be specified for functions. If the target
695supports it, it will emit functions to the section specified.</p>
696
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]697<p>An explicit alignment may be specified for a function. If not present, or if
698the alignment is set to zero, the alignment of the function is set by the target
699to whatever it feels convenient. If an explicit alignment is specified, the
700function is forced to have at least that much alignment. All alignments must be
701a power of 2.</p>
702
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]703</div>
704
Chris Lattner4e9aba72006-01-23 23:23:47 +0000[diff] [blame]705<!-- ======================================================================= -->
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]706<div class="doc_subsection"><a name="paramattrs">Parameter Attributes</a></div>
707<div class="doc_text">
708 <p>The return type and each parameter of a function type may have a set of
709 <i>parameter attributes</i> associated with them. Parameter attributes are
710 used to communicate additional information about the result or parameters of
711 a function. Parameter attributes are considered to be part of the function
712 type so two functions types that differ only by the parameter attributes
713 are different function types.</p>
714
Reid Spencer950e9f82007-01-15 18:27:39 +0000[diff] [blame]715 <p>Parameter attributes are simple keywords that follow the type specified. If
716 multiple parameter attributes are needed, they are space separated. For
Anton Korobeynikov7f705592007-01-12 19:20:47 +0000[diff] [blame]717 example:</p><pre>
Reid Spencer950e9f82007-01-15 18:27:39 +0000[diff] [blame]718 %someFunc = i16 (i8 sext %someParam) zext
719 %someFunc = i16 (i8 zext %someParam) zext</pre>
Anton Korobeynikov7f705592007-01-12 19:20:47 +0000[diff] [blame]720 <p>Note that the two function types above are unique because the parameter has
Reid Spencer950e9f82007-01-15 18:27:39 +0000[diff] [blame]721 a different attribute (sext in the first one, zext in the second). Also note
722 that the attribute for the function result (zext) comes immediately after the
723 argument list.</p>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]724
Anton Korobeynikov7f705592007-01-12 19:20:47 +0000[diff] [blame]725 <p>Currently, only the following parameter attributes are defined:</p>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]726 <dl>
Reid Spencer950e9f82007-01-15 18:27:39 +0000[diff] [blame]727 <dt><tt>zext</tt></dt>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]728 <dd>This indicates that the parameter should be zero extended just before
729 a call to this function.</dd>
Reid Spencer950e9f82007-01-15 18:27:39 +0000[diff] [blame]730 <dt><tt>sext</tt></dt>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]731 <dd>This indicates that the parameter should be sign extended just before
732 a call to this function.</dd>
Anton Korobeynikov34d6dea2007-01-28 14:30:45 +0000[diff] [blame]733 <dt><tt>inreg</tt></dt>
734 <dd>This indicates that the parameter should be placed in register (if
Anton Korobeynikov66a8c8c2007-01-28 15:27:21 +0000[diff] [blame]735 possible) during assembling function call. Support for this attribute is
736 target-specific</dd>
Anton Korobeynikov34d6dea2007-01-28 14:30:45 +0000[diff] [blame]737 <dt><tt>sret</tt></dt>
Anton Korobeynikov66a8c8c2007-01-28 15:27:21 +0000[diff] [blame]738 <dd>This indicates that the parameter specifies the address of a structure
739 that is the return value of the function in the source program.
740 </dd>
Anton Korobeynikov7f705592007-01-12 19:20:47 +0000[diff] [blame]741 </dl>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]742
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]743</div>
744
745<!-- ======================================================================= -->
Chris Lattner4e9aba72006-01-23 23:23:47 +0000[diff] [blame]746<div class="doc_subsection">
Chris Lattner1eeeb0c2006-04-08 04:40:53 +0000[diff] [blame]747 <a name="moduleasm">Module-Level Inline Assembly</a>
Chris Lattner4e9aba72006-01-23 23:23:47 +0000[diff] [blame]748</div>
749
750<div class="doc_text">
751<p>
752Modules may contain "module-level inline asm" blocks, which corresponds to the
753GCC "file scope inline asm" blocks. These blocks are internally concatenated by
754LLVM and treated as a single unit, but may be separated in the .ll file if
755desired. The syntax is very simple:
756</p>
757
758<div class="doc_code"><pre>
Chris Lattner52599e12006-01-24 00:37:20 +0000[diff] [blame]759 module asm "inline asm code goes here"
760 module asm "more can go here"
Chris Lattner4e9aba72006-01-23 23:23:47 +0000[diff] [blame]761</pre></div>
762
763<p>The strings can contain any character by escaping non-printable characters.
764 The escape sequence used is simply "\xx" where "xx" is the two digit hex code
765 for the number.
766</p>
767
768<p>
769 The inline asm code is simply printed to the machine code .s file when
770 assembly code is generated.
771</p>
772</div>
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]773
774
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]775<!-- *********************************************************************** -->
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]776<div class="doc_section"> <a name="typesystem">Type System</a> </div>
777<!-- *********************************************************************** -->
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]778
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]779<div class="doc_text">
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]780
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]781<p>The LLVM type system is one of the most important features of the
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]782intermediate representation. Being typed enables a number of
783optimizations to be performed on the IR directly, without having to do
784extra analyses on the side before the transformation. A strong type
785system makes it easier to read the generated code and enables novel
786analyses and transformations that are not feasible to perform on normal
787three address code representations.</p>
Chris Lattnerfa730212004-12-09 16:11:40 +0000[diff] [blame]788
789</div>
790
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]791<!-- ======================================================================= -->
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]792<div class="doc_subsection"> <a name="t_primitive">Primitive Types</a> </div>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]793<div class="doc_text">
John Criswell4457dc92004-04-09 16:48:45 +0000[diff] [blame]794<p>The primitive types are the fundamental building blocks of the LLVM
Chris Lattnerd4f6b172005-03-07 22:13:59 +0000[diff] [blame]795system. The current set of primitive types is as follows:</p>
Misha Brukmandaa4cb02004-03-01 17:47:27 +0000[diff] [blame]796
Reid Spencerd3f876c2004-11-01 08:19:36 +0000[diff] [blame]797<table class="layout">
798 <tr class="layout">
799 <td class="left">
800 <table>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]801 <tbody>
Reid Spencerd3f876c2004-11-01 08:19:36 +0000[diff] [blame]802 <tr><th>Type</th><th>Description</th></tr>
803 <tr><td><tt>void</tt></td><td>No value</td></tr>
Chris Lattner3b19d652007-01-15 01:54:13 +0000[diff] [blame]804 <tr><td><tt>i8</tt></td><td>8-bit value</td></tr>
805 <tr><td><tt>i32</tt></td><td>32-bit value</td></tr>
Misha Brukmancfa87bc2005-04-22 18:02:52 +0000[diff] [blame]806 <tr><td><tt>float</tt></td><td>32-bit floating point value</td></tr>
Reid Spencerd3f876c2004-11-01 08:19:36 +0000[diff] [blame]807 <tr><td><tt>label</tt></td><td>Branch destination</td></tr>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]808 </tbody>
809 </table>
Reid Spencerd3f876c2004-11-01 08:19:36 +0000[diff] [blame]810 </td>
811 <td class="right">
812 <table>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]813 <tbody>
Reid Spencerd3f876c2004-11-01 08:19:36 +0000[diff] [blame]814 <tr><th>Type</th><th>Description</th></tr>
Reid Spencerc78f3372007-01-12 03:35:51 +0000[diff] [blame]815 <tr><td><tt>i1</tt></td><td>True or False value</td></tr>
Chris Lattner3b19d652007-01-15 01:54:13 +0000[diff] [blame]816 <tr><td><tt>i16</tt></td><td>16-bit value</td></tr>
817 <tr><td><tt>i64</tt></td><td>64-bit value</td></tr>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]818 <tr><td><tt>double</tt></td><td>64-bit floating point value</td></tr>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]819 </tbody>
820 </table>
Reid Spencerd3f876c2004-11-01 08:19:36 +0000[diff] [blame]821 </td>
822 </tr>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]823</table>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]824</div>
Reid Spencerd3f876c2004-11-01 08:19:36 +0000[diff] [blame]825
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]826<!-- _______________________________________________________________________ -->
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]827<div class="doc_subsubsection"> <a name="t_classifications">Type
828Classifications</a> </div>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]829<div class="doc_text">
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]830<p>These different primitive types fall into a few useful
831classifications:</p>
Misha Brukmandaa4cb02004-03-01 17:47:27 +0000[diff] [blame]832
833<table border="1" cellspacing="0" cellpadding="4">
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]834 <tbody>
Reid Spencerd3f876c2004-11-01 08:19:36 +0000[diff] [blame]835 <tr><th>Classification</th><th>Types</th></tr>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]836 <tr>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]837 <td><a name="t_integer">integer</a></td>
Chris Lattner3b19d652007-01-15 01:54:13 +0000[diff] [blame]838 <td><tt>i1, i8, i16, i32, i64</tt></td>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]839 </tr>
840 <tr>
841 <td><a name="t_floating">floating point</a></td>
842 <td><tt>float, double</tt></td>
843 </tr>
844 <tr>
845 <td><a name="t_firstclass">first class</a></td>
Reid Spencerc78f3372007-01-12 03:35:51 +0000[diff] [blame]846 <td><tt>i1, i8, i16, i32, i64, float, double, <br/>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]847 <a href="#t_pointer">pointer</a>,<a href="#t_packed">packed</a></tt>
848 </td>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]849 </tr>
850 </tbody>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]851</table>
Misha Brukmandaa4cb02004-03-01 17:47:27 +0000[diff] [blame]852
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]853<p>The <a href="#t_firstclass">first class</a> types are perhaps the
854most important. Values of these types are the only ones which can be
855produced by instructions, passed as arguments, or used as operands to
856instructions. This means that all structures and arrays must be
857manipulated either by pointer or by component.</p>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]858</div>
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]859
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]860<!-- ======================================================================= -->
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]861<div class="doc_subsection"> <a name="t_derived">Derived Types</a> </div>
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]862
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]863<div class="doc_text">
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]864
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]865<p>The real power in LLVM comes from the derived types in the system.
866This is what allows a programmer to represent arrays, functions,
867pointers, and other useful types. Note that these derived types may be
868recursive: For example, it is possible to have a two dimensional array.</p>
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]869
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]870</div>
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]871
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]872<!-- _______________________________________________________________________ -->
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]873<div class="doc_subsubsection"> <a name="t_array">Array Type</a> </div>
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]874
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]875<div class="doc_text">
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]876
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]877<h5>Overview:</h5>
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]878
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]879<p>The array type is a very simple derived type that arranges elements
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]880sequentially in memory. The array type requires a size (number of
881elements) and an underlying data type.</p>
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]882
Chris Lattner7faa8832002-04-14 06:13:44 +0000[diff] [blame]883<h5>Syntax:</h5>
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]884
885<pre>
886 [&lt;# elements&gt; x &lt;elementtype&gt;]
887</pre>
888
John Criswelle4c57cc2005-05-12 16:52:32 +0000[diff] [blame]889<p>The number of elements is a constant integer value; elementtype may
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]890be any type with a size.</p>
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]891
Chris Lattner7faa8832002-04-14 06:13:44 +0000[diff] [blame]892<h5>Examples:</h5>
Reid Spencerd3f876c2004-11-01 08:19:36 +0000[diff] [blame]893<table class="layout">
894 <tr class="layout">
895 <td class="left">
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]896 <tt>[40 x i32 ]</tt><br/>
897 <tt>[41 x i32 ]</tt><br/>
Reid Spencera5173382007-01-04 16:43:23 +0000[diff] [blame]898 <tt>[40 x i8]</tt><br/>
Reid Spencerd3f876c2004-11-01 08:19:36 +0000[diff] [blame]899 </td>
900 <td class="left">
Reid Spencera5173382007-01-04 16:43:23 +0000[diff] [blame]901 Array of 40 32-bit integer values.<br/>
902 Array of 41 32-bit integer values.<br/>
903 Array of 40 8-bit integer values.<br/>
Reid Spencerd3f876c2004-11-01 08:19:36 +0000[diff] [blame]904 </td>
905 </tr>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]906</table>
Reid Spencerd3f876c2004-11-01 08:19:36 +0000[diff] [blame]907<p>Here are some examples of multidimensional arrays:</p>
908<table class="layout">
909 <tr class="layout">
910 <td class="left">
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]911 <tt>[3 x [4 x i32]]</tt><br/>
Reid Spencerd3f876c2004-11-01 08:19:36 +0000[diff] [blame]912 <tt>[12 x [10 x float]]</tt><br/>
Reid Spencera5173382007-01-04 16:43:23 +0000[diff] [blame]913 <tt>[2 x [3 x [4 x i16]]]</tt><br/>
Reid Spencerd3f876c2004-11-01 08:19:36 +0000[diff] [blame]914 </td>
915 <td class="left">
Reid Spencera5173382007-01-04 16:43:23 +0000[diff] [blame]916 3x4 array of 32-bit integer values.<br/>
Reid Spencerd3f876c2004-11-01 08:19:36 +0000[diff] [blame]917 12x10 array of single precision floating point values.<br/>
Reid Spencera5173382007-01-04 16:43:23 +0000[diff] [blame]918 2x3x4 array of 16-bit integer values.<br/>
Reid Spencerd3f876c2004-11-01 08:19:36 +0000[diff] [blame]919 </td>
920 </tr>
921</table>
Chris Lattnere67a9512005-06-24 17:22:57 +0000[diff] [blame]922
John Criswell0ec250c2005-10-24 16:17:18 +0000[diff] [blame]923<p>Note that 'variable sized arrays' can be implemented in LLVM with a zero
924length array. Normally, accesses past the end of an array are undefined in
Chris Lattnere67a9512005-06-24 17:22:57 +0000[diff] [blame]925LLVM (e.g. it is illegal to access the 5th element of a 3 element array).
926As a special case, however, zero length arrays are recognized to be variable
927length. This allows implementation of 'pascal style arrays' with the LLVM
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]928type "{ i32, [0 x float]}", for example.</p>
Chris Lattnere67a9512005-06-24 17:22:57 +0000[diff] [blame]929
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]930</div>
Reid Spencerd3f876c2004-11-01 08:19:36 +0000[diff] [blame]931
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]932<!-- _______________________________________________________________________ -->
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]933<div class="doc_subsubsection"> <a name="t_function">Function Type</a> </div>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]934<div class="doc_text">
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]935<h5>Overview:</h5>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]936<p>The function type can be thought of as a function signature. It
937consists of a return type and a list of formal parameter types.
John Criswell009900b2003-11-25 21:45:46 +0000[diff] [blame]938Function types are usually used to build virtual function tables
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]939(which are structures of pointers to functions), for indirect function
940calls, and when defining a function.</p>
John Criswell009900b2003-11-25 21:45:46 +0000[diff] [blame]941<p>
942The return type of a function type cannot be an aggregate type.
943</p>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]944<h5>Syntax:</h5>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]945<pre> &lt;returntype&gt; (&lt;parameter list&gt;)<br></pre>
John Criswell0ec250c2005-10-24 16:17:18 +0000[diff] [blame]946<p>...where '<tt>&lt;parameter list&gt;</tt>' is a comma-separated list of type
Misha Brukmanc24b7582004-08-12 20:16:08 +0000[diff] [blame]947specifiers. Optionally, the parameter list may include a type <tt>...</tt>,
Chris Lattner27f71f22003-09-03 00:41:47 +0000[diff] [blame]948which indicates that the function takes a variable number of arguments.
949Variable argument functions can access their arguments with the <a
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]950 href="#int_varargs">variable argument handling intrinsic</a> functions.</p>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]951<h5>Examples:</h5>
Reid Spencerd3f876c2004-11-01 08:19:36 +0000[diff] [blame]952<table class="layout">
953 <tr class="layout">
Reid Spencer92f82302006-12-31 07:18:34 +0000[diff] [blame]954 <td class="left"><tt>i32 (i32)</tt></td>
955 <td class="left">function taking an <tt>i32</tt>, returning an <tt>i32</tt>
Reid Spencerd3f876c2004-11-01 08:19:36 +0000[diff] [blame]956 </td>
Reid Spencer92f82302006-12-31 07:18:34 +0000[diff] [blame]957 </tr><tr class="layout">
Reid Spencer7bf214d2007-01-15 18:28:34 +0000[diff] [blame]958 <td class="left"><tt>float&nbsp;(i16&nbsp;sext,&nbsp;i32&nbsp;*)&nbsp;*
Reid Spencerf17a0b72006-12-31 07:20:23 +0000[diff] [blame]959 </tt></td>
Reid Spencer92f82302006-12-31 07:18:34 +0000[diff] [blame]960 <td class="left"><a href="#t_pointer">Pointer</a> to a function that takes
961 an <tt>i16</tt> that should be sign extended and a
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]962 <a href="#t_pointer">pointer</a> to <tt>i32</tt>, returning
Reid Spencer92f82302006-12-31 07:18:34 +0000[diff] [blame]963 <tt>float</tt>.
964 </td>
965 </tr><tr class="layout">
966 <td class="left"><tt>i32 (i8*, ...)</tt></td>
967 <td class="left">A vararg function that takes at least one
Reid Spencera5173382007-01-04 16:43:23 +0000[diff] [blame]968 <a href="#t_pointer">pointer</a> to <tt>i8 </tt> (char in C),
Reid Spencer92f82302006-12-31 07:18:34 +0000[diff] [blame]969 which returns an integer. This is the signature for <tt>printf</tt> in
970 LLVM.
Reid Spencerd3f876c2004-11-01 08:19:36 +0000[diff] [blame]971 </td>
972 </tr>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]973</table>
Misha Brukmandaa4cb02004-03-01 17:47:27 +0000[diff] [blame]974
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]975</div>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]976<!-- _______________________________________________________________________ -->
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]977<div class="doc_subsubsection"> <a name="t_struct">Structure Type</a> </div>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]978<div class="doc_text">
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]979<h5>Overview:</h5>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]980<p>The structure type is used to represent a collection of data members
981together in memory. The packing of the field types is defined to match
982the ABI of the underlying processor. The elements of a structure may
983be any type that has a size.</p>
984<p>Structures are accessed using '<tt><a href="#i_load">load</a></tt>
985and '<tt><a href="#i_store">store</a></tt>' by getting a pointer to a
986field with the '<tt><a href="#i_getelementptr">getelementptr</a></tt>'
987instruction.</p>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]988<h5>Syntax:</h5>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]989<pre> { &lt;type list&gt; }<br></pre>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]990<h5>Examples:</h5>
Reid Spencerd3f876c2004-11-01 08:19:36 +0000[diff] [blame]991<table class="layout">
992 <tr class="layout">
993 <td class="left">
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]994 <tt>{ i32, i32, i32 }</tt><br/>
995 <tt>{ float, i32 (i32) * }</tt><br/>
Reid Spencerd3f876c2004-11-01 08:19:36 +0000[diff] [blame]996 </td>
997 <td class="left">
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]998 a triple of three <tt>i32</tt> values<br/>
Reid Spencerd3f876c2004-11-01 08:19:36 +0000[diff] [blame]999 A pair, where the first element is a <tt>float</tt> and the second element
1000 is a <a href="#t_pointer">pointer</a> to a <a href="#t_function">function</a>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]1001 that takes an <tt>i32</tt>, returning an <tt>i32</tt>.<br/>
Reid Spencerd3f876c2004-11-01 08:19:36 +0000[diff] [blame]1002 </td>
1003 </tr>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1004</table>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1005</div>
Reid Spencerd3f876c2004-11-01 08:19:36 +0000[diff] [blame]1006
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1007<!-- _______________________________________________________________________ -->
Andrew Lenharth75e10682006-12-08 17:13:00 +0000[diff] [blame]1008<div class="doc_subsubsection"> <a name="t_pstruct">Packed Structure Type</a>
1009</div>
1010<div class="doc_text">
1011<h5>Overview:</h5>
1012<p>The packed structure type is used to represent a collection of data members
1013together in memory. There is no padding between fields. Further, the alignment
1014of a packed structure is 1 byte. The elements of a packed structure may
1015be any type that has a size.</p>
1016<p>Structures are accessed using '<tt><a href="#i_load">load</a></tt>
1017and '<tt><a href="#i_store">store</a></tt>' by getting a pointer to a
1018field with the '<tt><a href="#i_getelementptr">getelementptr</a></tt>'
1019instruction.</p>
1020<h5>Syntax:</h5>
1021<pre> &lt; { &lt;type list&gt; } &gt; <br></pre>
1022<h5>Examples:</h5>
1023<table class="layout">
1024 <tr class="layout">
1025 <td class="left">
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]1026 <tt> &lt; { i32, i32, i32 } &gt; </tt><br/>
1027 <tt> &lt; { float, i32 (i32) * } &gt; </tt><br/>
Andrew Lenharth75e10682006-12-08 17:13:00 +0000[diff] [blame]1028 </td>
1029 <td class="left">
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]1030 a triple of three <tt>i32</tt> values<br/>
Andrew Lenharth75e10682006-12-08 17:13:00 +0000[diff] [blame]1031 A pair, where the first element is a <tt>float</tt> and the second element
1032 is a <a href="#t_pointer">pointer</a> to a <a href="#t_function">function</a>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]1033 that takes an <tt>i32</tt>, returning an <tt>i32</tt>.<br/>
Andrew Lenharth75e10682006-12-08 17:13:00 +0000[diff] [blame]1034 </td>
1035 </tr>
1036</table>
1037</div>
1038
1039<!-- _______________________________________________________________________ -->
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1040<div class="doc_subsubsection"> <a name="t_pointer">Pointer Type</a> </div>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1041<div class="doc_text">
Chris Lattner7faa8832002-04-14 06:13:44 +0000[diff] [blame]1042<h5>Overview:</h5>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1043<p>As in many languages, the pointer type represents a pointer or
1044reference to another object, which must live in memory.</p>
Chris Lattner7faa8832002-04-14 06:13:44 +0000[diff] [blame]1045<h5>Syntax:</h5>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1046<pre> &lt;type&gt; *<br></pre>
Chris Lattner7faa8832002-04-14 06:13:44 +0000[diff] [blame]1047<h5>Examples:</h5>
Reid Spencerd3f876c2004-11-01 08:19:36 +0000[diff] [blame]1048<table class="layout">
1049 <tr class="layout">
1050 <td class="left">
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]1051 <tt>[4x i32]*</tt><br/>
1052 <tt>i32 (i32 *) *</tt><br/>
Reid Spencerd3f876c2004-11-01 08:19:36 +0000[diff] [blame]1053 </td>
1054 <td class="left">
1055 A <a href="#t_pointer">pointer</a> to <a href="#t_array">array</a> of
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]1056 four <tt>i32</tt> values<br/>
Reid Spencerd3f876c2004-11-01 08:19:36 +0000[diff] [blame]1057 A <a href="#t_pointer">pointer</a> to a <a
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]1058 href="#t_function">function</a> that takes an <tt>i32*</tt>, returning an
1059 <tt>i32</tt>.<br/>
Reid Spencerd3f876c2004-11-01 08:19:36 +0000[diff] [blame]1060 </td>
1061 </tr>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1062</table>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1063</div>
Reid Spencerd3f876c2004-11-01 08:19:36 +0000[diff] [blame]1064
Chris Lattnera58561b2004-08-12 19:12:28 +0000[diff] [blame]1065<!-- _______________________________________________________________________ -->
1066<div class="doc_subsubsection"> <a name="t_packed">Packed Type</a> </div>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1067<div class="doc_text">
Chris Lattner69c11bb2005-04-25 17:34:15 +0000[diff] [blame]1068
Chris Lattnera58561b2004-08-12 19:12:28 +0000[diff] [blame]1069<h5>Overview:</h5>
Chris Lattner69c11bb2005-04-25 17:34:15 +0000[diff] [blame]1070
Chris Lattnera58561b2004-08-12 19:12:28 +0000[diff] [blame]1071<p>A packed type is a simple derived type that represents a vector
1072of elements. Packed types are used when multiple primitive data
1073are operated in parallel using a single instruction (SIMD).
1074A packed type requires a size (number of
Chris Lattnerb8d172f2005-11-10 01:44:22 +0000[diff] [blame]1075elements) and an underlying primitive data type. Vectors must have a power
1076of two length (1, 2, 4, 8, 16 ...). Packed types are
Chris Lattnera58561b2004-08-12 19:12:28 +0000[diff] [blame]1077considered <a href="#t_firstclass">first class</a>.</p>
Chris Lattner69c11bb2005-04-25 17:34:15 +0000[diff] [blame]1078
Chris Lattnera58561b2004-08-12 19:12:28 +0000[diff] [blame]1079<h5>Syntax:</h5>
Chris Lattner69c11bb2005-04-25 17:34:15 +0000[diff] [blame]1080
1081<pre>
1082 &lt; &lt;# elements&gt; x &lt;elementtype&gt; &gt;
1083</pre>
1084
John Criswellc1f786c2005-05-13 22:25:59 +0000[diff] [blame]1085<p>The number of elements is a constant integer value; elementtype may
Chris Lattner3b19d652007-01-15 01:54:13 +0000[diff] [blame]1086be any integer or floating point type.</p>
Chris Lattner69c11bb2005-04-25 17:34:15 +0000[diff] [blame]1087
Chris Lattnera58561b2004-08-12 19:12:28 +0000[diff] [blame]1088<h5>Examples:</h5>
Chris Lattner69c11bb2005-04-25 17:34:15 +0000[diff] [blame]1089
Reid Spencerd3f876c2004-11-01 08:19:36 +0000[diff] [blame]1090<table class="layout">
1091 <tr class="layout">
1092 <td class="left">
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]1093 <tt>&lt;4 x i32&gt;</tt><br/>
Reid Spencerd3f876c2004-11-01 08:19:36 +0000[diff] [blame]1094 <tt>&lt;8 x float&gt;</tt><br/>
Reid Spencera5173382007-01-04 16:43:23 +0000[diff] [blame]1095 <tt>&lt;2 x i64&gt;</tt><br/>
Reid Spencerd3f876c2004-11-01 08:19:36 +0000[diff] [blame]1096 </td>
1097 <td class="left">
Reid Spencera5173382007-01-04 16:43:23 +0000[diff] [blame]1098 Packed vector of 4 32-bit integer values.<br/>
Reid Spencerd3f876c2004-11-01 08:19:36 +0000[diff] [blame]1099 Packed vector of 8 floating-point values.<br/>
Reid Spencera5173382007-01-04 16:43:23 +0000[diff] [blame]1100 Packed vector of 2 64-bit integer values.<br/>
Reid Spencerd3f876c2004-11-01 08:19:36 +0000[diff] [blame]1101 </td>
1102 </tr>
1103</table>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1104</div>
1105
Chris Lattner69c11bb2005-04-25 17:34:15 +0000[diff] [blame]1106<!-- _______________________________________________________________________ -->
1107<div class="doc_subsubsection"> <a name="t_opaque">Opaque Type</a> </div>
1108<div class="doc_text">
1109
1110<h5>Overview:</h5>
1111
1112<p>Opaque types are used to represent unknown types in the system. This
1113corresponds (for example) to the C notion of a foward declared structure type.
1114In LLVM, opaque types can eventually be resolved to any type (not just a
1115structure type).</p>
1116
1117<h5>Syntax:</h5>
1118
1119<pre>
1120 opaque
1121</pre>
1122
1123<h5>Examples:</h5>
1124
1125<table class="layout">
1126 <tr class="layout">
1127 <td class="left">
1128 <tt>opaque</tt>
1129 </td>
1130 <td class="left">
1131 An opaque type.<br/>
1132 </td>
1133 </tr>
1134</table>
1135</div>
1136
1137
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]1138<!-- *********************************************************************** -->
1139<div class="doc_section"> <a name="constants">Constants</a> </div>
1140<!-- *********************************************************************** -->
1141
1142<div class="doc_text">
1143
1144<p>LLVM has several different basic types of constants. This section describes
1145them all and their syntax.</p>
1146
1147</div>
1148
1149<!-- ======================================================================= -->
Reid Spencercc16dc32004-12-09 18:02:53 +0000[diff] [blame]1150<div class="doc_subsection"><a name="simpleconstants">Simple Constants</a></div>
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]1151
1152<div class="doc_text">
1153
1154<dl>
1155 <dt><b>Boolean constants</b></dt>
1156
1157 <dd>The two strings '<tt>true</tt>' and '<tt>false</tt>' are both valid
Reid Spencerc78f3372007-01-12 03:35:51 +0000[diff] [blame]1158 constants of the <tt><a href="#t_primitive">i1</a></tt> type.
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]1159 </dd>
1160
1161 <dt><b>Integer constants</b></dt>
1162
Reid Spencercc16dc32004-12-09 18:02:53 +0000[diff] [blame]1163 <dd>Standard integers (such as '4') are constants of the <a
Reid Spencera5173382007-01-04 16:43:23 +0000[diff] [blame]1164 href="#t_integer">integer</a> type. Negative numbers may be used with
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]1165 integer types.
1166 </dd>
1167
1168 <dt><b>Floating point constants</b></dt>
1169
1170 <dd>Floating point constants use standard decimal notation (e.g. 123.421),
1171 exponential notation (e.g. 1.23421e+2), or a more precise hexadecimal
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]1172 notation (see below). Floating point constants must have a <a
1173 href="#t_floating">floating point</a> type. </dd>
1174
1175 <dt><b>Null pointer constants</b></dt>
1176
John Criswell9e2485c2004-12-10 15:51:16 +0000[diff] [blame]1177 <dd>The identifier '<tt>null</tt>' is recognized as a null pointer constant
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]1178 and must be of <a href="#t_pointer">pointer type</a>.</dd>
1179
1180</dl>
1181
John Criswell9e2485c2004-12-10 15:51:16 +0000[diff] [blame]1182<p>The one non-intuitive notation for constants is the optional hexadecimal form
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]1183of floating point constants. For example, the form '<tt>double
11840x432ff973cafa8000</tt>' is equivalent to (but harder to read than) '<tt>double
11854.5e+15</tt>'. The only time hexadecimal floating point constants are required
Reid Spencercc16dc32004-12-09 18:02:53 +0000[diff] [blame]1186(and the only time that they are generated by the disassembler) is when a
1187floating point constant must be emitted but it cannot be represented as a
1188decimal floating point number. For example, NaN's, infinities, and other
1189special values are represented in their IEEE hexadecimal format so that
1190assembly and disassembly do not cause any bits to change in the constants.</p>
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]1191
1192</div>
1193
1194<!-- ======================================================================= -->
1195<div class="doc_subsection"><a name="aggregateconstants">Aggregate Constants</a>
1196</div>
1197
1198<div class="doc_text">
Chris Lattnerd4f6b172005-03-07 22:13:59 +0000[diff] [blame]1199<p>Aggregate constants arise from aggregation of simple constants
1200and smaller aggregate constants.</p>
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]1201
1202<dl>
1203 <dt><b>Structure constants</b></dt>
1204
1205 <dd>Structure constants are represented with notation similar to structure
1206 type definitions (a comma separated list of elements, surrounded by braces
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]1207 (<tt>{}</tt>)). For example: "<tt>{ i32 4, float 17.0, i32* %G }</tt>",
1208 where "<tt>%G</tt>" is declared as "<tt>%G = external global i32</tt>". Structure constants
Chris Lattnerd4f6b172005-03-07 22:13:59 +0000[diff] [blame]1209 must have <a href="#t_struct">structure type</a>, and the number and
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]1210 types of elements must match those specified by the type.
1211 </dd>
1212
1213 <dt><b>Array constants</b></dt>
1214
1215 <dd>Array constants are represented with notation similar to array type
1216 definitions (a comma separated list of elements, surrounded by square brackets
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]1217 (<tt>[]</tt>)). For example: "<tt>[ i32 42, i32 11, i32 74 ]</tt>". Array
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]1218 constants must have <a href="#t_array">array type</a>, and the number and
1219 types of elements must match those specified by the type.
1220 </dd>
1221
1222 <dt><b>Packed constants</b></dt>
1223
1224 <dd>Packed constants are represented with notation similar to packed type
1225 definitions (a comma separated list of elements, surrounded by
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]1226 less-than/greater-than's (<tt>&lt;&gt;</tt>)). For example: "<tt>&lt; i32 42,
1227 i32 11, i32 74, i32 100 &gt;</tt>". Packed constants must have <a
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]1228 href="#t_packed">packed type</a>, and the number and types of elements must
1229 match those specified by the type.
1230 </dd>
1231
1232 <dt><b>Zero initialization</b></dt>
1233
1234 <dd>The string '<tt>zeroinitializer</tt>' can be used to zero initialize a
1235 value to zero of <em>any</em> type, including scalar and aggregate types.
1236 This is often used to avoid having to print large zero initializers (e.g. for
John Criswell0ec250c2005-10-24 16:17:18 +0000[diff] [blame]1237 large arrays) and is always exactly equivalent to using explicit zero
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]1238 initializers.
1239 </dd>
1240</dl>
1241
1242</div>
1243
1244<!-- ======================================================================= -->
1245<div class="doc_subsection">
1246 <a name="globalconstants">Global Variable and Function Addresses</a>
1247</div>
1248
1249<div class="doc_text">
1250
1251<p>The addresses of <a href="#globalvars">global variables</a> and <a
1252href="#functionstructure">functions</a> are always implicitly valid (link-time)
John Criswell9e2485c2004-12-10 15:51:16 +0000[diff] [blame]1253constants. These constants are explicitly referenced when the <a
1254href="#identifiers">identifier for the global</a> is used and always have <a
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]1255href="#t_pointer">pointer</a> type. For example, the following is a legal LLVM
1256file:</p>
1257
1258<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]1259 %X = global i32 17
1260 %Y = global i32 42
1261 %Z = global [2 x i32*] [ i32* %X, i32* %Y ]
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]1262</pre>
1263
1264</div>
1265
1266<!-- ======================================================================= -->
Reid Spencer2dc45b82004-12-09 18:13:12 +0000[diff] [blame]1267<div class="doc_subsection"><a name="undefvalues">Undefined Values</a></div>
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]1268<div class="doc_text">
Reid Spencer2dc45b82004-12-09 18:13:12 +0000[diff] [blame]1269 <p>The string '<tt>undef</tt>' is recognized as a type-less constant that has
John Criswellc1f786c2005-05-13 22:25:59 +0000[diff] [blame]1270 no specific value. Undefined values may be of any type and be used anywhere
Reid Spencer2dc45b82004-12-09 18:13:12 +0000[diff] [blame]1271 a constant is permitted.</p>
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]1272
Reid Spencer2dc45b82004-12-09 18:13:12 +0000[diff] [blame]1273 <p>Undefined values indicate to the compiler that the program is well defined
1274 no matter what value is used, giving the compiler more freedom to optimize.
1275 </p>
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]1276</div>
1277
1278<!-- ======================================================================= -->
1279<div class="doc_subsection"><a name="constantexprs">Constant Expressions</a>
1280</div>
1281
1282<div class="doc_text">
1283
1284<p>Constant expressions are used to allow expressions involving other constants
1285to be used as constants. Constant expressions may be of any <a
John Criswellc1f786c2005-05-13 22:25:59 +0000[diff] [blame]1286href="#t_firstclass">first class</a> type and may involve any LLVM operation
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]1287that does not have side effects (e.g. load and call are not supported). The
1288following is the syntax for constant expressions:</p>
1289
1290<dl>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]1291 <dt><b><tt>trunc ( CST to TYPE )</tt></b></dt>
1292 <dd>Truncate a constant to another type. The bit size of CST must be larger
Chris Lattner3b19d652007-01-15 01:54:13 +0000[diff] [blame]1293 than the bit size of TYPE. Both types must be integers.</dd>
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]1294
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]1295 <dt><b><tt>zext ( CST to TYPE )</tt></b></dt>
1296 <dd>Zero extend a constant to another type. The bit size of CST must be
Chris Lattner3b19d652007-01-15 01:54:13 +0000[diff] [blame]1297 smaller or equal to the bit size of TYPE. Both types must be integers.</dd>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]1298
1299 <dt><b><tt>sext ( CST to TYPE )</tt></b></dt>
1300 <dd>Sign extend a constant to another type. The bit size of CST must be
Chris Lattner3b19d652007-01-15 01:54:13 +0000[diff] [blame]1301 smaller or equal to the bit size of TYPE. Both types must be integers.</dd>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]1302
1303 <dt><b><tt>fptrunc ( CST to TYPE )</tt></b></dt>
1304 <dd>Truncate a floating point constant to another floating point type. The
1305 size of CST must be larger than the size of TYPE. Both types must be
1306 floating point.</dd>
1307
1308 <dt><b><tt>fpext ( CST to TYPE )</tt></b></dt>
1309 <dd>Floating point extend a constant to another type. The size of CST must be
1310 smaller or equal to the size of TYPE. Both types must be floating point.</dd>
1311
1312 <dt><b><tt>fp2uint ( CST to TYPE )</tt></b></dt>
1313 <dd>Convert a floating point constant to the corresponding unsigned integer
1314 constant. TYPE must be an integer type. CST must be floating point. If the
1315 value won't fit in the integer type, the results are undefined.</dd>
1316
Reid Spencerd4448792006-11-09 23:03:26 +0000[diff] [blame]1317 <dt><b><tt>fptosi ( CST to TYPE )</tt></b></dt>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]1318 <dd>Convert a floating point constant to the corresponding signed integer
1319 constant. TYPE must be an integer type. CST must be floating point. If the
1320 value won't fit in the integer type, the results are undefined.</dd>
1321
Reid Spencerd4448792006-11-09 23:03:26 +0000[diff] [blame]1322 <dt><b><tt>uitofp ( CST to TYPE )</tt></b></dt>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]1323 <dd>Convert an unsigned integer constant to the corresponding floating point
1324 constant. TYPE must be floating point. CST must be of integer type. If the
1325 value won't fit in the floating point type, the results are undefined.</dd>
1326
Reid Spencerd4448792006-11-09 23:03:26 +0000[diff] [blame]1327 <dt><b><tt>sitofp ( CST to TYPE )</tt></b></dt>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]1328 <dd>Convert a signed integer constant to the corresponding floating point
1329 constant. TYPE must be floating point. CST must be of integer type. If the
1330 value won't fit in the floating point type, the results are undefined.</dd>
1331
Reid Spencer5c0ef472006-11-11 23:08:07 +0000[diff] [blame]1332 <dt><b><tt>ptrtoint ( CST to TYPE )</tt></b></dt>
1333 <dd>Convert a pointer typed constant to the corresponding integer constant
1334 TYPE must be an integer type. CST must be of pointer type. The CST value is
1335 zero extended, truncated, or unchanged to make it fit in TYPE.</dd>
1336
1337 <dt><b><tt>inttoptr ( CST to TYPE )</tt></b></dt>
1338 <dd>Convert a integer constant to a pointer constant. TYPE must be a
1339 pointer type. CST must be of integer type. The CST value is zero extended,
1340 truncated, or unchanged to make it fit in a pointer size. This one is
1341 <i>really</i> dangerous!</dd>
1342
1343 <dt><b><tt>bitcast ( CST to TYPE )</tt></b></dt>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]1344 <dd>Convert a constant, CST, to another TYPE. The size of CST and TYPE must be
1345 identical (same number of bits). The conversion is done as if the CST value
1346 was stored to memory and read back as TYPE. In other words, no bits change
Reid Spencer5c0ef472006-11-11 23:08:07 +0000[diff] [blame]1347 with this operator, just the type. This can be used for conversion of
1348 packed types to any other type, as long as they have the same bit width. For
1349 pointers it is only valid to cast to another pointer type.
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]1350 </dd>
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]1351
1352 <dt><b><tt>getelementptr ( CSTPTR, IDX0, IDX1, ... )</tt></b></dt>
1353
1354 <dd>Perform the <a href="#i_getelementptr">getelementptr operation</a> on
1355 constants. As with the <a href="#i_getelementptr">getelementptr</a>
1356 instruction, the index list may have zero or more indexes, which are required
1357 to make sense for the type of "CSTPTR".</dd>
1358
Robert Bocchino9fbe1452006-01-10 19:31:34 +0000[diff] [blame]1359 <dt><b><tt>select ( COND, VAL1, VAL2 )</tt></b></dt>
1360
1361 <dd>Perform the <a href="#i_select">select operation</a> on
Reid Spencer01c42592006-12-04 19:23:19 +0000[diff] [blame]1362 constants.</dd>
1363
1364 <dt><b><tt>icmp COND ( VAL1, VAL2 )</tt></b></dt>
1365 <dd>Performs the <a href="#i_icmp">icmp operation</a> on constants.</dd>
1366
1367 <dt><b><tt>fcmp COND ( VAL1, VAL2 )</tt></b></dt>
1368 <dd>Performs the <a href="#i_fcmp">fcmp operation</a> on constants.</dd>
Robert Bocchino9fbe1452006-01-10 19:31:34 +0000[diff] [blame]1369
1370 <dt><b><tt>extractelement ( VAL, IDX )</tt></b></dt>
1371
1372 <dd>Perform the <a href="#i_extractelement">extractelement
1373 operation</a> on constants.
1374
Robert Bocchino05ccd702006-01-15 20:48:27 +0000[diff] [blame]1375 <dt><b><tt>insertelement ( VAL, ELT, IDX )</tt></b></dt>
1376
1377 <dd>Perform the <a href="#i_insertelement">insertelement
Reid Spencer01c42592006-12-04 19:23:19 +0000[diff] [blame]1378 operation</a> on constants.</dd>
Robert Bocchino05ccd702006-01-15 20:48:27 +0000[diff] [blame]1379
Chris Lattnerc1989542006-04-08 00:13:41 +0000[diff] [blame]1380
1381 <dt><b><tt>shufflevector ( VEC1, VEC2, IDXMASK )</tt></b></dt>
1382
1383 <dd>Perform the <a href="#i_shufflevector">shufflevector
Reid Spencer01c42592006-12-04 19:23:19 +0000[diff] [blame]1384 operation</a> on constants.</dd>
Chris Lattnerc1989542006-04-08 00:13:41 +0000[diff] [blame]1385
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]1386 <dt><b><tt>OPCODE ( LHS, RHS )</tt></b></dt>
1387
Reid Spencer2dc45b82004-12-09 18:13:12 +0000[diff] [blame]1388 <dd>Perform the specified operation of the LHS and RHS constants. OPCODE may
1389 be any of the <a href="#binaryops">binary</a> or <a href="#bitwiseops">bitwise
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]1390 binary</a> operations. The constraints on operands are the same as those for
1391 the corresponding instruction (e.g. no bitwise operations on floating point
John Criswelle4c57cc2005-05-12 16:52:32 +0000[diff] [blame]1392 values are allowed).</dd>
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]1393</dl>
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]1394</div>
Chris Lattner9ee5d222004-03-08 16:49:10 +0000[diff] [blame]1395
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1396<!-- *********************************************************************** -->
Chris Lattnere87d6532006-01-25 23:47:57 +0000[diff] [blame]1397<div class="doc_section"> <a name="othervalues">Other Values</a> </div>
1398<!-- *********************************************************************** -->
1399
1400<!-- ======================================================================= -->
1401<div class="doc_subsection">
1402<a name="inlineasm">Inline Assembler Expressions</a>
1403</div>
1404
1405<div class="doc_text">
1406
1407<p>
1408LLVM supports inline assembler expressions (as opposed to <a href="#moduleasm">
1409Module-Level Inline Assembly</a>) through the use of a special value. This
1410value represents the inline assembler as a string (containing the instructions
1411to emit), a list of operand constraints (stored as a string), and a flag that
1412indicates whether or not the inline asm expression has side effects. An example
1413inline assembler expression is:
1414</p>
1415
1416<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]1417 i32 (i32) asm "bswap $0", "=r,r"
Chris Lattnere87d6532006-01-25 23:47:57 +0000[diff] [blame]1418</pre>
1419
1420<p>
1421Inline assembler expressions may <b>only</b> be used as the callee operand of
1422a <a href="#i_call"><tt>call</tt> instruction</a>. Thus, typically we have:
1423</p>
1424
1425<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]1426 %X = call i32 asm "<a href="#i_bswap">bswap</a> $0", "=r,r"(i32 %Y)
Chris Lattnere87d6532006-01-25 23:47:57 +0000[diff] [blame]1427</pre>
1428
1429<p>
1430Inline asms with side effects not visible in the constraint list must be marked
1431as having side effects. This is done through the use of the
1432'<tt>sideeffect</tt>' keyword, like so:
1433</p>
1434
1435<pre>
1436 call void asm sideeffect "eieio", ""()
1437</pre>
1438
1439<p>TODO: The format of the asm and constraints string still need to be
1440documented here. Constraints on what can be done (e.g. duplication, moving, etc
1441need to be documented).
1442</p>
1443
1444</div>
1445
1446<!-- *********************************************************************** -->
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1447<div class="doc_section"> <a name="instref">Instruction Reference</a> </div>
1448<!-- *********************************************************************** -->
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]1449
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1450<div class="doc_text">
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]1451
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1452<p>The LLVM instruction set consists of several different
1453classifications of instructions: <a href="#terminators">terminator
John Criswellc1f786c2005-05-13 22:25:59 +0000[diff] [blame]1454instructions</a>, <a href="#binaryops">binary instructions</a>,
1455<a href="#bitwiseops">bitwise binary instructions</a>, <a
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1456 href="#memoryops">memory instructions</a>, and <a href="#otherops">other
1457instructions</a>.</p>
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]1458
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1459</div>
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]1460
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1461<!-- ======================================================================= -->
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1462<div class="doc_subsection"> <a name="terminators">Terminator
1463Instructions</a> </div>
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]1464
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1465<div class="doc_text">
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]1466
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1467<p>As mentioned <a href="#functionstructure">previously</a>, every
1468basic block in a program ends with a "Terminator" instruction, which
1469indicates which block should be executed after the current block is
1470finished. These terminator instructions typically yield a '<tt>void</tt>'
1471value: they produce control flow, not values (the one exception being
1472the '<a href="#i_invoke"><tt>invoke</tt></a>' instruction).</p>
John Criswell9e2485c2004-12-10 15:51:16 +0000[diff] [blame]1473<p>There are six different terminator instructions: the '<a
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1474 href="#i_ret"><tt>ret</tt></a>' instruction, the '<a href="#i_br"><tt>br</tt></a>'
1475instruction, the '<a href="#i_switch"><tt>switch</tt></a>' instruction,
Chris Lattner35eca582004-10-16 18:04:13 +0000[diff] [blame]1476the '<a href="#i_invoke"><tt>invoke</tt></a>' instruction, the '<a
1477 href="#i_unwind"><tt>unwind</tt></a>' instruction, and the '<a
1478 href="#i_unreachable"><tt>unreachable</tt></a>' instruction.</p>
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]1479
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1480</div>
Chris Lattnerc3f59762004-12-09 17:30:23 +0000[diff] [blame]1481
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1482<!-- _______________________________________________________________________ -->
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1483<div class="doc_subsubsection"> <a name="i_ret">'<tt>ret</tt>'
1484Instruction</a> </div>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1485<div class="doc_text">
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1486<h5>Syntax:</h5>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1487<pre> ret &lt;type&gt; &lt;value&gt; <i>; Return a value from a non-void function</i>
Chris Lattner7faa8832002-04-14 06:13:44 +0000[diff] [blame]1488 ret void <i>; Return from void function</i>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1489</pre>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1490<h5>Overview:</h5>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1491<p>The '<tt>ret</tt>' instruction is used to return control flow (and a
John Criswellc1f786c2005-05-13 22:25:59 +0000[diff] [blame]1492value) from a function back to the caller.</p>
John Criswell4457dc92004-04-09 16:48:45 +0000[diff] [blame]1493<p>There are two forms of the '<tt>ret</tt>' instruction: one that
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1494returns a value and then causes control flow, and one that just causes
1495control flow to occur.</p>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1496<h5>Arguments:</h5>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1497<p>The '<tt>ret</tt>' instruction may return any '<a
1498 href="#t_firstclass">first class</a>' type. Notice that a function is
1499not <a href="#wellformed">well formed</a> if there exists a '<tt>ret</tt>'
1500instruction inside of the function that returns a value that does not
1501match the return type of the function.</p>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1502<h5>Semantics:</h5>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1503<p>When the '<tt>ret</tt>' instruction is executed, control flow
1504returns back to the calling function's context. If the caller is a "<a
John Criswellfa081872004-06-25 15:16:57 +0000[diff] [blame]1505 href="#i_call"><tt>call</tt></a>" instruction, execution continues at
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1506the instruction after the call. If the caller was an "<a
1507 href="#i_invoke"><tt>invoke</tt></a>" instruction, execution continues
John Criswelle4c57cc2005-05-12 16:52:32 +0000[diff] [blame]1508at the beginning of the "normal" destination block. If the instruction
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1509returns a value, that value shall set the call or invoke instruction's
1510return value.</p>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1511<h5>Example:</h5>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]1512<pre> ret i32 5 <i>; Return an integer value of 5</i>
Chris Lattner7faa8832002-04-14 06:13:44 +0000[diff] [blame]1513 ret void <i>; Return from a void function</i>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1514</pre>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1515</div>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1516<!-- _______________________________________________________________________ -->
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1517<div class="doc_subsubsection"> <a name="i_br">'<tt>br</tt>' Instruction</a> </div>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1518<div class="doc_text">
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1519<h5>Syntax:</h5>
Reid Spencerc78f3372007-01-12 03:35:51 +0000[diff] [blame]1520<pre> br i1 &lt;cond&gt;, label &lt;iftrue&gt;, label &lt;iffalse&gt;<br> br label &lt;dest&gt; <i>; Unconditional branch</i>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1521</pre>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1522<h5>Overview:</h5>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1523<p>The '<tt>br</tt>' instruction is used to cause control flow to
1524transfer to a different basic block in the current function. There are
1525two forms of this instruction, corresponding to a conditional branch
1526and an unconditional branch.</p>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1527<h5>Arguments:</h5>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1528<p>The conditional branch form of the '<tt>br</tt>' instruction takes a
Reid Spencerc78f3372007-01-12 03:35:51 +0000[diff] [blame]1529single '<tt>i1</tt>' value and two '<tt>label</tt>' values. The
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1530unconditional form of the '<tt>br</tt>' instruction takes a single '<tt>label</tt>'
1531value as a target.</p>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1532<h5>Semantics:</h5>
Reid Spencerc78f3372007-01-12 03:35:51 +0000[diff] [blame]1533<p>Upon execution of a conditional '<tt>br</tt>' instruction, the '<tt>i1</tt>'
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1534argument is evaluated. If the value is <tt>true</tt>, control flows
1535to the '<tt>iftrue</tt>' <tt>label</tt> argument. If "cond" is <tt>false</tt>,
1536control flows to the '<tt>iffalse</tt>' <tt>label</tt> argument.</p>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1537<h5>Example:</h5>
Reid Spencerc78f3372007-01-12 03:35:51 +0000[diff] [blame]1538<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
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]1539 href="#i_ret">ret</a> i32 1<br>IfUnequal:<br> <a href="#i_ret">ret</a> i32 0<br></pre>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1540</div>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1541<!-- _______________________________________________________________________ -->
Chris Lattnerc88c17b2004-02-24 04:54:45 +0000[diff] [blame]1542<div class="doc_subsubsection">
1543 <a name="i_switch">'<tt>switch</tt>' Instruction</a>
1544</div>
1545
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1546<div class="doc_text">
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1547<h5>Syntax:</h5>
Chris Lattnerc88c17b2004-02-24 04:54:45 +0000[diff] [blame]1548
1549<pre>
1550 switch &lt;intty&gt; &lt;value&gt;, label &lt;defaultdest&gt; [ &lt;intty&gt; &lt;val&gt;, label &lt;dest&gt; ... ]
1551</pre>
1552
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1553<h5>Overview:</h5>
Chris Lattnerc88c17b2004-02-24 04:54:45 +0000[diff] [blame]1554
1555<p>The '<tt>switch</tt>' instruction is used to transfer control flow to one of
1556several different places. It is a generalization of the '<tt>br</tt>'
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1557instruction, allowing a branch to occur to one of many possible
1558destinations.</p>
Chris Lattnerc88c17b2004-02-24 04:54:45 +0000[diff] [blame]1559
1560
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1561<h5>Arguments:</h5>
Chris Lattnerc88c17b2004-02-24 04:54:45 +0000[diff] [blame]1562
1563<p>The '<tt>switch</tt>' instruction uses three parameters: an integer
1564comparison value '<tt>value</tt>', a default '<tt>label</tt>' destination, and
1565an array of pairs of comparison value constants and '<tt>label</tt>'s. The
1566table is not allowed to contain duplicate constant entries.</p>
1567
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1568<h5>Semantics:</h5>
Chris Lattnerc88c17b2004-02-24 04:54:45 +0000[diff] [blame]1569
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1570<p>The <tt>switch</tt> instruction specifies a table of values and
1571destinations. When the '<tt>switch</tt>' instruction is executed, this
John Criswell84114752004-06-25 16:05:06 +0000[diff] [blame]1572table is searched for the given value. If the value is found, control flow is
1573transfered to the corresponding destination; otherwise, control flow is
1574transfered to the default destination.</p>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1575
Chris Lattnerc88c17b2004-02-24 04:54:45 +0000[diff] [blame]1576<h5>Implementation:</h5>
1577
1578<p>Depending on properties of the target machine and the particular
1579<tt>switch</tt> instruction, this instruction may be code generated in different
John Criswell84114752004-06-25 16:05:06 +0000[diff] [blame]1580ways. For example, it could be generated as a series of chained conditional
1581branches or with a lookup table.</p>
Chris Lattnerc88c17b2004-02-24 04:54:45 +0000[diff] [blame]1582
1583<h5>Example:</h5>
1584
1585<pre>
1586 <i>; Emulate a conditional br instruction</i>
Reid Spencerc78f3372007-01-12 03:35:51 +0000[diff] [blame]1587 %Val = <a href="#i_zext">zext</a> i1 %value to i32
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]1588 switch i32 %Val, label %truedest [i32 0, label %falsedest ]
Chris Lattnerc88c17b2004-02-24 04:54:45 +0000[diff] [blame]1589
1590 <i>; Emulate an unconditional br instruction</i>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]1591 switch i32 0, label %dest [ ]
Chris Lattnerc88c17b2004-02-24 04:54:45 +0000[diff] [blame]1592
1593 <i>; Implement a jump table:</i>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]1594 switch i32 %val, label %otherwise [ i32 0, label %onzero
1595 i32 1, label %onone
1596 i32 2, label %ontwo ]
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1597</pre>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1598</div>
Chris Lattnerbad10ee2005-05-06 22:57:40 +0000[diff] [blame]1599
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1600<!-- _______________________________________________________________________ -->
Chris Lattnerbad10ee2005-05-06 22:57:40 +0000[diff] [blame]1601<div class="doc_subsubsection">
1602 <a name="i_invoke">'<tt>invoke</tt>' Instruction</a>
1603</div>
1604
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1605<div class="doc_text">
Chris Lattnerbad10ee2005-05-06 22:57:40 +0000[diff] [blame]1606
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1607<h5>Syntax:</h5>
Chris Lattnerbad10ee2005-05-06 22:57:40 +0000[diff] [blame]1608
1609<pre>
1610 &lt;result&gt; = invoke [<a href="#callingconv">cconv</a>] &lt;ptr to function ty&gt; %&lt;function ptr val&gt;(&lt;function args&gt;)
Chris Lattner76b8a332006-05-14 18:23:06 +0000[diff] [blame]1611 to label &lt;normal label&gt; unwind label &lt;exception label&gt;
Chris Lattnerbad10ee2005-05-06 22:57:40 +0000[diff] [blame]1612</pre>
1613
Chris Lattner6536cfe2002-05-06 22:08:29 +0000[diff] [blame]1614<h5>Overview:</h5>
Chris Lattnerbad10ee2005-05-06 22:57:40 +0000[diff] [blame]1615
1616<p>The '<tt>invoke</tt>' instruction causes control to transfer to a specified
1617function, with the possibility of control flow transfer to either the
John Criswelle4c57cc2005-05-12 16:52:32 +0000[diff] [blame]1618'<tt>normal</tt>' label or the
1619'<tt>exception</tt>' label. If the callee function returns with the
Chris Lattnerbad10ee2005-05-06 22:57:40 +0000[diff] [blame]1620"<tt><a href="#i_ret">ret</a></tt>" instruction, control flow will return to the
1621"normal" label. If the callee (or any indirect callees) returns with the "<a
John Criswelle4c57cc2005-05-12 16:52:32 +0000[diff] [blame]1622href="#i_unwind"><tt>unwind</tt></a>" instruction, control is interrupted and
1623continued at the dynamically nearest "exception" label.</p>
Chris Lattnerbad10ee2005-05-06 22:57:40 +0000[diff] [blame]1624
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1625<h5>Arguments:</h5>
Chris Lattnerbad10ee2005-05-06 22:57:40 +0000[diff] [blame]1626
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1627<p>This instruction requires several arguments:</p>
Chris Lattnerbad10ee2005-05-06 22:57:40 +0000[diff] [blame]1628
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1629<ol>
Chris Lattnerbad10ee2005-05-06 22:57:40 +0000[diff] [blame]1630 <li>
John Criswellc1f786c2005-05-13 22:25:59 +0000[diff] [blame]1631 The optional "cconv" marker indicates which <a href="callingconv">calling
Chris Lattnerbad10ee2005-05-06 22:57:40 +0000[diff] [blame]1632 convention</a> the call should use. If none is specified, the call defaults
1633 to using C calling conventions.
1634 </li>
1635 <li>'<tt>ptr to function ty</tt>': shall be the signature of the pointer to
1636 function value being invoked. In most cases, this is a direct function
1637 invocation, but indirect <tt>invoke</tt>s are just as possible, branching off
1638 an arbitrary pointer to function value.
1639 </li>
1640
1641 <li>'<tt>function ptr val</tt>': An LLVM value containing a pointer to a
1642 function to be invoked. </li>
1643
1644 <li>'<tt>function args</tt>': argument list whose types match the function
1645 signature argument types. If the function signature indicates the function
1646 accepts a variable number of arguments, the extra arguments can be
1647 specified. </li>
1648
1649 <li>'<tt>normal label</tt>': the label reached when the called function
1650 executes a '<tt><a href="#i_ret">ret</a></tt>' instruction. </li>
1651
1652 <li>'<tt>exception label</tt>': the label reached when a callee returns with
1653 the <a href="#i_unwind"><tt>unwind</tt></a> instruction. </li>
1654
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1655</ol>
Chris Lattnerbad10ee2005-05-06 22:57:40 +0000[diff] [blame]1656
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1657<h5>Semantics:</h5>
Chris Lattnerbad10ee2005-05-06 22:57:40 +0000[diff] [blame]1658
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1659<p>This instruction is designed to operate as a standard '<tt><a
Chris Lattnerbad10ee2005-05-06 22:57:40 +0000[diff] [blame]1660href="#i_call">call</a></tt>' instruction in most regards. The primary
1661difference is that it establishes an association with a label, which is used by
1662the runtime library to unwind the stack.</p>
1663
1664<p>This instruction is used in languages with destructors to ensure that proper
1665cleanup is performed in the case of either a <tt>longjmp</tt> or a thrown
1666exception. Additionally, this is important for implementation of
1667'<tt>catch</tt>' clauses in high-level languages that support them.</p>
1668
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1669<h5>Example:</h5>
Chris Lattnerbad10ee2005-05-06 22:57:40 +0000[diff] [blame]1670<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]1671 %retval = invoke i32 %Test(i32 15) to label %Continue
1672 unwind label %TestCleanup <i>; {i32}:retval set</i>
1673 %retval = invoke <a href="#callingconv">coldcc</a> i32 %Test(i32 15) to label %Continue
1674 unwind label %TestCleanup <i>; {i32}:retval set</i>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1675</pre>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1676</div>
Chris Lattner35eca582004-10-16 18:04:13 +0000[diff] [blame]1677
1678
Chris Lattner27f71f22003-09-03 00:41:47 +0000[diff] [blame]1679<!-- _______________________________________________________________________ -->
Chris Lattner35eca582004-10-16 18:04:13 +0000[diff] [blame]1680
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1681<div class="doc_subsubsection"> <a name="i_unwind">'<tt>unwind</tt>'
1682Instruction</a> </div>
Chris Lattner35eca582004-10-16 18:04:13 +0000[diff] [blame]1683
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1684<div class="doc_text">
Chris Lattner35eca582004-10-16 18:04:13 +0000[diff] [blame]1685
Chris Lattner27f71f22003-09-03 00:41:47 +0000[diff] [blame]1686<h5>Syntax:</h5>
Chris Lattner35eca582004-10-16 18:04:13 +0000[diff] [blame]1687<pre>
1688 unwind
1689</pre>
1690
Chris Lattner27f71f22003-09-03 00:41:47 +0000[diff] [blame]1691<h5>Overview:</h5>
Chris Lattner35eca582004-10-16 18:04:13 +0000[diff] [blame]1692
1693<p>The '<tt>unwind</tt>' instruction unwinds the stack, continuing control flow
1694at the first callee in the dynamic call stack which used an <a
1695href="#i_invoke"><tt>invoke</tt></a> instruction to perform the call. This is
1696primarily used to implement exception handling.</p>
1697
Chris Lattner27f71f22003-09-03 00:41:47 +0000[diff] [blame]1698<h5>Semantics:</h5>
Chris Lattner35eca582004-10-16 18:04:13 +0000[diff] [blame]1699
1700<p>The '<tt>unwind</tt>' intrinsic causes execution of the current function to
1701immediately halt. The dynamic call stack is then searched for the first <a
1702href="#i_invoke"><tt>invoke</tt></a> instruction on the call stack. Once found,
1703execution continues at the "exceptional" destination block specified by the
1704<tt>invoke</tt> instruction. If there is no <tt>invoke</tt> instruction in the
1705dynamic call chain, undefined behavior results.</p>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1706</div>
Chris Lattner35eca582004-10-16 18:04:13 +0000[diff] [blame]1707
1708<!-- _______________________________________________________________________ -->
1709
1710<div class="doc_subsubsection"> <a name="i_unreachable">'<tt>unreachable</tt>'
1711Instruction</a> </div>
1712
1713<div class="doc_text">
1714
1715<h5>Syntax:</h5>
1716<pre>
1717 unreachable
1718</pre>
1719
1720<h5>Overview:</h5>
1721
1722<p>The '<tt>unreachable</tt>' instruction has no defined semantics. This
1723instruction is used to inform the optimizer that a particular portion of the
1724code is not reachable. This can be used to indicate that the code after a
1725no-return function cannot be reached, and other facts.</p>
1726
1727<h5>Semantics:</h5>
1728
1729<p>The '<tt>unreachable</tt>' instruction has no defined semantics.</p>
1730</div>
1731
1732
1733
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1734<!-- ======================================================================= -->
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1735<div class="doc_subsection"> <a name="binaryops">Binary Operations</a> </div>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1736<div class="doc_text">
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1737<p>Binary operators are used to do most of the computation in a
1738program. They require two operands, execute an operation on them, and
John Criswell9e2485c2004-12-10 15:51:16 +0000[diff] [blame]1739produce a single value. The operands might represent
Chris Lattnera58561b2004-08-12 19:12:28 +0000[diff] [blame]1740multiple data, as is the case with the <a href="#t_packed">packed</a> data type.
1741The result value of a binary operator is not
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1742necessarily the same type as its operands.</p>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1743<p>There are several different binary operators:</p>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1744</div>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1745<!-- _______________________________________________________________________ -->
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1746<div class="doc_subsubsection"> <a name="i_add">'<tt>add</tt>'
1747Instruction</a> </div>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1748<div class="doc_text">
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1749<h5>Syntax:</h5>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1750<pre> &lt;result&gt; = add &lt;ty&gt; &lt;var1&gt;, &lt;var2&gt; <i>; yields {ty}:result</i>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1751</pre>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1752<h5>Overview:</h5>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1753<p>The '<tt>add</tt>' instruction returns the sum of its two operands.</p>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1754<h5>Arguments:</h5>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1755<p>The two arguments to the '<tt>add</tt>' instruction must be either <a
Chris Lattnera58561b2004-08-12 19:12:28 +0000[diff] [blame]1756 href="#t_integer">integer</a> or <a href="#t_floating">floating point</a> values.
1757 This instruction can also take <a href="#t_packed">packed</a> versions of the values.
1758Both arguments must have identical types.</p>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1759<h5>Semantics:</h5>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1760<p>The value produced is the integer or floating point sum of the two
1761operands.</p>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1762<h5>Example:</h5>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]1763<pre> &lt;result&gt; = add i32 4, %var <i>; yields {i32}:result = 4 + %var</i>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1764</pre>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1765</div>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1766<!-- _______________________________________________________________________ -->
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1767<div class="doc_subsubsection"> <a name="i_sub">'<tt>sub</tt>'
1768Instruction</a> </div>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1769<div class="doc_text">
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1770<h5>Syntax:</h5>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1771<pre> &lt;result&gt; = sub &lt;ty&gt; &lt;var1&gt;, &lt;var2&gt; <i>; yields {ty}:result</i>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1772</pre>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1773<h5>Overview:</h5>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1774<p>The '<tt>sub</tt>' instruction returns the difference of its two
1775operands.</p>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1776<p>Note that the '<tt>sub</tt>' instruction is used to represent the '<tt>neg</tt>'
1777instruction present in most other intermediate representations.</p>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1778<h5>Arguments:</h5>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1779<p>The two arguments to the '<tt>sub</tt>' instruction must be either <a
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1780 href="#t_integer">integer</a> or <a href="#t_floating">floating point</a>
Chris Lattnera58561b2004-08-12 19:12:28 +0000[diff] [blame]1781values.
1782This instruction can also take <a href="#t_packed">packed</a> versions of the values.
1783Both arguments must have identical types.</p>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1784<h5>Semantics:</h5>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1785<p>The value produced is the integer or floating point difference of
1786the two operands.</p>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1787<h5>Example:</h5>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]1788<pre> &lt;result&gt; = sub i32 4, %var <i>; yields {i32}:result = 4 - %var</i>
1789 &lt;result&gt; = sub i32 0, %val <i>; yields {i32}:result = -%var</i>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1790</pre>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1791</div>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1792<!-- _______________________________________________________________________ -->
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1793<div class="doc_subsubsection"> <a name="i_mul">'<tt>mul</tt>'
1794Instruction</a> </div>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1795<div class="doc_text">
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1796<h5>Syntax:</h5>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1797<pre> &lt;result&gt; = mul &lt;ty&gt; &lt;var1&gt;, &lt;var2&gt; <i>; yields {ty}:result</i>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1798</pre>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1799<h5>Overview:</h5>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1800<p>The '<tt>mul</tt>' instruction returns the product of its two
1801operands.</p>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1802<h5>Arguments:</h5>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1803<p>The two arguments to the '<tt>mul</tt>' instruction must be either <a
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1804 href="#t_integer">integer</a> or <a href="#t_floating">floating point</a>
Chris Lattnera58561b2004-08-12 19:12:28 +0000[diff] [blame]1805values.
1806This instruction can also take <a href="#t_packed">packed</a> versions of the values.
1807Both arguments must have identical types.</p>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1808<h5>Semantics:</h5>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1809<p>The value produced is the integer or floating point product of the
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1810two operands.</p>
Reid Spencera5173382007-01-04 16:43:23 +0000[diff] [blame]1811<p>Because the operands are the same width, the result of an integer
1812multiplication is the same whether the operands should be deemed unsigned or
1813signed.</p>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1814<h5>Example:</h5>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]1815<pre> &lt;result&gt; = mul i32 4, %var <i>; yields {i32}:result = 4 * %var</i>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1816</pre>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1817</div>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1818<!-- _______________________________________________________________________ -->
Reid Spencer1628cec2006-10-26 06:15:43 +0000[diff] [blame]1819<div class="doc_subsubsection"> <a name="i_udiv">'<tt>udiv</tt>' Instruction
1820</a></div>
1821<div class="doc_text">
1822<h5>Syntax:</h5>
1823<pre> &lt;result&gt; = udiv &lt;ty&gt; &lt;var1&gt;, &lt;var2&gt; <i>; yields {ty}:result</i>
1824</pre>
1825<h5>Overview:</h5>
1826<p>The '<tt>udiv</tt>' instruction returns the quotient of its two
1827operands.</p>
1828<h5>Arguments:</h5>
1829<p>The two arguments to the '<tt>udiv</tt>' instruction must be
1830<a href="#t_integer">integer</a> values. Both arguments must have identical
1831types. This instruction can also take <a href="#t_packed">packed</a> versions
1832of the values in which case the elements must be integers.</p>
1833<h5>Semantics:</h5>
1834<p>The value produced is the unsigned integer quotient of the two operands. This
1835instruction always performs an unsigned division operation, regardless of
1836whether the arguments are unsigned or not.</p>
1837<h5>Example:</h5>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]1838<pre> &lt;result&gt; = udiv i32 4, %var <i>; yields {i32}:result = 4 / %var</i>
Reid Spencer1628cec2006-10-26 06:15:43 +0000[diff] [blame]1839</pre>
1840</div>
1841<!-- _______________________________________________________________________ -->
1842<div class="doc_subsubsection"> <a name="i_sdiv">'<tt>sdiv</tt>' Instruction
1843</a> </div>
1844<div class="doc_text">
1845<h5>Syntax:</h5>
1846<pre> &lt;result&gt; = sdiv &lt;ty&gt; &lt;var1&gt;, &lt;var2&gt; <i>; yields {ty}:result</i>
1847</pre>
1848<h5>Overview:</h5>
1849<p>The '<tt>sdiv</tt>' instruction returns the quotient of its two
1850operands.</p>
1851<h5>Arguments:</h5>
1852<p>The two arguments to the '<tt>sdiv</tt>' instruction must be
1853<a href="#t_integer">integer</a> values. Both arguments must have identical
1854types. This instruction can also take <a href="#t_packed">packed</a> versions
1855of the values in which case the elements must be integers.</p>
1856<h5>Semantics:</h5>
1857<p>The value produced is the signed integer quotient of the two operands. This
1858instruction always performs a signed division operation, regardless of whether
1859the arguments are signed or not.</p>
1860<h5>Example:</h5>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]1861<pre> &lt;result&gt; = sdiv i32 4, %var <i>; yields {i32}:result = 4 / %var</i>
Reid Spencer1628cec2006-10-26 06:15:43 +0000[diff] [blame]1862</pre>
1863</div>
1864<!-- _______________________________________________________________________ -->
1865<div class="doc_subsubsection"> <a name="i_fdiv">'<tt>fdiv</tt>'
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1866Instruction</a> </div>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1867<div class="doc_text">
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]1868<h5>Syntax:</h5>
Reid Spencer1628cec2006-10-26 06:15:43 +0000[diff] [blame]1869<pre> &lt;result&gt; = fdiv &lt;ty&gt; &lt;var1&gt;, &lt;var2&gt; <i>; yields {ty}:result</i>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1870</pre>
1871<h5>Overview:</h5>
Reid Spencer1628cec2006-10-26 06:15:43 +0000[diff] [blame]1872<p>The '<tt>fdiv</tt>' instruction returns the quotient of its two
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1873operands.</p>
1874<h5>Arguments:</h5>
Reid Spencer1628cec2006-10-26 06:15:43 +0000[diff] [blame]1875<p>The two arguments to the '<tt>div</tt>' instruction must be
1876<a href="#t_floating">floating point</a> values. Both arguments must have
1877identical types. This instruction can also take <a href="#t_packed">packed</a>
1878versions of the values in which case the elements must be floating point.</p>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1879<h5>Semantics:</h5>
Reid Spencer1628cec2006-10-26 06:15:43 +0000[diff] [blame]1880<p>The value produced is the floating point quotient of the two operands.</p>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1881<h5>Example:</h5>
Reid Spencer1628cec2006-10-26 06:15:43 +0000[diff] [blame]1882<pre> &lt;result&gt; = fdiv float 4.0, %var <i>; yields {float}:result = 4.0 / %var</i>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1883</pre>
1884</div>
1885<!-- _______________________________________________________________________ -->
Reid Spencer0a783f72006-11-02 01:53:59 +0000[diff] [blame]1886<div class="doc_subsubsection"> <a name="i_urem">'<tt>urem</tt>' Instruction</a>
1887</div>
1888<div class="doc_text">
1889<h5>Syntax:</h5>
1890<pre> &lt;result&gt; = urem &lt;ty&gt; &lt;var1&gt;, &lt;var2&gt; <i>; yields {ty}:result</i>
1891</pre>
1892<h5>Overview:</h5>
1893<p>The '<tt>urem</tt>' instruction returns the remainder from the
1894unsigned division of its two arguments.</p>
1895<h5>Arguments:</h5>
1896<p>The two arguments to the '<tt>urem</tt>' instruction must be
1897<a href="#t_integer">integer</a> values. Both arguments must have identical
1898types.</p>
1899<h5>Semantics:</h5>
1900<p>This instruction returns the unsigned integer <i>remainder</i> of a division.
1901This instruction always performs an unsigned division to get the remainder,
1902regardless of whether the arguments are unsigned or not.</p>
1903<h5>Example:</h5>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]1904<pre> &lt;result&gt; = urem i32 4, %var <i>; yields {i32}:result = 4 % %var</i>
Reid Spencer0a783f72006-11-02 01:53:59 +0000[diff] [blame]1905</pre>
1906
1907</div>
1908<!-- _______________________________________________________________________ -->
1909<div class="doc_subsubsection"> <a name="i_srem">'<tt>srem</tt>'
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1910Instruction</a> </div>
1911<div class="doc_text">
1912<h5>Syntax:</h5>
Reid Spencer0a783f72006-11-02 01:53:59 +0000[diff] [blame]1913<pre> &lt;result&gt; = srem &lt;ty&gt; &lt;var1&gt;, &lt;var2&gt; <i>; yields {ty}:result</i>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1914</pre>
1915<h5>Overview:</h5>
Reid Spencer0a783f72006-11-02 01:53:59 +0000[diff] [blame]1916<p>The '<tt>srem</tt>' instruction returns the remainder from the
1917signed division of its two operands.</p>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1918<h5>Arguments:</h5>
Reid Spencer0a783f72006-11-02 01:53:59 +0000[diff] [blame]1919<p>The two arguments to the '<tt>srem</tt>' instruction must be
1920<a href="#t_integer">integer</a> values. Both arguments must have identical
1921types.</p>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1922<h5>Semantics:</h5>
Reid Spencer0a783f72006-11-02 01:53:59 +0000[diff] [blame]1923<p>This instruction returns the <i>remainder</i> of a division (where the result
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1924has the same sign as the divisor), not the <i>modulus</i> (where the
1925result has the same sign as the dividend) of a value. For more
John Criswell0ec250c2005-10-24 16:17:18 +0000[diff] [blame]1926information about the difference, see <a
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1927 href="http://mathforum.org/dr.math/problems/anne.4.28.99.html">The
1928Math Forum</a>.</p>
1929<h5>Example:</h5>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]1930<pre> &lt;result&gt; = srem i32 4, %var <i>; yields {i32}:result = 4 % %var</i>
Reid Spencer0a783f72006-11-02 01:53:59 +0000[diff] [blame]1931</pre>
1932
1933</div>
1934<!-- _______________________________________________________________________ -->
1935<div class="doc_subsubsection"> <a name="i_frem">'<tt>frem</tt>'
1936Instruction</a> </div>
1937<div class="doc_text">
1938<h5>Syntax:</h5>
1939<pre> &lt;result&gt; = frem &lt;ty&gt; &lt;var1&gt;, &lt;var2&gt; <i>; yields {ty}:result</i>
1940</pre>
1941<h5>Overview:</h5>
1942<p>The '<tt>frem</tt>' instruction returns the remainder from the
1943division of its two operands.</p>
1944<h5>Arguments:</h5>
1945<p>The two arguments to the '<tt>frem</tt>' instruction must be
1946<a href="#t_floating">floating point</a> values. Both arguments must have
1947identical types.</p>
1948<h5>Semantics:</h5>
1949<p>This instruction returns the <i>remainder</i> of a division.</p>
1950<h5>Example:</h5>
1951<pre> &lt;result&gt; = frem float 4.0, %var <i>; yields {float}:result = 4.0 % %var</i>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]1952</pre>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]1953</div>
Robert Bocchino7b81c752006-02-17 21:18:08 +0000[diff] [blame]1954
Reid Spencer569f2fa2007-01-31 21:39:12 +0000[diff] [blame^]1955<!-- _______________________________________________________________________ -->
1956<div class="doc_subsubsection"> <a name="i_shl">'<tt>shl</tt>'
1957Instruction</a> </div>
1958<div class="doc_text">
1959<h5>Syntax:</h5>
1960<pre> &lt;result&gt; = shl &lt;ty&gt; &lt;var1&gt;, &lt;var2&gt; <i>; yields {ty}:result</i>
1961</pre>
1962<h5>Overview:</h5>
1963<p>The '<tt>shl</tt>' instruction returns the first operand shifted to
1964the left a specified number of bits.</p>
1965<h5>Arguments:</h5>
1966<p>Both arguments to the '<tt>shl</tt>' instruction must be the same <a
1967 href="#t_integer">integer</a> type.</p>
1968<h5>Semantics:</h5>
1969<p>The value produced is <tt>var1</tt> * 2<sup><tt>var2</tt></sup>.</p>
1970<h5>Example:</h5><pre>
1971 &lt;result&gt; = shl i32 4, %var <i>; yields {i32}: 4 &lt;&lt; %var</i>
1972 &lt;result&gt; = shl i32 4, 2 <i>; yields {i32}: 16</i>
1973 &lt;result&gt; = shl i32 1, 10 <i>; yields {i32}: 1024</i>
1974</pre>
1975</div>
1976<!-- _______________________________________________________________________ -->
1977<div class="doc_subsubsection"> <a name="i_lshr">'<tt>lshr</tt>'
1978Instruction</a> </div>
1979<div class="doc_text">
1980<h5>Syntax:</h5>
1981<pre> &lt;result&gt; = lshr &lt;ty&gt; &lt;var1&gt;, &lt;var2&gt; <i>; yields {ty}:result</i>
1982</pre>
1983
1984<h5>Overview:</h5>
1985<p>The '<tt>lshr</tt>' instruction (logical shift right) returns the first
1986operand shifted to the right a specified number of bits.</p>
1987
1988<h5>Arguments:</h5>
1989<p>Both arguments to the '<tt>lshr</tt>' instruction must be the same
1990<a href="#t_integer">integer</a> type.</p>
1991
1992<h5>Semantics:</h5>
1993<p>This instruction always performs a logical shift right operation. The most
1994significant bits of the result will be filled with zero bits after the
1995shift.</p>
1996
1997<h5>Example:</h5>
1998<pre>
1999 &lt;result&gt; = lshr i32 4, 1 <i>; yields {i32}:result = 2</i>
2000 &lt;result&gt; = lshr i32 4, 2 <i>; yields {i32}:result = 1</i>
2001 &lt;result&gt; = lshr i8 4, 3 <i>; yields {i8}:result = 0</i>
2002 &lt;result&gt; = lshr i8 -2, 1 <i>; yields {i8}:result = 0x7FFFFFFF </i>
2003</pre>
2004</div>
2005
2006<!-- ======================================================================= -->
2007<div class="doc_subsubsection"> <a name="i_ashr">'<tt>ashr</tt>'
2008Instruction</a> </div>
2009<div class="doc_text">
2010
2011<h5>Syntax:</h5>
2012<pre> &lt;result&gt; = ashr &lt;ty&gt; &lt;var1&gt;, &lt;var2&gt; <i>; yields {ty}:result</i>
2013</pre>
2014
2015<h5>Overview:</h5>
2016<p>The '<tt>ashr</tt>' instruction (arithmetic shift right) returns the first
2017operand shifted to the right a specified number of bits.</p>
2018
2019<h5>Arguments:</h5>
2020<p>Both arguments to the '<tt>ashr</tt>' instruction must be the same
2021<a href="#t_integer">integer</a> type.</p>
2022
2023<h5>Semantics:</h5>
2024<p>This instruction always performs an arithmetic shift right operation,
2025The most significant bits of the result will be filled with the sign bit
2026of <tt>var1</tt>.</p>
2027
2028<h5>Example:</h5>
2029<pre>
2030 &lt;result&gt; = ashr i32 4, 1 <i>; yields {i32}:result = 2</i>
2031 &lt;result&gt; = ashr i32 4, 2 <i>; yields {i32}:result = 1</i>
2032 &lt;result&gt; = ashr i8 4, 3 <i>; yields {i8}:result = 0</i>
2033 &lt;result&gt; = ashr i8 -2, 1 <i>; yields {i8}:result = -1</i>
2034</pre>
2035</div>
2036
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2037<!-- ======================================================================= -->
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2038<div class="doc_subsection"> <a name="bitwiseops">Bitwise Binary
2039Operations</a> </div>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2040<div class="doc_text">
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2041<p>Bitwise binary operators are used to do various forms of
2042bit-twiddling in a program. They are generally very efficient
John Criswell9e2485c2004-12-10 15:51:16 +0000[diff] [blame]2043instructions and can commonly be strength reduced from other
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2044instructions. They require two operands, execute an operation on them,
2045and produce a single value. The resulting value of the bitwise binary
2046operators is always the same type as its first operand.</p>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2047</div>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2048<!-- _______________________________________________________________________ -->
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2049<div class="doc_subsubsection"> <a name="i_and">'<tt>and</tt>'
2050Instruction</a> </div>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2051<div class="doc_text">
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2052<h5>Syntax:</h5>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2053<pre> &lt;result&gt; = and &lt;ty&gt; &lt;var1&gt;, &lt;var2&gt; <i>; yields {ty}:result</i>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2054</pre>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2055<h5>Overview:</h5>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2056<p>The '<tt>and</tt>' instruction returns the bitwise logical and of
2057its two operands.</p>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2058<h5>Arguments:</h5>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2059<p>The two arguments to the '<tt>and</tt>' instruction must be <a
Chris Lattner3b19d652007-01-15 01:54:13 +0000[diff] [blame]2060 href="#t_integer">integer</a> values. Both arguments must have
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2061identical types.</p>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2062<h5>Semantics:</h5>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2063<p>The truth table used for the '<tt>and</tt>' instruction is:</p>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2064<p> </p>
Misha Brukmandaa4cb02004-03-01 17:47:27 +0000[diff] [blame]2065<div style="align: center">
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2066<table border="1" cellspacing="0" cellpadding="4">
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2067 <tbody>
2068 <tr>
2069 <td>In0</td>
2070 <td>In1</td>
2071 <td>Out</td>
2072 </tr>
2073 <tr>
2074 <td>0</td>
2075 <td>0</td>
2076 <td>0</td>
2077 </tr>
2078 <tr>
2079 <td>0</td>
2080 <td>1</td>
2081 <td>0</td>
2082 </tr>
2083 <tr>
2084 <td>1</td>
2085 <td>0</td>
2086 <td>0</td>
2087 </tr>
2088 <tr>
2089 <td>1</td>
2090 <td>1</td>
2091 <td>1</td>
2092 </tr>
2093 </tbody>
2094</table>
Misha Brukmandaa4cb02004-03-01 17:47:27 +0000[diff] [blame]2095</div>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2096<h5>Example:</h5>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2097<pre> &lt;result&gt; = and i32 4, %var <i>; yields {i32}:result = 4 &amp; %var</i>
2098 &lt;result&gt; = and i32 15, 40 <i>; yields {i32}:result = 8</i>
2099 &lt;result&gt; = and i32 4, 8 <i>; yields {i32}:result = 0</i>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2100</pre>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2101</div>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2102<!-- _______________________________________________________________________ -->
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2103<div class="doc_subsubsection"> <a name="i_or">'<tt>or</tt>' Instruction</a> </div>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2104<div class="doc_text">
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2105<h5>Syntax:</h5>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2106<pre> &lt;result&gt; = or &lt;ty&gt; &lt;var1&gt;, &lt;var2&gt; <i>; yields {ty}:result</i>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2107</pre>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2108<h5>Overview:</h5>
2109<p>The '<tt>or</tt>' instruction returns the bitwise logical inclusive
2110or of its two operands.</p>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2111<h5>Arguments:</h5>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2112<p>The two arguments to the '<tt>or</tt>' instruction must be <a
Chris Lattner3b19d652007-01-15 01:54:13 +0000[diff] [blame]2113 href="#t_integer">integer</a> values. Both arguments must have
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2114identical types.</p>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2115<h5>Semantics:</h5>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2116<p>The truth table used for the '<tt>or</tt>' instruction is:</p>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2117<p> </p>
Misha Brukmandaa4cb02004-03-01 17:47:27 +0000[diff] [blame]2118<div style="align: center">
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2119<table border="1" cellspacing="0" cellpadding="4">
2120 <tbody>
2121 <tr>
2122 <td>In0</td>
2123 <td>In1</td>
2124 <td>Out</td>
2125 </tr>
2126 <tr>
2127 <td>0</td>
2128 <td>0</td>
2129 <td>0</td>
2130 </tr>
2131 <tr>
2132 <td>0</td>
2133 <td>1</td>
2134 <td>1</td>
2135 </tr>
2136 <tr>
2137 <td>1</td>
2138 <td>0</td>
2139 <td>1</td>
2140 </tr>
2141 <tr>
2142 <td>1</td>
2143 <td>1</td>
2144 <td>1</td>
2145 </tr>
2146 </tbody>
2147</table>
Misha Brukmandaa4cb02004-03-01 17:47:27 +0000[diff] [blame]2148</div>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2149<h5>Example:</h5>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2150<pre> &lt;result&gt; = or i32 4, %var <i>; yields {i32}:result = 4 | %var</i>
2151 &lt;result&gt; = or i32 15, 40 <i>; yields {i32}:result = 47</i>
2152 &lt;result&gt; = or i32 4, 8 <i>; yields {i32}:result = 12</i>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2153</pre>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2154</div>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2155<!-- _______________________________________________________________________ -->
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2156<div class="doc_subsubsection"> <a name="i_xor">'<tt>xor</tt>'
2157Instruction</a> </div>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2158<div class="doc_text">
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2159<h5>Syntax:</h5>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2160<pre> &lt;result&gt; = xor &lt;ty&gt; &lt;var1&gt;, &lt;var2&gt; <i>; yields {ty}:result</i>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2161</pre>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2162<h5>Overview:</h5>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2163<p>The '<tt>xor</tt>' instruction returns the bitwise logical exclusive
2164or of its two operands. The <tt>xor</tt> is used to implement the
2165"one's complement" operation, which is the "~" operator in C.</p>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2166<h5>Arguments:</h5>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2167<p>The two arguments to the '<tt>xor</tt>' instruction must be <a
Chris Lattner3b19d652007-01-15 01:54:13 +0000[diff] [blame]2168 href="#t_integer">integer</a> values. Both arguments must have
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2169identical types.</p>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2170<h5>Semantics:</h5>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2171<p>The truth table used for the '<tt>xor</tt>' instruction is:</p>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2172<p> </p>
Misha Brukmandaa4cb02004-03-01 17:47:27 +0000[diff] [blame]2173<div style="align: center">
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2174<table border="1" cellspacing="0" cellpadding="4">
2175 <tbody>
2176 <tr>
2177 <td>In0</td>
2178 <td>In1</td>
2179 <td>Out</td>
2180 </tr>
2181 <tr>
2182 <td>0</td>
2183 <td>0</td>
2184 <td>0</td>
2185 </tr>
2186 <tr>
2187 <td>0</td>
2188 <td>1</td>
2189 <td>1</td>
2190 </tr>
2191 <tr>
2192 <td>1</td>
2193 <td>0</td>
2194 <td>1</td>
2195 </tr>
2196 <tr>
2197 <td>1</td>
2198 <td>1</td>
2199 <td>0</td>
2200 </tr>
2201 </tbody>
2202</table>
Misha Brukmandaa4cb02004-03-01 17:47:27 +0000[diff] [blame]2203</div>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2204<p> </p>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2205<h5>Example:</h5>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2206<pre> &lt;result&gt; = xor i32 4, %var <i>; yields {i32}:result = 4 ^ %var</i>
2207 &lt;result&gt; = xor i32 15, 40 <i>; yields {i32}:result = 39</i>
2208 &lt;result&gt; = xor i32 4, 8 <i>; yields {i32}:result = 12</i>
2209 &lt;result&gt; = xor i32 %V, -1 <i>; yields {i32}:result = ~%V</i>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2210</pre>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2211</div>
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2212
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2213<!-- ======================================================================= -->
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2214<div class="doc_subsection">
Chris Lattner3df241e2006-04-08 23:07:04 +0000[diff] [blame]2215 <a name="vectorops">Vector Operations</a>
2216</div>
2217
2218<div class="doc_text">
2219
2220<p>LLVM supports several instructions to represent vector operations in a
2221target-independent manner. This instructions cover the element-access and
2222vector-specific operations needed to process vectors effectively. While LLVM
2223does directly support these vector operations, many sophisticated algorithms
2224will want to use target-specific intrinsics to take full advantage of a specific
2225target.</p>
2226
2227</div>
2228
2229<!-- _______________________________________________________________________ -->
2230<div class="doc_subsubsection">
2231 <a name="i_extractelement">'<tt>extractelement</tt>' Instruction</a>
2232</div>
2233
2234<div class="doc_text">
2235
2236<h5>Syntax:</h5>
2237
2238<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2239 &lt;result&gt; = extractelement &lt;n x &lt;ty&gt;&gt; &lt;val&gt;, i32 &lt;idx&gt; <i>; yields &lt;ty&gt;</i>
Chris Lattner3df241e2006-04-08 23:07:04 +0000[diff] [blame]2240</pre>
2241
2242<h5>Overview:</h5>
2243
2244<p>
2245The '<tt>extractelement</tt>' instruction extracts a single scalar
2246element from a packed vector at a specified index.
2247</p>
2248
2249
2250<h5>Arguments:</h5>
2251
2252<p>
2253The first operand of an '<tt>extractelement</tt>' instruction is a
2254value of <a href="#t_packed">packed</a> type. The second operand is
2255an index indicating the position from which to extract the element.
2256The index may be a variable.</p>
2257
2258<h5>Semantics:</h5>
2259
2260<p>
2261The result is a scalar of the same type as the element type of
2262<tt>val</tt>. Its value is the value at position <tt>idx</tt> of
2263<tt>val</tt>. If <tt>idx</tt> exceeds the length of <tt>val</tt>, the
2264results are undefined.
2265</p>
2266
2267<h5>Example:</h5>
2268
2269<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2270 %result = extractelement &lt;4 x i32&gt; %vec, i32 0 <i>; yields i32</i>
Chris Lattner3df241e2006-04-08 23:07:04 +0000[diff] [blame]2271</pre>
2272</div>
2273
2274
2275<!-- _______________________________________________________________________ -->
2276<div class="doc_subsubsection">
2277 <a name="i_insertelement">'<tt>insertelement</tt>' Instruction</a>
2278</div>
2279
2280<div class="doc_text">
2281
2282<h5>Syntax:</h5>
2283
2284<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2285 &lt;result&gt; = insertelement &lt;n x &lt;ty&gt;&gt; &lt;val&gt;, &lt;ty&gt; &lt;elt&gt, i32 &lt;idx&gt; <i>; yields &lt;n x &lt;ty&gt;&gt;</i>
Chris Lattner3df241e2006-04-08 23:07:04 +0000[diff] [blame]2286</pre>
2287
2288<h5>Overview:</h5>
2289
2290<p>
2291The '<tt>insertelement</tt>' instruction inserts a scalar
2292element into a packed vector at a specified index.
2293</p>
2294
2295
2296<h5>Arguments:</h5>
2297
2298<p>
2299The first operand of an '<tt>insertelement</tt>' instruction is a
2300value of <a href="#t_packed">packed</a> type. The second operand is a
2301scalar value whose type must equal the element type of the first
2302operand. The third operand is an index indicating the position at
2303which to insert the value. The index may be a variable.</p>
2304
2305<h5>Semantics:</h5>
2306
2307<p>
2308The result is a packed vector of the same type as <tt>val</tt>. Its
2309element values are those of <tt>val</tt> except at position
2310<tt>idx</tt>, where it gets the value <tt>elt</tt>. If <tt>idx</tt>
2311exceeds the length of <tt>val</tt>, the results are undefined.
2312</p>
2313
2314<h5>Example:</h5>
2315
2316<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2317 %result = insertelement &lt;4 x i32&gt; %vec, i32 1, i32 0 <i>; yields &lt;4 x i32&gt;</i>
Chris Lattner3df241e2006-04-08 23:07:04 +0000[diff] [blame]2318</pre>
2319</div>
2320
2321<!-- _______________________________________________________________________ -->
2322<div class="doc_subsubsection">
2323 <a name="i_shufflevector">'<tt>shufflevector</tt>' Instruction</a>
2324</div>
2325
2326<div class="doc_text">
2327
2328<h5>Syntax:</h5>
2329
2330<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2331 &lt;result&gt; = shufflevector &lt;n x &lt;ty&gt;&gt; &lt;v1&gt;, &lt;n x &lt;ty&gt;&gt; &lt;v2&gt;, &lt;n x i32&gt; &lt;mask&gt; <i>; yields &lt;n x &lt;ty&gt;&gt;</i>
Chris Lattner3df241e2006-04-08 23:07:04 +0000[diff] [blame]2332</pre>
2333
2334<h5>Overview:</h5>
2335
2336<p>
2337The '<tt>shufflevector</tt>' instruction constructs a permutation of elements
2338from two input vectors, returning a vector of the same type.
2339</p>
2340
2341<h5>Arguments:</h5>
2342
2343<p>
2344The first two operands of a '<tt>shufflevector</tt>' instruction are vectors
2345with types that match each other and types that match the result of the
2346instruction. The third argument is a shuffle mask, which has the same number
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2347of elements as the other vector type, but whose element type is always 'i32'.
Chris Lattner3df241e2006-04-08 23:07:04 +0000[diff] [blame]2348</p>
2349
2350<p>
2351The shuffle mask operand is required to be a constant vector with either
2352constant integer or undef values.
2353</p>
2354
2355<h5>Semantics:</h5>
2356
2357<p>
2358The elements of the two input vectors are numbered from left to right across
2359both of the vectors. The shuffle mask operand specifies, for each element of
2360the result vector, which element of the two input registers the result element
2361gets. The element selector may be undef (meaning "don't care") and the second
2362operand may be undef if performing a shuffle from only one vector.
2363</p>
2364
2365<h5>Example:</h5>
2366
2367<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2368 %result = shufflevector &lt;4 x i32&gt; %v1, &lt;4 x i32&gt; %v2,
2369 &lt;4 x i32&gt; &lt;i32 0, i32 4, i32 1, i32 5&gt; <i>; yields &lt;4 x i32&gt;</i>
2370 %result = shufflevector &lt;4 x i32&gt; %v1, &lt;4 x i32&gt; undef,
2371 &lt;4 x i32&gt; &lt;i32 0, i32 1, i32 2, i32 3&gt; <i>; yields &lt;4 x i32&gt;</i> - Identity shuffle.
Chris Lattner3df241e2006-04-08 23:07:04 +0000[diff] [blame]2372</pre>
2373</div>
2374
Tanya Lattner09474292006-04-14 19:24:33 +0000[diff] [blame]2375
Chris Lattner3df241e2006-04-08 23:07:04 +0000[diff] [blame]2376<!-- ======================================================================= -->
2377<div class="doc_subsection">
Chris Lattner884a9702006-08-15 00:45:58 +0000[diff] [blame]2378 <a name="memoryops">Memory Access and Addressing Operations</a>
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2379</div>
2380
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2381<div class="doc_text">
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2382
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2383<p>A key design point of an SSA-based representation is how it
2384represents memory. In LLVM, no memory locations are in SSA form, which
2385makes things very simple. This section describes how to read, write,
John Criswell9e2485c2004-12-10 15:51:16 +0000[diff] [blame]2386allocate, and free memory in LLVM.</p>
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2387
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2388</div>
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2389
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2390<!-- _______________________________________________________________________ -->
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2391<div class="doc_subsubsection">
2392 <a name="i_malloc">'<tt>malloc</tt>' Instruction</a>
2393</div>
2394
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2395<div class="doc_text">
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2396
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2397<h5>Syntax:</h5>
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2398
2399<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2400 &lt;result&gt; = malloc &lt;type&gt;[, i32 &lt;NumElements&gt;][, align &lt;alignment&gt;] <i>; yields {type*}:result</i>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2401</pre>
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2402
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2403<h5>Overview:</h5>
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2404
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2405<p>The '<tt>malloc</tt>' instruction allocates memory from the system
2406heap and returns a pointer to it.</p>
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2407
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2408<h5>Arguments:</h5>
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2409
2410<p>The '<tt>malloc</tt>' instruction allocates
2411<tt>sizeof(&lt;type&gt;)*NumElements</tt>
John Criswell6e4ca612004-02-24 16:13:56 +0000[diff] [blame]2412bytes of memory from the operating system and returns a pointer of the
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2413appropriate type to the program. If "NumElements" is specified, it is the
2414number of elements allocated. If an alignment is specified, the value result
2415of the allocation is guaranteed to be aligned to at least that boundary. If
2416not specified, or if zero, the target can choose to align the allocation on any
2417convenient boundary.</p>
2418
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2419<p>'<tt>type</tt>' must be a sized type.</p>
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2420
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2421<h5>Semantics:</h5>
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2422
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2423<p>Memory is allocated using the system "<tt>malloc</tt>" function, and
2424a pointer is returned.</p>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2425
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2426<h5>Example:</h5>
2427
2428<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2429 %array = malloc [4 x i8 ] <i>; yields {[%4 x i8]*}:array</i>
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2430
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2431 %size = <a href="#i_add">add</a> i32 2, 2 <i>; yields {i32}:size = i32 4</i>
2432 %array1 = malloc i8, i32 4 <i>; yields {i8*}:array1</i>
2433 %array2 = malloc [12 x i8], i32 %size <i>; yields {[12 x i8]*}:array2</i>
2434 %array3 = malloc i32, i32 4, align 1024 <i>; yields {i32*}:array3</i>
2435 %array4 = malloc i32, align 1024 <i>; yields {i32*}:array4</i>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2436</pre>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2437</div>
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2438
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2439<!-- _______________________________________________________________________ -->
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2440<div class="doc_subsubsection">
2441 <a name="i_free">'<tt>free</tt>' Instruction</a>
2442</div>
2443
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2444<div class="doc_text">
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2445
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2446<h5>Syntax:</h5>
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2447
2448<pre>
2449 free &lt;type&gt; &lt;value&gt; <i>; yields {void}</i>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2450</pre>
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2451
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2452<h5>Overview:</h5>
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2453
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2454<p>The '<tt>free</tt>' instruction returns memory back to the unused
John Criswellc1f786c2005-05-13 22:25:59 +0000[diff] [blame]2455memory heap to be reallocated in the future.</p>
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2456
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2457<h5>Arguments:</h5>
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2458
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2459<p>'<tt>value</tt>' shall be a pointer value that points to a value
2460that was allocated with the '<tt><a href="#i_malloc">malloc</a></tt>'
2461instruction.</p>
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2462
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2463<h5>Semantics:</h5>
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2464
John Criswell9e2485c2004-12-10 15:51:16 +0000[diff] [blame]2465<p>Access to the memory pointed to by the pointer is no longer defined
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2466after this instruction executes.</p>
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2467
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2468<h5>Example:</h5>
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2469
2470<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2471 %array = <a href="#i_malloc">malloc</a> [4 x i8] <i>; yields {[4 x i8]*}:array</i>
2472 free [4 x i8]* %array
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2473</pre>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2474</div>
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2475
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2476<!-- _______________________________________________________________________ -->
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2477<div class="doc_subsubsection">
2478 <a name="i_alloca">'<tt>alloca</tt>' Instruction</a>
2479</div>
2480
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2481<div class="doc_text">
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2482
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2483<h5>Syntax:</h5>
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2484
2485<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2486 &lt;result&gt; = alloca &lt;type&gt;[, i32 &lt;NumElements&gt;][, align &lt;alignment&gt;] <i>; yields {type*}:result</i>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2487</pre>
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2488
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2489<h5>Overview:</h5>
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2490
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2491<p>The '<tt>alloca</tt>' instruction allocates memory on the current
2492stack frame of the procedure that is live until the current function
2493returns to its caller.</p>
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2494
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2495<h5>Arguments:</h5>
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2496
John Criswell9e2485c2004-12-10 15:51:16 +0000[diff] [blame]2497<p>The '<tt>alloca</tt>' instruction allocates <tt>sizeof(&lt;type&gt;)*NumElements</tt>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2498bytes of memory on the runtime stack, returning a pointer of the
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2499appropriate type to the program. If "NumElements" is specified, it is the
2500number of elements allocated. If an alignment is specified, the value result
2501of the allocation is guaranteed to be aligned to at least that boundary. If
2502not specified, or if zero, the target can choose to align the allocation on any
2503convenient boundary.</p>
2504
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2505<p>'<tt>type</tt>' may be any sized type.</p>
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2506
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2507<h5>Semantics:</h5>
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2508
John Criswellc1f786c2005-05-13 22:25:59 +0000[diff] [blame]2509<p>Memory is allocated; a pointer is returned. '<tt>alloca</tt>'d
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2510memory is automatically released when the function returns. The '<tt>alloca</tt>'
2511instruction is commonly used to represent automatic variables that must
2512have an address available. When the function returns (either with the <tt><a
John Criswelldae2e932005-05-12 16:55:34 +0000[diff] [blame]2513 href="#i_ret">ret</a></tt> or <tt><a href="#i_unwind">unwind</a></tt>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2514instructions), the memory is reclaimed.</p>
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2515
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2516<h5>Example:</h5>
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2517
2518<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2519 %ptr = alloca i32 <i>; yields {i32*}:ptr</i>
2520 %ptr = alloca i32, i32 4 <i>; yields {i32*}:ptr</i>
2521 %ptr = alloca i32, i32 4, align 1024 <i>; yields {i32*}:ptr</i>
2522 %ptr = alloca i32, align 1024 <i>; yields {i32*}:ptr</i>
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2523</pre>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2524</div>
Chris Lattner2cbdc452005-11-06 08:02:57 +0000[diff] [blame]2525
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2526<!-- _______________________________________________________________________ -->
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2527<div class="doc_subsubsection"> <a name="i_load">'<tt>load</tt>'
2528Instruction</a> </div>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2529<div class="doc_text">
Chris Lattner2b7d3202002-05-06 03:03:22 +0000[diff] [blame]2530<h5>Syntax:</h5>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2531<pre> &lt;result&gt; = load &lt;ty&gt;* &lt;pointer&gt;<br> &lt;result&gt; = volatile load &lt;ty&gt;* &lt;pointer&gt;<br></pre>
Chris Lattner2b7d3202002-05-06 03:03:22 +0000[diff] [blame]2532<h5>Overview:</h5>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2533<p>The '<tt>load</tt>' instruction is used to read from memory.</p>
Chris Lattner2b7d3202002-05-06 03:03:22 +0000[diff] [blame]2534<h5>Arguments:</h5>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2535<p>The argument to the '<tt>load</tt>' instruction specifies the memory
John Criswell0ec250c2005-10-24 16:17:18 +0000[diff] [blame]2536address from which to load. The pointer must point to a <a
Chris Lattnere53e5082004-06-03 22:57:15 +0000[diff] [blame]2537 href="#t_firstclass">first class</a> type. If the <tt>load</tt> is
John Criswell0ec250c2005-10-24 16:17:18 +0000[diff] [blame]2538marked as <tt>volatile</tt>, then the optimizer is not allowed to modify
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2539the number or order of execution of this <tt>load</tt> with other
2540volatile <tt>load</tt> and <tt><a href="#i_store">store</a></tt>
2541instructions. </p>
Chris Lattner2b7d3202002-05-06 03:03:22 +0000[diff] [blame]2542<h5>Semantics:</h5>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2543<p>The location of memory pointed to is loaded.</p>
Chris Lattner2b7d3202002-05-06 03:03:22 +0000[diff] [blame]2544<h5>Examples:</h5>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2545<pre> %ptr = <a href="#i_alloca">alloca</a> i32 <i>; yields {i32*}:ptr</i>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2546 <a
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2547 href="#i_store">store</a> i32 3, i32* %ptr <i>; yields {void}</i>
2548 %val = load i32* %ptr <i>; yields {i32}:val = i32 3</i>
Chris Lattner2b7d3202002-05-06 03:03:22 +0000[diff] [blame]2549</pre>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2550</div>
Chris Lattner2b7d3202002-05-06 03:03:22 +0000[diff] [blame]2551<!-- _______________________________________________________________________ -->
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2552<div class="doc_subsubsection"> <a name="i_store">'<tt>store</tt>'
2553Instruction</a> </div>
Reid Spencer035ab572006-11-09 21:18:01 +0000[diff] [blame]2554<div class="doc_text">
Chris Lattner2b7d3202002-05-06 03:03:22 +0000[diff] [blame]2555<h5>Syntax:</h5>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2556<pre> store &lt;ty&gt; &lt;value&gt;, &lt;ty&gt;* &lt;pointer&gt; <i>; yields {void}</i>
Chris Lattnerf0651072003-09-08 18:27:49 +0000[diff] [blame]2557 volatile store &lt;ty&gt; &lt;value&gt;, &lt;ty&gt;* &lt;pointer&gt; <i>; yields {void}</i>
Chris Lattner2b7d3202002-05-06 03:03:22 +0000[diff] [blame]2558</pre>
Chris Lattner2b7d3202002-05-06 03:03:22 +0000[diff] [blame]2559<h5>Overview:</h5>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2560<p>The '<tt>store</tt>' instruction is used to write to memory.</p>
Chris Lattner2b7d3202002-05-06 03:03:22 +0000[diff] [blame]2561<h5>Arguments:</h5>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2562<p>There are two arguments to the '<tt>store</tt>' instruction: a value
John Criswell0ec250c2005-10-24 16:17:18 +0000[diff] [blame]2563to store and an address in which to store it. The type of the '<tt>&lt;pointer&gt;</tt>'
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2564operand must be a pointer to the type of the '<tt>&lt;value&gt;</tt>'
John Criswellc1f786c2005-05-13 22:25:59 +0000[diff] [blame]2565operand. If the <tt>store</tt> is marked as <tt>volatile</tt>, then the
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2566optimizer is not allowed to modify the number or order of execution of
2567this <tt>store</tt> with other volatile <tt>load</tt> and <tt><a
2568 href="#i_store">store</a></tt> instructions.</p>
2569<h5>Semantics:</h5>
2570<p>The contents of memory are updated to contain '<tt>&lt;value&gt;</tt>'
2571at the location specified by the '<tt>&lt;pointer&gt;</tt>' operand.</p>
Chris Lattner2b7d3202002-05-06 03:03:22 +0000[diff] [blame]2572<h5>Example:</h5>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2573<pre> %ptr = <a href="#i_alloca">alloca</a> i32 <i>; yields {i32*}:ptr</i>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2574 <a
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2575 href="#i_store">store</a> i32 3, i32* %ptr <i>; yields {void}</i>
2576 %val = load i32* %ptr <i>; yields {i32}:val = i32 3</i>
Chris Lattner2b7d3202002-05-06 03:03:22 +0000[diff] [blame]2577</pre>
Reid Spencer47ce1792006-11-09 21:15:49 +0000[diff] [blame]2578</div>
2579
Chris Lattner2b7d3202002-05-06 03:03:22 +0000[diff] [blame]2580<!-- _______________________________________________________________________ -->
Chris Lattnerf74d5c72004-04-05 01:30:49 +0000[diff] [blame]2581<div class="doc_subsubsection">
2582 <a name="i_getelementptr">'<tt>getelementptr</tt>' Instruction</a>
2583</div>
2584
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2585<div class="doc_text">
Chris Lattner7faa8832002-04-14 06:13:44 +0000[diff] [blame]2586<h5>Syntax:</h5>
Chris Lattnerf74d5c72004-04-05 01:30:49 +0000[diff] [blame]2587<pre>
2588 &lt;result&gt; = getelementptr &lt;ty&gt;* &lt;ptrval&gt;{, &lt;ty&gt; &lt;idx&gt;}*
2589</pre>
2590
Chris Lattner7faa8832002-04-14 06:13:44 +0000[diff] [blame]2591<h5>Overview:</h5>
Chris Lattnerf74d5c72004-04-05 01:30:49 +0000[diff] [blame]2592
2593<p>
2594The '<tt>getelementptr</tt>' instruction is used to get the address of a
2595subelement of an aggregate data structure.</p>
2596
Chris Lattner7faa8832002-04-14 06:13:44 +0000[diff] [blame]2597<h5>Arguments:</h5>
Chris Lattnerf74d5c72004-04-05 01:30:49 +0000[diff] [blame]2598
Reid Spencer85f5b5b2006-12-04 21:29:24 +0000[diff] [blame]2599<p>This instruction takes a list of integer operands that indicate what
Chris Lattnerf74d5c72004-04-05 01:30:49 +0000[diff] [blame]2600elements of the aggregate object to index to. The actual types of the arguments
2601provided depend on the type of the first pointer argument. The
2602'<tt>getelementptr</tt>' instruction is used to index down through the type
John Criswellfc6b8952005-05-16 16:17:45 +0000[diff] [blame]2603levels of a structure or to a specific index in an array. When indexing into a
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2604structure, only <tt>i32</tt> integer constants are allowed. When indexing
Reid Spencer85f5b5b2006-12-04 21:29:24 +0000[diff] [blame]2605into an array or pointer, only integers of 32 or 64 bits are allowed, and will
2606be sign extended to 64-bit values.</p>
Chris Lattnerf74d5c72004-04-05 01:30:49 +0000[diff] [blame]2607
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2608<p>For example, let's consider a C code fragment and how it gets
2609compiled to LLVM:</p>
Chris Lattnerf74d5c72004-04-05 01:30:49 +0000[diff] [blame]2610
2611<pre>
2612 struct RT {
2613 char A;
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2614 i32 B[10][20];
Chris Lattnerf74d5c72004-04-05 01:30:49 +0000[diff] [blame]2615 char C;
2616 };
2617 struct ST {
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2618 i32 X;
Chris Lattnerf74d5c72004-04-05 01:30:49 +0000[diff] [blame]2619 double Y;
2620 struct RT Z;
2621 };
2622
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2623 define i32 *foo(struct ST *s) {
Chris Lattnerf74d5c72004-04-05 01:30:49 +0000[diff] [blame]2624 return &amp;s[1].Z.B[5][13];
2625 }
2626</pre>
2627
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2628<p>The LLVM code generated by the GCC frontend is:</p>
Chris Lattnerf74d5c72004-04-05 01:30:49 +0000[diff] [blame]2629
2630<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2631 %RT = type { i8 , [10 x [20 x i32]], i8 }
2632 %ST = type { i32, double, %RT }
Chris Lattnerf74d5c72004-04-05 01:30:49 +0000[diff] [blame]2633
Brian Gaeke7283e7c2004-07-02 21:08:14 +0000[diff] [blame]2634 implementation
2635
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2636 define i32* %foo(%ST* %s) {
Brian Gaeke7283e7c2004-07-02 21:08:14 +0000[diff] [blame]2637 entry:
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2638 %reg = getelementptr %ST* %s, i32 1, i32 2, i32 1, i32 5, i32 13
2639 ret i32* %reg
Chris Lattnerf74d5c72004-04-05 01:30:49 +0000[diff] [blame]2640 }
2641</pre>
2642
Chris Lattner7faa8832002-04-14 06:13:44 +0000[diff] [blame]2643<h5>Semantics:</h5>
Chris Lattnerf74d5c72004-04-05 01:30:49 +0000[diff] [blame]2644
2645<p>The index types specified for the '<tt>getelementptr</tt>' instruction depend
John Criswellc1f786c2005-05-13 22:25:59 +0000[diff] [blame]2646on the pointer type that is being indexed into. <a href="#t_pointer">Pointer</a>
Reid Spencer85f5b5b2006-12-04 21:29:24 +0000[diff] [blame]2647and <a href="#t_array">array</a> types can use a 32-bit or 64-bit
Reid Spencer42ddd842006-12-03 16:53:48 +0000[diff] [blame]2648<a href="#t_integer">integer</a> type but the value will always be sign extended
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2649to 64-bits. <a href="#t_struct">Structure</a> types, require <tt>i32</tt>
Reid Spencer42ddd842006-12-03 16:53:48 +0000[diff] [blame]2650<b>constants</b>.</p>
Chris Lattnerf74d5c72004-04-05 01:30:49 +0000[diff] [blame]2651
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2652<p>In the example above, the first index is indexing into the '<tt>%ST*</tt>'
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2653type, which is a pointer, yielding a '<tt>%ST</tt>' = '<tt>{ i32, double, %RT
Chris Lattnerf74d5c72004-04-05 01:30:49 +0000[diff] [blame]2654}</tt>' type, a structure. The second index indexes into the third element of
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2655the structure, yielding a '<tt>%RT</tt>' = '<tt>{ i8 , [10 x [20 x i32]],
2656i8 }</tt>' type, another structure. The third index indexes into the second
2657element of the structure, yielding a '<tt>[10 x [20 x i32]]</tt>' type, an
Chris Lattnerf74d5c72004-04-05 01:30:49 +0000[diff] [blame]2658array. The two dimensions of the array are subscripted into, yielding an
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2659'<tt>i32</tt>' type. The '<tt>getelementptr</tt>' instruction returns a pointer
2660to this element, thus computing a value of '<tt>i32*</tt>' type.</p>
Chris Lattnerf74d5c72004-04-05 01:30:49 +0000[diff] [blame]2661
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]2662<p>Note that it is perfectly legal to index partially through a
2663structure, returning a pointer to an inner element. Because of this,
2664the LLVM code for the given testcase is equivalent to:</p>
Chris Lattnerf74d5c72004-04-05 01:30:49 +0000[diff] [blame]2665
2666<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2667 define i32* %foo(%ST* %s) {
2668 %t1 = getelementptr %ST* %s, i32 1 <i>; yields %ST*:%t1</i>
2669 %t2 = getelementptr %ST* %t1, i32 0, i32 2 <i>; yields %RT*:%t2</i>
2670 %t3 = getelementptr %RT* %t2, i32 0, i32 1 <i>; yields [10 x [20 x i32]]*:%t3</i>
2671 %t4 = getelementptr [10 x [20 x i32]]* %t3, i32 0, i32 5 <i>; yields [20 x i32]*:%t4</i>
2672 %t5 = getelementptr [20 x i32]* %t4, i32 0, i32 13 <i>; yields i32*:%t5</i>
2673 ret i32* %t5
Chris Lattnerf74d5c72004-04-05 01:30:49 +0000[diff] [blame]2674 }
Chris Lattner6536cfe2002-05-06 22:08:29 +0000[diff] [blame]2675</pre>
Chris Lattnere67a9512005-06-24 17:22:57 +0000[diff] [blame]2676
2677<p>Note that it is undefined to access an array out of bounds: array and
2678pointer indexes must always be within the defined bounds of the array type.
2679The one exception for this rules is zero length arrays. These arrays are
2680defined to be accessible as variable length arrays, which requires access
2681beyond the zero'th element.</p>
2682
Chris Lattner884a9702006-08-15 00:45:58 +0000[diff] [blame]2683<p>The getelementptr instruction is often confusing. For some more insight
2684into how it works, see <a href="GetElementPtr.html">the getelementptr
2685FAQ</a>.</p>
2686
Chris Lattner7faa8832002-04-14 06:13:44 +0000[diff] [blame]2687<h5>Example:</h5>
Chris Lattnere67a9512005-06-24 17:22:57 +0000[diff] [blame]2688
Chris Lattnerf74d5c72004-04-05 01:30:49 +0000[diff] [blame]2689<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2690 <i>; yields [12 x i8]*:aptr</i>
2691 %aptr = getelementptr {i32, [12 x i8]}* %sptr, i64 0, i32 1
Chris Lattnerf74d5c72004-04-05 01:30:49 +0000[diff] [blame]2692</pre>
Chris Lattnerf74d5c72004-04-05 01:30:49 +0000[diff] [blame]2693</div>
Reid Spencer47ce1792006-11-09 21:15:49 +0000[diff] [blame]2694
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]2695<!-- ======================================================================= -->
Reid Spencer2fd21e62006-11-08 01:18:52 +0000[diff] [blame]2696<div class="doc_subsection"> <a name="convertops">Conversion Operations</a>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2697</div>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2698<div class="doc_text">
Reid Spencer2fd21e62006-11-08 01:18:52 +0000[diff] [blame]2699<p>The instructions in this category are the conversion instructions (casting)
2700which all take a single operand and a type. They perform various bit conversions
2701on the operand.</p>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]2702</div>
Chris Lattnercc37aae2004-03-12 05:50:16 +0000[diff] [blame]2703
Chris Lattner6536cfe2002-05-06 22:08:29 +0000[diff] [blame]2704<!-- _______________________________________________________________________ -->
Chris Lattnercc37aae2004-03-12 05:50:16 +0000[diff] [blame]2705<div class="doc_subsubsection">
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]2706 <a name="i_trunc">'<tt>trunc .. to</tt>' Instruction</a>
2707</div>
2708<div class="doc_text">
2709
2710<h5>Syntax:</h5>
2711<pre>
2712 &lt;result&gt; = trunc &lt;ty&gt; &lt;value&gt; to &lt;ty2&gt; <i>; yields ty2</i>
2713</pre>
2714
2715<h5>Overview:</h5>
2716<p>
2717The '<tt>trunc</tt>' instruction truncates its operand to the type <tt>ty2</tt>.
2718</p>
2719
2720<h5>Arguments:</h5>
2721<p>
2722The '<tt>trunc</tt>' instruction takes a <tt>value</tt> to trunc, which must
2723be an <a href="#t_integer">integer</a> type, and a type that specifies the size
Chris Lattner3b19d652007-01-15 01:54:13 +0000[diff] [blame]2724and type of the result, which must be an <a href="#t_integer">integer</a>
Reid Spencerd4448792006-11-09 23:03:26 +0000[diff] [blame]2725type. The bit size of <tt>value</tt> must be larger than the bit size of
2726<tt>ty2</tt>. Equal sized types are not allowed.</p>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]2727
2728<h5>Semantics:</h5>
2729<p>
2730The '<tt>trunc</tt>' instruction truncates the high order bits in <tt>value</tt>
Reid Spencerd4448792006-11-09 23:03:26 +0000[diff] [blame]2731and converts the remaining bits to <tt>ty2</tt>. Since the source size must be
2732larger than the destination size, <tt>trunc</tt> cannot be a <i>no-op cast</i>.
2733It will always truncate bits.</p>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]2734
2735<h5>Example:</h5>
2736<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2737 %X = trunc i32 257 to i8 <i>; yields i8:1</i>
Reid Spencerc78f3372007-01-12 03:35:51 +0000[diff] [blame]2738 %Y = trunc i32 123 to i1 <i>; yields i1:true</i>
2739 %Y = trunc i32 122 to i1 <i>; yields i1:false</i>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]2740</pre>
2741</div>
2742
2743<!-- _______________________________________________________________________ -->
2744<div class="doc_subsubsection">
2745 <a name="i_zext">'<tt>zext .. to</tt>' Instruction</a>
2746</div>
2747<div class="doc_text">
2748
2749<h5>Syntax:</h5>
2750<pre>
2751 &lt;result&gt; = zext &lt;ty&gt; &lt;value&gt; to &lt;ty2&gt; <i>; yields ty2</i>
2752</pre>
2753
2754<h5>Overview:</h5>
2755<p>The '<tt>zext</tt>' instruction zero extends its operand to type
2756<tt>ty2</tt>.</p>
2757
2758
2759<h5>Arguments:</h5>
2760<p>The '<tt>zext</tt>' instruction takes a value to cast, which must be of
Chris Lattner3b19d652007-01-15 01:54:13 +0000[diff] [blame]2761<a href="#t_integer">integer</a> type, and a type to cast it to, which must
2762also be of <a href="#t_integer">integer</a> type. The bit size of the
Reid Spencerd4448792006-11-09 23:03:26 +0000[diff] [blame]2763<tt>value</tt> must be smaller than the bit size of the destination type,
2764<tt>ty2</tt>.</p>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]2765
2766<h5>Semantics:</h5>
2767<p>The <tt>zext</tt> fills the high order bits of the <tt>value</tt> with zero
2768bits until it reaches the size of the destination type, <tt>ty2</tt>. When the
2769the operand and the type are the same size, no bit filling is done and the
2770cast is considered a <i>no-op cast</i> because no bits change (only the type
2771changes).</p>
2772
Reid Spencerb5929522007-01-12 15:46:11 +0000[diff] [blame]2773<p>When zero extending from i1, the result will always be either 0 or 1.</p>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]2774
2775<h5>Example:</h5>
2776<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2777 %X = zext i32 257 to i64 <i>; yields i64:257</i>
Reid Spencerc78f3372007-01-12 03:35:51 +0000[diff] [blame]2778 %Y = zext i1 true to i32 <i>; yields i32:1</i>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]2779</pre>
2780</div>
2781
2782<!-- _______________________________________________________________________ -->
2783<div class="doc_subsubsection">
2784 <a name="i_sext">'<tt>sext .. to</tt>' Instruction</a>
2785</div>
2786<div class="doc_text">
2787
2788<h5>Syntax:</h5>
2789<pre>
2790 &lt;result&gt; = sext &lt;ty&gt; &lt;value&gt; to &lt;ty2&gt; <i>; yields ty2</i>
2791</pre>
2792
2793<h5>Overview:</h5>
2794<p>The '<tt>sext</tt>' sign extends <tt>value</tt> to the type <tt>ty2</tt>.</p>
2795
2796<h5>Arguments:</h5>
2797<p>
2798The '<tt>sext</tt>' instruction takes a value to cast, which must be of
Chris Lattner3b19d652007-01-15 01:54:13 +0000[diff] [blame]2799<a href="#t_integer">integer</a> type, and a type to cast it to, which must
2800also be of <a href="#t_integer">integer</a> type. The bit size of the
Reid Spencerd4448792006-11-09 23:03:26 +0000[diff] [blame]2801<tt>value</tt> must be smaller than the bit size of the destination type,
2802<tt>ty2</tt>.</p>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]2803
2804<h5>Semantics:</h5>
2805<p>
2806The '<tt>sext</tt>' instruction performs a sign extension by copying the sign
2807bit (highest order bit) of the <tt>value</tt> until it reaches the bit size of
2808the type <tt>ty2</tt>. When the the operand and the type are the same size,
2809no bit filling is done and the cast is considered a <i>no-op cast</i> because
2810no bits change (only the type changes).</p>
2811
Reid Spencerc78f3372007-01-12 03:35:51 +0000[diff] [blame]2812<p>When sign extending from i1, the extension always results in -1 or 0.</p>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]2813
2814<h5>Example:</h5>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]2815<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2816 %X = sext i8 -1 to i16 <i>; yields i16 :65535</i>
Reid Spencerc78f3372007-01-12 03:35:51 +0000[diff] [blame]2817 %Y = sext i1 true to i32 <i>; yields i32:-1</i>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]2818</pre>
2819</div>
2820
2821<!-- _______________________________________________________________________ -->
2822<div class="doc_subsubsection">
Reid Spencer3fa91b02006-11-09 21:48:10 +0000[diff] [blame]2823 <a name="i_fptrunc">'<tt>fptrunc .. to</tt>' Instruction</a>
2824</div>
2825
2826<div class="doc_text">
2827
2828<h5>Syntax:</h5>
2829
2830<pre>
2831 &lt;result&gt; = fptrunc &lt;ty&gt; &lt;value&gt; to &lt;ty2&gt; <i>; yields ty2</i>
2832</pre>
2833
2834<h5>Overview:</h5>
2835<p>The '<tt>fptrunc</tt>' instruction truncates <tt>value</tt> to type
2836<tt>ty2</tt>.</p>
2837
2838
2839<h5>Arguments:</h5>
2840<p>The '<tt>fptrunc</tt>' instruction takes a <a href="#t_floating">floating
2841 point</a> value to cast and a <a href="#t_floating">floating point</a> type to
2842cast it to. The size of <tt>value</tt> must be larger than the size of
2843<tt>ty2</tt>. This implies that <tt>fptrunc</tt> cannot be used to make a
2844<i>no-op cast</i>.</p>
2845
2846<h5>Semantics:</h5>
Reid Spencerd4448792006-11-09 23:03:26 +0000[diff] [blame]2847<p> The '<tt>fptrunc</tt>' instruction truncates a <tt>value</tt> from a larger
2848<a href="#t_floating">floating point</a> type to a smaller
2849<a href="#t_floating">floating point</a> type. If the value cannot fit within
2850the destination type, <tt>ty2</tt>, then the results are undefined.</p>
Reid Spencer3fa91b02006-11-09 21:48:10 +0000[diff] [blame]2851
2852<h5>Example:</h5>
2853<pre>
2854 %X = fptrunc double 123.0 to float <i>; yields float:123.0</i>
2855 %Y = fptrunc double 1.0E+300 to float <i>; yields undefined</i>
2856</pre>
2857</div>
2858
2859<!-- _______________________________________________________________________ -->
2860<div class="doc_subsubsection">
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]2861 <a name="i_fpext">'<tt>fpext .. to</tt>' Instruction</a>
2862</div>
2863<div class="doc_text">
2864
2865<h5>Syntax:</h5>
2866<pre>
2867 &lt;result&gt; = fpext &lt;ty&gt; &lt;value&gt; to &lt;ty2&gt; <i>; yields ty2</i>
2868</pre>
2869
2870<h5>Overview:</h5>
2871<p>The '<tt>fpext</tt>' extends a floating point <tt>value</tt> to a larger
2872floating point value.</p>
2873
2874<h5>Arguments:</h5>
2875<p>The '<tt>fpext</tt>' instruction takes a
2876<a href="#t_floating">floating point</a> <tt>value</tt> to cast,
Reid Spencerd4448792006-11-09 23:03:26 +0000[diff] [blame]2877and a <a href="#t_floating">floating point</a> type to cast it to. The source
2878type must be smaller than the destination type.</p>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]2879
2880<h5>Semantics:</h5>
Reid Spencerd4448792006-11-09 23:03:26 +0000[diff] [blame]2881<p>The '<tt>fpext</tt>' instruction extends the <tt>value</tt> from a smaller
2882<a href="t_floating">floating point</a> type to a larger
2883<a href="t_floating">floating point</a> type. The <tt>fpext</tt> cannot be
2884used to make a <i>no-op cast</i> because it always changes bits. Use
Reid Spencer5c0ef472006-11-11 23:08:07 +0000[diff] [blame]2885<tt>bitcast</tt> to make a <i>no-op cast</i> for a floating point cast.</p>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]2886
2887<h5>Example:</h5>
2888<pre>
2889 %X = fpext float 3.1415 to double <i>; yields double:3.1415</i>
2890 %Y = fpext float 1.0 to float <i>; yields float:1.0 (no-op)</i>
2891</pre>
2892</div>
2893
2894<!-- _______________________________________________________________________ -->
2895<div class="doc_subsubsection">
Reid Spencer24d6da52007-01-21 00:29:26 +0000[diff] [blame]2896 <a name="i_fptoui">'<tt>fptoui .. to</tt>' Instruction</a>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]2897</div>
2898<div class="doc_text">
2899
2900<h5>Syntax:</h5>
2901<pre>
2902 &lt;result&gt; = fp2uint &lt;ty&gt; &lt;value&gt; to &lt;ty2&gt; <i>; yields ty2</i>
2903</pre>
2904
2905<h5>Overview:</h5>
2906<p>The '<tt>fp2uint</tt>' converts a floating point <tt>value</tt> to its
2907unsigned integer equivalent of type <tt>ty2</tt>.
2908</p>
2909
2910<h5>Arguments:</h5>
2911<p>The '<tt>fp2uint</tt>' instruction takes a value to cast, which must be a
2912<a href="#t_floating">floating point</a> value, and a type to cast it to, which
Chris Lattner3b19d652007-01-15 01:54:13 +0000[diff] [blame]2913must be an <a href="#t_integer">integer</a> type.</p>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]2914
2915<h5>Semantics:</h5>
2916<p> The '<tt>fp2uint</tt>' instruction converts its
2917<a href="#t_floating">floating point</a> operand into the nearest (rounding
2918towards zero) unsigned integer value. If the value cannot fit in <tt>ty2</tt>,
2919the results are undefined.</p>
2920
Reid Spencerc78f3372007-01-12 03:35:51 +0000[diff] [blame]2921<p>When converting to i1, the conversion is done as a comparison against
2922zero. If the <tt>value</tt> was zero, the i1 result will be <tt>false</tt>.
2923If the <tt>value</tt> was non-zero, the i1 result will be <tt>true</tt>.</p>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]2924
2925<h5>Example:</h5>
2926<pre>
Reid Spencerc78f3372007-01-12 03:35:51 +0000[diff] [blame]2927 %X = fp2uint double 123.0 to i32 <i>; yields i32:123</i>
2928 %Y = fp2uint float 1.0E+300 to i1 <i>; yields i1:true</i>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2929 %X = fp2uint float 1.04E+17 to i8 <i>; yields undefined:1</i>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]2930</pre>
2931</div>
2932
2933<!-- _______________________________________________________________________ -->
2934<div class="doc_subsubsection">
Reid Spencerd4448792006-11-09 23:03:26 +0000[diff] [blame]2935 <a name="i_fptosi">'<tt>fptosi .. to</tt>' Instruction</a>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]2936</div>
2937<div class="doc_text">
2938
2939<h5>Syntax:</h5>
2940<pre>
Reid Spencerd4448792006-11-09 23:03:26 +0000[diff] [blame]2941 &lt;result&gt; = fptosi &lt;ty&gt; &lt;value&gt; to &lt;ty2&gt; <i>; yields ty2</i>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]2942</pre>
2943
2944<h5>Overview:</h5>
Reid Spencerd4448792006-11-09 23:03:26 +0000[diff] [blame]2945<p>The '<tt>fptosi</tt>' instruction converts
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]2946<a href="#t_floating">floating point</a> <tt>value</tt> to type <tt>ty2</tt>.
Chris Lattnercc37aae2004-03-12 05:50:16 +0000[diff] [blame]2947</p>
2948
2949
Chris Lattner6536cfe2002-05-06 22:08:29 +0000[diff] [blame]2950<h5>Arguments:</h5>
Reid Spencerd4448792006-11-09 23:03:26 +0000[diff] [blame]2951<p> The '<tt>fptosi</tt>' instruction takes a value to cast, which must be a
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]2952<a href="#t_floating">floating point</a> value, and a type to cast it to, which
Chris Lattner3b19d652007-01-15 01:54:13 +0000[diff] [blame]2953must also be an <a href="#t_integer">integer</a> type.</p>
Chris Lattnercc37aae2004-03-12 05:50:16 +0000[diff] [blame]2954
Chris Lattner6536cfe2002-05-06 22:08:29 +0000[diff] [blame]2955<h5>Semantics:</h5>
Reid Spencerd4448792006-11-09 23:03:26 +0000[diff] [blame]2956<p>The '<tt>fptosi</tt>' instruction converts its
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]2957<a href="#t_floating">floating point</a> operand into the nearest (rounding
2958towards zero) signed integer value. If the value cannot fit in <tt>ty2</tt>,
2959the results are undefined.</p>
Chris Lattnercc37aae2004-03-12 05:50:16 +0000[diff] [blame]2960
Reid Spencerc78f3372007-01-12 03:35:51 +0000[diff] [blame]2961<p>When converting to i1, the conversion is done as a comparison against
2962zero. If the <tt>value</tt> was zero, the i1 result will be <tt>false</tt>.
2963If the <tt>value</tt> was non-zero, the i1 result will be <tt>true</tt>.</p>
Chris Lattnercc37aae2004-03-12 05:50:16 +0000[diff] [blame]2964
Chris Lattner33ba0d92001-07-09 00:26:23 +0000[diff] [blame]2965<h5>Example:</h5>
Chris Lattnercc37aae2004-03-12 05:50:16 +0000[diff] [blame]2966<pre>
Reid Spencerc78f3372007-01-12 03:35:51 +0000[diff] [blame]2967 %X = fptosi double -123.0 to i32 <i>; yields i32:-123</i>
2968 %Y = fptosi float 1.0E-247 to i1 <i>; yields i1:true</i>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]2969 %X = fptosi float 1.04E+17 to i8 <i>; yields undefined:1</i>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]2970</pre>
2971</div>
2972
2973<!-- _______________________________________________________________________ -->
2974<div class="doc_subsubsection">
Reid Spencerd4448792006-11-09 23:03:26 +0000[diff] [blame]2975 <a name="i_uitofp">'<tt>uitofp .. to</tt>' Instruction</a>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]2976</div>
2977<div class="doc_text">
2978
2979<h5>Syntax:</h5>
2980<pre>
Reid Spencerd4448792006-11-09 23:03:26 +0000[diff] [blame]2981 &lt;result&gt; = uitofp &lt;ty&gt; &lt;value&gt; to &lt;ty2&gt; <i>; yields ty2</i>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]2982</pre>
2983
2984<h5>Overview:</h5>
Reid Spencerd4448792006-11-09 23:03:26 +0000[diff] [blame]2985<p>The '<tt>uitofp</tt>' instruction regards <tt>value</tt> as an unsigned
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]2986integer and converts that value to the <tt>ty2</tt> type.</p>
2987
2988
2989<h5>Arguments:</h5>
Reid Spencerd4448792006-11-09 23:03:26 +0000[diff] [blame]2990<p>The '<tt>uitofp</tt>' instruction takes a value to cast, which must be an
Chris Lattner3b19d652007-01-15 01:54:13 +0000[diff] [blame]2991<a href="#t_integer">integer</a> value, and a type to cast it to, which must
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]2992be a <a href="#t_floating">floating point</a> type.</p>
2993
2994<h5>Semantics:</h5>
Reid Spencerd4448792006-11-09 23:03:26 +0000[diff] [blame]2995<p>The '<tt>uitofp</tt>' instruction interprets its operand as an unsigned
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]2996integer quantity and converts it to the corresponding floating point value. If
2997the value cannot fit in the floating point value, the results are undefined.</p>
2998
2999
3000<h5>Example:</h5>
3001<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]3002 %X = uitofp i32 257 to float <i>; yields float:257.0</i>
3003 %Y = uitofp i8 -1 to double <i>; yields double:255.0</i>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]3004</pre>
3005</div>
3006
3007<!-- _______________________________________________________________________ -->
3008<div class="doc_subsubsection">
Reid Spencerd4448792006-11-09 23:03:26 +0000[diff] [blame]3009 <a name="i_sitofp">'<tt>sitofp .. to</tt>' Instruction</a>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]3010</div>
3011<div class="doc_text">
3012
3013<h5>Syntax:</h5>
3014<pre>
Reid Spencerd4448792006-11-09 23:03:26 +0000[diff] [blame]3015 &lt;result&gt; = sitofp &lt;ty&gt; &lt;value&gt; to &lt;ty2&gt; <i>; yields ty2</i>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]3016</pre>
3017
3018<h5>Overview:</h5>
Reid Spencerd4448792006-11-09 23:03:26 +0000[diff] [blame]3019<p>The '<tt>sitofp</tt>' instruction regards <tt>value</tt> as a signed
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]3020integer and converts that value to the <tt>ty2</tt> type.</p>
3021
3022<h5>Arguments:</h5>
Reid Spencerd4448792006-11-09 23:03:26 +0000[diff] [blame]3023<p>The '<tt>sitofp</tt>' instruction takes a value to cast, which must be an
Chris Lattner3b19d652007-01-15 01:54:13 +0000[diff] [blame]3024<a href="#t_integer">integer</a> value, and a type to cast it to, which must be
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]3025a <a href="#t_floating">floating point</a> type.</p>
3026
3027<h5>Semantics:</h5>
Reid Spencerd4448792006-11-09 23:03:26 +0000[diff] [blame]3028<p>The '<tt>sitofp</tt>' instruction interprets its operand as a signed
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]3029integer quantity and converts it to the corresponding floating point value. If
3030the value cannot fit in the floating point value, the results are undefined.</p>
3031
3032<h5>Example:</h5>
3033<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]3034 %X = sitofp i32 257 to float <i>; yields float:257.0</i>
3035 %Y = sitofp i8 -1 to double <i>; yields double:-1.0</i>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]3036</pre>
3037</div>
3038
3039<!-- _______________________________________________________________________ -->
3040<div class="doc_subsubsection">
Reid Spencer72679252006-11-11 21:00:47 +0000[diff] [blame]3041 <a name="i_ptrtoint">'<tt>ptrtoint .. to</tt>' Instruction</a>
3042</div>
3043<div class="doc_text">
3044
3045<h5>Syntax:</h5>
3046<pre>
3047 &lt;result&gt; = ptrtoint &lt;ty&gt; &lt;value&gt; to &lt;ty2&gt; <i>; yields ty2</i>
3048</pre>
3049
3050<h5>Overview:</h5>
3051<p>The '<tt>ptrtoint</tt>' instruction converts the pointer <tt>value</tt> to
3052the integer type <tt>ty2</tt>.</p>
3053
3054<h5>Arguments:</h5>
3055<p>The '<tt>ptrtoint</tt>' instruction takes a <tt>value</tt> to cast, which
3056must be a <a href="t_pointer">pointer</a> value, and a type to cast it to
3057<tt>ty2</tt>, which must be an <a href="#t_integer">integer</a> type.
3058
3059<h5>Semantics:</h5>
3060<p>The '<tt>ptrtoint</tt>' instruction converts <tt>value</tt> to integer type
3061<tt>ty2</tt> by interpreting the pointer value as an integer and either
3062truncating or zero extending that value to the size of the integer type. If
3063<tt>value</tt> is smaller than <tt>ty2</tt> then a zero extension is done. If
3064<tt>value</tt> is larger than <tt>ty2</tt> then a truncation is done. If they
3065are the same size, then nothing is done (<i>no-op cast</i>).</p>
3066
3067<h5>Example:</h5>
3068<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]3069 %X = ptrtoint i32* %X to i8 <i>; yields truncation on 32-bit</i>
3070 %Y = ptrtoint i32* %x to i64 <i>; yields zero extend on 32-bit</i>
Reid Spencer72679252006-11-11 21:00:47 +0000[diff] [blame]3071</pre>
3072</div>
3073
3074<!-- _______________________________________________________________________ -->
3075<div class="doc_subsubsection">
3076 <a name="i_inttoptr">'<tt>inttoptr .. to</tt>' Instruction</a>
3077</div>
3078<div class="doc_text">
3079
3080<h5>Syntax:</h5>
3081<pre>
3082 &lt;result&gt; = inttoptr &lt;ty&gt; &lt;value&gt; to &lt;ty2&gt; <i>; yields ty2</i>
3083</pre>
3084
3085<h5>Overview:</h5>
3086<p>The '<tt>inttoptr</tt>' instruction converts an integer <tt>value</tt> to
3087a pointer type, <tt>ty2</tt>.</p>
3088
3089<h5>Arguments:</h5>
3090<p>The '<tt>inttoptr</tt>' instruction takes an <a href="i_integer">integer</a>
3091value to cast, and a type to cast it to, which must be a
Anton Korobeynikov7f705592007-01-12 19:20:47 +0000[diff] [blame]3092<a href="#t_pointer">pointer</a> type.
Reid Spencer72679252006-11-11 21:00:47 +0000[diff] [blame]3093
3094<h5>Semantics:</h5>
3095<p>The '<tt>inttoptr</tt>' instruction converts <tt>value</tt> to type
3096<tt>ty2</tt> by applying either a zero extension or a truncation depending on
3097the size of the integer <tt>value</tt>. If <tt>value</tt> is larger than the
3098size of a pointer then a truncation is done. If <tt>value</tt> is smaller than
3099the size of a pointer then a zero extension is done. If they are the same size,
3100nothing is done (<i>no-op cast</i>).</p>
3101
3102<h5>Example:</h5>
3103<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]3104 %X = inttoptr i32 255 to i32* <i>; yields zero extend on 64-bit</i>
3105 %X = inttoptr i32 255 to i32* <i>; yields no-op on 32-bit </i>
3106 %Y = inttoptr i16 0 to i32* <i>; yields zero extend on 32-bit</i>
Reid Spencer72679252006-11-11 21:00:47 +0000[diff] [blame]3107</pre>
3108</div>
3109
3110<!-- _______________________________________________________________________ -->
3111<div class="doc_subsubsection">
Reid Spencer5c0ef472006-11-11 23:08:07 +0000[diff] [blame]3112 <a name="i_bitcast">'<tt>bitcast .. to</tt>' Instruction</a>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]3113</div>
3114<div class="doc_text">
3115
3116<h5>Syntax:</h5>
3117<pre>
Reid Spencer5c0ef472006-11-11 23:08:07 +0000[diff] [blame]3118 &lt;result&gt; = bitcast &lt;ty&gt; &lt;value&gt; to &lt;ty2&gt; <i>; yields ty2</i>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]3119</pre>
3120
3121<h5>Overview:</h5>
Reid Spencer5c0ef472006-11-11 23:08:07 +0000[diff] [blame]3122<p>The '<tt>bitcast</tt>' instruction converts <tt>value</tt> to type
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]3123<tt>ty2</tt> without changing any bits.</p>
3124
3125<h5>Arguments:</h5>
Reid Spencer5c0ef472006-11-11 23:08:07 +0000[diff] [blame]3126<p>The '<tt>bitcast</tt>' instruction takes a value to cast, which must be
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]3127a first class value, and a type to cast it to, which must also be a <a
3128 href="#t_firstclass">first class</a> type. The bit sizes of <tt>value</tt>
Reid Spencer19b569f2007-01-09 20:08:58 +0000[diff] [blame]3129and the destination type, <tt>ty2</tt>, must be identical. If the source
3130type is a pointer, the destination type must also be a pointer.</p>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]3131
3132<h5>Semantics:</h5>
Reid Spencer5c0ef472006-11-11 23:08:07 +0000[diff] [blame]3133<p>The '<tt>bitcast</tt>' instruction converts <tt>value</tt> to type
Reid Spencer72679252006-11-11 21:00:47 +0000[diff] [blame]3134<tt>ty2</tt>. It is always a <i>no-op cast</i> because no bits change with
3135this conversion. The conversion is done as if the <tt>value</tt> had been
3136stored to memory and read back as type <tt>ty2</tt>. Pointer types may only be
3137converted to other pointer types with this instruction. To convert pointers to
3138other types, use the <a href="#i_inttoptr">inttoptr</a> or
3139<a href="#i_ptrtoint">ptrtoint</a> instructions first.</p>
Reid Spencer9dee3ac2006-11-08 01:11:31 +0000[diff] [blame]3140
3141<h5>Example:</h5>
3142<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]3143 %X = bitcast i8 255 to i8 <i>; yields i8 :-1</i>
3144 %Y = bitcast i32* %x to sint* <i>; yields sint*:%x</i>
3145 %Z = bitcast <2xint> %V to i64; <i>; yields i64: %V</i>
Chris Lattner33ba0d92001-07-09 00:26:23 +0000[diff] [blame]3146</pre>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]3147</div>
Chris Lattnercc37aae2004-03-12 05:50:16 +0000[diff] [blame]3148
Reid Spencer2fd21e62006-11-08 01:18:52 +0000[diff] [blame]3149<!-- ======================================================================= -->
3150<div class="doc_subsection"> <a name="otherops">Other Operations</a> </div>
3151<div class="doc_text">
3152<p>The instructions in this category are the "miscellaneous"
3153instructions, which defy better classification.</p>
3154</div>
Reid Spencerf3a70a62006-11-18 21:50:54 +0000[diff] [blame]3155
3156<!-- _______________________________________________________________________ -->
3157<div class="doc_subsubsection"><a name="i_icmp">'<tt>icmp</tt>' Instruction</a>
3158</div>
3159<div class="doc_text">
3160<h5>Syntax:</h5>
Reid Spencerc78f3372007-01-12 03:35:51 +0000[diff] [blame]3161<pre> &lt;result&gt; = icmp &lt;cond&gt; &lt;ty&gt; &lt;var1&gt;, &lt;var2&gt;
3162<i>; yields {i1}:result</i>
Reid Spencerf3a70a62006-11-18 21:50:54 +0000[diff] [blame]3163</pre>
3164<h5>Overview:</h5>
3165<p>The '<tt>icmp</tt>' instruction returns a boolean value based on comparison
3166of its two integer operands.</p>
3167<h5>Arguments:</h5>
3168<p>The '<tt>icmp</tt>' instruction takes three operands. The first operand is
3169the condition code which indicates the kind of comparison to perform. It is not
3170a value, just a keyword. The possibilities for the condition code are:
3171<ol>
3172 <li><tt>eq</tt>: equal</li>
3173 <li><tt>ne</tt>: not equal </li>
3174 <li><tt>ugt</tt>: unsigned greater than</li>
3175 <li><tt>uge</tt>: unsigned greater or equal</li>
3176 <li><tt>ult</tt>: unsigned less than</li>
3177 <li><tt>ule</tt>: unsigned less or equal</li>
3178 <li><tt>sgt</tt>: signed greater than</li>
3179 <li><tt>sge</tt>: signed greater or equal</li>
3180 <li><tt>slt</tt>: signed less than</li>
3181 <li><tt>sle</tt>: signed less or equal</li>
3182</ol>
Chris Lattner3b19d652007-01-15 01:54:13 +0000[diff] [blame]3183<p>The remaining two arguments must be <a href="#t_integer">integer</a> or
Reid Spencer350f8aa2007-01-04 05:19:58 +0000[diff] [blame]3184<a href="#t_pointer">pointer</a> typed. They must also be identical types.</p>
Reid Spencerf3a70a62006-11-18 21:50:54 +0000[diff] [blame]3185<h5>Semantics:</h5>
3186<p>The '<tt>icmp</tt>' compares <tt>var1</tt> and <tt>var2</tt> according to
3187the condition code given as <tt>cond</tt>. The comparison performed always
Reid Spencerc78f3372007-01-12 03:35:51 +0000[diff] [blame]3188yields a <a href="#t_primitive">i1</a> result, as follows:
Reid Spencerf3a70a62006-11-18 21:50:54 +0000[diff] [blame]3189<ol>
3190 <li><tt>eq</tt>: yields <tt>true</tt> if the operands are equal,
3191 <tt>false</tt> otherwise. No sign interpretation is necessary or performed.
3192 </li>
3193 <li><tt>ne</tt>: yields <tt>true</tt> if the operands are unequal,
3194 <tt>false</tt> otherwise. No sign interpretation is necessary or performed.
3195 <li><tt>ugt</tt>: interprets the operands as unsigned values and yields
3196 <tt>true</tt> if <tt>var1</tt> is greater than <tt>var2</tt>.</li>
3197 <li><tt>uge</tt>: interprets the operands as unsigned values and yields
3198 <tt>true</tt> if <tt>var1</tt> is greater than or equal to <tt>var2</tt>.</li>
3199 <li><tt>ult</tt>: interprets the operands as unsigned values and yields
3200 <tt>true</tt> if <tt>var1</tt> is less than <tt>var2</tt>.</li>
3201 <li><tt>ule</tt>: interprets the operands as unsigned values and yields
3202 <tt>true</tt> if <tt>var1</tt> is less than or equal to <tt>var2</tt>.</li>
3203 <li><tt>sgt</tt>: interprets the operands as signed values and yields
3204 <tt>true</tt> if <tt>var1</tt> is greater than <tt>var2</tt>.</li>
3205 <li><tt>sge</tt>: interprets the operands as signed values and yields
3206 <tt>true</tt> if <tt>var1</tt> is greater than or equal to <tt>var2</tt>.</li>
3207 <li><tt>slt</tt>: interprets the operands as signed values and yields
3208 <tt>true</tt> if <tt>var1</tt> is less than <tt>var2</tt>.</li>
3209 <li><tt>sle</tt>: interprets the operands as signed values and yields
3210 <tt>true</tt> if <tt>var1</tt> is less than or equal to <tt>var2</tt>.</li>
Reid Spencerf3a70a62006-11-18 21:50:54 +0000[diff] [blame]3211</ol>
3212<p>If the operands are <a href="#t_pointer">pointer</a> typed, the pointer
3213values are treated as integers and then compared.</p>
Reid Spencerf3a70a62006-11-18 21:50:54 +0000[diff] [blame]3214
3215<h5>Example:</h5>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]3216<pre> &lt;result&gt; = icmp eq i32 4, 5 <i>; yields: result=false</i>
3217 &lt;result&gt; = icmp ne float* %X, %X <i>; yields: result=false</i>
3218 &lt;result&gt; = icmp ult i16 4, 5 <i>; yields: result=true</i>
3219 &lt;result&gt; = icmp sgt i16 4, 5 <i>; yields: result=false</i>
3220 &lt;result&gt; = icmp ule i16 -4, 5 <i>; yields: result=false</i>
3221 &lt;result&gt; = icmp sge i16 4, 5 <i>; yields: result=false</i>
Reid Spencerf3a70a62006-11-18 21:50:54 +0000[diff] [blame]3222</pre>
3223</div>
3224
3225<!-- _______________________________________________________________________ -->
3226<div class="doc_subsubsection"><a name="i_fcmp">'<tt>fcmp</tt>' Instruction</a>
3227</div>
3228<div class="doc_text">
3229<h5>Syntax:</h5>
Reid Spencerc78f3372007-01-12 03:35:51 +0000[diff] [blame]3230<pre> &lt;result&gt; = fcmp &lt;cond&gt; &lt;ty&gt; &lt;var1&gt;, &lt;var2&gt;
3231<i>; yields {i1}:result</i>
Reid Spencerf3a70a62006-11-18 21:50:54 +0000[diff] [blame]3232</pre>
3233<h5>Overview:</h5>
3234<p>The '<tt>fcmp</tt>' instruction returns a boolean value based on comparison
3235of its floating point operands.</p>
3236<h5>Arguments:</h5>
3237<p>The '<tt>fcmp</tt>' instruction takes three operands. The first operand is
3238the condition code which indicates the kind of comparison to perform. It is not
3239a value, just a keyword. The possibilities for the condition code are:
3240<ol>
Reid Spencerb7f26282006-11-19 03:00:14 +0000[diff] [blame]3241 <li><tt>false</tt>: no comparison, always returns false</li>
Reid Spencerf3a70a62006-11-18 21:50:54 +0000[diff] [blame]3242 <li><tt>oeq</tt>: ordered and equal</li>
3243 <li><tt>ogt</tt>: ordered and greater than </li>
3244 <li><tt>oge</tt>: ordered and greater than or equal</li>
3245 <li><tt>olt</tt>: ordered and less than </li>
3246 <li><tt>ole</tt>: ordered and less than or equal</li>
3247 <li><tt>one</tt>: ordered and not equal</li>
3248 <li><tt>ord</tt>: ordered (no nans)</li>
3249 <li><tt>ueq</tt>: unordered or equal</li>
3250 <li><tt>ugt</tt>: unordered or greater than </li>
3251 <li><tt>uge</tt>: unordered or greater than or equal</li>
3252 <li><tt>ult</tt>: unordered or less than </li>
3253 <li><tt>ule</tt>: unordered or less than or equal</li>
3254 <li><tt>une</tt>: unordered or not equal</li>
3255 <li><tt>uno</tt>: unordered (either nans)</li>
Reid Spencerb7f26282006-11-19 03:00:14 +0000[diff] [blame]3256 <li><tt>true</tt>: no comparison, always returns true</li>
Reid Spencerf3a70a62006-11-18 21:50:54 +0000[diff] [blame]3257</ol>
Reid Spencer93a49852006-12-06 07:08:07 +0000[diff] [blame]3258<p>In the preceding, <i>ordered</i> means that neither operand is a QNAN while
3259<i>unordered</i> means that either operand may be a QNAN.</p>
Reid Spencer350f8aa2007-01-04 05:19:58 +0000[diff] [blame]3260<p>The <tt>val1</tt> and <tt>val2</tt> arguments must be
3261<a href="#t_floating">floating point</a> typed. They must have identical
3262types.</p>
Reid Spencerb7f26282006-11-19 03:00:14 +0000[diff] [blame]3263<p>In the foregoing, <i>ordered</i> means that neither operand is a QNAN and
3264<i>unordered</i> means that either operand is a QNAN.</p>
Reid Spencerf3a70a62006-11-18 21:50:54 +0000[diff] [blame]3265<h5>Semantics:</h5>
3266<p>The '<tt>fcmp</tt>' compares <tt>var1</tt> and <tt>var2</tt> according to
3267the condition code given as <tt>cond</tt>. The comparison performed always
Reid Spencerc78f3372007-01-12 03:35:51 +0000[diff] [blame]3268yields a <a href="#t_primitive">i1</a> result, as follows:
Reid Spencerf3a70a62006-11-18 21:50:54 +0000[diff] [blame]3269<ol>
3270 <li><tt>false</tt>: always yields <tt>false</tt>, regardless of operands.</li>
Reid Spencerb7f26282006-11-19 03:00:14 +0000[diff] [blame]3271 <li><tt>oeq</tt>: yields <tt>true</tt> if both operands are not a QNAN and
Reid Spencerf3a70a62006-11-18 21:50:54 +0000[diff] [blame]3272 <tt>var1</tt> is equal to <tt>var2</tt>.</li>
Reid Spencerb7f26282006-11-19 03:00:14 +0000[diff] [blame]3273 <li><tt>ogt</tt>: yields <tt>true</tt> if both operands are not a QNAN and
Reid Spencerf3a70a62006-11-18 21:50:54 +0000[diff] [blame]3274 <tt>var1</tt> is greather than <tt>var2</tt>.</li>
Reid Spencerb7f26282006-11-19 03:00:14 +0000[diff] [blame]3275 <li><tt>oge</tt>: yields <tt>true</tt> if both operands are not a QNAN and
Reid Spencerf3a70a62006-11-18 21:50:54 +0000[diff] [blame]3276 <tt>var1</tt> is greater than or equal to <tt>var2</tt>.</li>
Reid Spencerb7f26282006-11-19 03:00:14 +0000[diff] [blame]3277 <li><tt>olt</tt>: yields <tt>true</tt> if both operands are not a QNAN and
Reid Spencerf3a70a62006-11-18 21:50:54 +0000[diff] [blame]3278 <tt>var1</tt> is less than <tt>var2</tt>.</li>
Reid Spencerb7f26282006-11-19 03:00:14 +0000[diff] [blame]3279 <li><tt>ole</tt>: yields <tt>true</tt> if both operands are not a QNAN and
Reid Spencerf3a70a62006-11-18 21:50:54 +0000[diff] [blame]3280 <tt>var1</tt> is less than or equal to <tt>var2</tt>.</li>
Reid Spencerb7f26282006-11-19 03:00:14 +0000[diff] [blame]3281 <li><tt>one</tt>: yields <tt>true</tt> if both operands are not a QNAN and
Reid Spencerf3a70a62006-11-18 21:50:54 +0000[diff] [blame]3282 <tt>var1</tt> is not equal to <tt>var2</tt>.</li>
Reid Spencerb7f26282006-11-19 03:00:14 +0000[diff] [blame]3283 <li><tt>ord</tt>: yields <tt>true</tt> if both operands are not a QNAN.</li>
3284 <li><tt>ueq</tt>: yields <tt>true</tt> if either operand is a QNAN or
Reid Spencerf3a70a62006-11-18 21:50:54 +0000[diff] [blame]3285 <tt>var1</tt> is equal to <tt>var2</tt>.</li>
Reid Spencerb7f26282006-11-19 03:00:14 +0000[diff] [blame]3286 <li><tt>ugt</tt>: yields <tt>true</tt> if either operand is a QNAN or
Reid Spencerf3a70a62006-11-18 21:50:54 +0000[diff] [blame]3287 <tt>var1</tt> is greater than <tt>var2</tt>.</li>
Reid Spencerb7f26282006-11-19 03:00:14 +0000[diff] [blame]3288 <li><tt>uge</tt>: yields <tt>true</tt> if either operand is a QNAN or
Reid Spencerf3a70a62006-11-18 21:50:54 +0000[diff] [blame]3289 <tt>var1</tt> is greater than or equal to <tt>var2</tt>.</li>
Reid Spencerb7f26282006-11-19 03:00:14 +0000[diff] [blame]3290 <li><tt>ult</tt>: yields <tt>true</tt> if either operand is a QNAN or
Reid Spencerf3a70a62006-11-18 21:50:54 +0000[diff] [blame]3291 <tt>var1</tt> is less than <tt>var2</tt>.</li>
Reid Spencerb7f26282006-11-19 03:00:14 +0000[diff] [blame]3292 <li><tt>ule</tt>: yields <tt>true</tt> if either operand is a QNAN or
Reid Spencerf3a70a62006-11-18 21:50:54 +0000[diff] [blame]3293 <tt>var1</tt> is less than or equal to <tt>var2</tt>.</li>
Reid Spencerb7f26282006-11-19 03:00:14 +0000[diff] [blame]3294 <li><tt>une</tt>: yields <tt>true</tt> if either operand is a QNAN or
Reid Spencerf3a70a62006-11-18 21:50:54 +0000[diff] [blame]3295 <tt>var1</tt> is not equal to <tt>var2</tt>.</li>
Reid Spencerb7f26282006-11-19 03:00:14 +0000[diff] [blame]3296 <li><tt>uno</tt>: yields <tt>true</tt> if either operand is a QNAN.</li>
Reid Spencerf3a70a62006-11-18 21:50:54 +0000[diff] [blame]3297 <li><tt>true</tt>: always yields <tt>true</tt>, regardless of operands.</li>
3298</ol>
Reid Spencerf3a70a62006-11-18 21:50:54 +0000[diff] [blame]3299
3300<h5>Example:</h5>
3301<pre> &lt;result&gt; = fcmp oeq float 4.0, 5.0 <i>; yields: result=false</i>
3302 &lt;result&gt; = icmp one float 4.0, 5.0 <i>; yields: result=true</i>
3303 &lt;result&gt; = icmp olt float 4.0, 5.0 <i>; yields: result=true</i>
3304 &lt;result&gt; = icmp ueq double 1.0, 2.0 <i>; yields: result=false</i>
3305</pre>
3306</div>
3307
Reid Spencer2fd21e62006-11-08 01:18:52 +0000[diff] [blame]3308<!-- _______________________________________________________________________ -->
3309<div class="doc_subsubsection"> <a name="i_phi">'<tt>phi</tt>'
3310Instruction</a> </div>
3311<div class="doc_text">
3312<h5>Syntax:</h5>
3313<pre> &lt;result&gt; = phi &lt;ty&gt; [ &lt;val0&gt;, &lt;label0&gt;], ...<br></pre>
3314<h5>Overview:</h5>
3315<p>The '<tt>phi</tt>' instruction is used to implement the &#966; node in
3316the SSA graph representing the function.</p>
3317<h5>Arguments:</h5>
3318<p>The type of the incoming values are specified with the first type
3319field. After this, the '<tt>phi</tt>' instruction takes a list of pairs
3320as arguments, with one pair for each predecessor basic block of the
3321current block. Only values of <a href="#t_firstclass">first class</a>
3322type may be used as the value arguments to the PHI node. Only labels
3323may be used as the label arguments.</p>
3324<p>There must be no non-phi instructions between the start of a basic
3325block and the PHI instructions: i.e. PHI instructions must be first in
3326a basic block.</p>
3327<h5>Semantics:</h5>
3328<p>At runtime, the '<tt>phi</tt>' instruction logically takes on the
3329value specified by the parameter, depending on which basic block we
3330came from in the last <a href="#terminators">terminator</a> instruction.</p>
3331<h5>Example:</h5>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]3332<pre>Loop: ; Infinite loop that counts from 0 on up...<br> %indvar = phi i32 [ 0, %LoopHeader ], [ %nextindvar, %Loop ]<br> %nextindvar = add i32 %indvar, 1<br> br label %Loop<br></pre>
Reid Spencer2fd21e62006-11-08 01:18:52 +0000[diff] [blame]3333</div>
3334
Chris Lattnercc37aae2004-03-12 05:50:16 +0000[diff] [blame]3335<!-- _______________________________________________________________________ -->
3336<div class="doc_subsubsection">
3337 <a name="i_select">'<tt>select</tt>' Instruction</a>
3338</div>
3339
3340<div class="doc_text">
3341
3342<h5>Syntax:</h5>
3343
3344<pre>
Reid Spencerc78f3372007-01-12 03:35:51 +0000[diff] [blame]3345 &lt;result&gt; = select i1 &lt;cond&gt;, &lt;ty&gt; &lt;val1&gt;, &lt;ty&gt; &lt;val2&gt; <i>; yields ty</i>
Chris Lattnercc37aae2004-03-12 05:50:16 +0000[diff] [blame]3346</pre>
3347
3348<h5>Overview:</h5>
3349
3350<p>
3351The '<tt>select</tt>' instruction is used to choose one value based on a
3352condition, without branching.
3353</p>
3354
3355
3356<h5>Arguments:</h5>
3357
3358<p>
3359The '<tt>select</tt>' instruction requires a boolean value indicating the condition, and two values of the same <a href="#t_firstclass">first class</a> type.
3360</p>
3361
3362<h5>Semantics:</h5>
3363
3364<p>
3365If the boolean condition evaluates to true, the instruction returns the first
John Criswellfc6b8952005-05-16 16:17:45 +0000[diff] [blame]3366value argument; otherwise, it returns the second value argument.
Chris Lattnercc37aae2004-03-12 05:50:16 +0000[diff] [blame]3367</p>
3368
3369<h5>Example:</h5>
3370
3371<pre>
Reid Spencerc78f3372007-01-12 03:35:51 +0000[diff] [blame]3372 %X = select i1 true, i8 17, i8 42 <i>; yields i8:17</i>
Chris Lattnercc37aae2004-03-12 05:50:16 +0000[diff] [blame]3373</pre>
3374</div>
3375
Robert Bocchino05ccd702006-01-15 20:48:27 +0000[diff] [blame]3376
3377<!-- _______________________________________________________________________ -->
3378<div class="doc_subsubsection">
Chris Lattner2bff5242005-05-06 05:47:36 +0000[diff] [blame]3379 <a name="i_call">'<tt>call</tt>' Instruction</a>
3380</div>
3381
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]3382<div class="doc_text">
Chris Lattner2bff5242005-05-06 05:47:36 +0000[diff] [blame]3383
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]3384<h5>Syntax:</h5>
Chris Lattner2bff5242005-05-06 05:47:36 +0000[diff] [blame]3385<pre>
Chris Lattnerbad10ee2005-05-06 22:57:40 +0000[diff] [blame]3386 &lt;result&gt; = [tail] call [<a href="#callingconv">cconv</a>] &lt;ty&gt;* &lt;fnptrval&gt;(&lt;param list&gt;)
Chris Lattner2bff5242005-05-06 05:47:36 +0000[diff] [blame]3387</pre>
3388
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]3389<h5>Overview:</h5>
Chris Lattner2bff5242005-05-06 05:47:36 +0000[diff] [blame]3390
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]3391<p>The '<tt>call</tt>' instruction represents a simple function call.</p>
Chris Lattner2bff5242005-05-06 05:47:36 +0000[diff] [blame]3392
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]3393<h5>Arguments:</h5>
Chris Lattner2bff5242005-05-06 05:47:36 +0000[diff] [blame]3394
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]3395<p>This instruction requires several arguments:</p>
Chris Lattner2bff5242005-05-06 05:47:36 +0000[diff] [blame]3396
Chris Lattner6536cfe2002-05-06 22:08:29 +0000[diff] [blame]3397<ol>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]3398 <li>
Chris Lattnerbad10ee2005-05-06 22:57:40 +0000[diff] [blame]3399 <p>The optional "tail" marker indicates whether the callee function accesses
3400 any allocas or varargs in the caller. If the "tail" marker is present, the
Chris Lattner2bff5242005-05-06 05:47:36 +0000[diff] [blame]3401 function call is eligible for tail call optimization. Note that calls may
3402 be marked "tail" even if they do not occur before a <a
3403 href="#i_ret"><tt>ret</tt></a> instruction.
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]3404 </li>
3405 <li>
Chris Lattnerbad10ee2005-05-06 22:57:40 +0000[diff] [blame]3406 <p>The optional "cconv" marker indicates which <a href="callingconv">calling
3407 convention</a> the call should use. If none is specified, the call defaults
3408 to using C calling conventions.
3409 </li>
3410 <li>
Chris Lattner2bff5242005-05-06 05:47:36 +0000[diff] [blame]3411 <p>'<tt>ty</tt>': shall be the signature of the pointer to function value
3412 being invoked. The argument types must match the types implied by this
John Criswellfc6b8952005-05-16 16:17:45 +0000[diff] [blame]3413 signature. This type can be omitted if the function is not varargs and
3414 if the function type does not return a pointer to a function.</p>
Chris Lattner2bff5242005-05-06 05:47:36 +0000[diff] [blame]3415 </li>
3416 <li>
3417 <p>'<tt>fnptrval</tt>': An LLVM value containing a pointer to a function to
3418 be invoked. In most cases, this is a direct function invocation, but
3419 indirect <tt>call</tt>s are just as possible, calling an arbitrary pointer
John Criswellfc6b8952005-05-16 16:17:45 +0000[diff] [blame]3420 to function value.</p>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]3421 </li>
3422 <li>
3423 <p>'<tt>function args</tt>': argument list whose types match the
Reid Spencera7e302a2005-05-01 22:22:57 +0000[diff] [blame]3424 function signature argument types. All arguments must be of
3425 <a href="#t_firstclass">first class</a> type. If the function signature
3426 indicates the function accepts a variable number of arguments, the extra
3427 arguments can be specified.</p>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]3428 </li>
Chris Lattner6536cfe2002-05-06 22:08:29 +0000[diff] [blame]3429</ol>
Chris Lattner2bff5242005-05-06 05:47:36 +0000[diff] [blame]3430
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]3431<h5>Semantics:</h5>
Chris Lattner2bff5242005-05-06 05:47:36 +0000[diff] [blame]3432
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]3433<p>The '<tt>call</tt>' instruction is used to cause control flow to
3434transfer to a specified function, with its incoming arguments bound to
3435the specified values. Upon a '<tt><a href="#i_ret">ret</a></tt>'
3436instruction in the called function, control flow continues with the
3437instruction after the function call, and the return value of the
3438function is bound to the result argument. This is a simpler case of
3439the <a href="#i_invoke">invoke</a> instruction.</p>
Chris Lattner2bff5242005-05-06 05:47:36 +0000[diff] [blame]3440
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]3441<h5>Example:</h5>
Chris Lattner2bff5242005-05-06 05:47:36 +0000[diff] [blame]3442
3443<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]3444 %retval = call i32 %test(i32 %argc)
3445 call i32(i8 *, ...) *%printf(i8 * %msg, i32 12, i8 42);
3446 %X = tail call i32 %foo()
3447 %Y = tail call <a href="#callingconv">fastcc</a> i32 %foo()
Chris Lattner2bff5242005-05-06 05:47:36 +0000[diff] [blame]3448</pre>
3449
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]3450</div>
Chris Lattnere19d7a72004-09-27 21:51:25 +0000[diff] [blame]3451
Chris Lattnerd9ad5b32003-05-08 04:57:36 +0000[diff] [blame]3452<!-- _______________________________________________________________________ -->
Chris Lattnere19d7a72004-09-27 21:51:25 +0000[diff] [blame]3453<div class="doc_subsubsection">
Chris Lattnerfb6977d2006-01-13 23:26:01 +0000[diff] [blame]3454 <a name="i_va_arg">'<tt>va_arg</tt>' Instruction</a>
Chris Lattnere19d7a72004-09-27 21:51:25 +0000[diff] [blame]3455</div>
3456
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]3457<div class="doc_text">
Chris Lattnere19d7a72004-09-27 21:51:25 +0000[diff] [blame]3458
Chris Lattner8d1a81d2003-10-18 05:51:36 +0000[diff] [blame]3459<h5>Syntax:</h5>
Chris Lattnere19d7a72004-09-27 21:51:25 +0000[diff] [blame]3460
3461<pre>
Andrew Lenharth8bf607a2005-06-18 18:28:17 +0000[diff] [blame]3462 &lt;resultval&gt; = va_arg &lt;va_list*&gt; &lt;arglist&gt;, &lt;argty&gt;
Chris Lattnere19d7a72004-09-27 21:51:25 +0000[diff] [blame]3463</pre>
3464
Chris Lattner8d1a81d2003-10-18 05:51:36 +0000[diff] [blame]3465<h5>Overview:</h5>
Chris Lattnere19d7a72004-09-27 21:51:25 +0000[diff] [blame]3466
Andrew Lenharth8bf607a2005-06-18 18:28:17 +0000[diff] [blame]3467<p>The '<tt>va_arg</tt>' instruction is used to access arguments passed through
Chris Lattnere19d7a72004-09-27 21:51:25 +0000[diff] [blame]3468the "variable argument" area of a function call. It is used to implement the
3469<tt>va_arg</tt> macro in C.</p>
3470
Chris Lattner8d1a81d2003-10-18 05:51:36 +0000[diff] [blame]3471<h5>Arguments:</h5>
Chris Lattnere19d7a72004-09-27 21:51:25 +0000[diff] [blame]3472
Andrew Lenharth8bf607a2005-06-18 18:28:17 +0000[diff] [blame]3473<p>This instruction takes a <tt>va_list*</tt> value and the type of
3474the argument. It returns a value of the specified argument type and
Jeff Cohen25d4f7e2005-11-11 02:15:27 +0000[diff] [blame]3475increments the <tt>va_list</tt> to point to the next argument. Again, the
Andrew Lenharth8bf607a2005-06-18 18:28:17 +0000[diff] [blame]3476actual type of <tt>va_list</tt> is target specific.</p>
Chris Lattnere19d7a72004-09-27 21:51:25 +0000[diff] [blame]3477
Chris Lattner8d1a81d2003-10-18 05:51:36 +0000[diff] [blame]3478<h5>Semantics:</h5>
Chris Lattnere19d7a72004-09-27 21:51:25 +0000[diff] [blame]3479
Andrew Lenharth8bf607a2005-06-18 18:28:17 +0000[diff] [blame]3480<p>The '<tt>va_arg</tt>' instruction loads an argument of the specified
3481type from the specified <tt>va_list</tt> and causes the
3482<tt>va_list</tt> to point to the next argument. For more information,
3483see the variable argument handling <a href="#int_varargs">Intrinsic
3484Functions</a>.</p>
Chris Lattnere19d7a72004-09-27 21:51:25 +0000[diff] [blame]3485
3486<p>It is legal for this instruction to be called in a function which does not
3487take a variable number of arguments, for example, the <tt>vfprintf</tt>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]3488function.</p>
Chris Lattnere19d7a72004-09-27 21:51:25 +0000[diff] [blame]3489
Andrew Lenharth8bf607a2005-06-18 18:28:17 +0000[diff] [blame]3490<p><tt>va_arg</tt> is an LLVM instruction instead of an <a
John Criswellfc6b8952005-05-16 16:17:45 +0000[diff] [blame]3491href="#intrinsics">intrinsic function</a> because it takes a type as an
Chris Lattnere19d7a72004-09-27 21:51:25 +0000[diff] [blame]3492argument.</p>
3493
Chris Lattner8d1a81d2003-10-18 05:51:36 +0000[diff] [blame]3494<h5>Example:</h5>
Chris Lattnere19d7a72004-09-27 21:51:25 +0000[diff] [blame]3495
3496<p>See the <a href="#int_varargs">variable argument processing</a> section.</p>
3497
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]3498</div>
Chris Lattner8ff75902004-01-06 05:31:32 +0000[diff] [blame]3499
Chris Lattnerd9ad5b32003-05-08 04:57:36 +0000[diff] [blame]3500<!-- *********************************************************************** -->
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]3501<div class="doc_section"> <a name="intrinsics">Intrinsic Functions</a> </div>
3502<!-- *********************************************************************** -->
Chris Lattner8ff75902004-01-06 05:31:32 +0000[diff] [blame]3503
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]3504<div class="doc_text">
Chris Lattner33aec9e2004-02-12 17:01:32 +0000[diff] [blame]3505
3506<p>LLVM supports the notion of an "intrinsic function". These functions have
John Criswellfc6b8952005-05-16 16:17:45 +0000[diff] [blame]3507well known names and semantics and are required to follow certain
Chris Lattner33aec9e2004-02-12 17:01:32 +0000[diff] [blame]3508restrictions. Overall, these instructions represent an extension mechanism for
3509the LLVM language that does not require changing all of the transformations in
3510LLVM to add to the language (or the bytecode reader/writer, the parser,
3511etc...).</p>
3512
John Criswellfc6b8952005-05-16 16:17:45 +0000[diff] [blame]3513<p>Intrinsic function names must all start with an "<tt>llvm.</tt>" prefix. This
3514prefix is reserved in LLVM for intrinsic names; thus, functions may not be named
Chris Lattner33aec9e2004-02-12 17:01:32 +0000[diff] [blame]3515this. Intrinsic functions must always be external functions: you cannot define
3516the body of intrinsic functions. Intrinsic functions may only be used in call
3517or invoke instructions: it is illegal to take the address of an intrinsic
3518function. Additionally, because intrinsic functions are part of the LLVM
3519language, it is required that they all be documented here if any are added.</p>
3520
3521
John Criswellfc6b8952005-05-16 16:17:45 +0000[diff] [blame]3522<p>To learn how to add an intrinsic function, please see the <a
Chris Lattner590cff32005-05-11 03:35:57 +0000[diff] [blame]3523href="ExtendingLLVM.html">Extending LLVM Guide</a>.
Chris Lattner33aec9e2004-02-12 17:01:32 +0000[diff] [blame]3524</p>
3525
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]3526</div>
Chris Lattner8ff75902004-01-06 05:31:32 +0000[diff] [blame]3527
Chris Lattnerd9ad5b32003-05-08 04:57:36 +0000[diff] [blame]3528<!-- ======================================================================= -->
Chris Lattner8ff75902004-01-06 05:31:32 +0000[diff] [blame]3529<div class="doc_subsection">
3530 <a name="int_varargs">Variable Argument Handling Intrinsics</a>
3531</div>
3532
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]3533<div class="doc_text">
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]3534
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]3535<p>Variable argument support is defined in LLVM with the <a
Chris Lattnerfb6977d2006-01-13 23:26:01 +0000[diff] [blame]3536 href="#i_va_arg"><tt>va_arg</tt></a> instruction and these three
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]3537intrinsic functions. These functions are related to the similarly
3538named macros defined in the <tt>&lt;stdarg.h&gt;</tt> header file.</p>
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]3539
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]3540<p>All of these functions operate on arguments that use a
3541target-specific value type "<tt>va_list</tt>". The LLVM assembly
3542language reference manual does not define what this type is, so all
3543transformations should be prepared to handle intrinsics with any type
3544used.</p>
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]3545
Chris Lattner374ab302006-05-15 17:26:46 +0000[diff] [blame]3546<p>This example shows how the <a href="#i_va_arg"><tt>va_arg</tt></a>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]3547instruction and the variable argument handling intrinsic functions are
3548used.</p>
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]3549
Chris Lattner33aec9e2004-02-12 17:01:32 +0000[diff] [blame]3550<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]3551define i32 %test(i32 %X, ...) {
Chris Lattner33aec9e2004-02-12 17:01:32 +0000[diff] [blame]3552 ; Initialize variable argument processing
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]3553 %ap = alloca i8 *
Chris Lattnerb75137d2007-01-08 07:55:15 +0000[diff] [blame]3554 %ap2 = bitcast i8** %ap to i8*
3555 call void %<a href="#i_va_start">llvm.va_start</a>(i8* %ap2)
Chris Lattner33aec9e2004-02-12 17:01:32 +0000[diff] [blame]3556
3557 ; Read a single integer argument
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]3558 %tmp = va_arg i8 ** %ap, i32
Chris Lattner33aec9e2004-02-12 17:01:32 +0000[diff] [blame]3559
3560 ; Demonstrate usage of llvm.va_copy and llvm.va_end
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]3561 %aq = alloca i8 *
Chris Lattnerb75137d2007-01-08 07:55:15 +0000[diff] [blame]3562 %aq2 = bitcast i8** %aq to i8*
3563 call void %<a href="#i_va_copy">llvm.va_copy</a>(i8 *%aq2, i8* %ap2)
3564 call void %<a href="#i_va_end">llvm.va_end</a>(i8* %aq2)
Chris Lattner33aec9e2004-02-12 17:01:32 +0000[diff] [blame]3565
3566 ; Stop processing of arguments.
Chris Lattnerb75137d2007-01-08 07:55:15 +0000[diff] [blame]3567 call void %<a href="#i_va_end">llvm.va_end</a>(i8* %ap2)
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]3568 ret i32 %tmp
Chris Lattner33aec9e2004-02-12 17:01:32 +0000[diff] [blame]3569}
3570</pre>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]3571</div>
Chris Lattner8ff75902004-01-06 05:31:32 +0000[diff] [blame]3572
Chris Lattnerd9ad5b32003-05-08 04:57:36 +0000[diff] [blame]3573<!-- _______________________________________________________________________ -->
Chris Lattner8ff75902004-01-06 05:31:32 +0000[diff] [blame]3574<div class="doc_subsubsection">
3575 <a name="i_va_start">'<tt>llvm.va_start</tt>' Intrinsic</a>
3576</div>
3577
3578
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]3579<div class="doc_text">
Chris Lattnerd9ad5b32003-05-08 04:57:36 +0000[diff] [blame]3580<h5>Syntax:</h5>
Chris Lattnerb75137d2007-01-08 07:55:15 +0000[diff] [blame]3581<pre> declare void %llvm.va_start(i8* &lt;arglist&gt;)<br></pre>
Chris Lattnerd9ad5b32003-05-08 04:57:36 +0000[diff] [blame]3582<h5>Overview:</h5>
Andrew Lenharth8bf607a2005-06-18 18:28:17 +0000[diff] [blame]3583<P>The '<tt>llvm.va_start</tt>' intrinsic initializes
3584<tt>*&lt;arglist&gt;</tt> for subsequent use by <tt><a
3585href="#i_va_arg">va_arg</a></tt>.</p>
3586
3587<h5>Arguments:</h5>
3588
3589<P>The argument is a pointer to a <tt>va_list</tt> element to initialize.</p>
3590
Chris Lattnerd9ad5b32003-05-08 04:57:36 +0000[diff] [blame]3591<h5>Semantics:</h5>
Andrew Lenharth8bf607a2005-06-18 18:28:17 +0000[diff] [blame]3592
3593<P>The '<tt>llvm.va_start</tt>' intrinsic works just like the <tt>va_start</tt>
3594macro available in C. In a target-dependent way, it initializes the
3595<tt>va_list</tt> element the argument points to, so that the next call to
3596<tt>va_arg</tt> will produce the first variable argument passed to the function.
3597Unlike the C <tt>va_start</tt> macro, this intrinsic does not need to know the
3598last argument of the function, the compiler can figure that out.</p>
3599
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]3600</div>
Chris Lattner8ff75902004-01-06 05:31:32 +0000[diff] [blame]3601
Chris Lattnerd9ad5b32003-05-08 04:57:36 +0000[diff] [blame]3602<!-- _______________________________________________________________________ -->
Chris Lattner8ff75902004-01-06 05:31:32 +0000[diff] [blame]3603<div class="doc_subsubsection">
3604 <a name="i_va_end">'<tt>llvm.va_end</tt>' Intrinsic</a>
3605</div>
3606
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]3607<div class="doc_text">
Chris Lattnerd9ad5b32003-05-08 04:57:36 +0000[diff] [blame]3608<h5>Syntax:</h5>
Chris Lattnerb75137d2007-01-08 07:55:15 +0000[diff] [blame]3609<pre> declare void %llvm.va_end(i8* &lt;arglist&gt;)<br></pre>
Chris Lattnerd9ad5b32003-05-08 04:57:36 +0000[diff] [blame]3610<h5>Overview:</h5>
Chris Lattnerb75137d2007-01-08 07:55:15 +0000[diff] [blame]3611
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]3612<p>The '<tt>llvm.va_end</tt>' intrinsic destroys <tt>&lt;arglist&gt;</tt>
3613which has been initialized previously with <tt><a href="#i_va_start">llvm.va_start</a></tt>
3614or <tt><a href="#i_va_copy">llvm.va_copy</a></tt>.</p>
Chris Lattnerb75137d2007-01-08 07:55:15 +0000[diff] [blame]3615
Chris Lattnerd9ad5b32003-05-08 04:57:36 +0000[diff] [blame]3616<h5>Arguments:</h5>
Chris Lattnerb75137d2007-01-08 07:55:15 +0000[diff] [blame]3617
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]3618<p>The argument is a <tt>va_list</tt> to destroy.</p>
Chris Lattnerb75137d2007-01-08 07:55:15 +0000[diff] [blame]3619
Chris Lattnerd9ad5b32003-05-08 04:57:36 +0000[diff] [blame]3620<h5>Semantics:</h5>
Chris Lattnerb75137d2007-01-08 07:55:15 +0000[diff] [blame]3621
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]3622<p>The '<tt>llvm.va_end</tt>' intrinsic works just like the <tt>va_end</tt>
Chris Lattner261efe92003-11-25 01:02:51 +0000[diff] [blame]3623macro available in C. In a target-dependent way, it destroys the <tt>va_list</tt>.
3624Calls to <a href="#i_va_start"><tt>llvm.va_start</tt></a> and <a
3625 href="#i_va_copy"><tt>llvm.va_copy</tt></a> must be matched exactly
3626with calls to <tt>llvm.va_end</tt>.</p>
Chris Lattnerb75137d2007-01-08 07:55:15 +0000[diff] [blame]3627
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]3628</div>
Chris Lattner8ff75902004-01-06 05:31:32 +0000[diff] [blame]3629
Chris Lattnerd9ad5b32003-05-08 04:57:36 +0000[diff] [blame]3630<!-- _______________________________________________________________________ -->
Chris Lattner8ff75902004-01-06 05:31:32 +0000[diff] [blame]3631<div class="doc_subsubsection">
3632 <a name="i_va_copy">'<tt>llvm.va_copy</tt>' Intrinsic</a>
3633</div>
3634
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]3635<div class="doc_text">
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]3636
Chris Lattnerd9ad5b32003-05-08 04:57:36 +0000[diff] [blame]3637<h5>Syntax:</h5>
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]3638
3639<pre>
Chris Lattnerb75137d2007-01-08 07:55:15 +0000[diff] [blame]3640 declare void %llvm.va_copy(i8* &lt;destarglist&gt;, i8* &lt;srcarglist&gt;)
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]3641</pre>
3642
Chris Lattnerd9ad5b32003-05-08 04:57:36 +0000[diff] [blame]3643<h5>Overview:</h5>
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]3644
Andrew Lenharth8bf607a2005-06-18 18:28:17 +0000[diff] [blame]3645<p>The '<tt>llvm.va_copy</tt>' intrinsic copies the current argument position from
3646the source argument list to the destination argument list.</p>
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]3647
Chris Lattnerd9ad5b32003-05-08 04:57:36 +0000[diff] [blame]3648<h5>Arguments:</h5>
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]3649
Andrew Lenharth8bf607a2005-06-18 18:28:17 +0000[diff] [blame]3650<p>The first argument is a pointer to a <tt>va_list</tt> element to initialize.
Andrew Lenharthd0a4c622005-06-22 20:38:11 +0000[diff] [blame]3651The second argument is a pointer to a <tt>va_list</tt> element to copy from.</p>
Andrew Lenharth8bf607a2005-06-18 18:28:17 +0000[diff] [blame]3652
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]3653
Chris Lattnerd9ad5b32003-05-08 04:57:36 +0000[diff] [blame]3654<h5>Semantics:</h5>
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]3655
Andrew Lenharth8bf607a2005-06-18 18:28:17 +0000[diff] [blame]3656<p>The '<tt>llvm.va_copy</tt>' intrinsic works just like the <tt>va_copy</tt> macro
3657available in C. In a target-dependent way, it copies the source
3658<tt>va_list</tt> element into the destination list. This intrinsic is necessary
3659because the <tt><a href="i_va_begin">llvm.va_begin</a></tt> intrinsic may be
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]3660arbitrarily complex and require memory allocation, for example.</p>
3661
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]3662</div>
Chris Lattner8ff75902004-01-06 05:31:32 +0000[diff] [blame]3663
Chris Lattner33aec9e2004-02-12 17:01:32 +0000[diff] [blame]3664<!-- ======================================================================= -->
3665<div class="doc_subsection">
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]3666 <a name="int_gc">Accurate Garbage Collection Intrinsics</a>
3667</div>
3668
3669<div class="doc_text">
3670
3671<p>
3672LLVM support for <a href="GarbageCollection.html">Accurate Garbage
3673Collection</a> requires the implementation and generation of these intrinsics.
3674These intrinsics allow identification of <a href="#i_gcroot">GC roots on the
3675stack</a>, as well as garbage collector implementations that require <a
3676href="#i_gcread">read</a> and <a href="#i_gcwrite">write</a> barriers.
3677Front-ends for type-safe garbage collected languages should generate these
3678intrinsics to make use of the LLVM garbage collectors. For more details, see <a
3679href="GarbageCollection.html">Accurate Garbage Collection with LLVM</a>.
3680</p>
3681</div>
3682
3683<!-- _______________________________________________________________________ -->
3684<div class="doc_subsubsection">
3685 <a name="i_gcroot">'<tt>llvm.gcroot</tt>' Intrinsic</a>
3686</div>
3687
3688<div class="doc_text">
3689
3690<h5>Syntax:</h5>
3691
3692<pre>
Reid Spencera8d451e2005-04-26 20:50:44 +0000[diff] [blame]3693 declare void %llvm.gcroot(&lt;ty&gt;** %ptrloc, &lt;ty2&gt;* %metadata)
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]3694</pre>
3695
3696<h5>Overview:</h5>
3697
John Criswell9e2485c2004-12-10 15:51:16 +0000[diff] [blame]3698<p>The '<tt>llvm.gcroot</tt>' intrinsic declares the existence of a GC root to
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]3699the code generator, and allows some metadata to be associated with it.</p>
3700
3701<h5>Arguments:</h5>
3702
3703<p>The first argument specifies the address of a stack object that contains the
3704root pointer. The second pointer (which must be either a constant or a global
3705value address) contains the meta-data to be associated with the root.</p>
3706
3707<h5>Semantics:</h5>
3708
3709<p>At runtime, a call to this intrinsics stores a null pointer into the "ptrloc"
3710location. At compile-time, the code generator generates information to allow
3711the runtime to find the pointer at GC safe points.
3712</p>
3713
3714</div>
3715
3716
3717<!-- _______________________________________________________________________ -->
3718<div class="doc_subsubsection">
3719 <a name="i_gcread">'<tt>llvm.gcread</tt>' Intrinsic</a>
3720</div>
3721
3722<div class="doc_text">
3723
3724<h5>Syntax:</h5>
3725
3726<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]3727 declare i8 * %llvm.gcread(i8 * %ObjPtr, i8 ** %Ptr)
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]3728</pre>
3729
3730<h5>Overview:</h5>
3731
3732<p>The '<tt>llvm.gcread</tt>' intrinsic identifies reads of references from heap
3733locations, allowing garbage collector implementations that require read
3734barriers.</p>
3735
3736<h5>Arguments:</h5>
3737
Chris Lattner80626e92006-03-14 20:02:51 +0000[diff] [blame]3738<p>The second argument is the address to read from, which should be an address
3739allocated from the garbage collector. The first object is a pointer to the
3740start of the referenced object, if needed by the language runtime (otherwise
3741null).</p>
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]3742
3743<h5>Semantics:</h5>
3744
3745<p>The '<tt>llvm.gcread</tt>' intrinsic has the same semantics as a load
3746instruction, but may be replaced with substantially more complex code by the
3747garbage collector runtime, as needed.</p>
3748
3749</div>
3750
3751
3752<!-- _______________________________________________________________________ -->
3753<div class="doc_subsubsection">
3754 <a name="i_gcwrite">'<tt>llvm.gcwrite</tt>' Intrinsic</a>
3755</div>
3756
3757<div class="doc_text">
3758
3759<h5>Syntax:</h5>
3760
3761<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]3762 declare void %llvm.gcwrite(i8 * %P1, i8 * %Obj, i8 ** %P2)
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]3763</pre>
3764
3765<h5>Overview:</h5>
3766
3767<p>The '<tt>llvm.gcwrite</tt>' intrinsic identifies writes of references to heap
3768locations, allowing garbage collector implementations that require write
3769barriers (such as generational or reference counting collectors).</p>
3770
3771<h5>Arguments:</h5>
3772
Chris Lattner80626e92006-03-14 20:02:51 +0000[diff] [blame]3773<p>The first argument is the reference to store, the second is the start of the
3774object to store it to, and the third is the address of the field of Obj to
3775store to. If the runtime does not require a pointer to the object, Obj may be
3776null.</p>
Chris Lattnerd7923912004-05-23 21:06:01 +0000[diff] [blame]3777
3778<h5>Semantics:</h5>
3779
3780<p>The '<tt>llvm.gcwrite</tt>' intrinsic has the same semantics as a store
3781instruction, but may be replaced with substantially more complex code by the
3782garbage collector runtime, as needed.</p>
3783
3784</div>
3785
3786
3787
3788<!-- ======================================================================= -->
3789<div class="doc_subsection">
Chris Lattner10610642004-02-14 04:08:35 +0000[diff] [blame]3790 <a name="int_codegen">Code Generator Intrinsics</a>
3791</div>
3792
3793<div class="doc_text">
3794<p>
3795These intrinsics are provided by LLVM to expose special features that may only
3796be implemented with code generator support.
3797</p>
3798
3799</div>
3800
3801<!-- _______________________________________________________________________ -->
3802<div class="doc_subsubsection">
3803 <a name="i_returnaddress">'<tt>llvm.returnaddress</tt>' Intrinsic</a>
3804</div>
3805
3806<div class="doc_text">
3807
3808<h5>Syntax:</h5>
3809<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]3810 declare i8 *%llvm.returnaddress(i32 &lt;level&gt;)
Chris Lattner10610642004-02-14 04:08:35 +0000[diff] [blame]3811</pre>
3812
3813<h5>Overview:</h5>
3814
3815<p>
Chris Lattner32b5d712006-10-15 20:05:59 +0000[diff] [blame]3816The '<tt>llvm.returnaddress</tt>' intrinsic attempts to compute a
3817target-specific value indicating the return address of the current function
3818or one of its callers.
Chris Lattner10610642004-02-14 04:08:35 +0000[diff] [blame]3819</p>
3820
3821<h5>Arguments:</h5>
3822
3823<p>
3824The argument to this intrinsic indicates which function to return the address
3825for. Zero indicates the calling function, one indicates its caller, etc. The
3826argument is <b>required</b> to be a constant integer value.
3827</p>
3828
3829<h5>Semantics:</h5>
3830
3831<p>
3832The '<tt>llvm.returnaddress</tt>' intrinsic either returns a pointer indicating
3833the return address of the specified call frame, or zero if it cannot be
3834identified. The value returned by this intrinsic is likely to be incorrect or 0
3835for arguments other than zero, so it should only be used for debugging purposes.
3836</p>
3837
3838<p>
3839Note that calling this intrinsic does not prevent function inlining or other
Chris Lattnerb40bb382005-03-07 20:30:51 +0000[diff] [blame]3840aggressive transformations, so the value returned may not be that of the obvious
Chris Lattner10610642004-02-14 04:08:35 +0000[diff] [blame]3841source-language caller.
3842</p>
3843</div>
3844
3845
3846<!-- _______________________________________________________________________ -->
3847<div class="doc_subsubsection">
3848 <a name="i_frameaddress">'<tt>llvm.frameaddress</tt>' Intrinsic</a>
3849</div>
3850
3851<div class="doc_text">
3852
3853<h5>Syntax:</h5>
3854<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]3855 declare i8 *%llvm.frameaddress(i32 &lt;level&gt;)
Chris Lattner10610642004-02-14 04:08:35 +0000[diff] [blame]3856</pre>
3857
3858<h5>Overview:</h5>
3859
3860<p>
Chris Lattner32b5d712006-10-15 20:05:59 +0000[diff] [blame]3861The '<tt>llvm.frameaddress</tt>' intrinsic attempts to return the
3862target-specific frame pointer value for the specified stack frame.
Chris Lattner10610642004-02-14 04:08:35 +0000[diff] [blame]3863</p>
3864
3865<h5>Arguments:</h5>
3866
3867<p>
3868The argument to this intrinsic indicates which function to return the frame
3869pointer for. Zero indicates the calling function, one indicates its caller,
3870etc. The argument is <b>required</b> to be a constant integer value.
3871</p>
3872
3873<h5>Semantics:</h5>
3874
3875<p>
3876The '<tt>llvm.frameaddress</tt>' intrinsic either returns a pointer indicating
3877the frame address of the specified call frame, or zero if it cannot be
3878identified. The value returned by this intrinsic is likely to be incorrect or 0
3879for arguments other than zero, so it should only be used for debugging purposes.
3880</p>
3881
3882<p>
3883Note that calling this intrinsic does not prevent function inlining or other
Chris Lattnerb40bb382005-03-07 20:30:51 +0000[diff] [blame]3884aggressive transformations, so the value returned may not be that of the obvious
Chris Lattner10610642004-02-14 04:08:35 +0000[diff] [blame]3885source-language caller.
3886</p>
3887</div>
3888
Chris Lattner9a9d7ac2005-02-28 19:24:19 +0000[diff] [blame]3889<!-- _______________________________________________________________________ -->
3890<div class="doc_subsubsection">
Chris Lattner57e1f392006-01-13 02:03:13 +0000[diff] [blame]3891 <a name="i_stacksave">'<tt>llvm.stacksave</tt>' Intrinsic</a>
3892</div>
3893
3894<div class="doc_text">
3895
3896<h5>Syntax:</h5>
3897<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]3898 declare i8 *%llvm.stacksave()
Chris Lattner57e1f392006-01-13 02:03:13 +0000[diff] [blame]3899</pre>
3900
3901<h5>Overview:</h5>
3902
3903<p>
3904The '<tt>llvm.stacksave</tt>' intrinsic is used to remember the current state of
3905the function stack, for use with <a href="#i_stackrestore">
3906<tt>llvm.stackrestore</tt></a>. This is useful for implementing language
3907features like scoped automatic variable sized arrays in C99.
3908</p>
3909
3910<h5>Semantics:</h5>
3911
3912<p>
3913This intrinsic returns a opaque pointer value that can be passed to <a
3914href="#i_stackrestore"><tt>llvm.stackrestore</tt></a>. When an
3915<tt>llvm.stackrestore</tt> intrinsic is executed with a value saved from
3916<tt>llvm.stacksave</tt>, it effectively restores the state of the stack to the
3917state it was in when the <tt>llvm.stacksave</tt> intrinsic executed. In
3918practice, this pops any <a href="#i_alloca">alloca</a> blocks from the stack
3919that were allocated after the <tt>llvm.stacksave</tt> was executed.
3920</p>
3921
3922</div>
3923
3924<!-- _______________________________________________________________________ -->
3925<div class="doc_subsubsection">
3926 <a name="i_stackrestore">'<tt>llvm.stackrestore</tt>' Intrinsic</a>
3927</div>
3928
3929<div class="doc_text">
3930
3931<h5>Syntax:</h5>
3932<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]3933 declare void %llvm.stackrestore(i8 * %ptr)
Chris Lattner57e1f392006-01-13 02:03:13 +0000[diff] [blame]3934</pre>
3935
3936<h5>Overview:</h5>
3937
3938<p>
3939The '<tt>llvm.stackrestore</tt>' intrinsic is used to restore the state of
3940the function stack to the state it was in when the corresponding <a
3941href="#llvm.stacksave"><tt>llvm.stacksave</tt></a> intrinsic executed. This is
3942useful for implementing language features like scoped automatic variable sized
3943arrays in C99.
3944</p>
3945
3946<h5>Semantics:</h5>
3947
3948<p>
3949See the description for <a href="#i_stacksave"><tt>llvm.stacksave</tt></a>.
3950</p>
3951
3952</div>
3953
3954
3955<!-- _______________________________________________________________________ -->
3956<div class="doc_subsubsection">
Chris Lattner9a9d7ac2005-02-28 19:24:19 +0000[diff] [blame]3957 <a name="i_prefetch">'<tt>llvm.prefetch</tt>' Intrinsic</a>
3958</div>
3959
3960<div class="doc_text">
3961
3962<h5>Syntax:</h5>
3963<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]3964 declare void %llvm.prefetch(i8 * &lt;address&gt;,
3965 i32 &lt;rw&gt;, i32 &lt;locality&gt;)
Chris Lattner9a9d7ac2005-02-28 19:24:19 +0000[diff] [blame]3966</pre>
3967
3968<h5>Overview:</h5>
3969
3970
3971<p>
3972The '<tt>llvm.prefetch</tt>' intrinsic is a hint to the code generator to insert
John Criswellfc6b8952005-05-16 16:17:45 +0000[diff] [blame]3973a prefetch instruction if supported; otherwise, it is a noop. Prefetches have
3974no
3975effect on the behavior of the program but can change its performance
Chris Lattner2a615362005-02-28 19:47:14 +0000[diff] [blame]3976characteristics.
Chris Lattner9a9d7ac2005-02-28 19:24:19 +0000[diff] [blame]3977</p>
3978
3979<h5>Arguments:</h5>
3980
3981<p>
3982<tt>address</tt> is the address to be prefetched, <tt>rw</tt> is the specifier
3983determining if the fetch should be for a read (0) or write (1), and
3984<tt>locality</tt> is a temporal locality specifier ranging from (0) - no
Chris Lattneraeffb4a2005-03-07 20:31:38 +0000[diff] [blame]3985locality, to (3) - extremely local keep in cache. The <tt>rw</tt> and
Chris Lattner9a9d7ac2005-02-28 19:24:19 +0000[diff] [blame]3986<tt>locality</tt> arguments must be constant integers.
3987</p>
3988
3989<h5>Semantics:</h5>
3990
3991<p>
3992This intrinsic does not modify the behavior of the program. In particular,
3993prefetches cannot trap and do not produce a value. On targets that support this
3994intrinsic, the prefetch can provide hints to the processor cache for better
3995performance.
3996</p>
3997
3998</div>
3999
Andrew Lenharth7f4ec3b2005-03-28 20:05:49 +0000[diff] [blame]4000<!-- _______________________________________________________________________ -->
4001<div class="doc_subsubsection">
4002 <a name="i_pcmarker">'<tt>llvm.pcmarker</tt>' Intrinsic</a>
4003</div>
4004
4005<div class="doc_text">
4006
4007<h5>Syntax:</h5>
4008<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]4009 declare void %llvm.pcmarker( i32 &lt;id&gt; )
Andrew Lenharth7f4ec3b2005-03-28 20:05:49 +0000[diff] [blame]4010</pre>
4011
4012<h5>Overview:</h5>
4013
4014
4015<p>
John Criswellfc6b8952005-05-16 16:17:45 +0000[diff] [blame]4016The '<tt>llvm.pcmarker</tt>' intrinsic is a method to export a Program Counter
4017(PC) in a region of
Andrew Lenharth7f4ec3b2005-03-28 20:05:49 +0000[diff] [blame]4018code to simulators and other tools. The method is target specific, but it is
4019expected that the marker will use exported symbols to transmit the PC of the marker.
Jeff Cohen25d4f7e2005-11-11 02:15:27 +0000[diff] [blame]4020The marker makes no guarantees that it will remain with any specific instruction
Chris Lattnerd07c3f42005-11-15 06:07:55 +0000[diff] [blame]4021after optimizations. It is possible that the presence of a marker will inhibit
Chris Lattnerb3e7afd2006-03-24 07:16:10 +0000[diff] [blame]4022optimizations. The intended use is to be inserted after optimizations to allow
John Criswellfc6b8952005-05-16 16:17:45 +0000[diff] [blame]4023correlations of simulation runs.
Andrew Lenharth7f4ec3b2005-03-28 20:05:49 +0000[diff] [blame]4024</p>
4025
4026<h5>Arguments:</h5>
4027
4028<p>
4029<tt>id</tt> is a numerical id identifying the marker.
4030</p>
4031
4032<h5>Semantics:</h5>
4033
4034<p>
4035This intrinsic does not modify the behavior of the program. Backends that do not
4036support this intrinisic may ignore it.
4037</p>
4038
4039</div>
4040
Andrew Lenharth51b8d542005-11-11 16:47:30 +0000[diff] [blame]4041<!-- _______________________________________________________________________ -->
4042<div class="doc_subsubsection">
4043 <a name="i_readcyclecounter">'<tt>llvm.readcyclecounter</tt>' Intrinsic</a>
4044</div>
4045
4046<div class="doc_text">
4047
4048<h5>Syntax:</h5>
4049<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]4050 declare i64 %llvm.readcyclecounter( )
Andrew Lenharth51b8d542005-11-11 16:47:30 +0000[diff] [blame]4051</pre>
4052
4053<h5>Overview:</h5>
4054
4055
4056<p>
4057The '<tt>llvm.readcyclecounter</tt>' intrinsic provides access to the cycle
4058counter register (or similar low latency, high accuracy clocks) on those targets
4059that support it. On X86, it should map to RDTSC. On Alpha, it should map to RPCC.
4060As the backing counters overflow quickly (on the order of 9 seconds on alpha), this
4061should only be used for small timings.
4062</p>
4063
4064<h5>Semantics:</h5>
4065
4066<p>
4067When directly supported, reading the cycle counter should not modify any memory.
4068Implementations are allowed to either return a application specific value or a
4069system wide value. On backends without support, this is lowered to a constant 0.
4070</p>
4071
4072</div>
4073
Chris Lattner10610642004-02-14 04:08:35 +0000[diff] [blame]4074<!-- ======================================================================= -->
4075<div class="doc_subsection">
Chris Lattner33aec9e2004-02-12 17:01:32 +0000[diff] [blame]4076 <a name="int_libc">Standard C Library Intrinsics</a>
4077</div>
4078
4079<div class="doc_text">
4080<p>
Chris Lattner10610642004-02-14 04:08:35 +0000[diff] [blame]4081LLVM provides intrinsics for a few important standard C library functions.
4082These intrinsics allow source-language front-ends to pass information about the
4083alignment of the pointer arguments to the code generator, providing opportunity
4084for more efficient code generation.
Chris Lattner33aec9e2004-02-12 17:01:32 +0000[diff] [blame]4085</p>
4086
4087</div>
4088
4089<!-- _______________________________________________________________________ -->
4090<div class="doc_subsubsection">
4091 <a name="i_memcpy">'<tt>llvm.memcpy</tt>' Intrinsic</a>
4092</div>
4093
4094<div class="doc_text">
4095
4096<h5>Syntax:</h5>
4097<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]4098 declare void %llvm.memcpy.i32(i8 * &lt;dest&gt;, i8 * &lt;src&gt;,
4099 i32 &lt;len&gt;, i32 &lt;align&gt;)
4100 declare void %llvm.memcpy.i64(i8 * &lt;dest&gt;, i8 * &lt;src&gt;,
4101 i64 &lt;len&gt;, i32 &lt;align&gt;)
Chris Lattner33aec9e2004-02-12 17:01:32 +0000[diff] [blame]4102</pre>
4103
4104<h5>Overview:</h5>
4105
4106<p>
Chris Lattner5b310c32006-03-03 00:07:20 +0000[diff] [blame]4107The '<tt>llvm.memcpy.*</tt>' intrinsics copy a block of memory from the source
Chris Lattner33aec9e2004-02-12 17:01:32 +0000[diff] [blame]4108location to the destination location.
4109</p>
4110
4111<p>
Chris Lattner5b310c32006-03-03 00:07:20 +0000[diff] [blame]4112Note that, unlike the standard libc function, the <tt>llvm.memcpy.*</tt>
4113intrinsics do not return a value, and takes an extra alignment argument.
Chris Lattner33aec9e2004-02-12 17:01:32 +0000[diff] [blame]4114</p>
4115
4116<h5>Arguments:</h5>
4117
4118<p>
4119The first argument is a pointer to the destination, the second is a pointer to
Chris Lattner5b310c32006-03-03 00:07:20 +0000[diff] [blame]4120the source. The third argument is an integer argument
Chris Lattner33aec9e2004-02-12 17:01:32 +0000[diff] [blame]4121specifying the number of bytes to copy, and the fourth argument is the alignment
4122of the source and destination locations.
4123</p>
4124
Chris Lattner3301ced2004-02-12 21:18:15 +0000[diff] [blame]4125<p>
4126If the call to this intrinisic has an alignment value that is not 0 or 1, then
Chris Lattnerf0afc2c2006-03-04 00:02:10 +0000[diff] [blame]4127the caller guarantees that both the source and destination pointers are aligned
4128to that boundary.
Chris Lattner3301ced2004-02-12 21:18:15 +0000[diff] [blame]4129</p>
4130
Chris Lattner33aec9e2004-02-12 17:01:32 +0000[diff] [blame]4131<h5>Semantics:</h5>
4132
4133<p>
Chris Lattner5b310c32006-03-03 00:07:20 +0000[diff] [blame]4134The '<tt>llvm.memcpy.*</tt>' intrinsics copy a block of memory from the source
Chris Lattner33aec9e2004-02-12 17:01:32 +0000[diff] [blame]4135location to the destination location, which are not allowed to overlap. It
4136copies "len" bytes of memory over. If the argument is known to be aligned to
4137some boundary, this can be specified as the fourth argument, otherwise it should
4138be set to 0 or 1.
4139</p>
4140</div>
4141
4142
Chris Lattner0eb51b42004-02-12 18:10:10 +0000[diff] [blame]4143<!-- _______________________________________________________________________ -->
4144<div class="doc_subsubsection">
4145 <a name="i_memmove">'<tt>llvm.memmove</tt>' Intrinsic</a>
4146</div>
4147
4148<div class="doc_text">
4149
4150<h5>Syntax:</h5>
4151<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]4152 declare void %llvm.memmove.i32(i8 * &lt;dest&gt;, i8 * &lt;src&gt;,
4153 i32 &lt;len&gt;, i32 &lt;align&gt;)
4154 declare void %llvm.memmove.i64(i8 * &lt;dest&gt;, i8 * &lt;src&gt;,
4155 i64 &lt;len&gt;, i32 &lt;align&gt;)
Chris Lattner0eb51b42004-02-12 18:10:10 +0000[diff] [blame]4156</pre>
4157
4158<h5>Overview:</h5>
4159
4160<p>
Chris Lattner5b310c32006-03-03 00:07:20 +0000[diff] [blame]4161The '<tt>llvm.memmove.*</tt>' intrinsics move a block of memory from the source
4162location to the destination location. It is similar to the
4163'<tt>llvm.memcmp</tt>' intrinsic but allows the two memory locations to overlap.
Chris Lattner0eb51b42004-02-12 18:10:10 +0000[diff] [blame]4164</p>
4165
4166<p>
Chris Lattner5b310c32006-03-03 00:07:20 +0000[diff] [blame]4167Note that, unlike the standard libc function, the <tt>llvm.memmove.*</tt>
4168intrinsics do not return a value, and takes an extra alignment argument.
Chris Lattner0eb51b42004-02-12 18:10:10 +0000[diff] [blame]4169</p>
4170
4171<h5>Arguments:</h5>
4172
4173<p>
4174The first argument is a pointer to the destination, the second is a pointer to
Chris Lattner5b310c32006-03-03 00:07:20 +0000[diff] [blame]4175the source. The third argument is an integer argument
Chris Lattner0eb51b42004-02-12 18:10:10 +0000[diff] [blame]4176specifying the number of bytes to copy, and the fourth argument is the alignment
4177of the source and destination locations.
4178</p>
4179
Chris Lattner3301ced2004-02-12 21:18:15 +0000[diff] [blame]4180<p>
4181If the call to this intrinisic has an alignment value that is not 0 or 1, then
Chris Lattnerf0afc2c2006-03-04 00:02:10 +0000[diff] [blame]4182the caller guarantees that the source and destination pointers are aligned to
4183that boundary.
Chris Lattner3301ced2004-02-12 21:18:15 +0000[diff] [blame]4184</p>
4185
Chris Lattner0eb51b42004-02-12 18:10:10 +0000[diff] [blame]4186<h5>Semantics:</h5>
4187
4188<p>
Chris Lattner5b310c32006-03-03 00:07:20 +0000[diff] [blame]4189The '<tt>llvm.memmove.*</tt>' intrinsics copy a block of memory from the source
Chris Lattner0eb51b42004-02-12 18:10:10 +0000[diff] [blame]4190location to the destination location, which may overlap. It
4191copies "len" bytes of memory over. If the argument is known to be aligned to
4192some boundary, this can be specified as the fourth argument, otherwise it should
4193be set to 0 or 1.
4194</p>
4195</div>
4196
Chris Lattner8ff75902004-01-06 05:31:32 +0000[diff] [blame]4197
Chris Lattner10610642004-02-14 04:08:35 +0000[diff] [blame]4198<!-- _______________________________________________________________________ -->
4199<div class="doc_subsubsection">
Chris Lattner5b310c32006-03-03 00:07:20 +0000[diff] [blame]4200 <a name="i_memset">'<tt>llvm.memset.*</tt>' Intrinsics</a>
Chris Lattner10610642004-02-14 04:08:35 +0000[diff] [blame]4201</div>
4202
4203<div class="doc_text">
4204
4205<h5>Syntax:</h5>
4206<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]4207 declare void %llvm.memset.i32(i8 * &lt;dest&gt;, i8 &lt;val&gt;,
4208 i32 &lt;len&gt;, i32 &lt;align&gt;)
4209 declare void %llvm.memset.i64(i8 * &lt;dest&gt;, i8 &lt;val&gt;,
4210 i64 &lt;len&gt;, i32 &lt;align&gt;)
Chris Lattner10610642004-02-14 04:08:35 +0000[diff] [blame]4211</pre>
4212
4213<h5>Overview:</h5>
4214
4215<p>
Chris Lattner5b310c32006-03-03 00:07:20 +0000[diff] [blame]4216The '<tt>llvm.memset.*</tt>' intrinsics fill a block of memory with a particular
Chris Lattner10610642004-02-14 04:08:35 +0000[diff] [blame]4217byte value.
4218</p>
4219
4220<p>
4221Note that, unlike the standard libc function, the <tt>llvm.memset</tt> intrinsic
4222does not return a value, and takes an extra alignment argument.
4223</p>
4224
4225<h5>Arguments:</h5>
4226
4227<p>
4228The first argument is a pointer to the destination to fill, the second is the
Chris Lattner5b310c32006-03-03 00:07:20 +0000[diff] [blame]4229byte value to fill it with, the third argument is an integer
Chris Lattner10610642004-02-14 04:08:35 +0000[diff] [blame]4230argument specifying the number of bytes to fill, and the fourth argument is the
4231known alignment of destination location.
4232</p>
4233
4234<p>
4235If the call to this intrinisic has an alignment value that is not 0 or 1, then
Chris Lattnerf0afc2c2006-03-04 00:02:10 +0000[diff] [blame]4236the caller guarantees that the destination pointer is aligned to that boundary.
Chris Lattner10610642004-02-14 04:08:35 +0000[diff] [blame]4237</p>
4238
4239<h5>Semantics:</h5>
4240
4241<p>
Chris Lattner5b310c32006-03-03 00:07:20 +0000[diff] [blame]4242The '<tt>llvm.memset.*</tt>' intrinsics fill "len" bytes of memory starting at
4243the
Chris Lattner10610642004-02-14 04:08:35 +0000[diff] [blame]4244destination location. If the argument is known to be aligned to some boundary,
4245this can be specified as the fourth argument, otherwise it should be set to 0 or
42461.
4247</p>
4248</div>
4249
4250
Chris Lattner32006282004-06-11 02:28:03 +0000[diff] [blame]4251<!-- _______________________________________________________________________ -->
4252<div class="doc_subsubsection">
Chris Lattnerec6cb612006-01-16 22:38:59 +0000[diff] [blame]4253 <a name="i_sqrt">'<tt>llvm.sqrt.*</tt>' Intrinsic</a>
Chris Lattnera4d74142005-07-21 01:29:16 +0000[diff] [blame]4254</div>
4255
4256<div class="doc_text">
4257
4258<h5>Syntax:</h5>
4259<pre>
Chris Lattnerf4d252d2006-09-08 06:34:02 +0000[diff] [blame]4260 declare float %llvm.sqrt.f32(float %Val)
4261 declare double %llvm.sqrt.f64(double %Val)
Chris Lattnera4d74142005-07-21 01:29:16 +0000[diff] [blame]4262</pre>
4263
4264<h5>Overview:</h5>
4265
4266<p>
Reid Spencer0b118202006-01-16 21:12:35 +0000[diff] [blame]4267The '<tt>llvm.sqrt</tt>' intrinsics return the sqrt of the specified operand,
Chris Lattnera4d74142005-07-21 01:29:16 +0000[diff] [blame]4268returning the same value as the libm '<tt>sqrt</tt>' function would. Unlike
4269<tt>sqrt</tt> in libm, however, <tt>llvm.sqrt</tt> has undefined behavior for
4270negative numbers (which allows for better optimization).
4271</p>
4272
4273<h5>Arguments:</h5>
4274
4275<p>
4276The argument and return value are floating point numbers of the same type.
4277</p>
4278
4279<h5>Semantics:</h5>
4280
4281<p>
4282This function returns the sqrt of the specified operand if it is a positive
4283floating point number.
4284</p>
4285</div>
4286
Chris Lattnerf4d252d2006-09-08 06:34:02 +0000[diff] [blame]4287<!-- _______________________________________________________________________ -->
4288<div class="doc_subsubsection">
4289 <a name="i_powi">'<tt>llvm.powi.*</tt>' Intrinsic</a>
4290</div>
4291
4292<div class="doc_text">
4293
4294<h5>Syntax:</h5>
4295<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]4296 declare float %llvm.powi.f32(float %Val, i32 %power)
4297 declare double %llvm.powi.f64(double %Val, i32 %power)
Chris Lattnerf4d252d2006-09-08 06:34:02 +0000[diff] [blame]4298</pre>
4299
4300<h5>Overview:</h5>
4301
4302<p>
4303The '<tt>llvm.powi.*</tt>' intrinsics return the first operand raised to the
4304specified (positive or negative) power. The order of evaluation of
4305multiplications is not defined.
4306</p>
4307
4308<h5>Arguments:</h5>
4309
4310<p>
4311The second argument is an integer power, and the first is a value to raise to
4312that power.
4313</p>
4314
4315<h5>Semantics:</h5>
4316
4317<p>
4318This function returns the first value raised to the second power with an
4319unspecified sequence of rounding operations.</p>
4320</div>
4321
4322
Andrew Lenharthec370fd2005-05-03 18:01:48 +0000[diff] [blame]4323<!-- ======================================================================= -->
4324<div class="doc_subsection">
Nate Begeman7e36c472006-01-13 23:26:38 +0000[diff] [blame]4325 <a name="int_manip">Bit Manipulation Intrinsics</a>
Andrew Lenharthec370fd2005-05-03 18:01:48 +0000[diff] [blame]4326</div>
4327
4328<div class="doc_text">
4329<p>
Nate Begeman7e36c472006-01-13 23:26:38 +0000[diff] [blame]4330LLVM provides intrinsics for a few important bit manipulation operations.
Andrew Lenharthec370fd2005-05-03 18:01:48 +0000[diff] [blame]4331These allow efficient code generation for some algorithms.
4332</p>
4333
4334</div>
4335
4336<!-- _______________________________________________________________________ -->
4337<div class="doc_subsubsection">
Nate Begeman7e36c472006-01-13 23:26:38 +0000[diff] [blame]4338 <a name="i_bswap">'<tt>llvm.bswap.*</tt>' Intrinsics</a>
4339</div>
4340
4341<div class="doc_text">
4342
4343<h5>Syntax:</h5>
4344<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]4345 declare i16 %llvm.bswap.i16(i16 &lt;id&gt;)
4346 declare i32 %llvm.bswap.i32(i32 &lt;id&gt;)
4347 declare i64 %llvm.bswap.i64(i64 &lt;id&gt;)
Nate Begeman7e36c472006-01-13 23:26:38 +0000[diff] [blame]4348</pre>
4349
4350<h5>Overview:</h5>
4351
4352<p>
4353The '<tt>llvm.bwsap</tt>' family of intrinsics is used to byteswap a 16, 32 or
435464 bit quantity. These are useful for performing operations on data that is not
4355in the target's native byte order.
4356</p>
4357
4358<h5>Semantics:</h5>
4359
4360<p>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]4361The <tt>llvm.bswap.16</tt> intrinsic returns an i16 value that has the high
4362and low byte of the input i16 swapped. Similarly, the <tt>llvm.bswap.i32</tt>
4363intrinsic returns an i32 value that has the four bytes of the input i32
4364swapped, so that if the input bytes are numbered 0, 1, 2, 3 then the returned
4365i32 will have its bytes in 3, 2, 1, 0 order. The <tt>llvm.bswap.i64</tt>
4366intrinsic extends this concept to 64 bits.
Nate Begeman7e36c472006-01-13 23:26:38 +0000[diff] [blame]4367</p>
4368
4369</div>
4370
4371<!-- _______________________________________________________________________ -->
4372<div class="doc_subsubsection">
Reid Spencer0b118202006-01-16 21:12:35 +0000[diff] [blame]4373 <a name="int_ctpop">'<tt>llvm.ctpop.*</tt>' Intrinsic</a>
Andrew Lenharthec370fd2005-05-03 18:01:48 +0000[diff] [blame]4374</div>
4375
4376<div class="doc_text">
4377
4378<h5>Syntax:</h5>
4379<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]4380 declare i8 %llvm.ctpop.i8 (i8 &lt;src&gt;)
4381 declare i16 %llvm.ctpop.i16(i16 &lt;src&gt;)
4382 declare i32 %llvm.ctpop.i32(i32 &lt;src&gt;)
4383 declare i64 %llvm.ctpop.i64(i64 &lt;src&gt;)
Andrew Lenharthec370fd2005-05-03 18:01:48 +0000[diff] [blame]4384</pre>
4385
4386<h5>Overview:</h5>
4387
4388<p>
Chris Lattnerec6cb612006-01-16 22:38:59 +0000[diff] [blame]4389The '<tt>llvm.ctpop</tt>' family of intrinsics counts the number of bits set in a
4390value.
Andrew Lenharthec370fd2005-05-03 18:01:48 +0000[diff] [blame]4391</p>
4392
4393<h5>Arguments:</h5>
4394
4395<p>
Chris Lattnercfe6b372005-05-07 01:46:40 +0000[diff] [blame]4396The only argument is the value to be counted. The argument may be of any
Reid Spencera5173382007-01-04 16:43:23 +0000[diff] [blame]4397integer type. The return type must match the argument type.
Andrew Lenharthec370fd2005-05-03 18:01:48 +0000[diff] [blame]4398</p>
4399
4400<h5>Semantics:</h5>
4401
4402<p>
4403The '<tt>llvm.ctpop</tt>' intrinsic counts the 1's in a variable.
4404</p>
4405</div>
4406
4407<!-- _______________________________________________________________________ -->
4408<div class="doc_subsubsection">
Chris Lattner8a886be2006-01-16 22:34:14 +0000[diff] [blame]4409 <a name="int_ctlz">'<tt>llvm.ctlz.*</tt>' Intrinsic</a>
Andrew Lenharthec370fd2005-05-03 18:01:48 +0000[diff] [blame]4410</div>
4411
4412<div class="doc_text">
4413
4414<h5>Syntax:</h5>
4415<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]4416 declare i8 %llvm.ctlz.i8 (i8 &lt;src&gt;)
4417 declare i16 %llvm.ctlz.i16(i16 &lt;src&gt;)
4418 declare i32 %llvm.ctlz.i32(i32 &lt;src&gt;)
4419 declare i64 %llvm.ctlz.i64(i64 &lt;src&gt;)
Andrew Lenharthec370fd2005-05-03 18:01:48 +0000[diff] [blame]4420</pre>
4421
4422<h5>Overview:</h5>
4423
4424<p>
Reid Spencer0b118202006-01-16 21:12:35 +0000[diff] [blame]4425The '<tt>llvm.ctlz</tt>' family of intrinsic functions counts the number of
4426leading zeros in a variable.
Andrew Lenharthec370fd2005-05-03 18:01:48 +0000[diff] [blame]4427</p>
4428
4429<h5>Arguments:</h5>
4430
4431<p>
Chris Lattnercfe6b372005-05-07 01:46:40 +0000[diff] [blame]4432The only argument is the value to be counted. The argument may be of any
Reid Spencera5173382007-01-04 16:43:23 +0000[diff] [blame]4433integer type. The return type must match the argument type.
Andrew Lenharthec370fd2005-05-03 18:01:48 +0000[diff] [blame]4434</p>
4435
4436<h5>Semantics:</h5>
4437
4438<p>
Chris Lattnereff29ab2005-05-15 19:39:26 +0000[diff] [blame]4439The '<tt>llvm.ctlz</tt>' intrinsic counts the leading (most significant) zeros
4440in a variable. If the src == 0 then the result is the size in bits of the type
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]4441of src. For example, <tt>llvm.ctlz(i32 2) = 30</tt>.
Andrew Lenharthec370fd2005-05-03 18:01:48 +0000[diff] [blame]4442</p>
4443</div>
Chris Lattner32006282004-06-11 02:28:03 +0000[diff] [blame]4444
4445
Chris Lattnereff29ab2005-05-15 19:39:26 +0000[diff] [blame]4446
4447<!-- _______________________________________________________________________ -->
4448<div class="doc_subsubsection">
Chris Lattner8a886be2006-01-16 22:34:14 +0000[diff] [blame]4449 <a name="int_cttz">'<tt>llvm.cttz.*</tt>' Intrinsic</a>
Chris Lattnereff29ab2005-05-15 19:39:26 +0000[diff] [blame]4450</div>
4451
4452<div class="doc_text">
4453
4454<h5>Syntax:</h5>
4455<pre>
Reid Spencerca86e162006-12-31 07:07:53 +0000[diff] [blame]4456 declare i8 %llvm.cttz.i8 (i8 &lt;src&gt;)
4457 declare i16 %llvm.cttz.i16(i16 &lt;src&gt;)
4458 declare i32 %llvm.cttz.i32(i32 &lt;src&gt;)
4459 declare i64 %llvm.cttz.i64(i64 &lt;src&gt;)
Chris Lattnereff29ab2005-05-15 19:39:26 +0000[diff] [blame]4460</pre>
4461
4462<h5>Overview:</h5>
4463
4464<p>
Reid Spencer0b118202006-01-16 21:12:35 +0000[diff] [blame]4465The '<tt>llvm.cttz</tt>' family of intrinsic functions counts the number of
4466trailing zeros.
Chris Lattnereff29ab2005-05-15 19:39:26 +0000[diff] [blame]4467</p>
4468
4469<h5>Arguments:</h5>
4470
4471<p>
4472The only argument is the value to be counted. The argument may be of any
Reid Spencera5173382007-01-04 16:43:23 +0000[diff] [blame]4473integer type. The return type must match the argument type.
Chris Lattnereff29ab2005-05-15 19:39:26 +0000[diff] [blame]4474</p>
4475
4476<h5>Semantics:</h5>
4477
4478<p>
4479The '<tt>llvm.cttz</tt>' intrinsic counts the trailing (least significant) zeros
4480in a variable. If the src == 0 then the result is the size in bits of the type
4481of src. For example, <tt>llvm.cttz(2) = 1</tt>.
4482</p>
4483</div>
4484
Chris Lattner8ff75902004-01-06 05:31:32 +0000[diff] [blame]4485<!-- ======================================================================= -->
4486<div class="doc_subsection">
4487 <a name="int_debugger">Debugger Intrinsics</a>
4488</div>
4489
4490<div class="doc_text">
4491<p>
4492The LLVM debugger intrinsics (which all start with <tt>llvm.dbg.</tt> prefix),
4493are described in the <a
4494href="SourceLevelDebugging.html#format_common_intrinsics">LLVM Source Level
4495Debugging</a> document.
4496</p>
4497</div>
4498
4499
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]4500<!-- *********************************************************************** -->
Chris Lattner00950542001-06-06 20:29:01 +0000[diff] [blame]4501<hr>
Misha Brukmandaa4cb02004-03-01 17:47:27 +0000[diff] [blame]4502<address>
4503 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
4504 src="http://jigsaw.w3.org/css-validator/images/vcss" alt="Valid CSS!"></a>
4505 <a href="http://validator.w3.org/check/referer"><img
4506 src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" /></a>
4507
4508 <a href="mailto:sabre@nondot.org">Chris Lattner</a><br>
Reid Spencer05fe4b02006-03-14 05:39:39 +0000[diff] [blame]4509 <a href="http://llvm.org">The LLVM Compiler Infrastructure</a><br>
Misha Brukmandaa4cb02004-03-01 17:47:27 +0000[diff] [blame]4510 Last modified: $Date$
4511</address>
Misha Brukman9d0919f2003-11-08 01:05:38 +0000[diff] [blame]4512</body>
4513</html>