| commit | 132a5f96d08b616ae9cda636eced1b7317a751e9 | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Wed Mar 08 12:25:43 2023 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Mar 08 12:27:21 2023 -0800 |
| tree | 4c6eb50431c958087feec15d95ab870708b0efed | |
| parent | 735539779287334ae1dcb585f5b90e902c6bf9fe [diff] |
Have getFdoBuildStamp return "SAFDO" when a .afdo profile is supplied along with xbinary_fdo. This change enables the fdo_type build stamp to be set to SAFDO in order to distinguish and track the prevalence of SAFDO in the fleet. As an alternative to this implementation, I also considered defining an SAFDO build feature and using a new file extention to identify SAFDO file. This CL is here unknown commit. I decided this implementation is preferable since from a blaze perspective, SAFDO is really no different that AFDO and adding a SAFDO build feature resulted in a huge amount of duplicate boilerplate code. The method used in this CL has the downside of relying on an implementation detail of SAFDO (SAFDO is afdo with xbinary_fdo set) but I think it is overall better due to to how much smaller a change it is but I am open to feedback. See[] PiperOrigin-RevId: 515109461 Change-Id: Idc515b058eaf0659556eb381a44fe3618e8eb435
{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
