summaryrefslogtreecommitdiffstats
path: root/llvm/docs
diff options
context:
space:
mode:
authorKostya Serebryany <kcc@google.com>2015-05-12 18:51:57 +0000
committerKostya Serebryany <kcc@google.com>2015-05-12 18:51:57 +0000
commit9690fcf12eee2c91b106991b3aad7b0e65c0c1b3 (patch)
treed391f453af9fab0a907542830c43d0a2ca952400 /llvm/docs
parent4744ec6da984f155450683c4aa223678278050a7 (diff)
downloadbcm5719-llvm-9690fcf12eee2c91b106991b3aad7b0e65c0c1b3.tar.gz
bcm5719-llvm-9690fcf12eee2c91b106991b3aad7b0e65c0c1b3.zip
[lib/Fuzzer] guess the right number of workers if -jobs=N is given but -workers=M is not. Update the docs.
llvm-svn: 237163
Diffstat (limited to 'llvm/docs')
-rw-r--r--llvm/docs/LibFuzzer.rst10
1 files changed, 4 insertions, 6 deletions
diff --git a/llvm/docs/LibFuzzer.rst b/llvm/docs/LibFuzzer.rst
index 949ccd58418..d454b741ba0 100644
--- a/llvm/docs/LibFuzzer.rst
+++ b/llvm/docs/LibFuzzer.rst
@@ -156,13 +156,11 @@ You may run ``N`` independent fuzzer jobs in parallel on ``M`` CPUs::
N=100; M=4; ./pcre_fuzzer ./CORPUS -jobs=$N -workers=$M
-This is useful when you already have an exhaustive test corpus.
-If you've just started fuzzing with no good corpus running independent
-jobs will create a corpus with too many duplicates.
-One way to avoid this and still use all of your CPUs is to use the flag ``-exit_on_first=1``
-which will cause the fuzzer to exit on the first new synthesised input::
+By default (``-reload=1``) the fuzzer processes will periodically scan the CORPUS directory
+and reload any new tests. This way the test inputs found by one process will be picked up
+by all others.
- N=100; M=4; ./pcre_fuzzer ./CORPUS -jobs=$N -workers=$M -exit_on_first=1
+If ``-workers=$M`` is not supplied, ``min($N,NumberOfCpuCore/2)`` will be used.
Heartbleed
----------
OpenPOWER on IntegriCloud