aboutsummaryrefslogtreecommitdiff
path: root/gcc/tree-ssa-loop-manip.c
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2020-08-10 15:42:38 +0200
committerTom de Vries <tdevries@suse.de>2020-08-19 09:48:45 +0200
commit9eaf11417b6a017b21a5052a74be3d2a251cfb78 (patch)
tree0dc89382ed84e248aae1d53ec87caaac7f93ef65 /gcc/tree-ssa-loop-manip.c
parenta7bbb5b1b1eb09db8175130474e8da952f30404b (diff)
downloadgcc-9eaf11417b6a017b21a5052a74be3d2a251cfb78.zip
gcc-9eaf11417b6a017b21a5052a74be3d2a251cfb78.tar.gz
gcc-9eaf11417b6a017b21a5052a74be3d2a251cfb78.tar.bz2
[testsuite, nvptx] Add effective target sync_int_long_stack
The nvptx target currently doesn't support effective target sync_int_long, although it has support for 32-bit and 64-bit atomic. When enabling sync_int_long for nvptx, we run into a failure in gcc.dg/pr86314.c: ... nvptx-run: error getting kernel result: operation not supported on \ global/shared address space ... due to a ptx restriction: accesses to local memory are illegal, and the test-case does an atomic operation on a stack address, which is mapped to local memory. Fix this by adding a target sync_int_long_stack, wich returns false for nvptx, which can be used to mark test-cases that require sync_int_long support for stack addresses. Build on nvptx and tested with make check-gcc. gcc/testsuite/ChangeLog: PR target/96494 * lib/target-supports.exp (check_effective_target_sync_int_long): Return 1 for nvptx. (check_effective_target_sync_int_long_stack): New proc. * gcc.dg/pr86314.c: Require effective target sync_int_long_stack.
Diffstat (limited to 'gcc/tree-ssa-loop-manip.c')
0 files changed, 0 insertions, 0 deletions