Skip to content
Snippets Groups Projects
Commit 405f58b7 authored by Deucе's avatar Deucе :ok_hand_tone4:
Browse files

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.
parent 641e6c4a
No related branches found
No related tags found
No related merge requests found
Pipeline #7676 passed
......@@ -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
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment