[Bug target/115389] Invalid ROP hashst offset is emitted when using -mabi=no-altivec

[cvs-commit at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115389

--- Comment #10 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Peter Bergner
<bergner@gcc.gnu.org>:

https://gcc.gnu.org/g:60e513cd47aadd8f139079f8388b14930e6e0913

commit r12-10639-g60e513cd47aadd8f139079f8388b14930e6e0913
Author: Peter Bergner <bergner@linux.ibm.com>
Date:   Fri Jun 14 14:36:20 2024 -0500

    rs6000: Compute rop_hash_save_offset for non-Altivec compiles [PR115389]

    We currently only compute the offset for the ROP hash save location in
    the stack frame for Altivec compiles.  For non-Altivec compiles when we
    emit ROP mitigation instructions, we use a default offset of zero which
    corresponds to the backchain save location which will get clobbered on
    any call.  The fix is to compute the ROP hash save location for all
    compiles.

    2024-06-14  Peter Bergner  <bergner@linux.ibm.com>

    gcc/
            PR target/115389
            * config/rs6000/rs6000-logue.cc (rs6000_stack_info): Compute
            rop_hash_save_offset for non-Altivec compiles.

    gcc/testsuite
            PR target/115389
            * gcc.target/powerpc/pr115389.c: New test.

    (cherry picked from commit c70eea0dba5f223d49c80cfb3e80e87b74330aac)