On Mon, Nov 23, 2009 at 10:26 AM, Riccardo Corradini <
riccardocorrad...@yahoo.it> wrote:
> Dear Michael,
> I have posted MPI_Iprobe.cc and MPI_Probe.cc with info as last flag.
> Please let me know if it helps in building other examples.
> For the comunicator issue I am thinking on passing a simple string as
> alternative comunicator and if nothing is provided by the user then
> MPI_COMM_WORLD is the default value.
> Thanks and bests
> Riccardo
>
>
Hi Riccardo and Michael,
I have already implemented basic support for the communicators in the SVN
tree.
The relevant functions now accept comm as their last argument, defaulting to
MPI_COMM_WORLD if not provided.
MPI_COMM_WORLD is a new function.
Note 1: The implementation imposes the requirement that MPI_Comm is a
typedef for signed 32-bit or 64-bit integer (int, long, or long long) which
is true in all major MPI implementations with the notable exception of
OpenMPI. OpenMPI uses raw pointers, which make things a bit difficult. One
option is to simply typecast the pointers to integers; but I feel a bit
uneasy about working with raw pointers in Octave, so I'm thinking about a
solution providing some validation as well.
I would, however, like to avoid creating a user type for each of MPI's
types.
Note 2:
There are no functions for creating new communicators yet.
--
RNDr. Jaroslav Hajek
computing expert & GNU Octave developer
Aeronautical Research and Test Institute (VZLU)
Prague, Czech Republic
url: www.highegg.matfyz.cz
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Octave-dev mailing list
Octave-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/octave-dev
