Changes in directory llvm/docs:

AliasAnalysis.html updated: 1.27 -> 1.28
DeveloperPolicy.html updated: 1.37 -> 1.38
ExceptionHandling.html updated: 1.1 -> 1.2
GarbageCollection.html updated: 1.8 -> 1.9
LangRef.html updated: 1.217 -> 1.218
ProgrammersManual.html updated: 1.130 -> 1.131
SystemLibrary.html updated: 1.10 -> 1.11
---
Log message:

Various hopefully correct easy fixes.


---
Diffs of the changes:  (+26 -27)

 AliasAnalysis.html     |    4 ++--
 DeveloperPolicy.html   |    4 ++--
 ExceptionHandling.html |    8 ++++----
 GarbageCollection.html |    4 ++--
 LangRef.html           |   21 ++++++++++-----------
 ProgrammersManual.html |    8 ++++----
 SystemLibrary.html     |    4 ++--
 7 files changed, 26 insertions(+), 27 deletions(-)


Index: llvm/docs/AliasAnalysis.html
diff -u llvm/docs/AliasAnalysis.html:1.27 llvm/docs/AliasAnalysis.html:1.28
--- llvm/docs/AliasAnalysis.html:1.27   Mon Mar 13 23:39:39 2006
+++ llvm/docs/AliasAnalysis.html        Fri Mar 30 07:22:09 2007
@@ -70,7 +70,7 @@
 different ways of classifying them: flow-sensitive vs flow-insensitive,
 context-sensitive vs context-insensitive, field-sensitive vs field-insensitive,
 unification-based vs subset-based, etc.  Traditionally, alias analyses respond
-to a query with a <a href="#MustNoMay">Must, May, or No</a> alias response,
+to a query with a <a href="#MustMayNo">Must, May, or No</a> alias response,
 indicating that two pointers always point to the same object, might point to 
the
 same object, or are known to never point to the same object.</p>
 
@@ -952,7 +952,7 @@
 
   <a href="mailto:[EMAIL PROTECTED]">Chris Lattner</a><br>
   <a href="http://llvm.org";>LLVM Compiler Infrastructure</a><br>
-  Last modified: $Date: 2006/03/14 05:39:39 $
+  Last modified: $Date: 2007/03/30 12:22:09 $
 </address>
 
 </body>


Index: llvm/docs/DeveloperPolicy.html
diff -u llvm/docs/DeveloperPolicy.html:1.37 llvm/docs/DeveloperPolicy.html:1.38
--- llvm/docs/DeveloperPolicy.html:1.37 Thu Mar  1 20:57:34 2007
+++ llvm/docs/DeveloperPolicy.html      Fri Mar 30 07:22:09 2007
@@ -162,7 +162,7 @@
     bug being fixed or feature being implemented is in the llvm-gcc C++
     front-end, in which case it must be written in C++).</li>
     <li>Test cases, especially for regressions, should be reduced as much as 
-    possible, by <a href="CommandGuide/html/bugpoint.html">bugpoint</a> or
+    possible, by <a href="Bugpoint.html">bugpoint</a> or
     manually. It is unacceptable 
     to place an entire failing program into <tt>llvm/test</tt> as this creates
     a <i>time-to-test</i> burden on all developers. Please keep them 
short.</li>
@@ -499,7 +499,7 @@
   Written by the 
   <a href="mailto:[EMAIL PROTECTED]">LLVM Oversight Group</a><br>
   <a href="http://llvm.org";>The LLVM Compiler Infrastructure</a><br>
-  Last modified: $Date: 2007/03/02 02:57:34 $
+  Last modified: $Date: 2007/03/30 12:22:09 $
 </address>
 </body>
 </html>


Index: llvm/docs/ExceptionHandling.html
diff -u llvm/docs/ExceptionHandling.html:1.1 
llvm/docs/ExceptionHandling.html:1.2
--- llvm/docs/ExceptionHandling.html:1.1        Wed Mar 14 14:29:42 2007
+++ llvm/docs/ExceptionHandling.html    Fri Mar 30 07:22:09 2007
@@ -22,10 +22,10 @@
   <ol>
     <li><a href="#throw">Throw</a></li>
     <li><a href="#try_catch">Try/Catch</a></li>
-    <li><a href="#finally">Finallys</a></li>
+    <li><a href="#finallys">Finallys</a></li>
     <li><a href="#throw_filters">Throw Filters</a></li>
   </ol></li>
-  <li><a href="#intrinsics">Exception Handling Intrinsics</a>
+  <li><a href="#format_common_intrinsics">Exception Handling Intrinsics</a>
   <ol>
        <li><a href="#llvm_eh_exception"><tt>llvm.eh.exception</tt></a></li>
        <li><a href="#llvm_eh_selector"><tt>llvm.eh.selector</tt></a></li>
@@ -281,7 +281,7 @@
 
 <!-- ======================================================================= 
-->
 <div class="doc_section">
-  <a name="intrinsics">Exception Handling Intrinsics</a>
+  <a name="format_common_intrinsics">Exception Handling Intrinsics</a>
 </div>
 
 <div class="doc_text">
@@ -453,7 +453,7 @@
 
   <a href="mailto:[EMAIL PROTECTED]">Chris Lattner</a><br>
   <a href="http://llvm.org";>LLVM Compiler Infrastructure</a><br>
-  Last modified: $Date: 2007/03/14 19:29:42 $
+  Last modified: $Date: 2007/03/30 12:22:09 $
 </address>
 
 </body>


Index: llvm/docs/GarbageCollection.html
diff -u llvm/docs/GarbageCollection.html:1.8 
llvm/docs/GarbageCollection.html:1.9
--- llvm/docs/GarbageCollection.html:1.8        Mon Mar 13 23:39:39 2006
+++ llvm/docs/GarbageCollection.html    Fri Mar 30 07:22:09 2007
@@ -387,7 +387,7 @@
 generator that iterates through all of the GC roots on the stack, calling the
 specified function pointer with each record.  For each GC root, the address of
 the pointer and the meta-data (from the <a
-href="#gcroot"><tt>llvm.gcroot</tt></a> intrinsic) are provided.
+href="#roots"><tt>llvm.gcroot</tt></a> intrinsic) are provided.
 </p>
 </div>
 
@@ -526,7 +526,7 @@
 
   <a href="mailto:[EMAIL PROTECTED]">Chris Lattner</a><br>
   <a href="http://llvm.org";>LLVM Compiler Infrastructure</a><br>
-  Last modified: $Date: 2006/03/14 05:39:39 $
+  Last modified: $Date: 2007/03/30 12:22:09 $
 </address>
 
 </body>


Index: llvm/docs/LangRef.html
diff -u llvm/docs/LangRef.html:1.217 llvm/docs/LangRef.html:1.218
--- llvm/docs/LangRef.html:1.217        Tue Mar 27 21:46:29 2007
+++ llvm/docs/LangRef.html      Fri Mar 30 07:22:09 2007
@@ -27,7 +27,6 @@
       <li><a href="#paramattrs">Parameter Attributes</a></li>
       <li><a href="#moduleasm">Module-Level Inline Assembly</a></li>
       <li><a href="#datalayout">Data Layout</a></li>
-      <li><a href="#checkpoint">Check Points</a></li>
     </ol>
   </li>
   <li><a href="#typesystem">Type System</a>
@@ -886,7 +885,7 @@
       <table>
         <tbody>
         <tr><th>Type</th><th>Description</th></tr>
-        <tr><td><tt>void</tt></td><td>No value</td></tr>
+        <tr><td><tt><a name="t_void">void</a></tt></td><td>No value</td></tr>
         <tr><td><tt>i8</tt></td><td>8-bit value</td></tr>
         <tr><td><tt>i32</tt></td><td>32-bit value</td></tr>
         <tr><td><tt>float</tt></td><td>32-bit floating point value</td></tr>
@@ -1714,7 +1713,7 @@
 
 <ol>
   <li>
-    The optional "cconv" marker indicates which <a href="callingconv">calling
+    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>
@@ -2966,8 +2965,8 @@
 
 <h5>Semantics:</h5>
 <p>The '<tt>fpext</tt>' instruction extends the <tt>value</tt> from a smaller
-<a href="t_floating">floating point</a> type to a larger 
-<a href="t_floating">floating point</a> type. The <tt>fpext</tt> cannot be 
+<a href="#t_floating">floating point</a> type to a larger 
+<a href="#t_floating">floating point</a> type. The <tt>fpext</tt> cannot be 
 used to make a <i>no-op cast</i> because it always changes bits. Use 
 <tt>bitcast</tt> to make a <i>no-op cast</i> for a floating point cast.</p>
 
@@ -3140,7 +3139,7 @@
 
 <h5>Arguments:</h5>
 <p>The '<tt>ptrtoint</tt>' instruction takes a <tt>value</tt> to cast, which 
-must be a <a href="t_pointer">pointer</a> value, and a type to cast it to
+must be a <a href="#t_pointer">pointer</a> value, and a type to cast it to
 <tt>ty2</tt>, which must be an <a href="#t_integer">integer</a> type. 
 
 <h5>Semantics:</h5>
@@ -3174,7 +3173,7 @@
 a pointer type, <tt>ty2</tt>.</p>
 
 <h5>Arguments:</h5>
-<p>The '<tt>inttoptr</tt>' instruction takes an <a href="i_integer">integer</a>
+<p>The '<tt>inttoptr</tt>' instruction takes an <a 
href="#t_integer">integer</a>
 value to cast, and a type to cast it to, which must be a 
 <a href="#t_pointer">pointer</a> type.
 
@@ -3490,7 +3489,7 @@
     href="#i_ret"><tt>ret</tt></a> instruction.
   </li>
   <li>
-    <p>The optional "cconv" marker indicates which <a 
href="callingconv">calling
+    <p>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>
@@ -3747,7 +3746,7 @@
 <p>The '<tt>llvm.va_copy</tt>' intrinsic works just like the <tt>va_copy</tt> 
macro
 available in C.  In a target-dependent way, it copies the source
 <tt>va_list</tt> element into the destination list.  This intrinsic is 
necessary
-because the <tt><a href="i_va_begin">llvm.va_begin</a></tt> intrinsic may be
+because the <tt><a href="#i_va_start">llvm.va_start</a></tt> intrinsic may be
 arbitrarily complex and require memory allocation, for example.</p>
 
 </div>
@@ -4029,7 +4028,7 @@
 <p>
 The '<tt>llvm.stackrestore</tt>' intrinsic is used to restore the state of
 the function stack to the state it was in when the corresponding <a
-href="#llvm.stacksave"><tt>llvm.stacksave</tt></a> intrinsic executed.  This is
+href="#i_stacksave"><tt>llvm.stacksave</tt></a> intrinsic executed.  This is
 useful for implementing language features like scoped automatic variable sized
 arrays in C99.
 </p>
@@ -4611,7 +4610,7 @@
 
   <a href="mailto:[EMAIL PROTECTED]">Chris Lattner</a><br>
   <a href="http://llvm.org";>The LLVM Compiler Infrastructure</a><br>
-  Last modified: $Date: 2007/03/28 02:46:29 $
+  Last modified: $Date: 2007/03/30 12:22:09 $
 </address>
 </body>
 </html>


Index: llvm/docs/ProgrammersManual.html
diff -u llvm/docs/ProgrammersManual.html:1.130 
llvm/docs/ProgrammersManual.html:1.131
--- llvm/docs/ProgrammersManual.html:1.130      Wed Mar 28 13:27:57 2007
+++ llvm/docs/ProgrammersManual.html    Fri Mar 30 07:22:09 2007
@@ -2195,7 +2195,7 @@
   point type.</dd>
   <dt><tt>StructType</tt></dt>
   <dd>Subclass of DerivedTypes for struct types.</dd>
-  <dt><tt>FunctionType</tt></dt>
+  <dt><tt><a name="FunctionType">FunctionType</a></tt></dt>
   <dd>Subclass of DerivedTypes for function types.
     <ul>
       <li><tt>bool isVarArg() const</tt>: Returns true if its a vararg
@@ -2389,7 +2389,7 @@
 </pre>
 </div>
 
-<p><a name="#nameWarning">The name of this instruction is "foo".</a> 
<b>NOTE</b>
+<p><a name="nameWarning">The name of this instruction is "foo".</a> <b>NOTE</b>
 that the name of any value may be missing (an empty string), so names should
 <b>ONLY</b> be used for debugging (making the source code easier to read,
 debugging printouts), they should not be used to keep track of values or map
@@ -2805,7 +2805,7 @@
     create and what type of linkage the function should have. The <a 
     href="#FunctionType"><tt>FunctionType</tt></a> argument
     specifies the formal arguments and return value for the function. The same
-    <a href="#FunctionTypel"><tt>FunctionType</tt></a> value can be used to
+    <a href="#FunctionType"><tt>FunctionType</tt></a> value can be used to
     create multiple functions. The <tt>Parent</tt> argument specifies the 
Module
     in which the function is defined. If this argument is provided, the 
function
     will automatically be inserted into that module's list of
@@ -3060,7 +3060,7 @@
   <a href="mailto:[EMAIL PROTECTED]">Dinakar Dhurjati</a> and
   <a href="mailto:[EMAIL PROTECTED]">Chris Lattner</a><br>
   <a href="http://llvm.org";>The LLVM Compiler Infrastructure</a><br>
-  Last modified: $Date: 2007/03/28 18:27:57 $
+  Last modified: $Date: 2007/03/30 12:22:09 $
 </address>
 
 </body>


Index: llvm/docs/SystemLibrary.html
diff -u llvm/docs/SystemLibrary.html:1.10 llvm/docs/SystemLibrary.html:1.11
--- llvm/docs/SystemLibrary.html:1.10   Mon Mar 13 23:39:39 2006
+++ llvm/docs/SystemLibrary.html        Fri Mar 30 07:22:09 2007
@@ -32,7 +32,7 @@
 </ul>
 
 <div class="doc_author">
-  <p>Written by <a href="[EMAIL PROTECTED]">Reid Spencer</a></p>
+  <p>Written by <a href="mailto:[EMAIL PROTECTED]">Reid Spencer</a></p>
 </div>
 
 
@@ -338,7 +338,7 @@
 
   <a href="mailto:[EMAIL PROTECTED]">Reid Spencer</a><br>
   <a href="http://llvm.org";>LLVM Compiler Infrastructure</a><br>
-  Last modified: $Date: 2006/03/14 05:39:39 $
+  Last modified: $Date: 2007/03/30 12:22:09 $
 </address>
 </body>
 </html>



_______________________________________________
llvm-commits mailing list
llvm-commits@cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits

Reply via email to