diff options
| author | Peter Collingbourne <pcc@google.com> | 2022-09-07 15:03:57 -0700 |
|---|---|---|
| committer | Peter Collingbourne <pcc@google.com> | 2022-12-16 03:25:04 +0000 |
| commit | d7b056514e38f3ec9bf38f7a0c39e792def45c0b (patch) | |
| tree | d5b3aded256c773b03f56d8246ac55303fca6a1b | |
| parent | db399f6befedb2b312606635d2e4fe455408897c (diff) | |
| download | build-d7b056514e38f3ec9bf38f7a0c39e792def45c0b.tar.gz | |
build.sh: Set FRAME_WARN to 0 in LTO=none builds
In development builds such as sanitizer and LTO=none builds we may
end up with frame sizes that exceed the size limit due to compiler
implementation details. It is useful to enforce the limit in shipping
builds but not for these development builds.
We are already setting FRAME_WARN to 0 in KASan builds. Do likewise for
LTO=none builds.
Change-Id: Iefe991d5e6e231c3ee22ed313d7568d99a655619
(cherry picked from commit bfaf00f82aff51e06c01eb42bbcd6422d8ac1da0)
| -rwxr-xr-x | build.sh | 3 |
1 files changed, 2 insertions, 1 deletions
@@ -660,7 +660,8 @@ if [ "${LTO}" = "none" -o "${LTO}" = "thin" -o "${LTO}" = "full" ]; then -e LTO_NONE \ -d LTO_CLANG_THIN \ -d LTO_CLANG_FULL \ - -d THINLTO + -d THINLTO \ + --set-val FRAME_WARN 0 elif [ "${LTO}" = "thin" ]; then # This is best-effort; some kernels don't support LTO_THIN mode # THINLTO was the old name for LTO_THIN, and it was 'default y' |