aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJinsong Ji <jji@us.ibm.com>2019-09-17 18:39:04 +0000
committerJinsong Ji <jji@us.ibm.com>2019-09-17 18:39:04 +0000
commit6fce46a5f137dff54d33995a655f347a966e61be (patch)
tree9103a783c7a1a992fdef48f9deb15b634cf72649
parent5584ead50e627a98498993339597f5a90b36c91a (diff)
downloadllvm-6fce46a5f137dff54d33995a655f347a966e61be.zip
llvm-6fce46a5f137dff54d33995a655f347a966e61be.tar.gz
llvm-6fce46a5f137dff54d33995a655f347a966e61be.tar.bz2
[docs][Bugpoint] Revert 5584ead50 a5aa3353
No sure why there are still warnings, revert while I investigate. llvm-svn: 372161
-rw-r--r--llvm/docs/Bugpoint.rst6
1 files changed, 0 insertions, 6 deletions
diff --git a/llvm/docs/Bugpoint.rst b/llvm/docs/Bugpoint.rst
index de4c6a3..f3bb54c 100644
--- a/llvm/docs/Bugpoint.rst
+++ b/llvm/docs/Bugpoint.rst
@@ -121,12 +121,6 @@ non-obvious ways. Here are some hints and tips:
miscompilation. Programs should be temporarily modified to disable outputs
that are likely to vary from run to run.
-* In the crash debugger, ``bugpoint`` does not distiguish different crashes
- during reduction. Thus, if new crash or miscompilation happens, ``bugpoint``
- will continue with the new crash instead. If you would like to stick to
- particular crash, you should write check scripts to validate the error
- message, see ``-compile-command`` in :doc:`/Bugpoint`_.
-
* In the code generator and miscompilation debuggers, debugging will go faster
if you manually modify the program or its inputs to reduce the runtime, but
still exhibit the problem.