HARNESS FT-MPI complete software distribution
Complete distribution of the FT-MPI runtime library software and the ICL/UTK 'C' based HARNESS runtime system.
Version number 1.0.1
The distribution is self contained and includes extensive documentation as well as a number of FT examples codes that can be used as templates for new FT applications.
The MD5 hash of the distribution is:
File name: harness-ftmpi-1.0.1.tar.gz
The distribution is: 800 KBytes
- bug fix/clearification of MPI_LONG_LONG respectively MPI_LONG_LONG_INT
- bug fix in the datatype handling for IA64 (and MPI_Aint)
- bug fix in msg.c for intel-compilers on IA64
- README's are cleaned up
- g_hcore_d loading of multiple plug-ins handled correctly
- some minor warnings (prototype issues) in the ftmpi directory
Copyright © 2017 The University of Tennessee. 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.
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.