aboutsummaryrefslogtreecommitdiff
path: root/gcc/testsuite/rust/compile/tuplepattern-rest-readonly.rs
diff options
context:
space:
mode:
authorTobias Burnus <tburnus@baylibre.com>2025-11-03 18:30:07 +0100
committerTobias Burnus <tburnus@baylibre.com>2025-11-03 18:30:07 +0100
commit28d20a591ddf1618d75f2b8261ba85bf15a49876 (patch)
tree47077c2b6bc3c5406ca55c1a90b407aa277dab3b /gcc/testsuite/rust/compile/tuplepattern-rest-readonly.rs
parent237a83da197adf6d0a70d715812182df77fa5bf7 (diff)
downloadgcc-master.zip
gcc-master.tar.gz
gcc-master.tar.bz2
libgomp.fortran/omp_target_memset.f90 - Avoid implicit mapping by an uninit size [PR122543]HEADtrunkmaster
In OpenMP, pointers are implicitly mapped - which means for Fortran that their pointer target is also mapped. However, for uninitialized memory, this means that some random pointee with some random amount of memory is copied - in the good case, size == 0, but if not, odd things can happen. Solution: Use 'fptr => null()' before the target mapping or - as done here - declare the pointer inside the region. libgomp/ChangeLog: PR libgomp/122543 * testsuite/libgomp.fortran/omp_target_memset.f90: Move fptr inside the target to avoid implicit mapping of its uninit pointee. * testsuite/libgomp.fortran/omp_target_memset-2.f90: Likewise.
Diffstat (limited to 'gcc/testsuite/rust/compile/tuplepattern-rest-readonly.rs')
0 files changed, 0 insertions, 0 deletions