| #
2235c4e2
|
| 23-Feb-2026 |
Satish Balay <balay@mcs.anl.gov> |
Merge branch 'dalcinl/bt-byte' into 'main'
Implement PetscBT with new PetscByte datatype as unsigned char
See merge request petsc/petsc!9046
|
| #
9d47de49
|
| 18-Feb-2026 |
Satish Balay <balay@mcs.anl.gov> |
Merge branch 'barry/2026-02-14/fix-defined-missing-braces' into 'main'
Fix the inconsistent usage of #if defined XXX compared to defined(XXX)
See merge request petsc/petsc!9040
|
| #
73bc78fd
|
| 17-Feb-2026 |
Lisandro Dalcin <dalcinl@gmail.com> |
Implement PetscBT with new PetscByte datatype as unsigned char
|
| #
beceaeb6
|
| 15-Feb-2026 |
Barry Smith <bsmith@mcs.anl.gov> |
Fix the inconsistent usage of #if [!]defined XXX compared to defined(XXX)
Thanks-to: Pierre Jolivet
An LLM Claude detected the incosnsitency it was not used to remove the inconsistency
|
| #
763f2bca
|
| 23-Jan-2026 |
Satish Balay <balay@mcs.anl.gov> |
Merge remote-tracking branch 'origin/release'
|
| #
7d4bf6f5
|
| 23-Jan-2026 |
Satish Balay <balay@mcs.anl.gov> |
Merge branch 'barry/2026-01-20/doc-ftn-callback-subtype' into 'release'
Document PetscFortranCallbackType
See merge request petsc/petsc!8968
|
| #
9e3fb531
|
| 21-Jan-2026 |
Barry Smith <bsmith@mcs.anl.gov> |
Document PetscFortranCallbackType
|
| #
6f3e8f24
|
| 26-Nov-2025 |
Satish Balay <balay@mcs.anl.gov> |
Merge branch 'MartinDiehl/detect-Intel-hidden-as-Cray' into 'main'
try to uncover Intel compilers pretending to be Cray
See merge request petsc/petsc!8835
|
| #
a0268130
|
| 08-Nov-2025 |
Martin Diehl <mail@martin-diehl.net> |
try to uncover Intel compilers pretending to be Cray
also documented how to get a Fortran logical that is compatible with C Bool for NVIDIA and Intel compilers
|
| #
fe7aa59f
|
| 22-Sep-2025 |
Satish Balay <balay@mcs.anl.gov> |
Merge branch 'barry/2025-08-31/fix-hypre-default-setting-reset-to-same' into 'main'
Fixes the bug with hypre whan user changes to parameters are ignored
See merge request petsc/petsc!8678
|
| #
8112c1cb
|
| 22-Sep-2025 |
Satish Balay <balay@mcs.anl.gov> |
Merge branch 'barry/2025-09-04/deprecate-mpiu-bool' into 'main'
Deprecate MPIU_BOOL which used to be for PETSc's enum Bool but now is just MPI_C_BOOL
See merge request petsc/petsc!8691
|
| #
4d81f786
|
| 01-Sep-2025 |
Barry Smith <bsmith@mcs.anl.gov> |
Add PetscOptionsBool3()
|
| #
5440e5dc
|
| 04-Sep-2025 |
Barry Smith <bsmith@mcs.anl.gov> |
Deprecate MPIU_BOOL which used to be for PETSc' enum Bool but now is just MPI_C_BOOL so no longer needs its own name
|
| #
51b144c6
|
| 29-Aug-2025 |
Satish Balay <balay@mcs.anl.gov> |
Merge branch 'MarDiehl/use-bool-instead-of-enum' into 'main'
use bool instead of enum
See merge request petsc/petsc!8528
|
| #
1dc74096
|
| 21-Jul-2025 |
Martin Diehl <mail@martin-diehl.net> |
use standard bool instead of enum
PetscBool is equivalent to _Bool/bool in C
For C standards prior to C23, true = 1 and false = 0 are defined in <stdbool.h>. For C23, true and false are real keywor
use standard bool instead of enum
PetscBool is equivalent to _Bool/bool in C
For C standards prior to C23, true = 1 and false = 0 are defined in <stdbool.h>. For C23, true and false are real keywords.
The Fortran equivalent is logical(C_BOOL) with C_BOOL from ISO_C_binding.
The C and the C++ standard do not specify the size of Booleans, but they typically have a size of 1 Byte with b00000000 for false and b00000001 for true. When using compilers from the same vendor, it is sane to assume that _Bool/bool in C and bool in C++ are fully compatible. But that is not guaranteed by the standards
show more ...
|
| #
09b68a49
|
| 04-Apr-2025 |
Satish Balay <balay@mcs.anl.gov> |
Merge remote-tracking branch 'origin/release'
|
| #
e80aff1c
|
| 03-Apr-2025 |
Satish Balay <balay@mcs.anl.gov> |
Merge branch 'jolivet/fix-petsc-case' into 'release'
Fix wrong case for PETSc
See merge request petsc/petsc!8266
|
| #
f0b74427
|
| 01-Apr-2025 |
Pierre Jolivet <pierre@joliv.et> |
Fix wrong case for PETSc
|
| #
b0dcfd16
|
| 23-Mar-2025 |
Satish Balay <balay@mcs.anl.gov> |
Merge branch 'barry/2025-03-20/minor-fortran-cleanup' into 'main'
Minor cleanup of Fortran binding stuff to simplify future maintainance
See merge request petsc/petsc!8218
|
| #
6dd63270
|
| 20-Mar-2025 |
Barry Smith <bsmith@mcs.anl.gov> |
Minor cleanup of Fortran binding stuff to simplify future maintainance
There 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 maintainance
There 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
show more ...
|
| #
6d8694c4
|
| 20-Mar-2025 |
Satish Balay <balay@mcs.anl.gov> |
Merge branch 'barry/2024-04-29/add-fortran-enums' into 'main'
Major updates to Fortran interface
See merge request petsc/petsc!7517
|
| #
ce78bad3
|
| 20-Feb-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 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 modules
Co-authored-by: Jose E. Roman <jroman@dsic.upv.es>
show more ...
|
| #
d34ab3a3
|
| 24-Feb-2025 |
Satish Balay <balay@mcs.anl.gov> |
Merge remote-tracking branch 'origin/release'
|
| #
32edcb65
|
| 22-Feb-2025 |
Satish Balay <balay@mcs.anl.gov> |
Merge branch 'jolivet/fix-docs' into 'release'
Fix typos
See merge request petsc/petsc!8155
|
| #
54c05997
|
| 21-Feb-2025 |
Pierre Jolivet <pierre@joliv.et> |
Fix typos
|