[llvm-commits] CVS: llvm/docs/Bugpoint.html

[Chris Lattner]

Changes in directory llvm/docs:

Bugpoint.html updated: 1.1 -> 1.2

---
Log message:

Fix broken links


---
Diffs of the changes:  (+4 -8)

Index: llvm/docs/Bugpoint.html
diff -u llvm/docs/Bugpoint.html:1.1 llvm/docs/Bugpoint.html:1.2
--- llvm/docs/Bugpoint.html:1.1	Thu Jul  1 15:10:40 2004
+++ llvm/docs/Bugpoint.html	Thu Jul  1 15:41:43 2004
@@ -12,7 +12,7 @@
 <h3>SYNOPSIS</h3>
 <tt>bugpoint [options] [input LLVM ll/bc files] [LLVM passes] --args <program arguments>...</tt>
 
-<img src="../img/Debugging.gif" width=444 height=314 align=right>
+<img src="img/Debugging.gif" width=444 height=314 align=right>
 <h3>DESCRIPTION</h3>
 
 The <tt>bugpoint</tt> tool narrows down the source of
@@ -20,7 +20,7 @@
 failures: optimizer crashes, miscompilations by optimizers, or bad native
 code generation (including problems in the static and JIT compilers).  It aims 
 to reduce large test cases to small, useful ones.  For example,
-if <tt><a href="gccas.html">gccas</a></tt> crashes while optimizing a file, it
+if <tt><a href="CommandGuide/gccas.html">gccas</a></tt> crashes while optimizing a file, it
 will identify the optimization (or combination of optimizations) that causes the
 crash, and reduce the file down to a small example which triggers the crash.<p>
 
@@ -84,8 +84,8 @@
 <tt>bugpoint</tt> deletes any individual LLVM instructions whose absence does
 not eliminate the failure.  At the end, <tt>bugpoint</tt> should tell you what
 passes crash, give you a bytecode file, and give you instructions on how to
-reproduce the failure with <tt><a href="opt.html">opt</a></tt>, <tt><a
-href="analyze.html">analyze</a></tt>, or <tt><a href="llc.html">llc</a></tt>.<p>
+reproduce the failure with <tt><a href="CommandGuide/opt.html">opt</a></tt>, <tt><a
+href="CommandGuide/analyze.html">analyze</a></tt>, or <tt><a href="CommandGuide/llc.html">llc</a></tt>.<p>
 
 <a name="codegendebug">
 <h4>Code generator debugger</h4>
@@ -239,10 +239,6 @@
 If <tt>bugpoint</tt> succeeds in finding a problem, it will exit with 0.
 Otherwise, if an error occurs, it will exit with a non-zero value.
 
-<h3>SEE ALSO</h3>
-<a href="opt.html"><tt>opt</tt></a>,
-<a href="analyze.html"><tt>analyze</tt></a>
-
 <HR>
 Maintained by the <a href="http://llvm.cs.uiuc.edu">LLVM Team</a>.
 </body>