summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Fuzzer/FuzzerMerge.cpp
Commit message (Collapse)AuthorAgeFilesLines
* [libFuzzer] Delete llvm/lib/FuzzerVitaly Buka2017-10-161-338/+0
| | | | | | | | | | | | Summary: Code is already in compiler-rt Reviewers: kcc Subscribers: krytarowski, llvm-commits, hiraditya Differential Revision: https://reviews.llvm.org/D38912 llvm-svn: 315937
* [libFuzzer] Allow non-fuzzer args after -ignore_remaining_args=1Justin Bogner2017-07-141-3/+4
| | | | | | | | | | | With this change, libFuzzer will ignore any arguments after a sigil argument, but it will preserve these arguments at the end of the command line when launching subprocesses. Using this, its possible to handle positional and single-dash arguments to the program under test by discarding everything up to -ignore_remaining_args=1 in LLVMFuzzerInitialize. llvm-svn: 308069
* [libFuzzer] fix stats during mergeKostya Serebryany2017-07-141-1/+0
| | | | llvm-svn: 308061
* Sort the remaining #include lines in include/... and lib/....Chandler Carruth2017-06-061-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | I did this a long time ago with a janky python script, but now clang-format has built-in support for this. I fed clang-format every line with a #include and let it re-sort things according to the precise LLVM rules for include ordering baked into clang-format these days. I've reverted a number of files where the results of sorting includes isn't healthy. Either places where we have legacy code relying on particular include ordering (where possible, I'll fix these separately) or where we have particular formatting around #include lines that I didn't want to disturb in this patch. This patch is *entirely* mechanical. If you get merge conflicts or anything, just ignore the changes in this patch and run clang-format over your #include lines in the files. Sorry for any noise here, but it is important to keep these things stable. I was seeing an increasing number of patches with irrelevant re-ordering of #include lines because clang-format was used. This patch at least isolates that churn, makes it easy to skip when resolving conflicts, and gets us to a clean baseline (again). llvm-svn: 304787
* [libFuzzer] add two experimental flags to make corpus merging more scalable: ↵Kostya Serebryany2017-03-221-4/+56
| | | | | | -save_coverage_summary/-load_coverage_summary. This is still WIP, the documentation will come later if these flags survive llvm-svn: 298548
* [libFuzzer] reduce the number of vector resizes during merge ↵Kostya Serebryany2017-03-111-6/+7
| | | | | | (https://github.com/google/oss-fuzz/issues/445) llvm-svn: 297551
* [libFuzzer] print how much memory is consumed by the outer merge process ↵Kostya Serebryany2017-03-111-1/+11
| | | | | | (https://github.com/google/oss-fuzz/issues/445) llvm-svn: 297546
* [libFuzzer] exit(1) on failed mergeKostya Serebryany2017-01-181-0/+6
| | | | llvm-svn: 292319
* [libFuzzer] improve error handling during the merge (handle various IO failures)Kostya Serebryany2017-01-051-0/+8
| | | | llvm-svn: 291182
* [libFuzzer] use /tmp (or $TMPDIR, if present) to store temp files during mergeKostya Serebryany2017-01-051-2/+2
| | | | llvm-svn: 291078
* [libFuzzer] use less memory for mergeKostya Serebryany2016-12-171-6/+7
| | | | llvm-svn: 290039
* [libFuzzer] enable the failure-resistant merge by default (with ↵Kostya Serebryany2016-12-151-2/+2
| | | | | | trace-pc-guard only) llvm-svn: 289772
* [libFuzzer] Add missing header needed for Windows.Marcos Pividori2016-12-131-0/+1
| | | | llvm-svn: 289564
* [libFuzzer] Avoid name collision with Windows API.Marcos Pividori2016-12-131-2/+2
| | | | | | | | | | Windows uses some macros to replace DeleteFile() by DeleteFileA() or DeleteFileW(). This was causing an error at link time. DeleteFile was renamed to RemoveFile(). Differential Revision: https://reviews.llvm.org/D27577 llvm-svn: 289563
* [libFuzzer] respect -max_len during mergeKostya Serebryany2016-12-121-0/+4
| | | | llvm-svn: 289467
* [libFuzzer] implement crash-resistant merge ↵Kostya Serebryany2016-12-091-0/+255
(https://github.com/google/sanitizers/issues/722). This is a first experimental variant that needs some more testing, thus not yet adding a lit test (but there are unit tests). llvm-svn: 289166
OpenPOWER on IntegriCloud