Hi George, I know MPI_Get_elements_x (). But Page 483 claims: These functions modify the opaque part of status so that a call to MPI_GET_ELEMENTS or MPI_GET_ELEMENTS_X will return count. MPI_GET_COUNT will return a compatible value. This will not work for large MPI_Count values provided by MPI_SET_ELEMENTS_X (i.e. MPI_UNDEFINED is returned by MPI_Get_count() in significant use of MPI_SET_ELEMENT_X). And Page 114 says that function MPI_Get_count has a different behavior than MPI_GET_ELEMENTS/MPI_GET_ELEMENTS_X. Thus, MPI_GET_COUNT is not obsolete and application has to develop a separate version of MPI_Get_count_x() if MPI_SET_ELEMENT_X might be used in the application or a library. Hubert ________________________________ From: [email protected] [[email protected]] on behalf of George Bosilca [[email protected]] Sent: Friday, August 31, 2012 2:26 PM To: Comments on the MPI Standard Subject: Re: [Mpi-comments] MPI_Get_count_x MPI_Get_elements_x, chap Datatypes page 114 (current make cleandoc). george. On Aug 31, 2012, at 13:45 , Hubert Ritzdorf <[email protected]<mailto:[email protected]>> wrote: Hi, I think, that function MPI_Get_count_x (const MPI_Status *status, MPI_Datatype datatype, MPI_Count *count) is missing. After use of function MPI_Status_set_elements_x, MPI_Get_count is possibly not able to return a compatible value. This is contradictory to Page 483, Lines 22-33. Hubert _______________________________________________ mpi-comments mailing list [email protected]<mailto:[email protected]> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-comments Click here<https://www.mailcontrol.com/sr/lGzi4c6egezTndxI!oX7UkkR2vxuiI13vs0Z85bSifOXOzDXd8zo8Mu3jtzAbPvtZhAszQEBXlpmYIqzE2R4VA==> to report this email as spam.