Displaying 2 results from an estimated 2 matches for "difinder".
Did you mean:
defender
2017 May 22
2
DebugInfo, Metadata usage
...el. (I've been reading some info
in LLVM Blog about metadata, in llvm docs about SourceLevel Debugging
with LLVM + StripSymbols.cpp, Metadata.cpp, DebugInfo.cpp)
I found that I can get it from DebugInfo or Metadata.
But my little research was not successful.
my code excerpt:
DebugInfoFinder DIFinder;
DIFinder.processModule(*M);
llvm::outs() << "Count of global Variables in Module : " <<
DIFinder.global_variable_count() << "\n";
for(DIGlobalVariableExpression *DIGVExpr : DIFinder.global_variables())
{
if(DIGlobalVariable *DIGV = DI...
2017 Jun 20
2
CloneFunctionInto produces invalid debug info
I was just going to say: With well-formed debug info it should create a deep copy up until the DISubprogram, but no further. But because the DISubprogram linked to the Function is missing the special handling of the DISubprogram (that would prohibit cloning the DICompileUnit is side-stepped).
But then I remembered the discussion we had in