RPCS3/llvm-mirror
1
0
Fork 0
mirror of https://github.com/RPCS3/llvm-mirror.git synced 2025-04-02 07:41:38 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

[fuzzer] properly annotate fallthrough, add one more entry to FAQ

Browse Source 
llvm-svn: 229880
This commit is contained in:
Kostya Serebryany 2015-02-19 18:21:12 +00:00
parent 08deae36a2
commit 1b890a52e0
2 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
lib/Fuzzer/FuzzerMutate.cpp
View File

@ -47,7 +47,7 @@ void Mutate(Unit *U, size_t MaxLen) {
U->erase(U->begin() + rand() % U->size()); U->erase(U->begin() + rand() % U->size());
break; break;
} }
// Fallthrough [[clang::fallthrough]];
case 1: case 1:
if (U->size() < MaxLen) { if (U->size() < MaxLen) {
U->insert(U->begin() + rand() % U->size(), RandCh()); U->insert(U->begin() + rand() % U->size(), RandCh());

6
lib/Fuzzer/README.txt
View File

@ -104,3 +104,9 @@ A.
more) the speed benefit from the in-process fuzzer is negligible. more) the speed benefit from the in-process fuzzer is negligible.
* If the target library runs persistent threads (that outlive * If the target library runs persistent threads (that outlive
execution of one test) the fuzzing results will be unreliable. 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.