Re: [petsc-users] Sparse solvers for distributed GPU matrices/vectors arising from 3D poisson eq

2022-02-04 Thread Junchao Zhang
On Fri, Feb 4, 2022 at 11:09 AM Sajid Ali Syed wrote: > Hi PETSc-developers, > > Could the linear solver table (at > https://petsc.org/main/overview/linear_solve_table/) be updated with > information regarding direct solvers that work on mpiaijkokkos/kokkos (or > mpiaijcusparse/cuda)

Re: [petsc-users] 3.16.4 amd blis libflame linking problem

2022-02-04 Thread Matthew Knepley
On Fri, Feb 4, 2022 at 11:35 AM Anton Popov wrote: > Hi Satish, > > I just discovered that PETSc 3.16.4 fails to link against the latest AMD > BLIS and LibFLAME libraries on a Linux box. > > > --- > You set a value for

[petsc-users] Sparse solvers for distributed GPU matrices/vectors arising from 3D poisson eq

2022-02-04 Thread Sajid Ali Syed
Hi PETSc-developers, Could the linear solver table (at https://petsc.org/main/overview/linear_solve_table/) be updated with information regarding direct solvers that work on mpiaijkokkos/kokkos (or mpiaijcusparse/cuda) matrix/vector types? The use case for this solver would be to repeatedly

Re: [petsc-users] 3.16.4 amd blis libflame linking problem

2022-02-04 Thread Matthew Knepley
Can you send the 3.9 log? Thanks, Matt On Fri, Feb 4, 2022 at 12:00 PM Anton Popov wrote: > > On 04.02.22 17:39, Matthew Knepley wrote: > > On Fri, Feb 4, 2022 at 11:35 AM Anton Popov wrote: > >> Hi Satish, >> >> I just discovered that PETSc 3.16.4 fails to link against the latest AMD

Re: [petsc-users] 3.16.4 amd blis libflame linking problem

2022-02-04 Thread Anton Popov
On 04.02.22 17:39, Matthew Knepley wrote: On Fri, Feb 4, 2022 at 11:35 AM Anton Popov wrote: Hi Satish, I just discovered that PETSc 3.16.4 fails to link against the latest AMD BLIS and LibFLAME libraries on a Linux box.

Re: [petsc-users] cannot open source file "petsc.h"

2022-02-04 Thread Evstafyeva,Tamara
Hi all again, Thanks again for your help and very quick replies. I managed to fix it at the end – unfortunately I cannot exactly pin-point what went wrong as I was trying different things until they worked – not very scientific of me xD. But the steps were as follows, I am not sure if this

Re: [petsc-users] 3.16.4 amd blis libflame linking problem

2022-02-04 Thread Barry Smith
Please do ldd -O /opt/amd/amd-libflame-3.1.0/lib/lp64/libflame.so You may need to list the gfortran library directory of libgfortran.so.5 it needs to use in LDFLAGS passed to PETSc configure Barry Note: Even though you explicitly listed a static library of libflame to use our

Re: [petsc-users] 3.16.4 amd blis libflame linking problem

2022-02-04 Thread Barry Smith
> On Feb 4, 2022, at 12:27 PM, Satish Balay wrote: > > Probably best if you can use the same version of gfortran to build both petsc > and libflame/blis > >> /usr/bin/ld: warning: libgfortran.so.5, needed by >> /opt/amd/amd-libflame-3.1.0/lib/lp64/libflame.so, not found (try using >>

Re: [petsc-users] 3.16.4 amd blis libflame linking problem

2022-02-04 Thread Anton Popov
Thanks Matt, Barry and Satish, for  your suggestions. The problem was indeed in mismatch between the gfortran library version (system has libgfortran.so.4 libflame needs libgfortran.so.5) 3.9.4 did not detect this during configure, but only gave error later during test. 3.16.4 detected

Re: [petsc-users] 3.16.4 amd blis libflame linking problem

2022-02-04 Thread Satish Balay via petsc-users
On Fri, 4 Feb 2022, Anton Popov wrote: > Thanks Matt, Barry and Satish, for  your suggestions. > > The problem was indeed in mismatch between the gfortran library version > (system has libgfortran.so.4 libflame needs libgfortran.so.5) > > 3.9.4 did not detect this during configure, but only

Re: [petsc-users] 3.16.4 amd blis libflame linking problem

2022-02-04 Thread Satish Balay via petsc-users
Probably best if you can use the same version of gfortran to build both petsc and libflame/blis > /usr/bin/ld: warning: libgfortran.so.5, needed by > /opt/amd/amd-libflame-3.1.0/lib/lp64/libflame.so, not found (try using -rpath > or -rpath-link): This is probably an ignore-able warning - but

Re: [petsc-users] 3.16.4 amd blis libflame linking problem

2022-02-04 Thread Barry Smith
> On Feb 4, 2022, at 12:38 PM, Satish Balay wrote: > > On Fri, 4 Feb 2022, Barry Smith wrote: > >> >> >>> On Feb 4, 2022, at 12:27 PM, Satish Balay wrote: >>> >>> Probably best if you can use the same version of gfortran to build both >>> petsc and libflame/blis >>> /usr/bin/ld:

Re: [petsc-users] 3.16.4 amd blis libflame linking problem

2022-02-04 Thread Satish Balay via petsc-users
On Fri, 4 Feb 2022, Barry Smith wrote: > > > > On Feb 4, 2022, at 12:27 PM, Satish Balay wrote: > > > > Probably best if you can use the same version of gfortran to build both > > petsc and libflame/blis > > > >> /usr/bin/ld: warning: libgfortran.so.5, needed by > >>

Re: [petsc-users] 3.16.4 amd blis libflame linking problem

2022-02-04 Thread Satish Balay via petsc-users
On Fri, 4 Feb 2022, Barry Smith wrote: > > > > On Feb 4, 2022, at 12:38 PM, Satish Balay wrote: > > > > On Fri, 4 Feb 2022, Barry Smith wrote: > > > >> > >> > >>> On Feb 4, 2022, at 12:27 PM, Satish Balay wrote: > >>> > >>> Probably best if you can use the same version of gfortran to

[petsc-users] Matrix preallocation

2022-02-04 Thread Samuel Estes
Hi, I have a very basic question about matrix preallocation. I am trying to use the MatCreate(), MatSetFromOptions(), MatSetPreallocation() paradigm. I thought that I should use the MatXAIJSetPreallocation() routine since the code may be run with a SeqAIJ or MPIAIJ matrix but I do not

Re: [petsc-users] 3.16.4 amd blis libflame linking problem

2022-02-04 Thread Anton Popov
Am 04.02.2022 um 18:54 schrieb Satish Balay: On Fri, 4 Feb 2022, Anton Popov wrote: Thanks Matt, Barry and Satish, for  your suggestions. The problem was indeed in mismatch between the gfortran library version (system has libgfortran.so.4 libflame needs libgfortran.so.5) 3.9.4 did not

Re: [petsc-users] 3.16.4 amd blis libflame linking problem

2022-02-04 Thread Satish Balay via petsc-users
On Fri, 4 Feb 2022, Anton Popov wrote: > > Am 04.02.2022 um 18:54 schrieb Satish Balay: > > On Fri, 4 Feb 2022, Anton Popov wrote: > > > >> Thanks Matt, Barry and Satish, for  your suggestions. > >> > >> The problem was indeed in mismatch between the gfortran library version > >> (system has