Delete dead `FdoContext`, `PropellerOptimizeInputFile`, and unused Starlark C++ methods FDO configuration and C++ rule logic now live in Starlark (`fdo_context.bzl` and `rules_cc`), leaving `FdoContext`, `PropellerOptimizeInputFile`, `CcToolchainProvider.getFdoContext()`, `CcModule.convertFromNoneable()`, seven `@StarlarkMethod` helpers in `CcStarlarkInternal`, and two `CppConfiguration` flag helpers without active callers. PiperOrigin-RevId: 1024563161 Change-Id: I0bf6600e03f8205e79646f17006ec0f3d8934982
{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.
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