https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103276
Yury Gribov <ygribov at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ygribov at gcc dot gnu.org --- Comment #2 from Yury Gribov <ygribov at gcc dot gnu.org> --- This might be by chance, it could be fixed in mainline - or your example is too much simplified. > At least as is it cannot fail as there is no main program but just a module. I see. But is a runtime crash really mandatory here? It requires a bit of luck so that address ranges of local variable in copyin_simple overlaps local variables in another call. And even if it does, the crash will not be very stable across branches (because stack layouts change, etc.). My main goal was to provide a minimal self-explanatory usecase - there is a clear reference to local stack object passed to GOACC_enter_exit_data which is missing in the original code...