| /petsc/doc/manualpages/MANSECHeaders/ |
| H A D | Matlab | ce78bad369055609e946c9d2c25ea67a45873e27 Thu Feb 20 06:12:11 UTC 2025 Barry Smith <bsmith@petsc.dev> 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 modules
Co-authored-by: Jose E. Roman <jroman@dsic.upv.es>
|
| H A D | DMComposite | ce78bad369055609e946c9d2c25ea67a45873e27 Thu Feb 20 06:12:11 UTC 2025 Barry Smith <bsmith@petsc.dev> 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 modules
Co-authored-by: Jose E. Roman <jroman@dsic.upv.es>
|
| H A D | Bag | ce78bad369055609e946c9d2c25ea67a45873e27 Thu Feb 20 06:12:11 UTC 2025 Barry Smith <bsmith@petsc.dev> 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 modules
Co-authored-by: Jose E. Roman <jroman@dsic.upv.es>
|
| H A D | Device | ce78bad369055609e946c9d2c25ea67a45873e27 Thu Feb 20 06:12:11 UTC 2025 Barry Smith <bsmith@petsc.dev> 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 modules
Co-authored-by: Jose E. Roman <jroman@dsic.upv.es>
|
| H A D | Log | ce78bad369055609e946c9d2c25ea67a45873e27 Thu Feb 20 06:12:11 UTC 2025 Barry Smith <bsmith@petsc.dev> 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 modules
Co-authored-by: Jose E. Roman <jroman@dsic.upv.es>
|
| H A D | BM | ce78bad369055609e946c9d2c25ea67a45873e27 Thu Feb 20 06:12:11 UTC 2025 Barry Smith <bsmith@petsc.dev> 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 modules
Co-authored-by: Jose E. Roman <jroman@dsic.upv.es>
|
| /petsc/src/sys/classes/viewer/impls/draw/draw/ |
| H A D | makefile | ce78bad369055609e946c9d2c25ea67a45873e27 Thu Feb 20 06:12:11 UTC 2025 Barry Smith <bsmith@petsc.dev> 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 modules
Co-authored-by: Jose E. Roman <jroman@dsic.upv.es>
|
| H A D | fdrawv.c | ce78bad369055609e946c9d2c25ea67a45873e27 Thu Feb 20 06:12:11 UTC 2025 Barry Smith <bsmith@petsc.dev> 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 modules
Co-authored-by: Jose E. Roman <jroman@dsic.upv.es>
|
| /petsc/src/dm/impls/plex/tutorials/output/ |
| H A D | ex14f90_1.out | ce78bad369055609e946c9d2c25ea67a45873e27 Thu Feb 20 06:12:11 UTC 2025 Barry Smith <bsmith@petsc.dev> 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 modules
Co-authored-by: Jose E. Roman <jroman@dsic.upv.es>
|
| H A D | ex4f90_1.out | ce78bad369055609e946c9d2c25ea67a45873e27 Thu Feb 20 06:12:11 UTC 2025 Barry Smith <bsmith@petsc.dev> 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 modules
Co-authored-by: Jose E. Roman <jroman@dsic.upv.es>
|
| /petsc/include/ |
| H A D | petscdmlabeltypes.h | ce78bad369055609e946c9d2c25ea67a45873e27 Thu Feb 20 06:12:11 UTC 2025 Barry Smith <bsmith@petsc.dev> 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 modules
Co-authored-by: Jose E. Roman <jroman@dsic.upv.es>
|
| H A D | petscbm.h | ce78bad369055609e946c9d2c25ea67a45873e27 Thu Feb 20 06:12:11 UTC 2025 Barry Smith <bsmith@petsc.dev> 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 modules
Co-authored-by: Jose E. Roman <jroman@dsic.upv.es>
|
| /petsc/src/snes/utils/libceed/ |
| H A D | makefile | ce78bad369055609e946c9d2c25ea67a45873e27 Thu Feb 20 06:12:11 UTC 2025 Barry Smith <bsmith@petsc.dev> 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 modules
Co-authored-by: Jose E. Roman <jroman@dsic.upv.es>
|
| H A D | dmplexsnesceed.c | ce78bad369055609e946c9d2c25ea67a45873e27 Thu Feb 20 06:12:11 UTC 2025 Barry Smith <bsmith@petsc.dev> 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 modules
Co-authored-by: Jose E. Roman <jroman@dsic.upv.es>
|
| /petsc/src/sys/utils/openmp/ |
| H A D | makefile | ce78bad369055609e946c9d2c25ea67a45873e27 Thu Feb 20 06:12:11 UTC 2025 Barry Smith <bsmith@petsc.dev> 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 modules
Co-authored-by: Jose E. Roman <jroman@dsic.upv.es>
|
| H A D | mpmpishm.c | ce78bad369055609e946c9d2c25ea67a45873e27 Thu Feb 20 06:12:11 UTC 2025 Barry Smith <bsmith@petsc.dev> 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 modules
Co-authored-by: Jose E. Roman <jroman@dsic.upv.es>
|
| /petsc/src/ts/utils/libceed/ |
| H A D | makefile | ce78bad369055609e946c9d2c25ea67a45873e27 Thu Feb 20 06:12:11 UTC 2025 Barry Smith <bsmith@petsc.dev> 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 modules
Co-authored-by: Jose E. Roman <jroman@dsic.upv.es>
|
| H A D | dmplextsceed.c | ce78bad369055609e946c9d2c25ea67a45873e27 Thu Feb 20 06:12:11 UTC 2025 Barry Smith <bsmith@petsc.dev> 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 modules
Co-authored-by: Jose E. Roman <jroman@dsic.upv.es>
|
| /petsc/include/petsc/private/ |
| H A D | bmimpl.h | ce78bad369055609e946c9d2c25ea67a45873e27 Thu Feb 20 06:12:11 UTC 2025 Barry Smith <bsmith@petsc.dev> 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 modules
Co-authored-by: Jose E. Roman <jroman@dsic.upv.es>
|
| /petsc/src/mat/graphops/coarsen/interface/ |
| H A D | makefile | ce78bad369055609e946c9d2c25ea67a45873e27 Thu Feb 20 06:12:11 UTC 2025 Barry Smith <bsmith@petsc.dev> 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 modules
Co-authored-by: Jose E. Roman <jroman@dsic.upv.es>
|
| /petsc/include/petsc/finclude/ |
| H A D | petscvecbase.h | ce78bad369055609e946c9d2c25ea67a45873e27 Thu Feb 20 06:12:11 UTC 2025 Barry Smith <bsmith@petsc.dev> 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 modules
Co-authored-by: Jose E. Roman <jroman@dsic.upv.es>
|
| H A D | petscisbase.h | ce78bad369055609e946c9d2c25ea67a45873e27 Thu Feb 20 06:12:11 UTC 2025 Barry Smith <bsmith@petsc.dev> 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 modules
Co-authored-by: Jose E. Roman <jroman@dsic.upv.es>
|
| /petsc/src/dm/impls/plex/tests/output/ |
| H A D | ex16_0_vtk.out | ce78bad369055609e946c9d2c25ea67a45873e27 Thu Feb 20 06:12:11 UTC 2025 Barry Smith <bsmith@petsc.dev> 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 modules
Co-authored-by: Jose E. Roman <jroman@dsic.upv.es>
|
| /petsc/lib/petsc/bin/maint/ |
| H A D | prettyprintAPI.py | ce78bad369055609e946c9d2c25ea67a45873e27 Thu Feb 20 06:12:11 UTC 2025 Barry Smith <bsmith@petsc.dev> 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 modules
Co-authored-by: Jose E. Roman <jroman@dsic.upv.es>
|
| /petsc/src/vec/vec/tests/ |
| H A D | ex32.c | ce78bad369055609e946c9d2c25ea67a45873e27 Thu Feb 20 06:12:11 UTC 2025 Barry Smith <bsmith@petsc.dev> 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 modules
Co-authored-by: Jose E. Roman <jroman@dsic.upv.es>
|