diff options
| author | Reid Kleckner <rnk@google.com> | 2019-07-11 23:20:04 +0000 |
|---|---|---|
| committer | Reid Kleckner <rnk@google.com> | 2019-07-11 23:20:04 +0000 |
| commit | 1a285c27fdf6407ceed3398e015d00559f5f533d (patch) | |
| tree | 1c2884f5a1bd35961d14567f0074ff2df47aaf2c /clang/lib/Frontend/CompilerInvocation.cpp | |
| parent | 41798c05cd20401b3f77d12b8bfcb0437132021f (diff) | |
| download | llvm-1a285c27fdf6407ceed3398e015d00559f5f533d.zip llvm-1a285c27fdf6407ceed3398e015d00559f5f533d.tar.gz llvm-1a285c27fdf6407ceed3398e015d00559f5f533d.tar.bz2 | |
Use clang driver for libfuzzer tests on Windows
Summary:
There's no real reason to use clang-cl on Windows, the clang driver
works just as well. This fixes a test which uses the -O0 flag, which was
recently removed from clang-cl to match MSVC, which lacks this flag.
While I'm here, remove the explicit -std=c++11 flag. Previously, this
flag was necessary when the default C++ standard was C++98. Now that the
default is C++14, this is no longer necessary. It's problematic on
Windows, because the Visual C++ standard library relies on C++14
features, and attempting to compile it with C++11 results in errors.
Rather than adding logic to conditionally set the standard to C++11 only
on non-Win, this flag can be removed.
See http://lab.llvm.org:8011/builders/clang-x64-windows-msvc and
https://reviews.llvm.org/D64506.
Reviewers: morehouse, thakis
Subscribers: #sanitizers, llvm-commits
Tags: #sanitizers, #llvm
Differential Revision: https://reviews.llvm.org/D64587
llvm-svn: 365841
Diffstat (limited to 'clang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions