[svn-r21479] Merge revision 21101 from trunk to 1.8 branch:

HDFFV-7639

Purpose:

    Remove H5_MPI_SPECIAL_COLLECTIVE_IO_WORKS and
    H5_MPI_COMPLEX_DERIVED_DATATYPE_WORKS #defines from source.

Description:

    Two advanced parallel functionalities, special collective IO and
    complex derived datatypes, are not supported by older
    implementations of mpi, and thus our code limits the use of these
    features with #ifdefs and has checks in configure to set them (or
    not). Unfortunately, configure can't actually run a parallel check
    to see if these features are working (nor not) so it resorts to
    looking in the config files where they are explicity enabled or
    disabled based on versions of mpi, sytems being built on, or for
    no documented reason at all (i.e. just set to on or off as some
    'default'). Overriding these settings is easy if need be, provided
    it is known that it needs to be done to get improved performance,
    and oftentimes it is not.

    Most new MPI implementations successfully handle the functionality
    requested when these #defines are set, and many of the "turn these
    features off" cases in the config files are for old (> 5 years)
    versions of MPI and retired systems (such as NCSA's tungsten).

    Therefore, the decision has been made to remove the support for
    these old versions of MPI and systems that cannot handle these
    behaviors. The #ifdefs and supporting setup in the config/ files
    and configure script has been removed, and the code executed when
    these options were not set removed from the source.

    In passing, this commit also cleans up some whitespace issues in
    both t_mpi.c and H5Dmpio.c. Furthermore, in t_mpi.c, the special
    collective IO test was not getting regularly run due to it being
    written to work only with four processes (we regularly test with
    six, previously with three), and thus it failed when actually run
    due to an out of bounds data buffer assignment. It has been
    modified to run at any number of processes greater than four, and
    the memory problem has been fixed so the test passes.

Tested:

    Jam, h5committest, Ember

1 files changed, 0 insertions, 83 deletions

diff --git a/config/mpich b/config/mpich
deleted file mode 100644
index 575859e..0000000
--- a/config/mpich
+++ /dev/null
@@ -1,83 +0,0 @@
-#							-*- shell-script -*-
-#
-# Copyright by The HDF Group.
-# Copyright by the Board of Trustees of the University of Illinois.
-# All rights reserved.
-#
-# This file is part of HDF5.  The full HDF5 copyright notice, including
-# terms governing use, modification, and redistribution, is contained in
-# the files COPYING and Copyright.html.  COPYING can be found at the root
-# of the source code distribution tree; Copyright.html can be found at the
-# root level of an installed copy of the electronic HDF5 document set and
-# is linked from the top-level documents page.  It can also be found at
-# http://hdfgroup.org/HDF5/doc/Copyright.html.  If you do not have
-# access to either file, you may request a copy from help@hdfgroup.org.
-
-# This file should be sourced into configure if the compiler is the
-# MPICH compiler script. It is careful not to do anything if the compiler
-# is not MPICH.
-
-# Check if mpicc can support complicated derived datatype correctly.
-# We know that mpich 1.2.4 and 1.2.5 do not support it correctly.  We assume
-# older versions do not work either.  We don't know of a way of testing its
-# correctness without the risk of hanging the configure process.  So, we
-# set the configure variable hdf5_cv_mpi_complex_derived_datatype_works to no.
-# Notice that this code works only if the mpicc compiler shows its $MPIVERSION
-# properly.  It is confirmed mpicc does that as far back as v1.2.3.
-
-# mpich2 do not support it correctly.  But mpich2 reports small version number
-# indistiguishable from mpich.  Some mpich2 reports blank, some reports 1.0.2.
-
-if [ -z "$hdf5_cv_mpi_complex_derived_datatype_works" ]; then
-    ccversion=`$CC -v 2>/dev/null`
-    # mpich compiler will give "mpicc for 1.2.x ..."
-    if echo "$ccversion" | grep '^mpicc for' > /dev/null ; then
-	# $CC is an MPICH compiler. Grab the version numbers.
-        ccversion=`echo $ccversion | cut -f3 -d' '`
-	case "$ccversion" in
-	    1.2.[0-5]*)
-		hdf5_cv_mpi_complex_derived_datatype_works='no'
-		;;
-	    1.0.2)
-		# mpich2 is recycling the version number, some report
-		# 1.0.2, some report blank.
-		hdf5_cv_mpi_complex_derived_datatype_works='no'
-		;;
-	    "")
-		# got blank ccversion.  Assume it is bad a mpich2.
-		hdf5_cv_mpi_complex_derived_datatype_works='no'
-		;;
-	    *)
-		# assume okay
-		;;
-	esac
-    fi
-fi
-
-if [ -z "$hdf5_cv_mpi_special_collective_io_works" ]; then
-    ccversion=`$CC -v 2>/dev/null`
-    # mpich compiler will give "mpicc for 1.2.x ..."
-    if echo "$ccversion" | grep '^mpicc for' > /dev/null ; then
-	# $CC is an MPICH compiler. Grab the version numbers.
-        ccversion=`echo $ccversion | cut -f3 -d' '`
-	case "$ccversion" in
-	    1.2.[0-6]*)
-		hdf5_cv_mpi_special_collective_io_works='no'
-		;;
-	    1.0.2)
-		# mpich2 is recycling the version number, some report
-		# 1.0.2, some report blank.
-		hdf5_cv_mpi_special_collective_io_works='no'
-		;;
-	    "")
-		# got blank ccversion.  Assume it is bad a mpich2.
-		hdf5_cv_mpi_special_collective_io_works='no'
-		;;
-	    *)
-		# assume okay
-		;;
-	esac
-    fi
-fi
-
-