Fix MPIU_* routines to always return MPI error codes and thus be usable with PetscCallMPI()

Introduce MPIU_Count to be used when MPI_Count is not available

Change from deprecated PETSC_MAX/MIN_INT to PETSC_INT_MAX/MIN

Commit-type: i.e. error-checking, optimization, bug-fix, portability-fix, testing-fix, style-fix, feature, documentation, example
Funded

Change from deprecated PETSC_MAX/MIN_INT to PETSC_INT_MAX/MIN

Commit-type: i.e. error-checking, optimization, bug-fix, portability-fix, testing-fix, style-fix, feature, documentation, example
Funded-by:
Project:
Time: hours
Reported-by:
Thanks-to:
Development Tools: Vim, Emacs, Eclipse

show more ...

Add support to MPIU_Allreduce to prevent int overflow with a single integer argument

Add to CI compilers flags '-Wconversion', '-Wno-sign-conversion', '-Wno-float-conversion', '-Wno-implicit-float-conversion']

Also fix the code to repository to compile cleanly with these flags in th

Add to CI compilers flags '-Wconversion', '-Wno-sign-conversion', '-Wno-float-conversion', '-Wno-implicit-float-conversion']

Also fix the code to repository to compile cleanly with these flags in the CI

show more ...

Fix usage of deprecated PETSC_DEFAULT

Deprecate PETSC_DEFAULT for Tao parameters with PETSC_CURRENT and add support for PETSC_DETEREMINE to use default

Merge remote-tracking branch 'origin/release'

Merge branch 'barry/2024-07-09/improve-docs-taogradientnorm/release' into 'release'

Clarify manual page for TaoGradientNorm(), other minor fixes.

See merge request petsc/petsc!7679

Docs: fix nonexisting functions and variables

Clarify manual page for TaoGradientNorm(), other minor fixes.

Reported-by: Sebastian Blauth <sebastian.blauth@itwm.fraunhofer.de>

This requires some changes to user FORTRAN code

Pass PETSC_NULL_XXX_ARRAY when passing a NULL as an argument that is expecting an array
Pass PETSC_NULL_ENUM when argument returns an enum instead of

This requires some changes to user FORTRAN code

Pass PETSC_NULL_XXX_ARRAY when passing a NULL as an argument that is expecting an array
Pass PETSC_NULL_ENUM when argument returns an enum instead of PETSC_NULL_INTEGER
Pass arrays (and not scalar values) when the argument is expecting an array; this means replace, for example, the argument v with [v]
Use PetscObjectIsNull(obj) to check if the object is NULL, instead of obj == PETSC_NULL_XXX

The compiler will now automatically prevent you from using the wrong argument type for the first three bullets above
This will also require an update sowing with the new sowing branch this MR is using.

show more ...

All constructors should do PetscAssertPointer on output object

Reported-by: Blaise Bourdin

Constructors should not initialize the output to NULL upon entry, serves no purpose

Fix some formatting i

All constructors should do PetscAssertPointer on output object

Reported-by: Blaise Bourdin

Constructors should not initialize the output to NULL upon entry, serves no purpose

Fix some formatting in constructors

show more ...

TAO: clarify usage of update hook

fix implementations

Update sowing bfort for automatic generation of XXXDestroy() code

Fix some Fortran stub code to work with generation of XXXDestroy()

Add some runtime tests for XXXCreate() calls

Also update sowing

Update sowing bfort for automatic generation of XXXDestroy() code

Fix some Fortran stub code to work with generation of XXXDestroy()

Add some runtime tests for XXXCreate() calls

Also update sowing and fortranimpl.h to use PETSC_NULLPTR instead of NULL

show more ...

Update to sowing version that supports PetscViewer and PetscObject

Remove manual Fortran stubs for PetscViewer and PetscObject arguments since now handled by sowing

Also handles the passing of null

Update to sowing version that supports PetscViewer and PetscObject

Remove manual Fortran stubs for PetscViewer and PetscObject arguments since now handled by sowing

Also handles the passing of null objects correctly

show more ...

Merge remote-tracking branch 'origin/release'

Fix gcc-14 -Warray-bounds warnings for hypothetical negative sizes

These warnings arise because we use (signed int32) PetscInt for sizes
that must be nonnegative, then cast to size_t. This leads to

Fix gcc-14 -Warray-bounds warnings for hypothetical negative sizes

These warnings arise because we use (signed int32) PetscInt for sizes
that must be nonnegative, then cast to size_t. This leads to warnings
when the compiler doesn't know that the integers can't be negative.

In function ‘PetscMemzero’,
inlined from ‘TSARKIMEXRegister’ at /home/jed/petsc/src/ts/impls/arkimex/arkimex.c:1182:10:
/home/jed/petsc/include/petscstring.h:758:3: warning: ‘memset’ pointer overflow between offset 0 and size [-17179869184, -8] [-Warray-bounds=]
758 | memset(a, 0, n);
| ^~~~~~~~~~~~~~~

Compare commit 095c51fa7c16ea848964bdaab3c2c2b53b8a3072 from 2023:
Fix gcc-13 -Warray-bounds warnings involving hypothetical negative sizes

show more ...

Merge branch 'hsuh/lmvm-dense-recursive' into 'main'

Recursive implementation for MatMult_LMVMDBFGS and MatSolve_LMVMDDFP

See merge request petsc/petsc!7472

Added recursive formulation for MatMult_LMVMDBFGS, and MatSolve_LMVMDDFP