diff options
| author | Andrew Pinski <quic_apinski@quicinc.com> | 2024-01-18 10:40:04 -0800 |
|---|---|---|
| committer | Andrew Pinski <quic_apinski@quicinc.com> | 2024-01-24 09:49:24 -0800 |
| commit | d3ff08a3764f2047d02b35212fc4f1da9eb75c7b (patch) | |
| tree | 2f0c2534f67ffb5fdf6496c4cc26700e0f865135 /gcc/cp | |
| parent | fb54b9772816968032518d4008be5090e0d95109 (diff) | |
| download | gcc-d3ff08a3764f2047d02b35212fc4f1da9eb75c7b.zip gcc-d3ff08a3764f2047d02b35212fc4f1da9eb75c7b.tar.gz gcc-d3ff08a3764f2047d02b35212fc4f1da9eb75c7b.tar.bz2 | |
aarch64: Fix __builtin_apply with -mgeneral-regs-only [PR113486]
The problem here is the builtin apply mechanism thinks the FP registers
are to be used due to get_raw_arg_mode not returning VOIDmode. This
fixes that oversight and the backend now returns VOIDmode for non-general-regs
if TARGET_GENERAL_REGS_ONLY is true.
Built and tested for aarch64-linux-gnu with no regressions.
PR target/113486
gcc/ChangeLog:
* config/aarch64/aarch64.cc (aarch64_get_reg_raw_mode): For
TARGET_GENERAL_REGS_ONLY, return VOIDmode for non-GP_REGNUM_P regno.
gcc/testsuite/ChangeLog:
* gcc.target/aarch64/builtin_apply-1.c: New test.
Signed-off-by: Andrew Pinski <quic_apinski@quicinc.com>
Diffstat (limited to 'gcc/cp')
0 files changed, 0 insertions, 0 deletions