diff options
author | Richard Earnshaw <rearnsha@arm.com> | 2025-03-21 15:20:03 +0000 |
---|---|---|
committer | Richard Earnshaw <rearnsha@arm.com> | 2025-03-21 15:32:59 +0000 |
commit | 1d2257dc850d088f6d9267b4624ba08533ab2475 (patch) | |
tree | 0aef3bea653b8dbf0540cd98dcda03684a6f1787 /gcc/fortran/iresolve.cc | |
parent | b1ac0c5f1986d0774cfc980da8323f17747a1ce9 (diff) | |
download | gcc-1d2257dc850d088f6d9267b4624ba08533ab2475.zip gcc-1d2257dc850d088f6d9267b4624ba08533ab2475.tar.gz gcc-1d2257dc850d088f6d9267b4624ba08533ab2475.tar.bz2 |
arm: testsuite: make unaligned-memcpy-*.c executable tests [PR91614]
These tests have been looking for a very specific instruction sequence
which has the tendency to be fairly unstable as a result. But what is
more interesting is that the the tests must not contain instructions
that can't be used for unaligned data, and whether or not the copy is
executed correctly.
So make these tests executable and scan the assembler only to confirm
the absence of instructions that must not be used when the data is not
aligned.
These tests also used to be restricted to targets that support
unaligned accesses (because you get very different code otherwise).
But now we've made the tests executable and to check for the absence
of problem instructions, just falling back to memcpy *is* an
acceptable implementation. So remove the requirement for unaligned
accesses.
gcc/testsuite:
PR target/91614
* gcc.target/arm/unaligned-memcpy-1.c: Make the test executable.
Only scan for the absence of instructions that cannot access
misaligned data. Remove constraint of having unaligned accesses.
* gcc.target/arm/unaligned-memcpy-2.c: Likewise.
* gcc.target/arm/unaligned-memcpy-3.c: Likewise.
* gcc.target/arm/unaligned-memcpy-4.c: Likewise.
Diffstat (limited to 'gcc/fortran/iresolve.cc')
0 files changed, 0 insertions, 0 deletions