Google Git
Sign in
pigweed/third_party/github/bazelbuild/rules_cc/943f3b07b58d47b0175b0d103059f29d6d1b0491
commit
943f3b07b58d47b0175b0d103059f29d6d1b0491
[log]
author
David Zbarsky <dzbarsky@gmail.com>
Mon Dec 08 19:06:36 2025 -0800
committer
Copybara-Service <copybara-worker@google.com>
Mon Dec 08 19:08:04 2025 -0800
tree
787445805440a5399c86ac05654a20bc1b15be87
parent
e912015aff2a86c655df77be7295cdc713e0e7fb [diff]
perf: Hoist common analysis work out of create_lto_backend_artifacts

Copybara Import from https://github.com/bazelbuild/rules_cc/pull/508

BEGIN_PUBLIC
perf: Hoist common analysis work out of create_lto_backend_artifacts (#508)

This work was duplicated.

Before:
<img width="1687" height="417" alt="image" src="https://github.com/user-attachments/assets/741f7f47-83c8-45d1-8d66-97bc04b2ce01" />

After:
<img width="1677" height="436" alt="image" src="https://github.com/user-attachments/assets/94247dc1-2d2d-4c02-8a27-42f19c5dc33c" />

Closes #508
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/508 from dzbarsky:zbarsky/cc-lto a58e7d1e92f58472a6d16d23f13b6d5b16af6c1e
PiperOrigin-RevId: 842004532
Change-Id: I7740e833f7e1595b3426f24764f7ce58aba71a50
2 files changed
tree: 787445805440a5399c86ac05654a20bc1b15be87
  1. .bazelci/
  2. .bcr/
  3. .github/
  4. cc/
  5. docs/
  6. examples/
  7. tests/
  8. .bazelignore
  9. .bazelrc
  10. .gitignore
  11. AUTHORS
  12. BUILD
  13. CODEOWNERS
  14. CONTRIBUTING.md
  15. googletest.patch
  16. ISSUE_TEMPLATE.md
  17. LICENSE
  18. MODULE.bazel
  19. README.md
  20. renovate.json
  21. WORKSPACE
  22. WORKSPACE.bzlmod
README.md

C++ rules for Bazel

  • Postsubmit Build status

This repository contains a Starlark implementation of C++ rules in Bazel.

The rules are being incrementally converted from their native implementations in the Bazel source tree.

For the list of C++ rules, see the Bazel documentation.

Getting Started

Add the following to your WORKSPACE file:

load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")

http_archive(
    name = "rules_cc",
    urls = ["https://github.com/bazelbuild/rules_cc/archive/refs/tags/<VERSION>.tar.gz"],
    sha256 = "...",
)

Then, in your BUILD files, import and use the rules:

load("@rules_cc//cc:defs.bzl", "cc_library")

cc_library(
    ...
)

Using the rules_cc toolchain

This repo contains an auto-detecting toolchain that expects to find tools installed on your host machine. This is non-hermetic, and may have varying behaviors depending on the versions of tools found.

There are third-party contributed hermetic toolchains you may want to investigate:

If you'd like to use the cc toolchain defined in this repo, add this to your WORKSPACE after you include rules_cc:

load("@rules_cc//cc:repositories.bzl", "rules_cc_dependencies", "rules_cc_toolchains")

rules_cc_dependencies()

rules_cc_toolchains()

Migration Tools

This repository also contains migration tools that can be used to migrate your project for Bazel incompatible changes.

Legacy fields migrator

Script that migrates legacy crosstool fields into features (incompatible flag, tracking issue).

TLDR:

bazel run @rules_cc//tools/migration:legacy_fields_migrator -- \
  --input=my_toolchain/CROSSTOOL \
  --inline

Contributing

Bazel and rules_cc are the work of many contributors. We appreciate your help!

To contribute, please read the contribution guidelines: CONTRIBUTING.md.

Note that the rules_cc use the GitHub issue tracker for bug reports and feature requests only. For asking questions see: