This commit mentions -find-bugs under the advice for using bugpoints section of the...
authorPatrick Jenkins <pjenkins@apple.com>
Tue, 15 Aug 2006 17:03:17 +0000 (17:03 +0000)
committerPatrick Jenkins <pjenkins@apple.com>
Tue, 15 Aug 2006 17:03:17 +0000 (17:03 +0000)
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@29705 91177308-0d34-0410-b5e6-96231b3b80d8

docs/Bugpoint.html

index e2a3611db27a3f85e730d7414bff1e9de062babd..4bcf9977d56d124207dee0c00ccff78a60525695 100644 (file)
@@ -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 an error occurs or the user
+    kills <tt>bugpoint</tt>.
     
 </ol>