[PA] Introduce Clang AllocToken's TypeFuncHash mode Switch AllocToken from the default typehashpointersplit mode to typefunchashpointersplit. The typefunchashpointersplit derives the token from both the allocated type and the name of the function containing the allocation, providing finer-grained tokens. To compile PartitionAlloc's tests with the production token mode rather than Clang's default one, stop excluding all of PartitionAlloc from instrumentation. Only allocator_shim, which defines the __alloc_token_* functions, is still excluded via a new allocator_shim_remove_configs. As __builtin_infer_alloc_token() cannot be used in constant expressions in this mode, the test tokens are now returned by helper functions instead of constexpr variables. Bug: 477186304 Change-Id: I14309580fb0b5ebf8c844af8921117f44ed80986 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8603136 Mega-CQ: Ai Nozaki <ainozaki@google.com> Commit-Queue: Ai Nozaki <ainozaki@google.com> Reviewed-by: Mikihito Matsuura <mikt@google.com> Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Reviewed-by: Stephen Nusko <nuskos@chromium.org> Cr-Commit-Position: refs/heads/main@{#1734513} NOKEYCHECK=True GitOrigin-RevId: ae0b25bdd57f2ede7e51fe9d6eef2c4ab39f466e
This directory is used to allow different products to customize settings for repos that are DEPS'ed in or shared.
For example: V8 could be built on its own (in a “standalone” configuration), and it could be built as part of Chromium. V8 might define a top-level target, //v8:d8 (a simple executable), that should only be built in the standalone configuration. To figure out whether or not it should be in a standalone configuration, v8 can create a file, build_overrides/v8.gni, that contains a variable, build_standalone_d8 = true. and import it (as import(“//build_overrides/v8.gni”) from its top-level BUILD.gn file.
Chromium, on the other hand, might not need to build d8, and so it would create its own build_overrides/v8.gni file, and in it set build_standalone_d8 = false.
The two files should define the same set of variables, but the values can vary as appropriate to the needs of the two different builds.
The build.gni file provides a way for projects to override defaults for variables used in //build itself (which we want to be shareable between projects).
TODO(crbug.com/41240413): Ideally //build_overrides and, in particular, //build_overrides/build.gni should go away completely in favor of some mechanism that can re-use other required files like //.gn, so that we don't have to keep requiring projects to create a bunch of different files to use GN.