Re: [petsc-users] valgrind with petscmpiexec

2020-12-15 Thread Yaqi Wang
Fande, Did you try set TMPDIR for valgrind? Sent from my iPhone > On Dec 15, 2020, at 1:23 AM, Barry Smith wrote: > > > No idea. Perhaps petscmpiexec could be modified so it only ran valgrind on > the first 10 ranks? Not clear how to do that. Or valgrind should get a MR > that removes

Re: [petsc-users] Petsc makefile and PETSC_COMPILE variable

2020-12-15 Thread Satish Balay via petsc-users
On Tue, 15 Dec 2020, Alex Koshkarov wrote: > Hi All, > > I have been using trivial makefile (see below) for the code which uses petsc. > The makefile relies on variable PETSC_COMPILE which disappeared in new petsc > version (absent in 3.14.2, but present in 3.13.4). What would be the right >

Re: [petsc-users] Petsc makefile and PETSC_COMPILE variable

2020-12-15 Thread Alex Koshkarov
Thank you! It makes sense to use share/petsc/Makefile.user - I will try to understand it. However, can you please tell me what is the meaning of "_SINGLE" in "PETSC_COMPILE_SINGLE"? Does it mean compile only one source file? Best regards, Alex Koshkarov. On 12/15/20, 9:25 AM, "Satish Balay"

Re: [petsc-users] Petsc makefile and PETSC_COMPILE variable

2020-12-15 Thread Matthew Knepley
On Tue, Dec 15, 2020 at 12:46 PM Alex Koshkarov wrote: > Thank you! > > It makes sense to use share/petsc/Makefile.user - I will try to understand > it. However, can you please tell me what is the meaning of "_SINGLE" in > "PETSC_COMPILE_SINGLE"? Does it mean compile only one source file? >

Re: [petsc-users] valgrind with petscmpiexec

2020-12-15 Thread Fande Kong
Thanks so much, Satish, On Tue, Dec 15, 2020 at 9:33 AM Satish Balay via petsc-users < petsc-users@mcs.anl.gov> wrote: > For one - I think using '--log-file=valgrind-%q{HOSTNAME}-%p.log' might > help [to keep the logs from each process separate] > > And I think the TMPDIR recommendation is to

[petsc-users] Petsc makefile and PETSC_COMPILE variable

2020-12-15 Thread Alex Koshkarov
Hi All, I have been using trivial makefile (see below) for the code which uses petsc. The makefile relies on variable PETSC_COMPILE which disappeared in new petsc version (absent in 3.14.2, but present in 3.13.4). What would be the right way to fix the makefile? (should I use something like

Re: [petsc-users] Petsc makefile and PETSC_COMPILE variable

2020-12-15 Thread Satish Balay via petsc-users
Its internal organization of some old code. Previously we had 2 things: - PETSC_COMPILE (perhaps PETSC_COMPILE_MULTIPLE is a more appropriate name) did something equivalent to 'gcc -c a.c b.c c.c' - i.e compile multiple files at the same time. - PETSC_COMPILE_SINGLE used was to compile one

Re: [petsc-users] valgrind with petscmpiexec

2020-12-15 Thread Satish Balay via petsc-users
For one - I think using '--log-file=valgrind-%q{HOSTNAME}-%p.log' might help [to keep the logs from each process separate] And I think the TMPDIR recommendation is to have a different value for each of the nodes [where the "pid" clash comes from] and perhaps "TMPDIR=/tmp" might work - as this

Re: [petsc-users] TS tutorial ex11 in Fortran

2020-12-15 Thread Thibault Bridel-Bertomeu
Hello everyone, So far, I have the wrappers in the files attached to this e-mail. I still do not know if they work properly - at least the code compiles and the calls to the wrapped-subroutine do not fail - but I wanted to put this here in case someone sees something really wrong with it already.

Re: [petsc-users] TS tutorial ex11 in Fortran

2020-12-15 Thread Barry Smith
This is great. If you make a branch off of the PETSc git repository with these additions and work on ex11 you can make a merge request and we can run the code easily on all our test systems (for security reasons one of use needs to launch the tests from your MR).

Re: [petsc-users] Petsc makefile and PETSC_COMPILE variable

2020-12-15 Thread Barry Smith
Alex, Since you are explicitly defining your rules you might as well just do it completely, so use something like >> objects/%.o: src/%.c $(DEP) >>${PCC} -c $< -o $@ ${PCC_FLAGS} ${PFLAGS} ${CCPPFLAGS} The P indicates either C and C flags or C++ compiler and its flags if

Re: [petsc-users] TS tutorial ex11 in Fortran

2020-12-15 Thread Thibault Bridel-Bertomeu
Hello everyone, Thank you Barry for the feedback. OK, yes I'll work up an MR as soon as I have got something working. By the way, does the fortran-version of the example have to be a single file ? If my push contains a directory with several files (different modules and the main), and the

Re: [petsc-users] valgrind with petscmpiexec

2020-12-15 Thread Jed Brown
Barry Smith writes: > No idea. Perhaps petscmpiexec could be modified so it only ran valgrind on > the first 10 ranks? Not clear how to do that. Or valgrind should get a MR > that removes this small arbitrary limitation on the number of processes. 576 > is so 2000 :-) I don't want it

Re: [petsc-users] TS tutorial ex11 in Fortran

2020-12-15 Thread Barry Smith
Thibault, A subdirectory for the example is fine; we have other examples that use subdirectories and multiple files. Note: even if you don't have something completely working you can still make MR and list it as DRAFT request for comments, some other PETSc members who understand the

Re: [petsc-users] valgrind with petscmpiexec

2020-12-15 Thread Barry Smith
No idea. Perhaps petscmpiexec could be modified so it only ran valgrind on the first 10 ranks? Not clear how to do that. Or valgrind should get a MR that removes this small arbitrary limitation on the number of processes. 576 is so 2000 :-) Barry > On Dec 14, 2020, at 11:59 PM, Fande