Side effects due to updates to PETSc
7 views
Skip to first unread message
Hammond, Glenn E
Jul 18, 2024, 4:27:43 PM (9 days ago) Jul 18
to pflotran-dev (pflotran-dev@googlegroups.com)
All,
Recent updates to PETSc necessitate a fairly comprehensive refactor of PFLOTRAN. For example:
1. All PETSC_NULL_XXX objects are no longer derived types, but classes (extended derived types).
2. Argument for XXXSetValuesXXX that are arrays must now be arrays (strictly enforced) where as previously you could pass an integer since Fortran is pass by address. No longer possible.
3. And there is more....
Bottom line, we need to refactor many calls to PETSc before the next PETSc release (~Oct) but after the upcoming PFLOTARN release (~Aug).
Glenn
Recent updates to PETSc necessitate a fairly comprehensive refactor of PFLOTRAN. For example:
1. All PETSC_NULL_XXX objects are no longer derived types, but classes (extended derived types).
2. Argument for XXXSetValuesXXX that are arrays must now be arrays (strictly enforced) where as previously you could pass an integer since Fortran is pass by address. No longer possible.
3. And there is more....
Bottom line, we need to refactor many calls to PETSc before the next PETSc release (~Oct) but after the upcoming PFLOTARN release (~Aug).
Glenn
Reply all
Reply to author
Forward
0 new messages