Ok, how about removing the reference to MPI_FILE_SET_VIEW, then? I'd like to return MPI_ERR_UNSUPPORTED_DATAREP as the error class in MPI_PACK_* functions for that case, and the current text kind of prohibits that. We can then rationalize the location of error classes in MPI-4. -Fab Rajeev Thakur wrote on Thu, 13 Mar 2014 at 12:52:44
The table on pg 551 is about I/O error codes and classes. So Pack_external/Unpack_external (from 9 chapters away) would look out of place there. The real solution might be to move the I/O error codes and classes from the I/O chapter to the chapter on error codes and classes, but that would be more than a ticket 0 change.
Rajeev
On Mar 13, 2014, at 12:02 PM, Fab Tillier <[email protected]> wrote:
Hi folks,
The standard defines MPI_ERR_UNSUPPORTED_DATAREP as an I/O error class, with the meaning "Unsupported datarep passed to MPI_FILE_SET_VIEW". However, datareps are also passed as input to MPI_PACK_EXTERNAL and MPI_UNPACK_EXTERNAL. Shouldn't these functions use the same error class for unsupported datareps, rather than MPI_ERR_ARG?
Can we update the description of MPI_ERR_UNSUPPORTED_DATAREP (page 551, line 10) to also include MPI_PACK_EXTERNAL and MPI_UNPACK_EXTERNAL as a ticket-0 item for MPI 3.1, or will this need to happen in a later version?
Thanks, -Fab _______________________________________________ mpi-forum mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum
_______________________________________________ mpi-forum mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum