summaryrefslogtreecommitdiffstats
path: root/llvm/docs/Bugpoint.html
diff options
context:
space:
mode:
authorPatrick Jenkins <pjenkins@apple.com>2006-08-15 17:03:17 +0000
committerPatrick Jenkins <pjenkins@apple.com>2006-08-15 17:03:17 +0000
commit478cc0435bd53c93d29e276fdcfcb646ebd7615c (patch)
treececfa9e16eb7293e2ab37f42092e38e5afbe54a0 /llvm/docs/Bugpoint.html
parent38a197a2eb20b65a061d3e1713d5cccf0aa5df24 (diff)
downloadbcm5719-llvm-478cc0435bd53c93d29e276fdcfcb646ebd7615c.tar.gz
bcm5719-llvm-478cc0435bd53c93d29e276fdcfcb646ebd7615c.zip
This commit mentions -find-bugs under the advice for using bugpoints section of the bugpoint design and usage document.
llvm-svn: 29705
Diffstat (limited to 'llvm/docs/Bugpoint.html')
-rw-r--r--llvm/docs/Bugpoint.html6
1 files changed, 6 insertions, 0 deletions
diff --git a/llvm/docs/Bugpoint.html b/llvm/docs/Bugpoint.html
index e2a3611db27..4bcf9977d56 100644
--- a/llvm/docs/Bugpoint.html
+++ b/llvm/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>
OpenPOWER on IntegriCloud