summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api
diff options
context:
space:
mode:
authorNico Weber <nicolasweber@gmx.de>2016-02-19 01:52:46 +0000
committerNico Weber <nicolasweber@gmx.de>2016-02-19 01:52:46 +0000
commit6a6376b17cdf6c0adf8e52a298beff75079d932a (patch)
tree28db16259c8b63d08c36b6519f9503652f35b37f /lldb/packages/Python/lldbsuite/test/python_api
parent74f5b282110eb6a548f93738e67b707d654b0882 (diff)
downloadbcm5719-llvm-6a6376b17cdf6c0adf8e52a298beff75079d932a.tar.gz
bcm5719-llvm-6a6376b17cdf6c0adf8e52a298beff75079d932a.zip
Implement the likely resolution of core issue 253.
C++11 requires const objects to have a user-provided constructor, even for classes without any fields. DR 253 relaxes this to say "If the implicit default constructor initializes all subobjects, no initializer should be required." clang is currently the only compiler that implements this C++11 rule, and e.g. libstdc++ relies on something like DR 253 to compile in newer versions. This change makes it possible to build code that says `const vector<int> v;' again when using libstdc++5.2 and _GLIBCXX_DEBUG (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60284). Fixes PR23381. http://reviews.llvm.org/D16552 llvm-svn: 261297
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud