From 405f58b750c7d25358a42000f8505f69eccc60a7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Deuc=D0=B5?= <shurd@sasktel.net>
Date: Tue, 7 Jan 2025 23:49:13 -0500
Subject: [PATCH] Don't explicitly omit the frame pointer.

At -O3, the only reason the frame pointer will be retained is when
removing it makes it impossible to get any reasonable information
out of a core dump.

I personally prefer to take the small performance hit on affected
platforms and always include the frame pointer because it makes
profiling release builds possible... but I can manually make that
adjustment when I want to.
---
 src/build/Common.gmake | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/build/Common.gmake b/src/build/Common.gmake
index 78ecf480d8..b7bc3c30a7 100644
--- a/src/build/Common.gmake
+++ b/src/build/Common.gmake
@@ -524,7 +524,7 @@ ifdef DEBUG
 else # RELEASE
  # -finline-functions (used to) break the baja build badly.
  # This also meant that -O3 wouldn't work either.
- CFLAGS	:= -O3 -Wno-unused-result -fomit-frame-pointer -ffast-math -funroll-loops $(CFLAGS)
+ CFLAGS	:= -O3 -Wno-unused-result -ffast-math -funroll-loops $(CFLAGS)
  ifndef NO_LTO
   # Not Yet... this requires more care with library ordering.
   # CFLAGS += -flto
-- 
GitLab