
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)
22 строки
846 B
Fortran
22 строки
846 B
Fortran
! -*- f90 -*-
|
|
!
|
|
! Copyright (c) 2010-2015 Cisco Systems, Inc. All rights reserved.
|
|
! Copyright (c) 2009-2015 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"
|
|
|
|
function MPI_Aint_add_f08(base, disp)
|
|
use :: mpi_f08_types, only : MPI_ADDRESS_KIND
|
|
use :: ompi_mpifh_bindings, only : ompi_aint_add_f
|
|
implicit none
|
|
INTEGER(MPI_ADDRESS_KIND) :: MPI_Aint_add_f08
|
|
INTEGER(MPI_ADDRESS_KIND), INTENT(IN) :: base
|
|
INTEGER(MPI_ADDRESS_KIND), INTENT(IN) :: disp
|
|
MPI_Aint_add_f08 = ompi_aint_add_f(base, disp)
|
|
end function MPI_Aint_add_f08
|