summaryrefslogtreecommitdiffstats
path: root/config/mpich
Commit message (Collapse)AuthorAgeFilesLines
* [svn-r21479] Merge revision 21101 from trunk to 1.8 branch:Mike McGreevy2011-10-051-83/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* [svn-r17655] Purpose:Mike McGreevy2009-10-151-9/+9
| | | | | | | | | | | | Configure cache-val cleanup Description: Corrected some misnamed cache values in configure / config files. Tested: h5committest
* [svn-r13312] Updated copyright notice.Albert Cheng2007-02-141-2/+3
|
* [svn-r12045] Purpose:MuQun Yang2006-03-091-0/+28
| | | | | | | | | | | | | Setting appropriate macro during configuration. Description: We found special collective IO doesn't work in mpich 1.2.5 and 1.2.6. Solution: Use this script to detect this during configuration and set the correct macro. Platforms tested: heping,mir and copper Misc. update:
* [svn-r11782] Purpose:Albert Cheng2005-12-111-0/+12
| | | | | | | | | | | | | | bug fix. Description: Mpich2 also has the derived type errors but some mpich2 gave no verison number and some gave 1.0.2. Solution: Added those two cases to catch mpich2 that had these sort of errors. Platforms tested: heping using mpich and mpich2.
* [svn-r11610] Purpose:Albert Cheng2005-10-261-0/+42
Bug fix. Description: The previous way of detecting the MPICH version fails if the suspected $CC does not give the expected MPICH version information. Though no consequence, it generates error messages that alarm users. Also, mpich2 gives the version information as if it were mpich v1.0.2 which was incorrectly included as an earlier version of the origianl mpich. Solution: Implemented a more robust code to detect the version and narrow the recognition down to v1.2.0-v1.2.5. Also, the code were duplicated in two files (linux-gnulibc1 and ia64-linux-gnu). Combined them into a new file called mpich. Platforms tested: Tested in heping using mpicc and mpich2/mpicc and also in tg-ncsa. Misc. update: Updated MANIFEST.