diff options
| author | Kyrylo Tkachov <kyrylo.tkachov@arm.com> | 2018-09-18 13:28:50 +0000 |
|---|---|---|
| committer | Kyrylo Tkachov <ktkachov@gcc.gnu.org> | 2018-09-18 13:28:50 +0000 |
| commit | 92cb1fbc2774035b9ce7eaa9ff8c9a3dadbd8827 (patch) | |
| tree | 82785d9fe703321c770bdfbb5e99c3370ae7ee46 /gcc/gimple-fold.c | |
| parent | 6a8aa2e11b29c598ec24be8be0d87ca2ddd0f932 (diff) | |
| download | gcc-92cb1fbc2774035b9ce7eaa9ff8c9a3dadbd8827.zip gcc-92cb1fbc2774035b9ce7eaa9ff8c9a3dadbd8827.tar.gz gcc-92cb1fbc2774035b9ce7eaa9ff8c9a3dadbd8827.tar.bz2 | |
[AArch64][testsuite][committed] Fix gcc.target/aarch64/combine_bfxil.c for -mabi=ilp32
As described in https://gcc.gnu.org/ml/gcc-patches/2018-09/msg00963.html this test generates UXTW instructions with -mabi=ilp32
because the foo* functions take pointers and store results into them. In ILP32 the callee clears the top bits with a UXTW.
This trips the scan-assembler-not UXTW test that checks that the zero_extend form of the BFXIL pattern is used, which it is.
This patch avoids this problem by not passing pointers to the results, but instead using global variables for which the foo* functions
will synthesise the address using ADRP, avoiding the UXTW instructions.
With this patch the test PASSes fully with -mabi=ilp32 and still PASSes on LP64.
* gcc.target/aarch64/combine_bfxil.c: Avoid passing pointers to
functions.
From-SVN: r264389
Diffstat (limited to 'gcc/gimple-fold.c')
0 files changed, 0 insertions, 0 deletions