-
Notifications
You must be signed in to change notification settings - Fork 4
WIP: LLVM 14.0.6 #1
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
Conversation
So, this compiles under armv7hl and i486, but fails under aarch64 with a reference to libz.so
I suppose I'll need to teach llvm to find this under |
You can ignore that, it comes from the |
You can ignore that, it comes from the
Can you check the ninja file, is libdir set correctly? |
It was indeed badly generated. Starting from a clean build directory, What's my best next step here; submit the packages to OBS and those as a repo to do my testing against? Manually installing all these RPMs in my targets is quite exhausting. I don't think I currently have an OBS account. |
What's my best next step here; submit the packages to OBS and those as a
repo to do my testing against? Manually installing all these RPMs in my
Yes please do so.
I can take the internal testing next week, over all this is good work.
|
I'm still trying to tackle an issue with Aarch64. By default, LLVM now emits LSE/out-of-line atomic calls, but these are not supported in GCC < 9.3.1. I'm testing a patch that disables out-of-line atomics on MeeGo vendors now. FWIW, I'm adding LLVM 14 and Rust 1.61 on my personal home-hosted repo for tests; I've scripted a bit around it. I hope you don't mind me re-organising the patch files a bit for easier rebases in the future. |
- return getArch() == llvm::Triple::x86_64; | ||
+ return true; | ||
} | ||
|
||
bool Generic_GCC::isPICDefault() const { | ||
-- | ||
2.20.1 | ||
|
||
+ if (getTriple().isMeeGo()) { | ||
+ return true; | ||
+ } | ||
switch (getArch()) { | ||
case llvm::Triple::aarch64: | ||
case llvm::Triple::ppc: |
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.
This was the most interesting conflict of the rebase. I'm not sure whether this still takes the commit message to heart .This might need some change in either the commit message or in the code (to replace it again with return true;
)
I just tested the 0006 patch, and it doesn't help. The resulting log of installing this version and trying to compile Could it be that Rust calls LLVM with just |
I have no idea what I am doing, but just wanted to leave this here, in case you were searching for it:
|
Found these indeed, but at no point are we using clang. The equivalent would be |
What's my best next step here; submit the packages to OBS and those as a
repo to do my testing against? Manually installing all these RPMs in my
Yes please do so.
I can take the internal testing next week, over all this is good work.
|
Is there any chance someone at Jolla can continue this work? I cannot seem to find a sizable slot in my schedule any time soon to fit the mental power to finish this up. Since it's apparently also needed for sailfishos/mesa#2, I suppose there's an incentive for Jolla to continue this work. |
Hi, I already did a test build of these and had to fix clang spec to make it build so maybe I can make a new PR or push to your branch. |
Glad you found a fix for the clang build. I've added you to my fork as collaborator, feel free to push to this branch if that's easy for you! It's very inaptly named |
Would it help to package gcc 12 or similar in parallel to the current gcc8? Has anyone started working on it or would I need to start from scratch? If so would you recommend starting from the current huge gcc8 rpm spec or from fedora or similar? |
Closing this as update was done in #2 |
LLVM 12+ is necessary for Rust 1.55+ sailfishos/rust#15
Nothing has been tested yet here. Just putting out the code. This one was easy to get to compile.
TODO: