Various hopefully correct easy fixes.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@35506 91177308-0d34-0410-b5e6-96231b3b80d8

7 files changed, 19 insertions, 20 deletions

diff --git a/docs/AliasAnalysis.html b/docs/AliasAnalysis.html
index 6356787..b1163e0 100644
--- a/docs/AliasAnalysis.html
+++ b/docs/AliasAnalysis.html
@@ -70,7 +70,7 @@ memory.  There are many different algorithms for alias analysis and many
 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>
 
diff --git a/docs/DeveloperPolicy.html b/docs/DeveloperPolicy.html
index db112af..85b8aab 100644
--- a/docs/DeveloperPolicy.html
+++ b/docs/DeveloperPolicy.html
@@ -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>
diff --git a/docs/ExceptionHandling.html b/docs/ExceptionHandling.html
index d515b4c..a0ecbfd 100644
--- a/docs/ExceptionHandling.html
+++ b/docs/ExceptionHandling.html
@@ -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 @@ exception structure.</p>
 
 <!-- ======================================================================= -->
 <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">
diff --git a/docs/GarbageCollection.html b/docs/GarbageCollection.html
index 91be239..f2f3722 100644
--- a/docs/GarbageCollection.html
+++ b/docs/GarbageCollection.html
@@ -387,7 +387,7 @@ The <tt>llvm_cg_walk_gcroots</tt> function is a function provided by the code
 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>
 
diff --git a/docs/LangRef.html b/docs/LangRef.html
index 11b43be..4342445 100644
--- a/docs/LangRef.html
+++ b/docs/LangRef.html
@@ -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 @@ system. The current set of primitive types is as follows:</p>
       <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 @@ continued at the dynamically nearest "exception" label.</p>
 
 <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 @@ type must be smaller than the destination type.</p>
 
 <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 @@ the integer type <tt>ty2</tt>.</p>
 
 <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 @@ are the same size, then nothing is done (<i>no-op cast</i>).</p>
 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 @@ value argument; otherwise, it returns the second value argument.
     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 @@ The second argument is a pointer to a <tt>va_list</tt> element to copy from.</p>
 <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 @@ that were allocated after the <tt>llvm.stacksave</tt> was executed.
 <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>
diff --git a/docs/ProgrammersManual.html b/docs/ProgrammersManual.html
index 9661b76..347861e 100644
--- a/docs/ProgrammersManual.html
+++ b/docs/ProgrammersManual.html
@@ -2195,7 +2195,7 @@ the <tt>lib/VMCore</tt> directory.</p>
   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 @@ method. In addition, all LLVM values can be named.  The "name" of the
 </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 @@ is its address (after linking) which is guaranteed to be constant.</p>
     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
diff --git a/docs/SystemLibrary.html b/docs/SystemLibrary.html
index 4dba5bc..b02c786 100644
--- a/docs/SystemLibrary.html
+++ b/docs/SystemLibrary.html
@@ -32,7 +32,7 @@
 </ul>
 
 <div class="doc_author">
-  <p>Written by <a href="rspencer@x10sys.com">Reid Spencer</a></p>
+  <p>Written by <a href="mailto:rspencer@x10sys.com">Reid Spencer</a></p>
 </div>