Richard Smith 3607ffee5c Update constexpr implementation to match CWG's chosen approach for core issues ... 1358, 1360, 1452 and 1453. - Instantiations of constexpr functions are always constexpr. This removes the need for separate declaration/definition checking, which is now gone. - This makes it possible for a constexpr function to be virtual, if they are only dependently virtual. Virtual calls to such functions are not constant expressions. - Likewise, it's now possible for a literal type to have virtual base classes. A constexpr constructor for such a type cannot actually produce a constant expression, though, so add a special-case diagnostic for a constructor call to such a type rather than trying to evaluate it. - Classes with trivial default constructors (for which value initialization can produce a fully-initialized value) are considered literal types. - Classes with volatile members are not literal types. - constexpr constructors can be members of non-literal types. We do not yet use static initialization for global objects constructed in this way. llvm-svn: 150359		2012-02-13 03:54:03 +00:00
..
p1.cpp	Update constexpr implementation to match CWG's chosen approach for core issues	2012-02-13 03:54:03 +00:00
p2.cpp	Update all tests other than Driver/std.cpp to use -std=c++11 rather than	2011-10-13 22:29:44 +00:00
p3.cpp	Update constexpr implementation to match CWG's chosen approach for core issues	2012-02-13 03:54:03 +00:00
p4.cpp	Update constexpr implementation to match CWG's chosen approach for core issues	2012-02-13 03:54:03 +00:00
p5.cpp	constexpr: Implement DR1358: An instantiation of a constexpr function which	2012-02-05 02:30:54 +00:00
p6.cpp	Update constexpr implementation to match CWG's chosen approach for core issues	2012-02-13 03:54:03 +00:00
p8.cpp	constexpr is allowed on static member functions of non-literal classes. Per report on cfe-dev.	2012-01-13 02:31:53 +00:00
p9.cpp	Update constexpr implementation to match CWG's chosen approach for core issues	2012-02-13 03:54:03 +00:00