[Mpi-22] Call for MPI 2.2 agenda items

[Supalov, Alexander]

Hi,

May be we add a couple of calls to pass data back and forth between the
client and MPI? Either assertions proposed by Dick Treumann, or more
extensible (MPI_Info based?) approach proposed by Jeff Squyres? That's
admittedly connected to subsets, but this is only an addition, no
backward incompatible change. MPI 2.2?

Best regards.

Alexander 

-----Original Message-----
From: mpi-22-bounces_at_[hidden]
[mailto:mpi-22-bounces_at_[hidden]] On Behalf Of Rajeev Thakur
Sent: Monday, May 05, 2008 10:36 PM
To: mpi-forum_at_[hidden]; mpi-22_at_[hidden]
Subject: [Mpi-22] Call for MPI 2.2 agenda items

Now that MPI 2.1 is close to completion, it is time to look at issues
for
MPI 2.2. Please send any items you may have for 2.2 to
mpi-22_at_[hidden] and/or upload them to the wiki (and let us
know).
I had made a note of the following items from the last meeting that were
deferred to 2.2:

* support for long long in maxloc, minloc

* fix meaning of first two sentences in intercommunicator barrier

* Ex 5.8 uses old style MPI_UB

* Many functions say "integer" instead of "nonnegative integer"

* const in C++ bindings 

* IN, OUT, and INOUT handle types broken 

* MPI_CHAR, MPI::CHAR should be signed char or char?

* Need 64-bit sizes for count in messages

* Sizes of MPI_Aint and MPI_Offset should not be different

* New predefined types MPI_AINT and MPI_OFFSET

* New predefined types corresponding to new types in C99, Fortran 2003,
and
C++ some year

_______________________________________________
mpi-22 mailing list
mpi-22_at_[hidden]
http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-22
---------------------------------------------------------------------
Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen Germany
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer
Registergericht: Muenchen HRB 47456 Ust.-IdNr.
VAT Registration No.: DE129385895
Citibank Frankfurt (BLZ 502 109 00) 600119052

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.