Please also put IMPICIT NONE to your SUBROUTINE and replace INCLUDE
'mpif.h' by USE mpi. This comes with the benefit of interface checking.
The compiler will throw an error due to missing tags.
It is even better style to write:
PROGRAM main
USE MPI
...
CONTAINS
SUBROUTINE ...
...
Hi Everyone!
Playing around with MPI_FILE_READ() puzzles me a little. To catch all
errors I set the error-handler - the one which is related to file I/O -
to MPI_ERRORS_ARE_FATAL.
However, when reading from a file which has not the necessary size
MPI_FILE_READ(...) returns 'MPI_SUCCESS: no
Dear all!
using the split collective procedures MPI_File_write_all_begin() and
MPI_File_write_all_end() causes some confusion to me.
It was my intention to implement asynchronous file i/o using those
procedures. The idea is to calculate some 'useful' stuff while writing
tons of data to disk.
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
ooo"
> comment aut 'USE mpi' an see your error (SIGSEGV) again, now without any
> MPI part in the program.
> So my suspiction is this is an bug in your GCC version. Especially because
> there
> is no SIGSEGV using 4.7.2 GCC (whereby it crasehs using 4.4.6)
>
> ==>
Hi There!
First of all, this is my first post here. In case I am doing something
inappropriate pleas be soft with me. On top of that I am not quite sure
whether that issue is related to Open MPI or GCC.
Regarding my problem: Well, it is a little bulky, see below. I could
figure out that the
