-
Notifications
You must be signed in to change notification settings - Fork 97
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
[clang] enable lld #104
Comments
Also, probably need to verify that |
Also, the TCWG @ linaro is also testing with Clang+LLD on by default. |
Unless upstream arranges for clang builds to use lld by default we should probably keep coverage of builds with GNU LD since that's what people will be building if they just decide to go and build with clang. Testing with lld would definitely be good and I'm all in favour of adding it, I just worry about loosing coverage of the more standard case. A reference to the discussion with Arnd would be helpful. |
Video call, unrecorded.
Sure if someone just does But we'd like to build the kernel with more than just clang; we'd like to use all llvm utilities so we can catch regressions in them. I agree that In the meantime, we'd really like to get testing coverage with lld. |
Maybe we could build a handful of defconfigs with an I think this could be defined as part of the Docker image used to do the kernel builds (Debian alternatives, or env variables set up before calling make...). |
An "all LLVM tools" option now exists by setting LLVM=1 on the "make" command line. So now we could do GCC+bfd, Clang+bfd, and Clang+lld+all-other-LLVM-tools. |
Sounds like something we should be trying with linux-next on staging. |
per a discussion today with Arnd, it would be good to make the clang builds use
LD=ld.lld
for their linkers. The kernel really stresses LLD's linker script support, so it would be good to get it under coverage soon. Should work with arm64.The text was updated successfully, but these errors were encountered: