From 82681661acd4a413cef45a519bdeb0827cf832a2 Mon Sep 17 00:00:00 2001
From: Patrick Jenkins <pjenkins@apple.com>
Date: Tue, 15 Aug 2006 17:03:17 +0000
Subject: This commit mentions -find-bugs under the advice for using bugpoints
 section of the bugpoint design and usage document.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@29705 91177308-0d34-0410-b5e6-96231b3b80d8
---
 docs/Bugpoint.html | 6 ++++++
 1 file changed, 6 insertions(+)

(limited to 'docs/Bugpoint.html')

diff --git a/docs/Bugpoint.html b/docs/Bugpoint.html
index e2a3611db2..4bcf9977d5 100644
--- a/docs/Bugpoint.html
+++ b/docs/Bugpoint.html
@@ -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>
 
-- 
cgit v1.2.3