-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
Switch to LLVM ORC v2 #38008
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
Switch to LLVM ORC v2 #38008
Conversation
|
And OrcV1 is gone: http://lists.llvm.org/pipermail/llvm-dev/2020-October/145866.html |
|
remaining tasks are:
|
In LLVM.jl I had to normalize the triple before passing it to target https://github.com/maleadt/LLVM.jl/blob/b0780fa710219b1ca2e0a418d5dc82fa6dfafe71/src/orc.jl#L130-L134 |
|
I suppose, but we don't usually like the default triple, and the process triple that we use appears to already call normalize: https://llvm.org/doxygen/Host_8cpp_source.html#l01545 |
699482d to
94bd2b8
Compare
vchuravy
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me! Tried this on PPC as well.
Let's squash and GTM?
Ensures that this usage is proper even if using an LLVM assertions build, but not using FORCE_ASSERTIONS=1 in Julia
This should not be a user-visible change, but should prepare us for being able to use new APIs (the legacy ones are deleted now on LLVM master / v12).
DRY some variables, and pass others along better
Refs JuliaLang#38008 & JuliaLang#38785 (This reverts commit 599d329, and fixes a load ordering issue with our JuliaOJIT::addModule)
Mostly pretty mechanical. Some old hacks went away. Result seems to work, so is presumably good?