aboutsummaryrefslogtreecommitdiffstats
path: root/tools/testing/selftests/powerpc/include
diff options
context:
space:
mode:
authorMichael Ellerman <mpe@ellerman.id.au>2019-10-14 13:30:43 +1100
committerMichael Ellerman <mpe@ellerman.id.au>2019-10-29 20:53:49 +1100
commita02cbc7ffe529ed58b6bbe54652104fc2c88bd77 (patch)
treee567ae6e97ac2b51d4e315798fe290d5c9b044f8 /tools/testing/selftests/powerpc/include
parentpowerpc/book3s64/hash: Use secondary hash for bolted mapping if the primary is full (diff)
downloadlinux-dev-a02cbc7ffe529ed58b6bbe54652104fc2c88bd77.tar.xz
linux-dev-a02cbc7ffe529ed58b6bbe54652104fc2c88bd77.zip
selftests/powerpc: Fixup clobbers for TM tests
Some of our TM (Transactional Memory) tests, list "r1" (the stack pointer) as a clobbered register. GCC >= 9 doesn't accept this, and the build breaks: ptrace-tm-spd-tar.c: In function 'tm_spd_tar': ptrace-tm-spd-tar.c:31:2: error: listing the stack pointer register 'r1' in a clobber list is deprecated [-Werror=deprecated] 31 | asm __volatile__( | ^~~ ptrace-tm-spd-tar.c:31:2: note: the value of the stack pointer after an 'asm' statement must be the same as it was before the statement We do have some fairly large inline asm blocks in these tests, and some of them do change the value of r1. However they should all return to C with the value in r1 restored, so I think it's legitimate to say r1 is not clobbered. As Segher points out, the r1 clobbers may have been added because of the use of `or 1,1,1`, however that doesn't actually clobber r1. Segher also points out that some of these tests do clobber LR, because they call functions, and that is not listed in the clobbers, so add that where appropriate. Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> Link: https://lore.kernel.org/r/20191029095324.14669-1-mpe@ellerman.id.au
Diffstat (limited to 'tools/testing/selftests/powerpc/include')
0 files changed, 0 insertions, 0 deletions