[Bug target/111096] Frame pointer is not used even when -fomit-frame-pointer is specified

2023-08-25 Thread tkoenig at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111096 --- Comment #9 from Thomas Koenig --- (In reply to Richard Earnshaw from comment #8) > (In reply to Thomas Koenig from comment #7) > > Would it make sense to document this somewhere? Or did I just miss it? :-) > > Possibly, but I've no idea

[Bug target/111096] Frame pointer is not used even when -fomit-frame-pointer is specified

2023-08-24 Thread rearnsha at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111096 --- Comment #8 from Richard Earnshaw --- (In reply to Thomas Koenig from comment #7) > Would it make sense to document this somewhere? Or did I just miss it? :-) Possibly, but I've no idea where. It's too target-specific to put under the

[Bug target/111096] Frame pointer is not used even when -fomit-frame-pointer is specified

2023-08-23 Thread tkoenig at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111096 --- Comment #7 from Thomas Koenig --- (In reply to Richard Earnshaw from comment #5) > This was a deliberate design choice. Although the frame chain is not set up > by code that omits the frame pointer, the chain of frames that are set up by >

[Bug target/111096] Frame pointer is not used even when -fomit-frame-pointer is specified

2023-08-23 Thread rearnsha at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111096 --- Comment #6 from Richard Earnshaw --- For completeness. The AArch64 ABI lists 4 alternatives with respect to having a frame chain. When -fomit-frame-pointer is used, GCC implements this one: - It may require the frame pointer to address a

[Bug target/111096] Frame pointer is not used even when -fomit-frame-pointer is specified

2023-08-23 Thread rearnsha at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111096 Richard Earnshaw changed: What|Removed |Added Resolution|--- |WONTFIX

[Bug target/111096] Frame pointer is not used even when -fomit-frame-pointer is specified

2023-08-22 Thread gccbug at provalid dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111096 gccbug at provalid dot com changed: What|Removed |Added CC||gccbug at provalid dot com

[Bug target/111096] Frame pointer is not used even when -fomit-frame-pointer is specified

2023-08-22 Thread tkoenig at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111096 --- Comment #3 from Thomas Koenig --- (In reply to Andrew Pinski from comment #2) > See https://gcc.gnu.org/pipermail/gcc-patches/2016-September/456662.html > > I think this is by design of the ABI ... The workaround mentioned in the thread

[Bug target/111096] Frame pointer is not used even when -fomit-frame-pointer is specified

2023-08-21 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111096 --- Comment #2 from Andrew Pinski --- See https://gcc.gnu.org/pipermail/gcc-patches/2016-September/456662.html I think this is by design of the ABI ...

[Bug target/111096] Frame pointer is not used even when -fomit-frame-pointer is specified

2023-08-21 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111096 --- Comment #1 from Andrew Pinski --- #define FIXED_REGISTERS \ { \ 0, 0, 0, 0, 0, 0, 0, 0, /* R0 - R7 */ \ 0, 0, 0, 0, 0, 0, 0, 0,