I think that we want to allow for this tradeoff, but make sure that in the case where sizeof(MPI_Aint) == sizeof(void *) != sizeof(MPI_Offset), everything still works. That's why I'd like to think carefully about what we call the datatype size type internally to MPICH2, and how we export it. Because of limitations in the MPI spec itself, we'll have to make some tradeoffs for systems with 32 bit pointers and 64 bit file offsets.
Bill
On May 5, 2008, at 9:01 AM, Pavan Balaji wrote:
In that case, more than 50% of the changes sent by IBM are invalid. So,
I'm back to my first question :-). Are these changes (in principle)
acceptable to be included in MPICH2? If not, we should tell them what to
do about this.
William Gropp
Paul and Cynthia Saylor Professor of Computer Science