Google Git
Sign in
bazel/rules_cc/5bcfcf78a7aefbbae3c55a3d1989b22c7d141a18
commit
5bcfcf78a7aefbbae3c55a3d1989b22c7d141a18
[log]
author
Alex Bakon <abakon@netflix.com>
Fri Aug 14 01:37:11 2026 -0700
committer
Copybara-Service <copybara-worker@google.com>
Fri Aug 14 01:38:36 2026 -0700
tree
30944305064dc3a1bc70a01eb5625f2484cd2b4d
parent
d27efa119e41d74243da34da24b86281811b6f7d [diff]
Pass fission flags to ThinLTO backend actions (#837)

Fix interaction between `--fission` and `--features=thin_lto`. Without this, every LTO backend action fails:

```
ERROR: output 'prog.lto/bazel-out/k8-opt/bin/_objs/prog/a.dwo' was not created
ERROR: LTO Backend Compile prog.lto/bazel-out/k8-opt/bin/_objs/prog/a.o failed:
       not all outputs were created or valid
```

Fixed by adding `ACTION_NAMES.lto_backend` to the `per_object_debug_info` flag_set in
`cc/private/toolchain/unix_cc_toolchain_config.bzl` and `cc/private/toolchain_config/legacy_features.bzl`.

Adds a test that uses the real Linux `cc_toolchain_config` since that wasn't covered by the existing test, and was broken.

Closes #837

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/837 from akonradi:abakon/fission-flags-for-lto-backend c033aba8813345a9c84a3f48cf11fb9bf970774d
PiperOrigin-RevId: 964562193
Change-Id: I09f0c92967f5d148dfa24edca0533e306a2647bb
5 files changed
tree: 30944305064dc3a1bc70a01eb5625f2484cd2b4d
  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. local_bazel.bzl
  19. MODULE.bazel
  20. README.md
  21. WORKSPACE
  22. WORKSPACE.bzlmod
README.md

C++ rules for Bazel

  • Postsubmit Build status

This repository contains C, C++, and Objective-C language support for the Bazel build system.

For this module's main reference, see the Bazel documentation.

Get Started

Install Bazel

Follow the official instructions to Install Bazel.

Add rules_cc to your MODULE.bazel

Add the latest release to your MODULE.bazel project file.

Declare a build target

In a BUILD.bazel file, import and use the rules:

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

cc_binary(
    name = "hello_world",
    srcs = ["hello_world.cc"],
)

Build and run your project

Build and run your C/C++ binary with one command:

$ bazel run hello_world

To build the project without running the binary, use Bazel's build subcommand:

$ bazel build hello_world

Toolchains

Default autoconfigured toolchain

rules_cc includes an auto-configured toolchain that uses the local compiler installed on the host machine.

You can disable the autoconfigured C/C++ toolchain by adding the following Bazel flag to your project's .bazelrc file:

--repo_env=BAZEL_DO_NOT_DETECT_CPP_TOOLCHAIN=1

Hermetic toolchains

Configuring a hermetic toolchain makes your build more deterministic. rules_cc itself does not yet offer a hermetic toolchain distribution. Other community owned and maintained projects offer hermetic C/C++ toolchains:

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: