Merge branch 'barry/2025-12-27/ftn-rm-funname-interface-definition' into 'main'

Remove the function name from generated Fortran interface definitions.

Closes #1838

See merge request petsc/petsc!89

Merge branch 'barry/2025-12-27/ftn-rm-funname-interface-definition' into 'main'

Remove the function name from generated Fortran interface definitions.

Closes #1838

See merge request petsc/petsc!8921

show more ...

Fortran 2008 has unlimited polymorphic/'*'

Merge branch 'barry/2025-12-04/fix-use-mpi-f08' into 'main'

Replace -with-mpi-f90module-visibility with -with-mpi-ftn-module=mpi_f08

See merge request petsc/petsc!8885

Replace -with-mpi-f90module-visibility with -with-mpi-f90module=mpi_f08

Add PETSC_INT_KIND and PETSC_MPIINT_KIND

Reported-by: M.Weiland@epcc.ed.ac.uk

Merge branch 'MarDiehl/improve-Fortran-examples' into 'main'

Improve Fortran examples

See merge request petsc/petsc!8698

place all the include statements at the top

Repeated inclusion in multiple location, e.g. at the start of a
module or function is not needed. This becomes clear if all includes are
outside of the ac

place all the include statements at the top

Repeated inclusion in multiple location, e.g. at the start of a
module or function is not needed. This becomes clear if all includes are
outside of the actual Fortran code.
Added regex to check that with the help of @sbalay

show more ...

Merge branch 'barry/2025-07-01/format-fortran-source-fprettify' into 'main'

format fortran source with fprettify

See merge request petsc/petsc!8514

Run fprettify

Merge branch 'barry/2025-07-02/fortran-no-semicolon-end-of-line' into 'main'

fortran no semicolon at end of line

See merge request petsc/petsc!8519

fortran no semicolon at end of line

Remove all unneeded ; at end of Fortran source code line

Add checkbadSource to check for semicolon at the end of lines

Merge branch 'barry/2024-04-29/add-fortran-enums' into 'main'

Major updates to Fortran interface

See merge request petsc/petsc!7517

Fortran 90: fully embrace After 34 years!

- deprecate use of 'F90' in Fortran function names
- use Fortran pointers when appropriate
- the new Fortran API is not backward compatible with previous ve

Fortran 90: fully embrace After 34 years!

- deprecate use of 'F90' in Fortran function names
- use Fortran pointers when appropriate
- the new Fortran API is not backward compatible with previous versions!
- also clean up inconsistent PETSc code detected by new Fortran generation tools
- drop use of bfort
- automatically generate all the Fortran PETSc objects, enums etc from the include files
- generate most of the Fortran interface definitions and functions from the source code
- simplify the number and organization of Fortran modules

Co-authored-by: Jose E. Roman <jroman@dsic.upv.es>

show more ...

Merge branch 'barry/2024-09-02/rebased-fix-conversion-warnings' into 'main'

Compiler finds (and forbid) casts from higher precision integers to lower

See merge request petsc/petsc!7806

Add to CI compilers flags '-Wconversion', '-Wno-sign-conversion', '-Wno-float-conversion', '-Wno-implicit-float-conversion']

Also fix the code to repository to compile cleanly with these flags in th

Add to CI compilers flags '-Wconversion', '-Wno-sign-conversion', '-Wno-float-conversion', '-Wno-implicit-float-conversion']

Also fix the code to repository to compile cleanly with these flags in the CI

show more ...

Merge branch 'barry/2024-05-29/minor-fortran-stub-cleanup' into 'main'

More improvements to Fortran stubs and interfaces

See merge request petsc/petsc!7598

This requires some changes to user FORTRAN code

Pass PETSC_NULL_XXX_ARRAY when passing a NULL as an argument that is expecting an array
Pass PETSC_NULL_ENUM when argument returns an enum instead of

This requires some changes to user FORTRAN code

Pass PETSC_NULL_XXX_ARRAY when passing a NULL as an argument that is expecting an array
Pass PETSC_NULL_ENUM when argument returns an enum instead of PETSC_NULL_INTEGER
Pass arrays (and not scalar values) when the argument is expecting an array; this means replace, for example, the argument v with [v]
Use PetscObjectIsNull(obj) to check if the object is NULL, instead of obj == PETSC_NULL_XXX

The compiler will now automatically prevent you from using the wrong argument type for the first three bullets above
This will also require an update sowing with the new sowing branch this MR is using.

show more ...

Merge branch 'jolivet/rm-first-empty-line' into 'main'

Remove first and last empty lines

See merge request petsc/petsc!6892

Remove first and last empty lines

Merge branch 'barry/2023-05-14/add-fortran-petsccheck' into 'main'

Add PetscCheck() and PetscCheckA() for Fortran

See merge request petsc/petsc!6464

Add PetscCheck() and PetscCheckA() for Fortran

Also fix incorrect use of " in Fortran examples that should be '

Merge remote-tracking branch 'origin/release'

Merge branch 'jolivet/fix-typos' into 'release'

Fix Typos

See merge request petsc/petsc!6024

Fix Typos

Merge branch 'narnoldm/petscsf-add-petscsfreduce' into 'main'

PetscSF: Add Fortran Interface for PetscSFReduce

See merge request petsc/petsc!5987

PetscSF: Add Fortran Interface for PetscSFReduce