[petsc-dev] CUDA + OMP make error

[Mark Adams]

https://www.mcs.anl.gov/petsc/miscellaneous/petscthreads.html

and I see this on my Mac:

14:23 1 mark/feature-xgc-interface-rebase *= ~/Codes/petsc$
../arch-macosx-gnu-O-omp.py


===============================================================================
             Configuring PETSc to compile on your system

===============================================================================
===============================================================================


               Warning: PETSC_ARCH from environment does not match
command-line or name of script.

                                     Warning: Using from command-line or
name of script: arch-macosx-gnu-O-omp, ignoring environment:
arch-macosx-gnu-g

===============================================================================


         TESTING: configureLibraryOptions from
PETSc.options.libraryOptions(config/PETSc/options/libraryOptions.py:37)


 *******************************************************************************
         UNABLE to CONFIGURE with GIVEN OPTIONS    (see configure.log for
details):
-------------------------------------------------------------------------------
Must use --with-log=0 with --with-threadsafety
*******************************************************************************


On Mon, Apr 13, 2020 at 2:54 PM Junchao Zhang <junchao.zhang at gmail.com>
wrote:

>
>
>
> On Mon, Apr 13, 2020 at 12:06 PM Mark Adams <mfadams at 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 <mfadams at 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.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/7442604f/attachment.html>