[petsc-dev] ?????? Petsc: Error code 1

ARM: configure with the following: -ffp-contract=off ./configure -with-debugging=0 COPTFLAGS='-O3 -ffp-contract=off -march=armv8.2-a -mtune=tsv110' CXXOPTFLAGS='-O3 -ffp-contract=off -march=armv8.2-a -mtune=tsv110' FOPTFLAGS='-O3 -ffp-contract=off -march=armv8.2-a -mtune=tsv110' --with-x=1 -do

[petsc-dev] ?????? Petsc: Error code 1

ARM: configure with the following: -ffp-contract=off ./configure -with-debugging=0 COPTFLAGS='-O3 -ffp-contract=off -march=armv8.2-a -mtune=tsv110' CXXOPTFLAGS='-O3 -ffp-contract=off -march=armv8.2-a -mtune=tsv110' FOPTFLAGS='-O3 -ffp-contract=off -march=armv8.2-a -mtune=tsv110' --with-x=1 -do

[petsc-dev] ?????? Petsc: Error code 1

ARM: configure with the following: -ffp-contract=off ./configure -with-debugging=0 COPTFLAGS='-O3 -ffp-contract=off -march=armv8.2-a -mtune=tsv110' CXXOPTFLAGS='-O3 -ffp-contract=off -march=armv8.2-a -mtune=tsv110' FOPTFLAGS='-O3 -ffp-contract=off -march=armv8.2-a -mtune=tsv110' --with-x=1 -do

[petsc-dev] ?????? Petsc: Error code 1

On ARM?? don't use O3?? configure like this # ./configure  --download-fblaslapack No fail. So the failure is related to the Code Optimization level. I guess maybe it related to the fmadd of the ARM cpu. I will try O3 and shutdown the fmadd again to see how it will go. # - #   Su

[petsc-dev] ?????? Petsc: Error code 1

Here is my configure options: ./configure -with-debugging=0 COPTFLAGS='-O3 -march=armv8.2-a -mtune=tsv110' CXXOPTFLAGS='-O3 -march=armv8.2-a -mtune=tsv110' FOPTFLAGS='-O3 -march=armv8.2-a -mtune=tsv110' --with-x=1 -download-fblaslapack PETSC-KERNEL-USE-UNROLL-4 --force The gcc is 9.3.1, the

Re: [petsc-dev] DMNetwork static sizing

Hong, It was just to keep things simple. We can have an API (and a run-time option) for setting the max. number of components instead of a configure option. I can work on making this change. Thanks, Shri From: petsc-dev on behalf of PETSc Development Reply-To: "Zhang, Hong" Date: Tuesday,

Re: [petsc-dev] (arm64) could not find object file symbol for symbol ___muldc3

Blaise, Thanks, can you try cd src/snes/tutorials and then cut and paste the huge line that you sent earlier that begins with mpif90 -Wl,-bind_at_load . and add at the end -lgcc and see if that line successfully links the Fortran code? Thanks Barry > On Apr 6, 2021, at 1

Re: [petsc-dev] DMNetwork static sizing

Shri, You designed this approach. Is it intended or out of implementation convenience at the time? Hong From: petsc-dev on behalf of Matthew Knepley Sent: Monday, April 5, 2021 5:47 AM To: PETSc Subject: [petsc-dev] DMNetwork static sizing Dowe really need a c

Re: [petsc-dev] -with-kokkos-cuda-arch=AMPERE80 nonsense

On Tue, Apr 6, 2021 at 2:08 PM Scott Kruger wrote: > > I wrote sent this yesterday but am having some strange mailing issues. > > On 2021-04-03 22:42, Barry Smith did write: > > > > It would be very nice to NOT require PETSc users to provide this flag, > how the heck will they know what it shou

Re: [petsc-dev] -with-kokkos-cuda-arch=AMPERE80 nonsense

I wrote sent this yesterday but am having some strange mailing issues. On 2021-04-03 22:42, Barry Smith did write: > > It would be very nice to NOT require PETSc users to provide this flag, how > the heck will they know what it should be when we cannot automate it > ourselves? > > Any i

Re: [petsc-dev] Petsc: Error code 1

> On Apr 6, 2021, at 12:06 PM, Satish Balay wrote: > >> See the attachements. alltest.log is on a machine with 96 cores, ARM, with >> FC,gcc9.3.5,mpich3.4.1,fblaslapack; 6 failures > > Perhaps this is an issue with ARM - and such diffs are expected - as we > already have multiple alt files

Re: [petsc-dev] Petsc: Error code 1

> See the attachements. alltest.log is on a machine with 96 cores, ARM, with > FC,gcc9.3.5,mpich3.4.1,fblaslapack; 6 failures Perhaps this is an issue with ARM - and such diffs are expected - as we already have multiple alt files for some of these tests $ ls -lt src/tao/bound/tutorials/output/p

Re: [petsc-dev] (arm64) could not find object file symbol for symbol ___muldc3

Blaise, Please send configure.log It would also be helpful if you could run nm -o /usr/lib/lib* | grep muldc3 Our cross language linker tests are not adding all the libraries they need to add when using Fortran for linking. Barry > On Apr 6, 2021, at 11:00 AM, Matthew Knepl

Re: [petsc-dev] Petsc: Error code 1

    Alp,   Except for the first test, these are all optimization problems (mostly in Fortran). The function values are very different so I am sending it to our optimization expert to take a look at it. The differences could possibly be related to the use of real() and maybe the direct use of floati

Re: [petsc-dev] Petsc: Error code 1 TS adapt difference

   Emil and Hong,   In this test the GLEE time step adapter is making a different decision on accepting or rejecting a step. It could be due to slight differences in round-off for different machines and compilers. I leave it to our ODE experts to take a look at it.  Barry alltests2.log Description

Re: [petsc-dev] -with-kokkos-cuda-arch=AMPERE80 nonsense

Jeff, Likely deviceQuery provides more than enough information; sometimes it is prebuilt but it seems now it is only provided as source code so the user needs to build it (and the Makefile is huge :-)). I think it would be enough if NVIDIA just always provided prebuilt deviceQuery in

Re: [petsc-dev] (arm64) could not find object file symbol for symbol ___muldc3

On Tue, Apr 6, 2021 at 11:04 AM Blaise A Bourdin wrote: > Hi, > > I am having the following warning when compiling any fortran example > (currently on main, but it’s been going on for a little while) on a ARM > mac. > > > ***Error detected during compile or > link!***

Re: [petsc-dev] Regression in manualpages generation?

> On 6 Apr 2021, at 5:03 PM, Satish Balay wrote: > > > https://www.mcs.anl.gov/petsc/petsc-current/ is from petsc-3.15.0 - > and is normally gets updated with the next patch release - i.e > petsc-3.15.1. [ok - I'll update now with current release snapshot] Ah, of course, I don’t know why I ch

[petsc-dev] (arm64) could not find object file symbol for symbol ___muldc3

Hi, I am having the following warning when compiling any fortran example (currently on main, but it’s been going on for a little while) on a ARM mac. ***Error detected during compile or link!*** See http://www.mcs.anl.gov/petsc/documentation/faq.html /opt/HPC/pe

Re: [petsc-dev] Regression in manualpages generation?

https://www.mcs.anl.gov/petsc/petsc-current/ is from petsc-3.15.0 - and is normally gets updated with the next patch release - i.e petsc-3.15.1. [ok - I'll update now with current release snapshot] Also dev pages should get updated daily [there is a bug here that I should fix] With the latest sn

Re: [petsc-dev] Regression in manualpages generation?

Thanks for the recent MR. This sadly only partially addresses the issue. https://www.mcs.anl.gov/petsc/petsc-3.14.6/docs/manualpages/Mat/MatGetRow.html correctly has MatGetRow_MPIDense while https://www.mcs.anl.gov/

[petsc-dev] ?????? Petsc: Error code 1

See the attachements. alltest.log is on a machine with 96 cores, ARM, with FC,gcc9.3.5,mpich3.4.1,fblaslapack; 6 failures                                  alltest2.log is on an intel machine with 40  cores,x86, without FC; icc&mkl& intel mpi; only 1 failure --