summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorPatrick Jenkins <pjenkins@apple.com>2006-08-15 17:38:36 +0000
committerPatrick Jenkins <pjenkins@apple.com>2006-08-15 17:38:36 +0000
commit94f7850af9034777855a7de6f459f1186c03debd (patch)
tree2dca7e6480379d71698f28911c3cd68d024190bb /docs
parent7d686d58a7cc035e7fbf7936a31730d3dd4d3ef6 (diff)
downloadllvm-94f7850af9034777855a7de6f459f1186c03debd.tar.gz
llvm-94f7850af9034777855a7de6f459f1186c03debd.tar.bz2
llvm-94f7850af9034777855a7de6f459f1186c03debd.tar.xz
Fixed the awkward description of -find-bugs in the "Advice for using bugpoint" section.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@29707 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs')
-rw-r--r--docs/Bugpoint.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/Bugpoint.html b/docs/Bugpoint.html
index 4bcf9977d5..f60a7ea33a 100644
--- a/docs/Bugpoint.html
+++ b/docs/Bugpoint.html
@@ -219,7 +219,7 @@ non-obvious ways. Here are some hints and tips:<p>
<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
+ program. This process will repeat until a bug is found or the user
kills <tt>bugpoint</tt>.
</ol>