[Openmp-dev] OpenMP offloading app gets in unresponsive

[Itaru Kitayama via Openmp-dev]

While it was observed on ThunderX2 with V100 system, I don't see it on
JURECA (with GPUs).

On Sat, Sep 19, 2020 at 1:21 PM Johannes Doerfert
<johannesdoerfert at gmail.com> wrote:
>
> I don't think so.
> The only thing that comes to mind is that we switched to `abort` instead
> of `exit` after the fatal error message.
> Though, I'm not sure why that would cause the program to hang, except if
> SIGABRT is somehow caught.
>
> ~ Johannes
>
> On 9/18/20 9:35 PM, Itaru Kitayama via Openmp-dev wrote:
> > [...]
> > Libomptarget error: Failed to synchronize device.
> > Libomptarget error: Call to targetDataEnd failed, abort target.
> > Libomptarget error: Failed to process data after launching the kernel.
> > Libomptarget error: run with env LIBOMPTARGET_INFO>1 to dump
> > host-targetpointer maps
> > Libomptarget fatal error 1: failure of target construct while
> > offloading is mandatory
> >
> > after this point, the process gets in the state of unresponsive and
> > don't receive a signal from the user. Is this due to a new feature of
> > LLVM?
> > _______________________________________________
> > Openmp-dev mailing list
> > Openmp-dev at lists.llvm.org
> > https://lists.llvm.org/cgi-bin/mailman/listinfo/openmp-dev