audk/BaseTools/Conf
Ard Biesheuvel ecb1d67775 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>
2024-07-28 20:45:13 +00:00
..
XMLSchema BaseTools: Fix various typos 2019-07-08 08:59:29 +08:00
Empty_Package_Information_Data_File.ini BaseTools: Replace BSD License with BSD+Patent License 2019-04-09 09:10:20 -07:00
ReadMe.txt BaseTools: Clean up source files 2018-07-09 10:25:47 +08:00
build_rule.template BaseTools: Remove the CLANGCC build rule for Hii-Binary-Package.UEFI_HII 2023-05-10 09:45:17 +00:00
diff.order BaseTools: convert diff.order to LF-only 2020-07-03 11:20:01 +00:00
gitattributes BaseTools/Conf/gitattributes: fix "--function-context" for C source code 2020-01-31 16:13:06 +00:00
target.template BaseTools/Conf/target.template: Use VS2019 as default tool chain 2023-11-29 20:44:12 +00:00
tools_def.template BaseTools/tools_def CLANGDWARF: Always use -Oz in RELEASE mode 2024-07-28 20:45:13 +00:00

ReadMe.txt

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

This directory contains the template files for the next generation of the
EDK II Build infrastructure.  These files will be copied into the WORKSPACE's
Conf directory if and only if the target files do not exist.

These files may be updated frequently.

The XMLSchema directory contains the EDK II Packaging XML definitions.  The
schema may change in the future.  It differs somewhat from the early versions
of the XML Schema.