February 2021 - petsc-dev - mailman3.cels.anl.gov

Infinite loop in A*B
by Pierre Jolivet 28 Feb '21

28 Feb '21

Hello, The following MWE loops indefinitely for MPI_Comm_size in {2; 3}. Nothing fancy, just MatAIJ and MatDense. The problem is either in MatMPIDenseScatter() or MatMatMultSymbolic_MPIAIJ_MPIDense(), I believe, so if someone familiar with those routines can figure out a hot fix, I’m all ears. I could of course switch to a MatMult(), but the same infinite loop happens in another more complex code with A = rows=8, cols=35212 B = rows=35212, cols=9 So I’ll need a fix eventually. Thanks, Pierre

1 0

Re: [petsc-dev] headsup: switch git default branch from 'master' to 'main'
by Satish Balay 26 Feb '21

26 Feb '21

Update: the switch (at gitlab.com/petsc/petsc) is done. Please delete your local copy of 'master' branch and start using 'main' branch. Satish On Tue, 23 Feb 2021, Satish Balay via petsc-dev wrote: > All, > > This is a heads-up, we are to switch the default branch in petsc git > repo from 'master' to 'main' > > [Will plan to do the switch on friday the 26th] > > We've previously switched 'maint' branch to 'release' before 3.14 > release - and this change (to 'main') is the next step in this direction. > > Satish >

1 0

Re: [petsc-dev] headsup: switch git default branch from 'master' to 'main'
by Satish Balay 26 Feb '21

26 Feb '21

https://www.mcs.anl.gov/petsc/petsc-main should be the primary petsc-master, petsc-dev etc will be links to it - and should continue to work. Satish On Fri, 26 Feb 2021, Pierre Jolivet wrote: > What about https://www.mcs.anl.gov/petsc/petsc-master <https://www.mcs.anl.gov/petsc/petsc-master> ? Will it be moved to https://www.mcs.anl.gov/petsc/petsc-main <https://www.mcs.anl.gov/petsc/petsc-main> or will only https://www.mcs.anl.gov/petsc/petsc-dev <https://www.mcs.anl.gov/petsc/petsc-dev> remain online? > > Thanks, > Pierre > > > On 26 Feb 2021, at 6:06 PM, Satish Balay via petsc-dev <petsc-dev(a)mcs.anl.gov> wrote: > > > > I plan to delete 'master' immediately - so that folk don't assume it still exits and work with it [assuming its the latest, creating MRs against it etc..] > > > > Satish > > > > On Fri, 26 Feb 2021, Patrick Sanan wrote: > > > >> The answers to these were probably stated already, but the reminder might be useful to others, as well. > >> > >> What will happen to "master" after today? Will it be deleted immediately or at some planned time? If not immediately deleted, will it be updated to match main? > >> > >>> Am 23.02.2021 um 18:19 schrieb Satish Balay via petsc-dev <petsc-dev(a)mcs.anl.gov>: > >>> > >>> All, > >>> > >>> This is a heads-up, we are to switch the default branch in petsc git > >>> repo from 'master' to 'main' > >>> > >>> [Will plan to do the switch on friday the 26th] > >>> > >>> We've previously switched 'maint' branch to 'release' before 3.14 > >>> release - and this change (to 'main') is the next step in this direction. > >>> > >>> Satish > >>> > >> > > > >

1 0

Re: [petsc-dev] headsup: switch git default branch from 'master' to 'main'
by Pierre Jolivet 26 Feb '21

26 Feb '21

What about https://www.mcs.anl.gov/petsc/petsc-master <https://www.mcs.anl.gov/petsc/petsc-master> ? Will it be moved to https://www.mcs.anl.gov/petsc/petsc-main <https://www.mcs.anl.gov/petsc/petsc-main> or will only https://www.mcs.anl.gov/petsc/petsc-dev <https://www.mcs.anl.gov/petsc/petsc-dev> remain online? Thanks, Pierre > On 26 Feb 2021, at 6:06 PM, Satish Balay via petsc-dev <petsc-dev(a)mcs.anl.gov> wrote: > > I plan to delete 'master' immediately - so that folk don't assume it still exits and work with it [assuming its the latest, creating MRs against it etc..] > > Satish > > On Fri, 26 Feb 2021, Patrick Sanan wrote: > >> The answers to these were probably stated already, but the reminder might be useful to others, as well. >> >> What will happen to "master" after today? Will it be deleted immediately or at some planned time? If not immediately deleted, will it be updated to match main? >> >>> Am 23.02.2021 um 18:19 schrieb Satish Balay via petsc-dev <petsc-dev(a)mcs.anl.gov>: >>> >>> All, >>> >>> This is a heads-up, we are to switch the default branch in petsc git >>> repo from 'master' to 'main' >>> >>> [Will plan to do the switch on friday the 26th] >>> >>> We've previously switched 'maint' branch to 'release' before 3.14 >>> release - and this change (to 'main') is the next step in this direction. >>> >>> Satish >>> >> >

1 0

Re: [petsc-dev] headsup: switch git default branch from 'master' to 'main'
by Satish Balay 26 Feb '21

26 Feb '21

I plan to delete 'master' immediately - so that folk don't assume it still exits and work with it [assuming its the latest, creating MRs against it etc..] Satish On Fri, 26 Feb 2021, Patrick Sanan wrote: > The answers to these were probably stated already, but the reminder might be useful to others, as well. > > What will happen to "master" after today? Will it be deleted immediately or at some planned time? If not immediately deleted, will it be updated to match main? > > > Am 23.02.2021 um 18:19 schrieb Satish Balay via petsc-dev <petsc-dev(a)mcs.anl.gov>: > > > > All, > > > > This is a heads-up, we are to switch the default branch in petsc git > > repo from 'master' to 'main' > > > > [Will plan to do the switch on friday the 26th] > > > > We've previously switched 'maint' branch to 'release' before 3.14 > > release - and this change (to 'main') is the next step in this direction. > > > > Satish > > >

1 0

Re: [petsc-dev] headsup: switch git default branch from 'master' to 'main'
by Patrick Sanan 26 Feb '21

26 Feb '21

The answers to these were probably stated already, but the reminder might be useful to others, as well. What will happen to "master" after today? Will it be deleted immediately or at some planned time? If not immediately deleted, will it be updated to match main? > Am 23.02.2021 um 18:19 schrieb Satish Balay via petsc-dev <petsc-dev(a)mcs.anl.gov>: > > All, > > This is a heads-up, we are to switch the default branch in petsc git > repo from 'master' to 'main' > > [Will plan to do the switch on friday the 26th] > > We've previously switched 'maint' branch to 'release' before 3.14 > release - and this change (to 'main') is the next step in this direction. > > Satish >

1 0

Re: [petsc-dev] [petsc-users] headsup: switch git default branch from 'master' to 'main'
by Lisandro Dalcin 23 Feb '21

23 Feb '21

May the force be with you, Satish. On Tue, 23 Feb 2021 at 20:19, Satish Balay via petsc-users < petsc-users(a)mcs.anl.gov> wrote: > All, > > This is a heads-up, we are to switch the default branch in petsc git > repo from 'master' to 'main' > > [Will plan to do the switch on friday the 26th] > > We've previously switched 'maint' branch to 'release' before 3.14 > release - and this change (to 'main') is the next step in this direction. > > Satish > > -- Lisandro Dalcin ============ Senior Research Scientist Extreme Computing Research Center (ECRC) King Abdullah University of Science and Technology (KAUST) http://ecrc.kaust.edu.sa/

1 0

Re: [petsc-dev] valgrind now a point of failure?
by Satish Balay 23 Feb '21

23 Feb '21

It took a long time to run - but valgrind gave no errors. balay@petsc-02:/scratch/balay/petsc/src/mat/tests$ valgrind --tool=memcheck ./ex238 -mat_block_size 15 ==8099== Memcheck, a memory error detector ==8099== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==8099== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info ==8099== Command: ./ex238 -mat_block_size 15 ==8099== ==8099== Warning: set address range perms: large range [0x59e43040, 0xeabb0bc0) (undefined) ==8099== Warning: set address range perms: large range [0x59e43028, 0xeabb0bd8) (noaccess) ==8099== ==8099== HEAP SUMMARY: ==8099== in use at exit: 121 bytes in 2 blocks ==8099== total heap usage: 535 allocs, 533 frees, 2,457,025,714 bytes allocated ==8099== ==8099== LEAK SUMMARY: ==8099== definitely lost: 0 bytes in 0 blocks ==8099== indirectly lost: 0 bytes in 0 blocks ==8099== possibly lost: 0 bytes in 0 blocks ==8099== still reachable: 121 bytes in 2 blocks ==8099== suppressed: 0 bytes in 0 blocks ==8099== Rerun with --leak-check=full to see details of leaked memory ==8099== ==8099== For counts of detected and suppressed errors, rerun with: -v ==8099== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) Satish On Tue, 23 Feb 2021, Barry Smith wrote: > > Satish, > > Thanks for running this, but it is the 15 that is breaking, not the 12 :-). It is crashing inside building the matrix on Solaris with memory corruption. But I am having trouble getting it to cause problems elsewhere. > > Barry > > I think it is just code what was not previously properly tested in the nightly builds, the code has been around for a while. Or could be a bug in my test program. > > > > > > > On Feb 22, 2021, at 10:31 PM, Satish Balay <balay(a)mcs.anl.gov> wrote: > > > > I get the following with a debug build. > > > >>>>>>>>> > > balay@petsc-02:/scratch/balay/petsc/src/mat/tests$ make ex238 > > gcc -fPIC -Wall -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -fstack-protector -fvisibility=hidden -g3 -fPIC -Wall -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -fstack-protector -fvisibility=hidden -g3 -I/scratch/balay/petsc/include -I/scratch/balay/petsc/arch-linux-c-debug/include ex238.c -Wl,-rpath,/scratch/balay/petsc/arch-linux-c-debug/lib -L/scratch/balay/petsc/arch-linux-c-debug/lib -Wl,-rpath,/usr/lib/gcc/x86_64-linux-gnu/7 -L/usr/lib/gcc/x86_64-linux-gnu/7 -Wl,-rpath,/usr/lib/x86_64-linux-gnu -L/usr/lib/x86_64-linux-gnu -Wl,-rpath,/lib/x86_64-linux-gnu -L/lib/x86_64-linux-gnu -lpetsc -llapack -lblas -lpthread -lm -lX11 -lstdc++ -ldl -lgfortran -lm -lgfortran -lm -lgcc_s -lquadmath -lstdc++ -ldl -o ex238 > > balay@petsc-02:/scratch/balay/petsc/src/mat/tests$ valgrind --tool=memcheck ./ex238 -mat_block_size 12 > > ==34355== Memcheck, a memory error detector > > ==34355== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. > > ==34355== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info > > ==34355== Command: ./ex238 -mat_block_size 12 > > ==34355== > > ==34355== Warning: set address range perms: large range [0x59e43040, 0xb696a840) (undefined) > > <<<<<<<< > > > > Hang? takes a long time. try a different example > > > >>>>>>> > > balay@petsc-02:/scratch/balay/petsc/src/mat/tests$ make ex237 > > gcc -fPIC -Wall -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -fstack-protector -fvisibility=hidden -g3 -fPIC -Wall -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -fstack-protector -fvisibility=hidden -g3 -I/scratch/balay/petsc/include -I/scratch/balay/petsc/arch-linux-c-debug/include ex237.c -Wl,-rpath,/scratch/balay/petsc/arch-linux-c-debug/lib -L/scratch/balay/petsc/arch-linux-c-debug/lib -Wl,-rpath,/usr/lib/gcc/x86_64-linux-gnu/7 -L/usr/lib/gcc/x86_64-linux-gnu/7 -Wl,-rpath,/usr/lib/x86_64-linux-gnu -L/usr/lib/x86_64-linux-gnu -Wl,-rpath,/lib/x86_64-linux-gnu -L/lib/x86_64-linux-gnu -lpetsc -llapack -lblas -lpthread -lm -lX11 -lstdc++ -ldl -lgfortran -lm -lgfortran -lm -lgcc_s -lquadmath -lstdc++ -ldl -o ex237 > > balay@petsc-02:/scratch/balay/petsc/src/mat/tests$ valgrind --tool=memcheck -q ./ex237 -f /scratch/balay/petsc/share/petsc/datafiles/matrices/spd-real-int32-float64 > > Benchmarking MatMult: with A seqaij 12x12 > > Benchmarking MatProduct AB: with A seqaij 12x12 and B seqdense 12x2 > > Benchmarking MatProduct AB: with A seqaij 12x12 and B seqdense 12x4 > > Benchmarking MatProduct AB: with A seqaij 12x12 and B seqdense 12x8 > > Benchmarking MatProduct AB: with A seqaij 12x12 and B seqdense 12x16 > > Benchmarking MatProduct AB: with A seqaij 12x12 and B seqdense 12x32 > > Benchmarking MatProduct AB: with A seqaij 12x12 and B seqdense 12x64 > > Benchmarking MatProduct AB: with A seqaij 12x12 and B seqdense 12x128 > > balay@petsc-02:/scratch/balay/petsc/src/mat/tests$ > > > > <<<<<<<<< > > > > So the likely issue is - this opt build with '-march=native' [perhaps this valgrind version is older than the cpu]. > > > > Ok try an optimized build on an older CPU - aka es [@gce] > > > >>>>>> > > > > balay@es:/scratch/balay/petsc/src/mat/tests$ make ex237 > > gcc -fPIC -Wall -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -fstack-protector -fvisibility=hidden -march=native -O3 -fPIC -Wall -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -fstack-protector -fvisibility=hidden -march=native -O3 -I/scratch/balay/petsc/include -I/scratch/balay/petsc/arch-linux-c-opt/include ex237.c -Wl,-rpath,/scratch/balay/petsc/arch-linux-c-opt/lib -L/scratch/balay/petsc/arch-linux-c-opt/lib -Wl,-rpath,/usr/lib/gcc/x86_64-linux-gnu/7 -L/usr/lib/gcc/x86_64-linux-gnu/7 -Wl,-rpath,/usr/lib/x86_64-linux-gnu -L/usr/lib/x86_64-linux-gnu -Wl,-rpath,/lib/x86_64-linux-gnu -L/lib/x86_64-linux-gnu -lpetsc -llapack -lblas -lpthread -lm -lX11 -lstdc++ -ldl -lgfortran -lm -lgfortran -lm -lgcc_s -lquadmath -lstdc++ -ldl -o ex237 > > balay@es:/scratch/balay/petsc/src/mat/tests$ valgrind --tool=memcheck -q ./ex237 -f /scratch/balay/petsc/share/petsc/datafiles/matrices/spd-real-int32-float64 > > Benchmarking MatMult: with A seqaij 12x12 > > Benchmarking MatProduct AB: with A seqaij 12x12 and B seqdense 12x2 > > Benchmarking MatProduct AB: with A seqaij 12x12 and B seqdense 12x4 > > Benchmarking MatProduct AB: with A seqaij 12x12 and B seqdense 12x8 > > Benchmarking MatProduct AB: with A seqaij 12x12 and B seqdense 12x16 > > Benchmarking MatProduct AB: with A seqaij 12x12 and B seqdense 12x32 > > Benchmarking MatProduct AB: with A seqaij 12x12 and B seqdense 12x64 > > Benchmarking MatProduct AB: with A seqaij 12x12 and B seqdense 12x128 > > balay@es:/scratch/balay/petsc/src/mat/tests$ > > > > <<<<<<< > > > > Satish > > > > > > > > On Mon, 22 Feb 2021, Barry Smith wrote: > > > >> > >> I knew they hate Macs but now Linux? Any trustworthy machines to run valgrind? > >> > >> > >> $ petscmpiexec -valgrind -n 1 ./ex238 -mat_block_size 12 > >> ==14144== > >> ==14144== Process terminating with default action of signal 4 (SIGILL) > >> ==14144== Illegal opcode at address 0x4F808A9 > >> ==14144== at 0x4F808A9: PetscSetDisplay (in /scratch/bsmith/petsc/arch-add-baij-12/lib/libpetsc.so.3.014.4) > >> ==14144== by 0x4F086BD: PetscOptionsCheckInitial_Private (in /scratch/bsmith/petsc/arch-add-baij-12/lib/libpetsc.so.3.014.4) > >> ==14144== by 0x4F0D5BC: PetscInitialize (in /scratch/bsmith/petsc/arch-add-baij-12/lib/libpetsc.so.3.014.4) > >> ==14144== by 0x108D0E: main (in /scratch/bsmith/petsc/src/mat/tests/ex238) > >> Illegal instruction (core dumped) > >> /scratch/bsmith/petsc/src/mat/tests (barry/2021-02-12/add-baij-12=) arch-add-baij-12 > >> $ echo $PETSC_OPTIONS > >> > >> /scratch/bsmith/petsc/src/mat/tests (barry/2021-02-12/add-baij-12=) arch-add-baij-12 > >> $ hostname > >> petsc-02 > >> /scratch/bsmith/petsc/src/mat/tests (barry/2021-02-12/add-baij-12=) arch-add-baij-12 > >> $ uname -a > >> Linux petsc-02 4.15.0-135-generic #139-Ubuntu SMP Mon Jan 18 17:38:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux > >> /scratch/bsmith/petsc/src/mat/tests (barry/2021-02-12/add-baij-12=) arch-add-baij-12 > >> $ which valgrind > >> /usr/bin/valgrind > >> > >> $ make ex237 > >> gcc -fPIC -Wall -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -fstack-protector -fvisibility=hidden -march=native -O3 -fPIC -Wall -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -fstack-protector -fvisibility=hidden -march=native -O3 -I/scratch/bsmith/petsc/include -I/scratch/bsmith/petsc/arch-add-baij-12/include ex237.c -Wl,-rpath,/scratch/bsmith/petsc/arch-add-baij-12/lib -L/scratch/bsmith/petsc/arch-add-baij-12/lib -lpetsc -llapack -lblas -lpthread -lm -lX11 -lquadmath -ldl -o ex237 > >> /scratch/bsmith/petsc/src/mat/tests (barry/2021-02-12/add-baij-12=) arch-add-baij-12 > >> $ petscmpiexec -valgrind -n 1 ./ex237 > >> ==14841== > >> ==14841== Process terminating with default action of signal 4 (SIGILL) > >> ==14841== Illegal opcode at address 0x4F808A9 > >> ==14841== at 0x4F808A9: PetscSetDisplay (in /scratch/bsmith/petsc/arch-add-baij-12/lib/libpetsc.so.3.014.4) > >> ==14841== by 0x4F086BD: PetscOptionsCheckInitial_Private (in /scratch/bsmith/petsc/arch-add-baij-12/lib/libpetsc.so.3.014.4) > >> ==14841== by 0x4F0D5BC: PetscInitialize (in /scratch/bsmith/petsc/arch-add-baij-12/lib/libpetsc.so.3.014.4) > >> ==14841== by 0x109DE0: main (in /scratch/bsmith/petsc/src/mat/tests/ex237) > >> Illegal instruction (core dumped) > >> /scratch/bsmith/petsc/src/mat/tests (barry/2021-02-12/add-baij-12=) arch-add-baij-12 > >> > >> > > >

1 0

headsup: switch git default branch from 'master' to 'main'
by Satish Balay 23 Feb '21

23 Feb '21

All, This is a heads-up, we are to switch the default branch in petsc git repo from 'master' to 'main' [Will plan to do the switch on friday the 26th] We've previously switched 'maint' branch to 'release' before 3.14 release - and this change (to 'main') is the next step in this direction. Satish

1 0

Re: [petsc-dev] valgrind now a point of failure?
by Barry Smith 23 Feb '21

23 Feb '21

Satish, Thanks for running this, but it is the 15 that is breaking, not the 12 :-). It is crashing inside building the matrix on Solaris with memory corruption. But I am having trouble getting it to cause problems elsewhere. Barry I think it is just code what was not previously properly tested in the nightly builds, the code has been around for a while. Or could be a bug in my test program. > On Feb 22, 2021, at 10:31 PM, Satish Balay <balay(a)mcs.anl.gov> wrote: > > I get the following with a debug build. > >>>>>>>>> > balay@petsc-02:/scratch/balay/petsc/src/mat/tests$ make ex238 > gcc -fPIC -Wall -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -fstack-protector -fvisibility=hidden -g3 -fPIC -Wall -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -fstack-protector -fvisibility=hidden -g3 -I/scratch/balay/petsc/include -I/scratch/balay/petsc/arch-linux-c-debug/include ex238.c -Wl,-rpath,/scratch/balay/petsc/arch-linux-c-debug/lib -L/scratch/balay/petsc/arch-linux-c-debug/lib -Wl,-rpath,/usr/lib/gcc/x86_64-linux-gnu/7 -L/usr/lib/gcc/x86_64-linux-gnu/7 -Wl,-rpath,/usr/lib/x86_64-linux-gnu -L/usr/lib/x86_64-linux-gnu -Wl,-rpath,/lib/x86_64-linux-gnu -L/lib/x86_64-linux-gnu -lpetsc -llapack -lblas -lpthread -lm -lX11 -lstdc++ -ldl -lgfortran -lm -lgfortran -lm -lgcc_s -lquadmath -lstdc++ -ldl -o ex238 > balay@petsc-02:/scratch/balay/petsc/src/mat/tests$ valgrind --tool=memcheck ./ex238 -mat_block_size 12 > ==34355== Memcheck, a memory error detector > ==34355== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. > ==34355== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info > ==34355== Command: ./ex238 -mat_block_size 12 > ==34355== > ==34355== Warning: set address range perms: large range [0x59e43040, 0xb696a840) (undefined) > <<<<<<<< > > Hang? takes a long time. try a different example > >>>>>>> > balay@petsc-02:/scratch/balay/petsc/src/mat/tests$ make ex237 > gcc -fPIC -Wall -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -fstack-protector -fvisibility=hidden -g3 -fPIC -Wall -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -fstack-protector -fvisibility=hidden -g3 -I/scratch/balay/petsc/include -I/scratch/balay/petsc/arch-linux-c-debug/include ex237.c -Wl,-rpath,/scratch/balay/petsc/arch-linux-c-debug/lib -L/scratch/balay/petsc/arch-linux-c-debug/lib -Wl,-rpath,/usr/lib/gcc/x86_64-linux-gnu/7 -L/usr/lib/gcc/x86_64-linux-gnu/7 -Wl,-rpath,/usr/lib/x86_64-linux-gnu -L/usr/lib/x86_64-linux-gnu -Wl,-rpath,/lib/x86_64-linux-gnu -L/lib/x86_64-linux-gnu -lpetsc -llapack -lblas -lpthread -lm -lX11 -lstdc++ -ldl -lgfortran -lm -lgfortran -lm -lgcc_s -lquadmath -lstdc++ -ldl -o ex237 > balay@petsc-02:/scratch/balay/petsc/src/mat/tests$ valgrind --tool=memcheck -q ./ex237 -f /scratch/balay/petsc/share/petsc/datafiles/matrices/spd-real-int32-float64 > Benchmarking MatMult: with A seqaij 12x12 > Benchmarking MatProduct AB: with A seqaij 12x12 and B seqdense 12x2 > Benchmarking MatProduct AB: with A seqaij 12x12 and B seqdense 12x4 > Benchmarking MatProduct AB: with A seqaij 12x12 and B seqdense 12x8 > Benchmarking MatProduct AB: with A seqaij 12x12 and B seqdense 12x16 > Benchmarking MatProduct AB: with A seqaij 12x12 and B seqdense 12x32 > Benchmarking MatProduct AB: with A seqaij 12x12 and B seqdense 12x64 > Benchmarking MatProduct AB: with A seqaij 12x12 and B seqdense 12x128 > balay@petsc-02:/scratch/balay/petsc/src/mat/tests$ > > <<<<<<<<< > > So the likely issue is - this opt build with '-march=native' [perhaps this valgrind version is older than the cpu]. > > Ok try an optimized build on an older CPU - aka es [@gce] > >>>>>> > > balay@es:/scratch/balay/petsc/src/mat/tests$ make ex237 > gcc -fPIC -Wall -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -fstack-protector -fvisibility=hidden -march=native -O3 -fPIC -Wall -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -fstack-protector -fvisibility=hidden -march=native -O3 -I/scratch/balay/petsc/include -I/scratch/balay/petsc/arch-linux-c-opt/include ex237.c -Wl,-rpath,/scratch/balay/petsc/arch-linux-c-opt/lib -L/scratch/balay/petsc/arch-linux-c-opt/lib -Wl,-rpath,/usr/lib/gcc/x86_64-linux-gnu/7 -L/usr/lib/gcc/x86_64-linux-gnu/7 -Wl,-rpath,/usr/lib/x86_64-linux-gnu -L/usr/lib/x86_64-linux-gnu -Wl,-rpath,/lib/x86_64-linux-gnu -L/lib/x86_64-linux-gnu -lpetsc -llapack -lblas -lpthread -lm -lX11 -lstdc++ -ldl -lgfortran -lm -lgfortran -lm -lgcc_s -lquadmath -lstdc++ -ldl -o ex237 > balay@es:/scratch/balay/petsc/src/mat/tests$ valgrind --tool=memcheck -q ./ex237 -f /scratch/balay/petsc/share/petsc/datafiles/matrices/spd-real-int32-float64 > Benchmarking MatMult: with A seqaij 12x12 > Benchmarking MatProduct AB: with A seqaij 12x12 and B seqdense 12x2 > Benchmarking MatProduct AB: with A seqaij 12x12 and B seqdense 12x4 > Benchmarking MatProduct AB: with A seqaij 12x12 and B seqdense 12x8 > Benchmarking MatProduct AB: with A seqaij 12x12 and B seqdense 12x16 > Benchmarking MatProduct AB: with A seqaij 12x12 and B seqdense 12x32 > Benchmarking MatProduct AB: with A seqaij 12x12 and B seqdense 12x64 > Benchmarking MatProduct AB: with A seqaij 12x12 and B seqdense 12x128 > balay@es:/scratch/balay/petsc/src/mat/tests$ > > <<<<<<< > > Satish > > > > On Mon, 22 Feb 2021, Barry Smith wrote: > >> >> I knew they hate Macs but now Linux? Any trustworthy machines to run valgrind? >> >> >> $ petscmpiexec -valgrind -n 1 ./ex238 -mat_block_size 12 >> ==14144== >> ==14144== Process terminating with default action of signal 4 (SIGILL) >> ==14144== Illegal opcode at address 0x4F808A9 >> ==14144== at 0x4F808A9: PetscSetDisplay (in /scratch/bsmith/petsc/arch-add-baij-12/lib/libpetsc.so.3.014.4) >> ==14144== by 0x4F086BD: PetscOptionsCheckInitial_Private (in /scratch/bsmith/petsc/arch-add-baij-12/lib/libpetsc.so.3.014.4) >> ==14144== by 0x4F0D5BC: PetscInitialize (in /scratch/bsmith/petsc/arch-add-baij-12/lib/libpetsc.so.3.014.4) >> ==14144== by 0x108D0E: main (in /scratch/bsmith/petsc/src/mat/tests/ex238) >> Illegal instruction (core dumped) >> /scratch/bsmith/petsc/src/mat/tests (barry/2021-02-12/add-baij-12=) arch-add-baij-12 >> $ echo $PETSC_OPTIONS >> >> /scratch/bsmith/petsc/src/mat/tests (barry/2021-02-12/add-baij-12=) arch-add-baij-12 >> $ hostname >> petsc-02 >> /scratch/bsmith/petsc/src/mat/tests (barry/2021-02-12/add-baij-12=) arch-add-baij-12 >> $ uname -a >> Linux petsc-02 4.15.0-135-generic #139-Ubuntu SMP Mon Jan 18 17:38:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux >> /scratch/bsmith/petsc/src/mat/tests (barry/2021-02-12/add-baij-12=) arch-add-baij-12 >> $ which valgrind >> /usr/bin/valgrind >> >> $ make ex237 >> gcc -fPIC -Wall -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -fstack-protector -fvisibility=hidden -march=native -O3 -fPIC -Wall -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -fstack-protector -fvisibility=hidden -march=native -O3 -I/scratch/bsmith/petsc/include -I/scratch/bsmith/petsc/arch-add-baij-12/include ex237.c -Wl,-rpath,/scratch/bsmith/petsc/arch-add-baij-12/lib -L/scratch/bsmith/petsc/arch-add-baij-12/lib -lpetsc -llapack -lblas -lpthread -lm -lX11 -lquadmath -ldl -o ex237 >> /scratch/bsmith/petsc/src/mat/tests (barry/2021-02-12/add-baij-12=) arch-add-baij-12 >> $ petscmpiexec -valgrind -n 1 ./ex237 >> ==14841== >> ==14841== Process terminating with default action of signal 4 (SIGILL) >> ==14841== Illegal opcode at address 0x4F808A9 >> ==14841== at 0x4F808A9: PetscSetDisplay (in /scratch/bsmith/petsc/arch-add-baij-12/lib/libpetsc.so.3.014.4) >> ==14841== by 0x4F086BD: PetscOptionsCheckInitial_Private (in /scratch/bsmith/petsc/arch-add-baij-12/lib/libpetsc.so.3.014.4) >> ==14841== by 0x4F0D5BC: PetscInitialize (in /scratch/bsmith/petsc/arch-add-baij-12/lib/libpetsc.so.3.014.4) >> ==14841== by 0x109DE0: main (in /scratch/bsmith/petsc/src/mat/tests/ex237) >> Illegal instruction (core dumped) >> /scratch/bsmith/petsc/src/mat/tests (barry/2021-02-12/add-baij-12=) arch-add-baij-12 >> >> >

1 0