So what are the alignment rules. If there are alignment rules, what is the
FILE_EXTENT of MPI_BYTE and the FILE_EXTENT of 4*MPI_BYTE?
What about the optional types? Are there going to be some required
representations? If not, is this useful?
Are MPI_DATA_MIPS32 and MPI_DATA_MIPS64 attibutes, constants for use with
open, both? Currently open uses the or-ing of bit fields (get your
representations in early :-).
Regards,
Leslie
>
> To get the ball rolling:
>
> MPI_DATA_MIPS32 MPI_DATA_MIPS64
> --------------- ---------------
> MPI_CHAR 1 1
> MPI_SHORT 2 2
> MPI_INT 4 4
> MPI_LONG 4 8
> MPI_LONG_LONG 8 8
> MPI_FLOAT 4 4
> MPI_DOUBLE 8 8
> MPI_LONG_DOUBLE 16 16
>
> MPI_INTEGER 4 4
> MPI_REAL 4 4
> MPI_DOUBLE_PRECISION 8 8
>
> endian-ness Big Big
> character format ASCII ASCII
> floating-point format IEEE IEEE
>
> Have I missed something? I suppose we probably need to address nasty issues
> like denorms and NaNs, but at least this is a start. Anyone else care to jump
> in?
>
> --
> Eric Salo Silicon Graphics Inc. salo@sgi.com
>