dc94074a6c
This uses the Clang profiling config during the instrumentation step of a PGO build. This allows getting the profiling data out of the sandboxed processes. This is not an ideal end state, ideally the coverage configuration should be refactored and things common to the two configurations should be moved to a new base config. This requires to use the new version of goma, see go/ma-rbe-dogfood (see crbug.com/990981#c26 for more details). To build a PGInstrumented build (first step to do a PGO build) compile with the following GN args: is_component_build = false is_debug = false chrome_pgo_phase = 1 use_goma = true Bug: 1056189 Change-Id: I717efdcbb6993ad574acce4c0f91eb5fb5bf3972 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2076424 Commit-Queue: Sébastien Marchand <sebmarchand@chromium.org> Reviewed-by: Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#750258}
About
//build contains:
- Core GN templates and configuration
- Core Python build scripts
Since this directory is DEPS'ed in by some other repositories (webrtc, pdfium,
v8, etc), it should be kept as self-contained as possible by not referring
to files outside of it. Some exceptions exist (//testing, select
//third_party subdirectories), but new dependencies tend to break these other
projects, and so should be avoided.
Changes to //build should be landed in the Chromium repo. They will then be
replicated to the stand-alone build repo
by the gsubtreed tool.
Note: You can find all directories already available through gsubtreed in the
list of all chromium repos.
Contents
//build/config- Common templates via.gnifiles.//build/toolchain- GN toolchain definitions.Other .py files- Some are used by GN/Ninja. Some by gclient hooks, some are just random utilities.
Files referenced by //.gn:
//build/BUILDCONFIG.gn- Included by allBUILD.gnfiles.//build/secondary- An overlay forBUILD.gnfiles. Enables addingBUILD.gnto directories that live in sub-repositories.//build_overrides- Refer to //build_overrides/README.md.