Displaying 5 results from an estimated 5 matches for "loadedobjinfo".
2020 May 26
2
[ORC JIT][MLIR] GDBRegistrationListener "second attempt to perform debug registration" assert
...saw this print and I then realized my “Adding” vs. “Registering” mistake.
// Run EventListener notifyLoaded callbacks.
{
std::lock_guard<std::mutex> Lock(RTDyldLayerMutex);
dbgs() << "Registering MemMgr " << MemMgr << "\n";
auto LOIItr = LoadedObjInfos.find(MemMgr);
assert(LOIItr != LoadedObjInfos.end() && "LoadedObjInfo missing");
for (auto *L : EventListeners) {
dbgs() << " key = " << reinterpret_cast<uintptr_t>(MemMgr) << "\n";
L->notifyObjectLoaded(...
2020 May 21
2
[ORC JIT][MLIR] GDBRegistrationListener "second attempt to perform debug registration" assert
...s#2=...,
>> __args#1=..., __args#0=<optimized out>, this=0x5555594e09b8) at
>> /usr/include/c++/7/bits/std_function.h:706
>>
>> #6 llvm::orc::RTDyldObjectLinkingLayer::onObjLoad (this=<optimized out>,
>> K=3, R=..., Obj=..., MemMgr=0x5555591c4160,
>> LoadedObjInfo=std::unique_ptr<llvm::RuntimeDyld::LoadedObjectInfo> = {...},
>>
>> Resolved=std::map with 8 elements = {...}, InternalSymbols=std::set
>> with 0 elements)
>>
>> at
>> /localdisk/adstraw/ngraph/build/mlir_project/llvm-project/llvm/lib/ExecutionEngin...
2020 Apr 16
4
ORC Assertion failure
...C++
libravi.dll!llvm::orc::RTDyldObjectLinkingLayer::onObjLoad(unsigned
__int64 K, llvm::orc::MaterializationResponsibility & R,
llvm::object::ObjectFile & Obj,
std::unique_ptr<llvm::RuntimeDyld::LoadedObjectInfo,std::default_delete<llvm::RuntimeDyld::LoadedObjectInfo>>
LoadedObjInfo, std::map<llvm::StringRef,llvm::JITEvaluatedSymbol,std::less<llvm::StringRef>,std::allocator<std::pair<llvm::StringRef
const ,llvm::JITEvaluatedSymbol>>> Resolved,
std::set<llvm::StringRef,std::less<llvm::StringRef>,std::allocator<llvm::StringRef>>
& In...
2020 May 20
2
[ORC JIT][MLIR] GDBRegistrationListener "second attempt to perform debug registration" assert
...RuntimeDyld::LoadedObjectInfo const&) const (__args#2=..., __args#1=..., __args#0=<optimized out>, this=0x5555594e09b8) at /usr/include/c++/7/bits/std_function.h:706
#6 llvm::orc::RTDyldObjectLinkingLayer::onObjLoad (this=<optimized out>, K=3, R=..., Obj=..., MemMgr=0x5555591c4160, LoadedObjInfo=std::unique_ptr<llvm::RuntimeDyld::LoadedObjectInfo> = {...},
Resolved=std::map with 8 elements = {...}, InternalSymbols=std::set with 0 elements)
at /localdisk/adstraw/ngraph/build/mlir_project/llvm-project/llvm/lib/ExecutionEngine/Orc/RTDyldObjectLinkingLayer.cpp:267
A little debug...
2015 Jun 04
2
[LLVMdev] MCJit interface question
When we were using MCJIT, I could do this:
// Attach the event listener
Context.EE->RegisterJITEventListener(
LLILCJitEventListener::createLLILCJitEventListener(
new LLILCJitEventWrapper(&Context)));
The event listeners listened for when an object is emitted (NotifyObjectEmitted), and that’s when we’d go through and extract debug info from the ObjectFile. Now, I imagine