[fuzzer] properly annotate fallthrough, add one more entry to FAQ
llvm-svn: 229880
diff --git a/llvm/lib/Fuzzer/FuzzerMutate.cpp b/llvm/lib/Fuzzer/FuzzerMutate.cpp
index 60d5623..b28264a 100644
--- a/llvm/lib/Fuzzer/FuzzerMutate.cpp
+++ b/llvm/lib/Fuzzer/FuzzerMutate.cpp
@@ -47,7 +47,7 @@
U->erase(U->begin() + rand() % U->size());
break;
}
- // Fallthrough
+ [[clang::fallthrough]];
case 1:
if (U->size() < MaxLen) {
U->insert(U->begin() + rand() % U->size(), RandCh());
diff --git a/llvm/lib/Fuzzer/README.txt b/llvm/lib/Fuzzer/README.txt
index 1e1acbb..e4d6b4f 100644
--- a/llvm/lib/Fuzzer/README.txt
+++ b/llvm/lib/Fuzzer/README.txt
@@ -104,3 +104,9 @@
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.