Fix libc++ configuration with -fsanitize-coverage
authorIvan Krasin <krasin@chromium.org>
Thu, 1 Sep 2016 01:38:32 +0000 (01:38 +0000)
committerIvan Krasin <krasin@chromium.org>
Thu, 1 Sep 2016 01:38:32 +0000 (01:38 +0000)
commitc735b902a96b85fb571a57e268bd1c111119bab3
treec4c4cd36b51d161020b970a0e98c99322609bf04
parente8ae5baaf768a3a53f9edec3de39e333971b785c
Fix libc++ configuration with -fsanitize-coverage

Summary:
a recent change (r280015) in libc++ configuration broke LibFuzzer bot:
http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-fuzzer/builds/12245

It's not restricted just to that bot; any code that uses the sanitize coverage and configures libc++ hits it.

This CL fixes the issue.

Reviewers: compnerd

Subscribers: aizatsky

Differential Revision: https://reviews.llvm.org/D24116

llvm-svn: 280335
libcxx/cmake/Modules/CheckLibcxxAtomic.cmake
libcxx/cmake/config-ix.cmake