Dear all,

There are some collective communications with the possibility of terminating 
abnormally when MPI_IN_PLACE is specified.
(MPI_Allgather/MPI_Allgatherv/MPI_Gather/MPI_Scatter)
They refer to sdtype or rdtype (For MPI_Scatter) unconditionally by the 
consideration leakage of the MPI standard at MPI_IN_PLACE.
It terminates abnormally when NULL is specified for a data type of the sending 
side or receiving side with which MPI_IN_PLACE is specifiable. 
e.g.) MPI_Allgather(MPI_IN_PLACE, scount, NULL, rbuf, rcount, recvdtype, ...);

- Functions which have this MPI_IN_PLACE problem:
    Which data type: The sending side data type
    It terminates abnormally when sdtype=NULL is specified at sbuf=MPI_IN_PLACE.
    (sdtype must be ignored when sbuf = MPI_IN_PLACE.)
          ompi_coll_tuned_allgather_intra_dec_fixed
          ompi_coll_tuned_allgatherv_intra_dec_fixed
      MPI_Gather
          ompi_coll_tuned_gather_intra_binomial
      MPI_Allgather
          ompi_coll_tuned_allgather_intra_bruck
          ompi_coll_tuned_allgather_intra_recursivedoubling
          ompi_coll_tuned_allgather_intra_ring
          ompi_coll_tuned_allgather_intra_neighborexchange
          ompi_coll_tuned_allgather_intra_two_procs
      MPI_Allgatherv
          ompi_coll_tuned_allgatherv_intra_bruck
          ompi_coll_tuned_allgatherv_intra_ring
          ompi_coll_tuned_allgatherv_intra_neighborexchange
          ompi_coll_tuned_allgatherv_intra_two_procs
    Which data type: The receiving side data type
    It terminates abnormally when rdtype=NULL is specified at rbuf=MPI_IN_PLACE.
    ("rdtype" must be ignored when rbuf = MPI_IN_PLACE.)
      MPI_Scatter
          ompi_coll_tuned_scatter_intra_binomial

We attach a patch.

Best Regards,
Yuki Matsumoto,
MPI development team,
Fujitsu

Attachment: inplace.patch
Description: inplace.patch

Copyright (c) 2012       FUJITSU LIMITED.  All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:

* Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.

* Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer listed
in this license in the documentation and/or other materials
provided with the distribution.

* Neither the name of the copyright holders nor the names of its
contributors may be used to endorse or promote products derived from
this software without specific prior written permission.

The copyright holders provide no reassurances that the source code
provided does not infringe any patent, copyright, or any other
intellectual property rights of third parties.  The copyright holders
disclaim any liability to any recipient for claims brought against
recipient by any third party for infringement of that parties
intellectual property rights.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.


Reply via email to