diff options
| author | Chris Lattner <sabre@nondot.org> | 2004-07-01 20:41:43 +0000 |
|---|---|---|
| committer | Chris Lattner <sabre@nondot.org> | 2004-07-01 20:41:43 +0000 |
| commit | 80b3aeafc06f3ceff687746f009ebdfc3c8f88b0 (patch) | |
| tree | 7e408f4edb0cfaa9af37d3af4bf89b75d62c2cef /llvm/docs/Bugpoint.html | |
| parent | d4ba0a5721416ec71c42b3d51ad8606b29899a01 (diff) | |
| download | bcm5719-llvm-80b3aeafc06f3ceff687746f009ebdfc3c8f88b0.tar.gz bcm5719-llvm-80b3aeafc06f3ceff687746f009ebdfc3c8f88b0.zip | |
Fix broken links
llvm-svn: 14548
Diffstat (limited to 'llvm/docs/Bugpoint.html')
| -rw-r--r-- | llvm/docs/Bugpoint.html | 12 |
1 files changed, 4 insertions, 8 deletions
diff --git a/llvm/docs/Bugpoint.html b/llvm/docs/Bugpoint.html index 519e02d5277..0fc16b710aa 100644 --- a/llvm/docs/Bugpoint.html +++ b/llvm/docs/Bugpoint.html @@ -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 @@ problems in LLVM tools and passes. It can be used to debug three types of 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 @@ flow graph, to reduce the size of the function as much as possible. Finally, <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 @@ non-obvious ways. Here are some hints and tips:<p> 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> |
