Fix memory when reuse reordering is used with matrices with different nonzero patterns.Reported-by: Markus Breit
PCHPDDM: remove wrong comment
PCHPDDM: use proper PetscOptions
PCFIELDSPLIT: skip ISComplement() to get the proper block size
PCHPDDM: add support for MAT_SCHUR_COMPLEMENT_AINV_BLOCK_DIAG
Packages: add Caliper, a profiling package used by Hypre
PCBDDCSubSchursSetUp: handle the case when size of the schur complement is the size of the local element
PCBDDCSetUpCorrection: do not use the factored matrix if KSP is not preonly
Rework MAT_SYMMETRIC and MAT_HERMITIAN options
Merge branch 'release'
Merge branch 'jolivet/pchpddm-iscreatestride-error' into 'release'PCHPDDM: check for dense rows in A_10See merge request petsc/petsc!8873
Merge branch 'barry/2025-11-24/fix-pc-factor-nonzeros-along-diagonal/release' into 'release'Crash when using MUMPs sequentially with -pc_factor_nonzeros_along_diagonal...See merge request petsc/p
Merge branch 'barry/2025-11-24/fix-pc-factor-nonzeros-along-diagonal/release' into 'release'Crash when using MUMPs sequentially with -pc_factor_nonzeros_along_diagonal...See merge request petsc/petsc!8866
show more ...
PCHPDDM: check for dense rows in A_10Reported-by: Bahaâ Eddine Sidi Hida <bahaa-eddine.sidi-hida@edf.fr>
Fix typos
PCTELESCOPE: fix missing MatPropagateSymmetryOptions()
Crash when using MUMPs sequentially with -pc_factor_nonzeros_along_diagonal but using MUMPS ordering.$ PETSC_OPTIONS="-pc_factor_mat_ordering_type external" python pythonprogram.py[0]PETSC ERROR:
Crash when using MUMPs sequentially with -pc_factor_nonzeros_along_diagonal but using MUMPS ordering.$ PETSC_OPTIONS="-pc_factor_mat_ordering_type external" python pythonprogram.py[0]PETSC ERROR: ------------------------------------------------------------------------[0]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range[0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger[0]PETSC ERROR: or see https://petsc.org/release/faq/#valgrind and https://petsc.org/release/faq/[0]PETSC ERROR: --------------------- Stack Frames ------------------------------------The line numbers in the error traceback are not always exact.[0] #1 MatReorderForNonzeroDiagonal_SeqAIJ() at /Users/barrysmith/Src/petsc/src/mat/utils/zerodiag.c:77[0] #2 MatReorderForNonzeroDiagonal() at /Users/barrysmith/Src/petsc/src/mat/utils/zerodiag.c:61[0] #3 PCSetUp_LU() at /Users/barrysmith/Src/petsc/src/ksp/pc/impls/factor/lu/lu.c:84[0] #4 PCSetUp() at /Users/barrysmith/Src/petsc/src/ksp/pc/interface/precon.c:1120[0] #5 KSPSetUp() at /Users/barrysmith/Src/petsc/src/ksp/ksp/interface/itfunc.c:429Bug was it still tried the nonzero diagonal reordering even when the ordering type was external so PETSc did not generate an orderingAlso fixed bug in PCSetUp_Cholesky() where it used GetBool on -pc_factor_nonzeros_along_diagonal when the argument may be followed by a numerical valueReported-by: Jørgen Dokken
PCHPDDM: add safeguards for -pc_hpddm_has_neumann
Merge branch 'barry/2025-10-18/optimize-aij-ops' into 'main'Refactor handling of diagonal marking in *AIJ and SELL matricesSee merge request petsc/petsc!8797
- Replace MatMissingDiagonal() and MatMarkDiagonals_SeqXXX() with MatGetDiagonalMarkers_SeqXXX() - Mat_SeqXXX->diag is not automatically created during MatAssemblyEnd() saving memory and time
- Replace MatMissingDiagonal() and MatMarkDiagonals_SeqXXX() with MatGetDiagonalMarkers_SeqXXX() - Mat_SeqXXX->diag is not automatically created during MatAssemblyEnd() saving memory and time - Accessing Mat_SeqXXX->diag now requires the use of MatGetDiagonalMarkers_SeqXXX() except when the current values are known to be correct; for example during numerical factorizations and solves - Mat_SeqXXX->diag is now never shared among matrices; hence the free_diag flag is gone. That was always a risky proposition since any of the owning matrices could chang the values thus making them incorrect for other owners.
Merge branch 'zach/add-petsccallhypre' into 'main'Add PetscCallHYPRE to properly handle and display HYPRE error codesSee merge request petsc/petsc!8790
Fix terminology for Pmat in KSPView output.
hypre: Use PetscCallHYPRE for member functions
hypre: Fix compiler warnings for mixed int configuration
hypre: Add PetscCallHYPRE macro to allow for printing HYPRE error strings
PCHPDDM: add support for MatProduct_AtB_Harmonic
12345678910>>...210