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

Chris Lattner lattner at cs.uiuc.edu
Fri Oct 15 10:05:57 PDT 2004



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

Bugpoint.html updated: 1.1 -> 1.2
---
Log message:

Fix broken links


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

Index: llvm-www/releases/1.3/docs/Bugpoint.html
diff -u llvm-www/releases/1.3/docs/Bugpoint.html:1.1 llvm-www/releases/1.3/docs/Bugpoint.html:1.2
--- llvm-www/releases/1.3/docs/Bugpoint.html:1.1	Fri Aug 13 17:03:03 2004
+++ llvm-www/releases/1.3/docs/Bugpoint.html	Fri Oct 15 12:05:47 2004
@@ -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="CommandGuide/gccas.html">gccas</a></tt> crashes while optimizing a file, it
+if <tt><a href="CommandGuide/html/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="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>
+reproduce the failure with <tt><a href="CommandGuide/html/opt.html">opt</a></tt>, <tt><a
+href="CommandGuide/html/analyze.html">analyze</a></tt>, or <tt><a href="CommandGuide/html/llc.html">llc</a></tt>.<p>
 
 <a name="codegendebug">
 <h4>Code generator debugger</h4>






More information about the llvm-commits mailing list