[Bug target/100811] Consider not omitting frame pointers by default on targets with many registers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100811 --- Comment #11 from Jakub Jelinek --- DWARF unwinding works properly, just in Linux kernel they decided they don't want it in the kernel (I think they had some non-perfect implementation in the past and it got removed).

[Bug target/100811] Consider not omitting frame pointers by default on targets with many registers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100811 Xi Ruoyao changed: What|Removed |Added CC||xry111 at gcc dot gnu.org --- Comment #10

[Bug target/100811] Consider not omitting frame pointers by default on targets with many registers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100811 --- Comment #9 from Jakub Jelinek --- Why? It should be enabled by default only if it is effectively mandated by the ABI and/or doesn't affect performance at all (and is actually useful in functions that don't need it like functions with

[Bug target/100811] Consider not omitting frame pointers by default on targets with many registers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100811 --- Comment #8 from AK --- Should we enable frame-pointers by default for RISCV64 as well?

[Bug target/100811] Consider not omitting frame pointers by default on targets with many registers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100811 --- Comment #7 from Florian Weimer --- (In reply to Jakub Jelinek from comment #6) > I think aarch64 defaults to -fno-omit-frame-pointer anyway. > /* Disable fomit-frame-pointer by default. */ > { OPT_LEVELS_ALL,

[Bug target/100811] Consider not omitting frame pointers by default on targets with many registers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100811 --- Comment #6 from Jakub Jelinek --- I think aarch64 defaults to -fno-omit-frame-pointer anyway. /* Disable fomit-frame-pointer by default. */ { OPT_LEVELS_ALL, OPT_fomit_frame_pointer, NULL, 0 },

[Bug target/100811] Consider not omitting frame pointers by default on targets with many registers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100811 --- Comment #5 from Andrew Pinski --- (In reply to AK from comment #4) > On AArch64 (typically mobile platforms) app developers typically would > enable frame pointers by default because it helps with crash reporting. s/AArch64 (typically

[Bug target/100811] Consider not omitting frame pointers by default on targets with many registers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100811 AK changed: What|Removed |Added CC||hiraditya at msn dot com --- Comment #4 from AK

[Bug target/100811] Consider not omitting frame pointers by default on targets with many registers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100811 --- Comment #3 from Andrew Pinski --- Also on say PowerPC, not omitting the frame pointer gives no benifit whats so ever really with respect to backtracing.

[Bug target/100811] Consider not omitting frame pointers by default on targets with many registers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100811 Florian Weimer changed: What|Removed |Added CC||fw at gcc dot gnu.org --- Comment #2

[Bug target/100811] Consider not omitting frame pointers by default on targets with many registers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100811 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment