summaryrefslogtreecommitdiffstats
path: root/ArmVirtPkg/Library/ArmVirtPL031FdtClientLib
diff options
context:
space:
mode:
authorArd Biesheuvel <ardb@kernel.org>2024-07-28 18:50:09 +0200
committermergify[bot] <37929162+mergify[bot]@users.noreply.github.com>2024-07-28 20:45:13 +0000
commitecb1d67775a6dcaa9a0deb4869ca60e250987e91 (patch)
treea36594bc7e1b170479c76ae63d93826158ab92b7 /ArmVirtPkg/Library/ArmVirtPL031FdtClientLib
parentb7f963d570ec5e27bc04d546372c6fc47e4f3b17 (diff)
downloadedk2-ecb1d67775a6dcaa9a0deb4869ca60e250987e91.tar.gz
edk2-ecb1d67775a6dcaa9a0deb4869ca60e250987e91.tar.bz2
edk2-ecb1d67775a6dcaa9a0deb4869ca60e250987e91.zip
BaseTools/tools_def CLANGDWARF: Always use -Oz in RELEASE mode
GCC5 and CLANGDWARF for IA32/X64 use -Os or -Oz as the optimization level, which agressively optimizes for the smallest possible object code. On AARCH64, RISCV64 and ARM, we use -O3 instead, which results in considerable image bloat, to the point where the Raspberry Pi 4 build in edk2-platforms does not even build with -D SECURE_BOOT_ENABLE. So let's align CLANGDWARF across all architectures, and use -Oz throughout. Note that O3 is still used for the linker, which build in LTO mode and therefore performs some code generation as well. This is deliberate: LLD does not support the Os/Oz optimization levels at all, and using Oz for the compile pass is sufficient to reduce the code size substantially. Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
Diffstat (limited to 'ArmVirtPkg/Library/ArmVirtPL031FdtClientLib')
0 files changed, 0 insertions, 0 deletions