Re: [petsc-users] memory scalable AO

Thanks! pushed to maint - and merged to master. Satish On Thu, 18 Feb 2016, Randall Mackie wrote: > Hi Satish, > > This patch works now. > > Thanks very much to all of you for your patience and help. > > Randy > > > > On Feb 17, 2016, at 9:58 PM, Satish Balay wrote: > >

Re: [petsc-users] memory scalable AO

Hi Satish, This patch works now. Thanks very much to all of you for your patience and help. Randy > On Feb 17, 2016, at 9:58 PM, Satish Balay wrote: > > Look like zdaindexf.c is not listed in makefile - so it never gets compiled. > > Also it has code for

Re: [petsc-users] memory scalable AO

Look like zdaindexf.c is not listed in makefile - so it never gets compiled. Also it has code for dmdagetglobalindices_() dmdarestoreglobalindices_(). But then src/docs/website/documentation/changes/35.html has: DMDAGetGlobalIndices(DM,PetscInt*,const PetscInt*[]) and

Re: [petsc-users] memory scalable AO

Randy, It is not suppose to be this hard! When you ran the make gnumake after you applied the patch did it recompile the file zdaindexf.c (in fact that file and daindexf.c should be the only files that changed and hence the only files that got recompiled). Barry > On Feb 17,

Re: [petsc-users] memory scalable AO

Satish, It is unclear from this email exchange if I am still suppose to do make allfortranstubs after updating these two files, or if these are the files that are suppose to result from that make operation. Although these files looked the same as what I tried before with Barry’s suggestions,

Re: [petsc-users] memory scalable AO

Attached are the modified src/dm/impls/da/ftn-auto/daindexf.c and src/dm/impls/da/ftn-custom/zdaindexf.c files. Satish On Wed, 17 Feb 2016, Jed Brown wrote: > Randall Mackie writes: > > > this leads to the error ‘bin/maint/generatefortranstubs.py’ …No such file. > > > >

Re: [petsc-users] memory scalable AO

Randall Mackie writes: > this leads to the error ‘bin/maint/generatefortranstubs.py’ …No such file. > > there is no maint directory under bin. Ah, I missed that you have a tarball, not a clone of the repository. Then you'll have to fix the file manually. I would start

Re: [petsc-users] memory scalable AO

this leads to the error ‘bin/maint/generatefortranstubs.py’ …No such file. there is no maint directory under bin. Randy > On Feb 17, 2016, at 7:05 PM, Jed Brown wrote: > > Randall Mackie writes: >> So it seems to be ignoring the dmdasetaotype_ in

Re: [petsc-users] memory scalable AO

Randall Mackie writes: > So it seems to be ignoring the dmdasetaotype_ in > /src/dm/impls/da/ftn-custom/zdaindexf.c in favor of ../ftn-auto/daindexf.c Sounds like you need to generate your Fortran stubs so that the version in ftn-auto/daindexf.c is fixed. make

Re: [petsc-users] memory scalable AO

> On Feb 17, 2016, at 8:58 PM, Randall Mackie wrote: > > If I remove lines 47-50 in daindexf.c (the PETSC_EXTERN …for dmdasetaotype_), > then when I try to compile the test code, it complains of an undefined > reference to dmdasetaotype_. > > So I put the lines back

Re: [petsc-users] memory scalable AO

If I remove lines 47-50 in daindexf.c (the PETSC_EXTERN …for dmdasetaotype_), then when I try to compile the test code, it complains of an undefined reference to dmdasetaotype_. So I put the lines back in, and with your patch applied, and then run in the debugger, with a breakpoint at

Re: [petsc-users] memory scalable AO

It is probably my fault. Edit src/dm/impls/da/ftn-auto/daindexf.c and remove the function function from that file and then run make on the library again. If that does not work then run in the debugger and put a break point in dmdasetaotype_ once it is there in the debugger you can make sure

Re: [petsc-users] memory scalable AO

Here is patch. fix-fortran-dmdasetaotype.patch Description: Binary data If it works for you I'll put it in maint and master tomorrow. Barry > On Feb 17, 2016, at 3:46 PM, Randall Mackie wrote: > > The attached test program demonstrates the problem. When I run

Re: [petsc-users] memory scalable AO

Ahh, yes. This is our fault. Because this function takes a string it needs a custom Fortran stub which it does not have. We'll get you a patch soon. Barry > On Feb 17, 2016, at 3:46 PM, Randall Mackie wrote: > > The attached test program demonstrates the problem.

Re: [petsc-users] memory scalable AO

The attached test program demonstrates the problem. When I run it, I get the following output: [0]PETSC ERROR: [0]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range