Google Git
Sign in
bazel / bazel / b81ff5672743d5f51e520c71a2da2b78983e484d
commitb81ff5672743d5f51e520c71a2da2b78983e484d[log] [tgz]
authorGoogler <ilist@google.com>Fri Apr 19 05:32:42 2024 -0700
committerCopybara-Service <copybara-worker@google.com>Fri Apr 19 05:35:38 2024 -0700
tree4856f19a314b21d3a40236b217e5c017210d3eb3
parent8ee8f797e72898282a81993e012e7502ff1bf656 [diff]
Rollforward of https://github.com/bazelbuild/bazel/commit/ee24c6ecb79a25ef730e5a54f64de0a299464028: Rewrite FdoContext to Starlark

Rewrite FdoHelper class and CcInternal.fdo_context to Starlark. The code should be mostly identical to native implementation without semantic changes.

Change FdoContext, PropellerOptimizeInputFile classes to a lightweight containers for a Starlark implemented FdoContext. This keeps supporting the remaining native code until it's in Starlark as well. Some classes needed to pass through EvalException because of this.

Expose necessary configuration fields: fdo_path, cs_fdo_path, propeller_optimize_absolute_{cc,ld}_profile to builtins. Necessary to rewrite the code.

NEW: Added "toolchain" parameter to the actions and testing it with --incompatible_auto_exec_groups flag
PiperOrigin-RevId: 626337032
Change-Id: If3aebaefd471e29a53a0b1b4dba1ed905198e0b3
20 files changed
tree: 4856f19a314b21d3a40236b217e5c017210d3eb3
  1. .bazelci/
  2. .github/
  3. examples/
  4. scripts/
  5. site/
  6. src/
  7. third_party/
  8. tools/
  9. .bazelrc
  10. .bazelversion
  11. .gitattributes
  12. .gitignore
  13. AUTHORS
  14. bazel_downloader.cfg
  15. BUILD
  16. CHANGELOG.md
  17. CODE_OF_CONDUCT.md
  18. CODEOWNERS
  19. combine_distfiles.py
  20. combine_distfiles_to_tar.sh
  21. compile.sh
  22. CONTRIBUTING.md
  23. CONTRIBUTORS
  24. distdir.bzl
  25. extensions.bzl
  26. LICENSE
  27. maven_install.json
  28. MODULE.bazel
  29. MODULE.bazel.lock
  30. rbe_extension.bzl
  31. README.md
  32. repositories.bzl
  33. requirements.txt
  34. SECURITY.md
  35. WORKSPACE
  36. WORKSPACE.bzlmod
  37. workspace_deps.bzl
README.md

Bazel

{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.

Getting Started

Documentation

Reporting a Vulnerability

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.

Contributing to Bazel

See CONTRIBUTING.md

Build status