summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Fuzzer/FuzzerIOPosix.cpp
diff options
context:
space:
mode:
authorMarcos Pividori <mpividori@google.com>2017-01-20 22:49:08 +0000
committerMarcos Pividori <mpividori@google.com>2017-01-20 22:49:08 +0000
commit3984eb4ad0efd3ed9536a295f57d4cea88a854b4 (patch)
tree9c958c4dd7bdf7efbea8faaede4c52049450c6f6 /llvm/lib/Fuzzer/FuzzerIOPosix.cpp
parentd41720267ed6c35ec10ff3cd58e2e70f839a47c3 (diff)
downloadbcm5719-llvm-3984eb4ad0efd3ed9536a295f57d4cea88a854b4.tar.gz
bcm5719-llvm-3984eb4ad0efd3ed9536a295f57d4cea88a854b4.zip
[libFuzzer] Use clang as linker on Windows, to properly include sanitizer libraries.
In order to use sanitizers on Windows, we need to link against many runtime libraries which will depend on the target being created (executable or dll) and the c runtime library used (MT/MD). By default, cmake uses link.exe for linking, which fails because we don't specify the appropiate dependencies. As we don't want to consider all of that possible situations which depends on the implementation of the compiler-rt, the simplest option is to change the rules for linking executables and shared libraries, using the compiler instead of link.exe. Clang driver will consider the sanitizer flags, and automatically provide the required libraries to the linker. Differential Revision: https://reviews.llvm.org/D27869 llvm-svn: 292669
Diffstat (limited to 'llvm/lib/Fuzzer/FuzzerIOPosix.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud