diff options
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/CodeGenerator.html | 7 | ||||
| -rw-r--r-- | docs/LangRef.html | 110 | ||||
| -rw-r--r-- | docs/ProgrammersManual.html | 24 | ||||
| -rw-r--r-- | docs/ReleaseNotes.html | 3 | ||||
| -rw-r--r-- | docs/SourceLevelDebugging.html | 22 | ||||
| -rw-r--r-- | docs/TableGenFundamentals.html | 6 |
6 files changed, 134 insertions, 38 deletions
diff --git a/docs/CodeGenerator.html b/docs/CodeGenerator.html index d39de19..2eb7abc 100644 --- a/docs/CodeGenerator.html +++ b/docs/CodeGenerator.html @@ -1731,11 +1731,6 @@ define fastcc i32 @tailcaller(i32 %in1, i32 %in2) { (because one or more of above constraints are not met) to be followed by a readjustment of the stack. So performance might be worse in such cases.</p> -<p>On x86 and x86-64 one register is reserved for indirect tail calls (e.g via a - function pointer). So there is one less register for integer argument - passing. For x86 this means 2 registers (if <tt>inreg</tt> parameter - attribute is used) and for x86-64 this means 5 register are used.</p> - </div> <!-- ======================================================================= --> <div class="doc_subsection"> @@ -2121,7 +2116,7 @@ MOVSX32rm16 -> movsx, 32-bit register, 16-bit memory <a href="mailto:sabre@nondot.org">Chris Lattner</a><br> <a href="http://llvm.org">The LLVM Compiler Infrastructure</a><br> - Last modified: $Date: 2009-10-10 23:30:55 +0200 (Sat, 10 Oct 2009) $ + Last modified: $Date: 2010-01-11 19:53:47 +0100 (Mon, 11 Jan 2010) $ </address> </body> diff --git a/docs/LangRef.html b/docs/LangRef.html index ba09f4c..6ea0ead 100644 --- a/docs/LangRef.html +++ b/docs/LangRef.html @@ -43,6 +43,7 @@ <li><a href="#globalvars">Global Variables</a></li> <li><a href="#functionstructure">Functions</a></li> <li><a href="#aliasstructure">Aliases</a></li> + <li><a href="#namedmetadatastructure">Named Metadata</a></li> <li><a href="#paramattrs">Parameter Attributes</a></li> <li><a href="#fnattrs">Function Attributes</a></li> <li><a href="#gc">Garbage Collector Names</a></li> @@ -85,12 +86,12 @@ <li><a href="#undefvalues">Undefined Values</a></li> <li><a href="#blockaddress">Addresses of Basic Blocks</a></li> <li><a href="#constantexprs">Constant Expressions</a></li> - <li><a href="#metadata">Embedded Metadata</a></li> </ol> </li> <li><a href="#othervalues">Other Values</a> <ol> <li><a href="#inlineasm">Inline Assembler Expressions</a></li> + <li><a href="#metadata">Metadata Nodes and Metadata Strings</a></li> </ol> </li> <li><a href="#intrinsic_globals">Intrinsic Global Variables</a> @@ -498,14 +499,19 @@ define i32 @main() { <i>; i32()* </i> <i>; Call puts function to write out the string to stdout.</i> <a href="#i_call">call</a> i32 @puts(i8 * %cast210) <i>; i32</i> - <a href="#i_ret">ret</a> i32 0<br>}<br> + <a href="#i_ret">ret</a> i32 0<br>} + +<i>; Named metadata</i> +!1 = metadata !{i32 41} +!foo = !{!1, null} </pre> </div> <p>This example is made up of a <a href="#globalvars">global variable</a> named - "<tt>.LC0</tt>", an external declaration of the "<tt>puts</tt>" function, and + "<tt>.LC0</tt>", an external declaration of the "<tt>puts</tt>" function, a <a href="#functionstructure">function definition</a> for - "<tt>main</tt>".</p> + "<tt>main</tt>" and <a href="#namedmetadatastructure">named metadata</a> + "<tt>foo"</tt>.</p> <p>In general, a module is made up of a list of global values, where both functions and global variables are global values. Global values are @@ -558,10 +564,17 @@ define i32 @main() { <i>; i32()* </i> <dt><tt><b><a name="linkage_linkonce">linkonce</a></b></tt></dt> <dd>Globals with "<tt>linkonce</tt>" linkage are merged with other globals of - the same name when linkage occurs. This is typically used to implement - inline functions, templates, or other code which must be generated in each - translation unit that uses it. Unreferenced <tt>linkonce</tt> globals are - allowed to be discarded.</dd> + the same name when linkage occurs. This can be used to implement + some forms of inline functions, templates, or other code which must be + generated in each translation unit that uses it, but where the body may + be overridden with a more definitive definition later. Unreferenced + <tt>linkonce</tt> globals are allowed to be discarded. Note that + <tt>linkonce</tt> linkage does not actually allow the optimizer to + inline the body of this function into callers because it doesn't know if + this definition of the function is the definitive definition within the + program or whether it will be overridden by a stronger definition. + To enable inlining and other optimizations, use "<tt>linkonce_odr</tt>" + linkage.</dd> <dt><tt><b><a name="linkage_weak">weak</a></b></tt></dt> <dd>"<tt>weak</tt>" linkage has the same merging semantics as @@ -671,9 +684,9 @@ define i32 @main() { <i>; i32()* </i> (e.g. by passing things in registers). This calling convention allows the target to use whatever tricks it wants to produce fast code for the target, without having to conform to an externally specified ABI - (Application Binary Interface). Implementations of this convention should - allow arbitrary <a href="CodeGenerator.html#tailcallopt">tail call - optimization</a> to be supported. This calling convention does not + (Application Binary Interface). + <a href="CodeGenerator.html#tailcallopt">Tail calls can only be optimized + when this convention is used.</a> This calling convention does not support varargs and requires the prototype of all callees to exactly match the prototype of the function definition.</dd> @@ -905,6 +918,27 @@ define [<a href="#linkage">linkage</a>] [<a href="#visibility">visibility</a>] </div> <!-- ======================================================================= --> +<div class="doc_subsection"> + <a name="namedmetadatastructure">Named Metadata</a> +</div> + +<div class="doc_text"> + +<p>Named metadata is a collection of metadata. <a href="#metadata"> Metadata </a> + node and null are the only valid named metadata operands. + Metadata strings are not allowed as an named metadata operand.</p> + +<h5>Syntax:</h5> +<div class="doc_code"> +<pre> +!1 = metadata !{metadata !"one"} +!name = !{null, !1} +</pre> +</div> + +</div> + +<!-- ======================================================================= --> <div class="doc_subsection"><a name="paramattrs">Parameter Attributes</a></div> <div class="doc_text"> @@ -1649,10 +1683,12 @@ Classifications</a> </div> underlying processor. The elements of a structure may be any type that has a size.</p> -<p>Structures are accessed using '<tt><a href="#i_load">load</a></tt> and - '<tt><a href="#i_store">store</a></tt>' by getting a pointer to a field with - the '<tt><a href="#i_getelementptr">getelementptr</a></tt>' instruction.</p> - +<p>Structures in memory are accessed using '<tt><a href="#i_load">load</a></tt>' + and '<tt><a href="#i_store">store</a></tt>' by getting a pointer to a field + with the '<tt><a href="#i_getelementptr">getelementptr</a></tt>' instruction. + Structures in registers are accessed using the + '<tt><a href="#i_extractvalue">extractvalue</a></tt>' and + '<tt><a href="#i_insertvalue">insertvalue</a></tt>' instructions.</p> <h5>Syntax:</h5> <pre> { <type list> } @@ -2305,12 +2341,12 @@ has undefined behavior.</p> </div> <!-- ======================================================================= --> -<div class="doc_subsection"><a name="metadata">Embedded Metadata</a> +<div class="doc_subsection"><a name="metadata">Metadata Nodes and Metadata Strings</a> </div> <div class="doc_text"> -<p>Embedded metadata provides a way to attach arbitrary data to the instruction +<p>Metadata provides a way to attach arbitrary data to the instruction stream without affecting the behaviour of the program. There are two metadata primitives, strings and nodes. All metadata has the <tt>metadata</tt> type and is identified in syntax by a preceding exclamation @@ -2329,6 +2365,9 @@ has undefined behavior.</p> event that a value is deleted, it will be replaced with a typeless "<tt>null</tt>", such as "<tt>metadata !{null, i32 10}</tt>".</p> +<p>A <a href="#namedmetadatastructure">named metadata</a> is a collection of + metadata nodes. For example: "<tt>!foo = metadata !{!4, !3}</tt>". + <p>Optimizations may rely on metadata to provide additional information about the program that isn't available in the instructions, or that isn't easily computable. Similarly, the code generator may expect a certain metadata @@ -3848,7 +3887,7 @@ Instruction</a> </div> <h5>Syntax:</h5> <pre> - <result> = insertvalue <aggregate type> <val>, <ty> <val>, <idx> <i>; yields <n x <ty>></i> + <result> = insertvalue <aggregate type> <val>, <ty> <elt>, <idx> <i>; yields <aggregate type></i> </pre> <h5>Overview:</h5> @@ -3873,7 +3912,8 @@ Instruction</a> </div> <h5>Example:</h5> <pre> - <result> = insertvalue {i32, float} %agg, i32 1, 0 <i>; yields {i32, float}</i> + %agg1 = insertvalue {i32, float} undef, i32 1, 0 <i>; yields {i32 1, float undef}</i> + %agg2 = insertvalue {i32, float} %agg1, float %val, 1 <i>; yields {i32 1, float %val}</i> </pre> </div> @@ -4983,15 +5023,31 @@ Loop: ; Infinite loop that counts from 0 on up... <p>This instruction requires several arguments:</p> <ol> - <li>The optional "tail" marker indicates whether the callee function accesses - any allocas or varargs in the caller. If the "tail" marker is present, - the function call is eligible for tail call optimization. Note that calls - may be marked "tail" even if they do not occur before - a <a href="#i_ret"><tt>ret</tt></a> instruction.</li> + <li>The optional "tail" marker indicates that the callee function does not + access any allocas or varargs in the caller. Note that calls may be + marked "tail" even if they do not occur before + a <a href="#i_ret"><tt>ret</tt></a> instruction. If the "tail" marker is + present, the function call is eligible for tail call optimization, + but <a href="CodeGenerator.html#tailcallopt">might not in fact be + optimized into a jump</a>. As of this writing, the extra requirements for + a call to actually be optimized are: + <ul> + <li>Caller and callee both have the calling + convention <tt>fastcc</tt>.</li> + <li>The call is in tail position (ret immediately follows call and ret + uses value of call or is void).</li> + <li>Option <tt>-tailcallopt</tt> is enabled, + or <code>llvm::PerformTailCallOpt</code> is <code>true</code>.</li> + <li><a href="CodeGenerator.html#tailcallopt">Platform specific + constraints are met.</a></li> + </ul> + </li> <li>The optional "cconv" marker indicates which <a href="#callingconv">calling convention</a> the call should use. If none is specified, the call - defaults to using C calling conventions.</li> + defaults to using C calling conventions. The calling convention of the + call must match the calling convention of the target function, or else the + behavior is undefined.</li> <li>The optional <a href="#paramattrs">Parameter Attributes</a> list for return values. Only '<tt>zeroext</tt>', '<tt>signext</tt>', and @@ -7263,7 +7319,7 @@ LLVM</a>.</p> <h5>Overview:</h5> <p>The <tt>llvm.objectsize</tt> intrinsic is designed to provide information - to the optimizers to either discover at compile time either a) when an + to the optimizers to discover at compile time either a) when an operation like memcpy will either overflow a buffer that corresponds to an object, or b) to determine that a runtime check for overflow isn't necessary. An object in this context means an allocation of a @@ -7294,7 +7350,7 @@ LLVM</a>.</p> <a href="mailto:sabre@nondot.org">Chris Lattner</a><br> <a href="http://llvm.org">The LLVM Compiler Infrastructure</a><br> - Last modified: $Date: 2009-12-23 01:29:49 +0100 (Wed, 23 Dec 2009) $ + Last modified: $Date: 2010-01-11 20:35:55 +0100 (Mon, 11 Jan 2010) $ </address> </body> diff --git a/docs/ProgrammersManual.html b/docs/ProgrammersManual.html index c5451b6..80a5db0 100644 --- a/docs/ProgrammersManual.html +++ b/docs/ProgrammersManual.html @@ -94,6 +94,7 @@ option</a></li> <li><a href="#ds_bit">BitVector-like containers</a> <ul> <li><a href="#dss_bitvector">A dense bitvector</a></li> + <li><a href="#dss_smallbitvector">A "small" dense bitvector</a></li> <li><a href="#dss_sparsebitvector">A sparse bitvector</a></li> </ul></li> </ul> @@ -1584,7 +1585,7 @@ please don't use it.</p> </div> <div class="doc_text"> -<p> The BitVector container provides a fixed size set of bits for manipulation. +<p> The BitVector container provides a dynamic size set of bits for manipulation. It supports individual bit setting/testing, as well as set operations. The set operations take time O(size of bitvector), but operations are performed one word at a time, instead of one bit at a time. This makes the BitVector very fast for @@ -1595,6 +1596,25 @@ the number of set bits to be high (IE a dense set). <!-- _______________________________________________________________________ --> <div class="doc_subsubsection"> + <a name="dss_smallbitvector">SmallBitVector</a> +</div> + +<div class="doc_text"> +<p> The SmallBitVector container provides the same interface as BitVector, but +it is optimized for the case where only a small number of bits, less than +25 or so, are needed. It also transparently supports larger bit counts, but +slightly less efficiently than a plain BitVector, so SmallBitVector should +only be used when larger counts are rare. +</p> + +<p> +At this time, SmallBitVector does not support set operations (and, or, xor), +and its operator[] does not provide an assignable lvalue. +</p> +</div> + +<!-- _______________________________________________________________________ --> +<div class="doc_subsubsection"> <a name="dss_sparsebitvector">SparseBitVector</a> </div> @@ -3872,7 +3892,7 @@ arguments. An argument has a pointer to the parent Function.</p> <a href="mailto:dhurjati@cs.uiuc.edu">Dinakar Dhurjati</a> and <a href="mailto:sabre@nondot.org">Chris Lattner</a><br> <a href="http://llvm.org">The LLVM Compiler Infrastructure</a><br> - Last modified: $Date: 2009-10-23 00:11:22 +0200 (Fri, 23 Oct 2009) $ + Last modified: $Date: 2010-01-05 19:24:00 +0100 (Tue, 05 Jan 2010) $ </address> </body> diff --git a/docs/ReleaseNotes.html b/docs/ReleaseNotes.html index 5a0936f..aff0836 100644 --- a/docs/ReleaseNotes.html +++ b/docs/ReleaseNotes.html @@ -58,6 +58,7 @@ Almost dead code. include/llvm/Analysis/LiveValues.h => Dan lib/Transforms/IPO/MergeFunctions.cpp => consider for 2.8. llvm/Analysis/PointerTracking.h => Edwin wants this, consider for 2.8. + ABCD, SCCVN, GEPSplitterPass --> @@ -1348,7 +1349,7 @@ lists</a>.</p> src="http://www.w3.org/Icons/valid-html401-blue" alt="Valid HTML 4.01"></a> <a href="http://llvm.org/">LLVM Compiler Infrastructure</a><br> - Last modified: $Date: 2009-11-03 22:50:09 +0100 (Tue, 03 Nov 2009) $ + Last modified: $Date: 2010-01-09 23:30:40 +0100 (Sat, 09 Jan 2010) $ </address> </body> diff --git a/docs/SourceLevelDebugging.html b/docs/SourceLevelDebugging.html index 4aca52c..83c979b 100644 --- a/docs/SourceLevelDebugging.html +++ b/docs/SourceLevelDebugging.html @@ -38,6 +38,7 @@ <li><a href="#format_common_intrinsics">Debugger intrinsic functions</a> <ul> <li><a href="#format_common_declare">llvm.dbg.declare</a></li> + <li><a href="#format_common_value">llvm.dbg.value</a></li> </ul></li> </ol></li> <li><a href="#format_common_lifetime">Object lifetimes and scoping</a></li> @@ -775,6 +776,25 @@ DW_TAG_return_variable = 258 </div> <!-- ======================================================================= --> +<div class="doc_subsubsection"> + <a name="format_common_value">llvm.dbg.value</a> +</div> + +<div class="doc_text"> +<pre> + void %<a href="#format_common_value">llvm.dbg.value</a>( metadata, i64, metadata ) +</pre> + +<p>This intrinsic provides information when a user source variable is set to a + new value. The first argument is the new value (wrapped as metadata). The + second argument is the offset in the user source variable where the new value + is written. The third argument is + the <tt>%<a href="#format_variables">llvm.dbg.variable</a></tt> containing + the description of the user source variable. </p> + +</div> + +<!-- ======================================================================= --> <div class="doc_subsection"> <a name="format_common_lifetime">Object lifetimes and scoping</a> </div> @@ -1718,7 +1738,7 @@ enum Trees { <a href="mailto:sabre@nondot.org">Chris Lattner</a><br> <a href="http://llvm.org">LLVM Compiler Infrastructure</a><br> - Last modified: $Date: 2009-12-01 01:59:58 +0100 (Tue, 01 Dec 2009) $ + Last modified: $Date: 2010-01-11 23:53:48 +0100 (Mon, 11 Jan 2010) $ </address> </body> diff --git a/docs/TableGenFundamentals.html b/docs/TableGenFundamentals.html index 4ae6718..b96aeab 100644 --- a/docs/TableGenFundamentals.html +++ b/docs/TableGenFundamentals.html @@ -423,6 +423,10 @@ class. This operation is analogous to $(foreach) in GNU make.</dd> <dd>An integer {0,1} indicating whether list 'a' is empty.</dd> <dt><tt>!if(a,b,c)</tt></dt> <dd>'b' if the result of integer operator 'a' is nonzero, 'c' otherwise.</dd> +<dt><tt>!eq(a,b)</tt></dt> + <dd>Integer one if string a is equal to string b, zero otherwise. This + only operates on string objects. Use !cast<string> to compare other + types of objects.</dd> </dl> <p>Note that all of the values have rules specifying how they convert to values @@ -794,7 +798,7 @@ This should highlight the APIs in <tt>TableGen/Record.h</tt>.</p> <a href="mailto:sabre@nondot.org">Chris Lattner</a><br> <a href="http://llvm.org">LLVM Compiler Infrastructure</a><br> - Last modified: $Date: 2009-10-29 19:10:34 +0100 (Thu, 29 Oct 2009) $ + Last modified: $Date: 2010-01-05 20:11:42 +0100 (Tue, 05 Jan 2010) $ </address> </body> |
