Re: [OMPI users] Initializing OMPI with invoking the array constructor on Fortran derived types causes the executable to crash

2013-01-14 Thread Iliev, Hristo
Hi, Gus, Automatic allocation (an reallocation) on assignment is among the nifty features of Fortran 2003. In this case "conc" is automatically allocated so to match the shape of its initialiser array "[ xx, yy ]". Note that "xx" and "yy" are not allocatable though their derived type has an alloca

Re: [OMPI users] Initializing OMPI with invoking the array constructor on Fortran derived types causes the executable to crash

2013-01-14 Thread Stefan Mauerberger
Well, I missed to emphasize one thing: It is my intension to exploit F2003's lhs-(re)allocate feature. Meaning, it is totally legal in F03 to write something like that: integer, allocatable :: array(:) array = [ 1,2,3,4 ] array = [ 1 ] where 'array' gets automatically (re)allocated. One more thing

Re: [OMPI users] Initializing OMPI with invoking the array constructor on Fortran derived types causes the executable to crash

2013-01-14 Thread Iliev, Hristo
Some MPI libraries (including OMPI and IMPI) hook the system memory management routines like 'malloc' and 'free' (used behind the scenes by Fortran on Unix). This is usually performed in order to manage memory registration for RDMA-based networks like InfiniBand. I would guess that Open MPI install

[OMPI users] Windows MPI with Fortran calling programs

2013-01-14 Thread Said Elnoshokaty
Dear Sirs, Parallel processing is needed to speed up processing of large-scale master and sub-problems. 32-bit Microsoft Access 2007 is used to capture data and then calls a DLL program written in 32-bit Microsoft Fortran 90 for processing (to be distributed in parallel among master and sub-prob

Re: [OMPI users] Initializing OMPI with invoking the array constructor on Fortran derived types causes the executable to crash

2013-01-14 Thread Stefan Mauerberger
On Mon, 2013-01-14 at 12:00 -0500, users-requ...@open-mpi.org wrote: > Could you try to run your serial program in Valgrind and see if it > reports any erroneous memory access attempts? It could be that GCC's > implementation of the automatic allocation is broken and that OMPI's > intervention in t