[MPIWG Fortran] Type of MPI_Status

Junchao Zhang jczhang at mcs.anl.gov
Mon Mar 17 13:39:23 CDT 2014


On Mon, Mar 17, 2014 at 11:52 AM, Craig Rasmussen <rasmus at cas.uoregon.edu>wrote:

> Jeff and I had a similar conversation last week.  It is my viewpoint that
> the MPI-3 interfaces are formal interfaces that can be adapted by an
> implementation in a way that formally meets the specification.
>

+1 for this view.


> For Open MPI I believe that Jeff will add configuration magic to check is
> INTEGER(C_INT) and default INTEGER have the same KIND value.  This should
> be true for 100% of the compilers.  If not, then that compiler will not be
> able to build Open MPI.
>

Supporting different INTEGER and c_int 1) is useless;  2) adds code
complexity; 3) adds extra runtime overhead (in MPICH implementation) even
when INTEGER and c_int are the same.  I prefer stopping the support and
doing configuration time check.


>
> The use of INTEGER(C_INT) to replace the default INTEGER in the MPI types
> is needed to stopped compiler warning from GNU.  We did this work (adding
> BIND(C) to gfortran) at Los Alamos and I think we perhaps got carried away
> with the warning messages.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mpi-forum.org/pipermail/mpiwg-fortran/attachments/20140317/dac92c3d/attachment-0001.html>


More information about the mpiwg-fortran mailing list