Maybe you haven't been in on the conversation related to this? The issue is that MPI_Aint is the size for extents, even in I/I space, and so we need it to be 64 bit to be able to do useful file I/I (think subarray access from many processes). -- Rob On May 2, 2008, at 7:41 PM, Pavan Balaji <[email protected]> wrote:
The MPI_Aint vs void * is a hack to deal with a combination of limitations in the MPI spec and in the MPICH2 implementation. Specifically, the real issue is to make MPI_Aint the same as MPI_Offset, though that's not the way it looks in their patch. Some
I tried to look through my older email, but couldn't find this discussion. Isn't the right way to use MPI_Offset where needed instead of forcing MPI_Aint and MPI_Offset to be of the same size? The code assumes in many places that (void *) and MPI_Aint are of the same size. If we change this, many things might break.
We should probably decide on this first, as a major part of the patches is based on this change.
Thanks.
-- Pavan
-- Pavan Balaji http://www.mcs.anl.gov/~balaji