summaryrefslogtreecommitdiffstats
path: root/clang
diff options
context:
space:
mode:
authorDavide Italiano <davide@freebsd.org>2017-12-14 23:11:15 +0000
committerDavide Italiano <davide@freebsd.org>2017-12-14 23:11:15 +0000
commitd416b0b90398f11a82d637fee0fa6a41fff2778a (patch)
tree960f8f0dce017a69f87a5f54122bb197dcb3f816 /clang
parentd123f8ccf17478c1a09b0cbdc7e267154c62ca40 (diff)
downloadbcm5719-llvm-d416b0b90398f11a82d637fee0fa6a41fff2778a.tar.gz
bcm5719-llvm-d416b0b90398f11a82d637fee0fa6a41fff2778a.zip
[ExpressionParser] Fix evaluation failures due to mismatch in C++ versions.
Clang recently switched to C++14 (with GNU extensions) as the default dialect, but LLDB didn't catch up. This causes failures as LLDB still evaluates ObjectiveC expressions as Objective C++ using C++98 as standard. There are things not available in C++98, including, e.g. nullptr. In some cases Objective-C `nil` is defined as `nullptr` so this causes an evaluation failure. Switch the default to overcome this issue (actually, currently lldb evaluates both C++11 and C++14 as C++11, but that seems a larger change and definitely could be re-evaluated in the future). No test as this is currently failing on the LLDB bots after the clang switch (so, de facto, there's a test already for it). <rdar://problem/36011995> llvm-svn: 320761
Diffstat (limited to 'clang')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud