6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2025-08-08 19:25:47 +00:00
Code Issues Projects Releases Wiki Activity

Fix broken links

Browse Source 
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@14548 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Chris Lattner
2004-07-01 20:41:43 +00:00
parent ff0c7664a4
commit 5706f25694
1 changed files with 4 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
docs/Bugpoint.html
View File

@@ -12,7 +12,7 @@
<h3>SYNOPSIS</h3> <h3>SYNOPSIS</h3>
<tt>bugpoint [options] [input LLVM ll/bc files] [LLVM passes] --args &lt;program arguments&gt;...</tt> <tt>bugpoint [options] [input LLVM ll/bc files] [LLVM passes] --args &lt;program arguments&gt;...</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> <h3>DESCRIPTION</h3>
The <tt>bugpoint</tt> tool narrows down the source of 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 failures: optimizer crashes, miscompilations by optimizers, or bad native
code generation (including problems in the static and JIT compilers). It aims code generation (including problems in the static and JIT compilers). It aims
to reduce large test cases to small, useful ones. For example, 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 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> 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 <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 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 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 reproduce the failure with <tt><a href="CommandGuide/opt.html">opt</a></tt>, <tt><a
href="analyze.html">analyze</a></tt>, or <tt><a href="llc.html">llc</a></tt>.<p> href="CommandGuide/analyze.html">analyze</a></tt>, or <tt><a href="CommandGuide/llc.html">llc</a></tt>.<p>
<a name="codegendebug"> <a name="codegendebug">
<h4>Code generator debugger</h4> <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. 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. 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> <HR>
Maintained by the <a href="http://llvm.cs.uiuc.edu">LLVM Team</a>. Maintained by the <a href="http://llvm.cs.uiuc.edu">LLVM Team</a>.
</body> </body>