Describe the recent changes to the bytecode format for PR761.

[oota-llvm.git] / docs / Bugpoint.html

diff --git a/docs/Bugpoint.html b/docs/Bugpoint.html
index e2a3611db27a3f85e730d7414bff1e9de062babd..1f295336706c4474373ed3d983a53f672bbf75c8 100644 (file)
--- a/docs/Bugpoint.html
+++ b/docs/Bugpoint.html
@@ -124,7 +124,7 @@ 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>opt</tt>, <tt>analyze</tt>, or <tt>llc</tt>.</p>
+reproduce the failure with <tt>opt</tt> or <tt>llc</tt>.</p>
 
 </div>
 
@@ -215,6 +215,12 @@ non-obvious ways.  Here are some hints and tips:<p>
     confused. One way to deal with this is to cause bugpoint to ignore the exit
     code from your program, by giving it the <tt>-check-exit-code=false</tt>
     option.
+
+<li><tt>bugpoint</tt> is useful for proactively finding bugs in LLVM. 
+    Invoking <tt>bugpoint</tt> with the <tt>-find-bugs</tt> option will cause
+    the list of specified optimizations to be randomized and applied to the 
+    program. This process will repeat until a bug is found or the user
+    kills <tt>bugpoint</tt>.
     
 </ol>