b9316d3136
Following the commit f750c6932c, I compared `ompi/mpi/fortran/use-mpi-f08/*.F90` and `ompi/mpi/fortran/use-mpi-f08/profile/p*.F90`, and `ompi/mpi/fortran/use-mpi-f08/mod/mpi-f08-interfaces.F90` and `ompi/mpi/fortran/use-mpi-f08/mod/pmpi-f08-interfaces.F90`. There are many differences. Some are bugs of `MPI_*`, some are bugs of `PMPI_*`. I'm not sure how these bugs affect applications. To make it easy to compare these files future, I also removed editorial differences. Signed-off-by: KAWASHIMA Takahiro <t-kawashima@jp.fujitsu.com> (cherry picked from commit cf6d28cb66981cf315f84e5efb8f8256b6c6a3a4)
33 строки
1.3 KiB
Fortran
33 строки
1.3 KiB
Fortran
! -*- f90 -*-
|
|
!
|
|
! Copyright (c) 2009-2012 Cisco Systems, Inc. All rights reserved.
|
|
! Copyright (c) 2009-2012 Los Alamos National Security, LLC.
|
|
! All rights reserved.
|
|
! Copyright (c) 2018 Research Organization for Information Science
|
|
! and Technology (RIST). All rights reserved.
|
|
! Copyright (c) 2018 FUJITSU LIMITED. All rights reserved.
|
|
! $COPYRIGHT$
|
|
|
|
#include "ompi/mpi/fortran/configure-fortran-output.h"
|
|
|
|
subroutine MPI_Pack_external_f08(datarep,inbuf,incount,datatype,outbuf,outsize, &
|
|
position,ierror)
|
|
use :: mpi_f08_types, only : MPI_Datatype, MPI_ADDRESS_KIND
|
|
use :: ompi_mpifh_bindings, only : ompi_pack_external_f
|
|
implicit none
|
|
CHARACTER(LEN=*), INTENT(IN) :: datarep
|
|
OMPI_FORTRAN_IGNORE_TKR_TYPE, INTENT(IN) :: inbuf
|
|
OMPI_FORTRAN_IGNORE_TKR_TYPE :: outbuf
|
|
INTEGER, INTENT(IN) :: incount
|
|
TYPE(MPI_Datatype), INTENT(IN) :: datatype
|
|
INTEGER(MPI_ADDRESS_KIND), INTENT(IN) :: outsize
|
|
INTEGER(MPI_ADDRESS_KIND), INTENT(INOUT) :: position
|
|
INTEGER, OPTIONAL, INTENT(OUT) :: ierror
|
|
integer :: c_ierror
|
|
|
|
call ompi_pack_external_f(datarep,inbuf,incount,datatype%MPI_VAL,outbuf, &
|
|
outsize,position,c_ierror,len(datarep))
|
|
if (present(ierror)) ierror = c_ierror
|
|
|
|
end subroutine MPI_Pack_external_f08
|