mirror of
https://github.com/capstone-engine/llvm-capstone.git
synced 2024-12-12 01:18:53 +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
19 lines
744 B
C++
19 lines
744 B
C++
// RUN: %clang_cc1 -fsyntax-only -verify %s
|
|
// RUN: %clang_cc1 -fsyntax-only -verify -std=c++14 %s
|
|
// RUN: %clang_cc1 -fsyntax-only -verify=expected,cxx17-compat -std=c++17 %s -Wpre-c++17-compat
|
|
|
|
// Check that we don't allow illegal uses of inline
|
|
// (checking C++-only constructs here)
|
|
struct c {inline int a;}; // expected-error{{'inline' can only appear on functions}}
|
|
|
|
void localVar() {
|
|
inline int a; // expected-error{{inline declaration of 'a' not allowed in block scope}}
|
|
}
|
|
|
|
// Check that we warn appropriately.
|
|
#if __cplusplus <= 201402L
|
|
inline int a; // expected-warning{{inline variables are a C++17 extension}}
|
|
#else
|
|
inline int a; // cxx17-compat-warning{{inline variables are incompatible with C++ standards before C++17}}
|
|
#endif
|