Lines Matching +full:gcc +full:- +full:pgo
2 # Use of this source code is governed by a BSD-style license that can be
10 import("//build/config/compiler/pgo/pgo.gni")
34 # In late bring-up on macOS (see docs/mac_lld.md).
49 # With GCC, warnings in no-Chromium code are always not treated as errors.
59 # -1 means auto-set according to debug/release and platform.
60 symbol_level = -1
62 # Android-only: Strip the debug info of libraries within lib.unstripped to
74 # gcc >= 4.8 or clang.
75 # http://gcc.gnu.org/wiki/DebugFission
79 # Enables support for ThinLTO, which links 3x-10x faster than full LTO. See
80 # also http://blog.llvm.org/2016/06/thinlto-scalable-and-incremental-lto.html
81 # Use it by default on official-optimized android and Chrome OS builds, but
82 # not ARC or linux-chromeos since it's been seen to not play nicely with
109 # For unofficial (e.g. development) builds and non-Chrome branded (e.g. Cronet
122 # Mark binaries as compatible with Shadow Stack of Control-flow Enforcement
125 # performed as mitigation against Return-oriented programming (ROP).
126 # https://chromium.googlesource.com/chromium/src/+/main/docs/design/sandbox.md#cet-shadow-stack
130 # enables the ML inliner when targeting Android for a size-optimized build.
171 # 32-bit builds (https://bugs.llvm.org/show_bug.cgi?id=18505) so disable them
177 # 64-bit Windows ABI doesn't support frame pointers.
215 # Windows 32-bit does provide frame pointers, but the compiler does not
236 …googlesource.com/chromium/src/+/main/docs/linux/debugging.md#Source-level-debug-with-fdebug_compil…
265 # TODO: https://issues.chromium.org/40120210 - remove this
277 assert(symbol_level >= -1 && symbol_level <= 2, "Invalid symbol_level")
278 if (symbol_level == -1) {
285 # turned on by --internal.
314 # Non-component debug builds with symbol_level = 2 are an undesirable (very slow
315 # build times, almost two-minute link times) combination. This is only checked
327 "Can't do non-component debug builds at symbol_level=2 without use_debug_fission=true")
331 # ml64.exe needs to be utilized as llvm-ml cannot yet assemble it. Once llvm-ml