commit | db347988dfd1b4b8cd5685de63d937f2ffa76b25 | [log] [tgz] |
---|---|---|
author | Googler <noreply@google.com> | Wed Jun 28 13:26:34 2023 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Wed Jun 28 13:27:48 2023 -0700 |
tree | db7b3d72a7002f65cb5946854680e3ba517a4596 | |
parent | 9092303c358b87c1e027abafe135c44a27531b36 [diff] |
Add thinlto support for tree artifacts Add a new feature to bazel: use_lto_native_object_directory. When this feature is enabled, the thinlto objects are stored in a different directory as the .imports and .thinlto.bc file outputs from the indexing action, and thinlto can be used in the presence of tree artifacts. Create LtoBackendActionTemplate.java to generate lto backend actions to tree artifact. Minor: move constants to rules/cpp/CppFileTypes.java and rules/cpp/CppHelper.java for consistency. Limitations: There is still no support for .dwo files for tree artifacts, i.e. compiling using fission. TreeArtifacts do not generate minimized bitcode files, only full bitcode files, because of lack of support at the indexing stage. PiperOrigin-RevId: 544144581 Change-Id: Idc6a638a6fccef6912b79948ea167dd6e651f156
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md