diff options
| author | Ard Biesheuvel <ard.biesheuvel@linaro.org> | 2017-09-16 02:06:02 +0300 |
|---|---|---|
| committer | Ard Biesheuvel <ard.biesheuvel@linaro.org> | 2017-09-19 19:39:48 +0300 |
| commit | 424a5ec33b3d5a842bff3f4695d0bd709c91a163 (patch) | |
| tree | 7426172580e72d4d3f4e57a51b84191232b80042 /BaseTools/Source/Python/Common/Database.py | |
| parent | 4bbcc285d5f74d34ec40733dde807f5a4f0cdf8c (diff) | |
| download | edk2-424a5ec33b3d5a842bff3f4695d0bd709c91a163.tar.xz | |
BaseTools/tools_def AARCH64: enable frame pointers for RELEASE builds
Commit 8f0b62a5dac0 ("BaseTools/tools_def AARCH64: enable frame pointers
for DEBUG builds") removed the -fomit-frame-pointer switch from the CFLAGS
definitions that are shared between AARCH64 DEBUG and RELEASE builds, and
moved it to the RELEASE specific ones, so that DEBUG builds can produce a
backtrace when a crash occurs.
This is actually a useful thing to have for RELEASE builds as well. AArch64
has 30 general purpose registers, and so the performance hit of having a
frame pointer is unlikely to be noticeable, nor are the additional 8 bytes
of stack space likely to present a problem.
So remove -fomit-frame-pointer altogether this time.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Reviewed-by: Leif Lindholm <leif.lindholm@linaro.org>
Reviewed-by: Liming Gao <liming.gao@intel.com>
Diffstat (limited to 'BaseTools/Source/Python/Common/Database.py')
0 files changed, 0 insertions, 0 deletions
