Docs: fix wrong occurences of then instead of than
Merge remote-tracking branch 'origin/release'
Fix capitalization of fortranCommit-type: housekeeping
Rename rules.doc and rules.utils because GitLab treats the former as a MS Word document.Thanks-to: Jed Brown
Fix use of offdiagonal to off-diagonal
Fix uneven back ticks
Delete unused code
Add static to internal functions
Manual fixes needed for linter for the KSP directory
Track levels of nesting of KSP, for example KSPBJACOBI has nesting 1 higher than the calling KSP
Remove nested declaration of variable pcCommit-type: housekeeping
... and apply it
Rename PetscValidPointer -> PetscAssertPointer
Deploy new PetscValidPointer, remove PetscValidXXXPointer
Fix -Wextra-semi-stmt
Lint apply: ksp
HAVE_FORTRAN should be USE_FORTRAN_BINDINGS since it is about generating the Fortran bindings, not about if the Fortran compiler exists
Fix gcc-13 -Warray-bounds warnings involving hypothetical negative sizesStatic analysis should be able to prove that these are alwaysnon-negative, but we can use PetscMax(s, 0) to avoid triggering
Fix gcc-13 -Warray-bounds warnings involving hypothetical negative sizesStatic analysis should be able to prove that these are alwaysnon-negative, but we can use PetscMax(s, 0) to avoid triggering thiswarning.In function ‘PetscMemcpy’, inlined from ‘TSRKRegister’ at /home/jed/petsc/src/ts/impls/explicit/rk/rk.c:470:10:/home/jed/petsc/include/petscstring.h:711:3: warning: ‘memcpy’ pointer overflow between offset 0 and size [-17179869184, -8] [-Warray-bounds=] 711 | memcpy(a, b, n); | ^~~~~~~~~~~~~~~
show more ...
Change use of PetscRealPart() for PetscMalloc to corresponding PetscBLASInt value
Clean up manual page for KSPFETIDP
MatGetFactor: support returning NULLThis is only for those combinations that cannot be checked if not at runtime
Fix PetscCallMPI(MPI_Allreduce()) with PETSc types
Fix documentation
12345678910>>...53