-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PPC doesn't support non-lazy JIT compilation #5188
Comments
I'm pretty sure you're correct that the eager JIT only exists on x86. It doesn't look that hard to implement emitFunctionStubAtAddr given emitFunctionStub (with some thought, maybe we can unify them), but I don't have a PPC or ARM to test on, so I'm a bit reluctant to try it myself. Would you be interested in taking a shot at the implementation? If not, I may be able to find a machine to test on or use the buildbots as guinea pigs. |
For PPC and ARM there are some Linux machines on the compile farm.
I may have some time for this late next week. |
I may wind up fixing this as part of the redesign for llvm/llvm-bugzilla-archive#5201 , so don't waste time working on it yet. |
Possible fix |
@llvm/issue-subscribers-backend-powerpc |
Hmm, this issue is from 14 years ago. I imagine it is no longer valid especially since it references an assert in a file that no longer exists. |
Extended Description
Disabling lazy compilation fails on PPC:
Release/bin/lli -disable-lazy-compilation ~/x.bc
Assertion failed: (0 && "This target doesn't implement emitFunctionStubAtAddr!"), function emitFunctionStubAtAddr, file /Users/acab/clamav-devel/libclamav/llvm/llvm/include/llvm/Target/TargetJITInfo.h, line 65.
0 lli 0x0065d50c llvm::sys::RWMutexImpl::writer_release() + 476
1 lli 0x0065dddc llvm::sys::RemoveFileOnSignal(llvm::sys::Path const&, std::string*) + 1244
2 libSystem.B.dylib 0x92f639fc _sigtramp + 68
Stack dump:
0. Program arguments: Release/bin/lli -disable-lazy-compilation /Users/acab/x.bc
Abort trap
It seems that X86 is the only target that implements that method.
In this case it is simply a matter of ordering the functions bottom-up according to the callgraph, and then non-lazy compilation should succeeed on the Mac too in this case, BUT it would fail for mutually recursive functions.
Is there a workaround that doesn't need emitFunctinStubAtAddr, or should I just always use lazy compilation on Mac/PPC? (rather anything non-X86?)
The text was updated successfully, but these errors were encountered: