[MPI3 Fortran] MPI function symbol naming convention for tools

Jeff Squyres jsquyres at cisco.com
Fri Jun 24 11:46:10 CDT 2011

On Jun 24, 2011, at 12:20 PM, Hubert Ritzdorf wrote:

> There are (compiled) libraries and object files containing the corresponding external references to MPI_SEND, mpi_send__, mpi_send_ or mpi_send. Therefore, you cannot simply change the interface of the MPI_Send routine without breaking these libraries. You can also not simply expect that they will be recompiled.

I think it is reasonable to ask applications / libraries / etc. to recompile with MPI-3.  This has been the position of the Forum.

> In addition, the mpif.h include file doesn't have an interface block (and will still generate the external references above)

It's actually not specified, right?  Meaning that an implementation *could* use an interface block if they wanted to.

> and Fortran 90 module doesn't have an optional error argument in the interface block even if you expect that the Fortran 90 module/compiler supports some NO_ARG_CHECK attribute.

We didn't add optional arguments to any of the existing MPI Fortran interfaces -- optional arguments are only (possibly) being added in the new F08 bindings.

Jeff Squyres
jsquyres at cisco.com
For corporate legal information go to:

More information about the mpiwg-fortran mailing list