2012-01-03 17:25:37 +00:00
|
|
|
Copyright (c) 2004-2007 The Trustees of Indiana University and Indiana
|
|
|
|
University Research and Technology
|
|
|
|
Corporation. All rights reserved.
|
2015-03-05 13:12:37 -05:00
|
|
|
Copyright (c) 2004-2015 The University of Tennessee and The University
|
2012-01-03 17:25:37 +00:00
|
|
|
of Tennessee Research Foundation. All rights
|
|
|
|
reserved.
|
2015-04-01 15:40:42 -07:00
|
|
|
Copyright (c) 2004-2008 High Performance Computing Center Stuttgart,
|
2012-01-03 17:25:37 +00:00
|
|
|
University of Stuttgart. All rights reserved.
|
|
|
|
Copyright (c) 2004-2007 The Regents of the University of California.
|
|
|
|
All rights reserved.
|
2016-02-02 11:22:04 -08:00
|
|
|
Copyright (c) 2006-2016 Cisco Systems, Inc. All rights reserved.
|
2012-01-03 17:25:37 +00:00
|
|
|
Copyright (c) 2006-2011 Mellanox Technologies. All rights reserved.
|
2012-01-24 15:50:45 +00:00
|
|
|
Copyright (c) 2006-2012 Oracle and/or its affiliates. All rights reserved.
|
2012-01-03 17:25:37 +00:00
|
|
|
Copyright (c) 2007 Myricom, Inc. All rights reserved.
|
|
|
|
Copyright (c) 2008 IBM Corporation. All rights reserved.
|
|
|
|
Copyright (c) 2010 Oak Ridge National Labs. All rights reserved.
|
2013-10-07 19:20:26 +00:00
|
|
|
Copyright (c) 2011 University of Houston. All rights reserved.
|
2015-04-15 08:05:08 -07:00
|
|
|
Copyright (c) 2013-2015 Intel, Inc. All rights reserved
|
2015-04-15 15:32:45 -04:00
|
|
|
Copyright (c) 2015 NVIDIA Corporation. All rights reserved.
|
2012-01-03 17:25:37 +00:00
|
|
|
$COPYRIGHT$
|
2004-11-22 01:38:40 +00:00
|
|
|
|
2012-01-03 17:25:37 +00:00
|
|
|
Additional copyrights may follow
|
|
|
|
|
|
|
|
$HEADER$
|
2015-04-01 15:40:42 -07:00
|
|
|
|
2012-01-03 17:25:37 +00:00
|
|
|
===========================================================================
|
|
|
|
|
|
|
|
When submitting questions and problems, be sure to include as much
|
|
|
|
extra information as possible. This web page details all the
|
|
|
|
information that we request in order to provide assistance:
|
|
|
|
|
|
|
|
http://www.open-mpi.org/community/help/
|
|
|
|
|
|
|
|
The best way to report bugs, send comments, or ask questions is to
|
|
|
|
sign up on the user's and/or developer's mailing list (for user-level
|
|
|
|
and developer-level questions; when in doubt, send to the user's
|
|
|
|
list):
|
|
|
|
|
|
|
|
users@open-mpi.org
|
|
|
|
devel@open-mpi.org
|
|
|
|
|
|
|
|
Because of spam, only subscribers are allowed to post to these lists
|
|
|
|
(ensure that you subscribe with and post from exactly the same e-mail
|
|
|
|
address -- joe@example.com is considered different than
|
|
|
|
joe@mycomputer.example.com!). Visit these pages to subscribe to the
|
|
|
|
lists:
|
|
|
|
|
|
|
|
http://www.open-mpi.org/mailman/listinfo.cgi/users
|
|
|
|
http://www.open-mpi.org/mailman/listinfo.cgi/devel
|
|
|
|
|
|
|
|
Thanks for your time.
|
|
|
|
|
|
|
|
===========================================================================
|
|
|
|
|
|
|
|
Much, much more information is also available in the Open MPI FAQ:
|
|
|
|
|
|
|
|
http://www.open-mpi.org/faq/
|
|
|
|
|
|
|
|
===========================================================================
|
|
|
|
|
|
|
|
The following abbreviated list of release notes applies to this code
|
2015-04-15 15:10:41 -07:00
|
|
|
base as of this writing (April 2015):
|
2012-01-03 17:25:37 +00:00
|
|
|
|
|
|
|
General notes
|
|
|
|
-------------
|
|
|
|
|
2013-11-07 17:14:28 +00:00
|
|
|
- Open MPI now includes two public software layers: MPI and OpenSHMEM.
|
2015-04-01 15:40:42 -07:00
|
|
|
Throughout this document, references to Open MPI implicitly include
|
|
|
|
both of these layers. When distinction between these two layers is
|
2013-11-07 17:14:28 +00:00
|
|
|
necessary, we will reference them as the "MPI" and "OSHMEM" layers
|
2015-04-01 15:40:42 -07:00
|
|
|
respectively.
|
|
|
|
|
2014-03-19 20:50:28 +00:00
|
|
|
- OpenSHMEM is a collaborative effort between academia, industry, and
|
|
|
|
the U.S. Government to create a specification for a standardized API
|
|
|
|
for parallel programming in the Partitioned Global Address Space
|
|
|
|
(PGAS). For more information about the OpenSHMEM project, including
|
|
|
|
access to the current OpenSHMEM specification, please visit:
|
2013-11-07 17:14:28 +00:00
|
|
|
|
|
|
|
http://openshmem.org/
|
2015-04-01 15:40:42 -07:00
|
|
|
|
2014-03-19 20:50:28 +00:00
|
|
|
This OpenSHMEM implementation is provided on an experimental basis;
|
|
|
|
it has been lightly tested and will only work in Linux environments.
|
|
|
|
Although this implementation attempts to be portable to multiple
|
|
|
|
different environments and networks, it is still new and will likely
|
|
|
|
experience growing pains typical of any new software package.
|
2014-03-19 20:57:37 +00:00
|
|
|
End-user feedback is greatly appreciated.
|
2014-03-19 20:50:28 +00:00
|
|
|
|
2014-03-19 20:57:37 +00:00
|
|
|
This implementation will currently most likely provide optimal
|
|
|
|
performance on Mellanox hardware and software stacks. Overall
|
|
|
|
performance is expected to improve as other network vendors and/or
|
|
|
|
institutions contribute platform specific optimizations.
|
2014-03-19 20:50:28 +00:00
|
|
|
|
|
|
|
See below for details on how to enable the OpenSHMEM implementation.
|
2013-11-07 17:14:28 +00:00
|
|
|
|
2012-01-03 17:25:37 +00:00
|
|
|
- Open MPI includes support for a wide variety of supplemental
|
|
|
|
hardware and software package. When configuring Open MPI, you may
|
|
|
|
need to supply additional flags to the "configure" script in order
|
|
|
|
to tell Open MPI where the header files, libraries, and any other
|
|
|
|
required files are located. As such, running "configure" by itself
|
|
|
|
may not include support for all the devices (etc.) that you expect,
|
|
|
|
especially if their support headers / libraries are installed in
|
|
|
|
non-standard locations. Network interconnects are an easy example
|
2015-04-15 15:10:41 -07:00
|
|
|
to discuss -- Libfabric and OpenFabrics networks, for example, both
|
2012-01-03 17:25:37 +00:00
|
|
|
have supplemental headers and libraries that must be found before
|
|
|
|
Open MPI can build support for them. You must specify where these
|
|
|
|
files are with the appropriate options to configure. See the
|
|
|
|
listing of configure command-line switches, below, for more details.
|
|
|
|
|
|
|
|
- The majority of Open MPI's documentation is here in this file, the
|
|
|
|
included man pages, and on the web site FAQ
|
2015-04-15 15:10:41 -07:00
|
|
|
(http://www.open-mpi.org/).
|
2012-01-03 17:25:37 +00:00
|
|
|
|
|
|
|
- Note that Open MPI documentation uses the word "component"
|
|
|
|
frequently; the word "plugin" is probably more familiar to most
|
|
|
|
users. As such, end users can probably completely substitute the
|
|
|
|
word "plugin" wherever you see "component" in our documentation.
|
|
|
|
For what it's worth, we use the word "component" for historical
|
|
|
|
reasons, mainly because it is part of our acronyms and internal API
|
2013-11-07 17:14:28 +00:00
|
|
|
function calls.
|
2012-01-03 17:25:37 +00:00
|
|
|
|
|
|
|
- The run-time systems that are currently supported are:
|
|
|
|
- rsh / ssh
|
|
|
|
- LoadLeveler
|
2012-02-24 11:03:40 +00:00
|
|
|
- PBS Pro, Torque
|
2012-01-03 17:25:37 +00:00
|
|
|
- Platform LSF (v7.0.2 and later)
|
|
|
|
- SLURM
|
2015-04-17 15:30:55 -07:00
|
|
|
- Cray XE, XC, and XK
|
2012-02-23 20:39:10 +00:00
|
|
|
- Oracle Grid Engine (OGE) 6.1, 6.2 and open source Grid Engine
|
2012-01-03 17:25:37 +00:00
|
|
|
|
|
|
|
- Systems that have been tested are:
|
2013-10-07 19:20:26 +00:00
|
|
|
- Linux (various flavors/distros), 32 bit, with gcc
|
2012-01-03 17:25:37 +00:00
|
|
|
- Linux (various flavors/distros), 64 bit (x86), with gcc, Absoft,
|
2013-10-07 19:20:26 +00:00
|
|
|
Intel, and Portland (*)
|
2015-04-17 15:30:55 -07:00
|
|
|
- OS X (10.6, 10.7, 10.8, 10.9, 10.10), 32 and 64 bit (x86_64), with
|
|
|
|
XCode and Absoft compilers (*)
|
2012-01-03 17:25:37 +00:00
|
|
|
|
|
|
|
(*) Be sure to read the Compiler Notes, below.
|
|
|
|
|
|
|
|
- Other systems have been lightly (but not fully tested):
|
2013-10-04 12:12:18 +00:00
|
|
|
- Cygwin 32 & 64 bit with gcc
|
2015-04-17 15:30:55 -07:00
|
|
|
- ARMv4, ARMv5, ARMv6, ARMv7, ARMv8
|
2012-01-03 17:25:37 +00:00
|
|
|
- Other 64 bit platforms (e.g., Linux on PPC64)
|
2013-10-07 19:20:26 +00:00
|
|
|
- Oracle Solaris 10 and 11, 32 and 64 bit (SPARC, i386, x86_64),
|
2015-04-17 15:30:55 -07:00
|
|
|
with Oracle Solaris Studio 12.2, 12.3, and 12.4
|
2012-01-03 17:25:37 +00:00
|
|
|
|
|
|
|
Compiler Notes
|
|
|
|
--------------
|
|
|
|
|
2015-06-23 18:43:37 -07:00
|
|
|
- Open MPI requires a C99-capable compiler to build.
|
|
|
|
|
2012-01-03 17:25:37 +00:00
|
|
|
- Mixing compilers from different vendors when building Open MPI
|
== Highlights ==
1. New mpifort wrapper compiler: you can utilize mpif.h, use mpi, and use mpi_f08 through this one wrapper compiler
1. mpif77 and mpif90 still exist, but are sym links to mpifort and may be removed in a future release
1. The mpi module has been re-implemented and is significantly "mo' bettah"
1. The mpi_f08 module offers many, many improvements over mpif.h and the mpi module
This stuff is coming from a VERY long-lived mercurial branch (3 years!); it'll almost certainly take a few SVN commits and a bunch of testing before I get it correctly committed to the SVN trunk.
== More details ==
Craig Rasmussen and I have been working with the MPI-3 Fortran WG and Fortran J3 committees for a long, long time to make a prototype MPI-3 Fortran bindings implementation. We think we're at a stable enough state to bring this stuff back to the trunk, with the goal of including it in OMPI v1.7.
Special thanks go out to everyone who has been incredibly patient and helpful to us in this journey:
* Rolf Rabenseifner/HLRS (mastermind/genius behind the entire MPI-3 Fortran effort)
* The Fortran J3 committee
* Tobias Burnus/gfortran
* Tony !Goetz/Absoft
* Terry !Donte/Oracle
* ...and probably others whom I'm forgetting :-(
There's still opportunities for optimization in the mpi_f08 implementation, but by and large, it is as far along as it can be until Fortran compilers start implementing the new F08 dimension(..) syntax.
Note that gfortran is currently unsupported for the mpi_f08 module and the new mpi module. gfortran users will a) fall back to the same mpi module implementation that is in OMPI v1.5.x, and b) not get the new mpi_f08 module. The gfortran maintainers are actively working hard to add the necessary features to support both the new mpi_f08 module and the new mpi module implementations. This will take some time.
As mentioned above, ompi/mpi/f77 and ompi/mpi/f90 no longer exist. All the fortran bindings implementations have been collated under ompi/mpi/fortran; each implementation has its own subdirectory:
{{{
ompi/mpi/fortran/
base/ - glue code
mpif-h/ - what used to be ompi/mpi/f77
use-mpi-tkr/ - what used to be ompi/mpi/f90
use-mpi-ignore-tkr/ - new mpi module implementation
use-mpi-f08/ - new mpi_f08 module implementation
}}}
There's also a prototype 6-function-MPI implementation under use-mpi-f08-desc that emulates the new F08 dimension(..) syntax that isn't fully available in Fortran compilers yet. We did that to prove it to ourselves that it could be done once the compilers fully support it. This directory/implementation will likely eventually replace the use-mpi-f08 version.
Other things that were done:
* ompi_info grew a few new output fields to describe what level of Fortran support is included
* Existing Fortran examples in examples/ were renamed; new mpi_f08 examples were added
* The old Fortran MPI libraries were renamed:
* libmpi_f77 -> libmpi_mpifh
* libmpi_f90 -> libmpi_usempi
* The configury for Fortran was consolidated and significantly slimmed down. Note that the F77 env variable is now IGNORED for configure; you should only use FC. Example:
{{{
shell$ ./configure CC=icc CXX=icpc FC=ifort ...
}}}
All of this work was done in a Mercurial branch off the SVN trunk, and hosted at Bitbucket. This branch has got to be one of OMPI's longest-running branches. Its first commit was Tue Apr 07 23:01:46 2009 -0400 -- it's over 3 years old! :-) We think we've pulled in all relevant changes from the OMPI trunk (e.g., Fortran implementations of the new MPI-3 MPROBE stuff for mpif.h, use mpi, and use mpi_f08, and the recent Fujitsu Fortran patches).
I anticipate some instability when we bring this stuff into the trunk, simply because it touches a LOT of code in the MPI layer in the OMPI code base. We'll try our best to make it as pain-free as possible, but please bear with us when it is committed.
This commit was SVN r26283.
2012-04-18 15:57:29 +00:00
|
|
|
(e.g., using the C/C++ compiler from one vendor and the Fortran
|
2012-01-03 17:25:37 +00:00
|
|
|
compiler from a different vendor) has been successfully employed by
|
|
|
|
some Open MPI users (discussed on the Open MPI user's mailing list),
|
|
|
|
but such configurations are not tested and not documented. For
|
|
|
|
example, such configurations may require additional compiler /
|
|
|
|
linker flags to make Open MPI build properly.
|
|
|
|
|
2012-02-23 20:39:10 +00:00
|
|
|
- In general, the latest versions of compilers of a given vendor's
|
|
|
|
series have the least bugs. We have seen cases where Vendor XYZ's
|
|
|
|
compiler version A.B fails to compile Open MPI, but version A.C
|
|
|
|
(where C>B) works just fine. If you run into a compile failure, you
|
|
|
|
might want to double check that you have the latest bug fixes and
|
|
|
|
patches for your compiler.
|
|
|
|
|
2014-01-17 21:39:59 +00:00
|
|
|
- Users have reported issues with older versions of the Fortran PGI
|
|
|
|
compiler suite when using Open MPI's (non-default) --enable-debug
|
|
|
|
configure option. Per the above advice of using the most recent
|
|
|
|
version of a compiler series, the Open MPI team recommends using the
|
|
|
|
latest version of the PGI suite, and/or not using the --enable-debug
|
2014-01-17 15:26:51 +00:00
|
|
|
configure option. If it helps, here's what we have found with some
|
|
|
|
(not comprehensive) testing of various versions of the PGI compiler
|
|
|
|
suite:
|
|
|
|
|
|
|
|
pgi-8 : NO known good version with --enable-debug
|
|
|
|
pgi-9 : 9.0-4 known GOOD
|
|
|
|
pgi-10: 10.0-0 known GOOD
|
|
|
|
pgi-11: NO known good version with --enable-debug
|
2015-07-17 17:39:43 -07:00
|
|
|
pgi-12: 12.10 known BAD due to C99 compliance issues, and 12.8
|
|
|
|
and 12.9 both known BAD with --enable-debug
|
2014-01-17 15:26:51 +00:00
|
|
|
pgi-13: 13.10 known GOOD
|
|
|
|
|
2014-01-17 21:39:59 +00:00
|
|
|
- Similarly, there is a known Fortran PGI compiler issue with long
|
2014-01-28 15:36:52 +00:00
|
|
|
source directory path names that was resolved in 9.0-4 (9.0-3 is
|
|
|
|
known to be broken in this regard).
|
2014-01-17 15:26:51 +00:00
|
|
|
|
2015-04-01 15:40:42 -07:00
|
|
|
- IBM's xlf compilers: NO known good version that can build/link
|
2014-08-15 21:25:51 +00:00
|
|
|
the MPI f08 bindings or build/link the OSHMEM Fortran bindings.
|
|
|
|
|
2014-01-14 18:59:26 +00:00
|
|
|
- On NetBSD-6 (at least AMD64 and i386), and possibly on OpenBSD,
|
|
|
|
libtool misidentifies properties of f95/g95, leading to obscure
|
|
|
|
compile-time failures if used to build Open MPI. You can work
|
|
|
|
around this issue by ensuring that libtool will not use f95/g95
|
|
|
|
(e.g., by specifying FC=<some_other_compiler>, or otherwise ensuring
|
|
|
|
a different Fortran compiler will be found earlier in the path than
|
|
|
|
f95/g95), or by disabling the Fortran MPI bindings with
|
|
|
|
--disable-mpi-fortran.
|
2014-01-13 17:06:35 +00:00
|
|
|
|
2012-09-05 18:45:38 +00:00
|
|
|
- Absoft 11.5.2 plus a service pack from September 2012 (which Absoft
|
|
|
|
says is available upon request), or a version later than 11.5.2
|
|
|
|
(e.g., 11.5.3), is required to compile the new Fortran mpi_f08
|
|
|
|
module.
|
|
|
|
|
2012-01-24 15:50:45 +00:00
|
|
|
- Open MPI does not support the Sparc v8 CPU target. However,
|
2015-04-01 15:40:42 -07:00
|
|
|
as of Solaris Studio 12.1, and later compilers, one should not
|
2012-01-24 15:50:45 +00:00
|
|
|
specify -xarch=v8plus or -xarch=v9. The use of the options
|
|
|
|
-m32 and -m64 for producing 32 and 64 bit targets, respectively,
|
2014-01-31 02:39:39 +00:00
|
|
|
are now preferred by the Solaris Studio compilers. GCC may
|
|
|
|
require either "-m32" or "-mcpu=v9 -m32", depending on GCC version.
|
2012-01-03 17:25:37 +00:00
|
|
|
|
2012-01-26 11:28:42 +00:00
|
|
|
- It has been noticed that if one uses CXX=sunCC, in which sunCC
|
2015-04-01 15:40:42 -07:00
|
|
|
is a link in the Solaris Studio compiler release, that the OMPI
|
2012-01-26 11:28:42 +00:00
|
|
|
build system has issue with sunCC and does not build libmpi_cxx.so.
|
|
|
|
Therefore the make install fails. So we suggest that one should
|
|
|
|
use CXX=CC, which works, instead of CXX=sunCC.
|
|
|
|
|
2012-02-10 19:25:23 +00:00
|
|
|
- If one tries to build OMPI on Ubuntu with Solaris Studio using the C++
|
2012-02-23 20:39:10 +00:00
|
|
|
compiler and the -m32 option, you might see a warning:
|
|
|
|
|
|
|
|
CC: Warning: failed to detect system linker version, falling back to
|
|
|
|
custom linker usage
|
|
|
|
|
2015-04-01 15:40:42 -07:00
|
|
|
And the build will fail. One can overcome this error by either
|
2012-02-10 19:25:23 +00:00
|
|
|
setting LD_LIBRARY_PATH to the location of the 32 bit libraries (most
|
2012-02-23 20:39:10 +00:00
|
|
|
likely /lib32), or giving LDFLAGS="-L/lib32 -R/lib32" to the configure
|
|
|
|
command. Officially, Solaris Studio is not supported on Ubuntu Linux
|
|
|
|
distributions, so additional problems might be incurred.
|
|
|
|
|
2012-02-24 11:03:40 +00:00
|
|
|
- Open MPI does not support the gccfss compiler (GCC For SPARC
|
|
|
|
Systems; a now-defunct compiler project from Sun).
|
|
|
|
|
2012-01-03 17:25:37 +00:00
|
|
|
- At least some versions of the Intel 8.1 compiler seg fault while
|
|
|
|
compiling certain Open MPI source code files. As such, it is not
|
|
|
|
supported.
|
|
|
|
|
|
|
|
- The Intel 9.0 v20051201 compiler on IA64 platforms seems to have a
|
|
|
|
problem with optimizing the ptmalloc2 memory manager component (the
|
|
|
|
generated code will segv). As such, the ptmalloc2 component will
|
|
|
|
automatically disable itself if it detects that it is on this
|
|
|
|
platform/compiler combination. The only effect that this should
|
|
|
|
have is that the MCA parameter mpi_leave_pinned will be inoperative.
|
|
|
|
|
2012-09-12 14:59:32 +00:00
|
|
|
- It has been reported that the Intel 9.1 and 10.0 compilers fail to
|
|
|
|
compile Open MPI on IA64 platforms. As of 12 Sep 2012, there is
|
|
|
|
very little (if any) testing performed on IA64 platforms (with any
|
|
|
|
compiler). Support is "best effort" for these platforms, but it is
|
|
|
|
doubtful that any effort will be expended to fix the Intel 9.1 /
|
|
|
|
10.0 compiler issuers on this platform.
|
|
|
|
|
2012-02-01 19:32:19 +00:00
|
|
|
- Early versions of the Intel 12.1 Linux compiler suite on x86_64 seem
|
|
|
|
to have a bug that prevents Open MPI from working. Symptoms
|
|
|
|
including immediate segv of the wrapper compilers (e.g., mpicc) and
|
|
|
|
MPI applications. As of 1 Feb 2012, if you upgrade to the latest
|
|
|
|
version of the Intel 12.1 Linux compiler suite, the problem will go
|
|
|
|
away.
|
|
|
|
|
2012-01-03 17:25:37 +00:00
|
|
|
- Early versions of the Portland Group 6.0 compiler have problems
|
|
|
|
creating the C++ MPI bindings as a shared library (e.g., v6.0-1).
|
|
|
|
Tests with later versions show that this has been fixed (e.g.,
|
|
|
|
v6.0-5).
|
|
|
|
|
|
|
|
- The Portland Group compilers prior to version 7.0 require the
|
|
|
|
"-Msignextend" compiler flag to extend the sign bit when converting
|
|
|
|
from a shorter to longer integer. This is is different than other
|
|
|
|
compilers (such as GNU). When compiling Open MPI with the Portland
|
|
|
|
compiler suite, the following flags should be passed to Open MPI's
|
|
|
|
configure script:
|
|
|
|
|
|
|
|
shell$ ./configure CFLAGS=-Msignextend CXXFLAGS=-Msignextend \
|
2015-04-15 15:10:41 -07:00
|
|
|
--with-wrapper-cflags=-Msignextend \
|
|
|
|
--with-wrapper-cxxflags=-Msignextend ...
|
2012-01-03 17:25:37 +00:00
|
|
|
|
|
|
|
This will both compile Open MPI with the proper compile flags and
|
|
|
|
also automatically add "-Msignextend" when the C and C++ MPI wrapper
|
|
|
|
compilers are used to compile user MPI applications.
|
|
|
|
|
2012-02-23 20:39:10 +00:00
|
|
|
- Using the MPI C++ bindings with older versions of the Pathscale
|
|
|
|
compiler on some platforms is an old issue that seems to be a
|
|
|
|
problem when Pathscale uses a back-end GCC 3.x compiler. Here's a
|
|
|
|
proposed solution from the Pathscale support team (from July 2010):
|
|
|
|
|
|
|
|
The proposed work-around is to install gcc-4.x on the system and
|
|
|
|
use the pathCC -gnu4 option. Newer versions of the compiler (4.x
|
|
|
|
and beyond) should have this fixed, but we'll have to test to
|
|
|
|
confirm it's actually fixed and working correctly.
|
|
|
|
|
|
|
|
We don't anticipate that this will be much of a problem for Open MPI
|
|
|
|
users these days (our informal testing shows that not many users are
|
|
|
|
still using GCC 3.x). Contact Pathscale support if you continue to
|
|
|
|
have problems with Open MPI's C++ bindings.
|
|
|
|
|
2012-01-03 17:25:37 +00:00
|
|
|
- Using the Absoft compiler to build the MPI Fortran bindings on Suse
|
|
|
|
9.3 is known to fail due to a Libtool compatibility issue.
|
|
|
|
|
== Highlights ==
1. New mpifort wrapper compiler: you can utilize mpif.h, use mpi, and use mpi_f08 through this one wrapper compiler
1. mpif77 and mpif90 still exist, but are sym links to mpifort and may be removed in a future release
1. The mpi module has been re-implemented and is significantly "mo' bettah"
1. The mpi_f08 module offers many, many improvements over mpif.h and the mpi module
This stuff is coming from a VERY long-lived mercurial branch (3 years!); it'll almost certainly take a few SVN commits and a bunch of testing before I get it correctly committed to the SVN trunk.
== More details ==
Craig Rasmussen and I have been working with the MPI-3 Fortran WG and Fortran J3 committees for a long, long time to make a prototype MPI-3 Fortran bindings implementation. We think we're at a stable enough state to bring this stuff back to the trunk, with the goal of including it in OMPI v1.7.
Special thanks go out to everyone who has been incredibly patient and helpful to us in this journey:
* Rolf Rabenseifner/HLRS (mastermind/genius behind the entire MPI-3 Fortran effort)
* The Fortran J3 committee
* Tobias Burnus/gfortran
* Tony !Goetz/Absoft
* Terry !Donte/Oracle
* ...and probably others whom I'm forgetting :-(
There's still opportunities for optimization in the mpi_f08 implementation, but by and large, it is as far along as it can be until Fortran compilers start implementing the new F08 dimension(..) syntax.
Note that gfortran is currently unsupported for the mpi_f08 module and the new mpi module. gfortran users will a) fall back to the same mpi module implementation that is in OMPI v1.5.x, and b) not get the new mpi_f08 module. The gfortran maintainers are actively working hard to add the necessary features to support both the new mpi_f08 module and the new mpi module implementations. This will take some time.
As mentioned above, ompi/mpi/f77 and ompi/mpi/f90 no longer exist. All the fortran bindings implementations have been collated under ompi/mpi/fortran; each implementation has its own subdirectory:
{{{
ompi/mpi/fortran/
base/ - glue code
mpif-h/ - what used to be ompi/mpi/f77
use-mpi-tkr/ - what used to be ompi/mpi/f90
use-mpi-ignore-tkr/ - new mpi module implementation
use-mpi-f08/ - new mpi_f08 module implementation
}}}
There's also a prototype 6-function-MPI implementation under use-mpi-f08-desc that emulates the new F08 dimension(..) syntax that isn't fully available in Fortran compilers yet. We did that to prove it to ourselves that it could be done once the compilers fully support it. This directory/implementation will likely eventually replace the use-mpi-f08 version.
Other things that were done:
* ompi_info grew a few new output fields to describe what level of Fortran support is included
* Existing Fortran examples in examples/ were renamed; new mpi_f08 examples were added
* The old Fortran MPI libraries were renamed:
* libmpi_f77 -> libmpi_mpifh
* libmpi_f90 -> libmpi_usempi
* The configury for Fortran was consolidated and significantly slimmed down. Note that the F77 env variable is now IGNORED for configure; you should only use FC. Example:
{{{
shell$ ./configure CC=icc CXX=icpc FC=ifort ...
}}}
All of this work was done in a Mercurial branch off the SVN trunk, and hosted at Bitbucket. This branch has got to be one of OMPI's longest-running branches. Its first commit was Tue Apr 07 23:01:46 2009 -0400 -- it's over 3 years old! :-) We think we've pulled in all relevant changes from the OMPI trunk (e.g., Fortran implementations of the new MPI-3 MPROBE stuff for mpif.h, use mpi, and use mpi_f08, and the recent Fujitsu Fortran patches).
I anticipate some instability when we bring this stuff into the trunk, simply because it touches a LOT of code in the MPI layer in the OMPI code base. We'll try our best to make it as pain-free as possible, but please bear with us when it is committed.
This commit was SVN r26283.
2012-04-18 15:57:29 +00:00
|
|
|
- MPI Fortran API support has been completely overhauled since the
|
2015-04-01 15:40:42 -07:00
|
|
|
Open MPI v1.5/v1.6 series.
|
== Highlights ==
1. New mpifort wrapper compiler: you can utilize mpif.h, use mpi, and use mpi_f08 through this one wrapper compiler
1. mpif77 and mpif90 still exist, but are sym links to mpifort and may be removed in a future release
1. The mpi module has been re-implemented and is significantly "mo' bettah"
1. The mpi_f08 module offers many, many improvements over mpif.h and the mpi module
This stuff is coming from a VERY long-lived mercurial branch (3 years!); it'll almost certainly take a few SVN commits and a bunch of testing before I get it correctly committed to the SVN trunk.
== More details ==
Craig Rasmussen and I have been working with the MPI-3 Fortran WG and Fortran J3 committees for a long, long time to make a prototype MPI-3 Fortran bindings implementation. We think we're at a stable enough state to bring this stuff back to the trunk, with the goal of including it in OMPI v1.7.
Special thanks go out to everyone who has been incredibly patient and helpful to us in this journey:
* Rolf Rabenseifner/HLRS (mastermind/genius behind the entire MPI-3 Fortran effort)
* The Fortran J3 committee
* Tobias Burnus/gfortran
* Tony !Goetz/Absoft
* Terry !Donte/Oracle
* ...and probably others whom I'm forgetting :-(
There's still opportunities for optimization in the mpi_f08 implementation, but by and large, it is as far along as it can be until Fortran compilers start implementing the new F08 dimension(..) syntax.
Note that gfortran is currently unsupported for the mpi_f08 module and the new mpi module. gfortran users will a) fall back to the same mpi module implementation that is in OMPI v1.5.x, and b) not get the new mpi_f08 module. The gfortran maintainers are actively working hard to add the necessary features to support both the new mpi_f08 module and the new mpi module implementations. This will take some time.
As mentioned above, ompi/mpi/f77 and ompi/mpi/f90 no longer exist. All the fortran bindings implementations have been collated under ompi/mpi/fortran; each implementation has its own subdirectory:
{{{
ompi/mpi/fortran/
base/ - glue code
mpif-h/ - what used to be ompi/mpi/f77
use-mpi-tkr/ - what used to be ompi/mpi/f90
use-mpi-ignore-tkr/ - new mpi module implementation
use-mpi-f08/ - new mpi_f08 module implementation
}}}
There's also a prototype 6-function-MPI implementation under use-mpi-f08-desc that emulates the new F08 dimension(..) syntax that isn't fully available in Fortran compilers yet. We did that to prove it to ourselves that it could be done once the compilers fully support it. This directory/implementation will likely eventually replace the use-mpi-f08 version.
Other things that were done:
* ompi_info grew a few new output fields to describe what level of Fortran support is included
* Existing Fortran examples in examples/ were renamed; new mpi_f08 examples were added
* The old Fortran MPI libraries were renamed:
* libmpi_f77 -> libmpi_mpifh
* libmpi_f90 -> libmpi_usempi
* The configury for Fortran was consolidated and significantly slimmed down. Note that the F77 env variable is now IGNORED for configure; you should only use FC. Example:
{{{
shell$ ./configure CC=icc CXX=icpc FC=ifort ...
}}}
All of this work was done in a Mercurial branch off the SVN trunk, and hosted at Bitbucket. This branch has got to be one of OMPI's longest-running branches. Its first commit was Tue Apr 07 23:01:46 2009 -0400 -- it's over 3 years old! :-) We think we've pulled in all relevant changes from the OMPI trunk (e.g., Fortran implementations of the new MPI-3 MPROBE stuff for mpif.h, use mpi, and use mpi_f08, and the recent Fujitsu Fortran patches).
I anticipate some instability when we bring this stuff into the trunk, simply because it touches a LOT of code in the MPI layer in the OMPI code base. We'll try our best to make it as pain-free as possible, but please bear with us when it is committed.
This commit was SVN r26283.
2012-04-18 15:57:29 +00:00
|
|
|
|
|
|
|
********************************************************************
|
|
|
|
********************************************************************
|
2014-03-19 20:50:28 +00:00
|
|
|
*** There is now only a single Fortran MPI wrapper compiler and a
|
|
|
|
*** single Fortran OSHMEM wrapper compiler: mpifort and oshfort,
|
|
|
|
*** respectively. mpif77 and mpif90 still exist, but they are
|
|
|
|
*** symbolic links to mpifort.
|
== Highlights ==
1. New mpifort wrapper compiler: you can utilize mpif.h, use mpi, and use mpi_f08 through this one wrapper compiler
1. mpif77 and mpif90 still exist, but are sym links to mpifort and may be removed in a future release
1. The mpi module has been re-implemented and is significantly "mo' bettah"
1. The mpi_f08 module offers many, many improvements over mpif.h and the mpi module
This stuff is coming from a VERY long-lived mercurial branch (3 years!); it'll almost certainly take a few SVN commits and a bunch of testing before I get it correctly committed to the SVN trunk.
== More details ==
Craig Rasmussen and I have been working with the MPI-3 Fortran WG and Fortran J3 committees for a long, long time to make a prototype MPI-3 Fortran bindings implementation. We think we're at a stable enough state to bring this stuff back to the trunk, with the goal of including it in OMPI v1.7.
Special thanks go out to everyone who has been incredibly patient and helpful to us in this journey:
* Rolf Rabenseifner/HLRS (mastermind/genius behind the entire MPI-3 Fortran effort)
* The Fortran J3 committee
* Tobias Burnus/gfortran
* Tony !Goetz/Absoft
* Terry !Donte/Oracle
* ...and probably others whom I'm forgetting :-(
There's still opportunities for optimization in the mpi_f08 implementation, but by and large, it is as far along as it can be until Fortran compilers start implementing the new F08 dimension(..) syntax.
Note that gfortran is currently unsupported for the mpi_f08 module and the new mpi module. gfortran users will a) fall back to the same mpi module implementation that is in OMPI v1.5.x, and b) not get the new mpi_f08 module. The gfortran maintainers are actively working hard to add the necessary features to support both the new mpi_f08 module and the new mpi module implementations. This will take some time.
As mentioned above, ompi/mpi/f77 and ompi/mpi/f90 no longer exist. All the fortran bindings implementations have been collated under ompi/mpi/fortran; each implementation has its own subdirectory:
{{{
ompi/mpi/fortran/
base/ - glue code
mpif-h/ - what used to be ompi/mpi/f77
use-mpi-tkr/ - what used to be ompi/mpi/f90
use-mpi-ignore-tkr/ - new mpi module implementation
use-mpi-f08/ - new mpi_f08 module implementation
}}}
There's also a prototype 6-function-MPI implementation under use-mpi-f08-desc that emulates the new F08 dimension(..) syntax that isn't fully available in Fortran compilers yet. We did that to prove it to ourselves that it could be done once the compilers fully support it. This directory/implementation will likely eventually replace the use-mpi-f08 version.
Other things that were done:
* ompi_info grew a few new output fields to describe what level of Fortran support is included
* Existing Fortran examples in examples/ were renamed; new mpi_f08 examples were added
* The old Fortran MPI libraries were renamed:
* libmpi_f77 -> libmpi_mpifh
* libmpi_f90 -> libmpi_usempi
* The configury for Fortran was consolidated and significantly slimmed down. Note that the F77 env variable is now IGNORED for configure; you should only use FC. Example:
{{{
shell$ ./configure CC=icc CXX=icpc FC=ifort ...
}}}
All of this work was done in a Mercurial branch off the SVN trunk, and hosted at Bitbucket. This branch has got to be one of OMPI's longest-running branches. Its first commit was Tue Apr 07 23:01:46 2009 -0400 -- it's over 3 years old! :-) We think we've pulled in all relevant changes from the OMPI trunk (e.g., Fortran implementations of the new MPI-3 MPROBE stuff for mpif.h, use mpi, and use mpi_f08, and the recent Fujitsu Fortran patches).
I anticipate some instability when we bring this stuff into the trunk, simply because it touches a LOT of code in the MPI layer in the OMPI code base. We'll try our best to make it as pain-free as possible, but please bear with us when it is committed.
This commit was SVN r26283.
2012-04-18 15:57:29 +00:00
|
|
|
********************************************************************
|
2013-11-07 17:14:28 +00:00
|
|
|
*** Similarly, Open MPI's configure script only recognizes the FC
|
== Highlights ==
1. New mpifort wrapper compiler: you can utilize mpif.h, use mpi, and use mpi_f08 through this one wrapper compiler
1. mpif77 and mpif90 still exist, but are sym links to mpifort and may be removed in a future release
1. The mpi module has been re-implemented and is significantly "mo' bettah"
1. The mpi_f08 module offers many, many improvements over mpif.h and the mpi module
This stuff is coming from a VERY long-lived mercurial branch (3 years!); it'll almost certainly take a few SVN commits and a bunch of testing before I get it correctly committed to the SVN trunk.
== More details ==
Craig Rasmussen and I have been working with the MPI-3 Fortran WG and Fortran J3 committees for a long, long time to make a prototype MPI-3 Fortran bindings implementation. We think we're at a stable enough state to bring this stuff back to the trunk, with the goal of including it in OMPI v1.7.
Special thanks go out to everyone who has been incredibly patient and helpful to us in this journey:
* Rolf Rabenseifner/HLRS (mastermind/genius behind the entire MPI-3 Fortran effort)
* The Fortran J3 committee
* Tobias Burnus/gfortran
* Tony !Goetz/Absoft
* Terry !Donte/Oracle
* ...and probably others whom I'm forgetting :-(
There's still opportunities for optimization in the mpi_f08 implementation, but by and large, it is as far along as it can be until Fortran compilers start implementing the new F08 dimension(..) syntax.
Note that gfortran is currently unsupported for the mpi_f08 module and the new mpi module. gfortran users will a) fall back to the same mpi module implementation that is in OMPI v1.5.x, and b) not get the new mpi_f08 module. The gfortran maintainers are actively working hard to add the necessary features to support both the new mpi_f08 module and the new mpi module implementations. This will take some time.
As mentioned above, ompi/mpi/f77 and ompi/mpi/f90 no longer exist. All the fortran bindings implementations have been collated under ompi/mpi/fortran; each implementation has its own subdirectory:
{{{
ompi/mpi/fortran/
base/ - glue code
mpif-h/ - what used to be ompi/mpi/f77
use-mpi-tkr/ - what used to be ompi/mpi/f90
use-mpi-ignore-tkr/ - new mpi module implementation
use-mpi-f08/ - new mpi_f08 module implementation
}}}
There's also a prototype 6-function-MPI implementation under use-mpi-f08-desc that emulates the new F08 dimension(..) syntax that isn't fully available in Fortran compilers yet. We did that to prove it to ourselves that it could be done once the compilers fully support it. This directory/implementation will likely eventually replace the use-mpi-f08 version.
Other things that were done:
* ompi_info grew a few new output fields to describe what level of Fortran support is included
* Existing Fortran examples in examples/ were renamed; new mpi_f08 examples were added
* The old Fortran MPI libraries were renamed:
* libmpi_f77 -> libmpi_mpifh
* libmpi_f90 -> libmpi_usempi
* The configury for Fortran was consolidated and significantly slimmed down. Note that the F77 env variable is now IGNORED for configure; you should only use FC. Example:
{{{
shell$ ./configure CC=icc CXX=icpc FC=ifort ...
}}}
All of this work was done in a Mercurial branch off the SVN trunk, and hosted at Bitbucket. This branch has got to be one of OMPI's longest-running branches. Its first commit was Tue Apr 07 23:01:46 2009 -0400 -- it's over 3 years old! :-) We think we've pulled in all relevant changes from the OMPI trunk (e.g., Fortran implementations of the new MPI-3 MPROBE stuff for mpif.h, use mpi, and use mpi_f08, and the recent Fujitsu Fortran patches).
I anticipate some instability when we bring this stuff into the trunk, simply because it touches a LOT of code in the MPI layer in the OMPI code base. We'll try our best to make it as pain-free as possible, but please bear with us when it is committed.
This commit was SVN r26283.
2012-04-18 15:57:29 +00:00
|
|
|
*** and FCFLAGS environment variables (to specify the Fortran
|
|
|
|
*** compiler and compiler flags, respectively). The F77 and FFLAGS
|
|
|
|
*** environment variables are IGNORED.
|
|
|
|
********************************************************************
|
|
|
|
********************************************************************
|
2015-04-01 15:40:42 -07:00
|
|
|
|
2014-01-24 21:00:00 +00:00
|
|
|
As a direct result, it is STRONGLY recommended that you specify a
|
|
|
|
Fortran compiler that uses file suffixes to determine Fortran code
|
|
|
|
layout (e.g., free form vs. fixed). For example, with some versions
|
|
|
|
of the IBM XLF compiler, it is preferable to use FC=xlf instead of
|
|
|
|
FC=xlf90, because xlf will automatically determine the difference
|
|
|
|
between free form and fixed Fortran source code.
|
|
|
|
|
2014-01-28 15:36:52 +00:00
|
|
|
However, many Fortran compilers allow specifying additional
|
2014-01-24 21:00:00 +00:00
|
|
|
command-line arguments to indicate which Fortran dialect to use.
|
|
|
|
For example, if FC=xlf90, you may need to use "mpifort --qfixed ..."
|
|
|
|
to compile fixed format Fortran source files.
|
== Highlights ==
1. New mpifort wrapper compiler: you can utilize mpif.h, use mpi, and use mpi_f08 through this one wrapper compiler
1. mpif77 and mpif90 still exist, but are sym links to mpifort and may be removed in a future release
1. The mpi module has been re-implemented and is significantly "mo' bettah"
1. The mpi_f08 module offers many, many improvements over mpif.h and the mpi module
This stuff is coming from a VERY long-lived mercurial branch (3 years!); it'll almost certainly take a few SVN commits and a bunch of testing before I get it correctly committed to the SVN trunk.
== More details ==
Craig Rasmussen and I have been working with the MPI-3 Fortran WG and Fortran J3 committees for a long, long time to make a prototype MPI-3 Fortran bindings implementation. We think we're at a stable enough state to bring this stuff back to the trunk, with the goal of including it in OMPI v1.7.
Special thanks go out to everyone who has been incredibly patient and helpful to us in this journey:
* Rolf Rabenseifner/HLRS (mastermind/genius behind the entire MPI-3 Fortran effort)
* The Fortran J3 committee
* Tobias Burnus/gfortran
* Tony !Goetz/Absoft
* Terry !Donte/Oracle
* ...and probably others whom I'm forgetting :-(
There's still opportunities for optimization in the mpi_f08 implementation, but by and large, it is as far along as it can be until Fortran compilers start implementing the new F08 dimension(..) syntax.
Note that gfortran is currently unsupported for the mpi_f08 module and the new mpi module. gfortran users will a) fall back to the same mpi module implementation that is in OMPI v1.5.x, and b) not get the new mpi_f08 module. The gfortran maintainers are actively working hard to add the necessary features to support both the new mpi_f08 module and the new mpi module implementations. This will take some time.
As mentioned above, ompi/mpi/f77 and ompi/mpi/f90 no longer exist. All the fortran bindings implementations have been collated under ompi/mpi/fortran; each implementation has its own subdirectory:
{{{
ompi/mpi/fortran/
base/ - glue code
mpif-h/ - what used to be ompi/mpi/f77
use-mpi-tkr/ - what used to be ompi/mpi/f90
use-mpi-ignore-tkr/ - new mpi module implementation
use-mpi-f08/ - new mpi_f08 module implementation
}}}
There's also a prototype 6-function-MPI implementation under use-mpi-f08-desc that emulates the new F08 dimension(..) syntax that isn't fully available in Fortran compilers yet. We did that to prove it to ourselves that it could be done once the compilers fully support it. This directory/implementation will likely eventually replace the use-mpi-f08 version.
Other things that were done:
* ompi_info grew a few new output fields to describe what level of Fortran support is included
* Existing Fortran examples in examples/ were renamed; new mpi_f08 examples were added
* The old Fortran MPI libraries were renamed:
* libmpi_f77 -> libmpi_mpifh
* libmpi_f90 -> libmpi_usempi
* The configury for Fortran was consolidated and significantly slimmed down. Note that the F77 env variable is now IGNORED for configure; you should only use FC. Example:
{{{
shell$ ./configure CC=icc CXX=icpc FC=ifort ...
}}}
All of this work was done in a Mercurial branch off the SVN trunk, and hosted at Bitbucket. This branch has got to be one of OMPI's longest-running branches. Its first commit was Tue Apr 07 23:01:46 2009 -0400 -- it's over 3 years old! :-) We think we've pulled in all relevant changes from the OMPI trunk (e.g., Fortran implementations of the new MPI-3 MPROBE stuff for mpif.h, use mpi, and use mpi_f08, and the recent Fujitsu Fortran patches).
I anticipate some instability when we bring this stuff into the trunk, simply because it touches a LOT of code in the MPI layer in the OMPI code base. We'll try our best to make it as pain-free as possible, but please bear with us when it is committed.
This commit was SVN r26283.
2012-04-18 15:57:29 +00:00
|
|
|
|
2015-04-01 15:40:42 -07:00
|
|
|
You can use either ompi_info or oshmem_info to see with which Fortran
|
|
|
|
compiler Open MPI was configured and compiled.
|
== Highlights ==
1. New mpifort wrapper compiler: you can utilize mpif.h, use mpi, and use mpi_f08 through this one wrapper compiler
1. mpif77 and mpif90 still exist, but are sym links to mpifort and may be removed in a future release
1. The mpi module has been re-implemented and is significantly "mo' bettah"
1. The mpi_f08 module offers many, many improvements over mpif.h and the mpi module
This stuff is coming from a VERY long-lived mercurial branch (3 years!); it'll almost certainly take a few SVN commits and a bunch of testing before I get it correctly committed to the SVN trunk.
== More details ==
Craig Rasmussen and I have been working with the MPI-3 Fortran WG and Fortran J3 committees for a long, long time to make a prototype MPI-3 Fortran bindings implementation. We think we're at a stable enough state to bring this stuff back to the trunk, with the goal of including it in OMPI v1.7.
Special thanks go out to everyone who has been incredibly patient and helpful to us in this journey:
* Rolf Rabenseifner/HLRS (mastermind/genius behind the entire MPI-3 Fortran effort)
* The Fortran J3 committee
* Tobias Burnus/gfortran
* Tony !Goetz/Absoft
* Terry !Donte/Oracle
* ...and probably others whom I'm forgetting :-(
There's still opportunities for optimization in the mpi_f08 implementation, but by and large, it is as far along as it can be until Fortran compilers start implementing the new F08 dimension(..) syntax.
Note that gfortran is currently unsupported for the mpi_f08 module and the new mpi module. gfortran users will a) fall back to the same mpi module implementation that is in OMPI v1.5.x, and b) not get the new mpi_f08 module. The gfortran maintainers are actively working hard to add the necessary features to support both the new mpi_f08 module and the new mpi module implementations. This will take some time.
As mentioned above, ompi/mpi/f77 and ompi/mpi/f90 no longer exist. All the fortran bindings implementations have been collated under ompi/mpi/fortran; each implementation has its own subdirectory:
{{{
ompi/mpi/fortran/
base/ - glue code
mpif-h/ - what used to be ompi/mpi/f77
use-mpi-tkr/ - what used to be ompi/mpi/f90
use-mpi-ignore-tkr/ - new mpi module implementation
use-mpi-f08/ - new mpi_f08 module implementation
}}}
There's also a prototype 6-function-MPI implementation under use-mpi-f08-desc that emulates the new F08 dimension(..) syntax that isn't fully available in Fortran compilers yet. We did that to prove it to ourselves that it could be done once the compilers fully support it. This directory/implementation will likely eventually replace the use-mpi-f08 version.
Other things that were done:
* ompi_info grew a few new output fields to describe what level of Fortran support is included
* Existing Fortran examples in examples/ were renamed; new mpi_f08 examples were added
* The old Fortran MPI libraries were renamed:
* libmpi_f77 -> libmpi_mpifh
* libmpi_f90 -> libmpi_usempi
* The configury for Fortran was consolidated and significantly slimmed down. Note that the F77 env variable is now IGNORED for configure; you should only use FC. Example:
{{{
shell$ ./configure CC=icc CXX=icpc FC=ifort ...
}}}
All of this work was done in a Mercurial branch off the SVN trunk, and hosted at Bitbucket. This branch has got to be one of OMPI's longest-running branches. Its first commit was Tue Apr 07 23:01:46 2009 -0400 -- it's over 3 years old! :-) We think we've pulled in all relevant changes from the OMPI trunk (e.g., Fortran implementations of the new MPI-3 MPROBE stuff for mpif.h, use mpi, and use mpi_f08, and the recent Fujitsu Fortran patches).
I anticipate some instability when we bring this stuff into the trunk, simply because it touches a LOT of code in the MPI layer in the OMPI code base. We'll try our best to make it as pain-free as possible, but please bear with us when it is committed.
This commit was SVN r26283.
2012-04-18 15:57:29 +00:00
|
|
|
|
|
|
|
There are up to three sets of Fortran MPI bindings that may be
|
2013-11-07 17:14:28 +00:00
|
|
|
provided depending on your Fortran compiler):
|
== Highlights ==
1. New mpifort wrapper compiler: you can utilize mpif.h, use mpi, and use mpi_f08 through this one wrapper compiler
1. mpif77 and mpif90 still exist, but are sym links to mpifort and may be removed in a future release
1. The mpi module has been re-implemented and is significantly "mo' bettah"
1. The mpi_f08 module offers many, many improvements over mpif.h and the mpi module
This stuff is coming from a VERY long-lived mercurial branch (3 years!); it'll almost certainly take a few SVN commits and a bunch of testing before I get it correctly committed to the SVN trunk.
== More details ==
Craig Rasmussen and I have been working with the MPI-3 Fortran WG and Fortran J3 committees for a long, long time to make a prototype MPI-3 Fortran bindings implementation. We think we're at a stable enough state to bring this stuff back to the trunk, with the goal of including it in OMPI v1.7.
Special thanks go out to everyone who has been incredibly patient and helpful to us in this journey:
* Rolf Rabenseifner/HLRS (mastermind/genius behind the entire MPI-3 Fortran effort)
* The Fortran J3 committee
* Tobias Burnus/gfortran
* Tony !Goetz/Absoft
* Terry !Donte/Oracle
* ...and probably others whom I'm forgetting :-(
There's still opportunities for optimization in the mpi_f08 implementation, but by and large, it is as far along as it can be until Fortran compilers start implementing the new F08 dimension(..) syntax.
Note that gfortran is currently unsupported for the mpi_f08 module and the new mpi module. gfortran users will a) fall back to the same mpi module implementation that is in OMPI v1.5.x, and b) not get the new mpi_f08 module. The gfortran maintainers are actively working hard to add the necessary features to support both the new mpi_f08 module and the new mpi module implementations. This will take some time.
As mentioned above, ompi/mpi/f77 and ompi/mpi/f90 no longer exist. All the fortran bindings implementations have been collated under ompi/mpi/fortran; each implementation has its own subdirectory:
{{{
ompi/mpi/fortran/
base/ - glue code
mpif-h/ - what used to be ompi/mpi/f77
use-mpi-tkr/ - what used to be ompi/mpi/f90
use-mpi-ignore-tkr/ - new mpi module implementation
use-mpi-f08/ - new mpi_f08 module implementation
}}}
There's also a prototype 6-function-MPI implementation under use-mpi-f08-desc that emulates the new F08 dimension(..) syntax that isn't fully available in Fortran compilers yet. We did that to prove it to ourselves that it could be done once the compilers fully support it. This directory/implementation will likely eventually replace the use-mpi-f08 version.
Other things that were done:
* ompi_info grew a few new output fields to describe what level of Fortran support is included
* Existing Fortran examples in examples/ were renamed; new mpi_f08 examples were added
* The old Fortran MPI libraries were renamed:
* libmpi_f77 -> libmpi_mpifh
* libmpi_f90 -> libmpi_usempi
* The configury for Fortran was consolidated and significantly slimmed down. Note that the F77 env variable is now IGNORED for configure; you should only use FC. Example:
{{{
shell$ ./configure CC=icc CXX=icpc FC=ifort ...
}}}
All of this work was done in a Mercurial branch off the SVN trunk, and hosted at Bitbucket. This branch has got to be one of OMPI's longest-running branches. Its first commit was Tue Apr 07 23:01:46 2009 -0400 -- it's over 3 years old! :-) We think we've pulled in all relevant changes from the OMPI trunk (e.g., Fortran implementations of the new MPI-3 MPROBE stuff for mpif.h, use mpi, and use mpi_f08, and the recent Fujitsu Fortran patches).
I anticipate some instability when we bring this stuff into the trunk, simply because it touches a LOT of code in the MPI layer in the OMPI code base. We'll try our best to make it as pain-free as possible, but please bear with us when it is committed.
This commit was SVN r26283.
2012-04-18 15:57:29 +00:00
|
|
|
|
|
|
|
- mpif.h: This is the first MPI Fortran interface that was defined
|
|
|
|
in MPI-1. It is a file that is included in Fortran source code.
|
|
|
|
Open MPI's mpif.h does not declare any MPI subroutines; they are
|
|
|
|
all implicit.
|
|
|
|
|
|
|
|
- mpi module: The mpi module file was added in MPI-2. It provides
|
|
|
|
strong compile-time parameter type checking for MPI subroutines.
|
|
|
|
|
|
|
|
- mpi_f08 module: The mpi_f08 module was added in MPI-3. It
|
|
|
|
provides many advantages over the mpif.h file and mpi module. For
|
|
|
|
example, MPI handles have distinct types (vs. all being integers).
|
|
|
|
See the MPI-3 document for more details.
|
|
|
|
|
|
|
|
*** The mpi_f08 module is STRONGLY is recommended for all new MPI
|
|
|
|
Fortran subroutines and applications. Note that the mpi_f08
|
|
|
|
module can be used in conjunction with the other two Fortran
|
|
|
|
MPI bindings in the same application (only one binding can be
|
|
|
|
used per subroutine/function, however). Full interoperability
|
|
|
|
between mpif.h/mpi module and mpi_f08 module MPI handle types
|
|
|
|
is provided, allowing mpi_f08 to be used in new subroutines in
|
|
|
|
legacy MPI applications.
|
|
|
|
|
2015-04-01 15:40:42 -07:00
|
|
|
Per the OSHMEM specification, there is only one Fortran OSHMEM binding
|
2013-11-07 17:14:28 +00:00
|
|
|
provided:
|
|
|
|
|
|
|
|
- shmem.fh: All Fortran OpenSHMEM programs **should** include 'shmem.fh',
|
|
|
|
and Fortran OSHMEM programs that use constants defined by OpenSHMEM
|
2015-04-01 15:40:42 -07:00
|
|
|
**MUST** include 'shmem.fh'.
|
2013-11-07 17:14:28 +00:00
|
|
|
|
== Highlights ==
1. New mpifort wrapper compiler: you can utilize mpif.h, use mpi, and use mpi_f08 through this one wrapper compiler
1. mpif77 and mpif90 still exist, but are sym links to mpifort and may be removed in a future release
1. The mpi module has been re-implemented and is significantly "mo' bettah"
1. The mpi_f08 module offers many, many improvements over mpif.h and the mpi module
This stuff is coming from a VERY long-lived mercurial branch (3 years!); it'll almost certainly take a few SVN commits and a bunch of testing before I get it correctly committed to the SVN trunk.
== More details ==
Craig Rasmussen and I have been working with the MPI-3 Fortran WG and Fortran J3 committees for a long, long time to make a prototype MPI-3 Fortran bindings implementation. We think we're at a stable enough state to bring this stuff back to the trunk, with the goal of including it in OMPI v1.7.
Special thanks go out to everyone who has been incredibly patient and helpful to us in this journey:
* Rolf Rabenseifner/HLRS (mastermind/genius behind the entire MPI-3 Fortran effort)
* The Fortran J3 committee
* Tobias Burnus/gfortran
* Tony !Goetz/Absoft
* Terry !Donte/Oracle
* ...and probably others whom I'm forgetting :-(
There's still opportunities for optimization in the mpi_f08 implementation, but by and large, it is as far along as it can be until Fortran compilers start implementing the new F08 dimension(..) syntax.
Note that gfortran is currently unsupported for the mpi_f08 module and the new mpi module. gfortran users will a) fall back to the same mpi module implementation that is in OMPI v1.5.x, and b) not get the new mpi_f08 module. The gfortran maintainers are actively working hard to add the necessary features to support both the new mpi_f08 module and the new mpi module implementations. This will take some time.
As mentioned above, ompi/mpi/f77 and ompi/mpi/f90 no longer exist. All the fortran bindings implementations have been collated under ompi/mpi/fortran; each implementation has its own subdirectory:
{{{
ompi/mpi/fortran/
base/ - glue code
mpif-h/ - what used to be ompi/mpi/f77
use-mpi-tkr/ - what used to be ompi/mpi/f90
use-mpi-ignore-tkr/ - new mpi module implementation
use-mpi-f08/ - new mpi_f08 module implementation
}}}
There's also a prototype 6-function-MPI implementation under use-mpi-f08-desc that emulates the new F08 dimension(..) syntax that isn't fully available in Fortran compilers yet. We did that to prove it to ourselves that it could be done once the compilers fully support it. This directory/implementation will likely eventually replace the use-mpi-f08 version.
Other things that were done:
* ompi_info grew a few new output fields to describe what level of Fortran support is included
* Existing Fortran examples in examples/ were renamed; new mpi_f08 examples were added
* The old Fortran MPI libraries were renamed:
* libmpi_f77 -> libmpi_mpifh
* libmpi_f90 -> libmpi_usempi
* The configury for Fortran was consolidated and significantly slimmed down. Note that the F77 env variable is now IGNORED for configure; you should only use FC. Example:
{{{
shell$ ./configure CC=icc CXX=icpc FC=ifort ...
}}}
All of this work was done in a Mercurial branch off the SVN trunk, and hosted at Bitbucket. This branch has got to be one of OMPI's longest-running branches. Its first commit was Tue Apr 07 23:01:46 2009 -0400 -- it's over 3 years old! :-) We think we've pulled in all relevant changes from the OMPI trunk (e.g., Fortran implementations of the new MPI-3 MPROBE stuff for mpif.h, use mpi, and use mpi_f08, and the recent Fujitsu Fortran patches).
I anticipate some instability when we bring this stuff into the trunk, simply because it touches a LOT of code in the MPI layer in the OMPI code base. We'll try our best to make it as pain-free as possible, but please bear with us when it is committed.
This commit was SVN r26283.
2012-04-18 15:57:29 +00:00
|
|
|
The following notes apply to the above-listed Fortran bindings:
|
|
|
|
|
Fortran: Fix MPI_SIZEOF. What a disaster. :-(
What started as a simple ticket ended up reaching the way up to the
MPI Forum.
It turns out that we are supposed to have MPI_SIZEOF for all Fortran
interfaces: mpif.h, the mpi module, and the mpi_f08 module.
It further turns out that to properly support MPI_SIZEOF, your Fortran
compiler *has* support the INTERFACE keyword and ISO_FORTRAN_ENV. We
can't use "ignore TKR" functionality, because the whole point of
MPI_SIZEOF is that the implementation knows what type was passed to it
("ignore TKR" functionality, by definition, throws that information
away). Hence, we have to have an MPI_SIZEOF interface+implementation
for all intrinsic types, kinds, and ranks.
This commit therefore adds a perl script that generates both the
interfaces and implementations for MPI_SIZEOF in each of mpif.h, the
mpi module, and mpi_f08 module (yay consolidation!).
The perl script uses the results of some new configure tests:
* check if the Fortran compiler supports the INTERFACE keyword
* check if the Fortran compiler supports ISO_FORTRAN_ENV
* find the max array rank (i.e., dimension) that the compiler supports
If the Fortran compiler supports both INTERFACE and ISO_FORTRAN_ENV,
then we'll build the MPI_SIZEOF interfaces. If not, we'll skip
MPI_SIZEOF in mpif.h and the mpi module. Note that we won't build the
mpi_f08 module -- to include the MPI_SIZEOF interfaces -- if the
Fortran compiler doesn't support INTERFACE, ISO_FORTRAN_ENV, and a
whole bunch of ther modern Fortran stuff.
Since MPI_SIZEOF interfaces are now generated by the perl script, this
commit also removes all the old MPI_SIZEOF implementations (which were
laden with a zillion #if blocks).
cmr=v1.8.3
This commit was SVN r32764.
2014-09-19 13:44:52 +00:00
|
|
|
- All Fortran compilers support the mpif.h/shmem.fh-based bindings,
|
|
|
|
with one exception: the MPI_SIZEOF interfaces will only be present
|
|
|
|
when Open MPI is built with a Fortran compiler that support the
|
|
|
|
INTERFACE keyword and ISO_FORTRAN_ENV. Most notably, this
|
|
|
|
excludes the GNU Fortran compiler suite before version 4.9.
|
2014-01-28 15:36:52 +00:00
|
|
|
|
|
|
|
- The level of support provided by the mpi module is based on your
|
|
|
|
Fortran compiler.
|
|
|
|
|
|
|
|
If Open MPI is built with a non-GNU Fortran compiler, or if Open
|
|
|
|
MPI is built with the GNU Fortran compiler >= v4.9, all MPI
|
|
|
|
subroutines will be prototyped in the mpi module. All calls to
|
|
|
|
MPI subroutines will therefore have their parameter types checked
|
|
|
|
at compile time.
|
|
|
|
|
|
|
|
If Open MPI is built with an old gfortran (i.e., < v4.9), a
|
|
|
|
limited "mpi" module will be built. Due to the limitations of
|
|
|
|
these compilers, and per guidance from the MPI-3 specification,
|
|
|
|
all MPI subroutines with "choice" buffers are specifically *not*
|
|
|
|
included in the "mpi" module, and their parameters will not be
|
|
|
|
checked at compile time. Specifically, all MPI subroutines with
|
|
|
|
no "choice" buffers are prototyped and will receive strong
|
|
|
|
parameter type checking at run-time (e.g., MPI_INIT,
|
|
|
|
MPI_COMM_RANK, etc.).
|
|
|
|
|
Fortran: Fix MPI_SIZEOF. What a disaster. :-(
What started as a simple ticket ended up reaching the way up to the
MPI Forum.
It turns out that we are supposed to have MPI_SIZEOF for all Fortran
interfaces: mpif.h, the mpi module, and the mpi_f08 module.
It further turns out that to properly support MPI_SIZEOF, your Fortran
compiler *has* support the INTERFACE keyword and ISO_FORTRAN_ENV. We
can't use "ignore TKR" functionality, because the whole point of
MPI_SIZEOF is that the implementation knows what type was passed to it
("ignore TKR" functionality, by definition, throws that information
away). Hence, we have to have an MPI_SIZEOF interface+implementation
for all intrinsic types, kinds, and ranks.
This commit therefore adds a perl script that generates both the
interfaces and implementations for MPI_SIZEOF in each of mpif.h, the
mpi module, and mpi_f08 module (yay consolidation!).
The perl script uses the results of some new configure tests:
* check if the Fortran compiler supports the INTERFACE keyword
* check if the Fortran compiler supports ISO_FORTRAN_ENV
* find the max array rank (i.e., dimension) that the compiler supports
If the Fortran compiler supports both INTERFACE and ISO_FORTRAN_ENV,
then we'll build the MPI_SIZEOF interfaces. If not, we'll skip
MPI_SIZEOF in mpif.h and the mpi module. Note that we won't build the
mpi_f08 module -- to include the MPI_SIZEOF interfaces -- if the
Fortran compiler doesn't support INTERFACE, ISO_FORTRAN_ENV, and a
whole bunch of ther modern Fortran stuff.
Since MPI_SIZEOF interfaces are now generated by the perl script, this
commit also removes all the old MPI_SIZEOF implementations (which were
laden with a zillion #if blocks).
cmr=v1.8.3
This commit was SVN r32764.
2014-09-19 13:44:52 +00:00
|
|
|
Similar to the mpif.h interface, MPI_SIZEOF is only supported on
|
|
|
|
Fortran compilers that support INTERFACE and ISO_FORTRAN_ENV.
|
|
|
|
|
== Highlights ==
1. New mpifort wrapper compiler: you can utilize mpif.h, use mpi, and use mpi_f08 through this one wrapper compiler
1. mpif77 and mpif90 still exist, but are sym links to mpifort and may be removed in a future release
1. The mpi module has been re-implemented and is significantly "mo' bettah"
1. The mpi_f08 module offers many, many improvements over mpif.h and the mpi module
This stuff is coming from a VERY long-lived mercurial branch (3 years!); it'll almost certainly take a few SVN commits and a bunch of testing before I get it correctly committed to the SVN trunk.
== More details ==
Craig Rasmussen and I have been working with the MPI-3 Fortran WG and Fortran J3 committees for a long, long time to make a prototype MPI-3 Fortran bindings implementation. We think we're at a stable enough state to bring this stuff back to the trunk, with the goal of including it in OMPI v1.7.
Special thanks go out to everyone who has been incredibly patient and helpful to us in this journey:
* Rolf Rabenseifner/HLRS (mastermind/genius behind the entire MPI-3 Fortran effort)
* The Fortran J3 committee
* Tobias Burnus/gfortran
* Tony !Goetz/Absoft
* Terry !Donte/Oracle
* ...and probably others whom I'm forgetting :-(
There's still opportunities for optimization in the mpi_f08 implementation, but by and large, it is as far along as it can be until Fortran compilers start implementing the new F08 dimension(..) syntax.
Note that gfortran is currently unsupported for the mpi_f08 module and the new mpi module. gfortran users will a) fall back to the same mpi module implementation that is in OMPI v1.5.x, and b) not get the new mpi_f08 module. The gfortran maintainers are actively working hard to add the necessary features to support both the new mpi_f08 module and the new mpi module implementations. This will take some time.
As mentioned above, ompi/mpi/f77 and ompi/mpi/f90 no longer exist. All the fortran bindings implementations have been collated under ompi/mpi/fortran; each implementation has its own subdirectory:
{{{
ompi/mpi/fortran/
base/ - glue code
mpif-h/ - what used to be ompi/mpi/f77
use-mpi-tkr/ - what used to be ompi/mpi/f90
use-mpi-ignore-tkr/ - new mpi module implementation
use-mpi-f08/ - new mpi_f08 module implementation
}}}
There's also a prototype 6-function-MPI implementation under use-mpi-f08-desc that emulates the new F08 dimension(..) syntax that isn't fully available in Fortran compilers yet. We did that to prove it to ourselves that it could be done once the compilers fully support it. This directory/implementation will likely eventually replace the use-mpi-f08 version.
Other things that were done:
* ompi_info grew a few new output fields to describe what level of Fortran support is included
* Existing Fortran examples in examples/ were renamed; new mpi_f08 examples were added
* The old Fortran MPI libraries were renamed:
* libmpi_f77 -> libmpi_mpifh
* libmpi_f90 -> libmpi_usempi
* The configury for Fortran was consolidated and significantly slimmed down. Note that the F77 env variable is now IGNORED for configure; you should only use FC. Example:
{{{
shell$ ./configure CC=icc CXX=icpc FC=ifort ...
}}}
All of this work was done in a Mercurial branch off the SVN trunk, and hosted at Bitbucket. This branch has got to be one of OMPI's longest-running branches. Its first commit was Tue Apr 07 23:01:46 2009 -0400 -- it's over 3 years old! :-) We think we've pulled in all relevant changes from the OMPI trunk (e.g., Fortran implementations of the new MPI-3 MPROBE stuff for mpif.h, use mpi, and use mpi_f08, and the recent Fujitsu Fortran patches).
I anticipate some instability when we bring this stuff into the trunk, simply because it touches a LOT of code in the MPI layer in the OMPI code base. We'll try our best to make it as pain-free as possible, but please bear with us when it is committed.
This commit was SVN r26283.
2012-04-18 15:57:29 +00:00
|
|
|
- The mpi_f08 module is new and has been tested with the Intel
|
2014-04-19 00:30:38 +00:00
|
|
|
Fortran compiler and gfortran >= 4.9. Other modern Fortran
|
|
|
|
compilers may also work (but are, as yet, only lightly tested).
|
|
|
|
It is expected that this support will mature over time.
|
== Highlights ==
1. New mpifort wrapper compiler: you can utilize mpif.h, use mpi, and use mpi_f08 through this one wrapper compiler
1. mpif77 and mpif90 still exist, but are sym links to mpifort and may be removed in a future release
1. The mpi module has been re-implemented and is significantly "mo' bettah"
1. The mpi_f08 module offers many, many improvements over mpif.h and the mpi module
This stuff is coming from a VERY long-lived mercurial branch (3 years!); it'll almost certainly take a few SVN commits and a bunch of testing before I get it correctly committed to the SVN trunk.
== More details ==
Craig Rasmussen and I have been working with the MPI-3 Fortran WG and Fortran J3 committees for a long, long time to make a prototype MPI-3 Fortran bindings implementation. We think we're at a stable enough state to bring this stuff back to the trunk, with the goal of including it in OMPI v1.7.
Special thanks go out to everyone who has been incredibly patient and helpful to us in this journey:
* Rolf Rabenseifner/HLRS (mastermind/genius behind the entire MPI-3 Fortran effort)
* The Fortran J3 committee
* Tobias Burnus/gfortran
* Tony !Goetz/Absoft
* Terry !Donte/Oracle
* ...and probably others whom I'm forgetting :-(
There's still opportunities for optimization in the mpi_f08 implementation, but by and large, it is as far along as it can be until Fortran compilers start implementing the new F08 dimension(..) syntax.
Note that gfortran is currently unsupported for the mpi_f08 module and the new mpi module. gfortran users will a) fall back to the same mpi module implementation that is in OMPI v1.5.x, and b) not get the new mpi_f08 module. The gfortran maintainers are actively working hard to add the necessary features to support both the new mpi_f08 module and the new mpi module implementations. This will take some time.
As mentioned above, ompi/mpi/f77 and ompi/mpi/f90 no longer exist. All the fortran bindings implementations have been collated under ompi/mpi/fortran; each implementation has its own subdirectory:
{{{
ompi/mpi/fortran/
base/ - glue code
mpif-h/ - what used to be ompi/mpi/f77
use-mpi-tkr/ - what used to be ompi/mpi/f90
use-mpi-ignore-tkr/ - new mpi module implementation
use-mpi-f08/ - new mpi_f08 module implementation
}}}
There's also a prototype 6-function-MPI implementation under use-mpi-f08-desc that emulates the new F08 dimension(..) syntax that isn't fully available in Fortran compilers yet. We did that to prove it to ourselves that it could be done once the compilers fully support it. This directory/implementation will likely eventually replace the use-mpi-f08 version.
Other things that were done:
* ompi_info grew a few new output fields to describe what level of Fortran support is included
* Existing Fortran examples in examples/ were renamed; new mpi_f08 examples were added
* The old Fortran MPI libraries were renamed:
* libmpi_f77 -> libmpi_mpifh
* libmpi_f90 -> libmpi_usempi
* The configury for Fortran was consolidated and significantly slimmed down. Note that the F77 env variable is now IGNORED for configure; you should only use FC. Example:
{{{
shell$ ./configure CC=icc CXX=icpc FC=ifort ...
}}}
All of this work was done in a Mercurial branch off the SVN trunk, and hosted at Bitbucket. This branch has got to be one of OMPI's longest-running branches. Its first commit was Tue Apr 07 23:01:46 2009 -0400 -- it's over 3 years old! :-) We think we've pulled in all relevant changes from the OMPI trunk (e.g., Fortran implementations of the new MPI-3 MPROBE stuff for mpif.h, use mpi, and use mpi_f08, and the recent Fujitsu Fortran patches).
I anticipate some instability when we bring this stuff into the trunk, simply because it touches a LOT of code in the MPI layer in the OMPI code base. We'll try our best to make it as pain-free as possible, but please bear with us when it is committed.
This commit was SVN r26283.
2012-04-18 15:57:29 +00:00
|
|
|
|
2014-01-28 15:36:52 +00:00
|
|
|
Many older Fortran compilers do not provide enough modern Fortran
|
|
|
|
features to support the mpi_f08 module. For example, gfortran <
|
|
|
|
v4.9 does provide enough support for the mpi_f08 module.
|
2012-01-03 17:25:37 +00:00
|
|
|
|
Fortran: Fix MPI_SIZEOF. What a disaster. :-(
What started as a simple ticket ended up reaching the way up to the
MPI Forum.
It turns out that we are supposed to have MPI_SIZEOF for all Fortran
interfaces: mpif.h, the mpi module, and the mpi_f08 module.
It further turns out that to properly support MPI_SIZEOF, your Fortran
compiler *has* support the INTERFACE keyword and ISO_FORTRAN_ENV. We
can't use "ignore TKR" functionality, because the whole point of
MPI_SIZEOF is that the implementation knows what type was passed to it
("ignore TKR" functionality, by definition, throws that information
away). Hence, we have to have an MPI_SIZEOF interface+implementation
for all intrinsic types, kinds, and ranks.
This commit therefore adds a perl script that generates both the
interfaces and implementations for MPI_SIZEOF in each of mpif.h, the
mpi module, and mpi_f08 module (yay consolidation!).
The perl script uses the results of some new configure tests:
* check if the Fortran compiler supports the INTERFACE keyword
* check if the Fortran compiler supports ISO_FORTRAN_ENV
* find the max array rank (i.e., dimension) that the compiler supports
If the Fortran compiler supports both INTERFACE and ISO_FORTRAN_ENV,
then we'll build the MPI_SIZEOF interfaces. If not, we'll skip
MPI_SIZEOF in mpif.h and the mpi module. Note that we won't build the
mpi_f08 module -- to include the MPI_SIZEOF interfaces -- if the
Fortran compiler doesn't support INTERFACE, ISO_FORTRAN_ENV, and a
whole bunch of ther modern Fortran stuff.
Since MPI_SIZEOF interfaces are now generated by the perl script, this
commit also removes all the old MPI_SIZEOF implementations (which were
laden with a zillion #if blocks).
cmr=v1.8.3
This commit was SVN r32764.
2014-09-19 13:44:52 +00:00
|
|
|
You can examine the output of the following command to see all
|
|
|
|
the Fortran features that are/are not enabled in your Open MPI
|
|
|
|
installation:
|
|
|
|
|
|
|
|
shell$ ompi_info | grep -i fort
|
|
|
|
|
2012-01-03 17:25:37 +00:00
|
|
|
|
|
|
|
General Run-Time Support Notes
|
|
|
|
------------------------------
|
|
|
|
|
|
|
|
- The Open MPI installation must be in your PATH on all nodes (and
|
2015-04-01 15:40:42 -07:00
|
|
|
potentially LD_LIBRARY_PATH (or DYLD_LIBRARY_PATH), if libmpi/libshmem
|
2013-11-07 17:14:28 +00:00
|
|
|
is a shared library), unless using the --prefix or
|
2012-02-23 20:39:10 +00:00
|
|
|
--enable-mpirun-prefix-by-default functionality (see below).
|
2012-01-03 17:25:37 +00:00
|
|
|
|
|
|
|
- Open MPI's run-time behavior can be customized via MCA ("MPI
|
|
|
|
Component Architecture") parameters (see below for more information
|
|
|
|
on how to get/set MCA parameter values). Some MCA parameters can be
|
|
|
|
set in a way that renders Open MPI inoperable (see notes about MCA
|
|
|
|
parameters later in this file). In particular, some parameters have
|
|
|
|
required options that must be included.
|
|
|
|
|
|
|
|
- If specified, the "btl" parameter must include the "self"
|
|
|
|
component, or Open MPI will not be able to deliver messages to the
|
|
|
|
same rank as the sender. For example: "mpirun --mca btl tcp,self
|
|
|
|
..."
|
|
|
|
- If specified, the "btl_tcp_if_exclude" paramater must include the
|
|
|
|
loopback device ("lo" on many Linux platforms), or Open MPI will
|
|
|
|
not be able to route MPI messages using the TCP BTL. For example:
|
|
|
|
"mpirun --mca btl_tcp_if_exclude lo,eth1 ..."
|
|
|
|
|
|
|
|
- Running on nodes with different endian and/or different datatype
|
|
|
|
sizes within a single parallel job is supported in this release.
|
|
|
|
However, Open MPI does not resize data when datatypes differ in size
|
|
|
|
(for example, sending a 4 byte MPI_DOUBLE and receiving an 8 byte
|
|
|
|
MPI_DOUBLE will fail).
|
|
|
|
|
|
|
|
|
|
|
|
MPI Functionality and Features
|
|
|
|
------------------------------
|
|
|
|
|
2015-08-25 09:53:25 -04:00
|
|
|
- Rank reordering support is available using the TreeMatch library. It
|
|
|
|
is activated for the graph and dist_graph topologies.
|
2015-03-05 13:12:37 -05:00
|
|
|
|
2015-04-15 15:10:41 -07:00
|
|
|
- All MPI-3 functionality is supported.
|
2012-01-03 17:25:37 +00:00
|
|
|
|
2012-02-23 20:39:10 +00:00
|
|
|
- When using MPI deprecated functions, some compilers will emit
|
|
|
|
warnings. For example:
|
|
|
|
|
|
|
|
shell$ cat deprecated_example.c
|
|
|
|
#include <mpi.h>
|
|
|
|
void foo(void) {
|
|
|
|
MPI_Datatype type;
|
|
|
|
MPI_Type_struct(1, NULL, NULL, NULL, &type);
|
|
|
|
}
|
|
|
|
shell$ mpicc -c deprecated_example.c
|
|
|
|
deprecated_example.c: In function 'foo':
|
|
|
|
deprecated_example.c:4: warning: 'MPI_Type_struct' is deprecated (declared at /opt/openmpi/include/mpi.h:1522)
|
|
|
|
shell$
|
|
|
|
|
2012-01-03 17:25:37 +00:00
|
|
|
- MPI_THREAD_MULTIPLE support is included, but is only lightly tested.
|
|
|
|
It likely does not work for thread-intensive applications. Note
|
|
|
|
that *only* the MPI point-to-point communication functions for the
|
2012-02-23 20:39:10 +00:00
|
|
|
BTL's listed here are considered thread safe. Other support
|
|
|
|
functions (e.g., MPI attributes) have not been certified as safe
|
|
|
|
when simultaneously used by multiple threads.
|
|
|
|
- tcp
|
|
|
|
- sm
|
|
|
|
- self
|
2012-01-03 17:25:37 +00:00
|
|
|
|
|
|
|
Note that Open MPI's thread support is in a fairly early stage; the
|
2013-10-04 12:12:18 +00:00
|
|
|
above devices may *work*, but the latency is likely to be fairly
|
|
|
|
high. Specifically, efforts so far have concentrated on
|
2012-01-03 17:25:37 +00:00
|
|
|
*correctness*, not *performance* (yet).
|
|
|
|
|
2014-01-28 15:36:52 +00:00
|
|
|
YMMV.
|
|
|
|
|
2012-01-03 17:25:37 +00:00
|
|
|
- MPI_REAL16 and MPI_COMPLEX32 are only supported on platforms where a
|
|
|
|
portable C datatype can be found that matches the Fortran type
|
|
|
|
REAL*16, both in size and bit representation.
|
|
|
|
|
|
|
|
- The "libompitrace" library is bundled in Open MPI and is installed
|
|
|
|
by default (it can be disabled via the --disable-libompitrace
|
|
|
|
flag). This library provides a simplistic tracing of select MPI
|
|
|
|
function calls via the MPI profiling interface. Linking it in to
|
|
|
|
your appliation via (e.g., via -lompitrace) will automatically
|
|
|
|
output to stderr when some MPI functions are invoked:
|
|
|
|
|
2016-04-01 20:50:26 +02:00
|
|
|
shell$ cd examples/
|
|
|
|
shell$ mpicc hello_c.c -o hello_c -lompitrace
|
|
|
|
shell$ mpirun -np 1 hello_c
|
2012-01-03 17:25:37 +00:00
|
|
|
MPI_INIT: argc 1
|
|
|
|
Hello, world, I am 0 of 1
|
|
|
|
MPI_BARRIER[0]: comm MPI_COMM_WORLD
|
|
|
|
MPI_FINALIZE[0]
|
2012-02-23 20:39:10 +00:00
|
|
|
shell$
|
2012-01-03 17:25:37 +00:00
|
|
|
|
|
|
|
Keep in mind that the output from the trace library is going to
|
|
|
|
stderr, so it may output in a slightly different order than the
|
|
|
|
stdout from your application.
|
|
|
|
|
|
|
|
This library is being offered as a "proof of concept" / convenience
|
|
|
|
from Open MPI. If there is interest, it is trivially easy to extend
|
|
|
|
it to printf for other MPI functions. Patches and/or suggestions
|
|
|
|
would be greatfully appreciated on the Open MPI developer's list.
|
|
|
|
|
2013-11-07 17:14:28 +00:00
|
|
|
OSHMEM Functionality and Features
|
|
|
|
------------------------------
|
|
|
|
|
|
|
|
- All OpenSHMEM-1.0 functionality is supported.
|
|
|
|
|
|
|
|
|
|
|
|
MPI Collectives
|
2012-01-03 17:25:37 +00:00
|
|
|
-----------
|
|
|
|
|
|
|
|
- The "hierarch" coll component (i.e., an implementation of MPI
|
|
|
|
collective operations) attempts to discover network layers of
|
|
|
|
latency in order to segregate individual "local" and "global"
|
|
|
|
operations as part of the overall collective operation. In this
|
|
|
|
way, network traffic can be reduced -- or possibly even minimized
|
|
|
|
(similar to MagPIe). The current "hierarch" component only
|
|
|
|
separates MPI processes into on- and off-node groups.
|
|
|
|
|
|
|
|
Hierarch has had sufficient correctness testing, but has not
|
|
|
|
received much performance tuning. As such, hierarch is not
|
|
|
|
activated by default -- it must be enabled manually by setting its
|
|
|
|
priority level to 100:
|
|
|
|
|
|
|
|
mpirun --mca coll_hierarch_priority 100 ...
|
|
|
|
|
|
|
|
We would appreciate feedback from the user community about how well
|
|
|
|
hierarch works for your applications.
|
|
|
|
|
2012-02-23 20:39:10 +00:00
|
|
|
- The "fca" coll component: the Mellanox Fabric Collective Accelerator
|
|
|
|
(FCA) is a solution for offloading collective operations from the
|
|
|
|
MPI process onto Mellanox QDR InfiniBand switch CPUs and HCAs.
|
2012-01-03 17:25:37 +00:00
|
|
|
|
2015-04-01 15:40:42 -07:00
|
|
|
- The "ML" coll component is an implementation of MPI collective
|
2015-08-25 09:53:25 -04:00
|
|
|
operations that takes advantage of communication hierarchies in
|
|
|
|
modern systems. A ML collective operation is implemented by
|
2015-04-01 15:40:42 -07:00
|
|
|
combining multiple independently progressing collective primitives
|
|
|
|
implemented over different communication hierarchies, hence a ML
|
2015-08-25 09:53:25 -04:00
|
|
|
collective operation is also referred to as a hierarchical
|
|
|
|
collective operation. The number of collective primitives that are
|
|
|
|
included in a ML collective operation is a function of
|
|
|
|
subgroups(hierarchies). Typically, MPI processes in a single
|
|
|
|
communication hierarchy such as CPU socket, node, or subnet are
|
|
|
|
grouped together into a single subgroup (hierarchy). The number of
|
|
|
|
subgroups are configurable at runtime, and each different collective
|
|
|
|
operation could be configured to have a different of number of
|
|
|
|
subgroups.
|
2012-08-21 21:09:36 +00:00
|
|
|
|
2015-04-15 15:10:41 -07:00
|
|
|
The component frameworks and components used by/required for a
|
2012-08-21 21:09:36 +00:00
|
|
|
"ML" collective operation.
|
|
|
|
|
2015-04-01 15:40:42 -07:00
|
|
|
Frameworks:
|
2015-08-25 09:53:25 -04:00
|
|
|
* "sbgp" - Provides functionality for grouping processes into
|
|
|
|
subgroups
|
2015-04-01 15:40:42 -07:00
|
|
|
* "bcol" - Provides collective primitives optimized for a particular
|
2015-04-15 15:10:41 -07:00
|
|
|
communication hierarchy
|
2012-08-21 21:09:36 +00:00
|
|
|
|
|
|
|
Components:
|
2015-08-25 09:53:25 -04:00
|
|
|
* sbgp components - Provides grouping functionality over a CPU
|
|
|
|
socket ("basesocket"), shared memory
|
|
|
|
("basesmuma"), Mellanox's ConnectX HCA
|
|
|
|
("ibnet"), and other interconnects supported by
|
|
|
|
PML ("p2p")
|
|
|
|
* BCOL components - Provides optimized collective primitives for
|
|
|
|
shared memory ("basesmuma"), Mellanox's ConnectX
|
|
|
|
HCA ("iboffload"), and other interconnects
|
|
|
|
supported by PML ("ptpcoll")
|
2012-08-21 21:09:36 +00:00
|
|
|
|
2015-04-15 15:10:41 -07:00
|
|
|
- The "cuda" coll component provides CUDA-aware support for the
|
|
|
|
reduction type collectives with GPU buffers. This component is only
|
|
|
|
compiled into the library when the library has been configured with
|
|
|
|
CUDA-aware support. It intercepts calls to the reduction
|
|
|
|
collectives, copies the data to staging buffers if GPU buffers, then
|
|
|
|
calls underlying collectives to do the work.
|
2012-08-21 21:09:36 +00:00
|
|
|
|
2013-11-07 17:14:28 +00:00
|
|
|
OSHMEM Collectives
|
|
|
|
-----------
|
|
|
|
|
|
|
|
- The "fca" scoll component: the Mellanox Fabric Collective Accelerator
|
|
|
|
(FCA) is a solution for offloading collective operations from the
|
|
|
|
MPI process onto Mellanox QDR InfiniBand switch CPUs and HCAs.
|
|
|
|
|
2015-04-01 15:40:42 -07:00
|
|
|
- The "basic" scoll component: Reference implementation of all OSHMEM
|
2013-11-07 17:14:28 +00:00
|
|
|
collective operations.
|
|
|
|
|
|
|
|
|
2012-01-03 17:25:37 +00:00
|
|
|
Network Support
|
|
|
|
---------------
|
|
|
|
|
2015-04-15 15:10:41 -07:00
|
|
|
- There are three main MPI network models available: "ob1", "cm", and
|
|
|
|
"yalla". "ob1" uses BTL ("Byte Transfer Layer") components for each
|
|
|
|
supported network. "cm" uses MTL ("Matching Tranport Layer")
|
|
|
|
components for each supported network. "yalla" uses the Mellanox
|
|
|
|
MXM transport.
|
2012-01-03 17:25:37 +00:00
|
|
|
|
|
|
|
- "ob1" supports a variety of networks that can be used in
|
|
|
|
combination with each other (per OS constraints; e.g., there are
|
|
|
|
reports that the GM and OpenFabrics kernel drivers do not operate
|
|
|
|
well together):
|
2012-02-23 20:39:10 +00:00
|
|
|
|
|
|
|
- OpenFabrics: InfiniBand, iWARP, and RoCE
|
2012-01-03 17:25:37 +00:00
|
|
|
- Loopback (send-to-self)
|
|
|
|
- Shared memory
|
|
|
|
- TCP
|
2014-01-10 05:03:00 +00:00
|
|
|
- Intel Phi SCIF
|
|
|
|
- SMCUDA
|
2013-07-19 22:14:49 +00:00
|
|
|
- Cisco usNIC
|
2015-04-23 16:58:30 -04:00
|
|
|
- uGNI (Cray Gemini, Aries)
|
2015-04-15 15:10:41 -07:00
|
|
|
- vader (XPMEM, Linux CMA, Linux KNEM, and general shared memory)
|
2012-01-03 17:25:37 +00:00
|
|
|
|
|
|
|
- "cm" supports a smaller number of networks (and they cannot be
|
2013-07-22 22:16:05 +00:00
|
|
|
used together), but may provide better overall MPI performance:
|
2012-02-23 20:39:10 +00:00
|
|
|
|
2015-07-23 14:37:55 -04:00
|
|
|
- QLogic InfiniPath / Intel True Scale PSM
|
|
|
|
- Intel Omni-Path PSM2
|
2012-01-03 17:25:37 +00:00
|
|
|
- Mellanox MXM
|
2014-01-10 05:03:00 +00:00
|
|
|
- Portals4
|
2015-07-23 14:37:55 -04:00
|
|
|
- OpenFabrics Interfaces ("libfabric" tag matching)
|
2012-01-03 17:25:37 +00:00
|
|
|
|
2015-07-23 14:37:55 -04:00
|
|
|
Open MPI will, by default, choose to use "cm" when one of the
|
|
|
|
above transports can be used. Otherwise, "ob1" will be used and
|
|
|
|
the corresponding BTLs will be selected. Users can force the use
|
|
|
|
of ob1 or cm if desired by setting the "pml" MCA parameter at
|
|
|
|
run-time:
|
2012-01-03 17:25:37 +00:00
|
|
|
|
2012-02-23 20:39:10 +00:00
|
|
|
shell$ mpirun --mca pml ob1 ...
|
|
|
|
or
|
|
|
|
shell$ mpirun --mca pml cm ...
|
2012-01-03 17:25:37 +00:00
|
|
|
|
2014-01-28 15:36:52 +00:00
|
|
|
- Similarly, there are two OSHMEM network models available: "yoda",
|
|
|
|
and "ikrit". "yoda" also uses the BTL components for many supported
|
|
|
|
network. "ikrit" interfaces directly with Mellanox MXM.
|
2013-11-07 17:14:28 +00:00
|
|
|
|
|
|
|
- "yoda" supports a variety of networks that can be used:
|
2015-04-01 15:40:42 -07:00
|
|
|
|
2013-11-07 17:14:28 +00:00
|
|
|
- OpenFabrics: InfiniBand, iWARP, and RoCE
|
|
|
|
- Loopback (send-to-self)
|
|
|
|
- Shared memory
|
|
|
|
- TCP
|
|
|
|
|
2015-04-01 15:40:42 -07:00
|
|
|
- "ikrit" only supports Mellanox MXM.
|
|
|
|
|
2014-01-28 15:36:52 +00:00
|
|
|
- MXM is the Mellanox Messaging Accelerator library utilizing a full
|
|
|
|
range of IB transports to provide the following messaging services
|
|
|
|
to the upper level MPI/OSHMEM libraries:
|
2012-02-23 20:39:10 +00:00
|
|
|
|
2015-04-01 15:40:42 -07:00
|
|
|
- Usage of all available IB transports
|
2012-01-03 17:25:37 +00:00
|
|
|
- Native RDMA support
|
|
|
|
- Progress thread
|
|
|
|
- Shared memory communication
|
2012-02-23 20:39:10 +00:00
|
|
|
- Hardware-assisted reliability
|
|
|
|
|
2013-07-19 22:14:49 +00:00
|
|
|
- The usnic BTL is support for Cisco's usNIC device ("userspace NIC")
|
|
|
|
on Cisco UCS servers with the Virtualized Interface Card (VIC).
|
2015-04-15 15:10:41 -07:00
|
|
|
Although the usNIC is accessed via the OpenFabrics Libfabric API
|
2013-07-19 22:14:49 +00:00
|
|
|
stack, this BTL is specific to the Cisco usNIC device.
|
|
|
|
|
2015-04-23 16:58:30 -04:00
|
|
|
- uGNI is a Cray library for communicating over the Gemini and Aries
|
2013-07-22 19:16:59 +00:00
|
|
|
interconnects.
|
|
|
|
|
2012-02-23 20:39:10 +00:00
|
|
|
- The OpenFabrics Enterprise Distribution (OFED) software package v1.0
|
|
|
|
will not work properly with Open MPI v1.2 (and later) due to how its
|
|
|
|
Mellanox InfiniBand plugin driver is created. The problem is fixed
|
|
|
|
OFED v1.1 (and later).
|
|
|
|
|
|
|
|
- Better memory management support is available for OFED-based
|
|
|
|
transports using the "ummunotify" Linux kernel module. OFED memory
|
|
|
|
managers are necessary for better bandwidth when re-using the same
|
|
|
|
buffers for large messages (e.g., benchmarks and some applications).
|
2015-04-01 15:40:42 -07:00
|
|
|
|
2012-02-23 20:39:10 +00:00
|
|
|
Unfortunately, the ummunotify module was not accepted by the Linux
|
|
|
|
kernel community (and is still not distributed by OFED). But it
|
|
|
|
still remains the best memory management solution for MPI
|
|
|
|
applications that used the OFED network transports. If Open MPI is
|
|
|
|
able to find the <linux/ummunotify.h> header file, it will build
|
|
|
|
support for ummunotify and include it by default. If MPI processes
|
2013-10-04 12:12:18 +00:00
|
|
|
then find the ummunotify kernel module loaded and active, then their
|
2012-02-23 20:39:10 +00:00
|
|
|
memory managers (which have been shown to be problematic in some
|
|
|
|
cases) will be disabled and ummunotify will be used. Otherwise, the
|
|
|
|
same memory managers from prior versions of Open MPI will be used.
|
|
|
|
The ummunotify Linux kernel module can be downloaded from:
|
|
|
|
|
|
|
|
http://lwn.net/Articles/343351/
|
|
|
|
|
|
|
|
- The use of fork() with OpenFabrics-based networks (i.e., the openib
|
|
|
|
BTL) is only partially supported, and only on Linux kernels >=
|
|
|
|
v2.6.15 with libibverbs v1.1 or later (first released as part of
|
|
|
|
OFED v1.2), per restrictions imposed by the OFED network stack.
|
2012-01-03 17:25:37 +00:00
|
|
|
|
2015-04-15 15:10:41 -07:00
|
|
|
- Linux "knem" support is used when the "vader" or "sm" (shared
|
|
|
|
memory) BTLs are compiled with knem support (see the --with-knem
|
|
|
|
configure option) and the knem Linux module is loaded in the running
|
|
|
|
kernel. If the knem Linux kernel module is not loaded, the knem
|
|
|
|
support is (by default) silently deactivated during Open MPI jobs.
|
2012-01-03 17:25:37 +00:00
|
|
|
|
|
|
|
See http://runtime.bordeaux.inria.fr/knem/ for details on Knem.
|
|
|
|
|
2015-04-15 15:10:41 -07:00
|
|
|
- Linux Cross-Memory Attach (CMA) or XPMEM is used by the vader
|
|
|
|
shared-memory BTL when the CMA/XPMEM libraries are installedm,
|
|
|
|
respectively. Linux CMA and XPMEM are similar (but different)
|
|
|
|
mechanisms for Open MPI to utilize single-copy semantics for shared
|
|
|
|
memory.
|
2012-02-23 20:39:10 +00:00
|
|
|
|
2012-01-03 17:25:37 +00:00
|
|
|
Open MPI Extensions
|
|
|
|
-------------------
|
|
|
|
|
2012-02-23 20:39:10 +00:00
|
|
|
- An MPI "extensions" framework has been added (but is not enabled by
|
|
|
|
default). See the "Open MPI API Extensions" section below for more
|
|
|
|
information on compiling and using MPI extensions.
|
2012-01-03 17:25:37 +00:00
|
|
|
|
|
|
|
- The following extensions are included in this version of Open MPI:
|
|
|
|
|
|
|
|
- affinity: Provides the OMPI_Affinity_str() routine on retrieving
|
|
|
|
a string that contains what resources a process is bound to. See
|
|
|
|
its man page for more details.
|
|
|
|
- cr: Provides routines to access to checkpoint restart routines.
|
|
|
|
See ompi/mpiext/cr/mpiext_cr_c.h for a listing of availble
|
|
|
|
functions.
|
2015-07-23 15:38:44 -04:00
|
|
|
- cuda: When the library is compiled with CUDA-aware support, it provides
|
|
|
|
two things. First, a macro MPIX_CUDA_AWARE_SUPPORT. Secondly, the
|
|
|
|
function MPIX_Query_cuda_support that can be used to query for support.
|
2012-01-03 17:25:37 +00:00
|
|
|
- example: A non-functional extension; its only purpose is to
|
|
|
|
provide an example for how to create other extensions.
|
|
|
|
|
|
|
|
===========================================================================
|
|
|
|
|
|
|
|
Building Open MPI
|
|
|
|
-----------------
|
|
|
|
|
|
|
|
Open MPI uses a traditional configure script paired with "make" to
|
|
|
|
build. Typical installs can be of the pattern:
|
|
|
|
|
|
|
|
---------------------------------------------------------------------------
|
|
|
|
shell$ ./configure [...options...]
|
|
|
|
shell$ make all install
|
|
|
|
---------------------------------------------------------------------------
|
|
|
|
|
|
|
|
There are many available configure options (see "./configure --help"
|
2014-01-28 15:36:52 +00:00
|
|
|
for a full list); a summary of the more commonly used ones is included
|
|
|
|
below.
|
|
|
|
|
|
|
|
Note that for many of Open MPI's --with-<foo> options, Open MPI will,
|
|
|
|
by default, search for header files and/or libraries for <foo>. If
|
|
|
|
the relevant files are found, Open MPI will built support for <foo>;
|
|
|
|
if they are not found, Open MPI will skip building support for <foo>.
|
|
|
|
However, if you specify --with-<foo> on the configure command line and
|
|
|
|
Open MPI is unable to find relevant support for <foo>, configure will
|
|
|
|
assume that it was unable to provide a feature that was specifically
|
|
|
|
requested and will abort so that a human can resolve out the issue.
|
2012-01-03 17:25:37 +00:00
|
|
|
|
2012-02-23 20:39:10 +00:00
|
|
|
INSTALLATION OPTIONS
|
|
|
|
|
2012-01-03 17:25:37 +00:00
|
|
|
--prefix=<directory>
|
|
|
|
Install Open MPI into the base directory named <directory>. Hence,
|
|
|
|
Open MPI will place its executables in <directory>/bin, its header
|
|