diff options
| author | Tom de Vries <tdevries@suse.de> | 2022-04-01 17:28:37 +0200 |
|---|---|---|
| committer | Tom de Vries <tdevries@suse.de> | 2022-04-04 13:37:19 +0200 |
| commit | 88cffa1a07d04187be1975238dfdca51a8ef5d65 (patch) | |
| tree | d98d105622aad833f00c9c393ba7b0e98e948081 /gcc/fortran/trans-openmp.cc | |
| parent | 376cf6d19cdcb791a4257bc1cafabfae89227683 (diff) | |
| download | gcc-88cffa1a07d04187be1975238dfdca51a8ef5d65.zip gcc-88cffa1a07d04187be1975238dfdca51a8ef5d65.tar.gz gcc-88cffa1a07d04187be1975238dfdca51a8ef5d65.tar.bz2 | |
[libgomp/testsuite] Fix libgomp.fortran/examples-4/declare_target-{1,2}.f90
The test-cases libgomp.fortran/examples-4/declare_target-{1,2}.f90 mean to
set an nvptx-specific limit using offload_target_nvptx, but also change
behaviour for amd.
That is, there is now a difference in behaviour between:
- a compiler configured for GCN offloading, and
- a compiler configured for both GCN and nvptx offloading.
Fix this by using instead on_device_arch_nvptx.
Tested on x86_64 with nvptx accelerator.
libgomp/ChangeLog:
2022-04-04 Tom de Vries <tdevries@suse.de>
* testsuite/libgomp.fortran/examples-4/declare_target-1.f90: Use
on_device_arch_nvptx instead of offload_target_nvptx.
* testsuite/libgomp.fortran/examples-4/declare_target-2.f90: Same.
Diffstat (limited to 'gcc/fortran/trans-openmp.cc')
0 files changed, 0 insertions, 0 deletions