diff options
| author | George Karpenkov <ekarpenkov@apple.com> | 2017-10-13 22:03:09 +0000 |
|---|---|---|
| committer | George Karpenkov <ekarpenkov@apple.com> | 2017-10-13 22:03:09 +0000 |
| commit | a3cd5247b3a15038e1bde0a867b69432531f98de (patch) | |
| tree | a349f874f8f3f5467076e746ba16d8692fa0e039 /llvm | |
| parent | 29d3ba7576b30a37bd19a5d40f304fc39c6ab13d (diff) | |
| download | bcm5719-llvm-a3cd5247b3a15038e1bde0a867b69432531f98de.tar.gz bcm5719-llvm-a3cd5247b3a15038e1bde0a867b69432531f98de.zip | |
Allow building libFuzzer in two-stage compiler-rt build
When LLVM_BUILD_EXTERNAL_COMPILER_RT option is set to true,
all of projects in compiler-rt are built with a freshly-built compiler using
a recursive CMake invocation.
(e.g. that's how compiler-rt is used in Swift)
Just now I have noticed that libFuzzer binaries were missing in such a case,
and ninja fuzzer returned "no such target", while ninja asan worked just fine.
To my surprise, the list of allowed targets was actually hardcoded in Clang!
While the current setup is clearly suboptimal, for the lack of a better fix
I'm just adding `fuzzer` to a list of `compiler-rt` targets.
Differential Revision: https://reviews.llvm.org/D38904
llvm-svn: 315771
Diffstat (limited to 'llvm')
0 files changed, 0 insertions, 0 deletions
