https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100678
--- Comment #2 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
I ran into this in a different OpenACC context (OpenACC privatization levels),
where in testcases we're trying to use 'atomic' on 'private' variables. ...
which for nvptx offloading only works for gang-private (PTX '.shared'), but
fails for everything else, per PR83812 ("old" failure mode).
(In reply to Tom de Vries from comment #1)
> I'm not sure what you aim to achieve with the test-case.
To document the current failure mode -- a deficiency in the OpenACC/nvptx
implementation. So that there is precedence for this, and it doesn't appear
just in the upcoming OpenACC privatization levels testcases.
And then, as reported in this issue here, I found the "wrong reduction result"
problem ("new" failure mode), which seems to be another deficiency in the
OpenACC/nvptx implementation.
> My inclination would be to skip it for nvptx, which AFAIU is opposite to
> your intent when adding it. So, perhaps just remove it?
I'd rather conditionalize the nvptx offloading XFAIL appropriately for both the
"old" and "new" failure modes, and then eventually un-XFAIL, once these issues
have been addressed.
