mirror of
https://github.com/llvm/llvm-project.git
synced 2025-04-29 11:16:07 +00:00
83ea47acd7
GCC from 11 onwards defaults to -std=gnu++17 for C++ source files. We want to do the same (https://discourse.llvm.org/t/c-objc-switch-to-gnu-17-as-the-default-dialect/64360). Split RUN lines, adjust `-verify`, or add `__cplusplus < 201703L` or `-Wno-dynamic-exception-spec`, so that tests will pass regardless of gnu++14/gnu++17 default. We have a desire to mark a test compatible with multiple language standards. There are ongoing discussions how to add markers in the long term: * https://discourse.llvm.org/t/iterating-lit-run-lines/62596 * https://discourse.llvm.org/t/lit-run-a-run-line-multiple-times-with-different-replacements/64932 As a workaround in the short term, add lit substitutions `%std_cxx98-`, `%std_cxx11-14`, etc. They can be used for tests which work across multiple language standards. If a range has `n` standards, run lit multiple times, with `LIT_CLANG_STD_GROUP=0`, `LIT_CLANG_STD_GROUP=1`, etc to cover all `n` standards. Reviewed By: #clang-language-wg, aaron.ballman Differential Revision: https://reviews.llvm.org/D131464
34 lines
608 B
C++
34 lines
608 B
C++
// RUN: %clang_cc1 %std_cxx98- -fcxx-exceptions -fexceptions -Wno-dynamic-exception-spec %s -triple=i686-unknown-linux -emit-llvm -o - | FileCheck %s
|
|
typedef int Array[10];
|
|
|
|
void foo() throw (Array) {
|
|
throw 0;
|
|
// CHECK: landingpad
|
|
// CHECK-NEXT: filter {{.*}} @_ZTIPi
|
|
}
|
|
|
|
struct S {
|
|
void foo() throw (S[10]) {
|
|
throw 0;
|
|
}
|
|
};
|
|
|
|
template <typename T>
|
|
struct S2 {
|
|
void foo() throw (T) {
|
|
throw 0;
|
|
}
|
|
};
|
|
|
|
int main() {
|
|
S s;
|
|
s.foo();
|
|
// CHECK: landingpad
|
|
// CHECK-NEXT: filter {{.*}} @_ZTIP1S
|
|
|
|
S2 <int[10]> s2;
|
|
s2.foo();
|
|
// CHECK: landingpad
|
|
// CHECK-NEXT: filter {{.*}} @_ZTIPi
|
|
}
|