[petsc-dev] gcc 10

[Satish Balay]

Here is the (ARM) build with gnu-10 compilers

https://gitlab.com/petsc/petsc/-/jobs/636087963

Compilers:
  C Compiler:         mpicc  -Wall -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -fstack-protector -fvisibility=hidden -g -O  
    Version: gcc (GCC) 10.1.1 20200507 (Red Hat 10.1.1-1)
  C++ Compiler:       mpicxx  -Wall -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -fstack-protector -fvisibility=hidden -g -O   
    Version: g++ (GCC) 10.1.1 20200507 (Red Hat 10.1.1-1)
  Fortran Compiler:   mpif90  -Wall -ffree-line-length-0 -Wno-unused-dummy-argument -g -O  
    Version: GNU Fortran (GCC) 10.1.1 20200507 (Red Hat 10.1.1-1)

Satish

On Mon, 13 Jul 2020, Satish Balay via petsc-dev wrote:

> Yeah - we fixed PETSc [maint] to not require -fallow-argument-mismatch - and use it only with externalpacakges that need it
> 
> And we do have one test box with gfortran-10 - but the test coverage with it is minimal. [mostly no externalpacakges]
> 
> Satish
> 
> On Mon, 13 Jul 2020, Jed Brown wrote:
> 
> > You want this for PETSc or for external packages?  We add it for a bunch of external packages.  I've been building PETSc with gcc/gfortran-10 for months now.
> > 
> > Matthew Knepley <knepley at gmail.com> writes:
> > 
> > > Do we have gfortran from gcc 10 running anywhere? We need a check to enable
> > >
> > >   -fallow-argument-mismatch
> > >
> > > from configure. Should be as simple as compiling Fortran which has
> > > PetscObjectSetName() in it.
> > >
> > >   Thanks,
> > >
> > >       Matt
> > >
> > > -- 
> > > What most experimenters take for granted before they begin their
> > > experiments is infinitely more interesting than any results to which their
> > > experiments lead.
> > > -- Norbert Wiener
> > >
> > > https://www.cse.buffalo.edu/~knepley/ <http://www.cse.buffalo.edu/~knepley/>
> > 
>