[llvm-commits] CVS: llvm-www/releases/1.0/docs/CodingStandards.html GettingStarted.html LangRef.html

[Tanya Brethour]

Changes in directory llvm-www/releases/1.0/docs:

CodingStandards.html updated: 1.1 -> 1.2
GettingStarted.html updated: 1.2 -> 1.3
LangRef.html updated: 1.1 -> 1.2

---
Log message:

Fixing broken links.


---
Diffs of the changes:  (+9 -9)

Index: llvm-www/releases/1.0/docs/CodingStandards.html
diff -u llvm-www/releases/1.0/docs/CodingStandards.html:1.1 llvm-www/releases/1.0/docs/CodingStandards.html:1.2
--- llvm-www/releases/1.0/docs/CodingStandards.html:1.1	Fri Oct 24 15:51:39 2003
+++ llvm-www/releases/1.0/docs/CodingStandards.html	Mon Jun 21 22:34:48 2004
@@ -168,7 +168,7 @@
 
 Immediately after the <a href="#scf_commenting">header file comment</a> (and
 include guards if working on a header file), the <a
-href="hl_dontinclude">minimal</a> list of #includes required by the file should
+href="#hl_dontinclude">minimal</a> list of #includes required by the file should
 be listed.  We prefer these #includes to be listed in this order:<p>
 
 <ol>


Index: llvm-www/releases/1.0/docs/GettingStarted.html
diff -u llvm-www/releases/1.0/docs/GettingStarted.html:1.2 llvm-www/releases/1.0/docs/GettingStarted.html:1.3
--- llvm-www/releases/1.0/docs/GettingStarted.html:1.2	Thu Nov  6 14:52:02 2003
+++ llvm-www/releases/1.0/docs/GettingStarted.html	Mon Jun 21 22:34:48 2004
@@ -156,7 +156,7 @@
     </ol>
 
     <p>
-    Consult the <a href="starting">Getting Started with LLVM</a> section for
+    Consult the <a href="#starting">Getting Started with LLVM</a> section for
     detailed information on configuring and compiling LLVM.  See
     <a href="#environment">Setting Up Your Environment</a> for tips that
     simplify working with the GCC front end and LLVM tools.  Go to


Index: llvm-www/releases/1.0/docs/LangRef.html
diff -u llvm-www/releases/1.0/docs/LangRef.html:1.1 llvm-www/releases/1.0/docs/LangRef.html:1.2
--- llvm-www/releases/1.0/docs/LangRef.html:1.1	Fri Oct 24 15:51:39 2003
+++ llvm-www/releases/1.0/docs/LangRef.html	Mon Jun 21 22:34:48 2004
@@ -432,7 +432,7 @@
 
 <tr><td><tt>{ float, int (int) * }</tt></td><td>: A pair, where the first
 element is a <tt>float</tt> and the second element is a <a
-href="#t_pointer">pointer</a> to a <a href="t_function">function</a> that takes
+href="#t_pointer">pointer</a> to a <a href="#t_function">function</a> that takes
 an <tt>int</tt>, returning an <tt>int</tt>.</td></tr>
 
 </table>
@@ -459,7 +459,7 @@
 href="#t_array">array</a> of four <tt>int</tt> values</td></tr>
 
 <tr><td><tt>int (int *) *</tt></td><td>: A <a href="#t_pointer">pointer</a> to a
-<a href="t_function">function</a> that takes an <tt>int</tt>, returning an
+<a href="#t_function">function</a> that takes an <tt>int</tt>, returning an
 <tt>int</tt>.</td></tr>
 
 </table>
@@ -1423,7 +1423,7 @@
 <h5>Arguments:</h5>
 
 The argument to the '<tt>load</tt>' instruction specifies the memory address to
-load from.  The pointer must point to a <a href="t_firstclass">first class</a>
+load from.  The pointer must point to a <a href="#t_firstclass">first class</a>
 type.  If the <tt>load</tt> is marked as <tt>volatile</tt> then the optimizer is
 not allowed to modify the number or order of execution of this <tt>load</tt>
 with other volatile <tt>load</tt> and <tt><a href="#i_store">store</a></tt>
@@ -1535,9 +1535,9 @@
 <h5>Semantics:</h5>
 
 The index types specified for the '<tt>getelementptr</tt>' instruction depend on
-the pointer type that is being index into.  <a href="t_pointer">Pointer</a> and
-<a href="t_array">array</a> types require '<tt>long</tt>' values, and <a
-href="t_struct">structure</a> types require '<tt>ubyte</tt>'
+the pointer type that is being index into.  <a href="#t_pointer">Pointer</a> and
+<a href="#t_array">array</a> types require '<tt>long</tt>' values, and <a
+href="#t_struct">structure</a> types require '<tt>ubyte</tt>'
 <b>constants</b>.<p>
 
 In the example above, the first index is indexing into the '<tt>%ST*</tt>' type,
@@ -1935,7 +1935,7 @@
 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 returned list.  This intrinsic is necessary
-because the <tt><a href="i_va_start">llvm.va_start</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>