diff options
| author | Max Moroz <mmoroz@chromium.org> | 2018-05-23 19:42:30 +0000 |
|---|---|---|
| committer | Max Moroz <mmoroz@chromium.org> | 2018-05-23 19:42:30 +0000 |
| commit | fe97441c2c61f6cbd0104f299540d7ddf4f068b0 (patch) | |
| tree | 6a5b88f26a7ebf9b3790cf245cf01072aa587429 /llvm/tools/llvm-objcopy/llvm-objcopy.cpp | |
| parent | 8b0da65bfba3f9dd18e90b872721b29c8799eb8f (diff) | |
| download | bcm5719-llvm-fe97441c2c61f6cbd0104f299540d7ddf4f068b0.tar.gz bcm5719-llvm-fe97441c2c61f6cbd0104f299540d7ddf4f068b0.zip | |
[libFuzzer] Don't complain about lack of interesting inputs when -runs=0.
Summary:
The most common usecase for -runs=0 is for generating code coverage
over some corpus. Coverage reports based on sancov are about to be deprecated,
which means some external coverage solution will be used, e.g. Clang source
based code coverage, which does not use any sancov instrumentations and thus
libFuzzer would consider any input to be not interesting in that case.
Reviewers: kcc
Reviewed By: kcc
Subscribers: alex, delcypher, #sanitizers, llvm-commits
Differential Revision: https://reviews.llvm.org/D47271
llvm-svn: 333116
Diffstat (limited to 'llvm/tools/llvm-objcopy/llvm-objcopy.cpp')
0 files changed, 0 insertions, 0 deletions
