summaryrefslogtreecommitdiffstats
path: root/clang/test/Driver/fuzzer.c
Commit message (Collapse)AuthorAgeFilesLines
* Revert r337635 "[Driver] Sanitizer support based on runtime library presence"Reid Kleckner2018-07-311-5/+5
| | | | | | | | This change causes issues with distributed build systems, which may only have compiler binaries without any runtime libraries. See discussion about this on https://reviews.llvm.org/D15225. llvm-svn: 338444
* [Driver] Sanitizer support based on runtime library presenceGeorge Karpenkov2018-07-201-5/+5
| | | | | | | | | | | | | | | The runtime libraries of sanitizers are built in compiler-rt, and Clang can be built without compiler-rt, or compiler-rt can be configured to only build certain sanitizers. The driver should provide reasonable diagnostics and not a link-time error when a runtime library is missing. This patch changes the driver for OS X to only support sanitizers of which we can find the runtime libraries. The discussion for this patch explains the rationale Differential Revision: https://reviews.llvm.org/D15225 llvm-svn: 337635
* [libFuzzer] switch -fsanitize=fuzzer from trace-pc-guard to inline-8bit-countersKostya Serebryany2017-09-011-2/+2
| | | | llvm-svn: 312346
* Fixed driver tests for -fsanitize=fuzzer.George Karpenkov2017-08-221-1/+1
| | | | llvm-svn: 311412
* Moving libFuzzer to compiler-rt: required updates to the Clang driver.George Karpenkov2017-08-211-3/+3
| | | | | | Differential Revision: https://reviews.llvm.org/D36909 llvm-svn: 311406
* Add -fsanitize=fuzzer-no-link flag to the driver.George Karpenkov2017-08-111-0/+5
| | | | | | | | | | | The flag will perform instrumentation necessary to the fuzzing, but will NOT link libLLVMFuzzer.a library. Necessary when modifying CFLAGS for projects which may produce executables as well as a fuzzable target. Differential Revision: https://reviews.llvm.org/D36600 llvm-svn: 310733
* [libFuzzer] add -fsanitize-coverage-pc-table to -fsanitize=fuzzerKostya Serebryany2017-08-041-0/+1
| | | | llvm-svn: 310136
* [libFuzzer] Add Fuzzer to the list of sanitizers which support coverage.George Karpenkov2017-06-291-0/+4
| | | | | | | | | Without this change, additional coverage flags specified after -fsanitize=fuzzer would get discarded. https://reviews.llvm.org/D34794 llvm-svn: 306734
* [libFuzzer] Do not link in libFuzzer with -fsanitize=fuzzer when producing a ↵George Karpenkov2017-06-291-0/+4
| | | | | | | | shared object https://reviews.llvm.org/D34791 llvm-svn: 306733
* Fix fuzzer.c test on platforms where CLANG_DEFAULT_CXX_STDLIB is libc++Ismail Donmez2017-04-251-1/+1
| | | | llvm-svn: 301302
* Specify a target explicitly in libfuzzer driver flag testGeorge Karpenkov2017-04-241-1/+1
| | | | llvm-svn: 301246
* Remove erroneous driver test for -fsanitize=fuzzer flagGeorge Karpenkov2017-04-241-2/+0
| | | | | | | libfuzzer is not available on all platforms, and hence we can not always rely that it was compiled. llvm-svn: 301216
* Flag -fsanitize=fuzzer to enable libfuzzerGeorge Karpenkov2017-04-241-0/+22
Previously, adding libfuzzer to a project was a multi-step procedure, involving libfuzzer compilation, linking the library, and specifying coverage flags. With this change,libfuzzer can be enabled by adding a single -fsanitize=fuzzer flag instead. llvm-svn: 301212
OpenPOWER on IntegriCloud