TS tests ex17: test TSResize for polynomial solutions

TS tutorials ex11: move to TSResize API

TS tests ex1: test TSResize

TSTHETA: support TSResize

TSALPHA: support TSResize

TSBDF: support TSResize

TSRK: support TSResize

TS: add infrastructure to support time-dependent problems with varying size

matrix free in docs and comments should be matrix-free

Lint apply: ts

Merge branch 'jacobf/2023-07-10/cleanup-unused-options' into 'main'

Cleanup Unused Options

See merge request petsc/petsc!6689

minor

Merge branch 'barry/2023-07-10/check-bad-source-picky' into 'main'

no extra blanks in test harness rules

See merge request petsc/petsc!6686

Remove uneeded blanks in test-harness rules since some reviewers fix them in GitLab

Remove -log_summary

Need to have test harness remove -options_left to tests that test handling of errors in tests

Commit-type: testing

TSBASICSYMPLECTIC: fix step computation

Allow generatefortranstubs.py to generate the stubs and module files in the PETSC_ARCH directory

Merge branch 'barry/2023-06-15/add-fortran-file-viewer' into 'main'

Allow one to attach a PETSCVIEWERASCII to a Fortran file unit

See merge request petsc/petsc!6607

HAVE_FORTRAN should be USE_FORTRAN_BINDINGS since it is about generating the Fortran bindings, not about if the Fortran compiler exists

Plex: Replace DMPlexGetGhostCellStratum() with DMPlexGetCellTypeStratum()
- Also fix DMPlexTransform version

Merge remote-tracking branch 'origin/release'

optimized launch bounds with AMD data, similar to old CUDA optimization

TSAdaptCheckStage: must call TSFunctionDomainError first

TS specific API must take precedence on internal solver handling.
For example, TSFunctionDomainError may indicate too large of a time step tr

TSAdaptCheckStage: must call TSFunctionDomainError first

TS specific API must take precedence on internal solver handling.
For example, TSFunctionDomainError may indicate too large of a time step triggered by a SNESSetFunctionDomainError.
inside a SNESMF solve.
In such a case, SNES error may be recoverable without the need of increasing the number of failures.

show more ...

Fix gcc-13 -Warray-bounds warnings involving hypothetical negative sizes

Static analysis should be able to prove that these are always
non-negative, but we can use PetscMax(s, 0) to avoid triggering

Fix gcc-13 -Warray-bounds warnings involving hypothetical negative sizes

Static analysis should be able to prove that these are always
non-negative, but we can use PetscMax(s, 0) to avoid triggering this
warning.

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 ...