diff options
| author | Peter Bergner <bergner@linux.ibm.com> | 2024-06-14 14:36:20 -0500 |
|---|---|---|
| committer | Peter Bergner <bergner@linux.ibm.com> | 2024-06-17 08:13:40 -0500 |
| commit | c70eea0dba5f223d49c80cfb3e80e87b74330aac (patch) | |
| tree | 0e860e5d1d3c94c27fc7f36cb04aeaaf134df637 /gcc/tree-ssa-alias.h | |
| parent | 83aad89fb99d0e82209734717c12f5aaca477970 (diff) | |
| download | gcc-c70eea0dba5f223d49c80cfb3e80e87b74330aac.zip gcc-c70eea0dba5f223d49c80cfb3e80e87b74330aac.tar.gz gcc-c70eea0dba5f223d49c80cfb3e80e87b74330aac.tar.bz2 | |
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.
Diffstat (limited to 'gcc/tree-ssa-alias.h')
0 files changed, 0 insertions, 0 deletions