gamzinav/cling
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Clang diagnostics cause havoc, disable until understood.

Browse Source
This commit is contained in:
Vassil Vassilev 2014-06-04 11:59:12 +02:00 committed by sftnight
parent 62a7f2c934
commit 21d9481ce0
1 changed files with 8 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
lib/Interpreter/IncrementalExecutor.cpp
View File

@ -265,13 +265,15 @@ IncrementalExecutor::executeFunction(llvm::StringRef funcname,
llvm::SmallVector<llvm::Function*, 128> funcsToFree;
for (std::set<std::string>::const_iterator i = m_unresolvedSymbols.begin(),
e = m_unresolvedSymbols.end(); i != e; ++i) {
unsigned diagID = m_Diags.getCustomDiagID(clang::DiagnosticsEngine::Error,
"%0 unresolved while jitting %1");
m_Diags.Report(diagID) << *i << funcname; // TODO: demangle the names.
// FIXME: This causes a lot of test failures, for some reason it causes
//unsigned diagID = m_Diags.getCustomDiagID(clang::DiagnosticsEngine::Error,
// "%0 unresolved while jitting %1");
// the call to HandleMissingFunction to be elided.
//m_Diags.Report(diagID) << *i << funcname; // TODO: demangle the names.
// llvm::errs() << "IncrementalExecutor::executeFunction: symbol '" << *i
// << "' unresolved while linking function '" << funcname
// << "'!\n";
llvm::errs() << "IncrementalExecutor::executeFunction: symbol '" << *i
<< "' unresolved while linking function '" << funcname
<< "'!\n";
llvm::Function *ff = m_engine->FindFunctionNamed(i->c_str());
// i could also reference a global variable, in which case ff == 0.
if (ff)