-
Notifications
You must be signed in to change notification settings - Fork 2.4k
infra: use LLD for all configurations #13203
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
base: master
Are you sure you want to change the base?
Conversation
kasper93 has previously contributed to projects/ffmpeg. The previous PR was #13175 |
/gcbrun trial_build.py all --sanitizer address --fuzzing-engine libfuzzer |
This makes it consistent to use LLD across all configurations. It also moves away from using gold linker, which has recently been deprecated. On top of that LLD is faster and has better compatibility with LLVM toolchain that is already used for building. This commit also fixes warnings that can sometimes occur with BFD linker that doesn't fully support DWARF 5, at least the version on the builder: DWARF: invalid or unhandled FORM value: 0x22 Some projects already replaced linker in their build scripts for this reason.
Added missing |
Are we using lld by default? I'm not sure we are, but I haven't looked. |
The proposal is to use LLD by default. I've outlined the main reason in commit message. Currently BFD linker is used, with some jobs using GOLD. Idea is to unify and modernize to use LLD. |
This makes it consistent to use LLD across all configurations. It also moves away from using gold linker, which has recently been deprecated.
On top of that LLD is faster and has better compatibility with LLVM toolchain that is already used for building.
This commit also fixes warnings that can sometimes occur with BFD linker that doesn't fully support DWARF 5, at least the version on the builder: DWARF: invalid or unhandled FORM value: 0x22
Some projects already replaced linker in thier build scripts for this reason.