[petsc-dev] CUDA + OMP make error

[Mark Adams]

I think the problem is that you have to turn off logging with openmp and
the (newish) GPU timers did not protect their timers.

I don't see a good reason to require logging be turned off with OMP. We
could use PETSC_HAVE_THREADSAFETY to protect logs that we care about (eg,
in MatSetValues) and as users discover more things that they want to call
in an OMP thread block, then tell them to turn logging off and we will fix
it when we can.

Any thoughts on the idea of letting users keep logging with openmp?

On Mon, Apr 13, 2020 at 11:40 AM Junchao Zhang <junchao.zhang at gmail.com>
wrote:

> Yes. Looks we need to include petsclog.h. Don't know why OMP triggered the
> error.
> --Junchao Zhang
>
>
> On Mon, Apr 13, 2020 at 9:59 AM Mark Adams <mfadams at lbl.gov> wrote:
>
>> Should I do an MR to fix this?
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20200413/bbbd9abe/attachment.html>