Blame - docs/LangRef.html - fp2-dev/platform/external/llvm

blob: 1beb670765d858eaabbc95df2030708f9665674a [file] [log] [blame]

Misha Brukman	daa4cb0	2004-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 Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	3	<html>
				4	<head>
				5	<title>LLVM Assembly Language Reference Manual</title>
Reid Spencer	3921c74	2004-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 Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	10	<link rel="stylesheet" href="llvm.css" type="text/css">
				11	</head>
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	12
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	13	<body>
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	14
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	15	<div class="doc_title"> LLVM Language Reference Manual </div>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	16	<ol>
Misha Brukman	9d0919f	2003-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 Lattner	fa73021	2004-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 Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	23	<li><a href="#linkage">Linkage Types</a></li>
Chris Lattner	bad10ee	2005-05-06 22:57:40 +0000	[diff] [blame]	24	<li><a href="#callingconv">Calling Conventions</a></li>
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	25	<li><a href="#globalvars">Global Variables</a></li>
Chris Lattner	4e9aba7	2006-01-23 23:23:47 +0000	[diff] [blame]	26	<li><a href="#functionstructure">Functions</a></li>
Anton Korobeynikov	c6c98af	2007-04-29 18:02:48 +0000	[diff] [blame]	27	<li><a href="#aliasstructure">Aliases</a>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	28	<li><a href="#paramattrs">Parameter Attributes</a></li>
Gordon Henriksen	80a75bf	2007-12-10 03:18:06 +0000	[diff] [blame]	29	<li><a href="#gc">Garbage Collector Names</a></li>
Devang Patel	cdc0669	2008-09-04 23:10:26 +0000	[diff] [blame]	30	<li><a href="#notes">Function Notes</a></li>
Chris Lattner	4e9aba7	2006-01-23 23:23:47 +0000	[diff] [blame]	31	<li><a href="#moduleasm">Module-Level Inline Assembly</a></li>
Reid Spencer	de15194	2007-02-19 23:54:10 +0000	[diff] [blame]	32	<li><a href="#datalayout">Data Layout</a></li>
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	33	</ol>
				34	</li>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	35	<li><a href="#typesystem">Type System</a>
				36	<ol>
Chris Lattner	4f69f46	2008-01-04 04:32:38 +0000	[diff] [blame]	37	<li><a href="#t_classifications">Type Classifications</a></li>
Robert Bocchino	7b81c75	2006-02-17 21:18:08 +0000	[diff] [blame]	38	<li><a href="#t_primitive">Primitive Types</a>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	39	<ol>
Chris Lattner	4f69f46	2008-01-04 04:32:38 +0000	[diff] [blame]	40	<li><a href="#t_floating">Floating Point Types</a></li>
				41	<li><a href="#t_void">Void Type</a></li>
				42	<li><a href="#t_label">Label Type</a></li>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	43	</ol>
				44	</li>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	45	<li><a href="#t_derived">Derived Types</a>
				46	<ol>
Chris Lattner	b9488a6	2007-12-18 06:18:21 +0000	[diff] [blame]	47	<li><a href="#t_integer">Integer Type</a></li>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	48	<li><a href="#t_array">Array Type</a></li>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	49	<li><a href="#t_function">Function Type</a></li>
				50	<li><a href="#t_pointer">Pointer Type</a></li>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	51	<li><a href="#t_struct">Structure Type</a></li>
Andrew Lenharth	75e1068	2006-12-08 17:13:00 +0000	[diff] [blame]	52	<li><a href="#t_pstruct">Packed Structure Type</a></li>
Reid Spencer	485bad1	2007-02-15 03:07:05 +0000	[diff] [blame]	53	<li><a href="#t_vector">Vector Type</a></li>
Chris Lattner	69c11bb	2005-04-25 17:34:15 +0000	[diff] [blame]	54	<li><a href="#t_opaque">Opaque Type</a></li>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	55	</ol>
				56	</li>
				57	</ol>
				58	</li>
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	59	<li><a href="#constants">Constants</a>
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	60	<ol>
				61	<li><a href="#simpleconstants">Simple Constants</a>
				62	<li><a href="#aggregateconstants">Aggregate Constants</a>
				63	<li><a href="#globalconstants">Global Variable and Function Addresses</a>
				64	<li><a href="#undefvalues">Undefined Values</a>
				65	<li><a href="#constantexprs">Constant Expressions</a>
				66	</ol>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	67	</li>
Chris Lattner	e87d653	2006-01-25 23:47:57 +0000	[diff] [blame]	68	<li><a href="#othervalues">Other Values</a>
				69	<ol>
				70	<li><a href="#inlineasm">Inline Assembler Expressions</a>
				71	</ol>
				72	</li>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	73	<li><a href="#instref">Instruction Reference</a>
				74	<ol>
				75	<li><a href="#terminators">Terminator Instructions</a>
				76	<ol>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	77	<li><a href="#i_ret">'<tt>ret</tt>' Instruction</a></li>
				78	<li><a href="#i_br">'<tt>br</tt>' Instruction</a></li>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	79	<li><a href="#i_switch">'<tt>switch</tt>' Instruction</a></li>
				80	<li><a href="#i_invoke">'<tt>invoke</tt>' Instruction</a></li>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	81	<li><a href="#i_unwind">'<tt>unwind</tt>' Instruction</a></li>
Chris Lattner	35eca58	2004-10-16 18:04:13 +0000	[diff] [blame]	82	<li><a href="#i_unreachable">'<tt>unreachable</tt>' Instruction</a></li>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	83	</ol>
				84	</li>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	85	<li><a href="#binaryops">Binary Operations</a>
				86	<ol>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	87	<li><a href="#i_add">'<tt>add</tt>' Instruction</a></li>
				88	<li><a href="#i_sub">'<tt>sub</tt>' Instruction</a></li>
				89	<li><a href="#i_mul">'<tt>mul</tt>' Instruction</a></li>
Reid Spencer	1628cec	2006-10-26 06:15:43 +0000	[diff] [blame]	90	<li><a href="#i_udiv">'<tt>udiv</tt>' Instruction</a></li>
				91	<li><a href="#i_sdiv">'<tt>sdiv</tt>' Instruction</a></li>
				92	<li><a href="#i_fdiv">'<tt>fdiv</tt>' Instruction</a></li>
Reid Spencer	0a783f7	2006-11-02 01:53:59 +0000	[diff] [blame]	93	<li><a href="#i_urem">'<tt>urem</tt>' Instruction</a></li>
				94	<li><a href="#i_srem">'<tt>srem</tt>' Instruction</a></li>
				95	<li><a href="#i_frem">'<tt>frem</tt>' Instruction</a></li>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	96	</ol>
				97	</li>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	98	<li><a href="#bitwiseops">Bitwise Binary Operations</a>
				99	<ol>
Reid Spencer	8e11bf8	2007-02-02 13:57:07 +0000	[diff] [blame]	100	<li><a href="#i_shl">'<tt>shl</tt>' Instruction</a></li>
				101	<li><a href="#i_lshr">'<tt>lshr</tt>' Instruction</a></li>
				102	<li><a href="#i_ashr">'<tt>ashr</tt>' Instruction</a></li>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	103	<li><a href="#i_and">'<tt>and</tt>' Instruction</a></li>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	104	<li><a href="#i_or">'<tt>or</tt>' Instruction</a></li>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	105	<li><a href="#i_xor">'<tt>xor</tt>' Instruction</a></li>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	106	</ol>
				107	</li>
Chris Lattner	3df241e	2006-04-08 23:07:04 +0000	[diff] [blame]	108	<li><a href="#vectorops">Vector Operations</a>
				109	<ol>
				110	<li><a href="#i_extractelement">'<tt>extractelement</tt>' Instruction</a></li>
				111	<li><a href="#i_insertelement">'<tt>insertelement</tt>' Instruction</a></li>
				112	<li><a href="#i_shufflevector">'<tt>shufflevector</tt>' Instruction</a></li>
Chris Lattner	3df241e	2006-04-08 23:07:04 +0000	[diff] [blame]	113	</ol>
				114	</li>
Dan Gohman	a334d5f	2008-05-12 23:51:09 +0000	[diff] [blame]	115	<li><a href="#aggregateops">Aggregate Operations</a>
				116	<ol>
				117	<li><a href="#i_extractvalue">'<tt>extractvalue</tt>' Instruction</a></li>
				118	<li><a href="#i_insertvalue">'<tt>insertvalue</tt>' Instruction</a></li>
				119	</ol>
				120	</li>
Chris Lattner	884a970	2006-08-15 00:45:58 +0000	[diff] [blame]	121	<li><a href="#memoryops">Memory Access and Addressing Operations</a>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	122	<ol>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	123	<li><a href="#i_malloc">'<tt>malloc</tt>' Instruction</a></li>
				124	<li><a href="#i_free">'<tt>free</tt>' Instruction</a></li>
				125	<li><a href="#i_alloca">'<tt>alloca</tt>' Instruction</a></li>
Robert Bocchino	7b81c75	2006-02-17 21:18:08 +0000	[diff] [blame]	126	<li><a href="#i_load">'<tt>load</tt>' Instruction</a></li>
				127	<li><a href="#i_store">'<tt>store</tt>' Instruction</a></li>
				128	<li><a href="#i_getelementptr">'<tt>getelementptr</tt>' Instruction</a></li>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	129	</ol>
				130	</li>
Reid Spencer	2fd21e6	2006-11-08 01:18:52 +0000	[diff] [blame]	131	<li><a href="#convertops">Conversion Operations</a>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	132	<ol>
				133	<li><a href="#i_trunc">'<tt>trunc .. to</tt>' Instruction</a></li>
				134	<li><a href="#i_zext">'<tt>zext .. to</tt>' Instruction</a></li>
				135	<li><a href="#i_sext">'<tt>sext .. to</tt>' Instruction</a></li>
				136	<li><a href="#i_fptrunc">'<tt>fptrunc .. to</tt>' Instruction</a></li>
				137	<li><a href="#i_fpext">'<tt>fpext .. to</tt>' Instruction</a></li>
Reid Spencer	d444879	2006-11-09 23:03:26 +0000	[diff] [blame]	138	<li><a href="#i_fptoui">'<tt>fptoui .. to</tt>' Instruction</a></li>
				139	<li><a href="#i_fptosi">'<tt>fptosi .. to</tt>' Instruction</a></li>
				140	<li><a href="#i_uitofp">'<tt>uitofp .. to</tt>' Instruction</a></li>
				141	<li><a href="#i_sitofp">'<tt>sitofp .. to</tt>' Instruction</a></li>
Reid Spencer	7267925	2006-11-11 21:00:47 +0000	[diff] [blame]	142	<li><a href="#i_ptrtoint">'<tt>ptrtoint .. to</tt>' Instruction</a></li>
				143	<li><a href="#i_inttoptr">'<tt>inttoptr .. to</tt>' Instruction</a></li>
Reid Spencer	5c0ef47	2006-11-11 23:08:07 +0000	[diff] [blame]	144	<li><a href="#i_bitcast">'<tt>bitcast .. to</tt>' Instruction</a></li>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	145	</ol>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	146	<li><a href="#otherops">Other Operations</a>
				147	<ol>
Reid Spencer	f3a70a6	2006-11-18 21:50:54 +0000	[diff] [blame]	148	<li><a href="#i_icmp">'<tt>icmp</tt>' Instruction</a></li>
				149	<li><a href="#i_fcmp">'<tt>fcmp</tt>' Instruction</a></li>
Nate Begeman	ac80ade	2008-05-12 19:01:56 +0000	[diff] [blame]	150	<li><a href="#i_vicmp">'<tt>vicmp</tt>' Instruction</a></li>
				151	<li><a href="#i_vfcmp">'<tt>vfcmp</tt>' Instruction</a></li>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	152	<li><a href="#i_phi">'<tt>phi</tt>' Instruction</a></li>
Chris Lattner	cc37aae	2004-03-12 05:50:16 +0000	[diff] [blame]	153	<li><a href="#i_select">'<tt>select</tt>' Instruction</a></li>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	154	<li><a href="#i_call">'<tt>call</tt>' Instruction</a></li>
Chris Lattner	fb6977d	2006-01-13 23:26:01 +0000	[diff] [blame]	155	<li><a href="#i_va_arg">'<tt>va_arg</tt>' Instruction</a></li>
Devang Patel	c3fc6df	2008-03-10 20:49:15 +0000	[diff] [blame]	156	<li><a href="#i_getresult">'<tt>getresult</tt>' Instruction</a></li>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	157	</ol>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	158	</li>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	159	</ol>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	160	</li>
Chris Lattner	d9ad5b3	2003-05-08 04:57:36 +0000	[diff] [blame]	161	<li><a href="#intrinsics">Intrinsic Functions</a>
Chris Lattner	d9ad5b3	2003-05-08 04:57:36 +0000	[diff] [blame]	162	<ol>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	163	<li><a href="#int_varargs">Variable Argument Handling Intrinsics</a>
				164	<ol>
Reid Spencer	a3e435f	2007-04-04 02:42:35 +0000	[diff] [blame]	165	<li><a href="#int_va_start">'<tt>llvm.va_start</tt>' Intrinsic</a></li>
				166	<li><a href="#int_va_end">'<tt>llvm.va_end</tt>' Intrinsic</a></li>
				167	<li><a href="#int_va_copy">'<tt>llvm.va_copy</tt>' Intrinsic</a></li>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	168	</ol>
				169	</li>
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	170	<li><a href="#int_gc">Accurate Garbage Collection Intrinsics</a>
				171	<ol>
Reid Spencer	a3e435f	2007-04-04 02:42:35 +0000	[diff] [blame]	172	<li><a href="#int_gcroot">'<tt>llvm.gcroot</tt>' Intrinsic</a></li>
				173	<li><a href="#int_gcread">'<tt>llvm.gcread</tt>' Intrinsic</a></li>
				174	<li><a href="#int_gcwrite">'<tt>llvm.gcwrite</tt>' Intrinsic</a></li>
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	175	</ol>
				176	</li>
Chris Lattner	1061064	2004-02-14 04:08:35 +0000	[diff] [blame]	177	<li><a href="#int_codegen">Code Generator Intrinsics</a>
				178	<ol>
Reid Spencer	a3e435f	2007-04-04 02:42:35 +0000	[diff] [blame]	179	<li><a href="#int_returnaddress">'<tt>llvm.returnaddress</tt>' Intrinsic</a></li>
				180	<li><a href="#int_frameaddress">'<tt>llvm.frameaddress</tt>' Intrinsic</a></li>
				181	<li><a href="#int_stacksave">'<tt>llvm.stacksave</tt>' Intrinsic</a></li>
				182	<li><a href="#int_stackrestore">'<tt>llvm.stackrestore</tt>' Intrinsic</a></li>
				183	<li><a href="#int_prefetch">'<tt>llvm.prefetch</tt>' Intrinsic</a></li>
				184	<li><a href="#int_pcmarker">'<tt>llvm.pcmarker</tt>' Intrinsic</a></li>
				185	<li><a href="#int_readcyclecounter"><tt>llvm.readcyclecounter</tt>' Intrinsic</a></li>
John Criswell	7123e27	2004-04-09 16:43:20 +0000	[diff] [blame]	186	</ol>
				187	</li>
Chris Lattner	33aec9e	2004-02-12 17:01:32 +0000	[diff] [blame]	188	<li><a href="#int_libc">Standard C Library Intrinsics</a>
				189	<ol>
Reid Spencer	a3e435f	2007-04-04 02:42:35 +0000	[diff] [blame]	190	<li><a href="#int_memcpy">'<tt>llvm.memcpy.*</tt>' Intrinsic</a></li>
				191	<li><a href="#int_memmove">'<tt>llvm.memmove.*</tt>' Intrinsic</a></li>
				192	<li><a href="#int_memset">'<tt>llvm.memset.*</tt>' Intrinsic</a></li>
				193	<li><a href="#int_sqrt">'<tt>llvm.sqrt.*</tt>' Intrinsic</a></li>
				194	<li><a href="#int_powi">'<tt>llvm.powi.*</tt>' Intrinsic</a></li>
Dan Gohman	91c284c	2007-10-15 20:30:11 +0000	[diff] [blame]	195	<li><a href="#int_sin">'<tt>llvm.sin.*</tt>' Intrinsic</a></li>
				196	<li><a href="#int_cos">'<tt>llvm.cos.*</tt>' Intrinsic</a></li>
				197	<li><a href="#int_pow">'<tt>llvm.pow.*</tt>' Intrinsic</a></li>
Chris Lattner	33aec9e	2004-02-12 17:01:32 +0000	[diff] [blame]	198	</ol>
				199	</li>
Nate Begeman	7e36c47	2006-01-13 23:26:38 +0000	[diff] [blame]	200	<li><a href="#int_manip">Bit Manipulation Intrinsics</a>
Andrew Lenharth	ec370fd	2005-05-03 18:01:48 +0000	[diff] [blame]	201	<ol>
Reid Spencer	a3e435f	2007-04-04 02:42:35 +0000	[diff] [blame]	202	<li><a href="#int_bswap">'<tt>llvm.bswap.*</tt>' Intrinsics</a></li>
Chris Lattner	8a886be	2006-01-16 22:34:14 +0000	[diff] [blame]	203	<li><a href="#int_ctpop">'<tt>llvm.ctpop.*</tt>' Intrinsic </a></li>
				204	<li><a href="#int_ctlz">'<tt>llvm.ctlz.*</tt>' Intrinsic </a></li>
				205	<li><a href="#int_cttz">'<tt>llvm.cttz.*</tt>' Intrinsic </a></li>
Reid Spencer	f86037f	2007-04-11 23:23:49 +0000	[diff] [blame]	206	<li><a href="#int_part_select">'<tt>llvm.part.select.*</tt>' Intrinsic </a></li>
				207	<li><a href="#int_part_set">'<tt>llvm.part.set.*</tt>' Intrinsic </a></li>
Andrew Lenharth	ec370fd	2005-05-03 18:01:48 +0000	[diff] [blame]	208	</ol>
				209	</li>
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	210	<li><a href="#int_debugger">Debugger intrinsics</a></li>
Jim Laskey	dd4ef1b	2007-03-14 19:31:19 +0000	[diff] [blame]	211	<li><a href="#int_eh">Exception Handling intrinsics</a></li>
Duncan Sands	f7331b3	2007-09-11 14:10:23 +0000	[diff] [blame]	212	<li><a href="#int_trampoline">Trampoline Intrinsic</a>
Duncan Sands	36397f5	2007-07-27 12:58:54 +0000	[diff] [blame]	213	<ol>
				214	<li><a href="#int_it">'<tt>llvm.init.trampoline</tt>' Intrinsic</a></li>
Duncan Sands	36397f5	2007-07-27 12:58:54 +0000	[diff] [blame]	215	</ol>
				216	</li>
Andrew Lenharth	22c5c1b	2008-02-16 01:24:58 +0000	[diff] [blame]	217	<li><a href="#int_atomics">Atomic intrinsics</a>
				218	<ol>
Andrew Lenharth	ab0b949	2008-02-21 06:45:13 +0000	[diff] [blame]	219	<li><a href="#int_memory_barrier"><tt>llvm.memory_barrier</tt></a></li>
Mon P Wang	2887310	2008-06-25 08:15:39 +0000	[diff] [blame]	220	<li><a href="#int_atomic_cmp_swap"><tt>llvm.atomic.cmp.swap</tt></a></li>
Andrew Lenharth	ab0b949	2008-02-21 06:45:13 +0000	[diff] [blame]	221	<li><a href="#int_atomic_swap"><tt>llvm.atomic.swap</tt></a></li>
Mon P Wang	2887310	2008-06-25 08:15:39 +0000	[diff] [blame]	222	<li><a href="#int_atomic_load_add"><tt>llvm.atomic.load.add</tt></a></li>
				223	<li><a href="#int_atomic_load_sub"><tt>llvm.atomic.load.sub</tt></a></li>
				224	<li><a href="#int_atomic_load_and"><tt>llvm.atomic.load.and</tt></a></li>
				225	<li><a href="#int_atomic_load_nand"><tt>llvm.atomic.load.nand</tt></a></li>
				226	<li><a href="#int_atomic_load_or"><tt>llvm.atomic.load.or</tt></a></li>
				227	<li><a href="#int_atomic_load_xor"><tt>llvm.atomic.load.xor</tt></a></li>
				228	<li><a href="#int_atomic_load_max"><tt>llvm.atomic.load.max</tt></a></li>
				229	<li><a href="#int_atomic_load_min"><tt>llvm.atomic.load.min</tt></a></li>
				230	<li><a href="#int_atomic_load_umax"><tt>llvm.atomic.load.umax</tt></a></li>
				231	<li><a href="#int_atomic_load_umin"><tt>llvm.atomic.load.umin</tt></a></li>
Andrew Lenharth	22c5c1b	2008-02-16 01:24:58 +0000	[diff] [blame]	232	</ol>
				233	</li>
Reid Spencer	2067764	2007-07-20 19:59:11 +0000	[diff] [blame]	234	<li><a href="#int_general">General intrinsics</a>
Tanya Lattner	6d806e9	2007-06-15 20:50:54 +0000	[diff] [blame]	235	<ol>
Reid Spencer	2067764	2007-07-20 19:59:11 +0000	[diff] [blame]	236	<li><a href="#int_var_annotation">
Tanya Lattner	91d0b88	2007-09-22 00:01:26 +0000	[diff] [blame]	237	<tt>llvm.var.annotation</tt>' Intrinsic</a></li>
Tanya Lattner	b636788	2007-09-21 22:59:12 +0000	[diff] [blame]	238	<li><a href="#int_annotation">
Tanya Lattner	91d0b88	2007-09-22 00:01:26 +0000	[diff] [blame]	239	<tt>llvm.annotation.*</tt>' Intrinsic</a></li>
Anton Korobeynikov	4cb8618	2008-01-15 22:31:34 +0000	[diff] [blame]	240	<li><a href="#int_trap">
				241	<tt>llvm.trap</tt>' Intrinsic</a></li>
Tanya Lattner	b636788	2007-09-21 22:59:12 +0000	[diff] [blame]	242	</ol>
Tanya Lattner	6d806e9	2007-06-15 20:50:54 +0000	[diff] [blame]	243	</li>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	244	</ol>
				245	</li>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	246	</ol>
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	247
				248	<div class="doc_author">
				249	<p>Written by <a href="mailto:sabre@nondot.org">Chris Lattner</a>
				250	and <a href="mailto:vadve@cs.uiuc.edu">Vikram Adve</a></p>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	251	</div>
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	252
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	253	<!-- *********************************************************************** -->
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	254	<div class="doc_section"> <a name="abstract">Abstract </a></div>
				255	<!-- *********************************************************************** -->
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	256
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	257	<div class="doc_text">
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	258	<p>This document is a reference manual for the LLVM assembly language.
Bill Wendling	837f39b	2008-08-05 22:29:16 +0000	[diff] [blame]	259	LLVM is a Static Single Assignment (SSA) based representation that provides
Chris Lattner	d3eda89	2008-08-05 18:29:16 +0000	[diff] [blame]	260	type safety, low-level operations, flexibility, and the capability of
				261	representing 'all' high-level languages cleanly. It is the common code
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	262	representation used throughout all phases of the LLVM compilation
				263	strategy.</p>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	264	</div>
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	265
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	266	<!-- *********************************************************************** -->
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	267	<div class="doc_section"> <a name="introduction">Introduction</a> </div>
				268	<!-- *********************************************************************** -->
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	269
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	270	<div class="doc_text">
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	271
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	272	<p>The LLVM code representation is designed to be used in three
Gabor Greif	04367bf	2007-07-06 22:07:22 +0000	[diff] [blame]	273	different forms: as an in-memory compiler IR, as an on-disk bitcode
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	274	representation (suitable for fast loading by a Just-In-Time compiler),
				275	and as a human readable assembly language representation. This allows
				276	LLVM to provide a powerful intermediate representation for efficient
				277	compiler transformations and analysis, while providing a natural means
				278	to debug and visualize the transformations. The three different forms
				279	of LLVM are all equivalent. This document describes the human readable
				280	representation and notation.</p>
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	281
John Criswell	c1f786c	2005-05-13 22:25:59 +0000	[diff] [blame]	282	<p>The LLVM representation aims to be light-weight and low-level
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	283	while being expressive, typed, and extensible at the same time. It
				284	aims to be a "universal IR" of sorts, by being at a low enough level
				285	that high-level ideas may be cleanly mapped to it (similar to how
				286	microprocessors are "universal IR's", allowing many source languages to
				287	be mapped to them). By providing type information, LLVM can be used as
				288	the target of optimizations: for example, through pointer analysis, it
				289	can be proven that a C automatic variable is never accessed outside of
				290	the current function... allowing it to be promoted to a simple SSA
				291	value instead of a memory location.</p>
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	292
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	293	</div>
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	294
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	295	<!-- _______________________________________________________________________ -->
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	296	<div class="doc_subsubsection"> <a name="wellformed">Well-Formedness</a> </div>
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	297
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	298	<div class="doc_text">
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	299
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	300	<p>It is important to note that this document describes 'well formed'
				301	LLVM assembly language. There is a difference between what the parser
				302	accepts and what is considered 'well formed'. For example, the
				303	following instruction is syntactically okay, but not well formed:</p>
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	304
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	305	<div class="doc_code">
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	306	<pre>
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	307	%x = <a href="#i_add">add</a> i32 1, %x
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	308	</pre>
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	309	</div>
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	310
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	311	<p>...because the definition of <tt>%x</tt> does not dominate all of
				312	its uses. The LLVM infrastructure provides a verification pass that may
				313	be used to verify that an LLVM module is well formed. This pass is
John Criswell	c1f786c	2005-05-13 22:25:59 +0000	[diff] [blame]	314	automatically run by the parser after parsing input assembly and by
Gabor Greif	04367bf	2007-07-06 22:07:22 +0000	[diff] [blame]	315	the optimizer before it outputs bitcode. The violations pointed out
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	316	by the verifier pass indicate bugs in transformation passes or input to
				317	the parser.</p>
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	318	</div>
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	319
Chris Lattner	cc68939	2007-10-03 17:34:29 +0000	[diff] [blame]	320	<!-- Describe the typesetting conventions here. -->
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	321
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	322	<!-- *********************************************************************** -->
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	323	<div class="doc_section"> <a name="identifiers">Identifiers</a> </div>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	324	<!-- *********************************************************************** -->
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	325
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	326	<div class="doc_text">
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	327
Reid Spencer	2c45228	2007-08-07 14:34:28 +0000	[diff] [blame]	328	<p>LLVM identifiers come in two basic types: global and local. Global
				329	identifiers (functions, global variables) begin with the @ character. Local
				330	identifiers (register names, types) begin with the % character. Additionally,
				331	there are three different formats for identifiers, for different purposes:
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	332
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	333	<ol>
Reid Spencer	2c45228	2007-08-07 14:34:28 +0000	[diff] [blame]	334	<li>Named values are represented as a string of characters with their prefix.
				335	For example, %foo, @DivisionByZero, %a.really.long.identifier. The actual
				336	regular expression used is '<tt>[%@][a-zA-Z$._][a-zA-Z$._0-9]*</tt>'.
Chris Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	337	Identifiers which require other characters in their names can be surrounded
Reid Spencer	2c45228	2007-08-07 14:34:28 +0000	[diff] [blame]	338	with quotes. In this way, anything except a <tt>"</tt> character can
				339	be used in a named value.</li>
Chris Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	340
Reid Spencer	2c45228	2007-08-07 14:34:28 +0000	[diff] [blame]	341	<li>Unnamed values are represented as an unsigned numeric value with their
				342	prefix. For example, %12, @2, %44.</li>
Chris Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	343
Reid Spencer	cc16dc3	2004-12-09 18:02:53 +0000	[diff] [blame]	344	<li>Constants, which are described in a <a href="#constants">section about
				345	constants</a>, below.</li>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	346	</ol>
Chris Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	347
Reid Spencer	2c45228	2007-08-07 14:34:28 +0000	[diff] [blame]	348	<p>LLVM requires that values start with a prefix for two reasons: Compilers
Chris Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	349	don't need to worry about name clashes with reserved words, and the set of
				350	reserved words may be expanded in the future without penalty. Additionally,
				351	unnamed identifiers allow a compiler to quickly come up with a temporary
				352	variable without having to avoid symbol table conflicts.</p>
				353
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	354	<p>Reserved words in LLVM are very similar to reserved words in other
Reid Spencer	5c0ef47	2006-11-11 23:08:07 +0000	[diff] [blame]	355	languages. There are keywords for different opcodes
				356	('<tt><a href="#i_add">add</a></tt>',
				357	'<tt><a href="#i_bitcast">bitcast</a></tt>',
				358	'<tt><a href="#i_ret">ret</a></tt>', etc...), for primitive type names ('<tt><a
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	359	href="#t_void">void</a></tt>', '<tt><a href="#t_primitive">i32</a></tt>', etc...),
Chris Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	360	and others. These reserved words cannot conflict with variable names, because
Reid Spencer	2c45228	2007-08-07 14:34:28 +0000	[diff] [blame]	361	none of them start with a prefix character ('%' or '@').</p>
Chris Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	362
				363	<p>Here is an example of LLVM code to multiply the integer variable
				364	'<tt>%X</tt>' by 8:</p>
				365
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	366	<p>The easy way:</p>
Chris Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	367
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	368	<div class="doc_code">
Chris Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	369	<pre>
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	370	%result = <a href="#i_mul">mul</a> i32 %X, 8
Chris Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	371	</pre>
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	372	</div>
Chris Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	373
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	374	<p>After strength reduction:</p>
Chris Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	375
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	376	<div class="doc_code">
Chris Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	377	<pre>
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	378	%result = <a href="#i_shl">shl</a> i32 %X, i8 3
Chris Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	379	</pre>
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	380	</div>
Chris Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	381
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	382	<p>And the hard way:</p>
Chris Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	383
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	384	<div class="doc_code">
Chris Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	385	<pre>
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	386	<a href="#i_add">add</a> i32 %X, %X <i>; yields {i32}:%0</i>
				387	<a href="#i_add">add</a> i32 %0, %0 <i>; yields {i32}:%1</i>
				388	%result = <a href="#i_add">add</a> i32 %1, %1
Chris Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	389	</pre>
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	390	</div>
Chris Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	391
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	392	<p>This last way of multiplying <tt>%X</tt> by 8 illustrates several
				393	important lexical features of LLVM:</p>
Chris Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	394
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	395	<ol>
Chris Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	396
				397	<li>Comments are delimited with a '<tt>;</tt>' and go until the end of
				398	line.</li>
				399
				400	<li>Unnamed temporaries are created when the result of a computation is not
				401	assigned to a named value.</li>
				402
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	403	<li>Unnamed temporaries are numbered sequentially</li>
Chris Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	404
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	405	</ol>
Chris Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	406
John Criswell	e4c57cc	2005-05-12 16:52:32 +0000	[diff] [blame]	407	<p>...and it also shows a convention that we follow in this document. When
Chris Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	408	demonstrating instructions, we will follow an instruction with a comment that
				409	defines the type and name of value produced. Comments are shown in italic
				410	text.</p>
				411
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	412	</div>
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	413
				414	<!-- *********************************************************************** -->
				415	<div class="doc_section"> <a name="highlevel">High Level Structure</a> </div>
				416	<!-- *********************************************************************** -->
				417
				418	<!-- ======================================================================= -->
				419	<div class="doc_subsection"> <a name="modulestructure">Module Structure</a>
				420	</div>
				421
				422	<div class="doc_text">
				423
				424	<p>LLVM programs are composed of "Module"s, each of which is a
				425	translation unit of the input programs. Each module consists of
				426	functions, global variables, and symbol table entries. Modules may be
				427	combined together with the LLVM linker, which merges function (and
				428	global variable) definitions, resolves forward declarations, and merges
				429	symbol table entries. Here is an example of the "hello world" module:</p>
				430
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	431	<div class="doc_code">
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	432	<pre><i>; Declare the string constant as a global constant...</i>
Chris Lattner	a89e5f1	2007-06-12 17:00:26 +0000	[diff] [blame]	433	<a href="#identifiers">@.LC0</a> = <a href="#linkage_internal">internal</a> <a
				434	href="#globalvars">constant</a> <a href="#t_array">[13 x i8]</a> c"hello world\0A\00" <i>; [13 x i8]*</i>
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	435
				436	<i>; External declaration of the puts function</i>
Chris Lattner	a89e5f1	2007-06-12 17:00:26 +0000	[diff] [blame]	437	<a href="#functionstructure">declare</a> i32 @puts(i8 ) <i>; i32(i8 )* </i>
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	438
				439	<i>; Definition of main function</i>
Chris Lattner	a89e5f1	2007-06-12 17:00:26 +0000	[diff] [blame]	440	define i32 @main() { <i>; i32()* </i>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	441	<i>; Convert [13x i8 ]* to i8 *...</i>
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	442	%cast210 = <a
Chris Lattner	6c0955b	2007-06-12 17:01:15 +0000	[diff] [blame]	443	href="#i_getelementptr">getelementptr</a> [13 x i8 ]* @.LC0, i64 0, i64 0 <i>; i8 *</i>
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	444
				445	<i>; Call puts function to write out the string to stdout...</i>
				446	<a
Chris Lattner	a89e5f1	2007-06-12 17:00:26 +0000	[diff] [blame]	447	href="#i_call">call</a> i32 @puts(i8 * %cast210) <i>; i32</i>
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	448	<a
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	449	href="#i_ret">ret</a> i32 0<br>}<br>
				450	</pre>
				451	</div>
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	452
				453	<p>This example is made up of a <a href="#globalvars">global variable</a>
				454	named "<tt>.LC0</tt>", an external declaration of the "<tt>puts</tt>"
				455	function, and a <a href="#functionstructure">function definition</a>
				456	for "<tt>main</tt>".</p>
				457
Chris Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	458	<p>In general, a module is made up of a list of global values,
				459	where both functions and global variables are global values. Global values are
				460	represented by a pointer to a memory location (in this case, a pointer to an
				461	array of char, and a pointer to a function), and have one of the following <a
				462	href="#linkage">linkage types</a>.</p>
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	463
Chris Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	464	</div>
				465
				466	<!-- ======================================================================= -->
				467	<div class="doc_subsection">
				468	<a name="linkage">Linkage Types</a>
				469	</div>
				470
				471	<div class="doc_text">
				472
				473	<p>
				474	All Global Variables and Functions have one of the following types of linkage:
				475	</p>
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	476
				477	<dl>
Chris Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	478
Dale Johannesen	2307a7f	2008-05-23 23:13:41 +0000	[diff] [blame]	479	<dt><tt><b><a name="linkage_internal">internal</a></b></tt>: </dt>
Chris Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	480
				481	<dd>Global values with internal linkage are only directly accessible by
				482	objects in the current module. In particular, linking code into a module with
				483	an internal global value may cause the internal to be renamed as necessary to
				484	avoid collisions. Because the symbol is internal to the module, all
				485	references can be updated. This corresponds to the notion of the
Chris Lattner	4887bd8	2007-01-14 06:51:48 +0000	[diff] [blame]	486	'<tt>static</tt>' keyword in C.
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	487	</dd>
Chris Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	488
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	489	<dt><tt><b><a name="linkage_linkonce">linkonce</a></b></tt>: </dt>
Chris Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	490
Chris Lattner	4887bd8	2007-01-14 06:51:48 +0000	[diff] [blame]	491	<dd>Globals with "<tt>linkonce</tt>" linkage are merged with other globals of
				492	the same name when linkage occurs. This is typically used to implement
				493	inline functions, templates, or other code which must be generated in each
				494	translation unit that uses it. Unreferenced <tt>linkonce</tt> globals are
				495	allowed to be discarded.
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	496	</dd>
Chris Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	497
Dale Johannesen	2307a7f	2008-05-23 23:13:41 +0000	[diff] [blame]	498	<dt><tt><b><a name="linkage_common">common</a></b></tt>: </dt>
				499
				500	<dd>"<tt>common</tt>" linkage is exactly the same as <tt>linkonce</tt>
				501	linkage, except that unreferenced <tt>common</tt> globals may not be
				502	discarded. This is used for globals that may be emitted in multiple
				503	translation units, but that are not guaranteed to be emitted into every
				504	translation unit that uses them. One example of this is tentative
				505	definitions in C, such as "<tt>int X;</tt>" at global scope.
				506	</dd>
				507
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	508	<dt><tt><b><a name="linkage_weak">weak</a></b></tt>: </dt>
Chris Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	509
Dale Johannesen	2307a7f	2008-05-23 23:13:41 +0000	[diff] [blame]	510	<dd>"<tt>weak</tt>" linkage is the same as <tt>common</tt> linkage, except
				511	that some targets may choose to emit different assembly sequences for them
				512	for target-dependent reasons. This is used for globals that are declared
				513	"weak" in C source code.
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	514	</dd>
Chris Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	515
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	516	<dt><tt><b><a name="linkage_appending">appending</a></b></tt>: </dt>
Chris Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	517
				518	<dd>"<tt>appending</tt>" linkage may only be applied to global variables of
				519	pointer to array type. When two global variables with appending linkage are
				520	linked together, the two global arrays are appended together. This is the
				521	LLVM, typesafe, equivalent of having the system linker append together
				522	"sections" with identical names when .o files are linked.
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	523	</dd>
Chris Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	524
Anton Korobeynikov	7f70559	2007-01-12 19:20:47 +0000	[diff] [blame]	525	<dt><tt><b><a name="linkage_externweak">extern_weak</a></b></tt>: </dt>
Chris Lattner	d3eda89	2008-08-05 18:29:16 +0000	[diff] [blame]	526	<dd>The semantics of this linkage follow the ELF object file model: the
				527	symbol is weak until linked, if not linked, the symbol becomes null instead
				528	of being an undefined reference.
Anton Korobeynikov	7f70559	2007-01-12 19:20:47 +0000	[diff] [blame]	529	</dd>
Anton Korobeynikov	7f70559	2007-01-12 19:20:47 +0000	[diff] [blame]	530
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	531	<dt><tt><b><a name="linkage_external">externally visible</a></b></tt>:</dt>
Chris Lattner	e5d947b	2004-12-09 16:36:40 +0000	[diff] [blame]	532
				533	<dd>If none of the above identifiers are used, the global is externally
				534	visible, meaning that it participates in linkage and can be used to resolve
				535	external symbol references.
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	536	</dd>
Reid Spencer	c891084	2007-04-11 23:49:50 +0000	[diff] [blame]	537	</dl>
Anton Korobeynikov	b74ed07	2006-09-14 18:23:27 +0000	[diff] [blame]	538
Anton Korobeynikov	b74ed07	2006-09-14 18:23:27 +0000	[diff] [blame]	539	<p>
				540	The next two types of linkage are targeted for Microsoft Windows platform
				541	only. They are designed to support importing (exporting) symbols from (to)
Chris Lattner	d3eda89	2008-08-05 18:29:16 +0000	[diff] [blame]	542	DLLs (Dynamic Link Libraries).
Anton Korobeynikov	b74ed07	2006-09-14 18:23:27 +0000	[diff] [blame]	543	</p>
				544
Anton Korobeynikov	7f70559	2007-01-12 19:20:47 +0000	[diff] [blame]	545	<dl>
Anton Korobeynikov	b74ed07	2006-09-14 18:23:27 +0000	[diff] [blame]	546	<dt><tt><b><a name="linkage_dllimport">dllimport</a></b></tt>: </dt>
				547
				548	<dd>"<tt>dllimport</tt>" linkage causes the compiler to reference a function
				549	or variable via a global pointer to a pointer that is set up by the DLL
				550	exporting the symbol. On Microsoft Windows targets, the pointer name is
				551	formed by combining <code>_imp__</code> and the function or variable name.
				552	</dd>
				553
				554	<dt><tt><b><a name="linkage_dllexport">dllexport</a></b></tt>: </dt>
				555
				556	<dd>"<tt>dllexport</tt>" linkage causes the compiler to provide a global
				557	pointer to a pointer in a DLL, so that it can be referenced with the
				558	<tt>dllimport</tt> attribute. On Microsoft Windows targets, the pointer
				559	name is formed by combining <code>_imp__</code> and the function or variable
				560	name.
				561	</dd>
				562
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	563	</dl>
				564
Anton Korobeynikov	7f70559	2007-01-12 19:20:47 +0000	[diff] [blame]	565	<p><a name="linkage_external"></a>For example, since the "<tt>.LC0</tt>"
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	566	variable is defined to be internal, if another module defined a "<tt>.LC0</tt>"
				567	variable and was linked with this one, one of the two would be renamed,
				568	preventing a collision. Since "<tt>main</tt>" and "<tt>puts</tt>" are
				569	external (i.e., lacking any linkage declarations), they are accessible
Reid Spencer	ac8d276	2007-01-05 00:59:10 +0000	[diff] [blame]	570	outside of the current module.</p>
				571	<p>It is illegal for a function <i>declaration</i>
				572	to have any linkage type other than "externally visible", <tt>dllimport</tt>,
Anton Korobeynikov	7f70559	2007-01-12 19:20:47 +0000	[diff] [blame]	573	or <tt>extern_weak</tt>.</p>
Anton Korobeynikov	8b0a8c8	2007-04-25 14:27:10 +0000	[diff] [blame]	574	<p>Aliases can have only <tt>external</tt>, <tt>internal</tt> and <tt>weak</tt>
				575	linkages.
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	576	</div>
				577
				578	<!-- ======================================================================= -->
				579	<div class="doc_subsection">
Chris Lattner	bad10ee	2005-05-06 22:57:40 +0000	[diff] [blame]	580	<a name="callingconv">Calling Conventions</a>
				581	</div>
				582
				583	<div class="doc_text">
				584
				585	<p>LLVM <a href="#functionstructure">functions</a>, <a href="#i_call">calls</a>
				586	and <a href="#i_invoke">invokes</a> can all have an optional calling convention
				587	specified for the call. The calling convention of any pair of dynamic
				588	caller/callee must match, or the behavior of the program is undefined. The
				589	following calling conventions are supported by LLVM, and more may be added in
				590	the future:</p>
				591
				592	<dl>
				593	<dt><b>"<tt>ccc</tt>" - The C calling convention</b>:</dt>
				594
				595	<dd>This calling convention (the default if no other calling convention is
				596	specified) matches the target C calling conventions. This calling convention
John Criswell	e4c57cc	2005-05-12 16:52:32 +0000	[diff] [blame]	597	supports varargs function calls and tolerates some mismatch in the declared
Reid Spencer	c28d2bc	2006-12-31 21:30:18 +0000	[diff] [blame]	598	prototype and implemented declaration of the function (as does normal C).
Chris Lattner	bad10ee	2005-05-06 22:57:40 +0000	[diff] [blame]	599	</dd>
				600
				601	<dt><b>"<tt>fastcc</tt>" - The fast calling convention</b>:</dt>
				602
				603	<dd>This calling convention attempts to make calls as fast as possible
				604	(e.g. by passing things in registers). This calling convention allows the
				605	target to use whatever tricks it wants to produce fast code for the target,
Chris Lattner	d3eda89	2008-08-05 18:29:16 +0000	[diff] [blame]	606	without having to conform to an externally specified ABI (Application Binary
				607	Interface). Implementations of this convention should allow arbitrary
Arnold Schwaighofer	9097d14	2008-05-14 09:17:12 +0000	[diff] [blame]	608	<a href="CodeGenerator.html#tailcallopt">tail call optimization</a> to be
				609	supported. This calling convention does not support varargs and requires the
				610	prototype of all callees to exactly match the prototype of the function
				611	definition.
Chris Lattner	bad10ee	2005-05-06 22:57:40 +0000	[diff] [blame]	612	</dd>
				613
				614	<dt><b>"<tt>coldcc</tt>" - The cold calling convention</b>:</dt>
				615
				616	<dd>This calling convention attempts to make code in the caller as efficient
				617	as possible under the assumption that the call is not commonly executed. As
				618	such, these calls often preserve all registers so that the call does not break
				619	any live ranges in the caller side. This calling convention does not support
				620	varargs and requires the prototype of all callees to exactly match the
				621	prototype of the function definition.
				622	</dd>
				623
Chris Lattner	cfe6b37	2005-05-07 01:46:40 +0000	[diff] [blame]	624	<dt><b>"<tt>cc <<em>n</em>></tt>" - Numbered convention</b>:</dt>
Chris Lattner	bad10ee	2005-05-06 22:57:40 +0000	[diff] [blame]	625
				626	<dd>Any calling convention may be specified by number, allowing
				627	target-specific calling conventions to be used. Target specific calling
				628	conventions start at 64.
				629	</dd>
Chris Lattner	cfe6b37	2005-05-07 01:46:40 +0000	[diff] [blame]	630	</dl>
Chris Lattner	bad10ee	2005-05-06 22:57:40 +0000	[diff] [blame]	631
				632	<p>More calling conventions can be added/defined on an as-needed basis, to
				633	support pascal conventions or any other well-known target-independent
				634	convention.</p>
				635
				636	</div>
				637
				638	<!-- ======================================================================= -->
				639	<div class="doc_subsection">
Anton Korobeynikov	8cea37b	2007-01-23 12:35:46 +0000	[diff] [blame]	640	<a name="visibility">Visibility Styles</a>
				641	</div>
				642
				643	<div class="doc_text">
				644
				645	<p>
				646	All Global Variables and Functions have one of the following visibility styles:
				647	</p>
				648
				649	<dl>
				650	<dt><b>"<tt>default</tt>" - Default style</b>:</dt>
				651
Chris Lattner	d3eda89	2008-08-05 18:29:16 +0000	[diff] [blame]	652	<dd>On targets that use the ELF object file format, default visibility means
				653	that the declaration is visible to other
Anton Korobeynikov	8cea37b	2007-01-23 12:35:46 +0000	[diff] [blame]	654	modules and, in shared libraries, means that the declared entity may be
				655	overridden. On Darwin, default visibility means that the declaration is
				656	visible to other modules. Default visibility corresponds to "external
				657	linkage" in the language.
				658	</dd>
				659
				660	<dt><b>"<tt>hidden</tt>" - Hidden style</b>:</dt>
				661
				662	<dd>Two declarations of an object with hidden visibility refer to the same
				663	object if they are in the same shared object. Usually, hidden visibility
				664	indicates that the symbol will not be placed into the dynamic symbol table,
				665	so no other module (executable or shared library) can reference it
				666	directly.
				667	</dd>
				668
Anton Korobeynikov	6f9896f	2007-04-29 18:35:00 +0000	[diff] [blame]	669	<dt><b>"<tt>protected</tt>" - Protected style</b>:</dt>
				670
				671	<dd>On ELF, protected visibility indicates that the symbol will be placed in
				672	the dynamic symbol table, but that references within the defining module will
				673	bind to the local symbol. That is, the symbol cannot be overridden by another
				674	module.
				675	</dd>
Anton Korobeynikov	8cea37b	2007-01-23 12:35:46 +0000	[diff] [blame]	676	</dl>
				677
				678	</div>
				679
				680	<!-- ======================================================================= -->
				681	<div class="doc_subsection">
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	682	<a name="globalvars">Global Variables</a>
				683	</div>
				684
				685	<div class="doc_text">
				686
Chris Lattner	3689a34	2005-02-12 19:30:21 +0000	[diff] [blame]	687	<p>Global variables define regions of memory allocated at compilation time
Chris Lattner	88f6c46	2005-11-12 00:45:07 +0000	[diff] [blame]	688	instead of run-time. Global variables may optionally be initialized, may have
Anton Korobeynikov	8b0a8c8	2007-04-25 14:27:10 +0000	[diff] [blame]	689	an explicit section to be placed in, and may have an optional explicit alignment
				690	specified. A variable may be defined as "thread_local", which means that it
				691	will not be shared by threads (each thread will have a separated copy of the
				692	variable). A variable may be defined as a global "constant," which indicates
				693	that the contents of the variable will <b>never</b> be modified (enabling better
Chris Lattner	3689a34	2005-02-12 19:30:21 +0000	[diff] [blame]	694	optimization, allowing the global data to be placed in the read-only section of
				695	an executable, etc). Note that variables that need runtime initialization
John Criswell	0ec250c	2005-10-24 16:17:18 +0000	[diff] [blame]	696	cannot be marked "constant" as there is a store to the variable.</p>
Chris Lattner	3689a34	2005-02-12 19:30:21 +0000	[diff] [blame]	697
				698	<p>
				699	LLVM explicitly allows <em>declarations</em> of global variables to be marked
				700	constant, even if the final definition of the global is not. This capability
				701	can be used to enable slightly better optimization of the program, but requires
				702	the language definition to guarantee that optimizations based on the
				703	'constantness' are valid for the translation units that do not include the
				704	definition.
				705	</p>
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	706
				707	<p>As SSA values, global variables define pointer values that are in
				708	scope (i.e. they dominate) all basic blocks in the program. Global
				709	variables always define a pointer to their "content" type because they
				710	describe a region of memory, and all memory objects in LLVM are
				711	accessed through pointers.</p>
				712
Christopher Lamb	284d992	2007-12-11 09:31:00 +0000	[diff] [blame]	713	<p>A global variable may be declared to reside in a target-specifc numbered
				714	address space. For targets that support them, address spaces may affect how
				715	optimizations are performed and/or what target instructions are used to access
Christopher Lamb	d49e18d	2007-12-12 08:44:39 +0000	[diff] [blame]	716	the variable. The default address space is zero. The address space qualifier
				717	must precede any other attributes.</p>
Christopher Lamb	284d992	2007-12-11 09:31:00 +0000	[diff] [blame]	718
Chris Lattner	88f6c46	2005-11-12 00:45:07 +0000	[diff] [blame]	719	<p>LLVM allows an explicit section to be specified for globals. If the target
				720	supports it, it will emit globals to the section specified.</p>
				721
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	722	<p>An explicit alignment may be specified for a global. If not present, or if
				723	the alignment is set to zero, the alignment of the global is set by the target
				724	to whatever it feels convenient. If an explicit alignment is specified, the
				725	global is forced to have at least that much alignment. All alignments must be
				726	a power of 2.</p>
				727
Christopher Lamb	284d992	2007-12-11 09:31:00 +0000	[diff] [blame]	728	<p>For example, the following defines a global in a numbered address space with
				729	an initializer, section, and alignment:</p>
Chris Lattner	68027ea	2007-01-14 00:27:09 +0000	[diff] [blame]	730
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	731	<div class="doc_code">
Chris Lattner	68027ea	2007-01-14 00:27:09 +0000	[diff] [blame]	732	<pre>
Christopher Lamb	284d992	2007-12-11 09:31:00 +0000	[diff] [blame]	733	@G = constant float 1.0 addrspace(5), section "foo", align 4
Chris Lattner	68027ea	2007-01-14 00:27:09 +0000	[diff] [blame]	734	</pre>
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	735	</div>
Chris Lattner	68027ea	2007-01-14 00:27:09 +0000	[diff] [blame]	736
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	737	</div>
				738
				739
				740	<!-- ======================================================================= -->
				741	<div class="doc_subsection">
				742	<a name="functionstructure">Functions</a>
				743	</div>
				744
				745	<div class="doc_text">
				746
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	747	<p>LLVM function definitions consist of the "<tt>define</tt>" keyord,
				748	an optional <a href="#linkage">linkage type</a>, an optional
Anton Korobeynikov	8cea37b	2007-01-23 12:35:46 +0000	[diff] [blame]	749	<a href="#visibility">visibility style</a>, an optional
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	750	<a href="#callingconv">calling convention</a>, a return type, an optional
				751	<a href="#paramattrs">parameter attribute</a> for the return type, a function
				752	name, a (possibly empty) argument list (each with optional
Anton Korobeynikov	8cea37b	2007-01-23 12:35:46 +0000	[diff] [blame]	753	<a href="#paramattrs">parameter attributes</a>), an optional section, an
Devang Patel	f8b9481	2008-09-04 23:05:13 +0000	[diff] [blame]	754	optional alignment, an optional <a href="#gc">garbage collector name</a>,
				755	an optional <a href="#notes">function notes</a>, an
Gordon Henriksen	80a75bf	2007-12-10 03:18:06 +0000	[diff] [blame]	756	opening curly brace, a list of basic blocks, and a closing curly brace.
Anton Korobeynikov	8cea37b	2007-01-23 12:35:46 +0000	[diff] [blame]	757
				758	LLVM function declarations consist of the "<tt>declare</tt>" keyword, an
				759	optional <a href="#linkage">linkage type</a>, an optional
				760	<a href="#visibility">visibility style</a>, an optional
				761	<a href="#callingconv">calling convention</a>, a return type, an optional
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	762	<a href="#paramattrs">parameter attribute</a> for the return type, a function
Gordon Henriksen	80a75bf	2007-12-10 03:18:06 +0000	[diff] [blame]	763	name, a possibly empty list of arguments, an optional alignment, and an optional
Gordon Henriksen	e754abe	2007-12-10 03:30:21 +0000	[diff] [blame]	764	<a href="#gc">garbage collector name</a>.</p>
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	765
Chris Lattner	d3eda89	2008-08-05 18:29:16 +0000	[diff] [blame]	766	<p>A function definition contains a list of basic blocks, forming the CFG
				767	(Control Flow Graph) for
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	768	the function. Each basic block may optionally start with a label (giving the
				769	basic block a symbol table entry), contains a list of instructions, and ends
				770	with a <a href="#terminators">terminator</a> instruction (such as a branch or
				771	function return).</p>
				772
Chris Lattner	4a3c901	2007-06-08 16:52:14 +0000	[diff] [blame]	773	<p>The first basic block in a function is special in two ways: it is immediately
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	774	executed on entrance to the function, and it is not allowed to have predecessor
				775	basic blocks (i.e. there can not be any branches to the entry block of a
				776	function). Because the block can have no predecessors, it also cannot have any
				777	<a href="#i_phi">PHI nodes</a>.</p>
				778
Chris Lattner	88f6c46	2005-11-12 00:45:07 +0000	[diff] [blame]	779	<p>LLVM allows an explicit section to be specified for functions. If the target
				780	supports it, it will emit functions to the section specified.</p>
				781
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	782	<p>An explicit alignment may be specified for a function. If not present, or if
				783	the alignment is set to zero, the alignment of the function is set by the target
				784	to whatever it feels convenient. If an explicit alignment is specified, the
				785	function is forced to have at least that much alignment. All alignments must be
				786	a power of 2.</p>
				787
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	788	</div>
				789
Anton Korobeynikov	8b0a8c8	2007-04-25 14:27:10 +0000	[diff] [blame]	790
				791	<!-- ======================================================================= -->
				792	<div class="doc_subsection">
				793	<a name="aliasstructure">Aliases</a>
				794	</div>
				795	<div class="doc_text">
				796	<p>Aliases act as "second name" for the aliasee value (which can be either
Anton Korobeynikov	726d45c	2008-03-22 08:36:14 +0000	[diff] [blame]	797	function, global variable, another alias or bitcast of global value). Aliases
				798	may have an optional <a href="#linkage">linkage type</a>, and an
Anton Korobeynikov	8b0a8c8	2007-04-25 14:27:10 +0000	[diff] [blame]	799	optional <a href="#visibility">visibility style</a>.</p>
				800
				801	<h5>Syntax:</h5>
				802
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	803	<div class="doc_code">
Bill Wendling	aac388b	2007-05-29 09:42:13 +0000	[diff] [blame]	804	<pre>
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	805	@<Name> = [Linkage] [Visibility] alias <AliaseeTy> @<Aliasee>
Bill Wendling	aac388b	2007-05-29 09:42:13 +0000	[diff] [blame]	806	</pre>
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	807	</div>
Anton Korobeynikov	8b0a8c8	2007-04-25 14:27:10 +0000	[diff] [blame]	808
				809	</div>
				810
				811
				812
Chris Lattner	4e9aba7	2006-01-23 23:23:47 +0000	[diff] [blame]	813	<!-- ======================================================================= -->
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	814	<div class="doc_subsection"><a name="paramattrs">Parameter Attributes</a></div>
				815	<div class="doc_text">
				816	<p>The return type and each parameter of a function type may have a set of
				817	<i>parameter attributes</i> associated with them. Parameter attributes are
				818	used to communicate additional information about the result or parameters of
Duncan Sands	dc02467	2007-11-27 13:23:08 +0000	[diff] [blame]	819	a function. Parameter attributes are considered to be part of the function,
				820	not of the function type, so functions with different parameter attributes
				821	can have the same function type.</p>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	822
Reid Spencer	950e9f8	2007-01-15 18:27:39 +0000	[diff] [blame]	823	<p>Parameter attributes are simple keywords that follow the type specified. If
				824	multiple parameter attributes are needed, they are space separated. For
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	825	example:</p>
				826
				827	<div class="doc_code">
				828	<pre>
Duncan Sands	dc02467	2007-11-27 13:23:08 +0000	[diff] [blame]	829	declare i32 @printf(i8* noalias , ...) nounwind
				830	declare i32 @atoi(i8*) nounwind readonly
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	831	</pre>
				832	</div>
				833
Duncan Sands	dc02467	2007-11-27 13:23:08 +0000	[diff] [blame]	834	<p>Note that any attributes for the function result (<tt>nounwind</tt>,
				835	<tt>readonly</tt>) come immediately after the argument list.</p>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	836
Anton Korobeynikov	7f70559	2007-01-12 19:20:47 +0000	[diff] [blame]	837	<p>Currently, only the following parameter attributes are defined:</p>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	838	<dl>
Reid Spencer	9445e9a	2007-07-19 23:13:04 +0000	[diff] [blame]	839	<dt><tt>zeroext</tt></dt>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	840	<dd>This indicates that the parameter should be zero extended just before
				841	a call to this function.</dd>
Chris Lattner	47507de	2008-01-11 06:20:47 +0000	[diff] [blame]	842
Reid Spencer	9445e9a	2007-07-19 23:13:04 +0000	[diff] [blame]	843	<dt><tt>signext</tt></dt>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	844	<dd>This indicates that the parameter should be sign extended just before
				845	a call to this function.</dd>
Chris Lattner	47507de	2008-01-11 06:20:47 +0000	[diff] [blame]	846
Anton Korobeynikov	34d6dea	2007-01-28 14:30:45 +0000	[diff] [blame]	847	<dt><tt>inreg</tt></dt>
				848	<dd>This indicates that the parameter should be placed in register (if
Anton Korobeynikov	66a8c8c	2007-01-28 15:27:21 +0000	[diff] [blame]	849	possible) during assembling function call. Support for this attribute is
				850	target-specific</dd>
Chris Lattner	47507de	2008-01-11 06:20:47 +0000	[diff] [blame]	851
				852	<dt><tt>byval</tt></dt>
Chris Lattner	0747baa	2008-01-15 04:34:22 +0000	[diff] [blame]	853	<dd>This indicates that the pointer parameter should really be passed by
				854	value to the function. The attribute implies that a hidden copy of the
				855	pointee is made between the caller and the callee, so the callee is unable
Chris Lattner	ebec678	2008-08-05 18:21:08 +0000	[diff] [blame]	856	to modify the value in the callee. This attribute is only valid on LLVM
Chris Lattner	0747baa	2008-01-15 04:34:22 +0000	[diff] [blame]	857	pointer arguments. It is generally used to pass structs and arrays by
				858	value, but is also valid on scalars (even though this is silly).</dd>
Chris Lattner	47507de	2008-01-11 06:20:47 +0000	[diff] [blame]	859
Anton Korobeynikov	34d6dea	2007-01-28 14:30:45 +0000	[diff] [blame]	860	<dt><tt>sret</tt></dt>
Duncan Sands	e26dec6	2008-02-18 04:19:38 +0000	[diff] [blame]	861	<dd>This indicates that the pointer parameter specifies the address of a
				862	structure that is the return value of the function in the source program.
Duncan Sands	b7f0c08	2008-03-17 12:17:41 +0000	[diff] [blame]	863	Loads and stores to the structure are assumed not to trap.
Duncan Sands	e26dec6	2008-02-18 04:19:38 +0000	[diff] [blame]	864	May only be applied to the first parameter.</dd>
Chris Lattner	47507de	2008-01-11 06:20:47 +0000	[diff] [blame]	865
Zhou Sheng	febca34	2007-06-05 05:28:26 +0000	[diff] [blame]	866	<dt><tt>noalias</tt></dt>
Owen Anderson	117bbd3	2008-02-18 04:09:01 +0000	[diff] [blame]	867	<dd>This indicates that the parameter does not alias any global or any other
				868	parameter. The caller is responsible for ensuring that this is the case,
				869	usually by placing the value in a stack allocation.</dd>
Chris Lattner	47507de	2008-01-11 06:20:47 +0000	[diff] [blame]	870
Reid Spencer	2dc5201	2007-03-22 02:18:56 +0000	[diff] [blame]	871	<dt><tt>noreturn</tt></dt>
				872	<dd>This function attribute indicates that the function never returns. This
				873	indicates to LLVM that every call to this function should be treated as if
				874	an <tt>unreachable</tt> instruction immediately followed the call.</dd>
Chris Lattner	47507de	2008-01-11 06:20:47 +0000	[diff] [blame]	875
Reid Spencer	6760612	2007-03-22 02:02:11 +0000	[diff] [blame]	876	<dt><tt>nounwind</tt></dt>
Duncan Sands	b7f0c08	2008-03-17 12:17:41 +0000	[diff] [blame]	877	<dd>This function attribute indicates that no exceptions unwind out of the
				878	function. Usually this is because the function makes no use of exceptions,
				879	but it may also be that the function catches any exceptions thrown when
				880	executing it.</dd>
				881
Duncan Sands	50f19f5	2007-07-27 19:57:41 +0000	[diff] [blame]	882	<dt><tt>nest</tt></dt>
Duncan Sands	0789b8b	2008-07-08 09:27:25 +0000	[diff] [blame]	883	<dd>This indicates that the pointer parameter can be excised using the
Duncan Sands	50f19f5	2007-07-27 19:57:41 +0000	[diff] [blame]	884	<a href="#int_trampoline">trampoline intrinsics</a>.</dd>
Duncan Sands	ed4a2f1	2007-11-22 20:23:04 +0000	[diff] [blame]	885	<dt><tt>readonly</tt></dt>
Duncan Sands	f04d584	2007-11-14 21:14:02 +0000	[diff] [blame]	886	<dd>This function attribute indicates that the function has no side-effects
Duncan Sands	ed4a2f1	2007-11-22 20:23:04 +0000	[diff] [blame]	887	except for producing a return value or throwing an exception. The value
				888	returned must only depend on the function arguments and/or global variables.
				889	It may use values obtained by dereferencing pointers.</dd>
				890	<dt><tt>readnone</tt></dt>
				891	<dd>A <tt>readnone</tt> function has the same restrictions as a <tt>readonly</tt>
Duncan Sands	f04d584	2007-11-14 21:14:02 +0000	[diff] [blame]	892	function, but in addition it is not allowed to dereference any pointer arguments
				893	or global variables.
Anton Korobeynikov	7f70559	2007-01-12 19:20:47 +0000	[diff] [blame]	894	</dl>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	895
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	896	</div>
				897
				898	<!-- ======================================================================= -->
Chris Lattner	4e9aba7	2006-01-23 23:23:47 +0000	[diff] [blame]	899	<div class="doc_subsection">
Gordon Henriksen	80a75bf	2007-12-10 03:18:06 +0000	[diff] [blame]	900	<a name="gc">Garbage Collector Names</a>
				901	</div>
				902
				903	<div class="doc_text">
				904	<p>Each function may specify a garbage collector name, which is simply a
				905	string.</p>
				906
				907	<div class="doc_code"><pre
				908	>define void @f() gc "name" { ...</pre></div>
				909
				910	<p>The compiler declares the supported values of <i>name</i>. Specifying a
				911	collector which will cause the compiler to alter its output in order to support
				912	the named garbage collection algorithm.</p>
				913	</div>
				914
				915	<!-- ======================================================================= -->
				916	<div class="doc_subsection">
Devang Patel	f8b9481	2008-09-04 23:05:13 +0000	[diff] [blame]	917	<a name="notes">Function Notes</a>
				918	</div>
				919
				920	<div class="doc_text">
Devang Patel	cdc0669	2008-09-04 23:10:26 +0000	[diff] [blame]	921	<p>The function definition may list function notes which are used by
				922	various passes.</p>
Devang Patel	f8b9481	2008-09-04 23:05:13 +0000	[diff] [blame]	923
				924	<div class="doc_code">
Bill Wendling	e36dccc	2008-09-07 10:26:33 +0000	[diff] [blame]	925	<pre>
				926	define void @f() notes(inline=Always) { ... }
				927	define void @f() notes(inline=Always,opt-size) { ... }
				928	define void @f() notes(inline=Never,opt-size) { ... }
				929	define void @f() notes(opt-size) { ... }
				930	</pre>
Devang Patel	f8b9481	2008-09-04 23:05:13 +0000	[diff] [blame]	931	</div>
				932
Bill Wendling	e36dccc	2008-09-07 10:26:33 +0000	[diff] [blame]	933	<dl>
				934	<dt><tt>inline=Always</tt></dt>
				935	<dd>This note requests inliner to inline this function irrespective of inlining
				936	size threshold for this function.</dd>
				937
				938	<dt><tt>inline=Never</tt></dt>
				939	<dd>This note requests inliner to never inline this function in any situation.
				940	This note may not be used together with <tt>inline=Always</tt> note.</dd>
				941
				942	<dt><tt>opt-size</tt></dt>
				943	<dd>This note suggests optimization passes and code generator passes to make
				944	choices that help reduce code size.</dd>
				945
				946	</dl>
				947
				948	<p>Any notes that are not documented here are considered invalid notes.</p>
Devang Patel	f8b9481	2008-09-04 23:05:13 +0000	[diff] [blame]	949	</div>
				950
				951	<!-- ======================================================================= -->
				952	<div class="doc_subsection">
Chris Lattner	1eeeb0c	2006-04-08 04:40:53 +0000	[diff] [blame]	953	<a name="moduleasm">Module-Level Inline Assembly</a>
Chris Lattner	4e9aba7	2006-01-23 23:23:47 +0000	[diff] [blame]	954	</div>
				955
				956	<div class="doc_text">
				957	<p>
				958	Modules may contain "module-level inline asm" blocks, which corresponds to the
				959	GCC "file scope inline asm" blocks. These blocks are internally concatenated by
				960	LLVM and treated as a single unit, but may be separated in the .ll file if
				961	desired. The syntax is very simple:
				962	</p>
				963
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	964	<div class="doc_code">
				965	<pre>
				966	module asm "inline asm code goes here"
				967	module asm "more can go here"
				968	</pre>
				969	</div>
Chris Lattner	4e9aba7	2006-01-23 23:23:47 +0000	[diff] [blame]	970
				971	<p>The strings can contain any character by escaping non-printable characters.
				972	The escape sequence used is simply "\xx" where "xx" is the two digit hex code
				973	for the number.
				974	</p>
				975
				976	<p>
				977	The inline asm code is simply printed to the machine code .s file when
				978	assembly code is generated.
				979	</p>
				980	</div>
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	981
Reid Spencer	de15194	2007-02-19 23:54:10 +0000	[diff] [blame]	982	<!-- ======================================================================= -->
				983	<div class="doc_subsection">
				984	<a name="datalayout">Data Layout</a>
				985	</div>
				986
				987	<div class="doc_text">
				988	<p>A module may specify a target specific data layout string that specifies how
Reid Spencer	c891084	2007-04-11 23:49:50 +0000	[diff] [blame]	989	data is to be laid out in memory. The syntax for the data layout is simply:</p>
				990	<pre> target datalayout = "<i>layout specification</i>"</pre>
				991	<p>The <i>layout specification</i> consists of a list of specifications
				992	separated by the minus sign character ('-'). Each specification starts with a
				993	letter and may include other information after the letter to define some
				994	aspect of the data layout. The specifications accepted are as follows: </p>
Reid Spencer	de15194	2007-02-19 23:54:10 +0000	[diff] [blame]	995	<dl>
				996	<dt><tt>E</tt></dt>
				997	<dd>Specifies that the target lays out data in big-endian form. That is, the
				998	bits with the most significance have the lowest address location.</dd>
				999	<dt><tt>e</tt></dt>
Chris Lattner	d3eda89	2008-08-05 18:29:16 +0000	[diff] [blame]	1000	<dd>Specifies that the target lays out data in little-endian form. That is,
Reid Spencer	de15194	2007-02-19 23:54:10 +0000	[diff] [blame]	1001	the bits with the least significance have the lowest address location.</dd>
				1002	<dt><tt>p:<i>size</i>:<i>abi</i>:<i>pref</i></tt></dt>
				1003	<dd>This specifies the <i>size</i> of a pointer and its <i>abi</i> and
				1004	<i>preferred</i> alignments. All sizes are in bits. Specifying the <i>pref</i>
				1005	alignment is optional. If omitted, the preceding <tt>:</tt> should be omitted
				1006	too.</dd>
				1007	<dt><tt>i<i>size</i>:<i>abi</i>:<i>pref</i></tt></dt>
				1008	<dd>This specifies the alignment for an integer type of a given bit
				1009	<i>size</i>. The value of <i>size</i> must be in the range [1,2^23).</dd>
				1010	<dt><tt>v<i>size</i>:<i>abi</i>:<i>pref</i></tt></dt>
				1011	<dd>This specifies the alignment for a vector type of a given bit
				1012	<i>size</i>.</dd>
				1013	<dt><tt>f<i>size</i>:<i>abi</i>:<i>pref</i></tt></dt>
				1014	<dd>This specifies the alignment for a floating point type of a given bit
				1015	<i>size</i>. The value of <i>size</i> must be either 32 (float) or 64
				1016	(double).</dd>
				1017	<dt><tt>a<i>size</i>:<i>abi</i>:<i>pref</i></tt></dt>
				1018	<dd>This specifies the alignment for an aggregate type of a given bit
				1019	<i>size</i>.</dd>
				1020	</dl>
				1021	<p>When constructing the data layout for a given target, LLVM starts with a
				1022	default set of specifications which are then (possibly) overriden by the
				1023	specifications in the <tt>datalayout</tt> keyword. The default specifications
				1024	are given in this list:</p>
				1025	<ul>
				1026	<li><tt>E</tt> - big endian</li>
				1027	<li><tt>p:32:64:64</tt> - 32-bit pointers with 64-bit alignment</li>
				1028	<li><tt>i1:8:8</tt> - i1 is 8-bit (byte) aligned</li>
				1029	<li><tt>i8:8:8</tt> - i8 is 8-bit (byte) aligned</li>
				1030	<li><tt>i16:16:16</tt> - i16 is 16-bit aligned</li>
				1031	<li><tt>i32:32:32</tt> - i32 is 32-bit aligned</li>
Chris Lattner	d3eda89	2008-08-05 18:29:16 +0000	[diff] [blame]	1032	<li><tt>i64:32:64</tt> - i64 has ABI alignment of 32-bits but preferred
Reid Spencer	de15194	2007-02-19 23:54:10 +0000	[diff] [blame]	1033	alignment of 64-bits</li>
				1034	<li><tt>f32:32:32</tt> - float is 32-bit aligned</li>
				1035	<li><tt>f64:64:64</tt> - double is 64-bit aligned</li>
				1036	<li><tt>v64:64:64</tt> - 64-bit vector is 64-bit aligned</li>
				1037	<li><tt>v128:128:128</tt> - 128-bit vector is 128-bit aligned</li>
				1038	<li><tt>a0:0:1</tt> - aggregates are 8-bit aligned</li>
				1039	</ul>
Chris Lattner	ebec678	2008-08-05 18:21:08 +0000	[diff] [blame]	1040	<p>When LLVM is determining the alignment for a given type, it uses the
Reid Spencer	de15194	2007-02-19 23:54:10 +0000	[diff] [blame]	1041	following rules:
				1042	<ol>
				1043	<li>If the type sought is an exact match for one of the specifications, that
				1044	specification is used.</li>
				1045	<li>If no match is found, and the type sought is an integer type, then the
				1046	smallest integer type that is larger than the bitwidth of the sought type is
				1047	used. If none of the specifications are larger than the bitwidth then the the
				1048	largest integer type is used. For example, given the default specifications
				1049	above, the i7 type will use the alignment of i8 (next largest) while both
				1050	i65 and i256 will use the alignment of i64 (largest specified).</li>
				1051	<li>If no match is found, and the type sought is a vector type, then the
				1052	largest vector type that is smaller than the sought vector type will be used
				1053	as a fall back. This happens because <128 x double> can be implemented in
				1054	terms of 64 <2 x double>, for example.</li>
				1055	</ol>
				1056	</div>
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	1057
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1058	<!-- *********************************************************************** -->
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1059	<div class="doc_section"> <a name="typesystem">Type System</a> </div>
				1060	<!-- *********************************************************************** -->
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	1061
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	1062	<div class="doc_text">
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	1063
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	1064	<p>The LLVM type system is one of the most important features of the
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1065	intermediate representation. Being typed enables a number of
Chris Lattner	d3eda89	2008-08-05 18:29:16 +0000	[diff] [blame]	1066	optimizations to be performed on the intermediate representation directly,
				1067	without having to do
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1068	extra analyses on the side before the transformation. A strong type
				1069	system makes it easier to read the generated code and enables novel
				1070	analyses and transformations that are not feasible to perform on normal
				1071	three address code representations.</p>
Chris Lattner	fa73021	2004-12-09 16:11:40 +0000	[diff] [blame]	1072
				1073	</div>
				1074
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1075	<!-- ======================================================================= -->
Chris Lattner	4f69f46	2008-01-04 04:32:38 +0000	[diff] [blame]	1076	<div class="doc_subsection"> <a name="t_classifications">Type
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1077	Classifications</a> </div>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	1078	<div class="doc_text">
Chris Lattner	4f69f46	2008-01-04 04:32:38 +0000	[diff] [blame]	1079	<p>The types fall into a few useful
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1080	classifications:</p>
Misha Brukman	daa4cb0	2004-03-01 17:47:27 +0000	[diff] [blame]	1081
				1082	<table border="1" cellspacing="0" cellpadding="4">
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1083	<tbody>
Reid Spencer	d3f876c	2004-11-01 08:19:36 +0000	[diff] [blame]	1084	<tr><th>Classification</th><th>Types</th></tr>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1085	<tr>
Chris Lattner	4f69f46	2008-01-04 04:32:38 +0000	[diff] [blame]	1086	<td><a href="#t_integer">integer</a></td>
Reid Spencer	2b91631	2007-05-16 18:44:01 +0000	[diff] [blame]	1087	<td><tt>i1, i2, i3, ... i8, ... i16, ... i32, ... i64, ... </tt></td>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1088	</tr>
				1089	<tr>
Chris Lattner	4f69f46	2008-01-04 04:32:38 +0000	[diff] [blame]	1090	<td><a href="#t_floating">floating point</a></td>
				1091	<td><tt>float, double, x86_fp80, fp128, ppc_fp128</tt></td>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1092	</tr>
				1093	<tr>
				1094	<td><a name="t_firstclass">first class</a></td>
Chris Lattner	4f69f46	2008-01-04 04:32:38 +0000	[diff] [blame]	1095	<td><a href="#t_integer">integer</a>,
				1096	<a href="#t_floating">floating point</a>,
				1097	<a href="#t_pointer">pointer</a>,
Dan Gohman	0066db6	2008-06-18 18:42:13 +0000	[diff] [blame]	1098	<a href="#t_vector">vector</a>,
Dan Gohman	a334d5f	2008-05-12 23:51:09 +0000	[diff] [blame]	1099	<a href="#t_struct">structure</a>,
				1100	<a href="#t_array">array</a>,
Dan Gohman	ade5faa	2008-05-23 22:50:26 +0000	[diff] [blame]	1101	<a href="#t_label">label</a>.
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	1102	</td>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1103	</tr>
Chris Lattner	4f69f46	2008-01-04 04:32:38 +0000	[diff] [blame]	1104	<tr>
				1105	<td><a href="#t_primitive">primitive</a></td>
				1106	<td><a href="#t_label">label</a>,
				1107	<a href="#t_void">void</a>,
Chris Lattner	4f69f46	2008-01-04 04:32:38 +0000	[diff] [blame]	1108	<a href="#t_floating">floating point</a>.</td>
				1109	</tr>
				1110	<tr>
				1111	<td><a href="#t_derived">derived</a></td>
				1112	<td><a href="#t_integer">integer</a>,
				1113	<a href="#t_array">array</a>,
				1114	<a href="#t_function">function</a>,
				1115	<a href="#t_pointer">pointer</a>,
				1116	<a href="#t_struct">structure</a>,
				1117	<a href="#t_pstruct">packed structure</a>,
				1118	<a href="#t_vector">vector</a>,
				1119	<a href="#t_opaque">opaque</a>.
				1120	</tr>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1121	</tbody>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	1122	</table>
Misha Brukman	daa4cb0	2004-03-01 17:47:27 +0000	[diff] [blame]	1123
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1124	<p>The <a href="#t_firstclass">first class</a> types are perhaps the
				1125	most important. Values of these types are the only ones which can be
				1126	produced by instructions, passed as arguments, or used as operands to
Dan Gohman	c4b49eb	2008-05-23 21:53:15 +0000	[diff] [blame]	1127	instructions.</p>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	1128	</div>
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1129
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1130	<!-- ======================================================================= -->
Chris Lattner	4f69f46	2008-01-04 04:32:38 +0000	[diff] [blame]	1131	<div class="doc_subsection"> <a name="t_primitive">Primitive Types</a> </div>
Chris Lattner	8f8c7b7	2008-01-04 04:34:14 +0000	[diff] [blame]	1132
Chris Lattner	4f69f46	2008-01-04 04:32:38 +0000	[diff] [blame]	1133	<div class="doc_text">
				1134	<p>The primitive types are the fundamental building blocks of the LLVM
				1135	system.</p>
				1136
Chris Lattner	8f8c7b7	2008-01-04 04:34:14 +0000	[diff] [blame]	1137	</div>
				1138
Chris Lattner	4f69f46	2008-01-04 04:32:38 +0000	[diff] [blame]	1139	<!-- _______________________________________________________________________ -->
				1140	<div class="doc_subsubsection"> <a name="t_floating">Floating Point Types</a> </div>
				1141
				1142	<div class="doc_text">
				1143	<table>
				1144	<tbody>
				1145	<tr><th>Type</th><th>Description</th></tr>
				1146	<tr><td><tt>float</tt></td><td>32-bit floating point value</td></tr>
				1147	<tr><td><tt>double</tt></td><td>64-bit floating point value</td></tr>
				1148	<tr><td><tt>fp128</tt></td><td>128-bit floating point value (112-bit mantissa)</td></tr>
				1149	<tr><td><tt>x86_fp80</tt></td><td>80-bit floating point value (X87)</td></tr>
				1150	<tr><td><tt>ppc_fp128</tt></td><td>128-bit floating point value (two 64-bits)</td></tr>
				1151	</tbody>
				1152	</table>
				1153	</div>
				1154
				1155	<!-- _______________________________________________________________________ -->
				1156	<div class="doc_subsubsection"> <a name="t_void">Void Type</a> </div>
				1157
				1158	<div class="doc_text">
				1159	<h5>Overview:</h5>
				1160	<p>The void type does not represent any value and has no size.</p>
				1161
				1162	<h5>Syntax:</h5>
				1163
				1164	<pre>
				1165	void
				1166	</pre>
				1167	</div>
				1168
				1169	<!-- _______________________________________________________________________ -->
				1170	<div class="doc_subsubsection"> <a name="t_label">Label Type</a> </div>
				1171
				1172	<div class="doc_text">
				1173	<h5>Overview:</h5>
				1174	<p>The label type represents code labels.</p>
				1175
				1176	<h5>Syntax:</h5>
				1177
				1178	<pre>
				1179	label
				1180	</pre>
				1181	</div>
				1182
				1183
				1184	<!-- ======================================================================= -->
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1185	<div class="doc_subsection"> <a name="t_derived">Derived Types</a> </div>
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1186
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	1187	<div class="doc_text">
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1188
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1189	<p>The real power in LLVM comes from the derived types in the system.
				1190	This is what allows a programmer to represent arrays, functions,
				1191	pointers, and other useful types. Note that these derived types may be
				1192	recursive: For example, it is possible to have a two dimensional array.</p>
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1193
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	1194	</div>
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1195
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1196	<!-- _______________________________________________________________________ -->
Reid Spencer	2b91631	2007-05-16 18:44:01 +0000	[diff] [blame]	1197	<div class="doc_subsubsection"> <a name="t_integer">Integer Type</a> </div>
				1198
				1199	<div class="doc_text">
				1200
				1201	<h5>Overview:</h5>
				1202	<p>The integer type is a very simple derived type that simply specifies an
				1203	arbitrary bit width for the integer type desired. Any bit width from 1 bit to
				1204	2^23-1 (about 8 million) can be specified.</p>
				1205
				1206	<h5>Syntax:</h5>
				1207
				1208	<pre>
				1209	iN
				1210	</pre>
				1211
				1212	<p>The number of bits the integer will occupy is specified by the <tt>N</tt>
				1213	value.</p>
				1214
				1215	<h5>Examples:</h5>
				1216	<table class="layout">
Chris Lattner	b9488a6	2007-12-18 06:18:21 +0000	[diff] [blame]	1217	<tbody>
				1218	<tr>
				1219	<td><tt>i1</tt></td>
				1220	<td>a single-bit integer.</td>
				1221	</tr><tr>
				1222	<td><tt>i32</tt></td>
				1223	<td>a 32-bit integer.</td>
				1224	</tr><tr>
				1225	<td><tt>i1942652</tt></td>
				1226	<td>a really big integer of over 1 million bits.</td>
Reid Spencer	2b91631	2007-05-16 18:44:01 +0000	[diff] [blame]	1227	</tr>
Chris Lattner	b9488a6	2007-12-18 06:18:21 +0000	[diff] [blame]	1228	</tbody>
Reid Spencer	2b91631	2007-05-16 18:44:01 +0000	[diff] [blame]	1229	</table>
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	1230	</div>
Reid Spencer	2b91631	2007-05-16 18:44:01 +0000	[diff] [blame]	1231
				1232	<!-- _______________________________________________________________________ -->
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1233	<div class="doc_subsubsection"> <a name="t_array">Array Type</a> </div>
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1234
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	1235	<div class="doc_text">
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1236
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1237	<h5>Overview:</h5>
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1238
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	1239	<p>The array type is a very simple derived type that arranges elements
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1240	sequentially in memory. The array type requires a size (number of
				1241	elements) and an underlying data type.</p>
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1242
Chris Lattner	7faa883	2002-04-14 06:13:44 +0000	[diff] [blame]	1243	<h5>Syntax:</h5>
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1244
				1245	<pre>
				1246	[<# elements> x <elementtype>]
				1247	</pre>
				1248
John Criswell	e4c57cc	2005-05-12 16:52:32 +0000	[diff] [blame]	1249	<p>The number of elements is a constant integer value; elementtype may
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1250	be any type with a size.</p>
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1251
Chris Lattner	7faa883	2002-04-14 06:13:44 +0000	[diff] [blame]	1252	<h5>Examples:</h5>
Reid Spencer	d3f876c	2004-11-01 08:19:36 +0000	[diff] [blame]	1253	<table class="layout">
				1254	<tr class="layout">
Chris Lattner	23ff1f9	2007-12-19 05:04:11 +0000	[diff] [blame]	1255	<td class="left"><tt>[40 x i32]</tt></td>
				1256	<td class="left">Array of 40 32-bit integer values.</td>
				1257	</tr>
				1258	<tr class="layout">
				1259	<td class="left"><tt>[41 x i32]</tt></td>
				1260	<td class="left">Array of 41 32-bit integer values.</td>
				1261	</tr>
				1262	<tr class="layout">
				1263	<td class="left"><tt>[4 x i8]</tt></td>
				1264	<td class="left">Array of 4 8-bit integer values.</td>
Reid Spencer	d3f876c	2004-11-01 08:19:36 +0000	[diff] [blame]	1265	</tr>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1266	</table>
Reid Spencer	d3f876c	2004-11-01 08:19:36 +0000	[diff] [blame]	1267	<p>Here are some examples of multidimensional arrays:</p>
				1268	<table class="layout">
				1269	<tr class="layout">
Chris Lattner	23ff1f9	2007-12-19 05:04:11 +0000	[diff] [blame]	1270	<td class="left"><tt>[3 x [4 x i32]]</tt></td>
				1271	<td class="left">3x4 array of 32-bit integer values.</td>
				1272	</tr>
				1273	<tr class="layout">
				1274	<td class="left"><tt>[12 x [10 x float]]</tt></td>
				1275	<td class="left">12x10 array of single precision floating point values.</td>
				1276	</tr>
				1277	<tr class="layout">
				1278	<td class="left"><tt>[2 x [3 x [4 x i16]]]</tt></td>
				1279	<td class="left">2x3x4 array of 16-bit integer values.</td>
Reid Spencer	d3f876c	2004-11-01 08:19:36 +0000	[diff] [blame]	1280	</tr>
				1281	</table>
Chris Lattner	e67a951	2005-06-24 17:22:57 +0000	[diff] [blame]	1282
John Criswell	0ec250c	2005-10-24 16:17:18 +0000	[diff] [blame]	1283	<p>Note that 'variable sized arrays' can be implemented in LLVM with a zero
				1284	length array. Normally, accesses past the end of an array are undefined in
Chris Lattner	e67a951	2005-06-24 17:22:57 +0000	[diff] [blame]	1285	LLVM (e.g. it is illegal to access the 5th element of a 3 element array).
				1286	As a special case, however, zero length arrays are recognized to be variable
				1287	length. This allows implementation of 'pascal style arrays' with the LLVM
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	1288	type "{ i32, [0 x float]}", for example.</p>
Chris Lattner	e67a951	2005-06-24 17:22:57 +0000	[diff] [blame]	1289
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	1290	</div>
Reid Spencer	d3f876c	2004-11-01 08:19:36 +0000	[diff] [blame]	1291
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1292	<!-- _______________________________________________________________________ -->
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1293	<div class="doc_subsubsection"> <a name="t_function">Function Type</a> </div>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	1294	<div class="doc_text">
Chris Lattner	f4cde4e	2008-04-23 04:59:35 +0000	[diff] [blame]	1295
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1296	<h5>Overview:</h5>
Chris Lattner	f4cde4e	2008-04-23 04:59:35 +0000	[diff] [blame]	1297
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1298	<p>The function type can be thought of as a function signature. It
Devang Patel	a582f40	2008-03-24 05:35:41 +0000	[diff] [blame]	1299	consists of a return type and a list of formal parameter types. The
Chris Lattner	f4cde4e	2008-04-23 04:59:35 +0000	[diff] [blame]	1300	return type of a function type is a scalar type, a void type, or a struct type.
Devang Patel	7a3ad1a	2008-03-24 20:52:42 +0000	[diff] [blame]	1301	If the return type is a struct type then all struct elements must be of first
Chris Lattner	f4cde4e	2008-04-23 04:59:35 +0000	[diff] [blame]	1302	class types, and the struct must have at least one element.</p>
Devang Patel	c3fc6df	2008-03-10 20:49:15 +0000	[diff] [blame]	1303
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1304	<h5>Syntax:</h5>
Chris Lattner	f4cde4e	2008-04-23 04:59:35 +0000	[diff] [blame]	1305
				1306	<pre>
				1307	<returntype list> (<parameter list>)
				1308	</pre>
				1309
John Criswell	0ec250c	2005-10-24 16:17:18 +0000	[diff] [blame]	1310	<p>...where '<tt><parameter list></tt>' is a comma-separated list of type
Misha Brukman	c24b758	2004-08-12 20:16:08 +0000	[diff] [blame]	1311	specifiers. Optionally, the parameter list may include a type <tt>...</tt>,
Chris Lattner	27f71f2	2003-09-03 00:41:47 +0000	[diff] [blame]	1312	which indicates that the function takes a variable number of arguments.
				1313	Variable argument functions can access their arguments with the <a
Devang Patel	c3fc6df	2008-03-10 20:49:15 +0000	[diff] [blame]	1314	href="#int_varargs">variable argument handling intrinsic</a> functions.
				1315	'<tt><returntype list></tt>' is a comma-separated list of
				1316	<a href="#t_firstclass">first class</a> type specifiers.</p>
Chris Lattner	f4cde4e	2008-04-23 04:59:35 +0000	[diff] [blame]	1317
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1318	<h5>Examples:</h5>
Reid Spencer	d3f876c	2004-11-01 08:19:36 +0000	[diff] [blame]	1319	<table class="layout">
				1320	<tr class="layout">
Reid Spencer	92f8230	2006-12-31 07:18:34 +0000	[diff] [blame]	1321	<td class="left"><tt>i32 (i32)</tt></td>
				1322	<td class="left">function taking an <tt>i32</tt>, returning an <tt>i32</tt>
Reid Spencer	d3f876c	2004-11-01 08:19:36 +0000	[diff] [blame]	1323	</td>
Reid Spencer	92f8230	2006-12-31 07:18:34 +0000	[diff] [blame]	1324	</tr><tr class="layout">
Reid Spencer	9445e9a	2007-07-19 23:13:04 +0000	[diff] [blame]	1325	<td class="left"><tt>float (i16 signext, i32 )
Reid Spencer	f17a0b7	2006-12-31 07:20:23 +0000	[diff] [blame]	1326	</tt></td>
Reid Spencer	92f8230	2006-12-31 07:18:34 +0000	[diff] [blame]	1327	<td class="left"><a href="#t_pointer">Pointer</a> to a function that takes
				1328	an <tt>i16</tt> that should be sign extended and a
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	1329	<a href="#t_pointer">pointer</a> to <tt>i32</tt>, returning
Reid Spencer	92f8230	2006-12-31 07:18:34 +0000	[diff] [blame]	1330	<tt>float</tt>.
				1331	</td>
				1332	</tr><tr class="layout">
				1333	<td class="left"><tt>i32 (i8*, ...)</tt></td>
				1334	<td class="left">A vararg function that takes at least one
Reid Spencer	a517338	2007-01-04 16:43:23 +0000	[diff] [blame]	1335	<a href="#t_pointer">pointer</a> to <tt>i8 </tt> (char in C),
Reid Spencer	92f8230	2006-12-31 07:18:34 +0000	[diff] [blame]	1336	which returns an integer. This is the signature for <tt>printf</tt> in
				1337	LLVM.
Reid Spencer	d3f876c	2004-11-01 08:19:36 +0000	[diff] [blame]	1338	</td>
Devang Patel	a582f40	2008-03-24 05:35:41 +0000	[diff] [blame]	1339	</tr><tr class="layout">
				1340	<td class="left"><tt>{i32, i32} (i32)</tt></td>
Devang Patel	3a5bff8	2008-03-24 18:10:52 +0000	[diff] [blame]	1341	<td class="left">A function taking an <tt>i32></tt>, returning two
				1342	<tt> i32 </tt> values as an aggregate of type <tt>{ i32, i32 }</tt>
Devang Patel	a582f40	2008-03-24 05:35:41 +0000	[diff] [blame]	1343	</td>
Reid Spencer	d3f876c	2004-11-01 08:19:36 +0000	[diff] [blame]	1344	</tr>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1345	</table>
Misha Brukman	daa4cb0	2004-03-01 17:47:27 +0000	[diff] [blame]	1346
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	1347	</div>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1348	<!-- _______________________________________________________________________ -->
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1349	<div class="doc_subsubsection"> <a name="t_struct">Structure Type</a> </div>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	1350	<div class="doc_text">
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1351	<h5>Overview:</h5>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1352	<p>The structure type is used to represent a collection of data members
				1353	together in memory. The packing of the field types is defined to match
				1354	the ABI of the underlying processor. The elements of a structure may
				1355	be any type that has a size.</p>
				1356	<p>Structures are accessed using '<tt><a href="#i_load">load</a></tt>
				1357	and '<tt><a href="#i_store">store</a></tt>' by getting a pointer to a
				1358	field with the '<tt><a href="#i_getelementptr">getelementptr</a></tt>'
				1359	instruction.</p>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1360	<h5>Syntax:</h5>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1361	<pre> { <type list> }<br></pre>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1362	<h5>Examples:</h5>
Reid Spencer	d3f876c	2004-11-01 08:19:36 +0000	[diff] [blame]	1363	<table class="layout">
				1364	<tr class="layout">
Jeff Cohen	6f1cc77	2007-04-22 01:17:39 +0000	[diff] [blame]	1365	<td class="left"><tt>{ i32, i32, i32 }</tt></td>
				1366	<td class="left">A triple of three <tt>i32</tt> values</td>
				1367	</tr><tr class="layout">
				1368	<td class="left"><tt>{ float, i32 (i32) * }</tt></td>
				1369	<td class="left">A pair, where the first element is a <tt>float</tt> and the
				1370	second element is a <a href="#t_pointer">pointer</a> to a
				1371	<a href="#t_function">function</a> that takes an <tt>i32</tt>, returning
				1372	an <tt>i32</tt>.</td>
Reid Spencer	d3f876c	2004-11-01 08:19:36 +0000	[diff] [blame]	1373	</tr>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1374	</table>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	1375	</div>
Reid Spencer	d3f876c	2004-11-01 08:19:36 +0000	[diff] [blame]	1376
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1377	<!-- _______________________________________________________________________ -->
Andrew Lenharth	75e1068	2006-12-08 17:13:00 +0000	[diff] [blame]	1378	<div class="doc_subsubsection"> <a name="t_pstruct">Packed Structure Type</a>
				1379	</div>
				1380	<div class="doc_text">
				1381	<h5>Overview:</h5>
				1382	<p>The packed structure type is used to represent a collection of data members
				1383	together in memory. There is no padding between fields. Further, the alignment
				1384	of a packed structure is 1 byte. The elements of a packed structure may
				1385	be any type that has a size.</p>
				1386	<p>Structures are accessed using '<tt><a href="#i_load">load</a></tt>
				1387	and '<tt><a href="#i_store">store</a></tt>' by getting a pointer to a
				1388	field with the '<tt><a href="#i_getelementptr">getelementptr</a></tt>'
				1389	instruction.</p>
				1390	<h5>Syntax:</h5>
				1391	<pre> < { <type list> } > <br></pre>
				1392	<h5>Examples:</h5>
				1393	<table class="layout">
				1394	<tr class="layout">
Jeff Cohen	6f1cc77	2007-04-22 01:17:39 +0000	[diff] [blame]	1395	<td class="left"><tt>< { i32, i32, i32 } ></tt></td>
				1396	<td class="left">A triple of three <tt>i32</tt> values</td>
				1397	</tr><tr class="layout">
Bill Wendling	e36dccc	2008-09-07 10:26:33 +0000	[diff] [blame]	1398	<td class="left">
				1399	<tt>< { float, i32 (i32)* } ></tt></td>
Jeff Cohen	6f1cc77	2007-04-22 01:17:39 +0000	[diff] [blame]	1400	<td class="left">A pair, where the first element is a <tt>float</tt> and the
				1401	second element is a <a href="#t_pointer">pointer</a> to a
				1402	<a href="#t_function">function</a> that takes an <tt>i32</tt>, returning
				1403	an <tt>i32</tt>.</td>
Andrew Lenharth	75e1068	2006-12-08 17:13:00 +0000	[diff] [blame]	1404	</tr>
				1405	</table>
				1406	</div>
				1407
				1408	<!-- _______________________________________________________________________ -->
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1409	<div class="doc_subsubsection"> <a name="t_pointer">Pointer Type</a> </div>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	1410	<div class="doc_text">
Chris Lattner	7faa883	2002-04-14 06:13:44 +0000	[diff] [blame]	1411	<h5>Overview:</h5>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1412	<p>As in many languages, the pointer type represents a pointer or
Christopher Lamb	284d992	2007-12-11 09:31:00 +0000	[diff] [blame]	1413	reference to another object, which must live in memory. Pointer types may have
				1414	an optional address space attribute defining the target-specific numbered
				1415	address space where the pointed-to object resides. The default address space is
				1416	zero.</p>
Chris Lattner	7faa883	2002-04-14 06:13:44 +0000	[diff] [blame]	1417	<h5>Syntax:</h5>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1418	<pre> <type> *<br></pre>
Chris Lattner	7faa883	2002-04-14 06:13:44 +0000	[diff] [blame]	1419	<h5>Examples:</h5>
Reid Spencer	d3f876c	2004-11-01 08:19:36 +0000	[diff] [blame]	1420	<table class="layout">
				1421	<tr class="layout">
Chris Lattner	23ff1f9	2007-12-19 05:04:11 +0000	[diff] [blame]	1422	<td class="left"><tt>[4x i32]*</tt></td>
				1423	<td class="left">A <a href="#t_pointer">pointer</a> to <a
				1424	href="#t_array">array</a> of four <tt>i32</tt> values.</td>
				1425	</tr>
				1426	<tr class="layout">
				1427	<td class="left"><tt>i32 (i32 ) </tt></td>
				1428	<td class="left"> A <a href="#t_pointer">pointer</a> to a <a
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	1429	href="#t_function">function</a> that takes an <tt>i32*</tt>, returning an
Chris Lattner	23ff1f9	2007-12-19 05:04:11 +0000	[diff] [blame]	1430	<tt>i32</tt>.</td>
				1431	</tr>
				1432	<tr class="layout">
				1433	<td class="left"><tt>i32 addrspace(5)*</tt></td>
				1434	<td class="left">A <a href="#t_pointer">pointer</a> to an <tt>i32</tt> value
				1435	that resides in address space #5.</td>
Reid Spencer	d3f876c	2004-11-01 08:19:36 +0000	[diff] [blame]	1436	</tr>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	1437	</table>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	1438	</div>
Reid Spencer	d3f876c	2004-11-01 08:19:36 +0000	[diff] [blame]	1439
Chris Lattner	a58561b	2004-08-12 19:12:28 +0000	[diff] [blame]	1440	<!-- _______________________________________________________________________ -->
Reid Spencer	485bad1	2007-02-15 03:07:05 +0000	[diff] [blame]	1441	<div class="doc_subsubsection"> <a name="t_vector">Vector Type</a> </div>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	1442	<div class="doc_text">
Chris Lattner	69c11bb	2005-04-25 17:34:15 +0000	[diff] [blame]	1443
Chris Lattner	a58561b	2004-08-12 19:12:28 +0000	[diff] [blame]	1444	<h5>Overview:</h5>
Chris Lattner	69c11bb	2005-04-25 17:34:15 +0000	[diff] [blame]	1445
Reid Spencer	485bad1	2007-02-15 03:07:05 +0000	[diff] [blame]	1446	<p>A vector type is a simple derived type that represents a vector
				1447	of elements. Vector types are used when multiple primitive data
Chris Lattner	a58561b	2004-08-12 19:12:28 +0000	[diff] [blame]	1448	are operated in parallel using a single instruction (SIMD).
Reid Spencer	485bad1	2007-02-15 03:07:05 +0000	[diff] [blame]	1449	A vector type requires a size (number of
Chris Lattner	b8d172f	2005-11-10 01:44:22 +0000	[diff] [blame]	1450	elements) and an underlying primitive data type. Vectors must have a power
Reid Spencer	485bad1	2007-02-15 03:07:05 +0000	[diff] [blame]	1451	of two length (1, 2, 4, 8, 16 ...). Vector types are
Chris Lattner	a58561b	2004-08-12 19:12:28 +0000	[diff] [blame]	1452	considered <a href="#t_firstclass">first class</a>.</p>
Chris Lattner	69c11bb	2005-04-25 17:34:15 +0000	[diff] [blame]	1453
Chris Lattner	a58561b	2004-08-12 19:12:28 +0000	[diff] [blame]	1454	<h5>Syntax:</h5>
Chris Lattner	69c11bb	2005-04-25 17:34:15 +0000	[diff] [blame]	1455
				1456	<pre>
				1457	< <# elements> x <elementtype> >
				1458	</pre>
				1459
John Criswell	c1f786c	2005-05-13 22:25:59 +0000	[diff] [blame]	1460	<p>The number of elements is a constant integer value; elementtype may
Chris Lattner	3b19d65	2007-01-15 01:54:13 +0000	[diff] [blame]	1461	be any integer or floating point type.</p>
Chris Lattner	69c11bb	2005-04-25 17:34:15 +0000	[diff] [blame]	1462
Chris Lattner	a58561b	2004-08-12 19:12:28 +0000	[diff] [blame]	1463	<h5>Examples:</h5>
Chris Lattner	69c11bb	2005-04-25 17:34:15 +0000	[diff] [blame]	1464
Reid Spencer	d3f876c	2004-11-01 08:19:36 +0000	[diff] [blame]	1465	<table class="layout">
				1466	<tr class="layout">
Chris Lattner	23ff1f9	2007-12-19 05:04:11 +0000	[diff] [blame]	1467	<td class="left"><tt><4 x i32></tt></td>
				1468	<td class="left">Vector of 4 32-bit integer values.</td>
				1469	</tr>
				1470	<tr class="layout">
				1471	<td class="left"><tt><8 x float></tt></td>
				1472	<td class="left">Vector of 8 32-bit floating-point values.</td>
				1473	</tr>
				1474	<tr class="layout">
				1475	<td class="left"><tt><2 x i64></tt></td>
				1476	<td class="left">Vector of 2 64-bit integer values.</td>
Reid Spencer	d3f876c	2004-11-01 08:19:36 +0000	[diff] [blame]	1477	</tr>
				1478	</table>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	1479	</div>
				1480
Chris Lattner	69c11bb	2005-04-25 17:34:15 +0000	[diff] [blame]	1481	<!-- _______________________________________________________________________ -->
				1482	<div class="doc_subsubsection"> <a name="t_opaque">Opaque Type</a> </div>
				1483	<div class="doc_text">
				1484
				1485	<h5>Overview:</h5>
				1486
				1487	<p>Opaque types are used to represent unknown types in the system. This
Gordon Henriksen	8ac04ff	2007-10-14 00:34:53 +0000	[diff] [blame]	1488	corresponds (for example) to the C notion of a forward declared structure type.
Chris Lattner	69c11bb	2005-04-25 17:34:15 +0000	[diff] [blame]	1489	In LLVM, opaque types can eventually be resolved to any type (not just a
				1490	structure type).</p>
				1491
				1492	<h5>Syntax:</h5>
				1493
				1494	<pre>
				1495	opaque
				1496	</pre>
				1497
				1498	<h5>Examples:</h5>
				1499
				1500	<table class="layout">
				1501	<tr class="layout">
Chris Lattner	23ff1f9	2007-12-19 05:04:11 +0000	[diff] [blame]	1502	<td class="left"><tt>opaque</tt></td>
				1503	<td class="left">An opaque type.</td>
Chris Lattner	69c11bb	2005-04-25 17:34:15 +0000	[diff] [blame]	1504	</tr>
				1505	</table>
				1506	</div>
				1507
				1508
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1509	<!-- *********************************************************************** -->
				1510	<div class="doc_section"> <a name="constants">Constants</a> </div>
				1511	<!-- *********************************************************************** -->
				1512
				1513	<div class="doc_text">
				1514
				1515	<p>LLVM has several different basic types of constants. This section describes
				1516	them all and their syntax.</p>
				1517
				1518	</div>
				1519
				1520	<!-- ======================================================================= -->
Reid Spencer	cc16dc3	2004-12-09 18:02:53 +0000	[diff] [blame]	1521	<div class="doc_subsection"><a name="simpleconstants">Simple Constants</a></div>
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1522
				1523	<div class="doc_text">
				1524
				1525	<dl>
				1526	<dt><b>Boolean constants</b></dt>
				1527
				1528	<dd>The two strings '<tt>true</tt>' and '<tt>false</tt>' are both valid
Reid Spencer	c78f337	2007-01-12 03:35:51 +0000	[diff] [blame]	1529	constants of the <tt><a href="#t_primitive">i1</a></tt> type.
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1530	</dd>
				1531
				1532	<dt><b>Integer constants</b></dt>
				1533
Reid Spencer	cc16dc3	2004-12-09 18:02:53 +0000	[diff] [blame]	1534	<dd>Standard integers (such as '4') are constants of the <a
Reid Spencer	a517338	2007-01-04 16:43:23 +0000	[diff] [blame]	1535	href="#t_integer">integer</a> type. Negative numbers may be used with
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1536	integer types.
				1537	</dd>
				1538
				1539	<dt><b>Floating point constants</b></dt>
				1540
				1541	<dd>Floating point constants use standard decimal notation (e.g. 123.421),
				1542	exponential notation (e.g. 1.23421e+2), or a more precise hexadecimal
Chris Lattner	a73afe0	2008-04-01 18:45:27 +0000	[diff] [blame]	1543	notation (see below). The assembler requires the exact decimal value of
				1544	a floating-point constant. For example, the assembler accepts 1.25 but
				1545	rejects 1.3 because 1.3 is a repeating decimal in binary. Floating point
				1546	constants must have a <a href="#t_floating">floating point</a> type. </dd>
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1547
				1548	<dt><b>Null pointer constants</b></dt>
				1549
John Criswell	9e2485c	2004-12-10 15:51:16 +0000	[diff] [blame]	1550	<dd>The identifier '<tt>null</tt>' is recognized as a null pointer constant
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1551	and must be of <a href="#t_pointer">pointer type</a>.</dd>
				1552
				1553	</dl>
				1554
John Criswell	9e2485c	2004-12-10 15:51:16 +0000	[diff] [blame]	1555	<p>The one non-intuitive notation for constants is the optional hexadecimal form
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1556	of floating point constants. For example, the form '<tt>double
				1557	0x432ff973cafa8000</tt>' is equivalent to (but harder to read than) '<tt>double
				1558	4.5e+15</tt>'. The only time hexadecimal floating point constants are required
Reid Spencer	cc16dc3	2004-12-09 18:02:53 +0000	[diff] [blame]	1559	(and the only time that they are generated by the disassembler) is when a
				1560	floating point constant must be emitted but it cannot be represented as a
				1561	decimal floating point number. For example, NaN's, infinities, and other
				1562	special values are represented in their IEEE hexadecimal format so that
				1563	assembly and disassembly do not cause any bits to change in the constants.</p>
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1564
				1565	</div>
				1566
				1567	<!-- ======================================================================= -->
				1568	<div class="doc_subsection"><a name="aggregateconstants">Aggregate Constants</a>
				1569	</div>
				1570
				1571	<div class="doc_text">
Chris Lattner	d4f6b17	2005-03-07 22:13:59 +0000	[diff] [blame]	1572	<p>Aggregate constants arise from aggregation of simple constants
				1573	and smaller aggregate constants.</p>
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1574
				1575	<dl>
				1576	<dt><b>Structure constants</b></dt>
				1577
				1578	<dd>Structure constants are represented with notation similar to structure
				1579	type definitions (a comma separated list of elements, surrounded by braces
Chris Lattner	64910ee	2007-12-25 20:34:52 +0000	[diff] [blame]	1580	(<tt>{}</tt>)). For example: "<tt>{ i32 4, float 17.0, i32* @G }</tt>",
				1581	where "<tt>@G</tt>" is declared as "<tt>@G = external global i32</tt>". Structure constants
Chris Lattner	d4f6b17	2005-03-07 22:13:59 +0000	[diff] [blame]	1582	must have <a href="#t_struct">structure type</a>, and the number and
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1583	types of elements must match those specified by the type.
				1584	</dd>
				1585
				1586	<dt><b>Array constants</b></dt>
				1587
				1588	<dd>Array constants are represented with notation similar to array type
				1589	definitions (a comma separated list of elements, surrounded by square brackets
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	1590	(<tt>[]</tt>)). For example: "<tt>[ i32 42, i32 11, i32 74 ]</tt>". Array
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1591	constants must have <a href="#t_array">array type</a>, and the number and
				1592	types of elements must match those specified by the type.
				1593	</dd>
				1594
Reid Spencer	485bad1	2007-02-15 03:07:05 +0000	[diff] [blame]	1595	<dt><b>Vector constants</b></dt>
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1596
Reid Spencer	485bad1	2007-02-15 03:07:05 +0000	[diff] [blame]	1597	<dd>Vector constants are represented with notation similar to vector type
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1598	definitions (a comma separated list of elements, surrounded by
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	1599	less-than/greater-than's (<tt><></tt>)). For example: "<tt>< i32 42,
Jeff Cohen	6f1cc77	2007-04-22 01:17:39 +0000	[diff] [blame]	1600	i32 11, i32 74, i32 100 ></tt>". Vector constants must have <a
Reid Spencer	485bad1	2007-02-15 03:07:05 +0000	[diff] [blame]	1601	href="#t_vector">vector type</a>, and the number and types of elements must
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1602	match those specified by the type.
				1603	</dd>
				1604
				1605	<dt><b>Zero initialization</b></dt>
				1606
				1607	<dd>The string '<tt>zeroinitializer</tt>' can be used to zero initialize a
				1608	value to zero of <em>any</em> type, including scalar and aggregate types.
				1609	This is often used to avoid having to print large zero initializers (e.g. for
John Criswell	0ec250c	2005-10-24 16:17:18 +0000	[diff] [blame]	1610	large arrays) and is always exactly equivalent to using explicit zero
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1611	initializers.
				1612	</dd>
				1613	</dl>
				1614
				1615	</div>
				1616
				1617	<!-- ======================================================================= -->
				1618	<div class="doc_subsection">
				1619	<a name="globalconstants">Global Variable and Function Addresses</a>
				1620	</div>
				1621
				1622	<div class="doc_text">
				1623
				1624	<p>The addresses of <a href="#globalvars">global variables</a> and <a
				1625	href="#functionstructure">functions</a> are always implicitly valid (link-time)
John Criswell	9e2485c	2004-12-10 15:51:16 +0000	[diff] [blame]	1626	constants. These constants are explicitly referenced when the <a
				1627	href="#identifiers">identifier for the global</a> is used and always have <a
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1628	href="#t_pointer">pointer</a> type. For example, the following is a legal LLVM
				1629	file:</p>
				1630
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	1631	<div class="doc_code">
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1632	<pre>
Chris Lattner	a18a424	2007-06-06 18:28:13 +0000	[diff] [blame]	1633	@X = global i32 17
				1634	@Y = global i32 42
				1635	@Z = global [2 x i32] [ i32 @X, i32* @Y ]
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1636	</pre>
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	1637	</div>
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1638
				1639	</div>
				1640
				1641	<!-- ======================================================================= -->
Reid Spencer	2dc45b8	2004-12-09 18:13:12 +0000	[diff] [blame]	1642	<div class="doc_subsection"><a name="undefvalues">Undefined Values</a></div>
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1643	<div class="doc_text">
Reid Spencer	2dc45b8	2004-12-09 18:13:12 +0000	[diff] [blame]	1644	<p>The string '<tt>undef</tt>' is recognized as a type-less constant that has
John Criswell	c1f786c	2005-05-13 22:25:59 +0000	[diff] [blame]	1645	no specific value. Undefined values may be of any type and be used anywhere
Reid Spencer	2dc45b8	2004-12-09 18:13:12 +0000	[diff] [blame]	1646	a constant is permitted.</p>
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1647
Reid Spencer	2dc45b8	2004-12-09 18:13:12 +0000	[diff] [blame]	1648	<p>Undefined values indicate to the compiler that the program is well defined
				1649	no matter what value is used, giving the compiler more freedom to optimize.
				1650	</p>
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1651	</div>
				1652
				1653	<!-- ======================================================================= -->
				1654	<div class="doc_subsection"><a name="constantexprs">Constant Expressions</a>
				1655	</div>
				1656
				1657	<div class="doc_text">
				1658
				1659	<p>Constant expressions are used to allow expressions involving other constants
				1660	to be used as constants. Constant expressions may be of any <a
John Criswell	c1f786c	2005-05-13 22:25:59 +0000	[diff] [blame]	1661	href="#t_firstclass">first class</a> type and may involve any LLVM operation
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1662	that does not have side effects (e.g. load and call are not supported). The
				1663	following is the syntax for constant expressions:</p>
				1664
				1665	<dl>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	1666	<dt><b><tt>trunc ( CST to TYPE )</tt></b></dt>
				1667	<dd>Truncate a constant to another type. The bit size of CST must be larger
Chris Lattner	3b19d65	2007-01-15 01:54:13 +0000	[diff] [blame]	1668	than the bit size of TYPE. Both types must be integers.</dd>
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1669
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	1670	<dt><b><tt>zext ( CST to TYPE )</tt></b></dt>
				1671	<dd>Zero extend a constant to another type. The bit size of CST must be
Chris Lattner	3b19d65	2007-01-15 01:54:13 +0000	[diff] [blame]	1672	smaller or equal to the bit size of TYPE. Both types must be integers.</dd>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	1673
				1674	<dt><b><tt>sext ( CST to TYPE )</tt></b></dt>
				1675	<dd>Sign extend a constant to another type. The bit size of CST must be
Chris Lattner	3b19d65	2007-01-15 01:54:13 +0000	[diff] [blame]	1676	smaller or equal to the bit size of TYPE. Both types must be integers.</dd>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	1677
				1678	<dt><b><tt>fptrunc ( CST to TYPE )</tt></b></dt>
				1679	<dd>Truncate a floating point constant to another floating point type. The
				1680	size of CST must be larger than the size of TYPE. Both types must be
				1681	floating point.</dd>
				1682
				1683	<dt><b><tt>fpext ( CST to TYPE )</tt></b></dt>
				1684	<dd>Floating point extend a constant to another type. The size of CST must be
				1685	smaller or equal to the size of TYPE. Both types must be floating point.</dd>
				1686
Reid Spencer	1539a1c	2007-07-31 14:40:14 +0000	[diff] [blame]	1687	<dt><b><tt>fptoui ( CST to TYPE )</tt></b></dt>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	1688	<dd>Convert a floating point constant to the corresponding unsigned integer
Nate Begeman	b348d18	2007-11-17 03:58:34 +0000	[diff] [blame]	1689	constant. TYPE must be a scalar or vector integer type. CST must be of scalar
				1690	or vector floating point type. Both CST and TYPE must be scalars, or vectors
				1691	of the same number of elements. If the value won't fit in the integer type,
				1692	the results are undefined.</dd>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	1693
Reid Spencer	d444879	2006-11-09 23:03:26 +0000	[diff] [blame]	1694	<dt><b><tt>fptosi ( CST to TYPE )</tt></b></dt>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	1695	<dd>Convert a floating point constant to the corresponding signed integer
Nate Begeman	b348d18	2007-11-17 03:58:34 +0000	[diff] [blame]	1696	constant. TYPE must be a scalar or vector integer type. CST must be of scalar
				1697	or vector floating point type. Both CST and TYPE must be scalars, or vectors
				1698	of the same number of elements. If the value won't fit in the integer type,
				1699	the results are undefined.</dd>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	1700
Reid Spencer	d444879	2006-11-09 23:03:26 +0000	[diff] [blame]	1701	<dt><b><tt>uitofp ( CST to TYPE )</tt></b></dt>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	1702	<dd>Convert an unsigned integer constant to the corresponding floating point
Nate Begeman	b348d18	2007-11-17 03:58:34 +0000	[diff] [blame]	1703	constant. TYPE must be a scalar or vector floating point type. CST must be of
				1704	scalar or vector integer type. Both CST and TYPE must be scalars, or vectors
				1705	of the same number of elements. If the value won't fit in the floating point
				1706	type, the results are undefined.</dd>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	1707
Reid Spencer	d444879	2006-11-09 23:03:26 +0000	[diff] [blame]	1708	<dt><b><tt>sitofp ( CST to TYPE )</tt></b></dt>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	1709	<dd>Convert a signed integer constant to the corresponding floating point
Nate Begeman	b348d18	2007-11-17 03:58:34 +0000	[diff] [blame]	1710	constant. TYPE must be a scalar or vector floating point type. CST must be of
				1711	scalar or vector integer type. Both CST and TYPE must be scalars, or vectors
				1712	of the same number of elements. If the value won't fit in the floating point
				1713	type, the results are undefined.</dd>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	1714
Reid Spencer	5c0ef47	2006-11-11 23:08:07 +0000	[diff] [blame]	1715	<dt><b><tt>ptrtoint ( CST to TYPE )</tt></b></dt>
				1716	<dd>Convert a pointer typed constant to the corresponding integer constant
				1717	TYPE must be an integer type. CST must be of pointer type. The CST value is
				1718	zero extended, truncated, or unchanged to make it fit in TYPE.</dd>
				1719
				1720	<dt><b><tt>inttoptr ( CST to TYPE )</tt></b></dt>
				1721	<dd>Convert a integer constant to a pointer constant. TYPE must be a
				1722	pointer type. CST must be of integer type. The CST value is zero extended,
				1723	truncated, or unchanged to make it fit in a pointer size. This one is
				1724	<i>really</i> dangerous!</dd>
				1725
				1726	<dt><b><tt>bitcast ( CST to TYPE )</tt></b></dt>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	1727	<dd>Convert a constant, CST, to another TYPE. The size of CST and TYPE must be
				1728	identical (same number of bits). The conversion is done as if the CST value
				1729	was stored to memory and read back as TYPE. In other words, no bits change
Reid Spencer	5c0ef47	2006-11-11 23:08:07 +0000	[diff] [blame]	1730	with this operator, just the type. This can be used for conversion of
Reid Spencer	485bad1	2007-02-15 03:07:05 +0000	[diff] [blame]	1731	vector types to any other type, as long as they have the same bit width. For
Dan Gohman	500233a	2008-09-08 16:45:59 +0000	[diff] [blame]	1732	pointers it is only valid to cast to another pointer type. It is not valid
				1733	to bitcast to or from an aggregate type.
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	1734	</dd>
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1735
				1736	<dt><b><tt>getelementptr ( CSTPTR, IDX0, IDX1, ... )</tt></b></dt>
				1737
				1738	<dd>Perform the <a href="#i_getelementptr">getelementptr operation</a> on
				1739	constants. As with the <a href="#i_getelementptr">getelementptr</a>
				1740	instruction, the index list may have zero or more indexes, which are required
				1741	to make sense for the type of "CSTPTR".</dd>
				1742
Robert Bocchino	9fbe145	2006-01-10 19:31:34 +0000	[diff] [blame]	1743	<dt><b><tt>select ( COND, VAL1, VAL2 )</tt></b></dt>
				1744
				1745	<dd>Perform the <a href="#i_select">select operation</a> on
Reid Spencer	01c4259	2006-12-04 19:23:19 +0000	[diff] [blame]	1746	constants.</dd>
				1747
				1748	<dt><b><tt>icmp COND ( VAL1, VAL2 )</tt></b></dt>
				1749	<dd>Performs the <a href="#i_icmp">icmp operation</a> on constants.</dd>
				1750
				1751	<dt><b><tt>fcmp COND ( VAL1, VAL2 )</tt></b></dt>
				1752	<dd>Performs the <a href="#i_fcmp">fcmp operation</a> on constants.</dd>
Robert Bocchino	9fbe145	2006-01-10 19:31:34 +0000	[diff] [blame]	1753
Nate Begeman	ac80ade	2008-05-12 19:01:56 +0000	[diff] [blame]	1754	<dt><b><tt>vicmp COND ( VAL1, VAL2 )</tt></b></dt>
				1755	<dd>Performs the <a href="#i_vicmp">vicmp operation</a> on constants.</dd>
				1756
				1757	<dt><b><tt>vfcmp COND ( VAL1, VAL2 )</tt></b></dt>
				1758	<dd>Performs the <a href="#i_vfcmp">vfcmp operation</a> on constants.</dd>
				1759
Robert Bocchino	9fbe145	2006-01-10 19:31:34 +0000	[diff] [blame]	1760	<dt><b><tt>extractelement ( VAL, IDX )</tt></b></dt>
				1761
				1762	<dd>Perform the <a href="#i_extractelement">extractelement
				1763	operation</a> on constants.
				1764
Robert Bocchino	05ccd70	2006-01-15 20:48:27 +0000	[diff] [blame]	1765	<dt><b><tt>insertelement ( VAL, ELT, IDX )</tt></b></dt>
				1766
				1767	<dd>Perform the <a href="#i_insertelement">insertelement
Reid Spencer	01c4259	2006-12-04 19:23:19 +0000	[diff] [blame]	1768	operation</a> on constants.</dd>
Robert Bocchino	05ccd70	2006-01-15 20:48:27 +0000	[diff] [blame]	1769
Chris Lattner	c198954	2006-04-08 00:13:41 +0000	[diff] [blame]	1770
				1771	<dt><b><tt>shufflevector ( VEC1, VEC2, IDXMASK )</tt></b></dt>
				1772
				1773	<dd>Perform the <a href="#i_shufflevector">shufflevector
Reid Spencer	01c4259	2006-12-04 19:23:19 +0000	[diff] [blame]	1774	operation</a> on constants.</dd>
Chris Lattner	c198954	2006-04-08 00:13:41 +0000	[diff] [blame]	1775
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1776	<dt><b><tt>OPCODE ( LHS, RHS )</tt></b></dt>
				1777
Reid Spencer	2dc45b8	2004-12-09 18:13:12 +0000	[diff] [blame]	1778	<dd>Perform the specified operation of the LHS and RHS constants. OPCODE may
				1779	be any of the <a href="#binaryops">binary</a> or <a href="#bitwiseops">bitwise
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1780	binary</a> operations. The constraints on operands are the same as those for
				1781	the corresponding instruction (e.g. no bitwise operations on floating point
John Criswell	e4c57cc	2005-05-12 16:52:32 +0000	[diff] [blame]	1782	values are allowed).</dd>
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1783	</dl>
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1784	</div>
Chris Lattner	9ee5d22	2004-03-08 16:49:10 +0000	[diff] [blame]	1785
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1786	<!-- *********************************************************************** -->
Chris Lattner	e87d653	2006-01-25 23:47:57 +0000	[diff] [blame]	1787	<div class="doc_section"> <a name="othervalues">Other Values</a> </div>
				1788	<!-- *********************************************************************** -->
				1789
				1790	<!-- ======================================================================= -->
				1791	<div class="doc_subsection">
				1792	<a name="inlineasm">Inline Assembler Expressions</a>
				1793	</div>
				1794
				1795	<div class="doc_text">
				1796
				1797	<p>
				1798	LLVM supports inline assembler expressions (as opposed to <a href="#moduleasm">
				1799	Module-Level Inline Assembly</a>) through the use of a special value. This
				1800	value represents the inline assembler as a string (containing the instructions
				1801	to emit), a list of operand constraints (stored as a string), and a flag that
				1802	indicates whether or not the inline asm expression has side effects. An example
				1803	inline assembler expression is:
				1804	</p>
				1805
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	1806	<div class="doc_code">
Chris Lattner	e87d653	2006-01-25 23:47:57 +0000	[diff] [blame]	1807	<pre>
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	1808	i32 (i32) asm "bswap $0", "=r,r"
Chris Lattner	e87d653	2006-01-25 23:47:57 +0000	[diff] [blame]	1809	</pre>
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	1810	</div>
Chris Lattner	e87d653	2006-01-25 23:47:57 +0000	[diff] [blame]	1811
				1812	<p>
				1813	Inline assembler expressions may <b>only</b> be used as the callee operand of
				1814	a <a href="#i_call"><tt>call</tt> instruction</a>. Thus, typically we have:
				1815	</p>
				1816
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	1817	<div class="doc_code">
Chris Lattner	e87d653	2006-01-25 23:47:57 +0000	[diff] [blame]	1818	<pre>
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	1819	%X = call i32 asm "<a href="#int_bswap">bswap</a> $0", "=r,r"(i32 %Y)
Chris Lattner	e87d653	2006-01-25 23:47:57 +0000	[diff] [blame]	1820	</pre>
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	1821	</div>
Chris Lattner	e87d653	2006-01-25 23:47:57 +0000	[diff] [blame]	1822
				1823	<p>
				1824	Inline asms with side effects not visible in the constraint list must be marked
				1825	as having side effects. This is done through the use of the
				1826	'<tt>sideeffect</tt>' keyword, like so:
				1827	</p>
				1828
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	1829	<div class="doc_code">
Chris Lattner	e87d653	2006-01-25 23:47:57 +0000	[diff] [blame]	1830	<pre>
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	1831	call void asm sideeffect "eieio", ""()
Chris Lattner	e87d653	2006-01-25 23:47:57 +0000	[diff] [blame]	1832	</pre>
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	1833	</div>
Chris Lattner	e87d653	2006-01-25 23:47:57 +0000	[diff] [blame]	1834
				1835	<p>TODO: The format of the asm and constraints string still need to be
				1836	documented here. Constraints on what can be done (e.g. duplication, moving, etc
				1837	need to be documented).
				1838	</p>
				1839
				1840	</div>
				1841
				1842	<!-- *********************************************************************** -->
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1843	<div class="doc_section"> <a name="instref">Instruction Reference</a> </div>
				1844	<!-- *********************************************************************** -->
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1845
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	1846	<div class="doc_text">
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1847
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1848	<p>The LLVM instruction set consists of several different
				1849	classifications of instructions: <a href="#terminators">terminator
John Criswell	c1f786c	2005-05-13 22:25:59 +0000	[diff] [blame]	1850	instructions</a>, <a href="#binaryops">binary instructions</a>,
				1851	<a href="#bitwiseops">bitwise binary instructions</a>, <a
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1852	href="#memoryops">memory instructions</a>, and <a href="#otherops">other
				1853	instructions</a>.</p>
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1854
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	1855	</div>
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1856
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1857	<!-- ======================================================================= -->
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1858	<div class="doc_subsection"> <a name="terminators">Terminator
				1859	Instructions</a> </div>
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1860
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	1861	<div class="doc_text">
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1862
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1863	<p>As mentioned <a href="#functionstructure">previously</a>, every
				1864	basic block in a program ends with a "Terminator" instruction, which
				1865	indicates which block should be executed after the current block is
				1866	finished. These terminator instructions typically yield a '<tt>void</tt>'
				1867	value: they produce control flow, not values (the one exception being
				1868	the '<a href="#i_invoke"><tt>invoke</tt></a>' instruction).</p>
John Criswell	9e2485c	2004-12-10 15:51:16 +0000	[diff] [blame]	1869	<p>There are six different terminator instructions: the '<a
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1870	href="#i_ret"><tt>ret</tt></a>' instruction, the '<a href="#i_br"><tt>br</tt></a>'
				1871	instruction, the '<a href="#i_switch"><tt>switch</tt></a>' instruction,
Chris Lattner	35eca58	2004-10-16 18:04:13 +0000	[diff] [blame]	1872	the '<a href="#i_invoke"><tt>invoke</tt></a>' instruction, the '<a
				1873	href="#i_unwind"><tt>unwind</tt></a>' instruction, and the '<a
				1874	href="#i_unreachable"><tt>unreachable</tt></a>' instruction.</p>
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1875
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	1876	</div>
Chris Lattner	c3f5976	2004-12-09 17:30:23 +0000	[diff] [blame]	1877
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1878	<!-- _______________________________________________________________________ -->
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1879	<div class="doc_subsubsection"> <a name="i_ret">'<tt>ret</tt>'
				1880	Instruction</a> </div>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	1881	<div class="doc_text">
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1882	<h5>Syntax:</h5>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1883	<pre> ret <type> <value> <i>; Return a value from a non-void function</i>
Chris Lattner	7faa883	2002-04-14 06:13:44 +0000	[diff] [blame]	1884	ret void <i>; Return from void function</i>
Devang Patel	c3fc6df	2008-03-10 20:49:15 +0000	[diff] [blame]	1885	ret <type> <value>, <type> <value> <i>; Return two values from a non-void function </i>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1886	</pre>
Chris Lattner	f4cde4e	2008-04-23 04:59:35 +0000	[diff] [blame]	1887
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1888	<h5>Overview:</h5>
Chris Lattner	f4cde4e	2008-04-23 04:59:35 +0000	[diff] [blame]	1889
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1890	<p>The '<tt>ret</tt>' instruction is used to return control flow (and a
John Criswell	c1f786c	2005-05-13 22:25:59 +0000	[diff] [blame]	1891	value) from a function back to the caller.</p>
John Criswell	4457dc9	2004-04-09 16:48:45 +0000	[diff] [blame]	1892	<p>There are two forms of the '<tt>ret</tt>' instruction: one that
Chris Lattner	f4cde4e	2008-04-23 04:59:35 +0000	[diff] [blame]	1893	returns value(s) and then causes control flow, and one that just causes
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1894	control flow to occur.</p>
Chris Lattner	f4cde4e	2008-04-23 04:59:35 +0000	[diff] [blame]	1895
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1896	<h5>Arguments:</h5>
Chris Lattner	f4cde4e	2008-04-23 04:59:35 +0000	[diff] [blame]	1897
				1898	<p>The '<tt>ret</tt>' instruction may return zero, one or multiple values.
				1899	The type of each return value must be a '<a href="#t_firstclass">first
				1900	class</a>' type. Note that a function is not <a href="#wellformed">well
				1901	formed</a> if there exists a '<tt>ret</tt>' instruction inside of the
				1902	function that returns values that do not match the return type of the
				1903	function.</p>
				1904
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1905	<h5>Semantics:</h5>
Chris Lattner	f4cde4e	2008-04-23 04:59:35 +0000	[diff] [blame]	1906
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1907	<p>When the '<tt>ret</tt>' instruction is executed, control flow
				1908	returns back to the calling function's context. If the caller is a "<a
John Criswell	fa08187	2004-06-25 15:16:57 +0000	[diff] [blame]	1909	href="#i_call"><tt>call</tt></a>" instruction, execution continues at
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1910	the instruction after the call. If the caller was an "<a
				1911	href="#i_invoke"><tt>invoke</tt></a>" instruction, execution continues
John Criswell	e4c57cc	2005-05-12 16:52:32 +0000	[diff] [blame]	1912	at the beginning of the "normal" destination block. If the instruction
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1913	returns a value, that value shall set the call or invoke instruction's
Devang Patel	c3fc6df	2008-03-10 20:49:15 +0000	[diff] [blame]	1914	return value. If the instruction returns multiple values then these
Devang Patel	0dbb4a1	2008-03-11 05:51:59 +0000	[diff] [blame]	1915	values can only be accessed through a '<a href="#i_getresult"><tt>getresult</tt>
				1916	</a>' instruction.</p>
Chris Lattner	f4cde4e	2008-04-23 04:59:35 +0000	[diff] [blame]	1917
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1918	<h5>Example:</h5>
Chris Lattner	f4cde4e	2008-04-23 04:59:35 +0000	[diff] [blame]	1919
				1920	<pre>
				1921	ret i32 5 <i>; Return an integer value of 5</i>
Chris Lattner	7faa883	2002-04-14 06:13:44 +0000	[diff] [blame]	1922	ret void <i>; Return from a void function</i>
Devang Patel	c3fc6df	2008-03-10 20:49:15 +0000	[diff] [blame]	1923	ret i32 4, i8 2 <i>; Return two values 4 and 2 </i>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1924	</pre>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	1925	</div>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1926	<!-- _______________________________________________________________________ -->
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1927	<div class="doc_subsubsection"> <a name="i_br">'<tt>br</tt>' Instruction</a> </div>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	1928	<div class="doc_text">
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1929	<h5>Syntax:</h5>
Reid Spencer	c78f337	2007-01-12 03:35:51 +0000	[diff] [blame]	1930	<pre> br i1 <cond>, label <iftrue>, label <iffalse><br> br label <dest> <i>; Unconditional branch</i>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1931	</pre>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1932	<h5>Overview:</h5>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1933	<p>The '<tt>br</tt>' instruction is used to cause control flow to
				1934	transfer to a different basic block in the current function. There are
				1935	two forms of this instruction, corresponding to a conditional branch
				1936	and an unconditional branch.</p>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1937	<h5>Arguments:</h5>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1938	<p>The conditional branch form of the '<tt>br</tt>' instruction takes a
Reid Spencer	c78f337	2007-01-12 03:35:51 +0000	[diff] [blame]	1939	single '<tt>i1</tt>' value and two '<tt>label</tt>' values. The
Reid Spencer	de15194	2007-02-19 23:54:10 +0000	[diff] [blame]	1940	unconditional form of the '<tt>br</tt>' instruction takes a single
				1941	'<tt>label</tt>' value as a target.</p>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1942	<h5>Semantics:</h5>
Reid Spencer	c78f337	2007-01-12 03:35:51 +0000	[diff] [blame]	1943	<p>Upon execution of a conditional '<tt>br</tt>' instruction, the '<tt>i1</tt>'
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1944	argument is evaluated. If the value is <tt>true</tt>, control flows
				1945	to the '<tt>iftrue</tt>' <tt>label</tt> argument. If "cond" is <tt>false</tt>,
				1946	control flows to the '<tt>iffalse</tt>' <tt>label</tt> argument.</p>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1947	<h5>Example:</h5>
Reid Spencer	c78f337	2007-01-12 03:35:51 +0000	[diff] [blame]	1948	<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 Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	1949	href="#i_ret">ret</a> i32 1<br>IfUnequal:<br> <a href="#i_ret">ret</a> i32 0<br></pre>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	1950	</div>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1951	<!-- _______________________________________________________________________ -->
Chris Lattner	c88c17b	2004-02-24 04:54:45 +0000	[diff] [blame]	1952	<div class="doc_subsubsection">
				1953	<a name="i_switch">'<tt>switch</tt>' Instruction</a>
				1954	</div>
				1955
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	1956	<div class="doc_text">
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1957	<h5>Syntax:</h5>
Chris Lattner	c88c17b	2004-02-24 04:54:45 +0000	[diff] [blame]	1958
				1959	<pre>
				1960	switch <intty> <value>, label <defaultdest> [ <intty> <val>, label <dest> ... ]
				1961	</pre>
				1962
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1963	<h5>Overview:</h5>
Chris Lattner	c88c17b	2004-02-24 04:54:45 +0000	[diff] [blame]	1964
				1965	<p>The '<tt>switch</tt>' instruction is used to transfer control flow to one of
				1966	several different places. It is a generalization of the '<tt>br</tt>'
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	1967	instruction, allowing a branch to occur to one of many possible
				1968	destinations.</p>
Chris Lattner	c88c17b	2004-02-24 04:54:45 +0000	[diff] [blame]	1969
				1970
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1971	<h5>Arguments:</h5>
Chris Lattner	c88c17b	2004-02-24 04:54:45 +0000	[diff] [blame]	1972
				1973	<p>The '<tt>switch</tt>' instruction uses three parameters: an integer
				1974	comparison value '<tt>value</tt>', a default '<tt>label</tt>' destination, and
				1975	an array of pairs of comparison value constants and '<tt>label</tt>'s. The
				1976	table is not allowed to contain duplicate constant entries.</p>
				1977
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1978	<h5>Semantics:</h5>
Chris Lattner	c88c17b	2004-02-24 04:54:45 +0000	[diff] [blame]	1979
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	1980	<p>The <tt>switch</tt> instruction specifies a table of values and
				1981	destinations. When the '<tt>switch</tt>' instruction is executed, this
John Criswell	8411475	2004-06-25 16:05:06 +0000	[diff] [blame]	1982	table is searched for the given value. If the value is found, control flow is
				1983	transfered to the corresponding destination; otherwise, control flow is
				1984	transfered to the default destination.</p>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	1985
Chris Lattner	c88c17b	2004-02-24 04:54:45 +0000	[diff] [blame]	1986	<h5>Implementation:</h5>
				1987
				1988	<p>Depending on properties of the target machine and the particular
				1989	<tt>switch</tt> instruction, this instruction may be code generated in different
John Criswell	8411475	2004-06-25 16:05:06 +0000	[diff] [blame]	1990	ways. For example, it could be generated as a series of chained conditional
				1991	branches or with a lookup table.</p>
Chris Lattner	c88c17b	2004-02-24 04:54:45 +0000	[diff] [blame]	1992
				1993	<h5>Example:</h5>
				1994
				1995	<pre>
				1996	<i>; Emulate a conditional br instruction</i>
Reid Spencer	c78f337	2007-01-12 03:35:51 +0000	[diff] [blame]	1997	%Val = <a href="#i_zext">zext</a> i1 %value to i32
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	1998	switch i32 %Val, label %truedest [i32 0, label %falsedest ]
Chris Lattner	c88c17b	2004-02-24 04:54:45 +0000	[diff] [blame]	1999
				2000	<i>; Emulate an unconditional br instruction</i>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	2001	switch i32 0, label %dest [ ]
Chris Lattner	c88c17b	2004-02-24 04:54:45 +0000	[diff] [blame]	2002
				2003	<i>; Implement a jump table:</i>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	2004	switch i32 %val, label %otherwise [ i32 0, label %onzero
				2005	i32 1, label %onone
				2006	i32 2, label %ontwo ]
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2007	</pre>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	2008	</div>
Chris Lattner	bad10ee	2005-05-06 22:57:40 +0000	[diff] [blame]	2009
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2010	<!-- _______________________________________________________________________ -->
Chris Lattner	bad10ee	2005-05-06 22:57:40 +0000	[diff] [blame]	2011	<div class="doc_subsubsection">
				2012	<a name="i_invoke">'<tt>invoke</tt>' Instruction</a>
				2013	</div>
				2014
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	2015	<div class="doc_text">
Chris Lattner	bad10ee	2005-05-06 22:57:40 +0000	[diff] [blame]	2016
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2017	<h5>Syntax:</h5>
Chris Lattner	bad10ee	2005-05-06 22:57:40 +0000	[diff] [blame]	2018
				2019	<pre>
Nick Lewycky	d703f65	2008-03-16 07:18:12 +0000	[diff] [blame]	2020	<result> = invoke [<a href="#callingconv">cconv</a>] <ptr to function ty> <function ptr val>(<function args>)
Chris Lattner	76b8a33	2006-05-14 18:23:06 +0000	[diff] [blame]	2021	to label <normal label> unwind label <exception label>
Chris Lattner	bad10ee	2005-05-06 22:57:40 +0000	[diff] [blame]	2022	</pre>
				2023
Chris Lattner	6536cfe	2002-05-06 22:08:29 +0000	[diff] [blame]	2024	<h5>Overview:</h5>
Chris Lattner	bad10ee	2005-05-06 22:57:40 +0000	[diff] [blame]	2025
				2026	<p>The '<tt>invoke</tt>' instruction causes control to transfer to a specified
				2027	function, with the possibility of control flow transfer to either the
John Criswell	e4c57cc	2005-05-12 16:52:32 +0000	[diff] [blame]	2028	'<tt>normal</tt>' label or the
				2029	'<tt>exception</tt>' label. If the callee function returns with the
Chris Lattner	bad10ee	2005-05-06 22:57:40 +0000	[diff] [blame]	2030	"<tt><a href="#i_ret">ret</a></tt>" instruction, control flow will return to the
				2031	"normal" label. If the callee (or any indirect callees) returns with the "<a
John Criswell	e4c57cc	2005-05-12 16:52:32 +0000	[diff] [blame]	2032	href="#i_unwind"><tt>unwind</tt></a>" instruction, control is interrupted and
Devang Patel	c3fc6df	2008-03-10 20:49:15 +0000	[diff] [blame]	2033	continued at the dynamically nearest "exception" label. If the callee function
Devang Patel	0dbb4a1	2008-03-11 05:51:59 +0000	[diff] [blame]	2034	returns multiple values then individual return values are only accessible through
				2035	a '<tt><a href="#i_getresult">getresult</a></tt>' instruction.</p>
Chris Lattner	bad10ee	2005-05-06 22:57:40 +0000	[diff] [blame]	2036
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2037	<h5>Arguments:</h5>
Chris Lattner	bad10ee	2005-05-06 22:57:40 +0000	[diff] [blame]	2038
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	2039	<p>This instruction requires several arguments:</p>
Chris Lattner	bad10ee	2005-05-06 22:57:40 +0000	[diff] [blame]	2040
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2041	<ol>
Chris Lattner	bad10ee	2005-05-06 22:57:40 +0000	[diff] [blame]	2042	<li>
Duncan Sands	8036ca4	2007-03-30 12:22:09 +0000	[diff] [blame]	2043	The optional "cconv" marker indicates which <a href="#callingconv">calling
Chris Lattner	bad10ee	2005-05-06 22:57:40 +0000	[diff] [blame]	2044	convention</a> the call should use. If none is specified, the call defaults
				2045	to using C calling conventions.
				2046	</li>
				2047	<li>'<tt>ptr to function ty</tt>': shall be the signature of the pointer to
				2048	function value being invoked. In most cases, this is a direct function
				2049	invocation, but indirect <tt>invoke</tt>s are just as possible, branching off
				2050	an arbitrary pointer to function value.
				2051	</li>
				2052
				2053	<li>'<tt>function ptr val</tt>': An LLVM value containing a pointer to a
				2054	function to be invoked. </li>
				2055
				2056	<li>'<tt>function args</tt>': argument list whose types match the function
				2057	signature argument types. If the function signature indicates the function
				2058	accepts a variable number of arguments, the extra arguments can be
				2059	specified. </li>
				2060
				2061	<li>'<tt>normal label</tt>': the label reached when the called function
				2062	executes a '<tt><a href="#i_ret">ret</a></tt>' instruction. </li>
				2063
				2064	<li>'<tt>exception label</tt>': the label reached when a callee returns with
				2065	the <a href="#i_unwind"><tt>unwind</tt></a> instruction. </li>
				2066
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2067	</ol>
Chris Lattner	bad10ee	2005-05-06 22:57:40 +0000	[diff] [blame]	2068
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2069	<h5>Semantics:</h5>
Chris Lattner	bad10ee	2005-05-06 22:57:40 +0000	[diff] [blame]	2070
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	2071	<p>This instruction is designed to operate as a standard '<tt><a
Chris Lattner	bad10ee	2005-05-06 22:57:40 +0000	[diff] [blame]	2072	href="#i_call">call</a></tt>' instruction in most regards. The primary
				2073	difference is that it establishes an association with a label, which is used by
				2074	the runtime library to unwind the stack.</p>
				2075
				2076	<p>This instruction is used in languages with destructors to ensure that proper
				2077	cleanup is performed in the case of either a <tt>longjmp</tt> or a thrown
				2078	exception. Additionally, this is important for implementation of
				2079	'<tt>catch</tt>' clauses in high-level languages that support them.</p>
				2080
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2081	<h5>Example:</h5>
Chris Lattner	bad10ee	2005-05-06 22:57:40 +0000	[diff] [blame]	2082	<pre>
Nick Lewycky	d703f65	2008-03-16 07:18:12 +0000	[diff] [blame]	2083	%retval = invoke i32 @Test(i32 15) to label %Continue
Jeff Cohen	6f1cc77	2007-04-22 01:17:39 +0000	[diff] [blame]	2084	unwind label %TestCleanup <i>; {i32}:retval set</i>
Nick Lewycky	d703f65	2008-03-16 07:18:12 +0000	[diff] [blame]	2085	%retval = invoke <a href="#callingconv">coldcc</a> i32 %Testfnptr(i32 15) to label %Continue
Jeff Cohen	6f1cc77	2007-04-22 01:17:39 +0000	[diff] [blame]	2086	unwind label %TestCleanup <i>; {i32}:retval set</i>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2087	</pre>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	2088	</div>
Chris Lattner	35eca58	2004-10-16 18:04:13 +0000	[diff] [blame]	2089
				2090
Chris Lattner	27f71f2	2003-09-03 00:41:47 +0000	[diff] [blame]	2091	<!-- _______________________________________________________________________ -->
Chris Lattner	35eca58	2004-10-16 18:04:13 +0000	[diff] [blame]	2092
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	2093	<div class="doc_subsubsection"> <a name="i_unwind">'<tt>unwind</tt>'
				2094	Instruction</a> </div>
Chris Lattner	35eca58	2004-10-16 18:04:13 +0000	[diff] [blame]	2095
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	2096	<div class="doc_text">
Chris Lattner	35eca58	2004-10-16 18:04:13 +0000	[diff] [blame]	2097
Chris Lattner	27f71f2	2003-09-03 00:41:47 +0000	[diff] [blame]	2098	<h5>Syntax:</h5>
Chris Lattner	35eca58	2004-10-16 18:04:13 +0000	[diff] [blame]	2099	<pre>
				2100	unwind
				2101	</pre>
				2102
Chris Lattner	27f71f2	2003-09-03 00:41:47 +0000	[diff] [blame]	2103	<h5>Overview:</h5>
Chris Lattner	35eca58	2004-10-16 18:04:13 +0000	[diff] [blame]	2104
				2105	<p>The '<tt>unwind</tt>' instruction unwinds the stack, continuing control flow
				2106	at the first callee in the dynamic call stack which used an <a
				2107	href="#i_invoke"><tt>invoke</tt></a> instruction to perform the call. This is
				2108	primarily used to implement exception handling.</p>
				2109
Chris Lattner	27f71f2	2003-09-03 00:41:47 +0000	[diff] [blame]	2110	<h5>Semantics:</h5>
Chris Lattner	35eca58	2004-10-16 18:04:13 +0000	[diff] [blame]	2111
Chris Lattner	72ed200	2008-04-19 21:01:16 +0000	[diff] [blame]	2112	<p>The '<tt>unwind</tt>' instruction causes execution of the current function to
Chris Lattner	35eca58	2004-10-16 18:04:13 +0000	[diff] [blame]	2113	immediately halt. The dynamic call stack is then searched for the first <a
				2114	href="#i_invoke"><tt>invoke</tt></a> instruction on the call stack. Once found,
				2115	execution continues at the "exceptional" destination block specified by the
				2116	<tt>invoke</tt> instruction. If there is no <tt>invoke</tt> instruction in the
				2117	dynamic call chain, undefined behavior results.</p>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	2118	</div>
Chris Lattner	35eca58	2004-10-16 18:04:13 +0000	[diff] [blame]	2119
				2120	<!-- _______________________________________________________________________ -->
				2121
				2122	<div class="doc_subsubsection"> <a name="i_unreachable">'<tt>unreachable</tt>'
				2123	Instruction</a> </div>
				2124
				2125	<div class="doc_text">
				2126
				2127	<h5>Syntax:</h5>
				2128	<pre>
				2129	unreachable
				2130	</pre>
				2131
				2132	<h5>Overview:</h5>
				2133
				2134	<p>The '<tt>unreachable</tt>' instruction has no defined semantics. This
				2135	instruction is used to inform the optimizer that a particular portion of the
				2136	code is not reachable. This can be used to indicate that the code after a
				2137	no-return function cannot be reached, and other facts.</p>
				2138
				2139	<h5>Semantics:</h5>
				2140
				2141	<p>The '<tt>unreachable</tt>' instruction has no defined semantics.</p>
				2142	</div>
				2143
				2144
				2145
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2146	<!-- ======================================================================= -->
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	2147	<div class="doc_subsection"> <a name="binaryops">Binary Operations</a> </div>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	2148	<div class="doc_text">
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	2149	<p>Binary operators are used to do most of the computation in a
Chris Lattner	5a15814	2008-04-01 18:47:32 +0000	[diff] [blame]	2150	program. They require two operands of the same type, execute an operation on them, and
John Criswell	9e2485c	2004-12-10 15:51:16 +0000	[diff] [blame]	2151	produce a single value. The operands might represent
Reid Spencer	485bad1	2007-02-15 03:07:05 +0000	[diff] [blame]	2152	multiple data, as is the case with the <a href="#t_vector">vector</a> data type.
Chris Lattner	5a15814	2008-04-01 18:47:32 +0000	[diff] [blame]	2153	The result value has the same type as its operands.</p>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	2154	<p>There are several different binary operators:</p>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	2155	</div>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2156	<!-- _______________________________________________________________________ -->
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2157	<div class="doc_subsubsection">
				2158	<a name="i_add">'<tt>add</tt>' Instruction</a>
				2159	</div>
				2160
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	2161	<div class="doc_text">
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2162
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2163	<h5>Syntax:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2164
				2165	<pre>
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	2166	<result> = add <ty> <op1>, <op2> <i>; yields {ty}:result</i>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2167	</pre>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2168
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2169	<h5>Overview:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2170
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	2171	<p>The '<tt>add</tt>' instruction returns the sum of its two operands.</p>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2172
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2173	<h5>Arguments:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2174
				2175	<p>The two arguments to the '<tt>add</tt>' instruction must be <a
				2176	href="#t_integer">integer</a>, <a href="#t_floating">floating point</a>, or
				2177	<a href="#t_vector">vector</a> values. Both arguments must have identical
				2178	types.</p>
				2179
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2180	<h5>Semantics:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2181
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	2182	<p>The value produced is the integer or floating point sum of the two
				2183	operands.</p>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2184
Chris Lattner	5ec8983	2008-01-28 00:36:27 +0000	[diff] [blame]	2185	<p>If an integer sum has unsigned overflow, the result returned is the
				2186	mathematical result modulo 2<sup>n</sup>, where n is the bit width of
				2187	the result.</p>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2188
Chris Lattner	5ec8983	2008-01-28 00:36:27 +0000	[diff] [blame]	2189	<p>Because LLVM integers use a two's complement representation, this
				2190	instruction is appropriate for both signed and unsigned integers.</p>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2191
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2192	<h5>Example:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2193
				2194	<pre>
				2195	<result> = add i32 4, %var <i>; yields {i32}:result = 4 + %var</i>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2196	</pre>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	2197	</div>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2198	<!-- _______________________________________________________________________ -->
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2199	<div class="doc_subsubsection">
				2200	<a name="i_sub">'<tt>sub</tt>' Instruction</a>
				2201	</div>
				2202
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	2203	<div class="doc_text">
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2204
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2205	<h5>Syntax:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2206
				2207	<pre>
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	2208	<result> = sub <ty> <op1>, <op2> <i>; yields {ty}:result</i>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2209	</pre>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2210
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2211	<h5>Overview:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2212
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	2213	<p>The '<tt>sub</tt>' instruction returns the difference of its two
				2214	operands.</p>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2215
				2216	<p>Note that the '<tt>sub</tt>' instruction is used to represent the
				2217	'<tt>neg</tt>' instruction present in most other intermediate
				2218	representations.</p>
				2219
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2220	<h5>Arguments:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2221
				2222	<p>The two arguments to the '<tt>sub</tt>' instruction must be <a
				2223	href="#t_integer">integer</a>, <a href="#t_floating">floating point</a>,
				2224	or <a href="#t_vector">vector</a> values. Both arguments must have identical
				2225	types.</p>
				2226
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2227	<h5>Semantics:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2228
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	2229	<p>The value produced is the integer or floating point difference of
				2230	the two operands.</p>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2231
Chris Lattner	5ec8983	2008-01-28 00:36:27 +0000	[diff] [blame]	2232	<p>If an integer difference has unsigned overflow, the result returned is the
				2233	mathematical result modulo 2<sup>n</sup>, where n is the bit width of
				2234	the result.</p>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2235
Chris Lattner	5ec8983	2008-01-28 00:36:27 +0000	[diff] [blame]	2236	<p>Because LLVM integers use a two's complement representation, this
				2237	instruction is appropriate for both signed and unsigned integers.</p>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2238
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2239	<h5>Example:</h5>
Bill Wendling	aac388b	2007-05-29 09:42:13 +0000	[diff] [blame]	2240	<pre>
				2241	<result> = sub i32 4, %var <i>; yields {i32}:result = 4 - %var</i>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	2242	<result> = sub i32 0, %val <i>; yields {i32}:result = -%var</i>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2243	</pre>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	2244	</div>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2245
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2246	<!-- _______________________________________________________________________ -->
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2247	<div class="doc_subsubsection">
				2248	<a name="i_mul">'<tt>mul</tt>' Instruction</a>
				2249	</div>
				2250
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	2251	<div class="doc_text">
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2252
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2253	<h5>Syntax:</h5>
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	2254	<pre> <result> = mul <ty> <op1>, <op2> <i>; yields {ty}:result</i>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2255	</pre>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2256	<h5>Overview:</h5>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	2257	<p>The '<tt>mul</tt>' instruction returns the product of its two
				2258	operands.</p>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2259
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2260	<h5>Arguments:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2261
				2262	<p>The two arguments to the '<tt>mul</tt>' instruction must be <a
				2263	href="#t_integer">integer</a>, <a href="#t_floating">floating point</a>,
				2264	or <a href="#t_vector">vector</a> values. Both arguments must have identical
				2265	types.</p>
				2266
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2267	<h5>Semantics:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2268
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	2269	<p>The value produced is the integer or floating point product of the
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	2270	two operands.</p>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2271
Chris Lattner	5ec8983	2008-01-28 00:36:27 +0000	[diff] [blame]	2272	<p>If the result of an integer multiplication has unsigned overflow,
				2273	the result returned is the mathematical result modulo
				2274	2<sup>n</sup>, where n is the bit width of the result.</p>
				2275	<p>Because LLVM integers use a two's complement representation, and the
				2276	result is the same width as the operands, this instruction returns the
				2277	correct result for both signed and unsigned integers. If a full product
				2278	(e.g. <tt>i32</tt>x<tt>i32</tt>-><tt>i64</tt>) is needed, the operands
				2279	should be sign-extended or zero-extended as appropriate to the
				2280	width of the full product.</p>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2281	<h5>Example:</h5>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	2282	<pre> <result> = mul i32 4, %var <i>; yields {i32}:result = 4 * %var</i>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2283	</pre>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	2284	</div>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2285
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2286	<!-- _______________________________________________________________________ -->
Reid Spencer	1628cec	2006-10-26 06:15:43 +0000	[diff] [blame]	2287	<div class="doc_subsubsection"> <a name="i_udiv">'<tt>udiv</tt>' Instruction
				2288	</a></div>
				2289	<div class="doc_text">
				2290	<h5>Syntax:</h5>
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	2291	<pre> <result> = udiv <ty> <op1>, <op2> <i>; yields {ty}:result</i>
Reid Spencer	1628cec	2006-10-26 06:15:43 +0000	[diff] [blame]	2292	</pre>
				2293	<h5>Overview:</h5>
				2294	<p>The '<tt>udiv</tt>' instruction returns the quotient of its two
				2295	operands.</p>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2296
Reid Spencer	1628cec	2006-10-26 06:15:43 +0000	[diff] [blame]	2297	<h5>Arguments:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2298
Reid Spencer	1628cec	2006-10-26 06:15:43 +0000	[diff] [blame]	2299	<p>The two arguments to the '<tt>udiv</tt>' instruction must be
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2300	<a href="#t_integer">integer</a> or <a href="#t_vector">vector</a> of integer
				2301	values. Both arguments must have identical types.</p>
				2302
Reid Spencer	1628cec	2006-10-26 06:15:43 +0000	[diff] [blame]	2303	<h5>Semantics:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2304
Chris Lattner	5ec8983	2008-01-28 00:36:27 +0000	[diff] [blame]	2305	<p>The value produced is the unsigned integer quotient of the two operands.</p>
				2306	<p>Note that unsigned integer division and signed integer division are distinct
				2307	operations; for signed integer division, use '<tt>sdiv</tt>'.</p>
				2308	<p>Division by zero leads to undefined behavior.</p>
Reid Spencer	1628cec	2006-10-26 06:15:43 +0000	[diff] [blame]	2309	<h5>Example:</h5>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	2310	<pre> <result> = udiv i32 4, %var <i>; yields {i32}:result = 4 / %var</i>
Reid Spencer	1628cec	2006-10-26 06:15:43 +0000	[diff] [blame]	2311	</pre>
				2312	</div>
				2313	<!-- _______________________________________________________________________ -->
				2314	<div class="doc_subsubsection"> <a name="i_sdiv">'<tt>sdiv</tt>' Instruction
				2315	</a> </div>
				2316	<div class="doc_text">
				2317	<h5>Syntax:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2318	<pre>
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	2319	<result> = sdiv <ty> <op1>, <op2> <i>; yields {ty}:result</i>
Reid Spencer	1628cec	2006-10-26 06:15:43 +0000	[diff] [blame]	2320	</pre>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2321
Reid Spencer	1628cec	2006-10-26 06:15:43 +0000	[diff] [blame]	2322	<h5>Overview:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2323
Reid Spencer	1628cec	2006-10-26 06:15:43 +0000	[diff] [blame]	2324	<p>The '<tt>sdiv</tt>' instruction returns the quotient of its two
				2325	operands.</p>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2326
Reid Spencer	1628cec	2006-10-26 06:15:43 +0000	[diff] [blame]	2327	<h5>Arguments:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2328
				2329	<p>The two arguments to the '<tt>sdiv</tt>' instruction must be
				2330	<a href="#t_integer">integer</a> or <a href="#t_vector">vector</a> of integer
				2331	values. Both arguments must have identical types.</p>
				2332
Reid Spencer	1628cec	2006-10-26 06:15:43 +0000	[diff] [blame]	2333	<h5>Semantics:</h5>
Chris Lattner	a73afe0	2008-04-01 18:45:27 +0000	[diff] [blame]	2334	<p>The value produced is the signed integer quotient of the two operands rounded towards zero.</p>
Chris Lattner	5ec8983	2008-01-28 00:36:27 +0000	[diff] [blame]	2335	<p>Note that signed integer division and unsigned integer division are distinct
				2336	operations; for unsigned integer division, use '<tt>udiv</tt>'.</p>
				2337	<p>Division by zero leads to undefined behavior. Overflow also leads to
				2338	undefined behavior; this is a rare case, but can occur, for example,
				2339	by doing a 32-bit division of -2147483648 by -1.</p>
Reid Spencer	1628cec	2006-10-26 06:15:43 +0000	[diff] [blame]	2340	<h5>Example:</h5>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	2341	<pre> <result> = sdiv i32 4, %var <i>; yields {i32}:result = 4 / %var</i>
Reid Spencer	1628cec	2006-10-26 06:15:43 +0000	[diff] [blame]	2342	</pre>
				2343	</div>
				2344	<!-- _______________________________________________________________________ -->
				2345	<div class="doc_subsubsection"> <a name="i_fdiv">'<tt>fdiv</tt>'
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	2346	Instruction</a> </div>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	2347	<div class="doc_text">
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2348	<h5>Syntax:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2349	<pre>
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	2350	<result> = fdiv <ty> <op1>, <op2> <i>; yields {ty}:result</i>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	2351	</pre>
				2352	<h5>Overview:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2353
Reid Spencer	1628cec	2006-10-26 06:15:43 +0000	[diff] [blame]	2354	<p>The '<tt>fdiv</tt>' instruction returns the quotient of its two
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	2355	operands.</p>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2356
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	2357	<h5>Arguments:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2358
Jeff Cohen	6f1cc77	2007-04-22 01:17:39 +0000	[diff] [blame]	2359	<p>The two arguments to the '<tt>fdiv</tt>' instruction must be
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2360	<a href="#t_floating">floating point</a> or <a href="#t_vector">vector</a>
				2361	of floating point values. Both arguments must have identical types.</p>
				2362
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	2363	<h5>Semantics:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2364
Reid Spencer	1628cec	2006-10-26 06:15:43 +0000	[diff] [blame]	2365	<p>The value produced is the floating point quotient of the two operands.</p>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2366
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	2367	<h5>Example:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2368
				2369	<pre>
				2370	<result> = fdiv float 4.0, %var <i>; yields {float}:result = 4.0 / %var</i>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	2371	</pre>
				2372	</div>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2373
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	2374	<!-- _______________________________________________________________________ -->
Reid Spencer	0a783f7	2006-11-02 01:53:59 +0000	[diff] [blame]	2375	<div class="doc_subsubsection"> <a name="i_urem">'<tt>urem</tt>' Instruction</a>
				2376	</div>
				2377	<div class="doc_text">
				2378	<h5>Syntax:</h5>
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	2379	<pre> <result> = urem <ty> <op1>, <op2> <i>; yields {ty}:result</i>
Reid Spencer	0a783f7	2006-11-02 01:53:59 +0000	[diff] [blame]	2380	</pre>
				2381	<h5>Overview:</h5>
				2382	<p>The '<tt>urem</tt>' instruction returns the remainder from the
				2383	unsigned division of its two arguments.</p>
				2384	<h5>Arguments:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2385	<p>The two arguments to the '<tt>urem</tt>' instruction must be
				2386	<a href="#t_integer">integer</a> or <a href="#t_vector">vector</a> of integer
				2387	values. Both arguments must have identical types.</p>
Reid Spencer	0a783f7	2006-11-02 01:53:59 +0000	[diff] [blame]	2388	<h5>Semantics:</h5>
				2389	<p>This instruction returns the unsigned integer <i>remainder</i> of a division.
Chris Lattner	a73afe0	2008-04-01 18:45:27 +0000	[diff] [blame]	2390	This instruction always performs an unsigned division to get the remainder.</p>
Chris Lattner	5ec8983	2008-01-28 00:36:27 +0000	[diff] [blame]	2391	<p>Note that unsigned integer remainder and signed integer remainder are
				2392	distinct operations; for signed integer remainder, use '<tt>srem</tt>'.</p>
				2393	<p>Taking the remainder of a division by zero leads to undefined behavior.</p>
Reid Spencer	0a783f7	2006-11-02 01:53:59 +0000	[diff] [blame]	2394	<h5>Example:</h5>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	2395	<pre> <result> = urem i32 4, %var <i>; yields {i32}:result = 4 % %var</i>
Reid Spencer	0a783f7	2006-11-02 01:53:59 +0000	[diff] [blame]	2396	</pre>
				2397
				2398	</div>
				2399	<!-- _______________________________________________________________________ -->
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2400	<div class="doc_subsubsection">
				2401	<a name="i_srem">'<tt>srem</tt>' Instruction</a>
				2402	</div>
				2403
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	2404	<div class="doc_text">
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2405
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	2406	<h5>Syntax:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2407
				2408	<pre>
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	2409	<result> = srem <ty> <op1>, <op2> <i>; yields {ty}:result</i>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	2410	</pre>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2411
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	2412	<h5>Overview:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2413
Reid Spencer	0a783f7	2006-11-02 01:53:59 +0000	[diff] [blame]	2414	<p>The '<tt>srem</tt>' instruction returns the remainder from the
Dan Gohman	8017631	2007-11-05 23:35:22 +0000	[diff] [blame]	2415	signed division of its two operands. This instruction can also take
				2416	<a href="#t_vector">vector</a> versions of the values in which case
				2417	the elements must be integers.</p>
Chris Lattner	c7d3ab3	2008-01-04 04:33:49 +0000	[diff] [blame]	2418
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	2419	<h5>Arguments:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2420
Reid Spencer	0a783f7	2006-11-02 01:53:59 +0000	[diff] [blame]	2421	<p>The two arguments to the '<tt>srem</tt>' instruction must be
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2422	<a href="#t_integer">integer</a> or <a href="#t_vector">vector</a> of integer
				2423	values. Both arguments must have identical types.</p>
				2424
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	2425	<h5>Semantics:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2426
Reid Spencer	0a783f7	2006-11-02 01:53:59 +0000	[diff] [blame]	2427	<p>This instruction returns the <i>remainder</i> of a division (where the result
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	2428	has the same sign as the dividend, <tt>op1</tt>), not the <i>modulo</i>
				2429	operator (where the result has the same sign as the divisor, <tt>op2</tt>) of
Reid Spencer	c9fdfc8	2007-03-24 22:23:39 +0000	[diff] [blame]	2430	a value. For more information about the difference, see <a
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	2431	href="http://mathforum.org/dr.math/problems/anne.4.28.99.html">The
Reid Spencer	c9fdfc8	2007-03-24 22:23:39 +0000	[diff] [blame]	2432	Math Forum</a>. For a table of how this is implemented in various languages,
Reid Spencer	64f5c6c	2007-03-24 22:40:44 +0000	[diff] [blame]	2433	please see <a href="http://en.wikipedia.org/wiki/Modulo_operation">
Reid Spencer	c9fdfc8	2007-03-24 22:23:39 +0000	[diff] [blame]	2434	Wikipedia: modulo operation</a>.</p>
Chris Lattner	5ec8983	2008-01-28 00:36:27 +0000	[diff] [blame]	2435	<p>Note that signed integer remainder and unsigned integer remainder are
				2436	distinct operations; for unsigned integer remainder, use '<tt>urem</tt>'.</p>
				2437	<p>Taking the remainder of a division by zero leads to undefined behavior.
				2438	Overflow also leads to undefined behavior; this is a rare case, but can occur,
				2439	for example, by taking the remainder of a 32-bit division of -2147483648 by -1.
				2440	(The remainder doesn't actually overflow, but this rule lets srem be
				2441	implemented using instructions that return both the result of the division
				2442	and the remainder.)</p>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	2443	<h5>Example:</h5>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	2444	<pre> <result> = srem i32 4, %var <i>; yields {i32}:result = 4 % %var</i>
Reid Spencer	0a783f7	2006-11-02 01:53:59 +0000	[diff] [blame]	2445	</pre>
				2446
				2447	</div>
				2448	<!-- _______________________________________________________________________ -->
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2449	<div class="doc_subsubsection">
				2450	<a name="i_frem">'<tt>frem</tt>' Instruction</a> </div>
				2451
Reid Spencer	0a783f7	2006-11-02 01:53:59 +0000	[diff] [blame]	2452	<div class="doc_text">
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2453
Reid Spencer	0a783f7	2006-11-02 01:53:59 +0000	[diff] [blame]	2454	<h5>Syntax:</h5>
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	2455	<pre> <result> = frem <ty> <op1>, <op2> <i>; yields {ty}:result</i>
Reid Spencer	0a783f7	2006-11-02 01:53:59 +0000	[diff] [blame]	2456	</pre>
				2457	<h5>Overview:</h5>
				2458	<p>The '<tt>frem</tt>' instruction returns the remainder from the
				2459	division of its two operands.</p>
				2460	<h5>Arguments:</h5>
				2461	<p>The two arguments to the '<tt>frem</tt>' instruction must be
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2462	<a href="#t_floating">floating point</a> or <a href="#t_vector">vector</a>
				2463	of floating point values. Both arguments must have identical types.</p>
				2464
Reid Spencer	0a783f7	2006-11-02 01:53:59 +0000	[diff] [blame]	2465	<h5>Semantics:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2466
Chris Lattner	a73afe0	2008-04-01 18:45:27 +0000	[diff] [blame]	2467	<p>This instruction returns the <i>remainder</i> of a division.
				2468	The remainder has the same sign as the dividend.</p>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2469
Reid Spencer	0a783f7	2006-11-02 01:53:59 +0000	[diff] [blame]	2470	<h5>Example:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2471
				2472	<pre>
				2473	<result> = frem float 4.0, %var <i>; yields {float}:result = 4.0 % %var</i>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	2474	</pre>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	2475	</div>
Robert Bocchino	7b81c75	2006-02-17 21:18:08 +0000	[diff] [blame]	2476
Reid Spencer	8e11bf8	2007-02-02 13:57:07 +0000	[diff] [blame]	2477	<!-- ======================================================================= -->
				2478	<div class="doc_subsection"> <a name="bitwiseops">Bitwise Binary
				2479	Operations</a> </div>
				2480	<div class="doc_text">
				2481	<p>Bitwise binary operators are used to do various forms of
				2482	bit-twiddling in a program. They are generally very efficient
				2483	instructions and can commonly be strength reduced from other
Chris Lattner	a73afe0	2008-04-01 18:45:27 +0000	[diff] [blame]	2484	instructions. They require two operands of the same type, execute an operation on them,
				2485	and produce a single value. The resulting value is the same type as its operands.</p>
Reid Spencer	8e11bf8	2007-02-02 13:57:07 +0000	[diff] [blame]	2486	</div>
				2487
Reid Spencer	569f2fa	2007-01-31 21:39:12 +0000	[diff] [blame]	2488	<!-- _______________________________________________________________________ -->
				2489	<div class="doc_subsubsection"> <a name="i_shl">'<tt>shl</tt>'
				2490	Instruction</a> </div>
				2491	<div class="doc_text">
				2492	<h5>Syntax:</h5>
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	2493	<pre> <result> = shl <ty> <op1>, <op2> <i>; yields {ty}:result</i>
Reid Spencer	569f2fa	2007-01-31 21:39:12 +0000	[diff] [blame]	2494	</pre>
Chris Lattner	6ccc2d5	2007-10-03 21:01:14 +0000	[diff] [blame]	2495
Reid Spencer	569f2fa	2007-01-31 21:39:12 +0000	[diff] [blame]	2496	<h5>Overview:</h5>
Chris Lattner	6ccc2d5	2007-10-03 21:01:14 +0000	[diff] [blame]	2497
Reid Spencer	569f2fa	2007-01-31 21:39:12 +0000	[diff] [blame]	2498	<p>The '<tt>shl</tt>' instruction returns the first operand shifted to
				2499	the left a specified number of bits.</p>
Chris Lattner	6ccc2d5	2007-10-03 21:01:14 +0000	[diff] [blame]	2500
Reid Spencer	569f2fa	2007-01-31 21:39:12 +0000	[diff] [blame]	2501	<h5>Arguments:</h5>
Chris Lattner	6ccc2d5	2007-10-03 21:01:14 +0000	[diff] [blame]	2502
Reid Spencer	569f2fa	2007-01-31 21:39:12 +0000	[diff] [blame]	2503	<p>Both arguments to the '<tt>shl</tt>' instruction must be the same <a
Nate Begeman	5bc1ea0	2008-07-29 15:49:41 +0000	[diff] [blame]	2504	href="#t_integer">integer</a> or <a href="#t_vector">vector</a> of integer
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	2505	type. '<tt>op2</tt>' is treated as an unsigned value.</p>
Chris Lattner	6ccc2d5	2007-10-03 21:01:14 +0000	[diff] [blame]	2506
Reid Spencer	569f2fa	2007-01-31 21:39:12 +0000	[diff] [blame]	2507	<h5>Semantics:</h5>
Chris Lattner	6ccc2d5	2007-10-03 21:01:14 +0000	[diff] [blame]	2508
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	2509	<p>The value produced is <tt>op1</tt> * 2<sup><tt>op2</tt></sup> mod 2<sup>n</sup>,
				2510	where n is the width of the result. If <tt>op2</tt> is (statically or dynamically) negative or
				2511	equal to or larger than the number of bits in <tt>op1</tt>, the result is undefined.</p>
Chris Lattner	6ccc2d5	2007-10-03 21:01:14 +0000	[diff] [blame]	2512
Reid Spencer	569f2fa	2007-01-31 21:39:12 +0000	[diff] [blame]	2513	<h5>Example:</h5><pre>
				2514	<result> = shl i32 4, %var <i>; yields {i32}: 4 << %var</i>
				2515	<result> = shl i32 4, 2 <i>; yields {i32}: 16</i>
				2516	<result> = shl i32 1, 10 <i>; yields {i32}: 1024</i>
Chris Lattner	6ccc2d5	2007-10-03 21:01:14 +0000	[diff] [blame]	2517	<result> = shl i32 1, 32 <i>; undefined</i>
Reid Spencer	569f2fa	2007-01-31 21:39:12 +0000	[diff] [blame]	2518	</pre>
				2519	</div>
				2520	<!-- _______________________________________________________________________ -->
				2521	<div class="doc_subsubsection"> <a name="i_lshr">'<tt>lshr</tt>'
				2522	Instruction</a> </div>
				2523	<div class="doc_text">
				2524	<h5>Syntax:</h5>
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	2525	<pre> <result> = lshr <ty> <op1>, <op2> <i>; yields {ty}:result</i>
Reid Spencer	569f2fa	2007-01-31 21:39:12 +0000	[diff] [blame]	2526	</pre>
				2527
				2528	<h5>Overview:</h5>
				2529	<p>The '<tt>lshr</tt>' instruction (logical shift right) returns the first
Jeff Cohen	6f1cc77	2007-04-22 01:17:39 +0000	[diff] [blame]	2530	operand shifted to the right a specified number of bits with zero fill.</p>
Reid Spencer	569f2fa	2007-01-31 21:39:12 +0000	[diff] [blame]	2531
				2532	<h5>Arguments:</h5>
				2533	<p>Both arguments to the '<tt>lshr</tt>' instruction must be the same
Nate Begeman	5bc1ea0	2008-07-29 15:49:41 +0000	[diff] [blame]	2534	<a href="#t_integer">integer</a> or <a href="#t_vector">vector</a> of integer
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	2535	type. '<tt>op2</tt>' is treated as an unsigned value.</p>
Reid Spencer	569f2fa	2007-01-31 21:39:12 +0000	[diff] [blame]	2536
				2537	<h5>Semantics:</h5>
Chris Lattner	6ccc2d5	2007-10-03 21:01:14 +0000	[diff] [blame]	2538
Reid Spencer	569f2fa	2007-01-31 21:39:12 +0000	[diff] [blame]	2539	<p>This instruction always performs a logical shift right operation. The most
				2540	significant bits of the result will be filled with zero bits after the
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	2541	shift. If <tt>op2</tt> is (statically or dynamically) equal to or larger than
				2542	the number of bits in <tt>op1</tt>, the result is undefined.</p>
Reid Spencer	569f2fa	2007-01-31 21:39:12 +0000	[diff] [blame]	2543
				2544	<h5>Example:</h5>
				2545	<pre>
				2546	<result> = lshr i32 4, 1 <i>; yields {i32}:result = 2</i>
				2547	<result> = lshr i32 4, 2 <i>; yields {i32}:result = 1</i>
				2548	<result> = lshr i8 4, 3 <i>; yields {i8}:result = 0</i>
				2549	<result> = lshr i8 -2, 1 <i>; yields {i8}:result = 0x7FFFFFFF </i>
Chris Lattner	6ccc2d5	2007-10-03 21:01:14 +0000	[diff] [blame]	2550	<result> = lshr i32 1, 32 <i>; undefined</i>
Reid Spencer	569f2fa	2007-01-31 21:39:12 +0000	[diff] [blame]	2551	</pre>
				2552	</div>
				2553
Reid Spencer	8e11bf8	2007-02-02 13:57:07 +0000	[diff] [blame]	2554	<!-- _______________________________________________________________________ -->
Reid Spencer	569f2fa	2007-01-31 21:39:12 +0000	[diff] [blame]	2555	<div class="doc_subsubsection"> <a name="i_ashr">'<tt>ashr</tt>'
				2556	Instruction</a> </div>
				2557	<div class="doc_text">
				2558
				2559	<h5>Syntax:</h5>
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	2560	<pre> <result> = ashr <ty> <op1>, <op2> <i>; yields {ty}:result</i>
Reid Spencer	569f2fa	2007-01-31 21:39:12 +0000	[diff] [blame]	2561	</pre>
				2562
				2563	<h5>Overview:</h5>
				2564	<p>The '<tt>ashr</tt>' instruction (arithmetic shift right) returns the first
Jeff Cohen	6f1cc77	2007-04-22 01:17:39 +0000	[diff] [blame]	2565	operand shifted to the right a specified number of bits with sign extension.</p>
Reid Spencer	569f2fa	2007-01-31 21:39:12 +0000	[diff] [blame]	2566
				2567	<h5>Arguments:</h5>
				2568	<p>Both arguments to the '<tt>ashr</tt>' instruction must be the same
Nate Begeman	5bc1ea0	2008-07-29 15:49:41 +0000	[diff] [blame]	2569	<a href="#t_integer">integer</a> or <a href="#t_vector">vector</a> of integer
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	2570	type. '<tt>op2</tt>' is treated as an unsigned value.</p>
Reid Spencer	569f2fa	2007-01-31 21:39:12 +0000	[diff] [blame]	2571
				2572	<h5>Semantics:</h5>
				2573	<p>This instruction always performs an arithmetic shift right operation,
				2574	The most significant bits of the result will be filled with the sign bit
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	2575	of <tt>op1</tt>. If <tt>op2</tt> is (statically or dynamically) equal to or
				2576	larger than the number of bits in <tt>op1</tt>, the result is undefined.
Chris Lattner	6ccc2d5	2007-10-03 21:01:14 +0000	[diff] [blame]	2577	</p>
Reid Spencer	569f2fa	2007-01-31 21:39:12 +0000	[diff] [blame]	2578
				2579	<h5>Example:</h5>
				2580	<pre>
				2581	<result> = ashr i32 4, 1 <i>; yields {i32}:result = 2</i>
				2582	<result> = ashr i32 4, 2 <i>; yields {i32}:result = 1</i>
				2583	<result> = ashr i8 4, 3 <i>; yields {i8}:result = 0</i>
				2584	<result> = ashr i8 -2, 1 <i>; yields {i8}:result = -1</i>
Chris Lattner	6ccc2d5	2007-10-03 21:01:14 +0000	[diff] [blame]	2585	<result> = ashr i32 1, 32 <i>; undefined</i>
Reid Spencer	569f2fa	2007-01-31 21:39:12 +0000	[diff] [blame]	2586	</pre>
				2587	</div>
				2588
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2589	<!-- _______________________________________________________________________ -->
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	2590	<div class="doc_subsubsection"> <a name="i_and">'<tt>and</tt>'
				2591	Instruction</a> </div>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2592
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	2593	<div class="doc_text">
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2594
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2595	<h5>Syntax:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2596
				2597	<pre>
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	2598	<result> = and <ty> <op1>, <op2> <i>; yields {ty}:result</i>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2599	</pre>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2600
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2601	<h5>Overview:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2602
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	2603	<p>The '<tt>and</tt>' instruction returns the bitwise logical and of
				2604	its two operands.</p>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2605
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2606	<h5>Arguments:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2607
				2608	<p>The two arguments to the '<tt>and</tt>' instruction must be
				2609	<a href="#t_integer">integer</a> or <a href="#t_vector">vector</a> of integer
				2610	values. Both arguments must have identical types.</p>
				2611
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2612	<h5>Semantics:</h5>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	2613	<p>The truth table used for the '<tt>and</tt>' instruction is:</p>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	2614	<p> </p>
Bill Wendling	c7e4c4d	2008-09-07 10:29:20 +0000	[diff] [blame]	2615	<div>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	2616	<table border="1" cellspacing="0" cellpadding="4">
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	2617	<tbody>
				2618	<tr>
				2619	<td>In0</td>
				2620	<td>In1</td>
				2621	<td>Out</td>
				2622	</tr>
				2623	<tr>
				2624	<td>0</td>
				2625	<td>0</td>
				2626	<td>0</td>
				2627	</tr>
				2628	<tr>
				2629	<td>0</td>
				2630	<td>1</td>
				2631	<td>0</td>
				2632	</tr>
				2633	<tr>
				2634	<td>1</td>
				2635	<td>0</td>
				2636	<td>0</td>
				2637	</tr>
				2638	<tr>
				2639	<td>1</td>
				2640	<td>1</td>
				2641	<td>1</td>
				2642	</tr>
				2643	</tbody>
				2644	</table>
Misha Brukman	daa4cb0	2004-03-01 17:47:27 +0000	[diff] [blame]	2645	</div>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2646	<h5>Example:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2647	<pre>
				2648	<result> = and i32 4, %var <i>; yields {i32}:result = 4 & %var</i>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	2649	<result> = and i32 15, 40 <i>; yields {i32}:result = 8</i>
				2650	<result> = and i32 4, 8 <i>; yields {i32}:result = 0</i>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2651	</pre>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	2652	</div>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2653	<!-- _______________________________________________________________________ -->
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	2654	<div class="doc_subsubsection"> <a name="i_or">'<tt>or</tt>' Instruction</a> </div>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	2655	<div class="doc_text">
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2656	<h5>Syntax:</h5>
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	2657	<pre> <result> = or <ty> <op1>, <op2> <i>; yields {ty}:result</i>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2658	</pre>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	2659	<h5>Overview:</h5>
				2660	<p>The '<tt>or</tt>' instruction returns the bitwise logical inclusive
				2661	or of its two operands.</p>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2662	<h5>Arguments:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2663
				2664	<p>The two arguments to the '<tt>or</tt>' instruction must be
				2665	<a href="#t_integer">integer</a> or <a href="#t_vector">vector</a> of integer
				2666	values. Both arguments must have identical types.</p>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2667	<h5>Semantics:</h5>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	2668	<p>The truth table used for the '<tt>or</tt>' instruction is:</p>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	2669	<p> </p>
Bill Wendling	c7e4c4d	2008-09-07 10:29:20 +0000	[diff] [blame]	2670	<div>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	2671	<table border="1" cellspacing="0" cellpadding="4">
				2672	<tbody>
				2673	<tr>
				2674	<td>In0</td>
				2675	<td>In1</td>
				2676	<td>Out</td>
				2677	</tr>
				2678	<tr>
				2679	<td>0</td>
				2680	<td>0</td>
				2681	<td>0</td>
				2682	</tr>
				2683	<tr>
				2684	<td>0</td>
				2685	<td>1</td>
				2686	<td>1</td>
				2687	</tr>
				2688	<tr>
				2689	<td>1</td>
				2690	<td>0</td>
				2691	<td>1</td>
				2692	</tr>
				2693	<tr>
				2694	<td>1</td>
				2695	<td>1</td>
				2696	<td>1</td>
				2697	</tr>
				2698	</tbody>
				2699	</table>
Misha Brukman	daa4cb0	2004-03-01 17:47:27 +0000	[diff] [blame]	2700	</div>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2701	<h5>Example:</h5>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	2702	<pre> <result> = or i32 4, %var <i>; yields {i32}:result = 4 \| %var</i>
				2703	<result> = or i32 15, 40 <i>; yields {i32}:result = 47</i>
				2704	<result> = or i32 4, 8 <i>; yields {i32}:result = 12</i>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2705	</pre>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	2706	</div>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2707	<!-- _______________________________________________________________________ -->
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	2708	<div class="doc_subsubsection"> <a name="i_xor">'<tt>xor</tt>'
				2709	Instruction</a> </div>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	2710	<div class="doc_text">
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2711	<h5>Syntax:</h5>
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	2712	<pre> <result> = xor <ty> <op1>, <op2> <i>; yields {ty}:result</i>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2713	</pre>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2714	<h5>Overview:</h5>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	2715	<p>The '<tt>xor</tt>' instruction returns the bitwise logical exclusive
				2716	or of its two operands. The <tt>xor</tt> is used to implement the
				2717	"one's complement" operation, which is the "~" operator in C.</p>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2718	<h5>Arguments:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2719	<p>The two arguments to the '<tt>xor</tt>' instruction must be
				2720	<a href="#t_integer">integer</a> or <a href="#t_vector">vector</a> of integer
				2721	values. Both arguments must have identical types.</p>
				2722
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2723	<h5>Semantics:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	2724
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	2725	<p>The truth table used for the '<tt>xor</tt>' instruction is:</p>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	2726	<p> </p>
Bill Wendling	c7e4c4d	2008-09-07 10:29:20 +0000	[diff] [blame]	2727	<div>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	2728	<table border="1" cellspacing="0" cellpadding="4">
				2729	<tbody>
				2730	<tr>
				2731	<td>In0</td>
				2732	<td>In1</td>
				2733	<td>Out</td>
				2734	</tr>
				2735	<tr>
				2736	<td>0</td>
				2737	<td>0</td>
				2738	<td>0</td>
				2739	</tr>
				2740	<tr>
				2741	<td>0</td>
				2742	<td>1</td>
				2743	<td>1</td>
				2744	</tr>
				2745	<tr>
				2746	<td>1</td>
				2747	<td>0</td>
				2748	<td>1</td>
				2749	</tr>
				2750	<tr>
				2751	<td>1</td>
				2752	<td>1</td>
				2753	<td>0</td>
				2754	</tr>
				2755	</tbody>
				2756	</table>
Misha Brukman	daa4cb0	2004-03-01 17:47:27 +0000	[diff] [blame]	2757	</div>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	2758	<p> </p>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2759	<h5>Example:</h5>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	2760	<pre> <result> = xor i32 4, %var <i>; yields {i32}:result = 4 ^ %var</i>
				2761	<result> = xor i32 15, 40 <i>; yields {i32}:result = 39</i>
				2762	<result> = xor i32 4, 8 <i>; yields {i32}:result = 12</i>
				2763	<result> = xor i32 %V, -1 <i>; yields {i32}:result = ~%V</i>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2764	</pre>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	2765	</div>
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	2766
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	2767	<!-- ======================================================================= -->
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	2768	<div class="doc_subsection">
Chris Lattner	3df241e	2006-04-08 23:07:04 +0000	[diff] [blame]	2769	<a name="vectorops">Vector Operations</a>
				2770	</div>
				2771
				2772	<div class="doc_text">
				2773
				2774	<p>LLVM supports several instructions to represent vector operations in a
Jeff Cohen	6f1cc77	2007-04-22 01:17:39 +0000	[diff] [blame]	2775	target-independent manner. These instructions cover the element-access and
Chris Lattner	3df241e	2006-04-08 23:07:04 +0000	[diff] [blame]	2776	vector-specific operations needed to process vectors effectively. While LLVM
				2777	does directly support these vector operations, many sophisticated algorithms
				2778	will want to use target-specific intrinsics to take full advantage of a specific
				2779	target.</p>
				2780
				2781	</div>
				2782
				2783	<!-- _______________________________________________________________________ -->
				2784	<div class="doc_subsubsection">
				2785	<a name="i_extractelement">'<tt>extractelement</tt>' Instruction</a>
				2786	</div>
				2787
				2788	<div class="doc_text">
				2789
				2790	<h5>Syntax:</h5>
				2791
				2792	<pre>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	2793	<result> = extractelement <n x <ty>> <val>, i32 <idx> <i>; yields <ty></i>
Chris Lattner	3df241e	2006-04-08 23:07:04 +0000	[diff] [blame]	2794	</pre>
				2795
				2796	<h5>Overview:</h5>
				2797
				2798	<p>
				2799	The '<tt>extractelement</tt>' instruction extracts a single scalar
Reid Spencer	485bad1	2007-02-15 03:07:05 +0000	[diff] [blame]	2800	element from a vector at a specified index.
Chris Lattner	3df241e	2006-04-08 23:07:04 +0000	[diff] [blame]	2801	</p>
				2802
				2803
				2804	<h5>Arguments:</h5>
				2805
				2806	<p>
				2807	The first operand of an '<tt>extractelement</tt>' instruction is a
Reid Spencer	485bad1	2007-02-15 03:07:05 +0000	[diff] [blame]	2808	value of <a href="#t_vector">vector</a> type. The second operand is
Chris Lattner	3df241e	2006-04-08 23:07:04 +0000	[diff] [blame]	2809	an index indicating the position from which to extract the element.
				2810	The index may be a variable.</p>
				2811
				2812	<h5>Semantics:</h5>
				2813
				2814	<p>
				2815	The result is a scalar of the same type as the element type of
				2816	<tt>val</tt>. Its value is the value at position <tt>idx</tt> of
				2817	<tt>val</tt>. If <tt>idx</tt> exceeds the length of <tt>val</tt>, the
				2818	results are undefined.
				2819	</p>
				2820
				2821	<h5>Example:</h5>
				2822
				2823	<pre>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	2824	%result = extractelement <4 x i32> %vec, i32 0 <i>; yields i32</i>
Chris Lattner	3df241e	2006-04-08 23:07:04 +0000	[diff] [blame]	2825	</pre>
				2826	</div>
				2827
				2828
				2829	<!-- _______________________________________________________________________ -->
				2830	<div class="doc_subsubsection">
				2831	<a name="i_insertelement">'<tt>insertelement</tt>' Instruction</a>
				2832	</div>
				2833
				2834	<div class="doc_text">
				2835
				2836	<h5>Syntax:</h5>
				2837
				2838	<pre>
Dan Gohman	f3480b9	2008-05-12 23:38:42 +0000	[diff] [blame]	2839	<result> = insertelement <n x <ty>> <val>, <ty> <elt>, i32 <idx> <i>; yields <n x <ty>></i>
Chris Lattner	3df241e	2006-04-08 23:07:04 +0000	[diff] [blame]	2840	</pre>
				2841
				2842	<h5>Overview:</h5>
				2843
				2844	<p>
				2845	The '<tt>insertelement</tt>' instruction inserts a scalar
Reid Spencer	485bad1	2007-02-15 03:07:05 +0000	[diff] [blame]	2846	element into a vector at a specified index.
Chris Lattner	3df241e	2006-04-08 23:07:04 +0000	[diff] [blame]	2847	</p>
				2848
				2849
				2850	<h5>Arguments:</h5>
				2851
				2852	<p>
				2853	The first operand of an '<tt>insertelement</tt>' instruction is a
Reid Spencer	485bad1	2007-02-15 03:07:05 +0000	[diff] [blame]	2854	value of <a href="#t_vector">vector</a> type. The second operand is a
Chris Lattner	3df241e	2006-04-08 23:07:04 +0000	[diff] [blame]	2855	scalar value whose type must equal the element type of the first
				2856	operand. The third operand is an index indicating the position at
				2857	which to insert the value. The index may be a variable.</p>
				2858
				2859	<h5>Semantics:</h5>
				2860
				2861	<p>
Reid Spencer	485bad1	2007-02-15 03:07:05 +0000	[diff] [blame]	2862	The result is a vector of the same type as <tt>val</tt>. Its
Chris Lattner	3df241e	2006-04-08 23:07:04 +0000	[diff] [blame]	2863	element values are those of <tt>val</tt> except at position
				2864	<tt>idx</tt>, where it gets the value <tt>elt</tt>. If <tt>idx</tt>
				2865	exceeds the length of <tt>val</tt>, the results are undefined.
				2866	</p>
				2867
				2868	<h5>Example:</h5>
				2869
				2870	<pre>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	2871	%result = insertelement <4 x i32> %vec, i32 1, i32 0 <i>; yields <4 x i32></i>
Chris Lattner	3df241e	2006-04-08 23:07:04 +0000	[diff] [blame]	2872	</pre>
				2873	</div>
				2874
				2875	<!-- _______________________________________________________________________ -->
				2876	<div class="doc_subsubsection">
				2877	<a name="i_shufflevector">'<tt>shufflevector</tt>' Instruction</a>
				2878	</div>
				2879
				2880	<div class="doc_text">
				2881
				2882	<h5>Syntax:</h5>
				2883
				2884	<pre>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	2885	<result> = shufflevector <n x <ty>> <v1>, <n x <ty>> <v2>, <n x i32> <mask> <i>; yields <n x <ty>></i>
Chris Lattner	3df241e	2006-04-08 23:07:04 +0000	[diff] [blame]	2886	</pre>
				2887
				2888	<h5>Overview:</h5>
				2889
				2890	<p>
				2891	The '<tt>shufflevector</tt>' instruction constructs a permutation of elements
				2892	from two input vectors, returning a vector of the same type.
				2893	</p>
				2894
				2895	<h5>Arguments:</h5>
				2896
				2897	<p>
				2898	The first two operands of a '<tt>shufflevector</tt>' instruction are vectors
				2899	with types that match each other and types that match the result of the
				2900	instruction. The third argument is a shuffle mask, which has the same number
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	2901	of elements as the other vector type, but whose element type is always 'i32'.
Chris Lattner	3df241e	2006-04-08 23:07:04 +0000	[diff] [blame]	2902	</p>
				2903
				2904	<p>
				2905	The shuffle mask operand is required to be a constant vector with either
				2906	constant integer or undef values.
				2907	</p>
				2908
				2909	<h5>Semantics:</h5>
				2910
				2911	<p>
				2912	The elements of the two input vectors are numbered from left to right across
				2913	both of the vectors. The shuffle mask operand specifies, for each element of
				2914	the result vector, which element of the two input registers the result element
				2915	gets. The element selector may be undef (meaning "don't care") and the second
				2916	operand may be undef if performing a shuffle from only one vector.
				2917	</p>
				2918
				2919	<h5>Example:</h5>
				2920
				2921	<pre>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	2922	%result = shufflevector <4 x i32> %v1, <4 x i32> %v2,
Jeff Cohen	6f1cc77	2007-04-22 01:17:39 +0000	[diff] [blame]	2923	<4 x i32> <i32 0, i32 4, i32 1, i32 5> <i>; yields <4 x i32></i>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	2924	%result = shufflevector <4 x i32> %v1, <4 x i32> undef,
				2925	<4 x i32> <i32 0, i32 1, i32 2, i32 3> <i>; yields <4 x i32></i> - Identity shuffle.
Chris Lattner	3df241e	2006-04-08 23:07:04 +0000	[diff] [blame]	2926	</pre>
				2927	</div>
				2928
Tanya Lattner	0947429	2006-04-14 19:24:33 +0000	[diff] [blame]	2929
Chris Lattner	3df241e	2006-04-08 23:07:04 +0000	[diff] [blame]	2930	<!-- ======================================================================= -->
				2931	<div class="doc_subsection">
Dan Gohman	a334d5f	2008-05-12 23:51:09 +0000	[diff] [blame]	2932	<a name="aggregateops">Aggregate Operations</a>
				2933	</div>
				2934
				2935	<div class="doc_text">
				2936
				2937	<p>LLVM supports several instructions for working with aggregate values.
				2938	</p>
				2939
				2940	</div>
				2941
				2942	<!-- _______________________________________________________________________ -->
				2943	<div class="doc_subsubsection">
				2944	<a name="i_extractvalue">'<tt>extractvalue</tt>' Instruction</a>
				2945	</div>
				2946
				2947	<div class="doc_text">
				2948
				2949	<h5>Syntax:</h5>
				2950
				2951	<pre>
				2952	<result> = extractvalue <aggregate type> <val>, <idx>{, <idx>}*
				2953	</pre>
				2954
				2955	<h5>Overview:</h5>
				2956
				2957	<p>
Dan Gohman	c3dac5c	2008-05-13 18:16:06 +0000	[diff] [blame]	2958	The '<tt>extractvalue</tt>' instruction extracts the value of a struct field
				2959	or array element from an aggregate value.
Dan Gohman	a334d5f	2008-05-12 23:51:09 +0000	[diff] [blame]	2960	</p>
				2961
				2962
				2963	<h5>Arguments:</h5>
				2964
				2965	<p>
				2966	The first operand of an '<tt>extractvalue</tt>' instruction is a
				2967	value of <a href="#t_struct">struct</a> or <a href="#t_array">array</a>
Dan Gohman	c3dac5c	2008-05-13 18:16:06 +0000	[diff] [blame]	2968	type. The operands are constant indices to specify which value to extract
Dan Gohman	81a0c0b	2008-05-31 00:58:22 +0000	[diff] [blame]	2969	in a similar manner as indices in a
Dan Gohman	a334d5f	2008-05-12 23:51:09 +0000	[diff] [blame]	2970	'<tt><a href="#i_getelementptr">getelementptr</a></tt>' instruction.
				2971	</p>
				2972
				2973	<h5>Semantics:</h5>
				2974
				2975	<p>
				2976	The result is the value at the position in the aggregate specified by
				2977	the index operands.
				2978	</p>
				2979
				2980	<h5>Example:</h5>
				2981
				2982	<pre>
Dan Gohman	81a0c0b	2008-05-31 00:58:22 +0000	[diff] [blame]	2983	%result = extractvalue {i32, float} %agg, 0 <i>; yields i32</i>
Dan Gohman	a334d5f	2008-05-12 23:51:09 +0000	[diff] [blame]	2984	</pre>
				2985	</div>
				2986
				2987
				2988	<!-- _______________________________________________________________________ -->
				2989	<div class="doc_subsubsection">
				2990	<a name="i_insertvalue">'<tt>insertvalue</tt>' Instruction</a>
				2991	</div>
				2992
				2993	<div class="doc_text">
				2994
				2995	<h5>Syntax:</h5>
				2996
				2997	<pre>
Dan Gohman	81a0c0b	2008-05-31 00:58:22 +0000	[diff] [blame]	2998	<result> = insertvalue <aggregate type> <val>, <ty> <val>, <idx> <i>; yields <n x <ty>></i>
Dan Gohman	a334d5f	2008-05-12 23:51:09 +0000	[diff] [blame]	2999	</pre>
				3000
				3001	<h5>Overview:</h5>
				3002
				3003	<p>
				3004	The '<tt>insertvalue</tt>' instruction inserts a value
Dan Gohman	c3dac5c	2008-05-13 18:16:06 +0000	[diff] [blame]	3005	into a struct field or array element in an aggregate.
Dan Gohman	a334d5f	2008-05-12 23:51:09 +0000	[diff] [blame]	3006	</p>
				3007
				3008
				3009	<h5>Arguments:</h5>
				3010
				3011	<p>
				3012	The first operand of an '<tt>insertvalue</tt>' instruction is a
				3013	value of <a href="#t_struct">struct</a> or <a href="#t_array">array</a> type.
				3014	The second operand is a first-class value to insert.
Dan Gohman	c4b49eb	2008-05-23 21:53:15 +0000	[diff] [blame]	3015	The following operands are constant indices
Dan Gohman	81a0c0b	2008-05-31 00:58:22 +0000	[diff] [blame]	3016	indicating the position at which to insert the value in a similar manner as
Dan Gohman	c3dac5c	2008-05-13 18:16:06 +0000	[diff] [blame]	3017	indices in a
Dan Gohman	a334d5f	2008-05-12 23:51:09 +0000	[diff] [blame]	3018	'<tt><a href="#i_getelementptr">getelementptr</a></tt>' instruction.
				3019	The value to insert must have the same type as the value identified
Dan Gohman	c3dac5c	2008-05-13 18:16:06 +0000	[diff] [blame]	3020	by the indices.
Dan Gohman	a334d5f	2008-05-12 23:51:09 +0000	[diff] [blame]	3021
				3022	<h5>Semantics:</h5>
				3023
				3024	<p>
				3025	The result is an aggregate of the same type as <tt>val</tt>. Its
				3026	value is that of <tt>val</tt> except that the value at the position
Dan Gohman	c3dac5c	2008-05-13 18:16:06 +0000	[diff] [blame]	3027	specified by the indices is that of <tt>elt</tt>.
Dan Gohman	a334d5f	2008-05-12 23:51:09 +0000	[diff] [blame]	3028	</p>
				3029
				3030	<h5>Example:</h5>
				3031
				3032	<pre>
Dan Gohman	52bb2db	2008-06-23 15:26:37 +0000	[diff] [blame]	3033	%result = insertvalue {i32, float} %agg, i32 1, 0 <i>; yields {i32, float}</i>
Dan Gohman	a334d5f	2008-05-12 23:51:09 +0000	[diff] [blame]	3034	</pre>
				3035	</div>
				3036
				3037
				3038	<!-- ======================================================================= -->
				3039	<div class="doc_subsection">
Chris Lattner	884a970	2006-08-15 00:45:58 +0000	[diff] [blame]	3040	<a name="memoryops">Memory Access and Addressing Operations</a>
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3041	</div>
				3042
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	3043	<div class="doc_text">
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3044
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	3045	<p>A key design point of an SSA-based representation is how it
				3046	represents memory. In LLVM, no memory locations are in SSA form, which
				3047	makes things very simple. This section describes how to read, write,
John Criswell	9e2485c	2004-12-10 15:51:16 +0000	[diff] [blame]	3048	allocate, and free memory in LLVM.</p>
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3049
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	3050	</div>
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3051
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	3052	<!-- _______________________________________________________________________ -->
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3053	<div class="doc_subsubsection">
				3054	<a name="i_malloc">'<tt>malloc</tt>' Instruction</a>
				3055	</div>
				3056
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	3057	<div class="doc_text">
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3058
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	3059	<h5>Syntax:</h5>
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3060
				3061	<pre>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	3062	<result> = malloc <type>[, i32 <NumElements>][, align <alignment>] <i>; yields {type*}:result</i>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	3063	</pre>
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3064
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	3065	<h5>Overview:</h5>
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3066
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	3067	<p>The '<tt>malloc</tt>' instruction allocates memory from the system
Christopher Lamb	303dae9	2007-12-17 01:00:21 +0000	[diff] [blame]	3068	heap and returns a pointer to it. The object is always allocated in the generic
				3069	address space (address space zero).</p>
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3070
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	3071	<h5>Arguments:</h5>
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3072
				3073	<p>The '<tt>malloc</tt>' instruction allocates
				3074	<tt>sizeof(<type>)*NumElements</tt>
John Criswell	6e4ca61	2004-02-24 16:13:56 +0000	[diff] [blame]	3075	bytes of memory from the operating system and returns a pointer of the
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3076	appropriate type to the program. If "NumElements" is specified, it is the
Gabor Greif	1acd2ee	2008-02-09 22:24:34 +0000	[diff] [blame]	3077	number of elements allocated, otherwise "NumElements" is defaulted to be one.
Chris Lattner	4316dec	2008-04-02 00:38:26 +0000	[diff] [blame]	3078	If a constant alignment is specified, the value result of the allocation is guaranteed to
Gabor Greif	1acd2ee	2008-02-09 22:24:34 +0000	[diff] [blame]	3079	be aligned to at least that boundary. If not specified, or if zero, the target can
				3080	choose to align the allocation on any convenient boundary.</p>
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3081
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	3082	<p>'<tt>type</tt>' must be a sized type.</p>
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3083
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	3084	<h5>Semantics:</h5>
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3085
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	3086	<p>Memory is allocated using the system "<tt>malloc</tt>" function, and
Chris Lattner	72ed200	2008-04-19 21:01:16 +0000	[diff] [blame]	3087	a pointer is returned. The result of a zero byte allocattion is undefined. The
				3088	result is null if there is insufficient memory available.</p>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	3089
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3090	<h5>Example:</h5>
				3091
				3092	<pre>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	3093	%array = malloc [4 x i8 ] <i>; yields {[%4 x i8]*}:array</i>
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3094
Bill Wendling	aac388b	2007-05-29 09:42:13 +0000	[diff] [blame]	3095	%size = <a href="#i_add">add</a> i32 2, 2 <i>; yields {i32}:size = i32 4</i>
				3096	%array1 = malloc i8, i32 4 <i>; yields {i8*}:array1</i>
				3097	%array2 = malloc [12 x i8], i32 %size <i>; yields {[12 x i8]*}:array2</i>
				3098	%array3 = malloc i32, i32 4, align 1024 <i>; yields {i32*}:array3</i>
				3099	%array4 = malloc i32, align 1024 <i>; yields {i32*}:array4</i>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	3100	</pre>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	3101	</div>
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3102
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	3103	<!-- _______________________________________________________________________ -->
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3104	<div class="doc_subsubsection">
				3105	<a name="i_free">'<tt>free</tt>' Instruction</a>
				3106	</div>
				3107
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	3108	<div class="doc_text">
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3109
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	3110	<h5>Syntax:</h5>
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3111
				3112	<pre>
				3113	free <type> <value> <i>; yields {void}</i>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	3114	</pre>
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3115
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	3116	<h5>Overview:</h5>
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3117
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	3118	<p>The '<tt>free</tt>' instruction returns memory back to the unused
John Criswell	c1f786c	2005-05-13 22:25:59 +0000	[diff] [blame]	3119	memory heap to be reallocated in the future.</p>
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3120
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	3121	<h5>Arguments:</h5>
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3122
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	3123	<p>'<tt>value</tt>' shall be a pointer value that points to a value
				3124	that was allocated with the '<tt><a href="#i_malloc">malloc</a></tt>'
				3125	instruction.</p>
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3126
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	3127	<h5>Semantics:</h5>
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3128
John Criswell	9e2485c	2004-12-10 15:51:16 +0000	[diff] [blame]	3129	<p>Access to the memory pointed to by the pointer is no longer defined
Chris Lattner	e0db56d	2008-04-19 22:41:32 +0000	[diff] [blame]	3130	after this instruction executes. If the pointer is null, the operation
				3131	is a noop.</p>
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3132
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	3133	<h5>Example:</h5>
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3134
				3135	<pre>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	3136	%array = <a href="#i_malloc">malloc</a> [4 x i8] <i>; yields {[4 x i8]*}:array</i>
				3137	free [4 x i8]* %array
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	3138	</pre>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	3139	</div>
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3140
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	3141	<!-- _______________________________________________________________________ -->
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3142	<div class="doc_subsubsection">
				3143	<a name="i_alloca">'<tt>alloca</tt>' Instruction</a>
				3144	</div>
				3145
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	3146	<div class="doc_text">
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3147
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	3148	<h5>Syntax:</h5>
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3149
				3150	<pre>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	3151	<result> = alloca <type>[, i32 <NumElements>][, align <alignment>] <i>; yields {type*}:result</i>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	3152	</pre>
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3153
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	3154	<h5>Overview:</h5>
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3155
Jeff Cohen	6f1cc77	2007-04-22 01:17:39 +0000	[diff] [blame]	3156	<p>The '<tt>alloca</tt>' instruction allocates memory on the stack frame of the
				3157	currently executing function, to be automatically released when this function
Christopher Lamb	303dae9	2007-12-17 01:00:21 +0000	[diff] [blame]	3158	returns to its caller. The object is always allocated in the generic address
				3159	space (address space zero).</p>
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3160
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	3161	<h5>Arguments:</h5>
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3162
John Criswell	9e2485c	2004-12-10 15:51:16 +0000	[diff] [blame]	3163	<p>The '<tt>alloca</tt>' instruction allocates <tt>sizeof(<type>)*NumElements</tt>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	3164	bytes of memory on the runtime stack, returning a pointer of the
Gabor Greif	1acd2ee	2008-02-09 22:24:34 +0000	[diff] [blame]	3165	appropriate type to the program. If "NumElements" is specified, it is the
				3166	number of elements allocated, otherwise "NumElements" is defaulted to be one.
Chris Lattner	4316dec	2008-04-02 00:38:26 +0000	[diff] [blame]	3167	If a constant alignment is specified, the value result of the allocation is guaranteed
Gabor Greif	1acd2ee	2008-02-09 22:24:34 +0000	[diff] [blame]	3168	to be aligned to at least that boundary. If not specified, or if zero, the target
				3169	can choose to align the allocation on any convenient boundary.</p>
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3170
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	3171	<p>'<tt>type</tt>' may be any sized type.</p>
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3172
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	3173	<h5>Semantics:</h5>
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3174
Chris Lattner	72ed200	2008-04-19 21:01:16 +0000	[diff] [blame]	3175	<p>Memory is allocated; a pointer is returned. The operation is undefiend if
				3176	there is insufficient stack space for the allocation. '<tt>alloca</tt>'d
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	3177	memory is automatically released when the function returns. The '<tt>alloca</tt>'
				3178	instruction is commonly used to represent automatic variables that must
				3179	have an address available. When the function returns (either with the <tt><a
John Criswell	dae2e93	2005-05-12 16:55:34 +0000	[diff] [blame]	3180	href="#i_ret">ret</a></tt> or <tt><a href="#i_unwind">unwind</a></tt>
Chris Lattner	4316dec	2008-04-02 00:38:26 +0000	[diff] [blame]	3181	instructions), the memory is reclaimed. Allocating zero bytes
				3182	is legal, but the result is undefined.</p>
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3183
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	3184	<h5>Example:</h5>
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3185
				3186	<pre>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	3187	%ptr = alloca i32 <i>; yields {i32*}:ptr</i>
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	3188	%ptr = alloca i32, i32 4 <i>; yields {i32*}:ptr</i>
				3189	%ptr = alloca i32, i32 4, align 1024 <i>; yields {i32*}:ptr</i>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	3190	%ptr = alloca i32, align 1024 <i>; yields {i32*}:ptr</i>
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	3191	</pre>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	3192	</div>
Chris Lattner	2cbdc45	2005-11-06 08:02:57 +0000	[diff] [blame]	3193
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	3194	<!-- _______________________________________________________________________ -->
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	3195	<div class="doc_subsubsection"> <a name="i_load">'<tt>load</tt>'
				3196	Instruction</a> </div>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	3197	<div class="doc_text">
Chris Lattner	2b7d320	2002-05-06 03:03:22 +0000	[diff] [blame]	3198	<h5>Syntax:</h5>
Christopher Lamb	2330e4d	2007-04-21 08:16:25 +0000	[diff] [blame]	3199	<pre> <result> = load <ty>* <pointer>[, align <alignment>]<br> <result> = volatile load <ty>* <pointer>[, align <alignment>]<br></pre>
Chris Lattner	2b7d320	2002-05-06 03:03:22 +0000	[diff] [blame]	3200	<h5>Overview:</h5>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	3201	<p>The '<tt>load</tt>' instruction is used to read from memory.</p>
Chris Lattner	2b7d320	2002-05-06 03:03:22 +0000	[diff] [blame]	3202	<h5>Arguments:</h5>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	3203	<p>The argument to the '<tt>load</tt>' instruction specifies the memory
John Criswell	0ec250c	2005-10-24 16:17:18 +0000	[diff] [blame]	3204	address from which to load. The pointer must point to a <a
Chris Lattner	e53e508	2004-06-03 22:57:15 +0000	[diff] [blame]	3205	href="#t_firstclass">first class</a> type. If the <tt>load</tt> is
John Criswell	0ec250c	2005-10-24 16:17:18 +0000	[diff] [blame]	3206	marked as <tt>volatile</tt>, then the optimizer is not allowed to modify
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	3207	the number or order of execution of this <tt>load</tt> with other
				3208	volatile <tt>load</tt> and <tt><a href="#i_store">store</a></tt>
				3209	instructions. </p>
Chris Lattner	a31d1d7	2008-01-06 21:04:43 +0000	[diff] [blame]	3210	<p>
Chris Lattner	4316dec	2008-04-02 00:38:26 +0000	[diff] [blame]	3211	The optional constant "align" argument specifies the alignment of the operation
Chris Lattner	a31d1d7	2008-01-06 21:04:43 +0000	[diff] [blame]	3212	(that is, the alignment of the memory address). A value of 0 or an
				3213	omitted "align" argument means that the operation has the preferential
				3214	alignment for the target. It is the responsibility of the code emitter
				3215	to ensure that the alignment information is correct. Overestimating
				3216	the alignment results in an undefined behavior. Underestimating the
				3217	alignment may produce less efficient code. An alignment of 1 is always
				3218	safe.
				3219	</p>
Chris Lattner	2b7d320	2002-05-06 03:03:22 +0000	[diff] [blame]	3220	<h5>Semantics:</h5>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	3221	<p>The location of memory pointed to is loaded.</p>
Chris Lattner	2b7d320	2002-05-06 03:03:22 +0000	[diff] [blame]	3222	<h5>Examples:</h5>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	3223	<pre> %ptr = <a href="#i_alloca">alloca</a> i32 <i>; yields {i32*}:ptr</i>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	3224	<a
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	3225	href="#i_store">store</a> i32 3, i32* %ptr <i>; yields {void}</i>
				3226	%val = load i32* %ptr <i>; yields {i32}:val = i32 3</i>
Chris Lattner	2b7d320	2002-05-06 03:03:22 +0000	[diff] [blame]	3227	</pre>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	3228	</div>
Chris Lattner	2b7d320	2002-05-06 03:03:22 +0000	[diff] [blame]	3229	<!-- _______________________________________________________________________ -->
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	3230	<div class="doc_subsubsection"> <a name="i_store">'<tt>store</tt>'
				3231	Instruction</a> </div>
Reid Spencer	035ab57	2006-11-09 21:18:01 +0000	[diff] [blame]	3232	<div class="doc_text">
Chris Lattner	2b7d320	2002-05-06 03:03:22 +0000	[diff] [blame]	3233	<h5>Syntax:</h5>
Christopher Lamb	2330e4d	2007-04-21 08:16:25 +0000	[diff] [blame]	3234	<pre> store <ty> <value>, <ty>* <pointer>[, align <alignment>] <i>; yields {void}</i>
				3235	volatile store <ty> <value>, <ty>* <pointer>[, align <alignment>] <i>; yields {void}</i>
Chris Lattner	2b7d320	2002-05-06 03:03:22 +0000	[diff] [blame]	3236	</pre>
Chris Lattner	2b7d320	2002-05-06 03:03:22 +0000	[diff] [blame]	3237	<h5>Overview:</h5>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	3238	<p>The '<tt>store</tt>' instruction is used to write to memory.</p>
Chris Lattner	2b7d320	2002-05-06 03:03:22 +0000	[diff] [blame]	3239	<h5>Arguments:</h5>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	3240	<p>There are two arguments to the '<tt>store</tt>' instruction: a value
Jeff Cohen	6f1cc77	2007-04-22 01:17:39 +0000	[diff] [blame]	3241	to store and an address at which to store it. The type of the '<tt><pointer></tt>'
Chris Lattner	4316dec	2008-04-02 00:38:26 +0000	[diff] [blame]	3242	operand must be a pointer to the <a href="#t_firstclass">first class</a> type
				3243	of the '<tt><value></tt>'
John Criswell	c1f786c	2005-05-13 22:25:59 +0000	[diff] [blame]	3244	operand. If the <tt>store</tt> is marked as <tt>volatile</tt>, then the
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	3245	optimizer is not allowed to modify the number or order of execution of
				3246	this <tt>store</tt> with other volatile <tt>load</tt> and <tt><a
				3247	href="#i_store">store</a></tt> instructions.</p>
Chris Lattner	a31d1d7	2008-01-06 21:04:43 +0000	[diff] [blame]	3248	<p>
Chris Lattner	4316dec	2008-04-02 00:38:26 +0000	[diff] [blame]	3249	The optional constant "align" argument specifies the alignment of the operation
Chris Lattner	a31d1d7	2008-01-06 21:04:43 +0000	[diff] [blame]	3250	(that is, the alignment of the memory address). A value of 0 or an
				3251	omitted "align" argument means that the operation has the preferential
				3252	alignment for the target. It is the responsibility of the code emitter
				3253	to ensure that the alignment information is correct. Overestimating
				3254	the alignment results in an undefined behavior. Underestimating the
				3255	alignment may produce less efficient code. An alignment of 1 is always
				3256	safe.
				3257	</p>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	3258	<h5>Semantics:</h5>
				3259	<p>The contents of memory are updated to contain '<tt><value></tt>'
				3260	at the location specified by the '<tt><pointer></tt>' operand.</p>
Chris Lattner	2b7d320	2002-05-06 03:03:22 +0000	[diff] [blame]	3261	<h5>Example:</h5>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	3262	<pre> %ptr = <a href="#i_alloca">alloca</a> i32 <i>; yields {i32*}:ptr</i>
Bill Wendling	8c6c72d	2007-10-22 05:10:05 +0000	[diff] [blame]	3263	store i32 3, i32* %ptr <i>; yields {void}</i>
				3264	%val = <a href="#i_load">load</a> i32* %ptr <i>; yields {i32}:val = i32 3</i>
Chris Lattner	2b7d320	2002-05-06 03:03:22 +0000	[diff] [blame]	3265	</pre>
Reid Spencer	47ce179	2006-11-09 21:15:49 +0000	[diff] [blame]	3266	</div>
				3267
Chris Lattner	2b7d320	2002-05-06 03:03:22 +0000	[diff] [blame]	3268	<!-- _______________________________________________________________________ -->
Chris Lattner	f74d5c7	2004-04-05 01:30:49 +0000	[diff] [blame]	3269	<div class="doc_subsubsection">
				3270	<a name="i_getelementptr">'<tt>getelementptr</tt>' Instruction</a>
				3271	</div>
				3272
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	3273	<div class="doc_text">
Chris Lattner	7faa883	2002-04-14 06:13:44 +0000	[diff] [blame]	3274	<h5>Syntax:</h5>
Chris Lattner	f74d5c7	2004-04-05 01:30:49 +0000	[diff] [blame]	3275	<pre>
				3276	<result> = getelementptr <ty>* <ptrval>{, <ty> <idx>}*
				3277	</pre>
				3278
Chris Lattner	7faa883	2002-04-14 06:13:44 +0000	[diff] [blame]	3279	<h5>Overview:</h5>
Chris Lattner	f74d5c7	2004-04-05 01:30:49 +0000	[diff] [blame]	3280
				3281	<p>
				3282	The '<tt>getelementptr</tt>' instruction is used to get the address of a
				3283	subelement of an aggregate data structure.</p>
				3284
Chris Lattner	7faa883	2002-04-14 06:13:44 +0000	[diff] [blame]	3285	<h5>Arguments:</h5>
Chris Lattner	f74d5c7	2004-04-05 01:30:49 +0000	[diff] [blame]	3286
Reid Spencer	85f5b5b	2006-12-04 21:29:24 +0000	[diff] [blame]	3287	<p>This instruction takes a list of integer operands that indicate what
Chris Lattner	f74d5c7	2004-04-05 01:30:49 +0000	[diff] [blame]	3288	elements of the aggregate object to index to. The actual types of the arguments
				3289	provided depend on the type of the first pointer argument. The
				3290	'<tt>getelementptr</tt>' instruction is used to index down through the type
John Criswell	fc6b895	2005-05-16 16:17:45 +0000	[diff] [blame]	3291	levels of a structure or to a specific index in an array. When indexing into a
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	3292	structure, only <tt>i32</tt> integer constants are allowed. When indexing
Chris Lattner	05d6709	2008-04-24 05:59:56 +0000	[diff] [blame]	3293	into an array or pointer, only integers of 32 or 64 bits are allowed; 32-bit
				3294	values will be sign extended to 64-bits if required.</p>
Chris Lattner	f74d5c7	2004-04-05 01:30:49 +0000	[diff] [blame]	3295
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	3296	<p>For example, let's consider a C code fragment and how it gets
				3297	compiled to LLVM:</p>
Chris Lattner	f74d5c7	2004-04-05 01:30:49 +0000	[diff] [blame]	3298
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	3299	<div class="doc_code">
Chris Lattner	f74d5c7	2004-04-05 01:30:49 +0000	[diff] [blame]	3300	<pre>
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	3301	struct RT {
				3302	char A;
Chris Lattner	cabc846	2007-05-29 15:43:56 +0000	[diff] [blame]	3303	int B[10][20];
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	3304	char C;
				3305	};
				3306	struct ST {
Chris Lattner	cabc846	2007-05-29 15:43:56 +0000	[diff] [blame]	3307	int X;
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	3308	double Y;
				3309	struct RT Z;
				3310	};
Chris Lattner	f74d5c7	2004-04-05 01:30:49 +0000	[diff] [blame]	3311
Chris Lattner	cabc846	2007-05-29 15:43:56 +0000	[diff] [blame]	3312	int foo(struct ST s) {
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	3313	return &s[1].Z.B[5][13];
				3314	}
Chris Lattner	f74d5c7	2004-04-05 01:30:49 +0000	[diff] [blame]	3315	</pre>
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	3316	</div>
Chris Lattner	f74d5c7	2004-04-05 01:30:49 +0000	[diff] [blame]	3317
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	3318	<p>The LLVM code generated by the GCC frontend is:</p>
Chris Lattner	f74d5c7	2004-04-05 01:30:49 +0000	[diff] [blame]	3319
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	3320	<div class="doc_code">
Chris Lattner	f74d5c7	2004-04-05 01:30:49 +0000	[diff] [blame]	3321	<pre>
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	3322	%RT = type { i8 , [10 x [20 x i32]], i8 }
				3323	%ST = type { i32, double, %RT }
Chris Lattner	f74d5c7	2004-04-05 01:30:49 +0000	[diff] [blame]	3324
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	3325	define i32* %foo(%ST* %s) {
				3326	entry:
				3327	%reg = getelementptr %ST* %s, i32 1, i32 2, i32 1, i32 5, i32 13
				3328	ret i32* %reg
				3329	}
Chris Lattner	f74d5c7	2004-04-05 01:30:49 +0000	[diff] [blame]	3330	</pre>
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	3331	</div>
Chris Lattner	f74d5c7	2004-04-05 01:30:49 +0000	[diff] [blame]	3332
Chris Lattner	7faa883	2002-04-14 06:13:44 +0000	[diff] [blame]	3333	<h5>Semantics:</h5>
Chris Lattner	f74d5c7	2004-04-05 01:30:49 +0000	[diff] [blame]	3334
				3335	<p>The index types specified for the '<tt>getelementptr</tt>' instruction depend
John Criswell	c1f786c	2005-05-13 22:25:59 +0000	[diff] [blame]	3336	on the pointer type that is being indexed into. <a href="#t_pointer">Pointer</a>
Reid Spencer	85f5b5b	2006-12-04 21:29:24 +0000	[diff] [blame]	3337	and <a href="#t_array">array</a> types can use a 32-bit or 64-bit
Reid Spencer	42ddd84	2006-12-03 16:53:48 +0000	[diff] [blame]	3338	<a href="#t_integer">integer</a> type but the value will always be sign extended
Chris Lattner	4316dec	2008-04-02 00:38:26 +0000	[diff] [blame]	3339	to 64-bits. <a href="#t_struct">Structure</a> and <a href="#t_pstruct">packed
				3340	structure</a> types require <tt>i32</tt> <b>constants</b>.</p>
Chris Lattner	f74d5c7	2004-04-05 01:30:49 +0000	[diff] [blame]	3341
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	3342	<p>In the example above, the first index is indexing into the '<tt>%ST*</tt>'
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	3343	type, which is a pointer, yielding a '<tt>%ST</tt>' = '<tt>{ i32, double, %RT
Chris Lattner	f74d5c7	2004-04-05 01:30:49 +0000	[diff] [blame]	3344	}</tt>' type, a structure. The second index indexes into the third element of
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	3345	the structure, yielding a '<tt>%RT</tt>' = '<tt>{ i8 , [10 x [20 x i32]],
				3346	i8 }</tt>' type, another structure. The third index indexes into the second
				3347	element of the structure, yielding a '<tt>[10 x [20 x i32]]</tt>' type, an
Chris Lattner	f74d5c7	2004-04-05 01:30:49 +0000	[diff] [blame]	3348	array. The two dimensions of the array are subscripted into, yielding an
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	3349	'<tt>i32</tt>' type. The '<tt>getelementptr</tt>' instruction returns a pointer
				3350	to this element, thus computing a value of '<tt>i32*</tt>' type.</p>
Chris Lattner	f74d5c7	2004-04-05 01:30:49 +0000	[diff] [blame]	3351
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	3352	<p>Note that it is perfectly legal to index partially through a
				3353	structure, returning a pointer to an inner element. Because of this,
				3354	the LLVM code for the given testcase is equivalent to:</p>
Chris Lattner	f74d5c7	2004-04-05 01:30:49 +0000	[diff] [blame]	3355
				3356	<pre>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	3357	define i32* %foo(%ST* %s) {
				3358	%t1 = getelementptr %ST* %s, i32 1 <i>; yields %ST*:%t1</i>
Jeff Cohen	6f1cc77	2007-04-22 01:17:39 +0000	[diff] [blame]	3359	%t2 = getelementptr %ST* %t1, i32 0, i32 2 <i>; yields %RT*:%t2</i>
				3360	%t3 = getelementptr %RT* %t2, i32 0, i32 1 <i>; yields [10 x [20 x i32]]*:%t3</i>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	3361	%t4 = getelementptr [10 x [20 x i32]]* %t3, i32 0, i32 5 <i>; yields [20 x i32]*:%t4</i>
				3362	%t5 = getelementptr [20 x i32]* %t4, i32 0, i32 13 <i>; yields i32*:%t5</i>
				3363	ret i32* %t5
Chris Lattner	f74d5c7	2004-04-05 01:30:49 +0000	[diff] [blame]	3364	}
Chris Lattner	6536cfe	2002-05-06 22:08:29 +0000	[diff] [blame]	3365	</pre>
Chris Lattner	e67a951	2005-06-24 17:22:57 +0000	[diff] [blame]	3366
				3367	<p>Note that it is undefined to access an array out of bounds: array and
				3368	pointer indexes must always be within the defined bounds of the array type.
Chris Lattner	05d6709	2008-04-24 05:59:56 +0000	[diff] [blame]	3369	The one exception for this rule is zero length arrays. These arrays are
Chris Lattner	e67a951	2005-06-24 17:22:57 +0000	[diff] [blame]	3370	defined to be accessible as variable length arrays, which requires access
				3371	beyond the zero'th element.</p>
				3372
Chris Lattner	884a970	2006-08-15 00:45:58 +0000	[diff] [blame]	3373	<p>The getelementptr instruction is often confusing. For some more insight
				3374	into how it works, see <a href="GetElementPtr.html">the getelementptr
				3375	FAQ</a>.</p>
				3376
Chris Lattner	7faa883	2002-04-14 06:13:44 +0000	[diff] [blame]	3377	<h5>Example:</h5>
Chris Lattner	e67a951	2005-06-24 17:22:57 +0000	[diff] [blame]	3378
Chris Lattner	f74d5c7	2004-04-05 01:30:49 +0000	[diff] [blame]	3379	<pre>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	3380	<i>; yields [12 x i8]*:aptr</i>
				3381	%aptr = getelementptr {i32, [12 x i8]}* %sptr, i64 0, i32 1
Chris Lattner	f74d5c7	2004-04-05 01:30:49 +0000	[diff] [blame]	3382	</pre>
Chris Lattner	f74d5c7	2004-04-05 01:30:49 +0000	[diff] [blame]	3383	</div>
Reid Spencer	47ce179	2006-11-09 21:15:49 +0000	[diff] [blame]	3384
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	3385	<!-- ======================================================================= -->
Reid Spencer	2fd21e6	2006-11-08 01:18:52 +0000	[diff] [blame]	3386	<div class="doc_subsection"> <a name="convertops">Conversion Operations</a>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	3387	</div>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	3388	<div class="doc_text">
Reid Spencer	2fd21e6	2006-11-08 01:18:52 +0000	[diff] [blame]	3389	<p>The instructions in this category are the conversion instructions (casting)
				3390	which all take a single operand and a type. They perform various bit conversions
				3391	on the operand.</p>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	3392	</div>
Chris Lattner	cc37aae	2004-03-12 05:50:16 +0000	[diff] [blame]	3393
Chris Lattner	6536cfe	2002-05-06 22:08:29 +0000	[diff] [blame]	3394	<!-- _______________________________________________________________________ -->
Chris Lattner	cc37aae	2004-03-12 05:50:16 +0000	[diff] [blame]	3395	<div class="doc_subsubsection">
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3396	<a name="i_trunc">'<tt>trunc .. to</tt>' Instruction</a>
				3397	</div>
				3398	<div class="doc_text">
				3399
				3400	<h5>Syntax:</h5>
				3401	<pre>
				3402	<result> = trunc <ty> <value> to <ty2> <i>; yields ty2</i>
				3403	</pre>
				3404
				3405	<h5>Overview:</h5>
				3406	<p>
				3407	The '<tt>trunc</tt>' instruction truncates its operand to the type <tt>ty2</tt>.
				3408	</p>
				3409
				3410	<h5>Arguments:</h5>
				3411	<p>
				3412	The '<tt>trunc</tt>' instruction takes a <tt>value</tt> to trunc, which must
				3413	be an <a href="#t_integer">integer</a> type, and a type that specifies the size
Chris Lattner	3b19d65	2007-01-15 01:54:13 +0000	[diff] [blame]	3414	and type of the result, which must be an <a href="#t_integer">integer</a>
Reid Spencer	d444879	2006-11-09 23:03:26 +0000	[diff] [blame]	3415	type. The bit size of <tt>value</tt> must be larger than the bit size of
				3416	<tt>ty2</tt>. Equal sized types are not allowed.</p>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3417
				3418	<h5>Semantics:</h5>
				3419	<p>
				3420	The '<tt>trunc</tt>' instruction truncates the high order bits in <tt>value</tt>
Reid Spencer	d444879	2006-11-09 23:03:26 +0000	[diff] [blame]	3421	and converts the remaining bits to <tt>ty2</tt>. Since the source size must be
				3422	larger than the destination size, <tt>trunc</tt> cannot be a <i>no-op cast</i>.
				3423	It will always truncate bits.</p>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3424
				3425	<h5>Example:</h5>
				3426	<pre>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	3427	%X = trunc i32 257 to i8 <i>; yields i8:1</i>
Reid Spencer	c78f337	2007-01-12 03:35:51 +0000	[diff] [blame]	3428	%Y = trunc i32 123 to i1 <i>; yields i1:true</i>
				3429	%Y = trunc i32 122 to i1 <i>; yields i1:false</i>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3430	</pre>
				3431	</div>
				3432
				3433	<!-- _______________________________________________________________________ -->
				3434	<div class="doc_subsubsection">
				3435	<a name="i_zext">'<tt>zext .. to</tt>' Instruction</a>
				3436	</div>
				3437	<div class="doc_text">
				3438
				3439	<h5>Syntax:</h5>
				3440	<pre>
				3441	<result> = zext <ty> <value> to <ty2> <i>; yields ty2</i>
				3442	</pre>
				3443
				3444	<h5>Overview:</h5>
				3445	<p>The '<tt>zext</tt>' instruction zero extends its operand to type
				3446	<tt>ty2</tt>.</p>
				3447
				3448
				3449	<h5>Arguments:</h5>
				3450	<p>The '<tt>zext</tt>' instruction takes a value to cast, which must be of
Chris Lattner	3b19d65	2007-01-15 01:54:13 +0000	[diff] [blame]	3451	<a href="#t_integer">integer</a> type, and a type to cast it to, which must
				3452	also be of <a href="#t_integer">integer</a> type. The bit size of the
Reid Spencer	d444879	2006-11-09 23:03:26 +0000	[diff] [blame]	3453	<tt>value</tt> must be smaller than the bit size of the destination type,
				3454	<tt>ty2</tt>.</p>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3455
				3456	<h5>Semantics:</h5>
				3457	<p>The <tt>zext</tt> fills the high order bits of the <tt>value</tt> with zero
Chris Lattner	d1d2517	2007-05-24 19:13:27 +0000	[diff] [blame]	3458	bits until it reaches the size of the destination type, <tt>ty2</tt>.</p>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3459
Reid Spencer	b592952	2007-01-12 15:46:11 +0000	[diff] [blame]	3460	<p>When zero extending from i1, the result will always be either 0 or 1.</p>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3461
				3462	<h5>Example:</h5>
				3463	<pre>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	3464	%X = zext i32 257 to i64 <i>; yields i64:257</i>
Reid Spencer	c78f337	2007-01-12 03:35:51 +0000	[diff] [blame]	3465	%Y = zext i1 true to i32 <i>; yields i32:1</i>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3466	</pre>
				3467	</div>
				3468
				3469	<!-- _______________________________________________________________________ -->
				3470	<div class="doc_subsubsection">
				3471	<a name="i_sext">'<tt>sext .. to</tt>' Instruction</a>
				3472	</div>
				3473	<div class="doc_text">
				3474
				3475	<h5>Syntax:</h5>
				3476	<pre>
				3477	<result> = sext <ty> <value> to <ty2> <i>; yields ty2</i>
				3478	</pre>
				3479
				3480	<h5>Overview:</h5>
				3481	<p>The '<tt>sext</tt>' sign extends <tt>value</tt> to the type <tt>ty2</tt>.</p>
				3482
				3483	<h5>Arguments:</h5>
				3484	<p>
				3485	The '<tt>sext</tt>' instruction takes a value to cast, which must be of
Chris Lattner	3b19d65	2007-01-15 01:54:13 +0000	[diff] [blame]	3486	<a href="#t_integer">integer</a> type, and a type to cast it to, which must
				3487	also be of <a href="#t_integer">integer</a> type. The bit size of the
Reid Spencer	d444879	2006-11-09 23:03:26 +0000	[diff] [blame]	3488	<tt>value</tt> must be smaller than the bit size of the destination type,
				3489	<tt>ty2</tt>.</p>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3490
				3491	<h5>Semantics:</h5>
				3492	<p>
				3493	The '<tt>sext</tt>' instruction performs a sign extension by copying the sign
				3494	bit (highest order bit) of the <tt>value</tt> until it reaches the bit size of
Chris Lattner	d1d2517	2007-05-24 19:13:27 +0000	[diff] [blame]	3495	the type <tt>ty2</tt>.</p>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3496
Reid Spencer	c78f337	2007-01-12 03:35:51 +0000	[diff] [blame]	3497	<p>When sign extending from i1, the extension always results in -1 or 0.</p>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3498
				3499	<h5>Example:</h5>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3500	<pre>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	3501	%X = sext i8 -1 to i16 <i>; yields i16 :65535</i>
Reid Spencer	c78f337	2007-01-12 03:35:51 +0000	[diff] [blame]	3502	%Y = sext i1 true to i32 <i>; yields i32:-1</i>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3503	</pre>
				3504	</div>
				3505
				3506	<!-- _______________________________________________________________________ -->
				3507	<div class="doc_subsubsection">
Reid Spencer	3fa91b0	2006-11-09 21:48:10 +0000	[diff] [blame]	3508	<a name="i_fptrunc">'<tt>fptrunc .. to</tt>' Instruction</a>
				3509	</div>
				3510
				3511	<div class="doc_text">
				3512
				3513	<h5>Syntax:</h5>
				3514
				3515	<pre>
				3516	<result> = fptrunc <ty> <value> to <ty2> <i>; yields ty2</i>
				3517	</pre>
				3518
				3519	<h5>Overview:</h5>
				3520	<p>The '<tt>fptrunc</tt>' instruction truncates <tt>value</tt> to type
				3521	<tt>ty2</tt>.</p>
				3522
				3523
				3524	<h5>Arguments:</h5>
				3525	<p>The '<tt>fptrunc</tt>' instruction takes a <a href="#t_floating">floating
				3526	point</a> value to cast and a <a href="#t_floating">floating point</a> type to
				3527	cast it to. The size of <tt>value</tt> must be larger than the size of
				3528	<tt>ty2</tt>. This implies that <tt>fptrunc</tt> cannot be used to make a
				3529	<i>no-op cast</i>.</p>
				3530
				3531	<h5>Semantics:</h5>
Reid Spencer	d444879	2006-11-09 23:03:26 +0000	[diff] [blame]	3532	<p> The '<tt>fptrunc</tt>' instruction truncates a <tt>value</tt> from a larger
				3533	<a href="#t_floating">floating point</a> type to a smaller
				3534	<a href="#t_floating">floating point</a> type. If the value cannot fit within
				3535	the destination type, <tt>ty2</tt>, then the results are undefined.</p>
Reid Spencer	3fa91b0	2006-11-09 21:48:10 +0000	[diff] [blame]	3536
				3537	<h5>Example:</h5>
				3538	<pre>
				3539	%X = fptrunc double 123.0 to float <i>; yields float:123.0</i>
				3540	%Y = fptrunc double 1.0E+300 to float <i>; yields undefined</i>
				3541	</pre>
				3542	</div>
				3543
				3544	<!-- _______________________________________________________________________ -->
				3545	<div class="doc_subsubsection">
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3546	<a name="i_fpext">'<tt>fpext .. to</tt>' Instruction</a>
				3547	</div>
				3548	<div class="doc_text">
				3549
				3550	<h5>Syntax:</h5>
				3551	<pre>
				3552	<result> = fpext <ty> <value> to <ty2> <i>; yields ty2</i>
				3553	</pre>
				3554
				3555	<h5>Overview:</h5>
				3556	<p>The '<tt>fpext</tt>' extends a floating point <tt>value</tt> to a larger
				3557	floating point value.</p>
				3558
				3559	<h5>Arguments:</h5>
				3560	<p>The '<tt>fpext</tt>' instruction takes a
				3561	<a href="#t_floating">floating point</a> <tt>value</tt> to cast,
Reid Spencer	d444879	2006-11-09 23:03:26 +0000	[diff] [blame]	3562	and a <a href="#t_floating">floating point</a> type to cast it to. The source
				3563	type must be smaller than the destination type.</p>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3564
				3565	<h5>Semantics:</h5>
Reid Spencer	d444879	2006-11-09 23:03:26 +0000	[diff] [blame]	3566	<p>The '<tt>fpext</tt>' instruction extends the <tt>value</tt> from a smaller
Duncan Sands	8036ca4	2007-03-30 12:22:09 +0000	[diff] [blame]	3567	<a href="#t_floating">floating point</a> type to a larger
				3568	<a href="#t_floating">floating point</a> type. The <tt>fpext</tt> cannot be
Reid Spencer	d444879	2006-11-09 23:03:26 +0000	[diff] [blame]	3569	used to make a <i>no-op cast</i> because it always changes bits. Use
Reid Spencer	5c0ef47	2006-11-11 23:08:07 +0000	[diff] [blame]	3570	<tt>bitcast</tt> to make a <i>no-op cast</i> for a floating point cast.</p>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3571
				3572	<h5>Example:</h5>
				3573	<pre>
				3574	%X = fpext float 3.1415 to double <i>; yields double:3.1415</i>
				3575	%Y = fpext float 1.0 to float <i>; yields float:1.0 (no-op)</i>
				3576	</pre>
				3577	</div>
				3578
				3579	<!-- _______________________________________________________________________ -->
				3580	<div class="doc_subsubsection">
Reid Spencer	24d6da5	2007-01-21 00:29:26 +0000	[diff] [blame]	3581	<a name="i_fptoui">'<tt>fptoui .. to</tt>' Instruction</a>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3582	</div>
				3583	<div class="doc_text">
				3584
				3585	<h5>Syntax:</h5>
				3586	<pre>
Reid Spencer	1539a1c	2007-07-31 14:40:14 +0000	[diff] [blame]	3587	<result> = fptoui <ty> <value> to <ty2> <i>; yields ty2</i>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3588	</pre>
				3589
				3590	<h5>Overview:</h5>
Reid Spencer	1539a1c	2007-07-31 14:40:14 +0000	[diff] [blame]	3591	<p>The '<tt>fptoui</tt>' converts a floating point <tt>value</tt> to its
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3592	unsigned integer equivalent of type <tt>ty2</tt>.
				3593	</p>
				3594
				3595	<h5>Arguments:</h5>
Reid Spencer	1539a1c	2007-07-31 14:40:14 +0000	[diff] [blame]	3596	<p>The '<tt>fptoui</tt>' instruction takes a value to cast, which must be a
Nate Begeman	b348d18	2007-11-17 03:58:34 +0000	[diff] [blame]	3597	scalar or vector <a href="#t_floating">floating point</a> value, and a type
				3598	to cast it to <tt>ty2</tt>, which must be an <a href="#t_integer">integer</a>
				3599	type. If <tt>ty</tt> is a vector floating point type, <tt>ty2</tt> must be a
				3600	vector integer type with the same number of elements as <tt>ty</tt></p>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3601
				3602	<h5>Semantics:</h5>
Reid Spencer	1539a1c	2007-07-31 14:40:14 +0000	[diff] [blame]	3603	<p> The '<tt>fptoui</tt>' instruction converts its
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3604	<a href="#t_floating">floating point</a> operand into the nearest (rounding
				3605	towards zero) unsigned integer value. If the value cannot fit in <tt>ty2</tt>,
				3606	the results are undefined.</p>
				3607
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3608	<h5>Example:</h5>
				3609	<pre>
Reid Spencer	1539a1c	2007-07-31 14:40:14 +0000	[diff] [blame]	3610	%X = fptoui double 123.0 to i32 <i>; yields i32:123</i>
Chris Lattner	8851904	2007-09-22 03:17:52 +0000	[diff] [blame]	3611	%Y = fptoui float 1.0E+300 to i1 <i>; yields undefined:1</i>
Reid Spencer	1539a1c	2007-07-31 14:40:14 +0000	[diff] [blame]	3612	%X = fptoui float 1.04E+17 to i8 <i>; yields undefined:1</i>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3613	</pre>
				3614	</div>
				3615
				3616	<!-- _______________________________________________________________________ -->
				3617	<div class="doc_subsubsection">
Reid Spencer	d444879	2006-11-09 23:03:26 +0000	[diff] [blame]	3618	<a name="i_fptosi">'<tt>fptosi .. to</tt>' Instruction</a>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3619	</div>
				3620	<div class="doc_text">
				3621
				3622	<h5>Syntax:</h5>
				3623	<pre>
Reid Spencer	d444879	2006-11-09 23:03:26 +0000	[diff] [blame]	3624	<result> = fptosi <ty> <value> to <ty2> <i>; yields ty2</i>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3625	</pre>
				3626
				3627	<h5>Overview:</h5>
Reid Spencer	d444879	2006-11-09 23:03:26 +0000	[diff] [blame]	3628	<p>The '<tt>fptosi</tt>' instruction converts
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3629	<a href="#t_floating">floating point</a> <tt>value</tt> to type <tt>ty2</tt>.
Chris Lattner	cc37aae	2004-03-12 05:50:16 +0000	[diff] [blame]	3630	</p>
				3631
Chris Lattner	6536cfe	2002-05-06 22:08:29 +0000	[diff] [blame]	3632	<h5>Arguments:</h5>
Reid Spencer	d444879	2006-11-09 23:03:26 +0000	[diff] [blame]	3633	<p> The '<tt>fptosi</tt>' instruction takes a value to cast, which must be a
Nate Begeman	b348d18	2007-11-17 03:58:34 +0000	[diff] [blame]	3634	scalar or vector <a href="#t_floating">floating point</a> value, and a type
				3635	to cast it to <tt>ty2</tt>, which must be an <a href="#t_integer">integer</a>
				3636	type. If <tt>ty</tt> is a vector floating point type, <tt>ty2</tt> must be a
				3637	vector integer type with the same number of elements as <tt>ty</tt></p>
Chris Lattner	cc37aae	2004-03-12 05:50:16 +0000	[diff] [blame]	3638
Chris Lattner	6536cfe	2002-05-06 22:08:29 +0000	[diff] [blame]	3639	<h5>Semantics:</h5>
Reid Spencer	d444879	2006-11-09 23:03:26 +0000	[diff] [blame]	3640	<p>The '<tt>fptosi</tt>' instruction converts its
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3641	<a href="#t_floating">floating point</a> operand into the nearest (rounding
				3642	towards zero) signed integer value. If the value cannot fit in <tt>ty2</tt>,
				3643	the results are undefined.</p>
Chris Lattner	cc37aae	2004-03-12 05:50:16 +0000	[diff] [blame]	3644
Chris Lattner	33ba0d9	2001-07-09 00:26:23 +0000	[diff] [blame]	3645	<h5>Example:</h5>
Chris Lattner	cc37aae	2004-03-12 05:50:16 +0000	[diff] [blame]	3646	<pre>
Reid Spencer	c78f337	2007-01-12 03:35:51 +0000	[diff] [blame]	3647	%X = fptosi double -123.0 to i32 <i>; yields i32:-123</i>
Chris Lattner	8851904	2007-09-22 03:17:52 +0000	[diff] [blame]	3648	%Y = fptosi float 1.0E-247 to i1 <i>; yields undefined:1</i>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	3649	%X = fptosi float 1.04E+17 to i8 <i>; yields undefined:1</i>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3650	</pre>
				3651	</div>
				3652
				3653	<!-- _______________________________________________________________________ -->
				3654	<div class="doc_subsubsection">
Reid Spencer	d444879	2006-11-09 23:03:26 +0000	[diff] [blame]	3655	<a name="i_uitofp">'<tt>uitofp .. to</tt>' Instruction</a>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3656	</div>
				3657	<div class="doc_text">
				3658
				3659	<h5>Syntax:</h5>
				3660	<pre>
Reid Spencer	d444879	2006-11-09 23:03:26 +0000	[diff] [blame]	3661	<result> = uitofp <ty> <value> to <ty2> <i>; yields ty2</i>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3662	</pre>
				3663
				3664	<h5>Overview:</h5>
Reid Spencer	d444879	2006-11-09 23:03:26 +0000	[diff] [blame]	3665	<p>The '<tt>uitofp</tt>' instruction regards <tt>value</tt> as an unsigned
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3666	integer and converts that value to the <tt>ty2</tt> type.</p>
				3667
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3668	<h5>Arguments:</h5>
Nate Begeman	b348d18	2007-11-17 03:58:34 +0000	[diff] [blame]	3669	<p>The '<tt>uitofp</tt>' instruction takes a value to cast, which must be a
				3670	scalar or vector <a href="#t_integer">integer</a> value, and a type to cast it
				3671	to <tt>ty2</tt>, which must be an <a href="#t_floating">floating point</a>
				3672	type. If <tt>ty</tt> is a vector integer type, <tt>ty2</tt> must be a vector
				3673	floating point type with the same number of elements as <tt>ty</tt></p>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3674
				3675	<h5>Semantics:</h5>
Reid Spencer	d444879	2006-11-09 23:03:26 +0000	[diff] [blame]	3676	<p>The '<tt>uitofp</tt>' instruction interprets its operand as an unsigned
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3677	integer quantity and converts it to the corresponding floating point value. If
Jeff Cohen	cb75731	2007-04-22 14:56:37 +0000	[diff] [blame]	3678	the value cannot fit in the floating point value, the results are undefined.</p>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3679
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3680	<h5>Example:</h5>
				3681	<pre>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	3682	%X = uitofp i32 257 to float <i>; yields float:257.0</i>
Jeff Cohen	b627eab	2007-04-29 01:07:00 +0000	[diff] [blame]	3683	%Y = uitofp i8 -1 to double <i>; yields double:255.0</i>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3684	</pre>
				3685	</div>
				3686
				3687	<!-- _______________________________________________________________________ -->
				3688	<div class="doc_subsubsection">
Reid Spencer	d444879	2006-11-09 23:03:26 +0000	[diff] [blame]	3689	<a name="i_sitofp">'<tt>sitofp .. to</tt>' Instruction</a>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3690	</div>
				3691	<div class="doc_text">
				3692
				3693	<h5>Syntax:</h5>
				3694	<pre>
Reid Spencer	d444879	2006-11-09 23:03:26 +0000	[diff] [blame]	3695	<result> = sitofp <ty> <value> to <ty2> <i>; yields ty2</i>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3696	</pre>
				3697
				3698	<h5>Overview:</h5>
Reid Spencer	d444879	2006-11-09 23:03:26 +0000	[diff] [blame]	3699	<p>The '<tt>sitofp</tt>' instruction regards <tt>value</tt> as a signed
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3700	integer and converts that value to the <tt>ty2</tt> type.</p>
				3701
				3702	<h5>Arguments:</h5>
Nate Begeman	b348d18	2007-11-17 03:58:34 +0000	[diff] [blame]	3703	<p>The '<tt>sitofp</tt>' instruction takes a value to cast, which must be a
				3704	scalar or vector <a href="#t_integer">integer</a> value, and a type to cast it
				3705	to <tt>ty2</tt>, which must be an <a href="#t_floating">floating point</a>
				3706	type. If <tt>ty</tt> is a vector integer type, <tt>ty2</tt> must be a vector
				3707	floating point type with the same number of elements as <tt>ty</tt></p>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3708
				3709	<h5>Semantics:</h5>
Reid Spencer	d444879	2006-11-09 23:03:26 +0000	[diff] [blame]	3710	<p>The '<tt>sitofp</tt>' instruction interprets its operand as a signed
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3711	integer quantity and converts it to the corresponding floating point value. If
Jeff Cohen	cb75731	2007-04-22 14:56:37 +0000	[diff] [blame]	3712	the value cannot fit in the floating point value, the results are undefined.</p>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3713
				3714	<h5>Example:</h5>
				3715	<pre>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	3716	%X = sitofp i32 257 to float <i>; yields float:257.0</i>
Jeff Cohen	b627eab	2007-04-29 01:07:00 +0000	[diff] [blame]	3717	%Y = sitofp i8 -1 to double <i>; yields double:-1.0</i>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3718	</pre>
				3719	</div>
				3720
				3721	<!-- _______________________________________________________________________ -->
				3722	<div class="doc_subsubsection">
Reid Spencer	7267925	2006-11-11 21:00:47 +0000	[diff] [blame]	3723	<a name="i_ptrtoint">'<tt>ptrtoint .. to</tt>' Instruction</a>
				3724	</div>
				3725	<div class="doc_text">
				3726
				3727	<h5>Syntax:</h5>
				3728	<pre>
				3729	<result> = ptrtoint <ty> <value> to <ty2> <i>; yields ty2</i>
				3730	</pre>
				3731
				3732	<h5>Overview:</h5>
				3733	<p>The '<tt>ptrtoint</tt>' instruction converts the pointer <tt>value</tt> to
				3734	the integer type <tt>ty2</tt>.</p>
				3735
				3736	<h5>Arguments:</h5>
				3737	<p>The '<tt>ptrtoint</tt>' instruction takes a <tt>value</tt> to cast, which
Duncan Sands	8036ca4	2007-03-30 12:22:09 +0000	[diff] [blame]	3738	must be a <a href="#t_pointer">pointer</a> value, and a type to cast it to
Reid Spencer	7267925	2006-11-11 21:00:47 +0000	[diff] [blame]	3739	<tt>ty2</tt>, which must be an <a href="#t_integer">integer</a> type.
				3740
				3741	<h5>Semantics:</h5>
				3742	<p>The '<tt>ptrtoint</tt>' instruction converts <tt>value</tt> to integer type
				3743	<tt>ty2</tt> by interpreting the pointer value as an integer and either
				3744	truncating or zero extending that value to the size of the integer type. If
				3745	<tt>value</tt> is smaller than <tt>ty2</tt> then a zero extension is done. If
				3746	<tt>value</tt> is larger than <tt>ty2</tt> then a truncation is done. If they
Jeff Cohen	b627eab	2007-04-29 01:07:00 +0000	[diff] [blame]	3747	are the same size, then nothing is done (<i>no-op cast</i>) other than a type
				3748	change.</p>
Reid Spencer	7267925	2006-11-11 21:00:47 +0000	[diff] [blame]	3749
				3750	<h5>Example:</h5>
				3751	<pre>
Jeff Cohen	b627eab	2007-04-29 01:07:00 +0000	[diff] [blame]	3752	%X = ptrtoint i32* %X to i8 <i>; yields truncation on 32-bit architecture</i>
				3753	%Y = ptrtoint i32* %x to i64 <i>; yields zero extension on 32-bit architecture</i>
Reid Spencer	7267925	2006-11-11 21:00:47 +0000	[diff] [blame]	3754	</pre>
				3755	</div>
				3756
				3757	<!-- _______________________________________________________________________ -->
				3758	<div class="doc_subsubsection">
				3759	<a name="i_inttoptr">'<tt>inttoptr .. to</tt>' Instruction</a>
				3760	</div>
				3761	<div class="doc_text">
				3762
				3763	<h5>Syntax:</h5>
				3764	<pre>
				3765	<result> = inttoptr <ty> <value> to <ty2> <i>; yields ty2</i>
				3766	</pre>
				3767
				3768	<h5>Overview:</h5>
				3769	<p>The '<tt>inttoptr</tt>' instruction converts an integer <tt>value</tt> to
				3770	a pointer type, <tt>ty2</tt>.</p>
				3771
				3772	<h5>Arguments:</h5>
Duncan Sands	8036ca4	2007-03-30 12:22:09 +0000	[diff] [blame]	3773	<p>The '<tt>inttoptr</tt>' instruction takes an <a href="#t_integer">integer</a>
Reid Spencer	7267925	2006-11-11 21:00:47 +0000	[diff] [blame]	3774	value to cast, and a type to cast it to, which must be a
Anton Korobeynikov	7f70559	2007-01-12 19:20:47 +0000	[diff] [blame]	3775	<a href="#t_pointer">pointer</a> type.
Reid Spencer	7267925	2006-11-11 21:00:47 +0000	[diff] [blame]	3776
				3777	<h5>Semantics:</h5>
				3778	<p>The '<tt>inttoptr</tt>' instruction converts <tt>value</tt> to type
				3779	<tt>ty2</tt> by applying either a zero extension or a truncation depending on
				3780	the size of the integer <tt>value</tt>. If <tt>value</tt> is larger than the
				3781	size of a pointer then a truncation is done. If <tt>value</tt> is smaller than
				3782	the size of a pointer then a zero extension is done. If they are the same size,
				3783	nothing is done (<i>no-op cast</i>).</p>
				3784
				3785	<h5>Example:</h5>
				3786	<pre>
Jeff Cohen	b627eab	2007-04-29 01:07:00 +0000	[diff] [blame]	3787	%X = inttoptr i32 255 to i32* <i>; yields zero extension on 64-bit architecture</i>
				3788	%X = inttoptr i32 255 to i32* <i>; yields no-op on 32-bit architecture</i>
				3789	%Y = inttoptr i64 0 to i32* <i>; yields truncation on 32-bit architecture</i>
Reid Spencer	7267925	2006-11-11 21:00:47 +0000	[diff] [blame]	3790	</pre>
				3791	</div>
				3792
				3793	<!-- _______________________________________________________________________ -->
				3794	<div class="doc_subsubsection">
Reid Spencer	5c0ef47	2006-11-11 23:08:07 +0000	[diff] [blame]	3795	<a name="i_bitcast">'<tt>bitcast .. to</tt>' Instruction</a>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3796	</div>
				3797	<div class="doc_text">
				3798
				3799	<h5>Syntax:</h5>
				3800	<pre>
Reid Spencer	5c0ef47	2006-11-11 23:08:07 +0000	[diff] [blame]	3801	<result> = bitcast <ty> <value> to <ty2> <i>; yields ty2</i>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3802	</pre>
				3803
				3804	<h5>Overview:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	3805
Reid Spencer	5c0ef47	2006-11-11 23:08:07 +0000	[diff] [blame]	3806	<p>The '<tt>bitcast</tt>' instruction converts <tt>value</tt> to type
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3807	<tt>ty2</tt> without changing any bits.</p>
				3808
				3809	<h5>Arguments:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	3810
Reid Spencer	5c0ef47	2006-11-11 23:08:07 +0000	[diff] [blame]	3811	<p>The '<tt>bitcast</tt>' instruction takes a value to cast, which must be
Dan Gohman	500233a	2008-09-08 16:45:59 +0000	[diff] [blame]	3812	a non-aggregate first class value, and a type to cast it to, which must also be
				3813	a non-aggregate <a href="#t_firstclass">first class</a> type. The bit sizes of
				3814	<tt>value</tt>
Reid Spencer	19b569f	2007-01-09 20:08:58 +0000	[diff] [blame]	3815	and the destination type, <tt>ty2</tt>, must be identical. If the source
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	3816	type is a pointer, the destination type must also be a pointer. This
				3817	instruction supports bitwise conversion of vectors to integers and to vectors
				3818	of other types (as long as they have the same size).</p>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3819
				3820	<h5>Semantics:</h5>
Reid Spencer	5c0ef47	2006-11-11 23:08:07 +0000	[diff] [blame]	3821	<p>The '<tt>bitcast</tt>' instruction converts <tt>value</tt> to type
Reid Spencer	7267925	2006-11-11 21:00:47 +0000	[diff] [blame]	3822	<tt>ty2</tt>. It is always a <i>no-op cast</i> because no bits change with
				3823	this conversion. The conversion is done as if the <tt>value</tt> had been
				3824	stored to memory and read back as type <tt>ty2</tt>. Pointer types may only be
				3825	converted to other pointer types with this instruction. To convert pointers to
				3826	other types, use the <a href="#i_inttoptr">inttoptr</a> or
				3827	<a href="#i_ptrtoint">ptrtoint</a> instructions first.</p>
Reid Spencer	9dee3ac	2006-11-08 01:11:31 +0000	[diff] [blame]	3828
				3829	<h5>Example:</h5>
				3830	<pre>
Jeff Cohen	b627eab	2007-04-29 01:07:00 +0000	[diff] [blame]	3831	%X = bitcast i8 255 to i8 <i>; yields i8 :-1</i>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	3832	%Y = bitcast i32* %x to sint* <i>; yields sint*:%x</i>
				3833	%Z = bitcast <2xint> %V to i64; <i>; yields i64: %V</i>
Chris Lattner	33ba0d9	2001-07-09 00:26:23 +0000	[diff] [blame]	3834	</pre>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	3835	</div>
Chris Lattner	cc37aae	2004-03-12 05:50:16 +0000	[diff] [blame]	3836
Reid Spencer	2fd21e6	2006-11-08 01:18:52 +0000	[diff] [blame]	3837	<!-- ======================================================================= -->
				3838	<div class="doc_subsection"> <a name="otherops">Other Operations</a> </div>
				3839	<div class="doc_text">
				3840	<p>The instructions in this category are the "miscellaneous"
				3841	instructions, which defy better classification.</p>
				3842	</div>
Reid Spencer	f3a70a6	2006-11-18 21:50:54 +0000	[diff] [blame]	3843
				3844	<!-- _______________________________________________________________________ -->
				3845	<div class="doc_subsubsection"><a name="i_icmp">'<tt>icmp</tt>' Instruction</a>
				3846	</div>
				3847	<div class="doc_text">
				3848	<h5>Syntax:</h5>
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	3849	<pre> <result> = icmp <cond> <ty> <op1>, <op2> <i>; yields {i1}:result</i>
Reid Spencer	f3a70a6	2006-11-18 21:50:54 +0000	[diff] [blame]	3850	</pre>
				3851	<h5>Overview:</h5>
				3852	<p>The '<tt>icmp</tt>' instruction returns a boolean value based on comparison
Chris Lattner	4316dec	2008-04-02 00:38:26 +0000	[diff] [blame]	3853	of its two integer or pointer operands.</p>
Reid Spencer	f3a70a6	2006-11-18 21:50:54 +0000	[diff] [blame]	3854	<h5>Arguments:</h5>
				3855	<p>The '<tt>icmp</tt>' instruction takes three operands. The first operand is
Jeff Cohen	b627eab	2007-04-29 01:07:00 +0000	[diff] [blame]	3856	the condition code indicating the kind of comparison to perform. It is not
				3857	a value, just a keyword. The possible condition code are:
Reid Spencer	f3a70a6	2006-11-18 21:50:54 +0000	[diff] [blame]	3858	<ol>
				3859	<li><tt>eq</tt>: equal</li>
				3860	<li><tt>ne</tt>: not equal </li>
				3861	<li><tt>ugt</tt>: unsigned greater than</li>
				3862	<li><tt>uge</tt>: unsigned greater or equal</li>
				3863	<li><tt>ult</tt>: unsigned less than</li>
				3864	<li><tt>ule</tt>: unsigned less or equal</li>
				3865	<li><tt>sgt</tt>: signed greater than</li>
				3866	<li><tt>sge</tt>: signed greater or equal</li>
				3867	<li><tt>slt</tt>: signed less than</li>
				3868	<li><tt>sle</tt>: signed less or equal</li>
				3869	</ol>
Chris Lattner	3b19d65	2007-01-15 01:54:13 +0000	[diff] [blame]	3870	<p>The remaining two arguments must be <a href="#t_integer">integer</a> or
Reid Spencer	350f8aa	2007-01-04 05:19:58 +0000	[diff] [blame]	3871	<a href="#t_pointer">pointer</a> typed. They must also be identical types.</p>
Reid Spencer	f3a70a6	2006-11-18 21:50:54 +0000	[diff] [blame]	3872	<h5>Semantics:</h5>
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	3873	<p>The '<tt>icmp</tt>' compares <tt>op1</tt> and <tt>op2</tt> according to
Reid Spencer	f3a70a6	2006-11-18 21:50:54 +0000	[diff] [blame]	3874	the condition code given as <tt>cond</tt>. The comparison performed always
Reid Spencer	c78f337	2007-01-12 03:35:51 +0000	[diff] [blame]	3875	yields a <a href="#t_primitive">i1</a> result, as follows:
Reid Spencer	f3a70a6	2006-11-18 21:50:54 +0000	[diff] [blame]	3876	<ol>
				3877	<li><tt>eq</tt>: yields <tt>true</tt> if the operands are equal,
				3878	<tt>false</tt> otherwise. No sign interpretation is necessary or performed.
				3879	</li>
				3880	<li><tt>ne</tt>: yields <tt>true</tt> if the operands are unequal,
				3881	<tt>false</tt> otherwise. No sign interpretation is necessary or performed.
				3882	<li><tt>ugt</tt>: interprets the operands as unsigned values and yields
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	3883	<tt>true</tt> if <tt>op1</tt> is greater than <tt>op2</tt>.</li>
Reid Spencer	f3a70a6	2006-11-18 21:50:54 +0000	[diff] [blame]	3884	<li><tt>uge</tt>: interprets the operands as unsigned values and yields
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	3885	<tt>true</tt> if <tt>op1</tt> is greater than or equal to <tt>op2</tt>.</li>
Reid Spencer	f3a70a6	2006-11-18 21:50:54 +0000	[diff] [blame]	3886	<li><tt>ult</tt>: interprets the operands as unsigned values and yields
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	3887	<tt>true</tt> if <tt>op1</tt> is less than <tt>op2</tt>.</li>
Reid Spencer	f3a70a6	2006-11-18 21:50:54 +0000	[diff] [blame]	3888	<li><tt>ule</tt>: interprets the operands as unsigned values and yields
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	3889	<tt>true</tt> if <tt>op1</tt> is less than or equal to <tt>op2</tt>.</li>
Reid Spencer	f3a70a6	2006-11-18 21:50:54 +0000	[diff] [blame]	3890	<li><tt>sgt</tt>: interprets the operands as signed values and yields
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	3891	<tt>true</tt> if <tt>op1</tt> is greater than <tt>op2</tt>.</li>
Reid Spencer	f3a70a6	2006-11-18 21:50:54 +0000	[diff] [blame]	3892	<li><tt>sge</tt>: interprets the operands as signed values and yields
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	3893	<tt>true</tt> if <tt>op1</tt> is greater than or equal to <tt>op2</tt>.</li>
Reid Spencer	f3a70a6	2006-11-18 21:50:54 +0000	[diff] [blame]	3894	<li><tt>slt</tt>: interprets the operands as signed values and yields
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	3895	<tt>true</tt> if <tt>op1</tt> is less than <tt>op2</tt>.</li>
Reid Spencer	f3a70a6	2006-11-18 21:50:54 +0000	[diff] [blame]	3896	<li><tt>sle</tt>: interprets the operands as signed values and yields
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	3897	<tt>true</tt> if <tt>op1</tt> is less than or equal to <tt>op2</tt>.</li>
Reid Spencer	f3a70a6	2006-11-18 21:50:54 +0000	[diff] [blame]	3898	</ol>
				3899	<p>If the operands are <a href="#t_pointer">pointer</a> typed, the pointer
Jeff Cohen	b627eab	2007-04-29 01:07:00 +0000	[diff] [blame]	3900	values are compared as if they were integers.</p>
Reid Spencer	f3a70a6	2006-11-18 21:50:54 +0000	[diff] [blame]	3901
				3902	<h5>Example:</h5>
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	3903	<pre> <result> = icmp eq i32 4, 5 <i>; yields: result=false</i>
				3904	<result> = icmp ne float* %X, %X <i>; yields: result=false</i>
				3905	<result> = icmp ult i16 4, 5 <i>; yields: result=true</i>
				3906	<result> = icmp sgt i16 4, 5 <i>; yields: result=false</i>
				3907	<result> = icmp ule i16 -4, 5 <i>; yields: result=false</i>
				3908	<result> = icmp sge i16 4, 5 <i>; yields: result=false</i>
Reid Spencer	f3a70a6	2006-11-18 21:50:54 +0000	[diff] [blame]	3909	</pre>
				3910	</div>
				3911
				3912	<!-- _______________________________________________________________________ -->
				3913	<div class="doc_subsubsection"><a name="i_fcmp">'<tt>fcmp</tt>' Instruction</a>
				3914	</div>
				3915	<div class="doc_text">
				3916	<h5>Syntax:</h5>
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	3917	<pre> <result> = fcmp <cond> <ty> <op1>, <op2> <i>; yields {i1}:result</i>
Reid Spencer	f3a70a6	2006-11-18 21:50:54 +0000	[diff] [blame]	3918	</pre>
				3919	<h5>Overview:</h5>
				3920	<p>The '<tt>fcmp</tt>' instruction returns a boolean value based on comparison
				3921	of its floating point operands.</p>
				3922	<h5>Arguments:</h5>
				3923	<p>The '<tt>fcmp</tt>' instruction takes three operands. The first operand is
Jeff Cohen	b627eab	2007-04-29 01:07:00 +0000	[diff] [blame]	3924	the condition code indicating the kind of comparison to perform. It is not
				3925	a value, just a keyword. The possible condition code are:
Reid Spencer	f3a70a6	2006-11-18 21:50:54 +0000	[diff] [blame]	3926	<ol>
Reid Spencer	b7f2628	2006-11-19 03:00:14 +0000	[diff] [blame]	3927	<li><tt>false</tt>: no comparison, always returns false</li>
Reid Spencer	f3a70a6	2006-11-18 21:50:54 +0000	[diff] [blame]	3928	<li><tt>oeq</tt>: ordered and equal</li>
				3929	<li><tt>ogt</tt>: ordered and greater than </li>
				3930	<li><tt>oge</tt>: ordered and greater than or equal</li>
				3931	<li><tt>olt</tt>: ordered and less than </li>
				3932	<li><tt>ole</tt>: ordered and less than or equal</li>
				3933	<li><tt>one</tt>: ordered and not equal</li>
				3934	<li><tt>ord</tt>: ordered (no nans)</li>
				3935	<li><tt>ueq</tt>: unordered or equal</li>
				3936	<li><tt>ugt</tt>: unordered or greater than </li>
				3937	<li><tt>uge</tt>: unordered or greater than or equal</li>
				3938	<li><tt>ult</tt>: unordered or less than </li>
				3939	<li><tt>ule</tt>: unordered or less than or equal</li>
				3940	<li><tt>une</tt>: unordered or not equal</li>
				3941	<li><tt>uno</tt>: unordered (either nans)</li>
Reid Spencer	b7f2628	2006-11-19 03:00:14 +0000	[diff] [blame]	3942	<li><tt>true</tt>: no comparison, always returns true</li>
Reid Spencer	f3a70a6	2006-11-18 21:50:54 +0000	[diff] [blame]	3943	</ol>
Jeff Cohen	b627eab	2007-04-29 01:07:00 +0000	[diff] [blame]	3944	<p><i>Ordered</i> means that neither operand is a QNAN while
Reid Spencer	93a4985	2006-12-06 07:08:07 +0000	[diff] [blame]	3945	<i>unordered</i> means that either operand may be a QNAN.</p>
Reid Spencer	350f8aa	2007-01-04 05:19:58 +0000	[diff] [blame]	3946	<p>The <tt>val1</tt> and <tt>val2</tt> arguments must be
				3947	<a href="#t_floating">floating point</a> typed. They must have identical
				3948	types.</p>
Reid Spencer	f3a70a6	2006-11-18 21:50:54 +0000	[diff] [blame]	3949	<h5>Semantics:</h5>
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	3950	<p>The '<tt>fcmp</tt>' instruction compares <tt>op1</tt> and <tt>op2</tt>
Nate Begeman	ac80ade	2008-05-12 19:01:56 +0000	[diff] [blame]	3951	according to the condition code given as <tt>cond</tt>. The comparison performed
				3952	always yields a <a href="#t_primitive">i1</a> result, as follows:
Reid Spencer	f3a70a6	2006-11-18 21:50:54 +0000	[diff] [blame]	3953	<ol>
				3954	<li><tt>false</tt>: always yields <tt>false</tt>, regardless of operands.</li>
Reid Spencer	b7f2628	2006-11-19 03:00:14 +0000	[diff] [blame]	3955	<li><tt>oeq</tt>: yields <tt>true</tt> if both operands are not a QNAN and
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	3956	<tt>op1</tt> is equal to <tt>op2</tt>.</li>
Reid Spencer	b7f2628	2006-11-19 03:00:14 +0000	[diff] [blame]	3957	<li><tt>ogt</tt>: yields <tt>true</tt> if both operands are not a QNAN and
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	3958	<tt>op1</tt> is greather than <tt>op2</tt>.</li>
Reid Spencer	b7f2628	2006-11-19 03:00:14 +0000	[diff] [blame]	3959	<li><tt>oge</tt>: yields <tt>true</tt> if both operands are not a QNAN and
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	3960	<tt>op1</tt> is greater than or equal to <tt>op2</tt>.</li>
Reid Spencer	b7f2628	2006-11-19 03:00:14 +0000	[diff] [blame]	3961	<li><tt>olt</tt>: yields <tt>true</tt> if both operands are not a QNAN and
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	3962	<tt>op1</tt> is less than <tt>op2</tt>.</li>
Reid Spencer	b7f2628	2006-11-19 03:00:14 +0000	[diff] [blame]	3963	<li><tt>ole</tt>: yields <tt>true</tt> if both operands are not a QNAN and
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	3964	<tt>op1</tt> is less than or equal to <tt>op2</tt>.</li>
Reid Spencer	b7f2628	2006-11-19 03:00:14 +0000	[diff] [blame]	3965	<li><tt>one</tt>: yields <tt>true</tt> if both operands are not a QNAN and
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	3966	<tt>op1</tt> is not equal to <tt>op2</tt>.</li>
Reid Spencer	b7f2628	2006-11-19 03:00:14 +0000	[diff] [blame]	3967	<li><tt>ord</tt>: yields <tt>true</tt> if both operands are not a QNAN.</li>
				3968	<li><tt>ueq</tt>: yields <tt>true</tt> if either operand is a QNAN or
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	3969	<tt>op1</tt> is equal to <tt>op2</tt>.</li>
Reid Spencer	b7f2628	2006-11-19 03:00:14 +0000	[diff] [blame]	3970	<li><tt>ugt</tt>: yields <tt>true</tt> if either operand is a QNAN or
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	3971	<tt>op1</tt> is greater than <tt>op2</tt>.</li>
Reid Spencer	b7f2628	2006-11-19 03:00:14 +0000	[diff] [blame]	3972	<li><tt>uge</tt>: yields <tt>true</tt> if either operand is a QNAN or
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	3973	<tt>op1</tt> is greater than or equal to <tt>op2</tt>.</li>
Reid Spencer	b7f2628	2006-11-19 03:00:14 +0000	[diff] [blame]	3974	<li><tt>ult</tt>: yields <tt>true</tt> if either operand is a QNAN or
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	3975	<tt>op1</tt> is less than <tt>op2</tt>.</li>
Reid Spencer	b7f2628	2006-11-19 03:00:14 +0000	[diff] [blame]	3976	<li><tt>ule</tt>: yields <tt>true</tt> if either operand is a QNAN or
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	3977	<tt>op1</tt> is less than or equal to <tt>op2</tt>.</li>
Reid Spencer	b7f2628	2006-11-19 03:00:14 +0000	[diff] [blame]	3978	<li><tt>une</tt>: yields <tt>true</tt> if either operand is a QNAN or
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	3979	<tt>op1</tt> is not equal to <tt>op2</tt>.</li>
Reid Spencer	b7f2628	2006-11-19 03:00:14 +0000	[diff] [blame]	3980	<li><tt>uno</tt>: yields <tt>true</tt> if either operand is a QNAN.</li>
Reid Spencer	f3a70a6	2006-11-18 21:50:54 +0000	[diff] [blame]	3981	<li><tt>true</tt>: always yields <tt>true</tt>, regardless of operands.</li>
				3982	</ol>
Reid Spencer	f3a70a6	2006-11-18 21:50:54 +0000	[diff] [blame]	3983
				3984	<h5>Example:</h5>
				3985	<pre> <result> = fcmp oeq float 4.0, 5.0 <i>; yields: result=false</i>
				3986	<result> = icmp one float 4.0, 5.0 <i>; yields: result=true</i>
				3987	<result> = icmp olt float 4.0, 5.0 <i>; yields: result=true</i>
				3988	<result> = icmp ueq double 1.0, 2.0 <i>; yields: result=false</i>
				3989	</pre>
				3990	</div>
				3991
Reid Spencer	2fd21e6	2006-11-08 01:18:52 +0000	[diff] [blame]	3992	<!-- _______________________________________________________________________ -->
Nate Begeman	ac80ade	2008-05-12 19:01:56 +0000	[diff] [blame]	3993	<div class="doc_subsubsection">
				3994	<a name="i_vicmp">'<tt>vicmp</tt>' Instruction</a>
				3995	</div>
				3996	<div class="doc_text">
				3997	<h5>Syntax:</h5>
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	3998	<pre> <result> = vicmp <cond> <ty> <op1>, <op2> <i>; yields {ty}:result</i>
Nate Begeman	ac80ade	2008-05-12 19:01:56 +0000	[diff] [blame]	3999	</pre>
				4000	<h5>Overview:</h5>
				4001	<p>The '<tt>vicmp</tt>' instruction returns an integer vector value based on
				4002	element-wise comparison of its two integer vector operands.</p>
				4003	<h5>Arguments:</h5>
				4004	<p>The '<tt>vicmp</tt>' instruction takes three operands. The first operand is
				4005	the condition code indicating the kind of comparison to perform. It is not
				4006	a value, just a keyword. The possible condition code are:
				4007	<ol>
				4008	<li><tt>eq</tt>: equal</li>
				4009	<li><tt>ne</tt>: not equal </li>
				4010	<li><tt>ugt</tt>: unsigned greater than</li>
				4011	<li><tt>uge</tt>: unsigned greater or equal</li>
				4012	<li><tt>ult</tt>: unsigned less than</li>
				4013	<li><tt>ule</tt>: unsigned less or equal</li>
				4014	<li><tt>sgt</tt>: signed greater than</li>
				4015	<li><tt>sge</tt>: signed greater or equal</li>
				4016	<li><tt>slt</tt>: signed less than</li>
				4017	<li><tt>sle</tt>: signed less or equal</li>
				4018	</ol>
				4019	<p>The remaining two arguments must be <a href="#t_vector">vector</a> of
				4020	<a href="#t_integer">integer</a> typed. They must also be identical types.</p>
				4021	<h5>Semantics:</h5>
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	4022	<p>The '<tt>vicmp</tt>' instruction compares <tt>op1</tt> and <tt>op2</tt>
Nate Begeman	ac80ade	2008-05-12 19:01:56 +0000	[diff] [blame]	4023	according to the condition code given as <tt>cond</tt>. The comparison yields a
				4024	<a href="#t_vector">vector</a> of <a href="#t_integer">integer</a> result, of
				4025	identical type as the values being compared. The most significant bit in each
				4026	element is 1 if the element-wise comparison evaluates to true, and is 0
				4027	otherwise. All other bits of the result are undefined. The condition codes
				4028	are evaluated identically to the <a href="#i_icmp">'<tt>icmp</tt>'
				4029	instruction</a>.
				4030
				4031	<h5>Example:</h5>
				4032	<pre>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	4033	<result> = vicmp eq <2 x i32> < i32 4, i32 0>, < i32 5, i32 0> <i>; yields: result=<2 x i32> < i32 0, i32 -1 ></i>
				4034	<result> = vicmp ult <2 x i8 > < i8 1, i8 2>, < i8 2, i8 2 > <i>; yields: result=<2 x i8> < i8 -1, i8 0 ></i>
Nate Begeman	ac80ade	2008-05-12 19:01:56 +0000	[diff] [blame]	4035	</pre>
				4036	</div>
				4037
				4038	<!-- _______________________________________________________________________ -->
				4039	<div class="doc_subsubsection">
				4040	<a name="i_vfcmp">'<tt>vfcmp</tt>' Instruction</a>
				4041	</div>
				4042	<div class="doc_text">
				4043	<h5>Syntax:</h5>
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	4044	<pre> <result> = vfcmp <cond> <ty> <op1>, <op2></pre>
Nate Begeman	ac80ade	2008-05-12 19:01:56 +0000	[diff] [blame]	4045	<h5>Overview:</h5>
				4046	<p>The '<tt>vfcmp</tt>' instruction returns an integer vector value based on
				4047	element-wise comparison of its two floating point vector operands. The output
				4048	elements have the same width as the input elements.</p>
				4049	<h5>Arguments:</h5>
				4050	<p>The '<tt>vfcmp</tt>' instruction takes three operands. The first operand is
				4051	the condition code indicating the kind of comparison to perform. It is not
				4052	a value, just a keyword. The possible condition code are:
				4053	<ol>
				4054	<li><tt>false</tt>: no comparison, always returns false</li>
				4055	<li><tt>oeq</tt>: ordered and equal</li>
				4056	<li><tt>ogt</tt>: ordered and greater than </li>
				4057	<li><tt>oge</tt>: ordered and greater than or equal</li>
				4058	<li><tt>olt</tt>: ordered and less than </li>
				4059	<li><tt>ole</tt>: ordered and less than or equal</li>
				4060	<li><tt>one</tt>: ordered and not equal</li>
				4061	<li><tt>ord</tt>: ordered (no nans)</li>
				4062	<li><tt>ueq</tt>: unordered or equal</li>
				4063	<li><tt>ugt</tt>: unordered or greater than </li>
				4064	<li><tt>uge</tt>: unordered or greater than or equal</li>
				4065	<li><tt>ult</tt>: unordered or less than </li>
				4066	<li><tt>ule</tt>: unordered or less than or equal</li>
				4067	<li><tt>une</tt>: unordered or not equal</li>
				4068	<li><tt>uno</tt>: unordered (either nans)</li>
				4069	<li><tt>true</tt>: no comparison, always returns true</li>
				4070	</ol>
				4071	<p>The remaining two arguments must be <a href="#t_vector">vector</a> of
				4072	<a href="#t_floating">floating point</a> typed. They must also be identical
				4073	types.</p>
				4074	<h5>Semantics:</h5>
Gabor Greif	fb224a2	2008-08-07 21:46:00 +0000	[diff] [blame]	4075	<p>The '<tt>vfcmp</tt>' instruction compares <tt>op1</tt> and <tt>op2</tt>
Nate Begeman	ac80ade	2008-05-12 19:01:56 +0000	[diff] [blame]	4076	according to the condition code given as <tt>cond</tt>. The comparison yields a
				4077	<a href="#t_vector">vector</a> of <a href="#t_integer">integer</a> result, with
				4078	an identical number of elements as the values being compared, and each element
				4079	having identical with to the width of the floating point elements. The most
				4080	significant bit in each element is 1 if the element-wise comparison evaluates to
				4081	true, and is 0 otherwise. All other bits of the result are undefined. The
				4082	condition codes are evaluated identically to the
				4083	<a href="#i_fcmp">'<tt>fcmp</tt>' instruction</a>.
				4084
				4085	<h5>Example:</h5>
				4086	<pre>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	4087	<result> = vfcmp oeq <2 x float> < float 4, float 0 >, < float 5, float 0 > <i>; yields: result=<2 x i32> < i32 0, i32 -1 ></i>
				4088	<result> = vfcmp ult <2 x double> < double 1, double 2 >, < double 2, double 2> <i>; yields: result=<2 x i64> < i64 -1, i64 0 ></i>
Nate Begeman	ac80ade	2008-05-12 19:01:56 +0000	[diff] [blame]	4089	</pre>
				4090	</div>
				4091
				4092	<!-- _______________________________________________________________________ -->
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	4093	<div class="doc_subsubsection">
				4094	<a name="i_phi">'<tt>phi</tt>' Instruction</a>
				4095	</div>
				4096
Reid Spencer	2fd21e6	2006-11-08 01:18:52 +0000	[diff] [blame]	4097	<div class="doc_text">
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	4098
Reid Spencer	2fd21e6	2006-11-08 01:18:52 +0000	[diff] [blame]	4099	<h5>Syntax:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	4100
Reid Spencer	2fd21e6	2006-11-08 01:18:52 +0000	[diff] [blame]	4101	<pre> <result> = phi <ty> [ <val0>, <label0>], ...<br></pre>
				4102	<h5>Overview:</h5>
				4103	<p>The '<tt>phi</tt>' instruction is used to implement the φ node in
				4104	the SSA graph representing the function.</p>
				4105	<h5>Arguments:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	4106
Jeff Cohen	b627eab	2007-04-29 01:07:00 +0000	[diff] [blame]	4107	<p>The type of the incoming values is specified with the first type
Reid Spencer	2fd21e6	2006-11-08 01:18:52 +0000	[diff] [blame]	4108	field. After this, the '<tt>phi</tt>' instruction takes a list of pairs
				4109	as arguments, with one pair for each predecessor basic block of the
				4110	current block. Only values of <a href="#t_firstclass">first class</a>
				4111	type may be used as the value arguments to the PHI node. Only labels
				4112	may be used as the label arguments.</p>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	4113
Reid Spencer	2fd21e6	2006-11-08 01:18:52 +0000	[diff] [blame]	4114	<p>There must be no non-phi instructions between the start of a basic
				4115	block and the PHI instructions: i.e. PHI instructions must be first in
				4116	a basic block.</p>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	4117
Reid Spencer	2fd21e6	2006-11-08 01:18:52 +0000	[diff] [blame]	4118	<h5>Semantics:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	4119
Jeff Cohen	b627eab	2007-04-29 01:07:00 +0000	[diff] [blame]	4120	<p>At runtime, the '<tt>phi</tt>' instruction logically takes on the value
				4121	specified by the pair corresponding to the predecessor basic block that executed
				4122	just prior to the current block.</p>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	4123
Reid Spencer	2fd21e6	2006-11-08 01:18:52 +0000	[diff] [blame]	4124	<h5>Example:</h5>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	4125	<pre>
				4126	Loop: ; Infinite loop that counts from 0 on up...
				4127	%indvar = phi i32 [ 0, %LoopHeader ], [ %nextindvar, %Loop ]
				4128	%nextindvar = add i32 %indvar, 1
				4129	br label %Loop
				4130	</pre>
Reid Spencer	2fd21e6	2006-11-08 01:18:52 +0000	[diff] [blame]	4131	</div>
				4132
Chris Lattner	cc37aae	2004-03-12 05:50:16 +0000	[diff] [blame]	4133	<!-- _______________________________________________________________________ -->
				4134	<div class="doc_subsubsection">
				4135	<a name="i_select">'<tt>select</tt>' Instruction</a>
				4136	</div>
				4137
				4138	<div class="doc_text">
				4139
				4140	<h5>Syntax:</h5>
				4141
				4142	<pre>
Reid Spencer	c78f337	2007-01-12 03:35:51 +0000	[diff] [blame]	4143	<result> = select i1 <cond>, <ty> <val1>, <ty> <val2> <i>; yields ty</i>
Chris Lattner	cc37aae	2004-03-12 05:50:16 +0000	[diff] [blame]	4144	</pre>
				4145
				4146	<h5>Overview:</h5>
				4147
				4148	<p>
				4149	The '<tt>select</tt>' instruction is used to choose one value based on a
				4150	condition, without branching.
				4151	</p>
				4152
				4153
				4154	<h5>Arguments:</h5>
				4155
				4156	<p>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	4157	The '<tt>select</tt>' instruction requires an 'i1' value indicating the
				4158	condition, and two values of the same <a href="#t_firstclass">first class</a>
				4159	type. If the val1/val2 are vectors, the entire vectors are selected, not
				4160	individual elements.
Chris Lattner	cc37aae	2004-03-12 05:50:16 +0000	[diff] [blame]	4161	</p>
				4162
				4163	<h5>Semantics:</h5>
				4164
				4165	<p>
Chris Lattner	5568e94	2008-05-20 20:48:21 +0000	[diff] [blame]	4166	If the i1 condition evaluates is 1, the instruction returns the first
John Criswell	fc6b895	2005-05-16 16:17:45 +0000	[diff] [blame]	4167	value argument; otherwise, it returns the second value argument.
Chris Lattner	cc37aae	2004-03-12 05:50:16 +0000	[diff] [blame]	4168	</p>
				4169
				4170	<h5>Example:</h5>
				4171
				4172	<pre>
Reid Spencer	c78f337	2007-01-12 03:35:51 +0000	[diff] [blame]	4173	%X = select i1 true, i8 17, i8 42 <i>; yields i8:17</i>
Chris Lattner	cc37aae	2004-03-12 05:50:16 +0000	[diff] [blame]	4174	</pre>
				4175	</div>
				4176
Robert Bocchino	05ccd70	2006-01-15 20:48:27 +0000	[diff] [blame]	4177
				4178	<!-- _______________________________________________________________________ -->
				4179	<div class="doc_subsubsection">
Chris Lattner	2bff524	2005-05-06 05:47:36 +0000	[diff] [blame]	4180	<a name="i_call">'<tt>call</tt>' Instruction</a>
				4181	</div>
				4182
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	4183	<div class="doc_text">
Chris Lattner	2bff524	2005-05-06 05:47:36 +0000	[diff] [blame]	4184
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	4185	<h5>Syntax:</h5>
Chris Lattner	2bff524	2005-05-06 05:47:36 +0000	[diff] [blame]	4186	<pre>
Nick Lewycky	db7e3c9	2007-09-08 13:57:50 +0000	[diff] [blame]	4187	<result> = [tail] call [<a href="#callingconv">cconv</a>] <ty> [<fnty>*] <fnptrval>(<param list>)
Chris Lattner	2bff524	2005-05-06 05:47:36 +0000	[diff] [blame]	4188	</pre>
				4189
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	4190	<h5>Overview:</h5>
Chris Lattner	2bff524	2005-05-06 05:47:36 +0000	[diff] [blame]	4191
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	4192	<p>The '<tt>call</tt>' instruction represents a simple function call.</p>
Chris Lattner	2bff524	2005-05-06 05:47:36 +0000	[diff] [blame]	4193
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	4194	<h5>Arguments:</h5>
Chris Lattner	2bff524	2005-05-06 05:47:36 +0000	[diff] [blame]	4195
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	4196	<p>This instruction requires several arguments:</p>
Chris Lattner	2bff524	2005-05-06 05:47:36 +0000	[diff] [blame]	4197
Chris Lattner	6536cfe	2002-05-06 22:08:29 +0000	[diff] [blame]	4198	<ol>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	4199	<li>
Chris Lattner	bad10ee	2005-05-06 22:57:40 +0000	[diff] [blame]	4200	<p>The optional "tail" marker indicates whether the callee function accesses
				4201	any allocas or varargs in the caller. If the "tail" marker is present, the
Chris Lattner	2bff524	2005-05-06 05:47:36 +0000	[diff] [blame]	4202	function call is eligible for tail call optimization. Note that calls may
				4203	be marked "tail" even if they do not occur before a <a
				4204	href="#i_ret"><tt>ret</tt></a> instruction.
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	4205	</li>
				4206	<li>
Duncan Sands	8036ca4	2007-03-30 12:22:09 +0000	[diff] [blame]	4207	<p>The optional "cconv" marker indicates which <a href="#callingconv">calling
Chris Lattner	bad10ee	2005-05-06 22:57:40 +0000	[diff] [blame]	4208	convention</a> the call should use. If none is specified, the call defaults
				4209	to using C calling conventions.
				4210	</li>
				4211	<li>
Nick Lewycky	db7e3c9	2007-09-08 13:57:50 +0000	[diff] [blame]	4212	<p>'<tt>ty</tt>': the type of the call instruction itself which is also
				4213	the type of the return value. Functions that return no value are marked
				4214	<tt><a href="#t_void">void</a></tt>.</p>
				4215	</li>
				4216	<li>
				4217	<p>'<tt>fnty</tt>': shall be the signature of the pointer to function
				4218	value being invoked. The argument types must match the types implied by
				4219	this signature. This type can be omitted if the function is not varargs
				4220	and if the function type does not return a pointer to a function.</p>
Chris Lattner	2bff524	2005-05-06 05:47:36 +0000	[diff] [blame]	4221	</li>
				4222	<li>
				4223	<p>'<tt>fnptrval</tt>': An LLVM value containing a pointer to a function to
				4224	be invoked. In most cases, this is a direct function invocation, but
				4225	indirect <tt>call</tt>s are just as possible, calling an arbitrary pointer
John Criswell	fc6b895	2005-05-16 16:17:45 +0000	[diff] [blame]	4226	to function value.</p>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	4227	</li>
				4228	<li>
				4229	<p>'<tt>function args</tt>': argument list whose types match the
Reid Spencer	a7e302a	2005-05-01 22:22:57 +0000	[diff] [blame]	4230	function signature argument types. All arguments must be of
				4231	<a href="#t_firstclass">first class</a> type. If the function signature
				4232	indicates the function accepts a variable number of arguments, the extra
				4233	arguments can be specified.</p>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	4234	</li>
Chris Lattner	6536cfe	2002-05-06 22:08:29 +0000	[diff] [blame]	4235	</ol>
Chris Lattner	2bff524	2005-05-06 05:47:36 +0000	[diff] [blame]	4236
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	4237	<h5>Semantics:</h5>
Chris Lattner	2bff524	2005-05-06 05:47:36 +0000	[diff] [blame]	4238
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	4239	<p>The '<tt>call</tt>' instruction is used to cause control flow to
				4240	transfer to a specified function, with its incoming arguments bound to
				4241	the specified values. Upon a '<tt><a href="#i_ret">ret</a></tt>'
				4242	instruction in the called function, control flow continues with the
				4243	instruction after the function call, and the return value of the
Chris Lattner	772fccf	2008-03-21 17:24:17 +0000	[diff] [blame]	4244	function is bound to the result argument. If the callee returns multiple
				4245	values then the return values of the function are only accessible through
				4246	the '<tt><a href="#i_getresult">getresult</a></tt>' instruction.</p>
Chris Lattner	2bff524	2005-05-06 05:47:36 +0000	[diff] [blame]	4247
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	4248	<h5>Example:</h5>
Chris Lattner	2bff524	2005-05-06 05:47:36 +0000	[diff] [blame]	4249
				4250	<pre>
Nick Lewycky	db7e3c9	2007-09-08 13:57:50 +0000	[diff] [blame]	4251	%retval = call i32 @test(i32 %argc)
Chris Lattner	772fccf	2008-03-21 17:24:17 +0000	[diff] [blame]	4252	call i32 (i8 , ...) @printf(i8 * %msg, i32 12, i8 42) <i>; yields i32</i>
				4253	%X = tail call i32 @foo() <i>; yields i32</i>
				4254	%Y = tail call <a href="#callingconv">fastcc</a> i32 @foo() <i>; yields i32</i>
				4255	call void %foo(i8 97 signext)
Devang Patel	c3fc6df	2008-03-10 20:49:15 +0000	[diff] [blame]	4256
				4257	%struct.A = type { i32, i8 }
Chris Lattner	772fccf	2008-03-21 17:24:17 +0000	[diff] [blame]	4258	%r = call %struct.A @foo() <i>; yields { 32, i8 }</i>
				4259	%gr = getresult %struct.A %r, 0 <i>; yields i32</i>
				4260	%gr1 = getresult %struct.A %r, 1 <i>; yields i8</i>
Chris Lattner	2bff524	2005-05-06 05:47:36 +0000	[diff] [blame]	4261	</pre>
				4262
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	4263	</div>
Chris Lattner	e19d7a7	2004-09-27 21:51:25 +0000	[diff] [blame]	4264
Chris Lattner	d9ad5b3	2003-05-08 04:57:36 +0000	[diff] [blame]	4265	<!-- _______________________________________________________________________ -->
Chris Lattner	e19d7a7	2004-09-27 21:51:25 +0000	[diff] [blame]	4266	<div class="doc_subsubsection">
Chris Lattner	fb6977d	2006-01-13 23:26:01 +0000	[diff] [blame]	4267	<a name="i_va_arg">'<tt>va_arg</tt>' Instruction</a>
Chris Lattner	e19d7a7	2004-09-27 21:51:25 +0000	[diff] [blame]	4268	</div>
				4269
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	4270	<div class="doc_text">
Chris Lattner	e19d7a7	2004-09-27 21:51:25 +0000	[diff] [blame]	4271
Chris Lattner	8d1a81d	2003-10-18 05:51:36 +0000	[diff] [blame]	4272	<h5>Syntax:</h5>
Chris Lattner	e19d7a7	2004-09-27 21:51:25 +0000	[diff] [blame]	4273
				4274	<pre>
Andrew Lenharth	8bf607a	2005-06-18 18:28:17 +0000	[diff] [blame]	4275	<resultval> = va_arg <va_list*> <arglist>, <argty>
Chris Lattner	e19d7a7	2004-09-27 21:51:25 +0000	[diff] [blame]	4276	</pre>
				4277
Chris Lattner	8d1a81d	2003-10-18 05:51:36 +0000	[diff] [blame]	4278	<h5>Overview:</h5>
Chris Lattner	e19d7a7	2004-09-27 21:51:25 +0000	[diff] [blame]	4279
Andrew Lenharth	8bf607a	2005-06-18 18:28:17 +0000	[diff] [blame]	4280	<p>The '<tt>va_arg</tt>' instruction is used to access arguments passed through
Chris Lattner	e19d7a7	2004-09-27 21:51:25 +0000	[diff] [blame]	4281	the "variable argument" area of a function call. It is used to implement the
				4282	<tt>va_arg</tt> macro in C.</p>
				4283
Chris Lattner	8d1a81d	2003-10-18 05:51:36 +0000	[diff] [blame]	4284	<h5>Arguments:</h5>
Chris Lattner	e19d7a7	2004-09-27 21:51:25 +0000	[diff] [blame]	4285
Andrew Lenharth	8bf607a	2005-06-18 18:28:17 +0000	[diff] [blame]	4286	<p>This instruction takes a <tt>va_list*</tt> value and the type of
				4287	the argument. It returns a value of the specified argument type and
Jeff Cohen	b627eab	2007-04-29 01:07:00 +0000	[diff] [blame]	4288	increments the <tt>va_list</tt> to point to the next argument. The
Andrew Lenharth	8bf607a	2005-06-18 18:28:17 +0000	[diff] [blame]	4289	actual type of <tt>va_list</tt> is target specific.</p>
Chris Lattner	e19d7a7	2004-09-27 21:51:25 +0000	[diff] [blame]	4290
Chris Lattner	8d1a81d	2003-10-18 05:51:36 +0000	[diff] [blame]	4291	<h5>Semantics:</h5>
Chris Lattner	e19d7a7	2004-09-27 21:51:25 +0000	[diff] [blame]	4292
Andrew Lenharth	8bf607a	2005-06-18 18:28:17 +0000	[diff] [blame]	4293	<p>The '<tt>va_arg</tt>' instruction loads an argument of the specified
				4294	type from the specified <tt>va_list</tt> and causes the
				4295	<tt>va_list</tt> to point to the next argument. For more information,
				4296	see the variable argument handling <a href="#int_varargs">Intrinsic
				4297	Functions</a>.</p>
Chris Lattner	e19d7a7	2004-09-27 21:51:25 +0000	[diff] [blame]	4298
				4299	<p>It is legal for this instruction to be called in a function which does not
				4300	take a variable number of arguments, for example, the <tt>vfprintf</tt>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	4301	function.</p>
Chris Lattner	e19d7a7	2004-09-27 21:51:25 +0000	[diff] [blame]	4302
Andrew Lenharth	8bf607a	2005-06-18 18:28:17 +0000	[diff] [blame]	4303	<p><tt>va_arg</tt> is an LLVM instruction instead of an <a
John Criswell	fc6b895	2005-05-16 16:17:45 +0000	[diff] [blame]	4304	href="#intrinsics">intrinsic function</a> because it takes a type as an
Chris Lattner	e19d7a7	2004-09-27 21:51:25 +0000	[diff] [blame]	4305	argument.</p>
				4306
Chris Lattner	8d1a81d	2003-10-18 05:51:36 +0000	[diff] [blame]	4307	<h5>Example:</h5>
Chris Lattner	e19d7a7	2004-09-27 21:51:25 +0000	[diff] [blame]	4308
				4309	<p>See the <a href="#int_varargs">variable argument processing</a> section.</p>
				4310
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	4311	</div>
Chris Lattner	8ff7590	2004-01-06 05:31:32 +0000	[diff] [blame]	4312
Devang Patel	c3fc6df	2008-03-10 20:49:15 +0000	[diff] [blame]	4313	<!-- _______________________________________________________________________ -->
				4314	<div class="doc_subsubsection">
				4315	<a name="i_getresult">'<tt>getresult</tt>' Instruction</a>
				4316	</div>
				4317
				4318	<div class="doc_text">
				4319
				4320	<h5>Syntax:</h5>
				4321	<pre>
Chris Lattner	45c5e8b	2008-03-21 17:20:51 +0000	[diff] [blame]	4322	<resultval> = getresult <type> <retval>, <index>
Devang Patel	c3fc6df	2008-03-10 20:49:15 +0000	[diff] [blame]	4323	</pre>
Chris Lattner	45c5e8b	2008-03-21 17:20:51 +0000	[diff] [blame]	4324
Devang Patel	c3fc6df	2008-03-10 20:49:15 +0000	[diff] [blame]	4325	<h5>Overview:</h5>
				4326
				4327	<p> The '<tt>getresult</tt>' instruction is used to extract individual values
Chris Lattner	45c5e8b	2008-03-21 17:20:51 +0000	[diff] [blame]	4328	from a '<tt><a href="#i_call">call</a></tt>'
				4329	or '<tt><a href="#i_invoke">invoke</a></tt>' instruction that returns multiple
				4330	results.</p>
Devang Patel	c3fc6df	2008-03-10 20:49:15 +0000	[diff] [blame]	4331
				4332	<h5>Arguments:</h5>
				4333
Chris Lattner	45c5e8b	2008-03-21 17:20:51 +0000	[diff] [blame]	4334	<p>The '<tt>getresult</tt>' instruction takes a call or invoke value as its
Chris Lattner	1c406d7	2008-04-23 04:06:52 +0000	[diff] [blame]	4335	first argument, or an undef value. The value must have <a
				4336	href="#t_struct">structure type</a>. The second argument is a constant
				4337	unsigned index value which must be in range for the number of values returned
				4338	by the call.</p>
Devang Patel	c3fc6df	2008-03-10 20:49:15 +0000	[diff] [blame]	4339
				4340	<h5>Semantics:</h5>
				4341
Chris Lattner	45c5e8b	2008-03-21 17:20:51 +0000	[diff] [blame]	4342	<p>The '<tt>getresult</tt>' instruction extracts the element identified by
				4343	'<tt>index</tt>' from the aggregate value.</p>
Devang Patel	c3fc6df	2008-03-10 20:49:15 +0000	[diff] [blame]	4344
				4345	<h5>Example:</h5>
				4346
				4347	<pre>
				4348	%struct.A = type { i32, i8 }
				4349
				4350	%r = call %struct.A @foo()
Chris Lattner	45c5e8b	2008-03-21 17:20:51 +0000	[diff] [blame]	4351	%gr = getresult %struct.A %r, 0 <i>; yields i32:%gr</i>
				4352	%gr1 = getresult %struct.A %r, 1 <i>; yields i8:%gr1</i>
Devang Patel	c3fc6df	2008-03-10 20:49:15 +0000	[diff] [blame]	4353	add i32 %gr, 42
				4354	add i8 %gr1, 41
				4355	</pre>
				4356
				4357	</div>
				4358
Chris Lattner	d9ad5b3	2003-05-08 04:57:36 +0000	[diff] [blame]	4359	<!-- *********************************************************************** -->
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	4360	<div class="doc_section"> <a name="intrinsics">Intrinsic Functions</a> </div>
				4361	<!-- *********************************************************************** -->
Chris Lattner	8ff7590	2004-01-06 05:31:32 +0000	[diff] [blame]	4362
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	4363	<div class="doc_text">
Chris Lattner	33aec9e	2004-02-12 17:01:32 +0000	[diff] [blame]	4364
				4365	<p>LLVM supports the notion of an "intrinsic function". These functions have
Reid Spencer	409e28f	2007-04-01 08:04:23 +0000	[diff] [blame]	4366	well known names and semantics and are required to follow certain restrictions.
				4367	Overall, these intrinsics represent an extension mechanism for the LLVM
Jeff Cohen	b627eab	2007-04-29 01:07:00 +0000	[diff] [blame]	4368	language that does not require changing all of the transformations in LLVM when
Gabor Greif	04367bf	2007-07-06 22:07:22 +0000	[diff] [blame]	4369	adding to the language (or the bitcode reader/writer, the parser, etc...).</p>
Chris Lattner	33aec9e	2004-02-12 17:01:32 +0000	[diff] [blame]	4370
John Criswell	fc6b895	2005-05-16 16:17:45 +0000	[diff] [blame]	4371	<p>Intrinsic function names must all start with an "<tt>llvm.</tt>" prefix. This
Jeff Cohen	b627eab	2007-04-29 01:07:00 +0000	[diff] [blame]	4372	prefix is reserved in LLVM for intrinsic names; thus, function names may not
				4373	begin with this prefix. Intrinsic functions must always be external functions:
				4374	you cannot define the body of intrinsic functions. Intrinsic functions may
				4375	only be used in call or invoke instructions: it is illegal to take the address
				4376	of an intrinsic function. Additionally, because intrinsic functions are part
				4377	of the LLVM language, it is required if any are added that they be documented
				4378	here.</p>
Chris Lattner	33aec9e	2004-02-12 17:01:32 +0000	[diff] [blame]	4379
Chandler Carruth	6994040	2007-08-04 01:51:18 +0000	[diff] [blame]	4380	<p>Some intrinsic functions can be overloaded, i.e., the intrinsic represents
				4381	a family of functions that perform the same operation but on different data
				4382	types. Because LLVM can represent over 8 million different integer types,
				4383	overloading is used commonly to allow an intrinsic function to operate on any
				4384	integer type. One or more of the argument types or the result type can be
				4385	overloaded to accept any integer type. Argument types may also be defined as
				4386	exactly matching a previous argument's type or the result type. This allows an
				4387	intrinsic function which accepts multiple arguments, but needs all of them to
				4388	be of the same type, to only be overloaded with respect to a single argument or
				4389	the result.</p>
Chris Lattner	33aec9e	2004-02-12 17:01:32 +0000	[diff] [blame]	4390
Chandler Carruth	6994040	2007-08-04 01:51:18 +0000	[diff] [blame]	4391	<p>Overloaded intrinsics will have the names of its overloaded argument types
				4392	encoded into its function name, each preceded by a period. Only those types
				4393	which are overloaded result in a name suffix. Arguments whose type is matched
				4394	against another type do not. For example, the <tt>llvm.ctpop</tt> function can
				4395	take an integer of any width and returns an integer of exactly the same integer
				4396	width. This leads to a family of functions such as
				4397	<tt>i8 @llvm.ctpop.i8(i8 %val)</tt> and <tt>i29 @llvm.ctpop.i29(i29 %val)</tt>.
				4398	Only one type, the return type, is overloaded, and only one type suffix is
				4399	required. Because the argument's type is matched against the return type, it
				4400	does not require its own name suffix.</p>
Reid Spencer	409e28f	2007-04-01 08:04:23 +0000	[diff] [blame]	4401
				4402	<p>To learn how to add an intrinsic function, please see the
				4403	<a href="ExtendingLLVM.html">Extending LLVM Guide</a>.
Chris Lattner	33aec9e	2004-02-12 17:01:32 +0000	[diff] [blame]	4404	</p>
				4405
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	4406	</div>
Chris Lattner	8ff7590	2004-01-06 05:31:32 +0000	[diff] [blame]	4407
Chris Lattner	d9ad5b3	2003-05-08 04:57:36 +0000	[diff] [blame]	4408	<!-- ======================================================================= -->
Chris Lattner	8ff7590	2004-01-06 05:31:32 +0000	[diff] [blame]	4409	<div class="doc_subsection">
				4410	<a name="int_varargs">Variable Argument Handling Intrinsics</a>
				4411	</div>
				4412
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	4413	<div class="doc_text">
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	4414
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	4415	<p>Variable argument support is defined in LLVM with the <a
Chris Lattner	fb6977d	2006-01-13 23:26:01 +0000	[diff] [blame]	4416	href="#i_va_arg"><tt>va_arg</tt></a> instruction and these three
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	4417	intrinsic functions. These functions are related to the similarly
				4418	named macros defined in the <tt><stdarg.h></tt> header file.</p>
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	4419
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	4420	<p>All of these functions operate on arguments that use a
				4421	target-specific value type "<tt>va_list</tt>". The LLVM assembly
				4422	language reference manual does not define what this type is, so all
Jeff Cohen	b627eab	2007-04-29 01:07:00 +0000	[diff] [blame]	4423	transformations should be prepared to handle these functions regardless of
				4424	the type used.</p>
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	4425
Chris Lattner	374ab30	2006-05-15 17:26:46 +0000	[diff] [blame]	4426	<p>This example shows how the <a href="#i_va_arg"><tt>va_arg</tt></a>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	4427	instruction and the variable argument handling intrinsic functions are
				4428	used.</p>
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	4429
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	4430	<div class="doc_code">
Chris Lattner	33aec9e	2004-02-12 17:01:32 +0000	[diff] [blame]	4431	<pre>
Anton Korobeynikov	5d522f3	2007-03-21 23:58:04 +0000	[diff] [blame]	4432	define i32 @test(i32 %X, ...) {
Chris Lattner	33aec9e	2004-02-12 17:01:32 +0000	[diff] [blame]	4433	; Initialize variable argument processing
Jeff Cohen	b627eab	2007-04-29 01:07:00 +0000	[diff] [blame]	4434	%ap = alloca i8*
Chris Lattner	b75137d	2007-01-08 07:55:15 +0000	[diff] [blame]	4435	%ap2 = bitcast i8** %ap to i8*
Anton Korobeynikov	5d522f3	2007-03-21 23:58:04 +0000	[diff] [blame]	4436	call void @llvm.va_start(i8* %ap2)
Chris Lattner	33aec9e	2004-02-12 17:01:32 +0000	[diff] [blame]	4437
				4438	; Read a single integer argument
Jeff Cohen	b627eab	2007-04-29 01:07:00 +0000	[diff] [blame]	4439	%tmp = va_arg i8** %ap, i32
Chris Lattner	33aec9e	2004-02-12 17:01:32 +0000	[diff] [blame]	4440
				4441	; Demonstrate usage of llvm.va_copy and llvm.va_end
Jeff Cohen	b627eab	2007-04-29 01:07:00 +0000	[diff] [blame]	4442	%aq = alloca i8*
Chris Lattner	b75137d	2007-01-08 07:55:15 +0000	[diff] [blame]	4443	%aq2 = bitcast i8** %aq to i8*
Jeff Cohen	b627eab	2007-04-29 01:07:00 +0000	[diff] [blame]	4444	call void @llvm.va_copy(i8* %aq2, i8* %ap2)
Anton Korobeynikov	5d522f3	2007-03-21 23:58:04 +0000	[diff] [blame]	4445	call void @llvm.va_end(i8* %aq2)
Chris Lattner	33aec9e	2004-02-12 17:01:32 +0000	[diff] [blame]	4446
				4447	; Stop processing of arguments.
Anton Korobeynikov	5d522f3	2007-03-21 23:58:04 +0000	[diff] [blame]	4448	call void @llvm.va_end(i8* %ap2)
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	4449	ret i32 %tmp
Chris Lattner	33aec9e	2004-02-12 17:01:32 +0000	[diff] [blame]	4450	}
Anton Korobeynikov	5d522f3	2007-03-21 23:58:04 +0000	[diff] [blame]	4451
				4452	declare void @llvm.va_start(i8*)
				4453	declare void @llvm.va_copy(i8, i8)
				4454	declare void @llvm.va_end(i8*)
Chris Lattner	33aec9e	2004-02-12 17:01:32 +0000	[diff] [blame]	4455	</pre>
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	4456	</div>
Chris Lattner	8ff7590	2004-01-06 05:31:32 +0000	[diff] [blame]	4457
Bill Wendling	2f7a8b0	2007-05-29 09:04:49 +0000	[diff] [blame]	4458	</div>
				4459
Chris Lattner	d9ad5b3	2003-05-08 04:57:36 +0000	[diff] [blame]	4460	<!-- _______________________________________________________________________ -->
Chris Lattner	8ff7590	2004-01-06 05:31:32 +0000	[diff] [blame]	4461	<div class="doc_subsubsection">
Reid Spencer	a3e435f	2007-04-04 02:42:35 +0000	[diff] [blame]	4462	<a name="int_va_start">'<tt>llvm.va_start</tt>' Intrinsic</a>
Chris Lattner	8ff7590	2004-01-06 05:31:32 +0000	[diff] [blame]	4463	</div>
				4464
				4465
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	4466	<div class="doc_text">
Chris Lattner	d9ad5b3	2003-05-08 04:57:36 +0000	[diff] [blame]	4467	<h5>Syntax:</h5>
Chris Lattner	b75137d	2007-01-08 07:55:15 +0000	[diff] [blame]	4468	<pre> declare void %llvm.va_start(i8* <arglist>)<br></pre>
Chris Lattner	d9ad5b3	2003-05-08 04:57:36 +0000	[diff] [blame]	4469	<h5>Overview:</h5>
Andrew Lenharth	8bf607a	2005-06-18 18:28:17 +0000	[diff] [blame]	4470	<P>The '<tt>llvm.va_start</tt>' intrinsic initializes
				4471	<tt>*<arglist></tt> for subsequent use by <tt><a
				4472	href="#i_va_arg">va_arg</a></tt>.</p>
				4473
				4474	<h5>Arguments:</h5>
				4475
				4476	<P>The argument is a pointer to a <tt>va_list</tt> element to initialize.</p>
				4477
Chris Lattner	d9ad5b3	2003-05-08 04:57:36 +0000	[diff] [blame]	4478	<h5>Semantics:</h5>
Andrew Lenharth	8bf607a	2005-06-18 18:28:17 +0000	[diff] [blame]	4479
				4480	<P>The '<tt>llvm.va_start</tt>' intrinsic works just like the <tt>va_start</tt>
				4481	macro available in C. In a target-dependent way, it initializes the
Jeff Cohen	b627eab	2007-04-29 01:07:00 +0000	[diff] [blame]	4482	<tt>va_list</tt> element to which the argument points, so that the next call to
Andrew Lenharth	8bf607a	2005-06-18 18:28:17 +0000	[diff] [blame]	4483	<tt>va_arg</tt> will produce the first variable argument passed to the function.
				4484	Unlike the C <tt>va_start</tt> macro, this intrinsic does not need to know the
Jeff Cohen	b627eab	2007-04-29 01:07:00 +0000	[diff] [blame]	4485	last argument of the function as the compiler can figure that out.</p>
Andrew Lenharth	8bf607a	2005-06-18 18:28:17 +0000	[diff] [blame]	4486
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	4487	</div>
Chris Lattner	8ff7590	2004-01-06 05:31:32 +0000	[diff] [blame]	4488
Chris Lattner	d9ad5b3	2003-05-08 04:57:36 +0000	[diff] [blame]	4489	<!-- _______________________________________________________________________ -->
Chris Lattner	8ff7590	2004-01-06 05:31:32 +0000	[diff] [blame]	4490	<div class="doc_subsubsection">
Reid Spencer	a3e435f	2007-04-04 02:42:35 +0000	[diff] [blame]	4491	<a name="int_va_end">'<tt>llvm.va_end</tt>' Intrinsic</a>
Chris Lattner	8ff7590	2004-01-06 05:31:32 +0000	[diff] [blame]	4492	</div>
				4493
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	4494	<div class="doc_text">
Chris Lattner	d9ad5b3	2003-05-08 04:57:36 +0000	[diff] [blame]	4495	<h5>Syntax:</h5>
Anton Korobeynikov	ec43a06	2007-03-22 00:02:17 +0000	[diff] [blame]	4496	<pre> declare void @llvm.va_end(i8* <arglist>)<br></pre>
Chris Lattner	d9ad5b3	2003-05-08 04:57:36 +0000	[diff] [blame]	4497	<h5>Overview:</h5>
Chris Lattner	b75137d	2007-01-08 07:55:15 +0000	[diff] [blame]	4498
Jeff Cohen	b627eab	2007-04-29 01:07:00 +0000	[diff] [blame]	4499	<p>The '<tt>llvm.va_end</tt>' intrinsic destroys <tt>*<arglist></tt>,
Reid Spencer	a3e435f	2007-04-04 02:42:35 +0000	[diff] [blame]	4500	which has been initialized previously with <tt><a href="#int_va_start">llvm.va_start</a></tt>
Chris Lattner	261efe9	2003-11-25 01:02:51 +0000	[diff] [blame]	4501	or <tt><a href="#i_va_copy">llvm.va_copy</a></tt>.</p>
Chris Lattner	b75137d	2007-01-08 07:55:15 +0000	[diff] [blame]	4502
Chris Lattner	d9ad5b3	2003-05-08 04:57:36 +0000	[diff] [blame]	4503	<h5>Arguments:</h5>
Chris Lattner	b75137d	2007-01-08 07:55:15 +0000	[diff] [blame]	4504
Jeff Cohen	b627eab	2007-04-29 01:07:00 +0000	[diff] [blame]	4505	<p>The argument is a pointer to a <tt>va_list</tt> to destroy.</p>
Chris Lattner	b75137d	2007-01-08 07:55:15 +0000	[diff] [blame]	4506
Chris Lattner	d9ad5b3	2003-05-08 04:57:36 +0000	[diff] [blame]	4507	<h5>Semantics:</h5>
Chris Lattner	b75137d	2007-01-08 07:55:15 +0000	[diff] [blame]	4508
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	4509	<p>The '<tt>llvm.va_end</tt>' intrinsic works just like the <tt>va_end</tt>
Jeff Cohen	b627eab	2007-04-29 01:07:00 +0000	[diff] [blame]	4510	macro available in C. In a target-dependent way, it destroys the
				4511	<tt>va_list</tt> element to which the argument points. Calls to <a
				4512	href="#int_va_start"><tt>llvm.va_start</tt></a> and <a href="#int_va_copy">
				4513	<tt>llvm.va_copy</tt></a> must be matched exactly with calls to
				4514	<tt>llvm.va_end</tt>.</p>
Chris Lattner	b75137d	2007-01-08 07:55:15 +0000	[diff] [blame]	4515
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	4516	</div>
Chris Lattner	8ff7590	2004-01-06 05:31:32 +0000	[diff] [blame]	4517
Chris Lattner	d9ad5b3	2003-05-08 04:57:36 +0000	[diff] [blame]	4518	<!-- _______________________________________________________________________ -->
Chris Lattner	8ff7590	2004-01-06 05:31:32 +0000	[diff] [blame]	4519	<div class="doc_subsubsection">
Reid Spencer	a3e435f	2007-04-04 02:42:35 +0000	[diff] [blame]	4520	<a name="int_va_copy">'<tt>llvm.va_copy</tt>' Intrinsic</a>
Chris Lattner	8ff7590	2004-01-06 05:31:32 +0000	[diff] [blame]	4521	</div>
				4522
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	4523	<div class="doc_text">
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	4524
Chris Lattner	d9ad5b3	2003-05-08 04:57:36 +0000	[diff] [blame]	4525	<h5>Syntax:</h5>
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	4526
				4527	<pre>
Anton Korobeynikov	ec43a06	2007-03-22 00:02:17 +0000	[diff] [blame]	4528	declare void @llvm.va_copy(i8* <destarglist>, i8* <srcarglist>)
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	4529	</pre>
				4530
Chris Lattner	d9ad5b3	2003-05-08 04:57:36 +0000	[diff] [blame]	4531	<h5>Overview:</h5>
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	4532
Jeff Cohen	b627eab	2007-04-29 01:07:00 +0000	[diff] [blame]	4533	<p>The '<tt>llvm.va_copy</tt>' intrinsic copies the current argument position
				4534	from the source argument list to the destination argument list.</p>
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	4535
Chris Lattner	d9ad5b3	2003-05-08 04:57:36 +0000	[diff] [blame]	4536	<h5>Arguments:</h5>
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	4537
Andrew Lenharth	8bf607a	2005-06-18 18:28:17 +0000	[diff] [blame]	4538	<p>The first argument is a pointer to a <tt>va_list</tt> element to initialize.
Andrew Lenharth	d0a4c62	2005-06-22 20:38:11 +0000	[diff] [blame]	4539	The second argument is a pointer to a <tt>va_list</tt> element to copy from.</p>
Andrew Lenharth	8bf607a	2005-06-18 18:28:17 +0000	[diff] [blame]	4540
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	4541
Chris Lattner	d9ad5b3	2003-05-08 04:57:36 +0000	[diff] [blame]	4542	<h5>Semantics:</h5>
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	4543
Jeff Cohen	b627eab	2007-04-29 01:07:00 +0000	[diff] [blame]	4544	<p>The '<tt>llvm.va_copy</tt>' intrinsic works just like the <tt>va_copy</tt>
				4545	macro available in C. In a target-dependent way, it copies the source
				4546	<tt>va_list</tt> element into the destination <tt>va_list</tt> element. This
				4547	intrinsic is necessary because the <tt><a href="#int_va_start">
				4548	llvm.va_start</a></tt> intrinsic may be arbitrarily complex and require, for
				4549	example, memory allocation.</p>
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	4550
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	4551	</div>
Chris Lattner	8ff7590	2004-01-06 05:31:32 +0000	[diff] [blame]	4552
Chris Lattner	33aec9e	2004-02-12 17:01:32 +0000	[diff] [blame]	4553	<!-- ======================================================================= -->
				4554	<div class="doc_subsection">
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	4555	<a name="int_gc">Accurate Garbage Collection Intrinsics</a>
				4556	</div>
				4557
				4558	<div class="doc_text">
				4559
				4560	<p>
				4561	LLVM support for <a href="GarbageCollection.html">Accurate Garbage
Chris Lattner	d3eda89	2008-08-05 18:29:16 +0000	[diff] [blame]	4562	Collection</a> (GC) requires the implementation and generation of these
				4563	intrinsics.
Reid Spencer	a3e435f	2007-04-04 02:42:35 +0000	[diff] [blame]	4564	These intrinsics allow identification of <a href="#int_gcroot">GC roots on the
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	4565	stack</a>, as well as garbage collector implementations that require <a
Reid Spencer	a3e435f	2007-04-04 02:42:35 +0000	[diff] [blame]	4566	href="#int_gcread">read</a> and <a href="#int_gcwrite">write</a> barriers.
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	4567	Front-ends for type-safe garbage collected languages should generate these
				4568	intrinsics to make use of the LLVM garbage collectors. For more details, see <a
				4569	href="GarbageCollection.html">Accurate Garbage Collection with LLVM</a>.
				4570	</p>
Christopher Lamb	303dae9	2007-12-17 01:00:21 +0000	[diff] [blame]	4571
				4572	<p>The garbage collection intrinsics only operate on objects in the generic
				4573	address space (address space zero).</p>
				4574
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	4575	</div>
				4576
				4577	<!-- _______________________________________________________________________ -->
				4578	<div class="doc_subsubsection">
Reid Spencer	a3e435f	2007-04-04 02:42:35 +0000	[diff] [blame]	4579	<a name="int_gcroot">'<tt>llvm.gcroot</tt>' Intrinsic</a>
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	4580	</div>
				4581
				4582	<div class="doc_text">
				4583
				4584	<h5>Syntax:</h5>
				4585
				4586	<pre>
Chris Lattner	1df4f75	2007-09-21 17:30:40 +0000	[diff] [blame]	4587	declare void @llvm.gcroot(i8** %ptrloc, i8* %metadata)
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	4588	</pre>
				4589
				4590	<h5>Overview:</h5>
				4591
John Criswell	9e2485c	2004-12-10 15:51:16 +0000	[diff] [blame]	4592	<p>The '<tt>llvm.gcroot</tt>' intrinsic declares the existence of a GC root to
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	4593	the code generator, and allows some metadata to be associated with it.</p>
				4594
				4595	<h5>Arguments:</h5>
				4596
				4597	<p>The first argument specifies the address of a stack object that contains the
				4598	root pointer. The second pointer (which must be either a constant or a global
				4599	value address) contains the meta-data to be associated with the root.</p>
				4600
				4601	<h5>Semantics:</h5>
				4602
Chris Lattner	05d6709	2008-04-24 05:59:56 +0000	[diff] [blame]	4603	<p>At runtime, a call to this intrinsic stores a null pointer into the "ptrloc"
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	4604	location. At compile-time, the code generator generates information to allow
Gordon Henriksen	e1433f2	2007-12-25 02:31:26 +0000	[diff] [blame]	4605	the runtime to find the pointer at GC safe points. The '<tt>llvm.gcroot</tt>'
				4606	intrinsic may only be used in a function which <a href="#gc">specifies a GC
				4607	algorithm</a>.</p>
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	4608
				4609	</div>
				4610
				4611
				4612	<!-- _______________________________________________________________________ -->
				4613	<div class="doc_subsubsection">
Reid Spencer	a3e435f	2007-04-04 02:42:35 +0000	[diff] [blame]	4614	<a name="int_gcread">'<tt>llvm.gcread</tt>' Intrinsic</a>
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	4615	</div>
				4616
				4617	<div class="doc_text">
				4618
				4619	<h5>Syntax:</h5>
				4620
				4621	<pre>
Chris Lattner	1df4f75	2007-09-21 17:30:40 +0000	[diff] [blame]	4622	declare i8* @llvm.gcread(i8* %ObjPtr, i8** %Ptr)
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	4623	</pre>
				4624
				4625	<h5>Overview:</h5>
				4626
				4627	<p>The '<tt>llvm.gcread</tt>' intrinsic identifies reads of references from heap
				4628	locations, allowing garbage collector implementations that require read
				4629	barriers.</p>
				4630
				4631	<h5>Arguments:</h5>
				4632
Chris Lattner	80626e9	2006-03-14 20:02:51 +0000	[diff] [blame]	4633	<p>The second argument is the address to read from, which should be an address
				4634	allocated from the garbage collector. The first object is a pointer to the
				4635	start of the referenced object, if needed by the language runtime (otherwise
				4636	null).</p>
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	4637
				4638	<h5>Semantics:</h5>
				4639
				4640	<p>The '<tt>llvm.gcread</tt>' intrinsic has the same semantics as a load
				4641	instruction, but may be replaced with substantially more complex code by the
Gordon Henriksen	e1433f2	2007-12-25 02:31:26 +0000	[diff] [blame]	4642	garbage collector runtime, as needed. The '<tt>llvm.gcread</tt>' intrinsic
				4643	may only be used in a function which <a href="#gc">specifies a GC
				4644	algorithm</a>.</p>
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	4645
				4646	</div>
				4647
				4648
				4649	<!-- _______________________________________________________________________ -->
				4650	<div class="doc_subsubsection">
Reid Spencer	a3e435f	2007-04-04 02:42:35 +0000	[diff] [blame]	4651	<a name="int_gcwrite">'<tt>llvm.gcwrite</tt>' Intrinsic</a>
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	4652	</div>
				4653
				4654	<div class="doc_text">
				4655
				4656	<h5>Syntax:</h5>
				4657
				4658	<pre>
Chris Lattner	1df4f75	2007-09-21 17:30:40 +0000	[diff] [blame]	4659	declare void @llvm.gcwrite(i8* %P1, i8* %Obj, i8** %P2)
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	4660	</pre>
				4661
				4662	<h5>Overview:</h5>
				4663
				4664	<p>The '<tt>llvm.gcwrite</tt>' intrinsic identifies writes of references to heap
				4665	locations, allowing garbage collector implementations that require write
				4666	barriers (such as generational or reference counting collectors).</p>
				4667
				4668	<h5>Arguments:</h5>
				4669
Chris Lattner	80626e9	2006-03-14 20:02:51 +0000	[diff] [blame]	4670	<p>The first argument is the reference to store, the second is the start of the
				4671	object to store it to, and the third is the address of the field of Obj to
				4672	store to. If the runtime does not require a pointer to the object, Obj may be
				4673	null.</p>
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	4674
				4675	<h5>Semantics:</h5>
				4676
				4677	<p>The '<tt>llvm.gcwrite</tt>' intrinsic has the same semantics as a store
				4678	instruction, but may be replaced with substantially more complex code by the
Gordon Henriksen	e1433f2	2007-12-25 02:31:26 +0000	[diff] [blame]	4679	garbage collector runtime, as needed. The '<tt>llvm.gcwrite</tt>' intrinsic
				4680	may only be used in a function which <a href="#gc">specifies a GC
				4681	algorithm</a>.</p>
Chris Lattner	d792391	2004-05-23 21:06:01 +0000	[diff] [blame]	4682
				4683	</div>
				4684
				4685
				4686
				4687	<!-- ======================================================================= -->
				4688	<div class="doc_subsection">
Chris Lattner	1061064	2004-02-14 04:08:35 +0000	[diff] [blame]	4689	<a name="int_codegen">Code Generator Intrinsics</a>
				4690	</div>
				4691
				4692	<div class="doc_text">
				4693	<p>
				4694	These intrinsics are provided by LLVM to expose special features that may only
				4695	be implemented with code generator support.
				4696	</p>
				4697
				4698	</div>
				4699
				4700	<!-- _______________________________________________________________________ -->
				4701	<div class="doc_subsubsection">
Reid Spencer	a3e435f	2007-04-04 02:42:35 +0000	[diff] [blame]	4702	<a name="int_returnaddress">'<tt>llvm.returnaddress</tt>' Intrinsic</a>
Chris Lattner	1061064	2004-02-14 04:08:35 +0000	[diff] [blame]	4703	</div>
				4704
				4705	<div class="doc_text">
				4706
				4707	<h5>Syntax:</h5>
				4708	<pre>
Anton Korobeynikov	ec43a06	2007-03-22 00:02:17 +0000	[diff] [blame]	4709	declare i8 *@llvm.returnaddress(i32 <level>)
Chris Lattner	1061064	2004-02-14 04:08:35 +0000	[diff] [blame]	4710	</pre>
				4711
				4712	<h5>Overview:</h5>
				4713
				4714	<p>
Chris Lattner	32b5d71	2006-10-15 20:05:59 +0000	[diff] [blame]	4715	The '<tt>llvm.returnaddress</tt>' intrinsic attempts to compute a
				4716	target-specific value indicating the return address of the current function
				4717	or one of its callers.
Chris Lattner	1061064	2004-02-14 04:08:35 +0000	[diff] [blame]	4718	</p>
				4719
				4720	<h5>Arguments:</h5>
				4721
				4722	<p>
				4723	The argument to this intrinsic indicates which function to return the address
				4724	for. Zero indicates the calling function, one indicates its caller, etc. The
				4725	argument is <b>required</b> to be a constant integer value.
				4726	</p>
				4727
				4728	<h5>Semantics:</h5>
				4729
				4730	<p>
				4731	The '<tt>llvm.returnaddress</tt>' intrinsic either returns a pointer indicating
				4732	the return address of the specified call frame, or zero if it cannot be
				4733	identified. The value returned by this intrinsic is likely to be incorrect or 0
				4734	for arguments other than zero, so it should only be used for debugging purposes.
				4735	</p>
				4736
				4737	<p>
				4738	Note that calling this intrinsic does not prevent function inlining or other
Chris Lattner	b40bb38	2005-03-07 20:30:51 +0000	[diff] [blame]	4739	aggressive transformations, so the value returned may not be that of the obvious
Chris Lattner	1061064	2004-02-14 04:08:35 +0000	[diff] [blame]	4740	source-language caller.
				4741	</p>
				4742	</div>
				4743
				4744
				4745	<!-- _______________________________________________________________________ -->
				4746	<div class="doc_subsubsection">
Reid Spencer	a3e435f	2007-04-04 02:42:35 +0000	[diff] [blame]	4747	<a name="int_frameaddress">'<tt>llvm.frameaddress</tt>' Intrinsic</a>
Chris Lattner	1061064	2004-02-14 04:08:35 +0000	[diff] [blame]	4748	</div>
				4749
				4750	<div class="doc_text">
				4751
				4752	<h5>Syntax:</h5>
				4753	<pre>
Chris Lattner	1df4f75	2007-09-21 17:30:40 +0000	[diff] [blame]	4754	declare i8 *@llvm.frameaddress(i32 <level>)
Chris Lattner	1061064	2004-02-14 04:08:35 +0000	[diff] [blame]	4755	</pre>
				4756
				4757	<h5>Overview:</h5>
				4758
				4759	<p>
Chris Lattner	32b5d71	2006-10-15 20:05:59 +0000	[diff] [blame]	4760	The '<tt>llvm.frameaddress</tt>' intrinsic attempts to return the
				4761	target-specific frame pointer value for the specified stack frame.
Chris Lattner	1061064	2004-02-14 04:08:35 +0000	[diff] [blame]	4762	</p>
				4763
				4764	<h5>Arguments:</h5>
				4765
				4766	<p>
				4767	The argument to this intrinsic indicates which function to return the frame
				4768	pointer for. Zero indicates the calling function, one indicates its caller,
				4769	etc. The argument is <b>required</b> to be a constant integer value.
				4770	</p>
				4771
				4772	<h5>Semantics:</h5>
				4773
				4774	<p>
				4775	The '<tt>llvm.frameaddress</tt>' intrinsic either returns a pointer indicating
				4776	the frame address of the specified call frame, or zero if it cannot be
				4777	identified. The value returned by this intrinsic is likely to be incorrect or 0
				4778	for arguments other than zero, so it should only be used for debugging purposes.
				4779	</p>
				4780
				4781	<p>
				4782	Note that calling this intrinsic does not prevent function inlining or other
Chris Lattner	b40bb38	2005-03-07 20:30:51 +0000	[diff] [blame]	4783	aggressive transformations, so the value returned may not be that of the obvious
Chris Lattner	1061064	2004-02-14 04:08:35 +0000	[diff] [blame]	4784	source-language caller.
				4785	</p>
				4786	</div>
				4787
Chris Lattner	9a9d7ac	2005-02-28 19:24:19 +0000	[diff] [blame]	4788	<!-- _______________________________________________________________________ -->
				4789	<div class="doc_subsubsection">
Reid Spencer	a3e435f	2007-04-04 02:42:35 +0000	[diff] [blame]	4790	<a name="int_stacksave">'<tt>llvm.stacksave</tt>' Intrinsic</a>
Chris Lattner	57e1f39	2006-01-13 02:03:13 +0000	[diff] [blame]	4791	</div>
				4792
				4793	<div class="doc_text">
				4794
				4795	<h5>Syntax:</h5>
				4796	<pre>
Chris Lattner	1df4f75	2007-09-21 17:30:40 +0000	[diff] [blame]	4797	declare i8 *@llvm.stacksave()
Chris Lattner	57e1f39	2006-01-13 02:03:13 +0000	[diff] [blame]	4798	</pre>
				4799
				4800	<h5>Overview:</h5>
				4801
				4802	<p>
				4803	The '<tt>llvm.stacksave</tt>' intrinsic is used to remember the current state of
Reid Spencer	a3e435f	2007-04-04 02:42:35 +0000	[diff] [blame]	4804	the function stack, for use with <a href="#int_stackrestore">
Chris Lattner	57e1f39	2006-01-13 02:03:13 +0000	[diff] [blame]	4805	<tt>llvm.stackrestore</tt></a>. This is useful for implementing language
				4806	features like scoped automatic variable sized arrays in C99.
				4807	</p>
				4808
				4809	<h5>Semantics:</h5>
				4810
				4811	<p>
				4812	This intrinsic returns a opaque pointer value that can be passed to <a
Reid Spencer	a3e435f	2007-04-04 02:42:35 +0000	[diff] [blame]	4813	href="#int_stackrestore"><tt>llvm.stackrestore</tt></a>. When an
Chris Lattner	57e1f39	2006-01-13 02:03:13 +0000	[diff] [blame]	4814	<tt>llvm.stackrestore</tt> intrinsic is executed with a value saved from
				4815	<tt>llvm.stacksave</tt>, it effectively restores the state of the stack to the
				4816	state it was in when the <tt>llvm.stacksave</tt> intrinsic executed. In
				4817	practice, this pops any <a href="#i_alloca">alloca</a> blocks from the stack
				4818	that were allocated after the <tt>llvm.stacksave</tt> was executed.
				4819	</p>
				4820
				4821	</div>
				4822
				4823	<!-- _______________________________________________________________________ -->
				4824	<div class="doc_subsubsection">
Reid Spencer	a3e435f	2007-04-04 02:42:35 +0000	[diff] [blame]	4825	<a name="int_stackrestore">'<tt>llvm.stackrestore</tt>' Intrinsic</a>
Chris Lattner	57e1f39	2006-01-13 02:03:13 +0000	[diff] [blame]	4826	</div>
				4827
				4828	<div class="doc_text">
				4829
				4830	<h5>Syntax:</h5>
				4831	<pre>
Anton Korobeynikov	ec43a06	2007-03-22 00:02:17 +0000	[diff] [blame]	4832	declare void @llvm.stackrestore(i8 * %ptr)
Chris Lattner	57e1f39	2006-01-13 02:03:13 +0000	[diff] [blame]	4833	</pre>
				4834
				4835	<h5>Overview:</h5>
				4836
				4837	<p>
				4838	The '<tt>llvm.stackrestore</tt>' intrinsic is used to restore the state of
				4839	the function stack to the state it was in when the corresponding <a
Reid Spencer	a3e435f	2007-04-04 02:42:35 +0000	[diff] [blame]	4840	href="#int_stacksave"><tt>llvm.stacksave</tt></a> intrinsic executed. This is
Chris Lattner	57e1f39	2006-01-13 02:03:13 +0000	[diff] [blame]	4841	useful for implementing language features like scoped automatic variable sized
				4842	arrays in C99.
				4843	</p>
				4844
				4845	<h5>Semantics:</h5>
				4846
				4847	<p>
Reid Spencer	a3e435f	2007-04-04 02:42:35 +0000	[diff] [blame]	4848	See the description for <a href="#int_stacksave"><tt>llvm.stacksave</tt></a>.
Chris Lattner	57e1f39	2006-01-13 02:03:13 +0000	[diff] [blame]	4849	</p>
				4850
				4851	</div>
				4852
				4853
				4854	<!-- _______________________________________________________________________ -->
				4855	<div class="doc_subsubsection">
Reid Spencer	a3e435f	2007-04-04 02:42:35 +0000	[diff] [blame]	4856	<a name="int_prefetch">'<tt>llvm.prefetch</tt>' Intrinsic</a>
Chris Lattner	9a9d7ac	2005-02-28 19:24:19 +0000	[diff] [blame]	4857	</div>
				4858
				4859	<div class="doc_text">
				4860
				4861	<h5>Syntax:</h5>
				4862	<pre>
Chris Lattner	1df4f75	2007-09-21 17:30:40 +0000	[diff] [blame]	4863	declare void @llvm.prefetch(i8* <address>, i32 <rw>, i32 <locality>)
Chris Lattner	9a9d7ac	2005-02-28 19:24:19 +0000	[diff] [blame]	4864	</pre>
				4865
				4866	<h5>Overview:</h5>
				4867
				4868
				4869	<p>
				4870	The '<tt>llvm.prefetch</tt>' intrinsic is a hint to the code generator to insert
John Criswell	fc6b895	2005-05-16 16:17:45 +0000	[diff] [blame]	4871	a prefetch instruction if supported; otherwise, it is a noop. Prefetches have
				4872	no
				4873	effect on the behavior of the program but can change its performance
Chris Lattner	2a61536	2005-02-28 19:47:14 +0000	[diff] [blame]	4874	characteristics.
Chris Lattner	9a9d7ac	2005-02-28 19:24:19 +0000	[diff] [blame]	4875	</p>
				4876
				4877	<h5>Arguments:</h5>
				4878
				4879	<p>
				4880	<tt>address</tt> is the address to be prefetched, <tt>rw</tt> is the specifier
				4881	determining if the fetch should be for a read (0) or write (1), and
				4882	<tt>locality</tt> is a temporal locality specifier ranging from (0) - no
Chris Lattner	aeffb4a	2005-03-07 20:31:38 +0000	[diff] [blame]	4883	locality, to (3) - extremely local keep in cache. The <tt>rw</tt> and
Chris Lattner	9a9d7ac	2005-02-28 19:24:19 +0000	[diff] [blame]	4884	<tt>locality</tt> arguments must be constant integers.
				4885	</p>
				4886
				4887	<h5>Semantics:</h5>
				4888
				4889	<p>
				4890	This intrinsic does not modify the behavior of the program. In particular,
				4891	prefetches cannot trap and do not produce a value. On targets that support this
				4892	intrinsic, the prefetch can provide hints to the processor cache for better
				4893	performance.
				4894	</p>
				4895
				4896	</div>
				4897
Andrew Lenharth	7f4ec3b	2005-03-28 20:05:49 +0000	[diff] [blame]	4898	<!-- _______________________________________________________________________ -->
				4899	<div class="doc_subsubsection">
Reid Spencer	a3e435f	2007-04-04 02:42:35 +0000	[diff] [blame]	4900	<a name="int_pcmarker">'<tt>llvm.pcmarker</tt>' Intrinsic</a>
Andrew Lenharth	7f4ec3b	2005-03-28 20:05:49 +0000	[diff] [blame]	4901	</div>
				4902
				4903	<div class="doc_text">
				4904
				4905	<h5>Syntax:</h5>
				4906	<pre>
Chris Lattner	1df4f75	2007-09-21 17:30:40 +0000	[diff] [blame]	4907	declare void @llvm.pcmarker(i32 <id>)
Andrew Lenharth	7f4ec3b	2005-03-28 20:05:49 +0000	[diff] [blame]	4908	</pre>
				4909
				4910	<h5>Overview:</h5>
				4911
				4912
				4913	<p>
John Criswell	fc6b895	2005-05-16 16:17:45 +0000	[diff] [blame]	4914	The '<tt>llvm.pcmarker</tt>' intrinsic is a method to export a Program Counter
Chris Lattner	d3eda89	2008-08-05 18:29:16 +0000	[diff] [blame]	4915	(PC) in a region of
				4916	code to simulators and other tools. The method is target specific, but it is
				4917	expected that the marker will use exported symbols to transmit the PC of the
				4918	marker.
				4919	The marker makes no guarantees that it will remain with any specific instruction
				4920	after optimizations. It is possible that the presence of a marker will inhibit
Chris Lattner	b3e7afd	2006-03-24 07:16:10 +0000	[diff] [blame]	4921	optimizations. The intended use is to be inserted after optimizations to allow
John Criswell	fc6b895	2005-05-16 16:17:45 +0000	[diff] [blame]	4922	correlations of simulation runs.
Andrew Lenharth	7f4ec3b	2005-03-28 20:05:49 +0000	[diff] [blame]	4923	</p>
				4924
				4925	<h5>Arguments:</h5>
				4926
				4927	<p>
				4928	<tt>id</tt> is a numerical id identifying the marker.
				4929	</p>
				4930
				4931	<h5>Semantics:</h5>
				4932
				4933	<p>
				4934	This intrinsic does not modify the behavior of the program. Backends that do not
				4935	support this intrinisic may ignore it.
				4936	</p>
				4937
				4938	</div>
				4939
Andrew Lenharth	51b8d54	2005-11-11 16:47:30 +0000	[diff] [blame]	4940	<!-- _______________________________________________________________________ -->
				4941	<div class="doc_subsubsection">
Reid Spencer	a3e435f	2007-04-04 02:42:35 +0000	[diff] [blame]	4942	<a name="int_readcyclecounter">'<tt>llvm.readcyclecounter</tt>' Intrinsic</a>
Andrew Lenharth	51b8d54	2005-11-11 16:47:30 +0000	[diff] [blame]	4943	</div>
				4944
				4945	<div class="doc_text">
				4946
				4947	<h5>Syntax:</h5>
				4948	<pre>
Anton Korobeynikov	ec43a06	2007-03-22 00:02:17 +0000	[diff] [blame]	4949	declare i64 @llvm.readcyclecounter( )
Andrew Lenharth	51b8d54	2005-11-11 16:47:30 +0000	[diff] [blame]	4950	</pre>
				4951
				4952	<h5>Overview:</h5>
				4953
				4954
				4955	<p>
				4956	The '<tt>llvm.readcyclecounter</tt>' intrinsic provides access to the cycle
				4957	counter register (or similar low latency, high accuracy clocks) on those targets
				4958	that support it. On X86, it should map to RDTSC. On Alpha, it should map to RPCC.
				4959	As the backing counters overflow quickly (on the order of 9 seconds on alpha), this
				4960	should only be used for small timings.
				4961	</p>
				4962
				4963	<h5>Semantics:</h5>
				4964
				4965	<p>
				4966	When directly supported, reading the cycle counter should not modify any memory.
				4967	Implementations are allowed to either return a application specific value or a
				4968	system wide value. On backends without support, this is lowered to a constant 0.
				4969	</p>
				4970
				4971	</div>
				4972
Chris Lattner	1061064	2004-02-14 04:08:35 +0000	[diff] [blame]	4973	<!-- ======================================================================= -->
				4974	<div class="doc_subsection">
Chris Lattner	33aec9e	2004-02-12 17:01:32 +0000	[diff] [blame]	4975	<a name="int_libc">Standard C Library Intrinsics</a>
				4976	</div>
				4977
				4978	<div class="doc_text">
				4979	<p>
Chris Lattner	1061064	2004-02-14 04:08:35 +0000	[diff] [blame]	4980	LLVM provides intrinsics for a few important standard C library functions.
				4981	These intrinsics allow source-language front-ends to pass information about the
				4982	alignment of the pointer arguments to the code generator, providing opportunity
				4983	for more efficient code generation.
Chris Lattner	33aec9e	2004-02-12 17:01:32 +0000	[diff] [blame]	4984	</p>
				4985
				4986	</div>
				4987
				4988	<!-- _______________________________________________________________________ -->
				4989	<div class="doc_subsubsection">
Reid Spencer	a3e435f	2007-04-04 02:42:35 +0000	[diff] [blame]	4990	<a name="int_memcpy">'<tt>llvm.memcpy</tt>' Intrinsic</a>
Chris Lattner	33aec9e	2004-02-12 17:01:32 +0000	[diff] [blame]	4991	</div>
				4992
				4993	<div class="doc_text">
				4994
				4995	<h5>Syntax:</h5>
				4996	<pre>
Anton Korobeynikov	ec43a06	2007-03-22 00:02:17 +0000	[diff] [blame]	4997	declare void @llvm.memcpy.i32(i8 * <dest>, i8 * <src>,
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	4998	i32 <len>, i32 <align>)
Anton Korobeynikov	ec43a06	2007-03-22 00:02:17 +0000	[diff] [blame]	4999	declare void @llvm.memcpy.i64(i8 * <dest>, i8 * <src>,
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	5000	i64 <len>, i32 <align>)
Chris Lattner	33aec9e	2004-02-12 17:01:32 +0000	[diff] [blame]	5001	</pre>
				5002
				5003	<h5>Overview:</h5>
				5004
				5005	<p>
Chris Lattner	5b310c3	2006-03-03 00:07:20 +0000	[diff] [blame]	5006	The '<tt>llvm.memcpy.*</tt>' intrinsics copy a block of memory from the source
Chris Lattner	33aec9e	2004-02-12 17:01:32 +0000	[diff] [blame]	5007	location to the destination location.
				5008	</p>
				5009
				5010	<p>
Chris Lattner	5b310c3	2006-03-03 00:07:20 +0000	[diff] [blame]	5011	Note that, unlike the standard libc function, the <tt>llvm.memcpy.*</tt>
				5012	intrinsics do not return a value, and takes an extra alignment argument.
Chris Lattner	33aec9e	2004-02-12 17:01:32 +0000	[diff] [blame]	5013	</p>
				5014
				5015	<h5>Arguments:</h5>
				5016
				5017	<p>
				5018	The first argument is a pointer to the destination, the second is a pointer to
Chris Lattner	5b310c3	2006-03-03 00:07:20 +0000	[diff] [blame]	5019	the source. The third argument is an integer argument
Chris Lattner	33aec9e	2004-02-12 17:01:32 +0000	[diff] [blame]	5020	specifying the number of bytes to copy, and the fourth argument is the alignment
				5021	of the source and destination locations.
				5022	</p>
				5023
Chris Lattner	3301ced	2004-02-12 21:18:15 +0000	[diff] [blame]	5024	<p>
				5025	If the call to this intrinisic has an alignment value that is not 0 or 1, then
Chris Lattner	f0afc2c	2006-03-04 00:02:10 +0000	[diff] [blame]	5026	the caller guarantees that both the source and destination pointers are aligned
				5027	to that boundary.
Chris Lattner	3301ced	2004-02-12 21:18:15 +0000	[diff] [blame]	5028	</p>
				5029
Chris Lattner	33aec9e	2004-02-12 17:01:32 +0000	[diff] [blame]	5030	<h5>Semantics:</h5>
				5031
				5032	<p>
Chris Lattner	5b310c3	2006-03-03 00:07:20 +0000	[diff] [blame]	5033	The '<tt>llvm.memcpy.*</tt>' intrinsics copy a block of memory from the source
Chris Lattner	33aec9e	2004-02-12 17:01:32 +0000	[diff] [blame]	5034	location to the destination location, which are not allowed to overlap. It
				5035	copies "len" bytes of memory over. If the argument is known to be aligned to
				5036	some boundary, this can be specified as the fourth argument, otherwise it should
				5037	be set to 0 or 1.
				5038	</p>
				5039	</div>
				5040
				5041
Chris Lattner	0eb51b4	2004-02-12 18:10:10 +0000	[diff] [blame]	5042	<!-- _______________________________________________________________________ -->
				5043	<div class="doc_subsubsection">
Reid Spencer	a3e435f	2007-04-04 02:42:35 +0000	[diff] [blame]	5044	<a name="int_memmove">'<tt>llvm.memmove</tt>' Intrinsic</a>
Chris Lattner	0eb51b4	2004-02-12 18:10:10 +0000	[diff] [blame]	5045	</div>
				5046
				5047	<div class="doc_text">
				5048
				5049	<h5>Syntax:</h5>
				5050	<pre>
Anton Korobeynikov	ec43a06	2007-03-22 00:02:17 +0000	[diff] [blame]	5051	declare void @llvm.memmove.i32(i8 * <dest>, i8 * <src>,
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	5052	i32 <len>, i32 <align>)
Anton Korobeynikov	ec43a06	2007-03-22 00:02:17 +0000	[diff] [blame]	5053	declare void @llvm.memmove.i64(i8 * <dest>, i8 * <src>,
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	5054	i64 <len>, i32 <align>)
Chris Lattner	0eb51b4	2004-02-12 18:10:10 +0000	[diff] [blame]	5055	</pre>
				5056
				5057	<h5>Overview:</h5>
				5058
				5059	<p>
Chris Lattner	5b310c3	2006-03-03 00:07:20 +0000	[diff] [blame]	5060	The '<tt>llvm.memmove.*</tt>' intrinsics move a block of memory from the source
				5061	location to the destination location. It is similar to the
Chris Lattner	4b2cbcf	2008-01-06 19:51:52 +0000	[diff] [blame]	5062	'<tt>llvm.memcpy</tt>' intrinsic but allows the two memory locations to overlap.
Chris Lattner	0eb51b4	2004-02-12 18:10:10 +0000	[diff] [blame]	5063	</p>
				5064
				5065	<p>
Chris Lattner	5b310c3	2006-03-03 00:07:20 +0000	[diff] [blame]	5066	Note that, unlike the standard libc function, the <tt>llvm.memmove.*</tt>
				5067	intrinsics do not return a value, and takes an extra alignment argument.
Chris Lattner	0eb51b4	2004-02-12 18:10:10 +0000	[diff] [blame]	5068	</p>
				5069
				5070	<h5>Arguments:</h5>
				5071
				5072	<p>
				5073	The first argument is a pointer to the destination, the second is a pointer to
Chris Lattner	5b310c3	2006-03-03 00:07:20 +0000	[diff] [blame]	5074	the source. The third argument is an integer argument
Chris Lattner	0eb51b4	2004-02-12 18:10:10 +0000	[diff] [blame]	5075	specifying the number of bytes to copy, and the fourth argument is the alignment
				5076	of the source and destination locations.
				5077	</p>
				5078
Chris Lattner	3301ced	2004-02-12 21:18:15 +0000	[diff] [blame]	5079	<p>
				5080	If the call to this intrinisic has an alignment value that is not 0 or 1, then
Chris Lattner	f0afc2c	2006-03-04 00:02:10 +0000	[diff] [blame]	5081	the caller guarantees that the source and destination pointers are aligned to
				5082	that boundary.
Chris Lattner	3301ced	2004-02-12 21:18:15 +0000	[diff] [blame]	5083	</p>
				5084
Chris Lattner	0eb51b4	2004-02-12 18:10:10 +0000	[diff] [blame]	5085	<h5>Semantics:</h5>
				5086
				5087	<p>
Chris Lattner	5b310c3	2006-03-03 00:07:20 +0000	[diff] [blame]	5088	The '<tt>llvm.memmove.*</tt>' intrinsics copy a block of memory from the source
Chris Lattner	0eb51b4	2004-02-12 18:10:10 +0000	[diff] [blame]	5089	location to the destination location, which may overlap. It
				5090	copies "len" bytes of memory over. If the argument is known to be aligned to
				5091	some boundary, this can be specified as the fourth argument, otherwise it should
				5092	be set to 0 or 1.
				5093	</p>
				5094	</div>
				5095
Chris Lattner	8ff7590	2004-01-06 05:31:32 +0000	[diff] [blame]	5096
Chris Lattner	1061064	2004-02-14 04:08:35 +0000	[diff] [blame]	5097	<!-- _______________________________________________________________________ -->
				5098	<div class="doc_subsubsection">
Reid Spencer	a3e435f	2007-04-04 02:42:35 +0000	[diff] [blame]	5099	<a name="int_memset">'<tt>llvm.memset.*</tt>' Intrinsics</a>
Chris Lattner	1061064	2004-02-14 04:08:35 +0000	[diff] [blame]	5100	</div>
				5101
				5102	<div class="doc_text">
				5103
				5104	<h5>Syntax:</h5>
				5105	<pre>
Anton Korobeynikov	ec43a06	2007-03-22 00:02:17 +0000	[diff] [blame]	5106	declare void @llvm.memset.i32(i8 * <dest>, i8 <val>,
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	5107	i32 <len>, i32 <align>)
Anton Korobeynikov	ec43a06	2007-03-22 00:02:17 +0000	[diff] [blame]	5108	declare void @llvm.memset.i64(i8 * <dest>, i8 <val>,
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	5109	i64 <len>, i32 <align>)
Chris Lattner	1061064	2004-02-14 04:08:35 +0000	[diff] [blame]	5110	</pre>
				5111
				5112	<h5>Overview:</h5>
				5113
				5114	<p>
Chris Lattner	5b310c3	2006-03-03 00:07:20 +0000	[diff] [blame]	5115	The '<tt>llvm.memset.*</tt>' intrinsics fill a block of memory with a particular
Chris Lattner	1061064	2004-02-14 04:08:35 +0000	[diff] [blame]	5116	byte value.
				5117	</p>
				5118
				5119	<p>
				5120	Note that, unlike the standard libc function, the <tt>llvm.memset</tt> intrinsic
				5121	does not return a value, and takes an extra alignment argument.
				5122	</p>
				5123
				5124	<h5>Arguments:</h5>
				5125
				5126	<p>
				5127	The first argument is a pointer to the destination to fill, the second is the
Chris Lattner	5b310c3	2006-03-03 00:07:20 +0000	[diff] [blame]	5128	byte value to fill it with, the third argument is an integer
Chris Lattner	1061064	2004-02-14 04:08:35 +0000	[diff] [blame]	5129	argument specifying the number of bytes to fill, and the fourth argument is the
				5130	known alignment of destination location.
				5131	</p>
				5132
				5133	<p>
				5134	If the call to this intrinisic has an alignment value that is not 0 or 1, then
Chris Lattner	f0afc2c	2006-03-04 00:02:10 +0000	[diff] [blame]	5135	the caller guarantees that the destination pointer is aligned to that boundary.
Chris Lattner	1061064	2004-02-14 04:08:35 +0000	[diff] [blame]	5136	</p>
				5137
				5138	<h5>Semantics:</h5>
				5139
				5140	<p>
Chris Lattner	5b310c3	2006-03-03 00:07:20 +0000	[diff] [blame]	5141	The '<tt>llvm.memset.*</tt>' intrinsics fill "len" bytes of memory starting at
				5142	the
Chris Lattner	1061064	2004-02-14 04:08:35 +0000	[diff] [blame]	5143	destination location. If the argument is known to be aligned to some boundary,
				5144	this can be specified as the fourth argument, otherwise it should be set to 0 or
				5145	1.
				5146	</p>
				5147	</div>
				5148
				5149
Chris Lattner	3200628	2004-06-11 02:28:03 +0000	[diff] [blame]	5150	<!-- _______________________________________________________________________ -->
				5151	<div class="doc_subsubsection">
Reid Spencer	a3e435f	2007-04-04 02:42:35 +0000	[diff] [blame]	5152	<a name="int_sqrt">'<tt>llvm.sqrt.*</tt>' Intrinsic</a>
Chris Lattner	a4d7414	2005-07-21 01:29:16 +0000	[diff] [blame]	5153	</div>
				5154
				5155	<div class="doc_text">
				5156
				5157	<h5>Syntax:</h5>
Dale Johannesen	408f9c1	2007-10-02 17:47:38 +0000	[diff] [blame]	5158	<p>This is an overloaded intrinsic. You can use <tt>llvm.sqrt</tt> on any
Dan Gohman	91c284c	2007-10-15 20:30:11 +0000	[diff] [blame]	5159	floating point or vector of floating point type. Not all targets support all
				5160	types however.
Chris Lattner	a4d7414	2005-07-21 01:29:16 +0000	[diff] [blame]	5161	<pre>
Dale Johannesen	408f9c1	2007-10-02 17:47:38 +0000	[diff] [blame]	5162	declare float @llvm.sqrt.f32(float %Val)
				5163	declare double @llvm.sqrt.f64(double %Val)
				5164	declare x86_fp80 @llvm.sqrt.f80(x86_fp80 %Val)
				5165	declare fp128 @llvm.sqrt.f128(fp128 %Val)
				5166	declare ppc_fp128 @llvm.sqrt.ppcf128(ppc_fp128 %Val)
Chris Lattner	a4d7414	2005-07-21 01:29:16 +0000	[diff] [blame]	5167	</pre>
				5168
				5169	<h5>Overview:</h5>
				5170
				5171	<p>
Reid Spencer	0b11820	2006-01-16 21:12:35 +0000	[diff] [blame]	5172	The '<tt>llvm.sqrt</tt>' intrinsics return the sqrt of the specified operand,
Dan Gohman	91c284c	2007-10-15 20:30:11 +0000	[diff] [blame]	5173	returning the same value as the libm '<tt>sqrt</tt>' functions would. Unlike
Chris Lattner	a4d7414	2005-07-21 01:29:16 +0000	[diff] [blame]	5174	<tt>sqrt</tt> in libm, however, <tt>llvm.sqrt</tt> has undefined behavior for
Chris Lattner	103e2d7	2008-01-29 07:00:44 +0000	[diff] [blame]	5175	negative numbers other than -0.0 (which allows for better optimization, because
				5176	there is no need to worry about errno being set). <tt>llvm.sqrt(-0.0)</tt> is
				5177	defined to return -0.0 like IEEE sqrt.
Chris Lattner	a4d7414	2005-07-21 01:29:16 +0000	[diff] [blame]	5178	</p>
				5179
				5180	<h5>Arguments:</h5>
				5181
				5182	<p>
				5183	The argument and return value are floating point numbers of the same type.
				5184	</p>
				5185
				5186	<h5>Semantics:</h5>
				5187
				5188	<p>
Dan Gohman	d6257fe	2007-07-16 14:37:41 +0000	[diff] [blame]	5189	This function returns the sqrt of the specified operand if it is a nonnegative
Chris Lattner	a4d7414	2005-07-21 01:29:16 +0000	[diff] [blame]	5190	floating point number.
				5191	</p>
				5192	</div>
				5193
Chris Lattner	f4d252d	2006-09-08 06:34:02 +0000	[diff] [blame]	5194	<!-- _______________________________________________________________________ -->
				5195	<div class="doc_subsubsection">
Reid Spencer	a3e435f	2007-04-04 02:42:35 +0000	[diff] [blame]	5196	<a name="int_powi">'<tt>llvm.powi.*</tt>' Intrinsic</a>
Chris Lattner	f4d252d	2006-09-08 06:34:02 +0000	[diff] [blame]	5197	</div>
				5198
				5199	<div class="doc_text">
				5200
				5201	<h5>Syntax:</h5>
Dale Johannesen	408f9c1	2007-10-02 17:47:38 +0000	[diff] [blame]	5202	<p>This is an overloaded intrinsic. You can use <tt>llvm.powi</tt> on any
Dan Gohman	91c284c	2007-10-15 20:30:11 +0000	[diff] [blame]	5203	floating point or vector of floating point type. Not all targets support all
				5204	types however.
Chris Lattner	f4d252d	2006-09-08 06:34:02 +0000	[diff] [blame]	5205	<pre>
Dale Johannesen	408f9c1	2007-10-02 17:47:38 +0000	[diff] [blame]	5206	declare float @llvm.powi.f32(float %Val, i32 %power)
				5207	declare double @llvm.powi.f64(double %Val, i32 %power)
				5208	declare x86_fp80 @llvm.powi.f80(x86_fp80 %Val, i32 %power)
				5209	declare fp128 @llvm.powi.f128(fp128 %Val, i32 %power)
				5210	declare ppc_fp128 @llvm.powi.ppcf128(ppc_fp128 %Val, i32 %power)
Chris Lattner	f4d252d	2006-09-08 06:34:02 +0000	[diff] [blame]	5211	</pre>
				5212
				5213	<h5>Overview:</h5>
				5214
				5215	<p>
				5216	The '<tt>llvm.powi.*</tt>' intrinsics return the first operand raised to the
				5217	specified (positive or negative) power. The order of evaluation of
Dan Gohman	91c284c	2007-10-15 20:30:11 +0000	[diff] [blame]	5218	multiplications is not defined. When a vector of floating point type is
				5219	used, the second argument remains a scalar integer value.
Chris Lattner	f4d252d	2006-09-08 06:34:02 +0000	[diff] [blame]	5220	</p>
				5221
				5222	<h5>Arguments:</h5>
				5223
				5224	<p>
				5225	The second argument is an integer power, and the first is a value to raise to
				5226	that power.
				5227	</p>
				5228
				5229	<h5>Semantics:</h5>
				5230
				5231	<p>
				5232	This function returns the first value raised to the second power with an
				5233	unspecified sequence of rounding operations.</p>
				5234	</div>
				5235
Dan Gohman	91c284c	2007-10-15 20:30:11 +0000	[diff] [blame]	5236	<!-- _______________________________________________________________________ -->
				5237	<div class="doc_subsubsection">
				5238	<a name="int_sin">'<tt>llvm.sin.*</tt>' Intrinsic</a>
				5239	</div>
				5240
				5241	<div class="doc_text">
				5242
				5243	<h5>Syntax:</h5>
				5244	<p>This is an overloaded intrinsic. You can use <tt>llvm.sin</tt> on any
				5245	floating point or vector of floating point type. Not all targets support all
				5246	types however.
				5247	<pre>
				5248	declare float @llvm.sin.f32(float %Val)
				5249	declare double @llvm.sin.f64(double %Val)
				5250	declare x86_fp80 @llvm.sin.f80(x86_fp80 %Val)
				5251	declare fp128 @llvm.sin.f128(fp128 %Val)
				5252	declare ppc_fp128 @llvm.sin.ppcf128(ppc_fp128 %Val)
				5253	</pre>
				5254
				5255	<h5>Overview:</h5>
				5256
				5257	<p>
				5258	The '<tt>llvm.sin.*</tt>' intrinsics return the sine of the operand.
				5259	</p>
				5260
				5261	<h5>Arguments:</h5>
				5262
				5263	<p>
				5264	The argument and return value are floating point numbers of the same type.
				5265	</p>
				5266
				5267	<h5>Semantics:</h5>
				5268
				5269	<p>
				5270	This function returns the sine of the specified operand, returning the
				5271	same values as the libm <tt>sin</tt> functions would, and handles error
Dan Gohman	ba83b7e	2007-10-17 18:05:13 +0000	[diff] [blame]	5272	conditions in the same way.</p>
Dan Gohman	91c284c	2007-10-15 20:30:11 +0000	[diff] [blame]	5273	</div>
				5274
				5275	<!-- _______________________________________________________________________ -->
				5276	<div class="doc_subsubsection">
				5277	<a name="int_cos">'<tt>llvm.cos.*</tt>' Intrinsic</a>
				5278	</div>
				5279
				5280	<div class="doc_text">
				5281
				5282	<h5>Syntax:</h5>
				5283	<p>This is an overloaded intrinsic. You can use <tt>llvm.cos</tt> on any
				5284	floating point or vector of floating point type. Not all targets support all
				5285	types however.
				5286	<pre>
				5287	declare float @llvm.cos.f32(float %Val)
				5288	declare double @llvm.cos.f64(double %Val)
				5289	declare x86_fp80 @llvm.cos.f80(x86_fp80 %Val)
				5290	declare fp128 @llvm.cos.f128(fp128 %Val)
				5291	declare ppc_fp128 @llvm.cos.ppcf128(ppc_fp128 %Val)
				5292	</pre>
				5293
				5294	<h5>Overview:</h5>
				5295
				5296	<p>
				5297	The '<tt>llvm.cos.*</tt>' intrinsics return the cosine of the operand.
				5298	</p>
				5299
				5300	<h5>Arguments:</h5>
				5301
				5302	<p>
				5303	The argument and return value are floating point numbers of the same type.
				5304	</p>
				5305
				5306	<h5>Semantics:</h5>
				5307
				5308	<p>
				5309	This function returns the cosine of the specified operand, returning the
				5310	same values as the libm <tt>cos</tt> functions would, and handles error
Dan Gohman	ba83b7e	2007-10-17 18:05:13 +0000	[diff] [blame]	5311	conditions in the same way.</p>
Dan Gohman	91c284c	2007-10-15 20:30:11 +0000	[diff] [blame]	5312	</div>
				5313
				5314	<!-- _______________________________________________________________________ -->
				5315	<div class="doc_subsubsection">
				5316	<a name="int_pow">'<tt>llvm.pow.*</tt>' Intrinsic</a>
				5317	</div>
				5318
				5319	<div class="doc_text">
				5320
				5321	<h5>Syntax:</h5>
				5322	<p>This is an overloaded intrinsic. You can use <tt>llvm.pow</tt> on any
				5323	floating point or vector of floating point type. Not all targets support all
				5324	types however.
				5325	<pre>
				5326	declare float @llvm.pow.f32(float %Val, float %Power)
				5327	declare double @llvm.pow.f64(double %Val, double %Power)
				5328	declare x86_fp80 @llvm.pow.f80(x86_fp80 %Val, x86_fp80 %Power)
				5329	declare fp128 @llvm.pow.f128(fp128 %Val, fp128 %Power)
				5330	declare ppc_fp128 @llvm.pow.ppcf128(ppc_fp128 %Val, ppc_fp128 Power)
				5331	</pre>
				5332
				5333	<h5>Overview:</h5>
				5334
				5335	<p>
				5336	The '<tt>llvm.pow.*</tt>' intrinsics return the first operand raised to the
				5337	specified (positive or negative) power.
				5338	</p>
				5339
				5340	<h5>Arguments:</h5>
				5341
				5342	<p>
				5343	The second argument is a floating point power, and the first is a value to
				5344	raise to that power.
				5345	</p>
				5346
				5347	<h5>Semantics:</h5>
				5348
				5349	<p>
				5350	This function returns the first value raised to the second power,
				5351	returning the
				5352	same values as the libm <tt>pow</tt> functions would, and handles error
Dan Gohman	ba83b7e	2007-10-17 18:05:13 +0000	[diff] [blame]	5353	conditions in the same way.</p>
Dan Gohman	91c284c	2007-10-15 20:30:11 +0000	[diff] [blame]	5354	</div>
				5355
Chris Lattner	f4d252d	2006-09-08 06:34:02 +0000	[diff] [blame]	5356
Andrew Lenharth	ec370fd	2005-05-03 18:01:48 +0000	[diff] [blame]	5357	<!-- ======================================================================= -->
				5358	<div class="doc_subsection">
Nate Begeman	7e36c47	2006-01-13 23:26:38 +0000	[diff] [blame]	5359	<a name="int_manip">Bit Manipulation Intrinsics</a>
Andrew Lenharth	ec370fd	2005-05-03 18:01:48 +0000	[diff] [blame]	5360	</div>
				5361
				5362	<div class="doc_text">
				5363	<p>
Nate Begeman	7e36c47	2006-01-13 23:26:38 +0000	[diff] [blame]	5364	LLVM provides intrinsics for a few important bit manipulation operations.
Andrew Lenharth	ec370fd	2005-05-03 18:01:48 +0000	[diff] [blame]	5365	These allow efficient code generation for some algorithms.
				5366	</p>
				5367
				5368	</div>
				5369
				5370	<!-- _______________________________________________________________________ -->
				5371	<div class="doc_subsubsection">
Reid Spencer	a3e435f	2007-04-04 02:42:35 +0000	[diff] [blame]	5372	<a name="int_bswap">'<tt>llvm.bswap.*</tt>' Intrinsics</a>
Nate Begeman	7e36c47	2006-01-13 23:26:38 +0000	[diff] [blame]	5373	</div>
				5374
				5375	<div class="doc_text">
				5376
				5377	<h5>Syntax:</h5>
Reid Spencer	409e28f	2007-04-01 08:04:23 +0000	[diff] [blame]	5378	<p>This is an overloaded intrinsic function. You can use bswap on any integer
Chandler Carruth	6994040	2007-08-04 01:51:18 +0000	[diff] [blame]	5379	type that is an even number of bytes (i.e. BitWidth % 16 == 0).
Nate Begeman	7e36c47	2006-01-13 23:26:38 +0000	[diff] [blame]	5380	<pre>
Chandler Carruth	6994040	2007-08-04 01:51:18 +0000	[diff] [blame]	5381	declare i16 @llvm.bswap.i16(i16 <id>)
				5382	declare i32 @llvm.bswap.i32(i32 <id>)
				5383	declare i64 @llvm.bswap.i64(i64 <id>)
Nate Begeman	7e36c47	2006-01-13 23:26:38 +0000	[diff] [blame]	5384	</pre>
				5385
				5386	<h5>Overview:</h5>
				5387
				5388	<p>
Reid Spencer	338ea09	2007-04-02 02:25:19 +0000	[diff] [blame]	5389	The '<tt>llvm.bswap</tt>' family of intrinsics is used to byte swap integer
Reid Spencer	409e28f	2007-04-01 08:04:23 +0000	[diff] [blame]	5390	values with an even number of bytes (positive multiple of 16 bits). These are
				5391	useful for performing operations on data that is not in the target's native
				5392	byte order.
Nate Begeman	7e36c47	2006-01-13 23:26:38 +0000	[diff] [blame]	5393	</p>
				5394
				5395	<h5>Semantics:</h5>
				5396
				5397	<p>
Chandler Carruth	6994040	2007-08-04 01:51:18 +0000	[diff] [blame]	5398	The <tt>llvm.bswap.i16</tt> intrinsic returns an i16 value that has the high
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	5399	and low byte of the input i16 swapped. Similarly, the <tt>llvm.bswap.i32</tt>
				5400	intrinsic returns an i32 value that has the four bytes of the input i32
				5401	swapped, so that if the input bytes are numbered 0, 1, 2, 3 then the returned
Chandler Carruth	6994040	2007-08-04 01:51:18 +0000	[diff] [blame]	5402	i32 will have its bytes in 3, 2, 1, 0 order. The <tt>llvm.bswap.i48</tt>,
				5403	<tt>llvm.bswap.i64</tt> and other intrinsics extend this concept to
Reid Spencer	409e28f	2007-04-01 08:04:23 +0000	[diff] [blame]	5404	additional even-byte lengths (6 bytes, 8 bytes and more, respectively).
Nate Begeman	7e36c47	2006-01-13 23:26:38 +0000	[diff] [blame]	5405	</p>
				5406
				5407	</div>
				5408
				5409	<!-- _______________________________________________________________________ -->
				5410	<div class="doc_subsubsection">
Reid Spencer	0b11820	2006-01-16 21:12:35 +0000	[diff] [blame]	5411	<a name="int_ctpop">'<tt>llvm.ctpop.*</tt>' Intrinsic</a>
Andrew Lenharth	ec370fd	2005-05-03 18:01:48 +0000	[diff] [blame]	5412	</div>
				5413
				5414	<div class="doc_text">
				5415
				5416	<h5>Syntax:</h5>
Reid Spencer	409e28f	2007-04-01 08:04:23 +0000	[diff] [blame]	5417	<p>This is an overloaded intrinsic. You can use llvm.ctpop on any integer bit
				5418	width. Not all targets support all bit widths however.
Andrew Lenharth	ec370fd	2005-05-03 18:01:48 +0000	[diff] [blame]	5419	<pre>
Chandler Carruth	6994040	2007-08-04 01:51:18 +0000	[diff] [blame]	5420	declare i8 @llvm.ctpop.i8 (i8 <src>)
				5421	declare i16 @llvm.ctpop.i16(i16 <src>)
Anton Korobeynikov	ec43a06	2007-03-22 00:02:17 +0000	[diff] [blame]	5422	declare i32 @llvm.ctpop.i32(i32 <src>)
Chandler Carruth	6994040	2007-08-04 01:51:18 +0000	[diff] [blame]	5423	declare i64 @llvm.ctpop.i64(i64 <src>)
				5424	declare i256 @llvm.ctpop.i256(i256 <src>)
Andrew Lenharth	ec370fd	2005-05-03 18:01:48 +0000	[diff] [blame]	5425	</pre>
				5426
				5427	<h5>Overview:</h5>
				5428
				5429	<p>
Chris Lattner	ec6cb61	2006-01-16 22:38:59 +0000	[diff] [blame]	5430	The '<tt>llvm.ctpop</tt>' family of intrinsics counts the number of bits set in a
				5431	value.
Andrew Lenharth	ec370fd	2005-05-03 18:01:48 +0000	[diff] [blame]	5432	</p>
				5433
				5434	<h5>Arguments:</h5>
				5435
				5436	<p>
Chris Lattner	cfe6b37	2005-05-07 01:46:40 +0000	[diff] [blame]	5437	The only argument is the value to be counted. The argument may be of any
Reid Spencer	a517338	2007-01-04 16:43:23 +0000	[diff] [blame]	5438	integer type. The return type must match the argument type.
Andrew Lenharth	ec370fd	2005-05-03 18:01:48 +0000	[diff] [blame]	5439	</p>
				5440
				5441	<h5>Semantics:</h5>
				5442
				5443	<p>
				5444	The '<tt>llvm.ctpop</tt>' intrinsic counts the 1's in a variable.
				5445	</p>
				5446	</div>
				5447
				5448	<!-- _______________________________________________________________________ -->
				5449	<div class="doc_subsubsection">
Chris Lattner	8a886be	2006-01-16 22:34:14 +0000	[diff] [blame]	5450	<a name="int_ctlz">'<tt>llvm.ctlz.*</tt>' Intrinsic</a>
Andrew Lenharth	ec370fd	2005-05-03 18:01:48 +0000	[diff] [blame]	5451	</div>
				5452
				5453	<div class="doc_text">
				5454
				5455	<h5>Syntax:</h5>
Reid Spencer	409e28f	2007-04-01 08:04:23 +0000	[diff] [blame]	5456	<p>This is an overloaded intrinsic. You can use <tt>llvm.ctlz</tt> on any
				5457	integer bit width. Not all targets support all bit widths however.
Andrew Lenharth	ec370fd	2005-05-03 18:01:48 +0000	[diff] [blame]	5458	<pre>
Chandler Carruth	6994040	2007-08-04 01:51:18 +0000	[diff] [blame]	5459	declare i8 @llvm.ctlz.i8 (i8 <src>)
				5460	declare i16 @llvm.ctlz.i16(i16 <src>)
Anton Korobeynikov	ec43a06	2007-03-22 00:02:17 +0000	[diff] [blame]	5461	declare i32 @llvm.ctlz.i32(i32 <src>)
Chandler Carruth	6994040	2007-08-04 01:51:18 +0000	[diff] [blame]	5462	declare i64 @llvm.ctlz.i64(i64 <src>)
				5463	declare i256 @llvm.ctlz.i256(i256 <src>)
Andrew Lenharth	ec370fd	2005-05-03 18:01:48 +0000	[diff] [blame]	5464	</pre>
				5465
				5466	<h5>Overview:</h5>
				5467
				5468	<p>
Reid Spencer	0b11820	2006-01-16 21:12:35 +0000	[diff] [blame]	5469	The '<tt>llvm.ctlz</tt>' family of intrinsic functions counts the number of
				5470	leading zeros in a variable.
Andrew Lenharth	ec370fd	2005-05-03 18:01:48 +0000	[diff] [blame]	5471	</p>
				5472
				5473	<h5>Arguments:</h5>
				5474
				5475	<p>
Chris Lattner	cfe6b37	2005-05-07 01:46:40 +0000	[diff] [blame]	5476	The only argument is the value to be counted. The argument may be of any
Reid Spencer	a517338	2007-01-04 16:43:23 +0000	[diff] [blame]	5477	integer type. The return type must match the argument type.
Andrew Lenharth	ec370fd	2005-05-03 18:01:48 +0000	[diff] [blame]	5478	</p>
				5479
				5480	<h5>Semantics:</h5>
				5481
				5482	<p>
Chris Lattner	eff29ab	2005-05-15 19:39:26 +0000	[diff] [blame]	5483	The '<tt>llvm.ctlz</tt>' intrinsic counts the leading (most significant) zeros
				5484	in a variable. If the src == 0 then the result is the size in bits of the type
Reid Spencer	ca86e16	2006-12-31 07:07:53 +0000	[diff] [blame]	5485	of src. For example, <tt>llvm.ctlz(i32 2) = 30</tt>.
Andrew Lenharth	ec370fd	2005-05-03 18:01:48 +0000	[diff] [blame]	5486	</p>
				5487	</div>
Chris Lattner	3200628	2004-06-11 02:28:03 +0000	[diff] [blame]	5488
				5489
Chris Lattner	eff29ab	2005-05-15 19:39:26 +0000	[diff] [blame]	5490
				5491	<!-- _______________________________________________________________________ -->
				5492	<div class="doc_subsubsection">
Chris Lattner	8a886be	2006-01-16 22:34:14 +0000	[diff] [blame]	5493	<a name="int_cttz">'<tt>llvm.cttz.*</tt>' Intrinsic</a>
Chris Lattner	eff29ab	2005-05-15 19:39:26 +0000	[diff] [blame]	5494	</div>
				5495
				5496	<div class="doc_text">
				5497
				5498	<h5>Syntax:</h5>
Reid Spencer	409e28f	2007-04-01 08:04:23 +0000	[diff] [blame]	5499	<p>This is an overloaded intrinsic. You can use <tt>llvm.cttz</tt> on any
				5500	integer bit width. Not all targets support all bit widths however.
Chris Lattner	eff29ab	2005-05-15 19:39:26 +0000	[diff] [blame]	5501	<pre>
Chandler Carruth	6994040	2007-08-04 01:51:18 +0000	[diff] [blame]	5502	declare i8 @llvm.cttz.i8 (i8 <src>)
				5503	declare i16 @llvm.cttz.i16(i16 <src>)
Anton Korobeynikov	ec43a06	2007-03-22 00:02:17 +0000	[diff] [blame]	5504	declare i32 @llvm.cttz.i32(i32 <src>)
Chandler Carruth	6994040	2007-08-04 01:51:18 +0000	[diff] [blame]	5505	declare i64 @llvm.cttz.i64(i64 <src>)
				5506	declare i256 @llvm.cttz.i256(i256 <src>)
Chris Lattner	eff29ab	2005-05-15 19:39:26 +0000	[diff] [blame]	5507	</pre>
				5508
				5509	<h5>Overview:</h5>
				5510
				5511	<p>
Reid Spencer	0b11820	2006-01-16 21:12:35 +0000	[diff] [blame]	5512	The '<tt>llvm.cttz</tt>' family of intrinsic functions counts the number of
				5513	trailing zeros.
Chris Lattner	eff29ab	2005-05-15 19:39:26 +0000	[diff] [blame]	5514	</p>
				5515
				5516	<h5>Arguments:</h5>
				5517
				5518	<p>
				5519	The only argument is the value to be counted. The argument may be of any
Reid Spencer	a517338	2007-01-04 16:43:23 +0000	[diff] [blame]	5520	integer type. The return type must match the argument type.
Chris Lattner	eff29ab	2005-05-15 19:39:26 +0000	[diff] [blame]	5521	</p>
				5522
				5523	<h5>Semantics:</h5>
				5524
				5525	<p>
				5526	The '<tt>llvm.cttz</tt>' intrinsic counts the trailing (least significant) zeros
				5527	in a variable. If the src == 0 then the result is the size in bits of the type
				5528	of src. For example, <tt>llvm.cttz(2) = 1</tt>.
				5529	</p>
				5530	</div>
				5531
Reid Spencer	497d93e	2007-04-01 08:27:01 +0000	[diff] [blame]	5532	<!-- _______________________________________________________________________ -->
				5533	<div class="doc_subsubsection">
Reid Spencer	beacf66	2007-04-10 02:51:31 +0000	[diff] [blame]	5534	<a name="int_part_select">'<tt>llvm.part.select.*</tt>' Intrinsic</a>
Reid Spencer	a13ba7d	2007-04-01 19:00:37 +0000	[diff] [blame]	5535	</div>
				5536
				5537	<div class="doc_text">
				5538
				5539	<h5>Syntax:</h5>
Reid Spencer	beacf66	2007-04-10 02:51:31 +0000	[diff] [blame]	5540	<p>This is an overloaded intrinsic. You can use <tt>llvm.part.select</tt>
Reid Spencer	a13ba7d	2007-04-01 19:00:37 +0000	[diff] [blame]	5541	on any integer bit width.
				5542	<pre>
Chandler Carruth	6994040	2007-08-04 01:51:18 +0000	[diff] [blame]	5543	declare i17 @llvm.part.select.i17 (i17 %val, i32 %loBit, i32 %hiBit)
				5544	declare i29 @llvm.part.select.i29 (i29 %val, i32 %loBit, i32 %hiBit)
Reid Spencer	a13ba7d	2007-04-01 19:00:37 +0000	[diff] [blame]	5545	</pre>
				5546
				5547	<h5>Overview:</h5>
Reid Spencer	beacf66	2007-04-10 02:51:31 +0000	[diff] [blame]	5548	<p>The '<tt>llvm.part.select</tt>' family of intrinsic functions selects a
Reid Spencer	a13ba7d	2007-04-01 19:00:37 +0000	[diff] [blame]	5549	range of bits from an integer value and returns them in the same bit width as
				5550	the original value.</p>
				5551
				5552	<h5>Arguments:</h5>
				5553	<p>The first argument, <tt>%val</tt> and the result may be integer types of
				5554	any bit width but they must have the same bit width. The second and third
Reid Spencer	a3e435f	2007-04-04 02:42:35 +0000	[diff] [blame]	5555	arguments must be <tt>i32</tt> type since they specify only a bit index.</p>
Reid Spencer	a13ba7d	2007-04-01 19:00:37 +0000	[diff] [blame]	5556
				5557	<h5>Semantics:</h5>
Reid Spencer	beacf66	2007-04-10 02:51:31 +0000	[diff] [blame]	5558	<p>The operation of the '<tt>llvm.part.select</tt>' intrinsic has two modes
Reid Spencer	a3e435f	2007-04-04 02:42:35 +0000	[diff] [blame]	5559	of operation: forwards and reverse. If <tt>%loBit</tt> is greater than
				5560	<tt>%hiBits</tt> then the intrinsic operates in reverse mode. Otherwise it
				5561	operates in forward mode.</p>
				5562	<p>In forward mode, this intrinsic is the equivalent of shifting <tt>%val</tt>
				5563	right by <tt>%loBit</tt> bits and then ANDing it with a mask with
Reid Spencer	a13ba7d	2007-04-01 19:00:37 +0000	[diff] [blame]	5564	only the <tt>%hiBit - %loBit</tt> bits set, as follows:</p>
				5565	<ol>
				5566	<li>The <tt>%val</tt> is shifted right (LSHR) by the number of bits specified
				5567	by <tt>%loBits</tt>. This normalizes the value to the low order bits.</li>
				5568	<li>The <tt>%loBits</tt> value is subtracted from the <tt>%hiBits</tt> value
				5569	to determine the number of bits to retain.</li>
				5570	<li>A mask of the retained bits is created by shifting a -1 value.</li>
				5571	<li>The mask is ANDed with <tt>%val</tt> to produce the result.
				5572	</ol>
Reid Spencer	d6a85b5	2007-05-14 16:14:57 +0000	[diff] [blame]	5573	<p>In reverse mode, a similar computation is made except that the bits are
				5574	returned in the reverse order. So, for example, if <tt>X</tt> has the value
				5575	<tt>i16 0x0ACF (101011001111)</tt> and we apply
				5576	<tt>part.select(i16 X, 8, 3)</tt> to it, we get back the value
				5577	<tt>i16 0x0026 (000000100110)</tt>.</p>
Reid Spencer	a13ba7d	2007-04-01 19:00:37 +0000	[diff] [blame]	5578	</div>
				5579
Reid Spencer	f86037f	2007-04-11 23:23:49 +0000	[diff] [blame]	5580	<div class="doc_subsubsection">
				5581	<a name="int_part_set">'<tt>llvm.part.set.*</tt>' Intrinsic</a>
				5582	</div>
				5583
				5584	<div class="doc_text">
				5585
				5586	<h5>Syntax:</h5>
				5587	<p>This is an overloaded intrinsic. You can use <tt>llvm.part.set</tt>
				5588	on any integer bit width.
				5589	<pre>
Chandler Carruth	6994040	2007-08-04 01:51:18 +0000	[diff] [blame]	5590	declare i17 @llvm.part.set.i17.i9 (i17 %val, i9 %repl, i32 %lo, i32 %hi)
				5591	declare i29 @llvm.part.set.i29.i9 (i29 %val, i9 %repl, i32 %lo, i32 %hi)
Reid Spencer	f86037f	2007-04-11 23:23:49 +0000	[diff] [blame]	5592	</pre>
				5593
				5594	<h5>Overview:</h5>
				5595	<p>The '<tt>llvm.part.set</tt>' family of intrinsic functions replaces a range
				5596	of bits in an integer value with another integer value. It returns the integer
				5597	with the replaced bits.</p>
				5598
				5599	<h5>Arguments:</h5>
				5600	<p>The first argument, <tt>%val</tt> and the result may be integer types of
				5601	any bit width but they must have the same bit width. <tt>%val</tt> is the value
				5602	whose bits will be replaced. The second argument, <tt>%repl</tt> may be an
				5603	integer of any bit width. The third and fourth arguments must be <tt>i32</tt>
				5604	type since they specify only a bit index.</p>
				5605
				5606	<h5>Semantics:</h5>
				5607	<p>The operation of the '<tt>llvm.part.set</tt>' intrinsic has two modes
				5608	of operation: forwards and reverse. If <tt>%lo</tt> is greater than
				5609	<tt>%hi</tt> then the intrinsic operates in reverse mode. Otherwise it
				5610	operates in forward mode.</p>
				5611	<p>For both modes, the <tt>%repl</tt> value is prepared for use by either
				5612	truncating it down to the size of the replacement area or zero extending it
				5613	up to that size.</p>
				5614	<p>In forward mode, the bits between <tt>%lo</tt> and <tt>%hi</tt> (inclusive)
				5615	are replaced with corresponding bits from <tt>%repl</tt>. That is the 0th bit
				5616	in <tt>%repl</tt> replaces the <tt>%lo</tt>th bit in <tt>%val</tt> and etc. up
				5617	to the <tt>%hi</tt>th bit.
Reid Spencer	c6749c4	2007-05-14 16:50:20 +0000	[diff] [blame]	5618	<p>In reverse mode, a similar computation is made except that the bits are
				5619	reversed. That is, the <tt>0</tt>th bit in <tt>%repl</tt> replaces the
				5620	<tt>%hi</tt> bit in <tt>%val</tt> and etc. down to the <tt>%lo</tt>th bit.
Reid Spencer	f86037f	2007-04-11 23:23:49 +0000	[diff] [blame]	5621	<h5>Examples:</h5>
				5622	<pre>
Reid Spencer	f0dbf64	2007-04-12 01:03:03 +0000	[diff] [blame]	5623	llvm.part.set(0xFFFF, 0, 4, 7) -> 0xFF0F
Reid Spencer	c6749c4	2007-05-14 16:50:20 +0000	[diff] [blame]	5624	llvm.part.set(0xFFFF, 0, 7, 4) -> 0xFF0F
				5625	llvm.part.set(0xFFFF, 1, 7, 4) -> 0xFF8F
				5626	llvm.part.set(0xFFFF, F, 8, 3) -> 0xFFE7
Reid Spencer	f0dbf64	2007-04-12 01:03:03 +0000	[diff] [blame]	5627	llvm.part.set(0xFFFF, 0, 3, 8) -> 0xFE07
Reid Spencer	c891084	2007-04-11 23:49:50 +0000	[diff] [blame]	5628	</pre>
Reid Spencer	f86037f	2007-04-11 23:23:49 +0000	[diff] [blame]	5629	</div>
				5630
Chris Lattner	8ff7590	2004-01-06 05:31:32 +0000	[diff] [blame]	5631	<!-- ======================================================================= -->
				5632	<div class="doc_subsection">
				5633	<a name="int_debugger">Debugger Intrinsics</a>
				5634	</div>
				5635
				5636	<div class="doc_text">
				5637	<p>
				5638	The LLVM debugger intrinsics (which all start with <tt>llvm.dbg.</tt> prefix),
				5639	are described in the <a
				5640	href="SourceLevelDebugging.html#format_common_intrinsics">LLVM Source Level
				5641	Debugging</a> document.
				5642	</p>
				5643	</div>
				5644
				5645
Jim Laskey	dd4ef1b	2007-03-14 19:31:19 +0000	[diff] [blame]	5646	<!-- ======================================================================= -->
				5647	<div class="doc_subsection">
				5648	<a name="int_eh">Exception Handling Intrinsics</a>
				5649	</div>
				5650
				5651	<div class="doc_text">
				5652	<p> The LLVM exception handling intrinsics (which all start with
				5653	<tt>llvm.eh.</tt> prefix), are described in the <a
				5654	href="ExceptionHandling.html#format_common_intrinsics">LLVM Exception
				5655	Handling</a> document. </p>
				5656	</div>
				5657
Tanya Lattner	6d806e9	2007-06-15 20:50:54 +0000	[diff] [blame]	5658	<!-- ======================================================================= -->
				5659	<div class="doc_subsection">
Duncan Sands	f7331b3	2007-09-11 14:10:23 +0000	[diff] [blame]	5660	<a name="int_trampoline">Trampoline Intrinsic</a>
Duncan Sands	36397f5	2007-07-27 12:58:54 +0000	[diff] [blame]	5661	</div>
				5662
				5663	<div class="doc_text">
				5664	<p>
Duncan Sands	f7331b3	2007-09-11 14:10:23 +0000	[diff] [blame]	5665	This intrinsic makes it possible to excise one parameter, marked with
Duncan Sands	36397f5	2007-07-27 12:58:54 +0000	[diff] [blame]	5666	the <tt>nest</tt> attribute, from a function. The result is a callable
				5667	function pointer lacking the nest parameter - the caller does not need
				5668	to provide a value for it. Instead, the value to use is stored in
				5669	advance in a "trampoline", a block of memory usually allocated
				5670	on the stack, which also contains code to splice the nest value into the
				5671	argument list. This is used to implement the GCC nested function address
				5672	extension.
				5673	</p>
				5674	<p>
				5675	For example, if the function is
				5676	<tt>i32 f(i8* nest %c, i32 %x, i32 %y)</tt> then the resulting function
Bill Wendling	03295ca	2007-09-22 09:23:55 +0000	[diff] [blame]	5677	pointer has signature <tt>i32 (i32, i32)*</tt>. It can be created as follows:</p>
Duncan Sands	36397f5	2007-07-27 12:58:54 +0000	[diff] [blame]	5678	<pre>
Duncan Sands	f7331b3	2007-09-11 14:10:23 +0000	[diff] [blame]	5679	%tramp = alloca [10 x i8], align 4 ; size and alignment only correct for X86
				5680	%tramp1 = getelementptr [10 x i8]* %tramp, i32 0, i32 0
				5681	%p = call i8* @llvm.init.trampoline( i8* %tramp1, i8* bitcast (i32 (i8* nest , i32, i32)* @f to i8), i8 %nval )
				5682	%fp = bitcast i8* %p to i32 (i32, i32)*
Duncan Sands	36397f5	2007-07-27 12:58:54 +0000	[diff] [blame]	5683	</pre>
Bill Wendling	03295ca	2007-09-22 09:23:55 +0000	[diff] [blame]	5684	<p>The call <tt>%val = call i32 %fp( i32 %x, i32 %y )</tt> is then equivalent
				5685	to <tt>%val = call i32 %f( i8* %nval, i32 %x, i32 %y )</tt>.</p>
Duncan Sands	36397f5	2007-07-27 12:58:54 +0000	[diff] [blame]	5686	</div>
				5687
				5688	<!-- _______________________________________________________________________ -->
				5689	<div class="doc_subsubsection">
				5690	<a name="int_it">'<tt>llvm.init.trampoline</tt>' Intrinsic</a>
				5691	</div>
				5692	<div class="doc_text">
				5693	<h5>Syntax:</h5>
				5694	<pre>
Duncan Sands	f7331b3	2007-09-11 14:10:23 +0000	[diff] [blame]	5695	declare i8* @llvm.init.trampoline(i8* <tramp>, i8* <func>, i8* <nval>)
Duncan Sands	36397f5	2007-07-27 12:58:54 +0000	[diff] [blame]	5696	</pre>
				5697	<h5>Overview:</h5>
				5698	<p>
Duncan Sands	f7331b3	2007-09-11 14:10:23 +0000	[diff] [blame]	5699	This fills the memory pointed to by <tt>tramp</tt> with code
				5700	and returns a function pointer suitable for executing it.
Duncan Sands	36397f5	2007-07-27 12:58:54 +0000	[diff] [blame]	5701	</p>
				5702	<h5>Arguments:</h5>
				5703	<p>
				5704	The <tt>llvm.init.trampoline</tt> intrinsic takes three arguments, all
				5705	pointers. The <tt>tramp</tt> argument must point to a sufficiently large
				5706	and sufficiently aligned block of memory; this memory is written to by the
Duncan Sands	c00c2ba	2007-08-22 23:39:54 +0000	[diff] [blame]	5707	intrinsic. Note that the size and the alignment are target-specific - LLVM
				5708	currently provides no portable way of determining them, so a front-end that
				5709	generates this intrinsic needs to have some target-specific knowledge.
				5710	The <tt>func</tt> argument must hold a function bitcast to an <tt>i8*</tt>.
Duncan Sands	36397f5	2007-07-27 12:58:54 +0000	[diff] [blame]	5711	</p>
				5712	<h5>Semantics:</h5>
				5713	<p>
				5714	The block of memory pointed to by <tt>tramp</tt> is filled with target
Duncan Sands	f7331b3	2007-09-11 14:10:23 +0000	[diff] [blame]	5715	dependent code, turning it into a function. A pointer to this function is
				5716	returned, but needs to be bitcast to an
Duncan Sands	36397f5	2007-07-27 12:58:54 +0000	[diff] [blame]	5717	<a href="#int_trampoline">appropriate function pointer type</a>
Duncan Sands	f7331b3	2007-09-11 14:10:23 +0000	[diff] [blame]	5718	before being called. The new function's signature is the same as that of
				5719	<tt>func</tt> with any arguments marked with the <tt>nest</tt> attribute
				5720	removed. At most one such <tt>nest</tt> argument is allowed, and it must be
				5721	of pointer type. Calling the new function is equivalent to calling
				5722	<tt>func</tt> with the same argument list, but with <tt>nval</tt> used for the
				5723	missing <tt>nest</tt> argument. If, after calling
				5724	<tt>llvm.init.trampoline</tt>, the memory pointed to by <tt>tramp</tt> is
				5725	modified, then the effect of any later call to the returned function pointer is
				5726	undefined.
Duncan Sands	36397f5	2007-07-27 12:58:54 +0000	[diff] [blame]	5727	</p>
				5728	</div>
				5729
				5730	<!-- ======================================================================= -->
				5731	<div class="doc_subsection">
Andrew Lenharth	22c5c1b	2008-02-16 01:24:58 +0000	[diff] [blame]	5732	<a name="int_atomics">Atomic Operations and Synchronization Intrinsics</a>
				5733	</div>
				5734
				5735	<div class="doc_text">
				5736	<p>
				5737	These intrinsic functions expand the "universal IR" of LLVM to represent
				5738	hardware constructs for atomic operations and memory synchronization. This
				5739	provides an interface to the hardware, not an interface to the programmer. It
Chris Lattner	d3eda89	2008-08-05 18:29:16 +0000	[diff] [blame]	5740	is aimed at a low enough level to allow any programming models or APIs
				5741	(Application Programming Interfaces) which
Andrew Lenharth	22c5c1b	2008-02-16 01:24:58 +0000	[diff] [blame]	5742	need atomic behaviors to map cleanly onto it. It is also modeled primarily on
				5743	hardware behavior. Just as hardware provides a "universal IR" for source
				5744	languages, it also provides a starting point for developing a "universal"
				5745	atomic operation and synchronization IR.
				5746	</p>
				5747	<p>
				5748	These do <em>not</em> form an API such as high-level threading libraries,
				5749	software transaction memory systems, atomic primitives, and intrinsic
				5750	functions as found in BSD, GNU libc, atomic_ops, APR, and other system and
				5751	application libraries. The hardware interface provided by LLVM should allow
				5752	a clean implementation of all of these APIs and parallel programming models.
				5753	No one model or paradigm should be selected above others unless the hardware
				5754	itself ubiquitously does so.
				5755
				5756	</p>
				5757	</div>
				5758
				5759	<!-- _______________________________________________________________________ -->
				5760	<div class="doc_subsubsection">
				5761	<a name="int_memory_barrier">'<tt>llvm.memory.barrier</tt>' Intrinsic</a>
				5762	</div>
				5763	<div class="doc_text">
				5764	<h5>Syntax:</h5>
				5765	<pre>
				5766	declare void @llvm.memory.barrier( i1 <ll>, i1 <ls>, i1 <sl>, i1 <ss>,
				5767	i1 <device> )
				5768
				5769	</pre>
				5770	<h5>Overview:</h5>
				5771	<p>
				5772	The <tt>llvm.memory.barrier</tt> intrinsic guarantees ordering between
				5773	specific pairs of memory access types.
				5774	</p>
				5775	<h5>Arguments:</h5>
				5776	<p>
				5777	The <tt>llvm.memory.barrier</tt> intrinsic requires five boolean arguments.
				5778	The first four arguments enables a specific barrier as listed below. The fith
				5779	argument specifies that the barrier applies to io or device or uncached memory.
				5780
				5781	</p>
				5782	<ul>
				5783	<li><tt>ll</tt>: load-load barrier</li>
				5784	<li><tt>ls</tt>: load-store barrier</li>
				5785	<li><tt>sl</tt>: store-load barrier</li>
				5786	<li><tt>ss</tt>: store-store barrier</li>
				5787	<li><tt>device</tt>: barrier applies to device and uncached memory also.
				5788	</ul>
				5789	<h5>Semantics:</h5>
				5790	<p>
				5791	This intrinsic causes the system to enforce some ordering constraints upon
				5792	the loads and stores of the program. This barrier does not indicate
				5793	<em>when</em> any events will occur, it only enforces an <em>order</em> in
				5794	which they occur. For any of the specified pairs of load and store operations
				5795	(f.ex. load-load, or store-load), all of the first operations preceding the
				5796	barrier will complete before any of the second operations succeeding the
				5797	barrier begin. Specifically the semantics for each pairing is as follows:
				5798	</p>
				5799	<ul>
				5800	<li><tt>ll</tt>: All loads before the barrier must complete before any load
				5801	after the barrier begins.</li>
				5802
				5803	<li><tt>ls</tt>: All loads before the barrier must complete before any
				5804	store after the barrier begins.</li>
				5805	<li><tt>ss</tt>: All stores before the barrier must complete before any
				5806	store after the barrier begins.</li>
				5807	<li><tt>sl</tt>: All stores before the barrier must complete before any
				5808	load after the barrier begins.</li>
				5809	</ul>
				5810	<p>
				5811	These semantics are applied with a logical "and" behavior when more than one
				5812	is enabled in a single memory barrier intrinsic.
				5813	</p>
				5814	<p>
				5815	Backends may implement stronger barriers than those requested when they do not
				5816	support as fine grained a barrier as requested. Some architectures do not
				5817	need all types of barriers and on such architectures, these become noops.
				5818	</p>
				5819	<h5>Example:</h5>
				5820	<pre>
				5821	%ptr = malloc i32
				5822	store i32 4, %ptr
				5823
				5824	%result1 = load i32* %ptr <i>; yields {i32}:result1 = 4</i>
				5825	call void @llvm.memory.barrier( i1 false, i1 true, i1 false, i1 false )
				5826	<i>; guarantee the above finishes</i>
				5827	store i32 8, %ptr <i>; before this begins</i>
				5828	</pre>
				5829	</div>
				5830
Andrew Lenharth	ab0b949	2008-02-21 06:45:13 +0000	[diff] [blame]	5831	<!-- _______________________________________________________________________ -->
				5832	<div class="doc_subsubsection">
Mon P Wang	2887310	2008-06-25 08:15:39 +0000	[diff] [blame]	5833	<a name="int_atomic_cmp_swap">'<tt>llvm.atomic.cmp.swap.*</tt>' Intrinsic</a>
Andrew Lenharth	ab0b949	2008-02-21 06:45:13 +0000	[diff] [blame]	5834	</div>
				5835	<div class="doc_text">
				5836	<h5>Syntax:</h5>
				5837	<p>
Mon P Wang	e3b3a72	2008-07-30 04:36:53 +0000	[diff] [blame]	5838	This is an overloaded intrinsic. You can use <tt>llvm.atomic.cmp.swap</tt> on
				5839	any integer bit width and for different address spaces. Not all targets
				5840	support all bit widths however.</p>
Andrew Lenharth	ab0b949	2008-02-21 06:45:13 +0000	[diff] [blame]	5841
				5842	<pre>
Mon P Wang	e3b3a72	2008-07-30 04:36:53 +0000	[diff] [blame]	5843	declare i8 @llvm.atomic.cmp.swap.i8.p0i8( i8* <ptr>, i8 <cmp>, i8 <val> )
				5844	declare i16 @llvm.atomic.cmp.swap.i16.p0i16( i16* <ptr>, i16 <cmp>, i16 <val> )
				5845	declare i32 @llvm.atomic.cmp.swap.i32.p0i32( i32* <ptr>, i32 <cmp>, i32 <val> )
				5846	declare i64 @llvm.atomic.cmp.swap.i64.p0i64( i64* <ptr>, i64 <cmp>, i64 <val> )
Andrew Lenharth	ab0b949	2008-02-21 06:45:13 +0000	[diff] [blame]	5847
				5848	</pre>
				5849	<h5>Overview:</h5>
				5850	<p>
				5851	This loads a value in memory and compares it to a given value. If they are
				5852	equal, it stores a new value into the memory.
				5853	</p>
				5854	<h5>Arguments:</h5>
				5855	<p>
Mon P Wang	2887310	2008-06-25 08:15:39 +0000	[diff] [blame]	5856	The <tt>llvm.atomic.cmp.swap</tt> intrinsic takes three arguments. The result as
Andrew Lenharth	ab0b949	2008-02-21 06:45:13 +0000	[diff] [blame]	5857	well as both <tt>cmp</tt> and <tt>val</tt> must be integer values with the
				5858	same bit width. The <tt>ptr</tt> argument must be a pointer to a value of
				5859	this integer type. While any bit width integer may be used, targets may only
				5860	lower representations they support in hardware.
				5861
				5862	</p>
				5863	<h5>Semantics:</h5>
				5864	<p>
				5865	This entire intrinsic must be executed atomically. It first loads the value
				5866	in memory pointed to by <tt>ptr</tt> and compares it with the value
				5867	<tt>cmp</tt>. If they are equal, <tt>val</tt> is stored into the memory. The
				5868	loaded value is yielded in all cases. This provides the equivalent of an
				5869	atomic compare-and-swap operation within the SSA framework.
				5870	</p>
				5871	<h5>Examples:</h5>
				5872
				5873	<pre>
				5874	%ptr = malloc i32
				5875	store i32 4, %ptr
				5876
				5877	%val1 = add i32 4, 4
Mon P Wang	e3b3a72	2008-07-30 04:36:53 +0000	[diff] [blame]	5878	%result1 = call i32 @llvm.atomic.cmp.swap.i32.p0i32( i32* %ptr, i32 4, %val1 )
Andrew Lenharth	ab0b949	2008-02-21 06:45:13 +0000	[diff] [blame]	5879	<i>; yields {i32}:result1 = 4</i>
				5880	%stored1 = icmp eq i32 %result1, 4 <i>; yields {i1}:stored1 = true</i>
				5881	%memval1 = load i32* %ptr <i>; yields {i32}:memval1 = 8</i>
				5882
				5883	%val2 = add i32 1, 1
Mon P Wang	e3b3a72	2008-07-30 04:36:53 +0000	[diff] [blame]	5884	%result2 = call i32 @llvm.atomic.cmp.swap.i32.p0i32( i32* %ptr, i32 5, %val2 )
Andrew Lenharth	ab0b949	2008-02-21 06:45:13 +0000	[diff] [blame]	5885	<i>; yields {i32}:result2 = 8</i>
				5886	%stored2 = icmp eq i32 %result2, 5 <i>; yields {i1}:stored2 = false</i>
				5887
				5888	%memval2 = load i32* %ptr <i>; yields {i32}:memval2 = 8</i>
				5889	</pre>
				5890	</div>
				5891
				5892	<!-- _______________________________________________________________________ -->
				5893	<div class="doc_subsubsection">
				5894	<a name="int_atomic_swap">'<tt>llvm.atomic.swap.*</tt>' Intrinsic</a>
				5895	</div>
				5896	<div class="doc_text">
				5897	<h5>Syntax:</h5>
				5898
				5899	<p>
				5900	This is an overloaded intrinsic. You can use <tt>llvm.atomic.swap</tt> on any
				5901	integer bit width. Not all targets support all bit widths however.</p>
				5902	<pre>
Mon P Wang	e3b3a72	2008-07-30 04:36:53 +0000	[diff] [blame]	5903	declare i8 @llvm.atomic.swap.i8.p0i8( i8* <ptr>, i8 <val> )
				5904	declare i16 @llvm.atomic.swap.i16.p0i16( i16* <ptr>, i16 <val> )
				5905	declare i32 @llvm.atomic.swap.i32.p0i32( i32* <ptr>, i32 <val> )
				5906	declare i64 @llvm.atomic.swap.i64.p0i64( i64* <ptr>, i64 <val> )
Andrew Lenharth	ab0b949	2008-02-21 06:45:13 +0000	[diff] [blame]	5907
				5908	</pre>
				5909	<h5>Overview:</h5>
				5910	<p>
				5911	This intrinsic loads the value stored in memory at <tt>ptr</tt> and yields
				5912	the value from memory. It then stores the value in <tt>val</tt> in the memory
				5913	at <tt>ptr</tt>.
				5914	</p>
				5915	<h5>Arguments:</h5>
				5916
				5917	<p>
Mon P Wang	2887310	2008-06-25 08:15:39 +0000	[diff] [blame]	5918	The <tt>llvm.atomic.swap</tt> intrinsic takes two arguments. Both the
Andrew Lenharth	ab0b949	2008-02-21 06:45:13 +0000	[diff] [blame]	5919	<tt>val</tt> argument and the result must be integers of the same bit width.
				5920	The first argument, <tt>ptr</tt>, must be a pointer to a value of this
				5921	integer type. The targets may only lower integer representations they
				5922	support.
				5923	</p>
				5924	<h5>Semantics:</h5>
				5925	<p>
				5926	This intrinsic loads the value pointed to by <tt>ptr</tt>, yields it, and
				5927	stores <tt>val</tt> back into <tt>ptr</tt> atomically. This provides the
				5928	equivalent of an atomic swap operation within the SSA framework.
				5929
				5930	</p>
				5931	<h5>Examples:</h5>
				5932	<pre>
				5933	%ptr = malloc i32
				5934	store i32 4, %ptr
				5935
				5936	%val1 = add i32 4, 4
Mon P Wang	e3b3a72	2008-07-30 04:36:53 +0000	[diff] [blame]	5937	%result1 = call i32 @llvm.atomic.swap.i32.p0i32( i32* %ptr, i32 %val1 )
Andrew Lenharth	ab0b949	2008-02-21 06:45:13 +0000	[diff] [blame]	5938	<i>; yields {i32}:result1 = 4</i>
				5939	%stored1 = icmp eq i32 %result1, 4 <i>; yields {i1}:stored1 = true</i>
				5940	%memval1 = load i32* %ptr <i>; yields {i32}:memval1 = 8</i>
				5941
				5942	%val2 = add i32 1, 1
Mon P Wang	e3b3a72	2008-07-30 04:36:53 +0000	[diff] [blame]	5943	%result2 = call i32 @llvm.atomic.swap.i32.p0i32( i32* %ptr, i32 %val2 )
Andrew Lenharth	ab0b949	2008-02-21 06:45:13 +0000	[diff] [blame]	5944	<i>; yields {i32}:result2 = 8</i>
				5945
				5946	%stored2 = icmp eq i32 %result2, 8 <i>; yields {i1}:stored2 = true</i>
				5947	%memval2 = load i32* %ptr <i>; yields {i32}:memval2 = 2</i>
				5948	</pre>
				5949	</div>
				5950
				5951	<!-- _______________________________________________________________________ -->
				5952	<div class="doc_subsubsection">
Mon P Wang	2887310	2008-06-25 08:15:39 +0000	[diff] [blame]	5953	<a name="int_atomic_load_add">'<tt>llvm.atomic.load.add.*</tt>' Intrinsic</a>
Andrew Lenharth	ab0b949	2008-02-21 06:45:13 +0000	[diff] [blame]	5954
				5955	</div>
				5956	<div class="doc_text">
				5957	<h5>Syntax:</h5>
				5958	<p>
Mon P Wang	2887310	2008-06-25 08:15:39 +0000	[diff] [blame]	5959	This is an overloaded intrinsic. You can use <tt>llvm.atomic.load.add</tt> on any
Andrew Lenharth	ab0b949	2008-02-21 06:45:13 +0000	[diff] [blame]	5960	integer bit width. Not all targets support all bit widths however.</p>
				5961	<pre>
Mon P Wang	e3b3a72	2008-07-30 04:36:53 +0000	[diff] [blame]	5962	declare i8 @llvm.atomic.load.add.i8..p0i8( i8* <ptr>, i8 <delta> )
				5963	declare i16 @llvm.atomic.load.add.i16..p0i16( i16* <ptr>, i16 <delta> )
				5964	declare i32 @llvm.atomic.load.add.i32..p0i32( i32* <ptr>, i32 <delta> )
				5965	declare i64 @llvm.atomic.load.add.i64..p0i64( i64* <ptr>, i64 <delta> )
Andrew Lenharth	ab0b949	2008-02-21 06:45:13 +0000	[diff] [blame]	5966
				5967	</pre>
				5968	<h5>Overview:</h5>
				5969	<p>
				5970	This intrinsic adds <tt>delta</tt> to the value stored in memory at
				5971	<tt>ptr</tt>. It yields the original value at <tt>ptr</tt>.
				5972	</p>
				5973	<h5>Arguments:</h5>
				5974	<p>
				5975
				5976	The intrinsic takes two arguments, the first a pointer to an integer value
				5977	and the second an integer value. The result is also an integer value. These
				5978	integer types can have any bit width, but they must all have the same bit
				5979	width. The targets may only lower integer representations they support.
				5980	</p>
				5981	<h5>Semantics:</h5>
				5982	<p>
				5983	This intrinsic does a series of operations atomically. It first loads the
				5984	value stored at <tt>ptr</tt>. It then adds <tt>delta</tt>, stores the result
				5985	to <tt>ptr</tt>. It yields the original value stored at <tt>ptr</tt>.
				5986	</p>
				5987
				5988	<h5>Examples:</h5>
				5989	<pre>
				5990	%ptr = malloc i32
				5991	store i32 4, %ptr
Mon P Wang	e3b3a72	2008-07-30 04:36:53 +0000	[diff] [blame]	5992	%result1 = call i32 @llvm.atomic.load.add.i32.p0i32( i32* %ptr, i32 4 )
Andrew Lenharth	ab0b949	2008-02-21 06:45:13 +0000	[diff] [blame]	5993	<i>; yields {i32}:result1 = 4</i>
Mon P Wang	e3b3a72	2008-07-30 04:36:53 +0000	[diff] [blame]	5994	%result2 = call i32 @llvm.atomic.load.add.i32.p0i32( i32* %ptr, i32 2 )
Andrew Lenharth	ab0b949	2008-02-21 06:45:13 +0000	[diff] [blame]	5995	<i>; yields {i32}:result2 = 8</i>
Mon P Wang	e3b3a72	2008-07-30 04:36:53 +0000	[diff] [blame]	5996	%result3 = call i32 @llvm.atomic.load.add.i32.p0i32( i32* %ptr, i32 5 )
Andrew Lenharth	ab0b949	2008-02-21 06:45:13 +0000	[diff] [blame]	5997	<i>; yields {i32}:result3 = 10</i>
Mon P Wang	2887310	2008-06-25 08:15:39 +0000	[diff] [blame]	5998	%memval1 = load i32* %ptr <i>; yields {i32}:memval1 = 15</i>
Andrew Lenharth	ab0b949	2008-02-21 06:45:13 +0000	[diff] [blame]	5999	</pre>
				6000	</div>
				6001
Mon P Wang	2887310	2008-06-25 08:15:39 +0000	[diff] [blame]	6002	<!-- _______________________________________________________________________ -->
				6003	<div class="doc_subsubsection">
				6004	<a name="int_atomic_load_sub">'<tt>llvm.atomic.load.sub.*</tt>' Intrinsic</a>
				6005
				6006	</div>
				6007	<div class="doc_text">
				6008	<h5>Syntax:</h5>
				6009	<p>
				6010	This is an overloaded intrinsic. You can use <tt>llvm.atomic.load.sub</tt> on
Mon P Wang	e3b3a72	2008-07-30 04:36:53 +0000	[diff] [blame]	6011	any integer bit width and for different address spaces. Not all targets
				6012	support all bit widths however.</p>
Mon P Wang	2887310	2008-06-25 08:15:39 +0000	[diff] [blame]	6013	<pre>
Mon P Wang	e3b3a72	2008-07-30 04:36:53 +0000	[diff] [blame]	6014	declare i8 @llvm.atomic.load.sub.i8.p0i32( i8* <ptr>, i8 <delta> )
				6015	declare i16 @llvm.atomic.load.sub.i16.p0i32( i16* <ptr>, i16 <delta> )
				6016	declare i32 @llvm.atomic.load.sub.i32.p0i32( i32* <ptr>, i32 <delta> )
				6017	declare i64 @llvm.atomic.load.sub.i64.p0i32( i64* <ptr>, i64 <delta> )
Mon P Wang	2887310	2008-06-25 08:15:39 +0000	[diff] [blame]	6018
				6019	</pre>
				6020	<h5>Overview:</h5>
				6021	<p>
				6022	This intrinsic subtracts <tt>delta</tt> to the value stored in memory at
				6023	<tt>ptr</tt>. It yields the original value at <tt>ptr</tt>.
				6024	</p>
				6025	<h5>Arguments:</h5>
				6026	<p>
				6027
				6028	The intrinsic takes two arguments, the first a pointer to an integer value
				6029	and the second an integer value. The result is also an integer value. These
				6030	integer types can have any bit width, but they must all have the same bit
				6031	width. The targets may only lower integer representations they support.
				6032	</p>
				6033	<h5>Semantics:</h5>
				6034	<p>
				6035	This intrinsic does a series of operations atomically. It first loads the
				6036	value stored at <tt>ptr</tt>. It then subtracts <tt>delta</tt>, stores the
				6037	result to <tt>ptr</tt>. It yields the original value stored at <tt>ptr</tt>.
				6038	</p>
				6039
				6040	<h5>Examples:</h5>
				6041	<pre>
				6042	%ptr = malloc i32
				6043	store i32 8, %ptr
Mon P Wang	e3b3a72	2008-07-30 04:36:53 +0000	[diff] [blame]	6044	%result1 = call i32 @llvm.atomic.load.sub.i32.p0i32( i32* %ptr, i32 4 )
Mon P Wang	2887310	2008-06-25 08:15:39 +0000	[diff] [blame]	6045	<i>; yields {i32}:result1 = 8</i>
Mon P Wang	e3b3a72	2008-07-30 04:36:53 +0000	[diff] [blame]	6046	%result2 = call i32 @llvm.atomic.load.sub.i32.p0i32( i32* %ptr, i32 2 )
Mon P Wang	2887310	2008-06-25 08:15:39 +0000	[diff] [blame]	6047	<i>; yields {i32}:result2 = 4</i>
Mon P Wang	e3b3a72	2008-07-30 04:36:53 +0000	[diff] [blame]	6048	%result3 = call i32 @llvm.atomic.load.sub.i32.p0i32( i32* %ptr, i32 5 )
Mon P Wang	2887310	2008-06-25 08:15:39 +0000	[diff] [blame]	6049	<i>; yields {i32}:result3 = 2</i>
				6050	%memval1 = load i32* %ptr <i>; yields {i32}:memval1 = -3</i>
				6051	</pre>
				6052	</div>
				6053
				6054	<!-- _______________________________________________________________________ -->
				6055	<div class="doc_subsubsection">
				6056	<a name="int_atomic_load_and">'<tt>llvm.atomic.load.and.*</tt>' Intrinsic</a><br>
				6057	<a name="int_atomic_load_nand">'<tt>llvm.atomic.load.nand.*</tt>' Intrinsic</a><br>
				6058	<a name="int_atomic_load_or">'<tt>llvm.atomic.load.or.*</tt>' Intrinsic</a><br>
				6059	<a name="int_atomic_load_xor">'<tt>llvm.atomic.load.xor.*</tt>' Intrinsic</a><br>
				6060
				6061	</div>
				6062	<div class="doc_text">
				6063	<h5>Syntax:</h5>
				6064	<p>
				6065	These are overloaded intrinsics. You can use <tt>llvm.atomic.load_and</tt>,
				6066	<tt>llvm.atomic.load_nand</tt>, <tt>llvm.atomic.load_or</tt>, and
Mon P Wang	e3b3a72	2008-07-30 04:36:53 +0000	[diff] [blame]	6067	<tt>llvm.atomic.load_xor</tt> on any integer bit width and for different
				6068	address spaces. Not all targets support all bit widths however.</p>
Mon P Wang	2887310	2008-06-25 08:15:39 +0000	[diff] [blame]	6069	<pre>
Mon P Wang	e3b3a72	2008-07-30 04:36:53 +0000	[diff] [blame]	6070	declare i8 @llvm.atomic.load.and.i8.p0i8( i8* <ptr>, i8 <delta> )
				6071	declare i16 @llvm.atomic.load.and.i16.p0i16( i16* <ptr>, i16 <delta> )
				6072	declare i32 @llvm.atomic.load.and.i32.p0i32( i32* <ptr>, i32 <delta> )
				6073	declare i64 @llvm.atomic.load.and.i64.p0i64( i64* <ptr>, i64 <delta> )
Mon P Wang	2887310	2008-06-25 08:15:39 +0000	[diff] [blame]	6074
				6075	</pre>
				6076
				6077	<pre>
Mon P Wang	e3b3a72	2008-07-30 04:36:53 +0000	[diff] [blame]	6078	declare i8 @llvm.atomic.load.or.i8.p0i8( i8* <ptr>, i8 <delta> )
				6079	declare i16 @llvm.atomic.load.or.i16.p0i16( i16* <ptr>, i16 <delta> )
				6080	declare i32 @llvm.atomic.load.or.i32.p0i32( i32* <ptr>, i32 <delta> )
				6081	declare i64 @llvm.atomic.load.or.i64.p0i64( i64* <ptr>, i64 <delta> )
Mon P Wang	2887310	2008-06-25 08:15:39 +0000	[diff] [blame]	6082
				6083	</pre>
				6084
				6085	<pre>
Mon P Wang	e3b3a72	2008-07-30 04:36:53 +0000	[diff] [blame]	6086	declare i8 @llvm.atomic.load.nand.i8.p0i32( i8* <ptr>, i8 <delta> )
				6087	declare i16 @llvm.atomic.load.nand.i16.p0i32( i16* <ptr>, i16 <delta> )
				6088	declare i32 @llvm.atomic.load.nand.i32.p0i32( i32* <ptr>, i32 <delta> )
				6089	declare i64 @llvm.atomic.load.nand.i64.p0i32( i64* <ptr>, i64 <delta> )
Mon P Wang	2887310	2008-06-25 08:15:39 +0000	[diff] [blame]	6090
				6091	</pre>
				6092
				6093	<pre>
Mon P Wang	e3b3a72	2008-07-30 04:36:53 +0000	[diff] [blame]	6094	declare i8 @llvm.atomic.load.xor.i8.p0i32( i8* <ptr>, i8 <delta> )
				6095	declare i16 @llvm.atomic.load.xor.i16.p0i32( i16* <ptr>, i16 <delta> )
				6096	declare i32 @llvm.atomic.load.xor.i32.p0i32( i32* <ptr>, i32 <delta> )
				6097	declare i64 @llvm.atomic.load.xor.i64.p0i32( i64* <ptr>, i64 <delta> )
Mon P Wang	2887310	2008-06-25 08:15:39 +0000	[diff] [blame]	6098
				6099	</pre>
				6100	<h5>Overview:</h5>
				6101	<p>
				6102	These intrinsics bitwise the operation (and, nand, or, xor) <tt>delta</tt> to
				6103	the value stored in memory at <tt>ptr</tt>. It yields the original value
				6104	at <tt>ptr</tt>.
				6105	</p>
				6106	<h5>Arguments:</h5>
				6107	<p>
				6108
				6109	These intrinsics take two arguments, the first a pointer to an integer value
				6110	and the second an integer value. The result is also an integer value. These
				6111	integer types can have any bit width, but they must all have the same bit
				6112	width. The targets may only lower integer representations they support.
				6113	</p>
				6114	<h5>Semantics:</h5>
				6115	<p>
				6116	These intrinsics does a series of operations atomically. They first load the
				6117	value stored at <tt>ptr</tt>. They then do the bitwise operation
				6118	<tt>delta</tt>, store the result to <tt>ptr</tt>. They yield the original
				6119	value stored at <tt>ptr</tt>.
				6120	</p>
				6121
				6122	<h5>Examples:</h5>
				6123	<pre>
				6124	%ptr = malloc i32
				6125	store i32 0x0F0F, %ptr
Mon P Wang	e3b3a72	2008-07-30 04:36:53 +0000	[diff] [blame]	6126	%result0 = call i32 @llvm.atomic.load.nand.i32.p0i32( i32* %ptr, i32 0xFF )
Mon P Wang	2887310	2008-06-25 08:15:39 +0000	[diff] [blame]	6127	<i>; yields {i32}:result0 = 0x0F0F</i>
Mon P Wang	e3b3a72	2008-07-30 04:36:53 +0000	[diff] [blame]	6128	%result1 = call i32 @llvm.atomic.load.and.i32.p0i32( i32* %ptr, i32 0xFF )
Mon P Wang	2887310	2008-06-25 08:15:39 +0000	[diff] [blame]	6129	<i>; yields {i32}:result1 = 0xFFFFFFF0</i>
Mon P Wang	e3b3a72	2008-07-30 04:36:53 +0000	[diff] [blame]	6130	%result2 = call i32 @llvm.atomic.load.or.i32.p0i32( i32* %ptr, i32 0F )
Mon P Wang	2887310	2008-06-25 08:15:39 +0000	[diff] [blame]	6131	<i>; yields {i32}:result2 = 0xF0</i>
Mon P Wang	e3b3a72	2008-07-30 04:36:53 +0000	[diff] [blame]	6132	%result3 = call i32 @llvm.atomic.load.xor.i32.p0i32( i32* %ptr, i32 0F )
Mon P Wang	2887310	2008-06-25 08:15:39 +0000	[diff] [blame]	6133	<i>; yields {i32}:result3 = FF</i>
				6134	%memval1 = load i32* %ptr <i>; yields {i32}:memval1 = F0</i>
				6135	</pre>
				6136	</div>
				6137
				6138
				6139	<!-- _______________________________________________________________________ -->
				6140	<div class="doc_subsubsection">
				6141	<a name="int_atomic_load_max">'<tt>llvm.atomic.load.max.*</tt>' Intrinsic</a><br>
				6142	<a name="int_atomic_load_min">'<tt>llvm.atomic.load.min.*</tt>' Intrinsic</a><br>
				6143	<a name="int_atomic_load_umax">'<tt>llvm.atomic.load.umax.*</tt>' Intrinsic</a><br>
				6144	<a name="int_atomic_load_umin">'<tt>llvm.atomic.load.umin.*</tt>' Intrinsic</a><br>
				6145
				6146	</div>
				6147	<div class="doc_text">
				6148	<h5>Syntax:</h5>
				6149	<p>
				6150	These are overloaded intrinsics. You can use <tt>llvm.atomic.load_max</tt>,
				6151	<tt>llvm.atomic.load_min</tt>, <tt>llvm.atomic.load_umax</tt>, and
Mon P Wang	e3b3a72	2008-07-30 04:36:53 +0000	[diff] [blame]	6152	<tt>llvm.atomic.load_umin</tt> on any integer bit width and for different
				6153	address spaces. Not all targets
Mon P Wang	2887310	2008-06-25 08:15:39 +0000	[diff] [blame]	6154	support all bit widths however.</p>
				6155	<pre>
Mon P Wang	e3b3a72	2008-07-30 04:36:53 +0000	[diff] [blame]	6156	declare i8 @llvm.atomic.load.max.i8.p0i8( i8* <ptr>, i8 <delta> )
				6157	declare i16 @llvm.atomic.load.max.i16.p0i16( i16* <ptr>, i16 <delta> )
				6158	declare i32 @llvm.atomic.load.max.i32.p0i32( i32* <ptr>, i32 <delta> )
				6159	declare i64 @llvm.atomic.load.max.i64.p0i64( i64* <ptr>, i64 <delta> )
Mon P Wang	2887310	2008-06-25 08:15:39 +0000	[diff] [blame]	6160
				6161	</pre>
				6162
				6163	<pre>
Mon P Wang	e3b3a72	2008-07-30 04:36:53 +0000	[diff] [blame]	6164	declare i8 @llvm.atomic.load.min.i8.p0i8( i8* <ptr>, i8 <delta> )
				6165	declare i16 @llvm.atomic.load.min.i16.p0i16( i16* <ptr>, i16 <delta> )
				6166	declare i32 @llvm.atomic.load.min.i32..p0i32( i32* <ptr>, i32 <delta> )
				6167	declare i64 @llvm.atomic.load.min.i64..p0i64( i64* <ptr>, i64 <delta> )
Mon P Wang	2887310	2008-06-25 08:15:39 +0000	[diff] [blame]	6168
				6169	</pre>
				6170
				6171	<pre>
Mon P Wang	e3b3a72	2008-07-30 04:36:53 +0000	[diff] [blame]	6172	declare i8 @llvm.atomic.load.umax.i8.p0i8( i8* <ptr>, i8 <delta> )
				6173	declare i16 @llvm.atomic.load.umax.i16.p0i16( i16* <ptr>, i16 <delta> )
				6174	declare i32 @llvm.atomic.load.umax.i32.p0i32( i32* <ptr>, i32 <delta> )
				6175	declare i64 @llvm.atomic.load.umax.i64.p0i64( i64* <ptr>, i64 <delta> )
Mon P Wang	2887310	2008-06-25 08:15:39 +0000	[diff] [blame]	6176
				6177	</pre>
				6178
				6179	<pre>
Mon P Wang	e3b3a72	2008-07-30 04:36:53 +0000	[diff] [blame]	6180	declare i8 @llvm.atomic.load.umin.i8..p0i8( i8* <ptr>, i8 <delta> )
				6181	declare i16 @llvm.atomic.load.umin.i16.p0i16( i16* <ptr>, i16 <delta> )
				6182	declare i32 @llvm.atomic.load.umin.i32..p0i32( i32* <ptr>, i32 <delta> )
				6183	declare i64 @llvm.atomic.load.umin.i64..p0i64( i64* <ptr>, i64 <delta> )
Mon P Wang	2887310	2008-06-25 08:15:39 +0000	[diff] [blame]	6184
				6185	</pre>
				6186	<h5>Overview:</h5>
				6187	<p>
				6188	These intrinsics takes the signed or unsigned minimum or maximum of
				6189	<tt>delta</tt> and the value stored in memory at <tt>ptr</tt>. It yields the
				6190	original value at <tt>ptr</tt>.
				6191	</p>
				6192	<h5>Arguments:</h5>
				6193	<p>
				6194
				6195	These intrinsics take two arguments, the first a pointer to an integer value
				6196	and the second an integer value. The result is also an integer value. These
				6197	integer types can have any bit width, but they must all have the same bit
				6198	width. The targets may only lower integer representations they support.
				6199	</p>
				6200	<h5>Semantics:</h5>
				6201	<p>
				6202	These intrinsics does a series of operations atomically. They first load the
				6203	value stored at <tt>ptr</tt>. They then do the signed or unsigned min or max
				6204	<tt>delta</tt> and the value, store the result to <tt>ptr</tt>. They yield
				6205	the original value stored at <tt>ptr</tt>.
				6206	</p>
				6207
				6208	<h5>Examples:</h5>
				6209	<pre>
				6210	%ptr = malloc i32
				6211	store i32 7, %ptr
Mon P Wang	e3b3a72	2008-07-30 04:36:53 +0000	[diff] [blame]	6212	%result0 = call i32 @llvm.atomic.load.min.i32.p0i32( i32* %ptr, i32 -2 )
Mon P Wang	2887310	2008-06-25 08:15:39 +0000	[diff] [blame]	6213	<i>; yields {i32}:result0 = 7</i>
Mon P Wang	e3b3a72	2008-07-30 04:36:53 +0000	[diff] [blame]	6214	%result1 = call i32 @llvm.atomic.load.max.i32.p0i32( i32* %ptr, i32 8 )
Mon P Wang	2887310	2008-06-25 08:15:39 +0000	[diff] [blame]	6215	<i>; yields {i32}:result1 = -2</i>
Mon P Wang	e3b3a72	2008-07-30 04:36:53 +0000	[diff] [blame]	6216	%result2 = call i32 @llvm.atomic.load.umin.i32.p0i32( i32* %ptr, i32 10 )
Mon P Wang	2887310	2008-06-25 08:15:39 +0000	[diff] [blame]	6217	<i>; yields {i32}:result2 = 8</i>
Mon P Wang	e3b3a72	2008-07-30 04:36:53 +0000	[diff] [blame]	6218	%result3 = call i32 @llvm.atomic.load.umax.i32.p0i32( i32* %ptr, i32 30 )
Mon P Wang	2887310	2008-06-25 08:15:39 +0000	[diff] [blame]	6219	<i>; yields {i32}:result3 = 8</i>
				6220	%memval1 = load i32* %ptr <i>; yields {i32}:memval1 = 30</i>
				6221	</pre>
				6222	</div>
Andrew Lenharth	22c5c1b	2008-02-16 01:24:58 +0000	[diff] [blame]	6223
				6224	<!-- ======================================================================= -->
				6225	<div class="doc_subsection">
Tanya Lattner	6d806e9	2007-06-15 20:50:54 +0000	[diff] [blame]	6226	<a name="int_general">General Intrinsics</a>
				6227	</div>
				6228
				6229	<div class="doc_text">
				6230	<p> This class of intrinsics is designed to be generic and has
				6231	no specific purpose. </p>
				6232	</div>
				6233
				6234	<!-- _______________________________________________________________________ -->
				6235	<div class="doc_subsubsection">
				6236	<a name="int_var_annotation">'<tt>llvm.var.annotation</tt>' Intrinsic</a>
				6237	</div>
				6238
				6239	<div class="doc_text">
				6240
				6241	<h5>Syntax:</h5>
				6242	<pre>
Tanya Lattner	d2e8442	2007-06-18 23:42:37 +0000	[diff] [blame]	6243	declare void @llvm.var.annotation(i8* <val>, i8* <str>, i8* <str>, i32 <int> )
Tanya Lattner	6d806e9	2007-06-15 20:50:54 +0000	[diff] [blame]	6244	</pre>
				6245
				6246	<h5>Overview:</h5>
				6247
				6248	<p>
				6249	The '<tt>llvm.var.annotation</tt>' intrinsic
				6250	</p>
				6251
				6252	<h5>Arguments:</h5>
				6253
				6254	<p>
Tanya Lattner	d2e8442	2007-06-18 23:42:37 +0000	[diff] [blame]	6255	The first argument is a pointer to a value, the second is a pointer to a
				6256	global string, the third is a pointer to a global string which is the source
				6257	file name, and the last argument is the line number.
Tanya Lattner	6d806e9	2007-06-15 20:50:54 +0000	[diff] [blame]	6258	</p>
				6259
				6260	<h5>Semantics:</h5>
				6261
				6262	<p>
Anton Korobeynikov	4cb8618	2008-01-15 22:31:34 +0000	[diff] [blame]	6263	This intrinsic allows annotation of local variables with arbitrary strings.
Tanya Lattner	6d806e9	2007-06-15 20:50:54 +0000	[diff] [blame]	6264	This can be useful for special purpose optimizations that want to look for these
Anton Korobeynikov	4cb8618	2008-01-15 22:31:34 +0000	[diff] [blame]	6265	annotations. These have no other defined use, they are ignored by code
				6266	generation and optimization.
				6267	</p>
Tanya Lattner	6d806e9	2007-06-15 20:50:54 +0000	[diff] [blame]	6268	</div>
				6269
Tanya Lattner	b636788	2007-09-21 22:59:12 +0000	[diff] [blame]	6270	<!-- _______________________________________________________________________ -->
				6271	<div class="doc_subsubsection">
Tanya Lattner	e1a8da0	2007-09-21 23:57:59 +0000	[diff] [blame]	6272	<a name="int_annotation">'<tt>llvm.annotation.*</tt>' Intrinsic</a>
Tanya Lattner	b636788	2007-09-21 22:59:12 +0000	[diff] [blame]	6273	</div>
				6274
				6275	<div class="doc_text">
				6276
				6277	<h5>Syntax:</h5>
Tanya Lattner	39cfba6	2007-09-21 23:56:27 +0000	[diff] [blame]	6278	<p>This is an overloaded intrinsic. You can use '<tt>llvm.annotation</tt>' on
				6279	any integer bit width.
				6280	</p>
Tanya Lattner	b636788	2007-09-21 22:59:12 +0000	[diff] [blame]	6281	<pre>
Tanya Lattner	d3989a8	2007-09-22 00:03:01 +0000	[diff] [blame]	6282	declare i8 @llvm.annotation.i8(i8 <val>, i8* <str>, i8* <str>, i32 <int> )
				6283	declare i16 @llvm.annotation.i16(i16 <val>, i8* <str>, i8* <str>, i32 <int> )
				6284	declare i32 @llvm.annotation.i32(i32 <val>, i8* <str>, i8* <str>, i32 <int> )
				6285	declare i64 @llvm.annotation.i64(i64 <val>, i8* <str>, i8* <str>, i32 <int> )
				6286	declare i256 @llvm.annotation.i256(i256 <val>, i8* <str>, i8* <str>, i32 <int> )
Tanya Lattner	b636788	2007-09-21 22:59:12 +0000	[diff] [blame]	6287	</pre>
				6288
				6289	<h5>Overview:</h5>
Tanya Lattner	39cfba6	2007-09-21 23:56:27 +0000	[diff] [blame]	6290
				6291	<p>
				6292	The '<tt>llvm.annotation</tt>' intrinsic.
Tanya Lattner	b636788	2007-09-21 22:59:12 +0000	[diff] [blame]	6293	</p>
				6294
				6295	<h5>Arguments:</h5>
				6296
				6297	<p>
				6298	The first argument is an integer value (result of some expression),
				6299	the second is a pointer to a global string, the third is a pointer to a global
				6300	string which is the source file name, and the last argument is the line number.
Tanya Lattner	39cfba6	2007-09-21 23:56:27 +0000	[diff] [blame]	6301	It returns the value of the first argument.
Tanya Lattner	b636788	2007-09-21 22:59:12 +0000	[diff] [blame]	6302	</p>
				6303
				6304	<h5>Semantics:</h5>
				6305
				6306	<p>
				6307	This intrinsic allows annotations to be put on arbitrary expressions
				6308	with arbitrary strings. This can be useful for special purpose optimizations
				6309	that want to look for these annotations. These have no other defined use, they
				6310	are ignored by code generation and optimization.
				6311	</div>
Jim Laskey	dd4ef1b	2007-03-14 19:31:19 +0000	[diff] [blame]	6312
Anton Korobeynikov	4cb8618	2008-01-15 22:31:34 +0000	[diff] [blame]	6313	<!-- _______________________________________________________________________ -->
				6314	<div class="doc_subsubsection">
				6315	<a name="int_trap">'<tt>llvm.trap</tt>' Intrinsic</a>
				6316	</div>
				6317
				6318	<div class="doc_text">
				6319
				6320	<h5>Syntax:</h5>
				6321	<pre>
				6322	declare void @llvm.trap()
				6323	</pre>
				6324
				6325	<h5>Overview:</h5>
				6326
				6327	<p>
				6328	The '<tt>llvm.trap</tt>' intrinsic
				6329	</p>
				6330
				6331	<h5>Arguments:</h5>
				6332
				6333	<p>
				6334	None
				6335	</p>
				6336
				6337	<h5>Semantics:</h5>
				6338
				6339	<p>
				6340	This intrinsics is lowered to the target dependent trap instruction. If the
				6341	target does not have a trap instruction, this intrinsic will be lowered to the
				6342	call of the abort() function.
				6343	</p>
				6344	</div>
				6345
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	6346	<!-- *********************************************************************** -->
Chris Lattner	0095054	2001-06-06 20:29:01 +0000	[diff] [blame]	6347	<hr>
Misha Brukman	daa4cb0	2004-03-01 17:47:27 +0000	[diff] [blame]	6348	<address>
				6349	<a href="http://jigsaw.w3.org/css-validator/check/referer"><img
				6350	src="http://jigsaw.w3.org/css-validator/images/vcss" alt="Valid CSS!"></a>
				6351	<a href="http://validator.w3.org/check/referer"><img
Chris Lattner	c7d3ab3	2008-01-04 04:33:49 +0000	[diff] [blame]	6352	src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!"></a>
Misha Brukman	daa4cb0	2004-03-01 17:47:27 +0000	[diff] [blame]	6353
				6354	<a href="mailto:sabre@nondot.org">Chris Lattner</a><br>
Reid Spencer	05fe4b0	2006-03-14 05:39:39 +0000	[diff] [blame]	6355	<a href="http://llvm.org">The LLVM Compiler Infrastructure</a><br>
Misha Brukman	daa4cb0	2004-03-01 17:47:27 +0000	[diff] [blame]	6356	Last modified: $Date$
				6357	</address>
Chris Lattner	c7d3ab3	2008-01-04 04:33:49 +0000	[diff] [blame]	6358
Misha Brukman	9d0919f	2003-11-08 01:05:38 +0000	[diff] [blame]	6359	</body>
				6360	</html>