2013-09-20 11:03:06 +08:00
|
|
|
// RUN: %clang_cc1 %s -Wno-uninitialized -std=c++11 -fsyntax-only -verify
|
2011-12-31 05:15:51 +08:00
|
|
|
|
|
|
|
struct A {
|
2013-04-26 22:36:30 +08:00
|
|
|
constexpr A() : a(b + 1), b(a + 1) {} // expected-note {{outside its lifetime}}
|
2011-12-31 05:15:51 +08:00
|
|
|
int a;
|
|
|
|
int b;
|
|
|
|
};
|
|
|
|
struct B {
|
|
|
|
A a;
|
|
|
|
};
|
|
|
|
|
2013-12-06 00:25:25 +08:00
|
|
|
constexpr A a; // ok, zero initialization precedes static initialization
|
2011-12-31 05:15:51 +08:00
|
|
|
void f() {
|
|
|
|
constexpr A a; // expected-error {{constant expression}} expected-note {{in call to 'A()'}}
|
|
|
|
}
|
|
|
|
|
2016-02-19 09:52:46 +08:00
|
|
|
constexpr B b1; // ok
|
2011-12-31 05:15:51 +08:00
|
|
|
constexpr B b2 = B(); // ok
|
|
|
|
static_assert(b2.a.a == 1, "");
|
|
|
|
static_assert(b2.a.b == 2, "");
|
|
|
|
|
|
|
|
struct C {
|
|
|
|
int c;
|
|
|
|
};
|
|
|
|
struct D : C { int d; };
|
Move fixit for const init from note to diag, weaken to warning in MS mode.
r235046 turned "extern __declspec(selectany) int a;" from a declaration into
a definition to fix PR23242 (required for compatibility with mc.exe output).
However, this broke parsing Windows headers: A d3d11 headers contain something
like
struct SomeStruct {};
extern const __declspec(selectany) SomeStruct some_struct;
This is now a definition, and const objects either need an explicit default
ctor or an initializer so this errors out with
d3d11.h(1065,48) :
error: default initialization of an object of const type
'const CD3D11_DEFAULT' without a user-provided default constructor
(cl.exe just doesn't implement this rule, independent of selectany.)
To work around this, weaken this error into a warning for selectany decls
in microsoft mode, and recover with zero-initialization.
Doing this is a bit hairy since it adds a fixit on an error emitted
by InitializationSequence – this means it needs to build a correct AST, which
in turn means InitializationSequence::Failed() cannot return true when this
fixit is applied. As a workaround, the patch adds a fixit member to
InitializationSequence, and InitializationSequence::Perform() prints the
diagnostic if the fixit member is set right after its call to Diagnose.
That function is usually called when InitializationSequences are used –
InitListChecker::PerformEmptyInit() doesn't call it, but the InitListChecker
case never performs default-initialization, so this is technically OK.
This is the alternative, original fix for PR20208 that got reviewed in the
thread "[patch] Improve diagnostic on default-initializing const variables
(PR20208)". This change basically reverts r213725, adds the original fix for
PR20208, and makes the error a warning in Microsoft mode.
llvm-svn: 235166
2015-04-17 16:32:38 +08:00
|
|
|
constexpr C c1; // expected-error {{without a user-provided default constructor}}
|
2011-12-31 05:15:51 +08:00
|
|
|
constexpr C c2 = C(); // ok
|
Move fixit for const init from note to diag, weaken to warning in MS mode.
r235046 turned "extern __declspec(selectany) int a;" from a declaration into
a definition to fix PR23242 (required for compatibility with mc.exe output).
However, this broke parsing Windows headers: A d3d11 headers contain something
like
struct SomeStruct {};
extern const __declspec(selectany) SomeStruct some_struct;
This is now a definition, and const objects either need an explicit default
ctor or an initializer so this errors out with
d3d11.h(1065,48) :
error: default initialization of an object of const type
'const CD3D11_DEFAULT' without a user-provided default constructor
(cl.exe just doesn't implement this rule, independent of selectany.)
To work around this, weaken this error into a warning for selectany decls
in microsoft mode, and recover with zero-initialization.
Doing this is a bit hairy since it adds a fixit on an error emitted
by InitializationSequence – this means it needs to build a correct AST, which
in turn means InitializationSequence::Failed() cannot return true when this
fixit is applied. As a workaround, the patch adds a fixit member to
InitializationSequence, and InitializationSequence::Perform() prints the
diagnostic if the fixit member is set right after its call to Diagnose.
That function is usually called when InitializationSequences are used –
InitListChecker::PerformEmptyInit() doesn't call it, but the InitListChecker
case never performs default-initialization, so this is technically OK.
This is the alternative, original fix for PR20208 that got reviewed in the
thread "[patch] Improve diagnostic on default-initializing const variables
(PR20208)". This change basically reverts r213725, adds the original fix for
PR20208, and makes the error a warning in Microsoft mode.
llvm-svn: 235166
2015-04-17 16:32:38 +08:00
|
|
|
constexpr D d1; // expected-error {{without a user-provided default constructor}}
|
2012-02-13 11:54:03 +08:00
|
|
|
constexpr D d2 = D(); // ok with DR1452
|
2011-12-31 05:15:51 +08:00
|
|
|
static_assert(D().c == 0, "");
|
|
|
|
static_assert(D().d == 0, "");
|
2012-02-17 08:44:16 +08:00
|
|
|
|
|
|
|
struct V : virtual C {};
|
|
|
|
template<typename T> struct Z : T {
|
|
|
|
constexpr Z() : V() {}
|
|
|
|
};
|
|
|
|
constexpr int n = Z<V>().c; // expected-error {{constant expression}} expected-note {{virtual base class}}
|