Originally by RolfRabenseifner on 2010-09-01 11:01:23 -0500

247-S: All new Fortran 2008 bindings - Part 1See Ticket #229-A for an overview on the New MPI-3 Fortran Support.

Description

-Major decisions in this ticket:*

Detailed decision about all new Fortran 2008 interfaces in mpi_f08.

-Details:*

This ticket provides the rule for converting existing Fortran interfaces into new Fortran 2008 interfaces.

Extended Scope

None.

History

Proposed Solution

-MPI-2.2, Section 5.9.5 User-Defined Reduction Operations, page 172, lines 9-12 read*

The Fortran declaration of the user-defined function appears below.

  SUBROUTINE USER_FUNCTION(INVEC, INOUTVEC, LEN, TYPE)
    <type> INVEC(LEN), INOUTVEC(LEN)
    INTEGER LEN, TYPE

-but should read*

When using mpif.h or the mpi module, the ~~The~~ Fortran declaration of the user-defined function is:

  SUBROUTINE USER_FUNCTION(INVEC, INOUTVEC, LEN, TYPE)
    <type> INVEC(LEN), INOUTVEC(LEN)
    INTEGER LEN, TYPE

__When using the mpi_f08 module, the declaration is:

  SUBROUTINE user_function(invec, inoutvec, len, type)
    TYPE(*) :: invec(len), inoutvec(len)
    INTEGER :: len
    TYPE(MPI_Datatype) :: type

-CAUTION:* If Ticket #234-F does not pass, then the new TYPE(*) line above must be substituted by [[BR]]<type> invec(len), inoutvec(len)

-CAUTION:* If Ticket #231-C does not pass, then the new INTEGER and the new TYPE(MPI_Datatype) line above must be substituted by [[BR]]INTEGER :: len, type

-MPI-2.2, Section 5.9.5 User-Defined Reduction Operations, page 173, lines 8-13 read*

-but should read*

The Fortran version of MPI_REDUCE will invoke a user-defined reduce function using the Fortran calling conventions and will pass a Fortran-type datatype argument; the C version will use C calling convention and the C representation of a datatype handle. If a Fortran user-defined reduce function is used, then the calling sequence further depends on whether MPI_OP_CREATE was invoked via the mpif.h or USE mpi interface, or the USE mpi_f08 interface. Users who plan to mix languages should define their reduction functions accordingly. [[BR]](End of advice to users.)

-MPI-2.2, Section 6.7 Caching*

-TODO*: Declaration of MPI_COMM_CREATE_KEYVAL, COMM_COPY_ATTR_FN, COMM_DELETE_ATTR_FN, MPI_WIN_CREATE_KEYVAL, WIN_COPY_ATTR_FN, WIN_DELETE_ATTR_FN, MPI_TYPE_CREATE_KEYVAL, TYPE_COPY_ATTR_FN, TYPE_DELETE_ATTR_FN

-MPI-2.2, Section 8.3 Error Handling*

-TODO*: Declaration of MPI_XXX_CREATE_ERRHANDLER with XXX = COMM, WIN, or FILE, and XXX_ERRHANDLER_FUNCTION

-MPI-2.2, Section 12.2 Generalized Requests*

-TODO*: Declaration of MPI_GREQUEST_START, GREQUEST_QUERY_FUNCTION, GREQUEST_FREE_FUNCTION, GREQUEST_CANCEL_FUNCTION,

-MPI-2.2, Appendix A.1.3 Prototype definitions, page 525-528*

-TODO*: Must be done also by hand

'''MPI-2.2, Appendix A.3, Fortran Bindings, page 547, line 1 reads (in AppLang-Fortran.tex)'''

A.3 Fortran Bindings

-but should read*

A.3 Fortran Bindings with mpif.h or the mpi Module

'''After MPI-2.2, Appendix A.3, Fortran Bindings, i.e., after page 570, add new Section (in new AppLang-Fortran2008.tex, which must be included by mpi-report.tex, and which includes AppLang-F2008Names.tex, which is produced by MAKE-APPLANG)'''

A.4 Fortran 2008 Bindings with the mpi_f08 Module

-It contains same as MPI-2.2, A.3, but*

Provided that Ticket #234-F (strong buffer typing) has passed:
- <type> xxx(*)}}, yyy(*)} --> {{{TYPE(*), DIMENSION(..) :: xxx, yyy
- <type> xxx(*) --> TYPE(*), DIMENSION(..) :: xxx
- <type> X --> TYPE(*) :: x
Provided that Ticket #231-C (strong handle typing) has passed:
- INTEGER FILE --> TYPE(MPI_File) :: file
- INTEGER FH --> TYPE(MPI_File) :: fh
- INTEGER DATATYPE --> TYPE(MPI_Datatype) :: datatype
- INTEGER SENDTYPE --> TYPE(MPI_Datatype) :: sendtype
- INTEGER RECVTYPE --> TYPE(MPI_Datatype) :: recvtype
- INTEGER SENDTYPES(*) --> TYPE(MPI_Datatype) :: sendtypes(*)
- INTEGER RECVTYPES(*) --> TYPE(MPI_Datatype) :: recvtypes(*)
- INTEGER OLDTYPE --> TYPE(MPI_Datatype) :: oldtype
- INTEGER ARRAY_OF_TYPES(*) --> TYPE(MPI_Datatype) :: array_of_types(*)
- INTEGER TYPE --> TYPE(MPI_Datatype) :: type
- INTEGER ARRAY_OF_DATATYPES(*) --> TYPE(MPI_Datatype) :: array_of_datatypes(*)
- INTEGER NEWTYPE --> TYPE(MPI_Datatype) :: newtype
- INTEGER ORIGIN_DATATYPE --> TYPE(MPI_Datatype) :: origin_datatype
- INTEGER TARGET_DATATYPE --> TYPE(MPI_Datatype) :: target_datatype
- INTEGER ETYPE --> TYPE(MPI_Datatype) :: etype
- INTEGER FILETYPE --> TYPE(MPI_Datatype) :: filetype
- INTEGER OP --> TYPE(MPI_Op) :: op
- INTEGER OLDCOMM --> TYPE(MPI_Comm) :: oldcomm
- INTEGER INFO --> TYPE(MPI_Info) :: info
- INTEGER NEWINFO --> TYPE(MPI_Info) :: newinfo
- INTEGER INFO_USED --> TYPE(MPI_Info) :: info_used
- INTEGER ARRAY_OF_INFO(*) --> TYPE(MPI_Info) :: array_of_info(*)
- INTEGER COMM --> TYPE(MPI_Comm) :: comm
- INTEGER COMM1 --> TYPE(MPI_Comm) :: comm1
- INTEGER COMM2 --> TYPE(MPI_Comm) :: comm2
- INTEGER LOCAL_COMM --> TYPE(MPI_Comm) :: local_comm
- INTEGER PEER_COMM --> TYPE(MPI_Comm) :: peer_comm
- INTEGER NEWINTERCOMM --> TYPE(MPI_Comm) :: newintercomm
- INTEGER INTERCOMM --> TYPE(MPI_Comm) :: intercomm
- INTEGER INTRACOMM --> TYPE(MPI_Comm) :: intracomm
- INTEGER COMM_OLD --> TYPE(MPI_Comm) :: comm_old
- INTEGER COMM_CART --> TYPE(MPI_Comm) :: comm_cart
- INTEGER COMM_DIST_GRAPH --> TYPE(MPI_Comm) :: comm_dist_graph
- INTEGER COMM_GRAPH --> TYPE(MPI_Comm) :: comm_graph
- INTEGER PARENT --> TYPE(MPI_Comm) :: parent
- INTEGER GROUP --> TYPE(MPI_Group) :: group
- INTEGER GROUP1 --> TYPE(MPI_Group) :: group1
- INTEGER GROUP2 --> TYPE(MPI_Group) :: group2
- INTEGER NEWGROUP --> TYPE(MPI_Group) :: newgroup
- INTEGER NEWCOMM --> TYPE(MPI_Comm) :: newcomm
- INTEGER REQUEST --> TYPE(MPI_Request) :: request
- INTEGER ARRAY_OF_REQUESTS(*) --> TYPE(MPI_Request) :: array_of_requests(*)
- INTEGER WIN --> TYPE(MPI_Win) :: win
- INTEGER ERRHANDLER --> TYPE(MPI_Errhandler) :: errhandler
Reorder type declaration lines according to the dummy argument list.
Remove first REQUEST in the declarations of the Fortran interface of MPI_BSEND_INIT and MPI_SEND_INIT.
MPI-2.2, A.3.14 Deprecated Fortran Bindings hasn't a counterpart in new A.4

mpi-forum / mpi-forum-historic

New MPI-3 Fortran Support - #S: All new Fortran 2008 bindings - Part 1 #247

247-S: All new Fortran 2008 bindings - Part 1See Ticket #229-A for an overview on the New MPI-3 Fortran Support.

Description

Extended Scope

History

Proposed Solution

Impact on Implementations

Impact on Applications / Users

Alternative Solutions

Entry for the Change Log