Closed Bug 1751839 Opened 2 years ago Closed 2 years ago

Separate out the clang stage 1 build as an independent task

Categories

(Firefox Build System :: Toolchains, task)

task

Tracking

(firefox98 fixed)

RESOLVED FIXED
98 Branch
Tracking Status
firefox98 --- fixed

People

(Reporter: glandium, Assigned: glandium)

References

Details

Attachments

(5 files)

No description provided.

This will allow to decouple the clang toolchain used for toolchain builds
and Firefox.

This allows to start building other toolchains, compiler runtimes, much
earlier, since we don't have to wait for a complete 4-stage-optimized
compiler to start these, while the output produced by clang is
presumably the same whether it's a stage 1 or a stage 4 clang.

Blocks: 1751824
Pushed by mh@glandium.org:
https://hg.mozilla.org/integration/autoland/rev/e556e1a4a94e
Make most toolchains use a clang-toolchain alias instead of clang/clang-13. r=firefox-build-system-reviewers,andi
https://hg.mozilla.org/integration/autoland/rev/ea44d65e2de8
Don't build the gold linker plugin when not using a sysroot. r=firefox-build-system-reviewers,andi
https://hg.mozilla.org/integration/autoland/rev/acc91bf4e4f4
Add options to skip clang build stages. r=firefox-build-system-reviewers,andi
https://hg.mozilla.org/integration/autoland/rev/5c02a8fc256d
Build clang stage 1 as a separate task. r=firefox-build-system-reviewers,andi
See Also: → 1751929

We do want to use the llvm-symbolizer from the full clang build, which
has broader binary compatibility and is better guaranteed to match the
compiler used for builds that require llvm-symbolizer.

Pushed by malexandru@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/93e9c17940dc
Don't use clang-toolchain to derive llvm-symbolizer a=fix
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: