Mismatch in explicit fortran interface for MatGetInfo

Barry Smith bsmith at mcs.anl.gov
Thu Jun 18 11:39:12 CDT 2009


     Those are ones for which our automatic tools do not work for  
(mostly because they have character strings in the arguments and our  
tools cannot handle the translation from Fortran to C automatically).   
So we are in the position of
1) having better tools that can handle these cases or
2) making the interfaces manually.
Neither path is desirable to us :-(


On Jun 18, 2009, at 7:22 AM, Stephan Kramer wrote:

> Hi Satish,
> I tried with p6 and it indeed works fine now. Thanks a lot for  
> looking into this. A related question: it seems still quite a lot of  
> very common interfaces (PETScInitialize, KSPSettype, MatView, etc.)  
> are missing. Are there any plans of adding those in the future?
> Cheers
> Stephan
> Satish Balay wrote:
>> On Sat, 30 May 2009, Stephan Kramer wrote:
>>> Satish Balay wrote:
>>>> On Sat, 30 May 2009, Stephan Kramer wrote:
>>>>> Thanks a lot for looking into this. The explicit fortran  
>>>>> interfaces are in
>>>>> general very useful. The problem occurred for me with  
>>>>> petsc-3.0.0-p1. I'm
>>>>> happy to try it out with a more recent patch-level or with petsc- 
>>>>> dev.
>>>> Did you configure with '--with-fortran-interfaces=1' or are you
>>>> directly using '#include "finclude/ftn-auto/petscmat.h90"'?
>>> Configured with '--with-fortran-interfaces=1', yes, and then using  
>>> them via
>>> the fortran modules: "use petscksp", "use petscmat", etc.
>> ok. --with-fortran-interfaces was broken in p0, worked in p1,p2,p3,p4
>> - broken in curent p5. The next patch update - p6 will have the fix
>> for this issue [along with the fix for MatGetInfo() interface]
>> Satish

More information about the petsc-users mailing list