https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114690
--- Comment #1 from Thomas Schwinge <tschwinge at gcc dot gnu.org> --- I suggest that in the short term, we at least add a safeguard in the 'GOMP_OFFLOAD_load_image's to error out if 'GOMP_INDIRECT_ADDR_MAP' has already been set (that should address (a), right?), and in the 'GOMP_OFFLOAD_unload_image's error out if 'GOMP_INDIRECT_ADDR_MAP' has been set (that should address (b) -- right?). (I'm assuming that stale mappings being present may potentially be problematic?) Those should be no-ops for the presumably common case that either dynamic loading/unloading of images isn't used at all, or if it is, that no 'indirect' clauses are actually present.
