configure: update CMake
Merge remote-tracking branch 'origin/release'
Add initial version PetscRegressor, part of the planned machine learning (ML) toolkitCo-authored-by: Mr. Hong Zhang <hongzhang@anl.gov>Co-authored-by: Hansol Suh <hsuh@anl.gov>Co-authored-by: Bar
Add initial version PetscRegressor, part of the planned machine learning (ML) toolkitCo-authored-by: Mr. Hong Zhang <hongzhang@anl.gov>Co-authored-by: Hansol Suh <hsuh@anl.gov>Co-authored-by: Barry Smith <bsmith@petsc.dev>Co-authored-by: Toby Isaac <toby.isaac@gmail.com>Co-authored-by: Satish Balay <balay@mcs.anl.gov>Mr. Hong Zhang developed the petsc4py interface and examples.Hansol Suh provided extensive help with updating the code to the latest PETSc coding guidelines and APIs, some documentation development, getting documentation to build correctly, getting new tests into the test harness, and numerous big fixes plus minor changes.Barry Smith provided extensive feedback and code to get the Fortran interfaces and documentation build working.Toby Isaac provided a fix to prevent breakage with complex-arithmetic builds.Satish Balay provided important help with fixing builds.Thanks-to: Pierre Jolivet <pierre@joliv.et>Thanks-to: Jed Brown <jed@jedbrown.org>Thanks-to: Jose Roman <jroman@dsic.upv.es>Thanks-to: Stefano Zampini <stefano.zampini@gmail.com>Pierre, Jed, Jose, and Stefano provided extremely helpful feedback and suggestions during the merge review process.
show more ...
configure: update muparser/ScaLAPACK to avoid failures with CMake 4.0.0
CMake: add necessary flags for deprecated packages
Prevent the Fortran binding generating from including include files in themselves.Reported-by: Jed Brown
Merge branch 'ptscotch-bison' into 'release'ptscotch: bison is only required to build, not linkSee merge request petsc/petsc!8267
Merge branch 'balay/petsc4py-py-ver-check' into 'release'petsc4py: update python version check [min 3.6]See merge request petsc/petsc!8251
configure: update HYPRE and p4est
Fix wrong case for PETSc
ptscotch: bison is only required to build, not link
petsc4py: update python version check [min 3.6]
Fix typos
configure: SLEPc v3.23.0
configure: SLEPc v3.023.0
SLEPc: update to latest (pre-3.23.0) snapshot
generatefortranstubs: move out of maint (to config/utils)- as its needed in tarball
Kokkos: update to 4.6.00
Merge branch 'jczhang/2025-03-19/update-frontier-script' into 'main'Update arch-olcf-frontier-opt.pySee merge request petsc/petsc!8212
configure: update HPDDM and SLEPc
Minor cleanup of Fortran binding stuff to simplify future maintainanceThere is no distinction between F90 and non-F90 code so combine ftn-custom and f90-custom directories and fortranimpl.h and f90
Minor cleanup of Fortran binding stuff to simplify future maintainanceThere is no distinction between F90 and non-F90 code so combine ftn-custom and f90-custom directories and fortranimpl.h and f90impl.h files. Also move uses of f90 to ftn when simple
CI: test PETSC_HAVE_FORTRAN_UNDERSCORE via arch-ci-macos-opt-armCI: test PETSC_HAVE_FORTRAN_UNDERSCORE_UNDERSCORE via clang-uni
config: Update CGNS version to latest releaseAlso fix up plex/tests/ex100 compiler warning
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 modulesCo-authored-by: Jose E. Roman <jroman@dsic.upv.es>
1...<<11121314151617181920>>...430