https://gcc.gnu.org/bugzilla/show_bug.cgi?id=127186
--- Comment #1 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tobias Burnus <[email protected]>: https://gcc.gnu.org/g:b590dc3fdc0aeb9bcd923cfd22778a0864102101 commit r17-3858-gb590dc3fdc0aeb9bcd923cfd22778a0864102101 Author: Tobias Burnus <[email protected]> Date: Wed Sep 2 13:57:30 2026 +0200 libgomp: fix comment, add testcase libgomp.c/usm_env_handling-2.c [PR127186] The following is with GOMP_RUNTIME_USM=enabled and a suitable device available: In r17-3807-g82104cde7ac0ba I wrongly claimed that in a 'target' structured block, a global static variable will not be address translated such that the code will access the host variable, which would cause inconsistency issues (aka wrong code). However, the compiler middle end already optimizes his by accessing directly the respective global variable and not even passing the variable address to libgomp for host->device address translation. Thus, there is no issue in this regard. Add a testcase for this. libgomp/ChangeLog: PR libgomp/127186 * target.c (GOMP_target_ext): Fix comment related to GOMP_RUNTIME_USM. * testsuite/libgomp.c/usm_env_handling-2.c: New test.
