Mismatch in explicit fortran interface for MatGetInfo

Barry Smith bsmith at mcs.anl.gov
Sat May 23 18:59:30 CDT 2009


     Thanks for reporting the problem. Our tool generates either both  
the Fortran stub and Fortran interface definition or neither. For this  
function it generates the stub correctly but the wrong interface.  The  
"quick" fix is to turn off the auto generation for this function and  
provide both manually. I'll see about making a patch. Unless someone  
has a better solution.


On May 23, 2009, at 9:00 AM, Stephan Kramer wrote:

> Hi all,
> First of all thanks of a lot for providing explicit fortran  
> interfaces for most functions in Petsc 3. This is of great help. I  
> do however run into a problem using MatGetInfo. The calling sequence  
> for fortran (according to the manual) is:
> double precision info(MAT_INFO_SIZE)
> Mat <cid:part1.02040105.02020103 at imperial.ac.uk> A
> integer ierr
> call MatGetInfo  
> <cid:part2.00070305.02060306 at imperial.ac.uk>(A,MAT_LOCAL,info,ierr)
> The interface however seems to indicate the info argument has to be  
> a single double precision (i.e. a scalar not an array). I guess with  
> implicit interfaces this sort of thing would work, but with the  
> provided explicit interface, at least gfortran won't let me have it.
> Cheers
> Stephan

More information about the petsc-users mailing list