[petsc-users] Usage of PETSC_NULL_INTEGER for PCASMGetSubKSP via Fortran interface

Mark Adams mfadams at lbl.gov
Fri Dec 11 12:59:04 CST 2020

Integers in the C interface are now PETSC_DEFAULT_INTEGER in the Fortran
Types were not checked in 3.12. THis seems to have started in 3.13.

On Fri, Dec 11, 2020 at 9:50 AM WUKIE, NATHAN A DR-02 USAF AFMC AFRL/RQVC
via petsc-users <petsc-users at mcs.anl.gov> wrote:

> Hello,
> It looks like there has been some recent reorganization of Fortran
> interfaces. One item that has cropped up is that the interface for
> procedure PCASMGetSubKSP has been moved to a module via
> src/ksp/f90-mod/petscksp.h90.
> The question I have arrises when trying to pass PETSC_NULL_INTEGER, which
> seems to be an array, but the module interface to PCASMGetSubKSP now checks
> type rank consistency. PCASMGetSubKSP PetscInt arguments expect scalar
> values so just passing PETSC_NULL_INTEGER generates a compile-time error
> due to Scalar - Rank(1) mismatch.
> It seems one could pass PETSC_NULL_INTEGER(0) or PETSC_NULL_INTEGER(1),
> but I haven't found any documentation about how that's defined or if this
> is even the correct approach to resolve that issue. Could someone provide
> some insight or advise on the correct way forward?
> Thanks,
> Nathan
> petsc version: v3.14.2
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20201211/6b98ce61/attachment.html>

More information about the petsc-users mailing list