petsc now requires f90 - so remove some of the f77 specific flags/code -i.e remove USE_FORTRANKIND [and special code for unsupported Compaq-F90]

This part of code isn't getting tested anyway.

Merge remote-tracking branch 'origin/maint'

git grep -l "seperate" | xargs sed -i '' -e 's/seperate/separate/g'

Commit-type: spelling-fix
Reported-by: Pierre JOLIVET <Pierre.Jolivet@enseeiht.fr>

Add support for users to pass in FFLAGS the option for promoting integers to 8 bytes.

Tested for ifort and gfortran

Tested with MPICH and OpenMPI and MPI-Uni

Since MPI does not provide any mechani

Add support for users to pass in FFLAGS the option for promoting integers to 8 bytes.

Tested for ifort and gfortran

Tested with MPICH and OpenMPI and MPI-Uni

Since MPI does not provide any mechanism for integer promotion the code very crudely adjusts the
values in the mpif.h to mark them as 4 byte integers this is not neccessary portable for all MPI implementations

This is an extremely fragile option that we should probably not be supporting.

Users must insure their Fortran codes passes only 4 byte integers to MPI calls

PETSc Fortran examples were all fixed to explicitly use 4 byte integers for MPI calls.

Commit-type: portability-fix, testing-fix, feature
Time: 20 hours
Reported-by: Dmitry Melnichuk <dmitry.melnichuk@geosteertech.com>

show more ...

Merge remote-tracking branch 'origin/maint'

MatSetValues calls =%D => MatSetValues calls=%D

Replace use of 1 with appropriate error code; use PetscObjecComm() instead of PETSC_COMM_SELF for errors when appropriate

Commit-type: error-checking, testing-fix, style-fix, examples