https://gcc.gnu.org/bugzilla/show_bug.cgi?id=128414
Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2026-11-03
Assignee|unassigned at gcc dot gnu.org |burnus at gcc dot
gnu.org
Status|UNCONFIRMED |WAITING
Ever confirmed|0 |1
--- Comment #1 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
(In reply to Tobias Burnus from comment #0)
> The following code is supposed to offload to the GPU and print there
>
> 0 - 0 - 0
>
> and exit with exit status 0. That happens with nvptx offloading an my
> GCC 16 distro compiler.
Also for (mostly recent) GCC trunk, in my case.
> However, it now does with nvptx offloading:
>
> 0 - 0 - 0
> 0 - 0 - 0
> 0 - 0 - 0
> 0 - 0 - 0
> (in total 31 such lines)
>
> libgomp: cuCtxSynchronize error: unspecified launch failure (perhaps abort
> was called)
Based on similar such things that you've reported in the past: please check
that your GCC/nvptx' 'mgomp' multilib exists.
> I tried to revert [...]
> However, reverting [...] and re-compiling did not fix it.
> Hence, either the regression is older - or I messed up with my reverting -
> or my tree is broken for some reasons [i.e. needs a clean bootstrap and
> proper regression hunting] - [...]
In case my suspicion from above is right, I wonder what you're doing to get
your GCC/nvptx into that broken state, every once in a while?