diff options
author | Richard Sandiford <richard.sandiford@arm.com> | 2023-01-13 10:01:32 +0000 |
---|---|---|
committer | Richard Sandiford <richard.sandiford@arm.com> | 2023-01-13 10:01:32 +0000 |
commit | eb4994545fbd2a670e422f6e98c16e4ed60ac53e (patch) | |
tree | 817f3df6de411ac2834a11087abe44862e34e10a /gcc/gimple-array-bounds.cc | |
parent | 3893c9c0a16832f55d8d0827f50c48a56c52f6e7 (diff) | |
download | gcc-eb4994545fbd2a670e422f6e98c16e4ed60ac53e.zip gcc-eb4994545fbd2a670e422f6e98c16e4ed60ac53e.tar.gz gcc-eb4994545fbd2a670e422f6e98c16e4ed60ac53e.tar.bz2 |
aarch64: Fix DWARF frame register sizes for predicates
Jakub pointed out that __builtin_init_dwarf_reg_size_table
set the size of predicate registers to their current runtime
size when compiled with +sve, but to 8 bytes otherwise.
As explained in the comment, both behaviours are wrong.
Predicates change size with VL and should never need to be
restored during unwinding.
In contrast, the call-saved FP&SIMD frame registers are 8 bytes
(even though the hardware registers are at least 16 bytes) and
the call-clobbered registers have zero size. A zero size seems
correct for predicates too.
gcc/
* config/aarch64/aarch64.cc (aarch64_dwarf_frame_reg_mode): New
function.
(TARGET_DWARF_FRAME_REG_MODE): Define.
gcc/testsuite/
* gcc.target/aarch64/dwarf_reg_size_1.c: New test.
* gcc.target/aarch64/dwarf_reg_size_2.c: Likewise.
Diffstat (limited to 'gcc/gimple-array-bounds.cc')
0 files changed, 0 insertions, 0 deletions