Plex: Now allow variable bounds along boundaries- Add DM_BC_LOWER_BOUND and DM_BC_LOWER_BOUND- Add DMHasBound()- Add DMPlexInsertBounds() and implementation DMPlexInsertBounds_Plex()
Merge remote-tracking branch 'origin/release'
Remove the last of the uses of $ in the first line of formatted manual pages
Do not expose unneeded symbols
Remove dead code
Remove unneeded variable and functions
Merge branch 'barry/2025-04-09/docs-dmproduct/release' into 'release'Improve docs for DMPRODUCT and add a viewerSee merge request petsc/petsc!8300
Improve docs for DMPRODUCT and add a viewer
Merge branch 'barry/2025-04-04/add-fortran-dmcreatefielddecomposition/release' into 'release'Add Fortran binding for dmcreatefielddecompositionSee merge request petsc/petsc!8276
Add Fortran support for DMCreateFieldDecompositionIncludes test with DMDA
Bug fixes for DMDA not handling Matt's plex handling of fields that he assumes works for all DM, not just DMPLEX
Fix -Whigher-precision-for-complex-division with Intel oneAPI 2025.1.0src/mat/impls/mffd/mffddef.c:78:31: warning: excess precision is requested but the target does not support excess precision whi
Fix -Whigher-precision-for-complex-division with Intel oneAPI 2025.1.0src/mat/impls/mffd/mffddef.c:78:31: warning: excess precision is requested but the target does not support excess precision which may result in observable differences in complex division behavior [-Whigher-precision-for-complex-division] 78 | *h = ctx->error_rel * dot / (nrm * nrm); | ^1 warning generated.src/dm/interface/dmgeommodel.c:42:77: warning: excess precision is requested but the target does not support excess precision which may result in observable differences in complex division behavior [-Whigher-precision-for-complex-division] 42 | for (PetscInt d = 0; d < dE - 1; ++d) gcoords[d] = gmax[0] * mcoords[d] / norm; | ^src/ksp/ksp/impls/bcgs/qmrcgs/qmrcgs.c:117:32: warning: excess precision is requested but the target does not support excess precision which may result in observable differences in complex division behavior, additional uses where the requested higher precision cannot be honored were found but not diagnosed [-Whigher-precision-for-complex-division] 117 | cf = theta * theta * eta / alpha; | ^src/mat/impls/dense/seq/dense.c:1043:73: warning: excess precision is requested but the target does not support excess precision which may result in observable differences in complex division behavior, additional uses where the requested higher precision cannot be honored were found but not diagnosed [-Whigher-precision-for-complex-division] 1043 | x[i] = (1. - omega) * x[i] + omega * (xt + v[i + i * m] * x[i]) / (v[i + i * m] + shift); | ^
show more ...
Plex: Add ability to save a mesh transform
Merge branch 'jolivet/fix-typos' into 'release'Fix typosSee merge request petsc/petsc!8259
Fix manual pages related to FortranRemove a couple of dead Fortran bindings
Fix typos
PetscLayout: default block size 1
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
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>
DMAddBoundary: fix docs
12345678910>>...60