mirror of
https://github.com/llvm/llvm-project.git
synced 2025-04-17 04:16:46 +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
20 lines
811 B
C++
20 lines
811 B
C++
// RUN: %clang_cc1 %std_cxx98- -fsyntax-only -verify -w %s
|
|
|
|
struct ABC {
|
|
static double a;
|
|
static double b;
|
|
static double c;
|
|
static double d;
|
|
static double e;
|
|
static double f;
|
|
};
|
|
|
|
double ABC::a = 1.0;
|
|
extern double ABC::b = 1.0; // expected-error {{static data member definition cannot specify a storage class}}
|
|
static double ABC::c = 1.0; // expected-error {{'static' can only be specified inside the class definition}}
|
|
__private_extern__ double ABC::d = 1.0; // expected-error {{static data member definition cannot specify a storage class}}
|
|
auto double ABC::e = 1.0; // expected-error {{static data member definition cannot specify a storage class}}
|
|
#if __cplusplus < 201703L
|
|
register double ABC::f = 1.0; // expected-error {{static data member definition cannot specify a storage class}}
|
|
#endif
|