Thank you very much Barry, it works indeed to build petsc with the qopenmp
flags!
Best
Timothee
2018-01-30 18:46 GMT+01:00 Satish Balay :
> Try building PETSc with -qopenmp flag and see if this makes a difference.
>
> i.e use CFLAGS=-qopenmp FFLAGS=-qopenmp CXXFLAGS=-qopenmp
>
> Potential expla
Try building PETSc with -qopenmp flag and see if this makes a difference.
i.e use CFLAGS=-qopenmp FFLAGS=-qopenmp CXXFLAGS=-qopenmp
Potential explanation:
Compilers do different things internally [for ex - link to different
libraries] when different compile flags are used.
When -qopenmp is used
Thank you for your answer,
I am not responsible for the choices in this code to begin with, but in any
case, as you can see in the example, I am not using any petsc call. Also in
our code, even though openmp is used, this is never in interaction with
petsc, the latter being used only at a specific
I don't know what you are trying to do with OpenMP and PETSc, nor do I
understand why anyone would use OpenMP, but you cannot call virtually any PETSc
function or operation while you are using threads.
Best to use PETSc as intended, with one MPI process per core or hardware
thread and not
Dear petsc team,
For a while, I have been wondering why I have never managed to print what
threads are doing in an openMP region in my FORTRAN programs. Some people
told me it was normal because threads will get confused all trying to write
at the same time. However I realised today that the probl
