https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98018
rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rsandifo at gcc dot gnu.org
--- Comment #6 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org>
---
I assume this isn't just about forcing a function to set up
a frame pointer: I assume we also need the function to set up
the frame pointer at the earliest opportunity and keep it valid
for as long as possible. This means (at least) that:
* We need to disable shrink-wrapping of the frame pointer
* There needs to be a full scheduling barrier after the
frame pointer has been set up and before it is torn down
So I don't think this is just about disabling optimisations
(unless perhaps we disable scheduling completely). It seems
like an entirely new mode that will involve new code.
