summaryrefslogtreecommitdiffstats
path: root/clang/test/SemaCXX
diff options
context:
space:
mode:
authorRichard Smith <richard-llvm@metafoo.co.uk>2012-10-29 18:26:47 +0000
committerRichard Smith <richard-llvm@metafoo.co.uk>2012-10-29 18:26:47 +0000
commitbf83009c7faafe321dd09f15b2ce8f8847d2ded0 (patch)
tree387c6d8687172568ca342d6d11f985624b02e52a /clang/test/SemaCXX
parent908c936fa9239da91962503527dd701ebe71a9b4 (diff)
downloadbcm5719-llvm-bf83009c7faafe321dd09f15b2ce8f8847d2ded0.tar.gz
bcm5719-llvm-bf83009c7faafe321dd09f15b2ce8f8847d2ded0.zip
Partially roll back r166898; it exposed a bug in the standard.
The problem is as follows: C++11 has contexts which are not potentially-evaluated, and yet in which we are required or encouraged to perform constant evaluation. In such contexts, we are not permitted to implicitly define special member functions for literal types, therefore we cannot evalaute those constant expressions. Punt on this in one more context for now by skipping checking constexpr variable initializers if they occur in dependent contexts. llvm-svn: 166956
Diffstat (limited to 'clang/test/SemaCXX')
-rw-r--r--clang/test/SemaCXX/constant-expression-cxx11.cpp27
1 files changed, 23 insertions, 4 deletions
diff --git a/clang/test/SemaCXX/constant-expression-cxx11.cpp b/clang/test/SemaCXX/constant-expression-cxx11.cpp
index 9a9746ee29b..0dd7ffe5a9a 100644
--- a/clang/test/SemaCXX/constant-expression-cxx11.cpp
+++ b/clang/test/SemaCXX/constant-expression-cxx11.cpp
@@ -521,7 +521,7 @@ namespace DependentValues {
struct I { int n; typedef I V[10]; };
I::V x, y;
-int g(); // expected-note {{here}}
+int g();
template<bool B, typename T> struct S : T {
int k;
void f() {
@@ -529,9 +529,8 @@ template<bool B, typename T> struct S : T {
I &i = cells[k];
switch (i.n) {}
- constexpr int n = g(); // \
- // expected-error {{must be initialized by a constant expression}} \
- // expected-note {{non-constexpr function 'g'}}
+ // FIXME: We should be able to diagnose this.
+ constexpr int n = g();
constexpr int m = this->g(); // ok, could be constexpr
}
@@ -1435,3 +1434,23 @@ namespace TypeId {
constexpr auto &y = typeid(g()); // expected-error{{constant expression}} \
// expected-note{{typeid applied to expression of polymorphic type 'TypeId::A' is not allowed in a constant expression}}
}
+
+namespace PR14203 {
+ struct duration {
+ constexpr duration() {}
+ constexpr operator int() const { return 0; }
+ };
+ template<typename T> void f() {
+ // If we want to evaluate this at the point of the template definition, we
+ // need to trigger the implicit definition of the move constructor at that
+ // point.
+ // FIXME: C++ does not permit us to implicitly define it at the appropriate
+ // times, since it is only allowed to be implicitly defined when it is
+ // odr-used.
+ constexpr duration d = duration();
+ }
+ // FIXME: It's unclear whether this is valid. On the one hand, we're not
+ // allowed to generate a move constructor. On the other hand, if we did,
+ // this would be a constant expression.
+ int n = sizeof(short{duration(duration())}); // expected-error {{non-constant-expression cannot be narrowed}} expected-note {{override}}
+}
OpenPOWER on IntegriCloud