summaryrefslogtreecommitdiffstats
path: root/llvm
diff options
context:
space:
mode:
authorJustin Bogner <mail@justinbogner.com>2017-10-13 06:29:09 +0000
committerJustin Bogner <mail@justinbogner.com>2017-10-13 06:29:09 +0000
commit1cd8cf393711fc1fcd3401d784c0547d603dbe73 (patch)
tree4239ed7e5169b542a372e08ac885406634cc8a17 /llvm
parentba23183ba7ef3be316b4bd5649520a0c1d35281d (diff)
downloadbcm5719-llvm-1cd8cf393711fc1fcd3401d784c0547d603dbe73.tar.gz
bcm5719-llvm-1cd8cf393711fc1fcd3401d784c0547d603dbe73.zip
docs: Improve wording on building for fuzzing
The original sentence didn't really make sense. Patch by Vedant Kumar. Thanks! llvm-svn: 315676
Diffstat (limited to 'llvm')
-rw-r--r--llvm/docs/FuzzingLLVM.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/llvm/docs/FuzzingLLVM.rst b/llvm/docs/FuzzingLLVM.rst
index 138c655a962..5ac0ff8d519 100644
--- a/llvm/docs/FuzzingLLVM.rst
+++ b/llvm/docs/FuzzingLLVM.rst
@@ -199,9 +199,9 @@ Configuring LLVM to Build Fuzzers
Fuzzers will be built and linked to libFuzzer by default as long as you build
LLVM with sanitizer coverage enabled. You would typically also enable at least
-one sanitizer for the fuzzers to be particularly likely, so the most common way
-to build the fuzzers is by adding the following two flags to your CMake
-invocation: ``-DLLVM_USE_SANITIZER=Address -DLLVM_USE_SANITIZE_COVERAGE=On``.
+one sanitizer to find bugs faster. The most common way to build the fuzzers is
+by adding the following two flags to your CMake invocation:
+``-DLLVM_USE_SANITIZER=Address -DLLVM_USE_SANITIZE_COVERAGE=On``.
.. note:: If you have ``compiler-rt`` checked out in an LLVM tree when building
with sanitizers, you'll want to specify ``-DLLVM_BUILD_RUNTIME=Off``
OpenPOWER on IntegriCloud