diff options
| author | Krasimir Georgiev <krasimir@google.com> | 2019-07-25 12:15:46 +0000 |
|---|---|---|
| committer | Krasimir Georgiev <krasimir@google.com> | 2019-07-25 12:15:46 +0000 |
| commit | 369dd3407ccfe7c25cd3c32b4b866117c27f48ba (patch) | |
| tree | fb05b1b0fe3dd513d6421b7bf9f2ebfe2ff6e87e /lldb/packages/Python/lldbsuite/test/python_api/thread/main2.cpp | |
| parent | bc4a63fd3c29c1a8ce22891bf34ee4dccfef578c (diff) | |
| download | bcm5719-llvm-369dd3407ccfe7c25cd3c32b4b866117c27f48ba.tar.gz bcm5719-llvm-369dd3407ccfe7c25cd3c32b4b866117c27f48ba.zip | |
Update some tests after r366702
Summary:
r366702 added a set of new clang-cl -- specific openmp flags together with tests.
The way the newly added tests work is problematic: consider for example this
asertion:
```
// RUN: %clang_cl --target=x86_64-windows-msvc /openmp -### -- %s 2>&1 | FileCheck --check-prefix=CHECK-CC1-OPENMP %s
...
// CHECK-CC1-OPENMP: "-fopenmp"
```
It asserts that an `/openmp` flag should expand into `-fopenmp`. This however
depends on the default value of Clang's CLANG_DEFAULT_OPENMP_RUNTIME value.
Indeed, the code that adds `-fopenmp` to the output only does it if the default
runtime is `libomp` or `libiomp5`, not when it is `libgomp`.
I've updated the tests to not depend on the default value of this setting by
specifying the runtime to use explicitly in each assertion.
Reviewers: jdoerfert
Subscribers: cfe-commits
Tags: #clang
Differential Revision: https://reviews.llvm.org/D65272
llvm-svn: 367012
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/thread/main2.cpp')
0 files changed, 0 insertions, 0 deletions
