[llvm-bugs] [Bug 36896] New: Orc C Bindings crash on platforms without lazy loading support
via llvm-bugs
llvm-bugs at lists.llvm.org
Sun Mar 25 21:43:50 PDT 2018
https://bugs.llvm.org/show_bug.cgi?id=36896
Bug ID: 36896
Summary: Orc C Bindings crash on platforms without lazy loading
support
Product: libraries
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: OrcJIT
Assignee: unassignedbugs at nondot.org
Reporter: andres at anarazel.de
CC: llvm-bugs at lists.llvm.org
Hi,
Even when not using LLVMOrcAddLazilyCompiledIR() Orc crashes on platforms
without indirect stub support. The reason for that is that its constructor
dereferences a nullptr functor (IndirectStubsMgrBuilder):
OrcCBindingsStack(TargetMachine &TM,
std::unique_ptr<CompileCallbackMgr> CCMgr,
IndirectStubsManagerBuilder IndirectStubsMgrBuilder)
: ES(SSP), DL(TM.createDataLayout()),
IndirectStubsMgr(IndirectStubsMgrBuilder()), CCMgr(std::move(CCMgr)),
which is invoked by:
LLVMOrcJITStackRef LLVMOrcCreateInstance(LLVMTargetMachineRef TM) {
TargetMachine *TM2(unwrap(TM));
Triple T(TM2->getTargetTriple());
auto CompileCallbackMgr = orc::createLocalCompileCallbackManager(T, 0);
auto IndirectStubsMgrBuilder =
orc::createLocalIndirectStubsManagerBuilder(T);
OrcCBindingsStack *JITStack = new OrcCBindingsStack(
*TM2, std::move(CompileCallbackMgr), IndirectStubsMgrBuilder);
return wrap(JITStack);
}
std::function<std::unique_ptr<IndirectStubsManager>()>
createLocalIndirectStubsManagerBuilder(const Triple &T) {
switch (T.getArch()) {
default: return nullptr;
...
}
So, if any orc is used on a platform (e.g. powerpc) without stub support, orc
can't be used in eager support either.
It's not hard to fix this. We can either make
createLocalIndirectSubsManagerBuilder() return
orc::LocalIndirectStubsManager<orc::OrcGenericABI>>(); or have the C stack not
construct IndirectStubsMgr until necessary. Any preference?
I'd be awesome if we could get this fixed for 6.1, this is currently breaking
postgres' JIT on PPC.
I'm planning to update the orc unittests so a) they actually test aarch64,
given that that should now be fully supported. b) split the tests into indirect
/ no jit at all capability, so crashes like this can be detected automatically
in the future.
--
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20180326/ebb8e8c2/attachment.html>
More information about the llvm-bugs
mailing list