зеркало из https://github.com/mozilla/gecko-dev.git
c7dcbe9387
Currently, in LTO builds, we use the new pass manager during the initial translation to bitcode but not for the final optimization during linking. On Linux, we can enable the new pass manager during LTO with a plugin option. I've landed a patch upstream to allow it on Windows as well, which is included here. Switching the pass manager brings speed improvements on its own, but it also reduces code size by ~6%, which we can use a portion of as budget to increase the import limit (via the hot multiplier) for even more speed improvements. Differential Revision: https://phabricator.services.mozilla.com/D96108 |
||
---|---|---|
.. | ||
README | ||
android-mangling-error.patch | ||
bug-1605181-isConstexpr.patch | ||
bug-1606630-if_constexpr.patch | ||
bug47258-extract-symbols-mbcs.patch | ||
build-clang.py | ||
clang-5.0-linux64.json | ||
clang-7-linux64.json | ||
clang-10-linux64.json | ||
clang-11-android.json | ||
clang-11-linux64-aarch64-cross.json | ||
clang-11-linux64.json | ||
clang-11-macosx64.json | ||
clang-11-mingw.json | ||
clang-11-win64-2stage.json | ||
clang-11-win64.json | ||
clang-android.json | ||
clang-linux64-aarch64-cross.json | ||
clang-linux64.json | ||
clang-macosx64.json | ||
clang-tidy-ci.patch | ||
clang-tidy-external-linux64.json | ||
clang-tidy-linux64.json | ||
clang-tidy-macosx64.json | ||
clang-tidy-no-errors.patch | ||
clang-tidy-win64.json | ||
clang-win64-2stage.json | ||
clang-win64.json | ||
clang_format_10.patch | ||
compiler-rt-cross-compile.patch | ||
compiler-rt-no-codesign.patch | ||
critical_section_on_gcov_flush-rG02ce9d8ef5a8.patch | ||
downgrade-mangling-error.patch | ||
find_symbolizer_linux.patch | ||
find_symbolizer_linux_clang_10.patch | ||
llvmorg-10-init-5191-ga84b200e604-windows-pgo.patch | ||
llvmorg-11-init-4265-g2dcbdba8540.patch | ||
llvmorg-11-init-4265-g2dcbdba8540_clang_10.patch | ||
llvmorg-11-init-15486-gfc937806efd-dont-jump-to-landing-pads.patch | ||
llvmorg-12-init-10926-gb79e990f401-LTO-new-pass-manager.patch | ||
loosen-msvc-detection.patch | ||
r350774.patch | ||
rG7e18aeba5062.patch | ||
rG7e18aeba5062_clang_10.patch | ||
rename_gcov_flush.patch | ||
rename_gcov_flush_7.patch | ||
rename_gcov_flush_clang_10.patch | ||
rename_gcov_flush_clang_11.patch | ||
revert-r362047-and-r362065.patch | ||
static-llvm-symbolizer.patch | ||
tsan-hang-be41a98ac222.patch | ||
tsan-hang-be41a98ac222_clang_10.patch | ||
unpoison-thread-stacks.patch | ||
unpoison-thread-stacks_clang_10.patch |
README
build-clang.py ============== A script to build clang from source. ``` usage: build-clang.py [-h] -c CONFIG [--clean] optional arguments: -h, --help show this help message and exit -c CONFIG, --config CONFIG Clang configuration file --clean Clean the build directory ``` Pre-requisites -------------- * Working build toolchain. * git * CMake * Ninja * Python 2.7 and 3 Please use the latest available CMake for your platform to avoid surprises. Config file format ------------------ build-clang.py accepts a JSON config format with the following fields: * stages: Use 1, 2, 3 or 4 to select different compiler stages. The default is 3. * python_path: Path to the Python 2.7 installation on the machine building clang. * gcc_dir: Path to the gcc toolchain installation, only required on Linux. * cc: Path to the bootsraping C Compiler. * cxx: Path to the bootsraping C++ Compiler. * as: Path to the assembler tool. * ar: Path to the library archiver tool. * ranlib: Path to the ranlib tool (optional). * libtool: Path to the libtool tool (optional). * ld: Path to the linker. * patches: Optional list of patches to apply. * build_type: The type of build to make. Supported types: Release, Debug, RelWithDebInfo or MinSizeRel. * build_libcxx: Whether to build with libcxx. The default is false. * build_clang_tidy: Whether to build clang-tidy with the Mozilla checks imported. The default is false. * osx_cross_compile: Whether to invoke CMake for OS X cross compile builds. * assertions: Whether to enable LLVM assertions. The default is false. * pgo: Whether to build with PGO (requires stages == 4). The default is false. The revisions are defined in taskcluster/ci/fetch/toolchains.yml. They are usually commit sha1s corresponding to upstream tags. Environment Variables --------------------- The following environment variables are used for cross-compile builds targeting OS X on Linux. * CROSS_CCTOOLS_PATH: Path to the cctools directory where the cross compiler toolchain is located. * CROSS_SYSROOT: Path to the OS X SDK directory for cross compile builds.