https://gcc.gnu.org/bugzilla/show_bug.cgi?id=127186
--- Comment #4 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:1f0018091064c26334f4dd67b3472f93c62b0b80 commit r17-3917-g1f0018091064c26334f4dd67b3472f93c62b0b80 Author: Tobias Burnus <[email protected]> Date: Fri Sep 4 09:20:40 2026 +0200 libgomp: GOMP_RUNTIME_USM - fix pointer attachment + update .texi [PR127186] If GOMP_RUNTIME_USM enables self mapping: Handle GOMP_MAP_ATTACH pointer attachment to global static (pointer) variables in map claues on 'target enter/exit data'. Update the documentation to GOMP_RUNTIME_USM to explicitly state what is not supported, removing the reference to 'requires self_maps/USM'. Because: The two features have diverged by now: * For GOMP_RUNTIME_USM, only 'target'/'target data' with 'always' modifier is mishandled (being tracked in the PR); there is an error abort in that case. * For 'requires self_maps/unified_shard_memory', currently more goes wrong but there is a pending compiler patch that turns all 'enter' into 'link' clauses when the requirement is specified, which should solve the issue completely without requiring the changes to libgomp. libgomp/ChangeLog: PR libgomp/127186 * libgomp.texi (GOMP_RUNTIME_USM): Update caveat section. * target.c (gomp_target_enter_exit_data_usm): Handle GOMP_MAP_ATTACH. * testsuite/libgomp.c/usm_env_handling-3.c: New test.
