Changes in directory llvm/docs:
LangRef.html updated: 1.161 -> 1.162 --- Log message: Fix the section headings. --- Diffs of the changes: (+39 -30) LangRef.html | 69 +++++++++++++++++++++++++++++++++-------------------------- 1 files changed, 39 insertions(+), 30 deletions(-) Index: llvm/docs/LangRef.html diff -u llvm/docs/LangRef.html:1.161 llvm/docs/LangRef.html:1.162 --- llvm/docs/LangRef.html:1.161 Tue Nov 7 19:11:31 2006 +++ llvm/docs/LangRef.html Tue Nov 7 19:18:52 2006 @@ -115,7 +115,7 @@ <li><a href="#i_getelementptr">'<tt>getelementptr</tt>' Instruction</a></li> </ol> </li> - <li><a href="#otherops">Cast Operations</a> + <li><a href="#convertops">Conversion Operations</a> <ol> <li><a href="#i_trunc">'<tt>trunc .. to</tt>' Instruction</a></li> <li><a href="#i_zext">'<tt>zext .. to</tt>' Instruction</a></li> @@ -2763,36 +2763,12 @@ </div> <!-- ======================================================================= --> -<div class="doc_subsection"> <a name="otherops">Other Operations</a> </div> -<div class="doc_text"> -<p>The instructions in this category are the "miscellaneous" -instructions, which defy better classification.</p> +<div class="doc_subsection"> <a name="convertops">Conversion Operations</a> </div> -<!-- _______________________________________________________________________ --> -<div class="doc_subsubsection"> <a name="i_phi">'<tt>phi</tt>' -Instruction</a> </div> <div class="doc_text"> -<h5>Syntax:</h5> -<pre> <result> = phi <ty> [ <val0>, <label0>], ...<br></pre> -<h5>Overview:</h5> -<p>The '<tt>phi</tt>' instruction is used to implement the φ node in -the SSA graph representing the function.</p> -<h5>Arguments:</h5> -<p>The type of the incoming values are specified with the first type -field. After this, the '<tt>phi</tt>' instruction takes a list of pairs -as arguments, with one pair for each predecessor basic block of the -current block. Only values of <a href="#t_firstclass">first class</a> -type may be used as the value arguments to the PHI node. Only labels -may be used as the label arguments.</p> -<p>There must be no non-phi instructions between the start of a basic -block and the PHI instructions: i.e. PHI instructions must be first in -a basic block.</p> -<h5>Semantics:</h5> -<p>At runtime, the '<tt>phi</tt>' instruction logically takes on the -value specified by the parameter, depending on which basic block we -came from in the last <a href="#terminators">terminator</a> instruction.</p> -<h5>Example:</h5> -<pre>Loop: ; Infinite loop that counts from 0 on up...<br> %indvar = phi uint [ 0, %LoopHeader ], [ %nextindvar, %Loop ]<br> %nextindvar = add uint %indvar, 1<br> br label %Loop<br></pre> +<p>The instructions in this category are the conversion instructions (casting) +which all take a single operand and a type. They perform various bit conversions +on the operand.</p> </div> <!-- _______________________________________________________________________ --> @@ -3169,6 +3145,39 @@ </pre> </div> +<!-- ======================================================================= --> +<div class="doc_subsection"> <a name="otherops">Other Operations</a> </div> +<div class="doc_text"> +<p>The instructions in this category are the "miscellaneous" +instructions, which defy better classification.</p> +</div> +<!-- _______________________________________________________________________ --> +<div class="doc_subsubsection"> <a name="i_phi">'<tt>phi</tt>' +Instruction</a> </div> +<div class="doc_text"> +<h5>Syntax:</h5> +<pre> <result> = phi <ty> [ <val0>, <label0>], ...<br></pre> +<h5>Overview:</h5> +<p>The '<tt>phi</tt>' instruction is used to implement the φ node in +the SSA graph representing the function.</p> +<h5>Arguments:</h5> +<p>The type of the incoming values are specified with the first type +field. After this, the '<tt>phi</tt>' instruction takes a list of pairs +as arguments, with one pair for each predecessor basic block of the +current block. Only values of <a href="#t_firstclass">first class</a> +type may be used as the value arguments to the PHI node. Only labels +may be used as the label arguments.</p> +<p>There must be no non-phi instructions between the start of a basic +block and the PHI instructions: i.e. PHI instructions must be first in +a basic block.</p> +<h5>Semantics:</h5> +<p>At runtime, the '<tt>phi</tt>' instruction logically takes on the +value specified by the parameter, depending on which basic block we +came from in the last <a href="#terminators">terminator</a> instruction.</p> +<h5>Example:</h5> +<pre>Loop: ; Infinite loop that counts from 0 on up...<br> %indvar = phi uint [ 0, %LoopHeader ], [ %nextindvar, %Loop ]<br> %nextindvar = add uint %indvar, 1<br> br label %Loop<br></pre> +</div> + <!-- _______________________________________________________________________ --> <div class="doc_subsubsection"> <a name="i_select">'<tt>select</tt>' Instruction</a> @@ -4372,7 +4381,7 @@ <a href="mailto:[EMAIL PROTECTED]">Chris Lattner</a><br> <a href="http://llvm.org">The LLVM Compiler Infrastructure</a><br> - Last modified: $Date: 2006/11/08 01:11:31 $ + Last modified: $Date: 2006/11/08 01:18:52 $ </address> </body> </html> _______________________________________________ llvm-commits mailing list llvm-commits@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits