Remove the function name from generated Fortran interface definitions.Except for polymorphic functions PetscObjectXXX and PetscBarrierReported-by: Martin Diehl
Merge branch 'barry/2025-12-04/fix-use-mpi-f08' into 'main'Replace -with-mpi-f90module-visibility with -with-mpi-ftn-module=mpi_f08See merge request petsc/petsc!8885
Kokkos: update to v5.0.0CI: remove kokkos from linux-cuda-pkgs (in favor of linux-kokkos-cuda) as v5 breaks with many external pkgs,CI: continue to use kokkos v4.7.01 for hip builds - as they curr
Kokkos: update to v5.0.0CI: remove kokkos from linux-cuda-pkgs (in favor of linux-kokkos-cuda) as v5 breaks with many external pkgs,CI: continue to use kokkos v4.7.01 for hip builds - as they currently use rocm-5.4.3Co-authored-by: Satish Balay <balay@mcs.anl.gov>
show more ...
Replace -with-mpi-f90module-visibility with -with-mpi-f90module=mpi_f08Add PETSC_INT_KIND and PETSC_MPIINT_KINDReported-by: M.Weiland@epcc.ed.ac.uk
Use the same getAPI.py and generatefortranbindings.py scripts for both PETSc and SLEPcIncludes some cleanup of the scripts
configure: removed unused regex package
Fortran is always F2003: removed leftovers
remove labeled do loopslabeled do loops confused fprettify, so used it to rectify indentation
place all the include statements at the topRepeated inclusion in multiple location, e.g. at the start of amodule or function is not needed. This becomes clear if all includes areoutside of the ac
place all the include statements at the topRepeated inclusion in multiple location, e.g. at the start of amodule or function is not needed. This becomes clear if all includes areoutside of the actual Fortran code.Added regex to check that with the help of @sbalay
checkbadSource: add GITFSRC and remove duplicate '*.[hF]90'Co-authored-by: Satish Balay <balay@mcs.anl.gov>
checkbadSource: check style of config/*
Remove more unneeded parentheses
Merge remote-tracking branch 'origin/release'
Merge branch 'jczhang/2025-10-09/make-check-verbose' into 'main'Support make check V=1See merge request petsc/petsc!8775
Build: improve LINK.kokkos.cxx rulesThanks to: Steven Dargaville (@stevendargaville)close #1818
Merge branch 'jczhang/2024-06-26/revise-mpi-openmp-stream' into 'main'Revise MPI and OpenMP stream benchmarksSee merge request petsc/petsc!7651
Build: print compile command, PWD - when compiling examples via 'make check V=1'
clangformat: apply to src/src/benchmarks
checkbadSource: enforce proper style in makefiles
make: update PETSC_COMPILE_SINGLE etc. targets to use '$@' instead of '$*.o' to enable usage with multiple dirsFix SEPARATE_COMPILE_LINK=1 targets (used by sycl, ms/c++) to use '$@.o' for intermedi
make: update PETSC_COMPILE_SINGLE etc. targets to use '$@' instead of '$*.o' to enable usage with multiple dirsFix SEPARATE_COMPILE_LINK=1 targets (used by sycl, ms/c++) to use '$@.o' for intermediate obj files
script to check fortran binding coverage
Remove more unneeded braces
better debugging capabilitiesusing MPIU wrappers where available and PetscCallMPI for all MPI(U)functions
use standard bool instead of enumPetscBool is equivalent to _Bool/bool in CFor C standards prior to C23, true = 1 and false = 0 are defined in <stdbool.h>.For C23, true and false are real keywor
use standard bool instead of enumPetscBool is equivalent to _Bool/bool in CFor C standards prior to C23, true = 1 and false = 0 are defined in <stdbool.h>.For C23, true and false are real keywords.The Fortran equivalent is logical(C_BOOL) with C_BOOL fromISO_C_binding.The C and the C++ standard do not specify the size of Booleans, but theytypically have a size of 1 Byte with b00000000 for false and b00000001 for true.When using compilers from the same vendor, it is sane to assume that_Bool/bool in C and bool in C++ are fully compatible. But that is notguaranteed by the standards
clang-format: update to v21 (and update CI)
12345678910>>...48