summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Fuzzer/README.txt
diff options
context:
space:
mode:
Diffstat (limited to 'llvm/lib/Fuzzer/README.txt')
-rw-r--r--llvm/lib/Fuzzer/README.txt6
1 files changed, 6 insertions, 0 deletions
diff --git a/llvm/lib/Fuzzer/README.txt b/llvm/lib/Fuzzer/README.txt
index 1e1acbbe1dd..e4d6b4f2079 100644
--- a/llvm/lib/Fuzzer/README.txt
+++ b/llvm/lib/Fuzzer/README.txt
@@ -104,3 +104,9 @@ A.
more) the speed benefit from the in-process fuzzer is negligible.
* If the target library runs persistent threads (that outlive
execution of one test) the fuzzing results will be unreliable.
+
+Q. So, what exactly this Fuzzer is good for?
+A. This Fuzzer might be a good choice for testing libraries that have relatively
+small inputs, each input takes < 1ms to run, and the library code is not expected
+to crash on invalid inputs.
+Examples: regular expression matchers, text or binary format parsers.
OpenPOWER on IntegriCloud