diff options
| author | Kyrylo Tkachov <kyrylo.tkachov@arm.com> | 2022-11-18 14:29:36 +0000 |
|---|---|---|
| committer | Kyrylo Tkachov <kyrylo.tkachov@arm.com> | 2022-11-18 14:29:36 +0000 |
| commit | 92905f614e206a94d4ba72a4d425f78859ead418 (patch) | |
| tree | 73333eb512865b2dfeca07f02aa8eaf494957835 /gcc/function.cc | |
| parent | 20d2a8c24f3ca487ffd35fefcc9b1562bb10b609 (diff) | |
| download | gcc-92905f614e206a94d4ba72a4d425f78859ead418.zip gcc-92905f614e206a94d4ba72a4d425f78859ead418.tar.gz gcc-92905f614e206a94d4ba72a4d425f78859ead418.tar.bz2 | |
aarch64: Fix LDAPURS assembly output
... And another follow-up once I realised that the sign-extending load, of course,
needs to have strictly an X-reg as a destination for DImode extensions and a W-reg
for SImode ones.
Tested on aarch64-none-linux.
gcc/ChangeLog:
* config/aarch64/atomics.md (*aarch64_atomic_load<ALLX:mode>_rcpc_sext):
Use <GPI:w> for destination format.
* config/aarch64/iterators.md (w_sz): Delete.
gcc/testsuite/ChangeLog:
* gcc.target/aarch64/ldapr-sext.c: Adjust expected output.
Diffstat (limited to 'gcc/function.cc')
0 files changed, 0 insertions, 0 deletions