forked from OSchip/llvm-project
[ExpressionParser] Rollback C++98 as the standard for evaluating.
Some ubuntu bots are failing with this patch in, let me unblock while I investigate. llvm-svn: 320769
This commit is contained in:
parent
f157ad444c
commit
75dfd9a525
|
@ -381,15 +381,7 @@ ClangExpressionParser::ClangExpressionParser(ExecutionContextScope *exe_scope,
|
|||
// For now, the expression parser must use C++ anytime the
|
||||
// language is a C family language, because the expression parser
|
||||
// uses features of C++ to capture values.
|
||||
|
||||
// Clang now sets as default C++14 as the default standard (with
|
||||
// GNU extensions), so we do the same here to avoid mismatches that
|
||||
// cause compiler error when evaluating expressions (e.g. nullptr
|
||||
// not found as it's a C++11 feature). Currently lldb evaluates
|
||||
// C++14 as C++11 (see two lines below) so we decide to be consistent
|
||||
// with that, but this could be re-evaluated in the future.
|
||||
m_compiler->getLangOpts().CPlusPlus = true;
|
||||
m_compiler->getLangOpts().CPlusPlus11 = true;
|
||||
break;
|
||||
case lldb::eLanguageTypeObjC:
|
||||
m_compiler->getLangOpts().ObjC1 = true;
|
||||
|
|
Loading…
Reference in New Issue