aboutsummaryrefslogtreecommitdiff
path: root/libphobos/libdruntime/gcc
diff options
context:
space:
mode:
authorJakub Jelinek <jakub@redhat.com>2022-06-15 10:45:04 +0200
committerJakub Jelinek <jakub@redhat.com>2022-06-15 10:45:04 +0200
commit7bfb3f488a7ec58109a859c66bf4eddc6354065b (patch)
tree26fa99d006bd7db16cf9b7590fa0fe7decce88f1 /libphobos/libdruntime/gcc
parentacb1e6f43dc2bbedd1248ea61c7ab537a11fe59b (diff)
downloadgcc-7bfb3f488a7ec58109a859c66bf4eddc6354065b.zip
gcc-7bfb3f488a7ec58109a859c66bf4eddc6354065b.tar.gz
gcc-7bfb3f488a7ec58109a859c66bf4eddc6354065b.tar.bz2
openmp: Fix up get-mapped-ptr-1.{c,f90} tests
On Tue, Jun 14, 2022 at 06:41:37PM +0200, Thomas Schwinge wrote: > In an offloading configuration, I'm seeing: > > PASS: libgomp.fortran/get-mapped-ptr-1.f90 -O (test for excess errors) > [-PASS:-]{+FAIL:+} libgomp.fortran/get-mapped-ptr-1.f90 -O execution test > > Does that one need similar treatment? I assume not just that but libgomp.c-c++-common/get-mapped-ptr-1.c too? It both needs the same treatment, and in the get-mapped-ptr-1.c case there is even UB, while the Fortran version was using c_loc (q) as the host pointer, in C/C++ it was using q which was value of uninitialized pointer. 2022-06-15 Jakub Jelinek <jakub@redhat.com> * testsuite/libgomp.c-c++-common/get-mapped-ptr-1.c (main): Initialize q to ddress of an automatic variable. Use -5 instead of -1 in omp_get_mapped_ptr call. Add test with omp_initial_device. * testsuite/libgomp.fortran/get-mapped-ptr-1.f90 (main): Use -5 instead of -1 in omp_get_mapped_ptr call. Add test with omp_initial_device. Renumber stop arguments afterwards.
Diffstat (limited to 'libphobos/libdruntime/gcc')
0 files changed, 0 insertions, 0 deletions