diff options
| author | Tom de Vries <tdevries@suse.de> | 2022-01-20 13:37:08 +0100 |
|---|---|---|
| committer | Tom de Vries <tdevries@suse.de> | 2022-02-01 08:13:06 +0100 |
| commit | be362d5e127e087dcd4a2c0d843cf7b9a7399c73 (patch) | |
| tree | 61d3783a20e25e7580ef9c0587cca950e5e687ed /gcc | |
| parent | 2989516651579dc045e968d7517857c581e3a2dd (diff) | |
| download | gcc-be362d5e127e087dcd4a2c0d843cf7b9a7399c73.zip gcc-be362d5e127e087dcd4a2c0d843cf7b9a7399c73.tar.gz gcc-be362d5e127e087dcd4a2c0d843cf7b9a7399c73.tar.bz2 | |
[libgomp, testsuite] Reduce recursion depth in declare_target-*.f90
When running the libgomp testsuite with GOMP_NVPTX_JIT=-O0 using an nvptx
accelerator (Nvidia T400, 2GB), I run into:
...
libgomp: cuCtxSynchronize error: unspecified launch failure \
(perhaps abort was called)
libgomp: cuMemFree_v2 error: unspecified launch failure
libgomp: device finalization failed
FAIL: libgomp.fortran/examples-4/declare_target-1.f90 -O0 execution test
...
The test-case contains:
...
! Reduced from 25 to 23, otherwise execution runs out of thread stack on
! Nvidia Titan V.
if (fib (23) /= fib_wrapper (23)) stop 2
...
Fix this by reducing the fib/fib_wrapper argument from 23 to 22.
Same for declare_target-2.f90.
Tested on x86_64 with nvptx accelerator.
libgomp/ChangeLog:
2022-01-27 Tom de Vries <tdevries@suse.de>
* testsuite/libgomp.fortran/examples-4/declare_target-1.f90: Reduce
recursion depth.
* testsuite/libgomp.fortran/examples-4/declare_target-2.f90: Same.
Diffstat (limited to 'gcc')
0 files changed, 0 insertions, 0 deletions