Kawashima-san,

you are right, I mixed MPI_Buffer_detach and MPI_Win_detach
sorry for the confusion

Cheers,

Gilles

On Thursday, August 27, 2015, Kawashima, Takahiro <
t-kawash...@jp.fujitsu.com> wrote:

> Gilles,
>
> > there is a comment in the source code to explain this.
>
> Could you point where the comment is?
>
> I can find a comment about MPI_Buffer_detach in
> ompi/mpi/fortran/mpif-h/buffer_detach_f.c and
> ompi/mpi/fortran/use-mpi-f08/buffer_detach.c files.
> But the situation is different form MPI_Buffer_detach.
>
> The declaration of MPI_Win_detach is not changed since
> the one-sided code was merged into the trunk at commit
> 49d938de (svn r30816).
>
> Regards,
> Takahiro Kawashima
>
> > iirc, the MPI_Win_detach discrepancy with the standard is intentional in
> > fortran 2008,
> > there is a comment in the source code to explain this.
> >
> > On Thursday, August 27, 2015, Kawashima, Takahiro <
> > t-kawash...@jp.fujitsu.com <javascript:;>> wrote:
> >
> > > Oh, I also noticed it yesterday and was about to report it.
> > >
> > > And one more, the base parameter of MPI_Win_detach.
> > >
> > > Regards,
> > > Takahiro Kawashima
> > >
> > > > Dear OpenMPI developers,
> > > >
> > > > I noticed a bug in the definition of the 3 MPI-3 RMA functions
> > > > MPI_Compare_and_swap, MPI_Fetch_and_op and MPI_Raccumulate.
> > > >
> > > > According to the MPI standard, the origin_addr and compare_addr
> > > > parameters of these functions have a const attribute, which is
> missing
> > > > in OpenMPI's mpi.h (OpenMPI 1.8.x and 1.10.0).
> > > >
> > > > Regards,
> > > >
> > > > Michael
> _______________________________________________
> devel mailing list
> de...@open-mpi.org <javascript:;>
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post:
> http://www.open-mpi.org/community/lists/devel/2015/08/17880.php
>

Reply via email to