Displaying 3 results from an estimated 3 matches for "rtdyldobjectlinkinglayerbase".
2017 Aug 24
1
Invalid Signature of orc::RTDyldObjectLinkingLayer::NotifyLoadedFtor
... const RuntimeDyld::LoadedObjectInfo
&L) {}
It doesn't break OrcMCJITReplacement as it duplicates the issue and the
Info parameter remains unused:
$ grep -h -r -A 4 -B 2 "const LoadedObjectInfo &Info"
./lib/ExecutionEngine/Orc/OrcMCJITReplacement.h
void operator()(RTDyldObjectLinkingLayerBase::ObjHandleT H,
const RTDyldObjectLinkingLayer::ObjectPtr &Obj,
const LoadedObjectInfo &Info) const {
M.UnfinalizedSections[H] =
std::move(M.SectionsAllocatedSinceLastLoad);
M.SectionsAllocatedSinceLastLoad = SectionAddrSet();
M.MemMg...
2017 Aug 06
2
Compile issues with LLVM ORC JIT
...6_64-linux-gnu/6.3.0/../../../../include/c++/6.3.0/backward
/usr/local/include /usr/local/bin/../lib/clang/4.0.1/include
/usr/include/x86_64-linux-gnu /usr/include Endof search list.|
The error I get is this:
error: unknown type name 'RTDyldObjectLinkingLayer'; did you mean
'RTDyldObjectLinkingLayerBase'?
Moreover, I get more errors. This tells me something is wrong with the
templating.
error: too many template arguments for class template
'IRCompileLayer' IRCompileLayer CompileLayer;
Another error with regards to RTDyldObjectLinkingLayer:
error: too many template argu...
2018 Nov 05
2
ORC JIT api, object files and stackmaps
Hi Christian
Your use case seems to have similar requirements as remote JITing in
ORC. So far I haven't used that part myself and I am sure Lang can tell
you much more about it. However, this comment on the
RemoteObjectClientLayer class sounds promising for your questions (1)
and (2):
/// Sending relocatable objects to the server (rather than fully relocated
/// bits) allows JIT'd code