diff options
| author | Patrick Jenkins <pjenkins@apple.com> | 2006-08-15 17:03:17 +0000 |
|---|---|---|
| committer | Patrick Jenkins <pjenkins@apple.com> | 2006-08-15 17:03:17 +0000 |
| commit | 82681661acd4a413cef45a519bdeb0827cf832a2 (patch) | |
| tree | e709ce8cd33203b15ce7900f9aad8172d274e375 /docs/Bugpoint.html | |
| parent | 032091d7f62774443c282915964189ea3d8930de (diff) | |
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
Diffstat (limited to 'docs/Bugpoint.html')
| -rw-r--r-- | docs/Bugpoint.html | 6 |
1 files changed, 6 insertions, 0 deletions
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> |