https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118939
Mikael Pettersson <mikpelinux at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mikpelinux at gmail dot com
--- Comment #11 from Mikael Pettersson <mikpelinux at gmail dot com> ---
(In reply to Eric Botcazou from comment #10)
> The main difference between GCC 13 and GCC 14 is that -fstack-check triggers
> the (late) use of the frame pointer after commit 2971ff:
> arm_frame_pointer_required is called only once with the former and returns
> false, whereas it is called twice with the latter and returns first false
> and then true (when invoked from the new lra_update_fp2sp_elimination
> routine). This instability looks fishy.
Just an FYI: I worked on a private port of gcc-14/15 to an old processor last
year, and having <target>_frame_pointer_required switching from returning false
to returning true during the compilation of a function resulted in wrong code.
