Eric,
A quick grep in Open MPI source indicates that the only 2 places where
MPI_ERR_UNSUPPORTED_DATAREP is issue are deep inside the imported ROMIO code
(3.14):
./ompi/mca/io/romio314/romio/adio/include/adioi_errmsg.h:70:MPI_ERR_UNSUPPORTED_DATAREP
./ompi/mca/io/romio314/romio/adio/include/mpio_error.h:74:/*
MPI_ERR_UNSUPPORTED_DATAREP */
./ompi/mca/io/romio314/romio/mpi-io/set_view.c:138:
MPI_ERR_UNSUPPORTED_DATAREP,
The culprit seems to be the set_view.c code, where MPI_ERR_UNSUPPORTED_DATAREP
is generated for any data rep that is not extenal32. This also explains why you
get a similar issue with MPICH, we both share the same ROMIO code (maybe few
minor versions apart).
You just hit one of these obscure MPI features that few ever use (and you’re
one of them!). The quickest option I can see for you at this point is either to
fallback on the “external32” format when you generate the file (on the 64 bits
architecture) to get an architecture-agnostic output, or to rely on saving
External Data Representation (XDR) yourself.
George.
> On Mar 12, 2016, at 22:26 , Éric Chamberland
> <eric.chamberl...@giref.ulaval.ca> wrote:
>
> ERROR Returned by MPI: 51
> ERROR_string Returned by MPI: MPI_ERR_UNSUPPORTED_DATAREP: data
> representation not supported
>
> which is pretty similar to MPICH output...
>
> So I am completely stuck into implementing a solution to read/write "native"
> 64 bits datarep files from a 32 bits architecture...
>
> Isn't that into the MPI-2 standard? Does it means that no MPI implementation
> is standard compliant? >:)
