On Mon, Apr 13, 2020 at 12:06 PM Mark Adams <mfad...@lbl.gov> wrote: > BTW, I can build on SUMMIT with logging and OMP, apparently. I also seem > to be able to build with debugging. Both of which are not allowed according > the the docs. I am puzzled. > What are "the docs"?
> > On Mon, Apr 13, 2020 at 12:05 PM Mark Adams <mfad...@lbl.gov> wrote: > >> 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.zh...@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 <mfad...@lbl.gov> wrote: >>> >>>> Should I do an MR to fix this? >>>> >>>
