technically speaking, this is a cosmetic change, but having the wrong
parameter names was extremely confusing -- it took me a while (and I
had to cross-reference MPI-1) to figure out that they were wrong, and
I was thinking about the functions incorrectly as a result. Our mpi.h
should have the Right names in order to not confuse users (and
developers!).
This commit was SVN r5034.
This commit was SVN r4978.
The following SVN revisions from the original message are invalid or
inconsistent and therefore were not cross-referenced:
r4977
threads (defaults to use MPI threads, disable progress threads). This
allows us to have MPI threaded support, but without progress threads
and all that fun stuff.
This commit was SVN r4443.
- Use fcntl.h, not sys/fcntl.h (man pages on every platform I could find
say fcntl.h and solaris/AIX don't provide sys/fcntl.h)
- Make timeradd macro available on platforms where sys/time.h exists but
timeradd macro doesn't (Solaris)
- Include util/printf.h from ompi_config_bottom.h so that ompi_asprintf
and friends are always available.
This commit was SVN r4441.
are generated at configure time, so there is no need to have them in the
tarball (and doing so can cause some really evil VPATH issues). The .in
files needed to make ompi_config.h and mpif.h are included in the tarball.
This commit was SVN r4367.
#if OMPI_WANT_MPI2_ONE_SIDED and some automake conditionals. Also had
to add some AC_SUBSTs to eliminate part of mpif.h (otherwise the
"external" statements would have made undefined symbols).
All the MPI-2 one-sided functionality (including the skeleton
top-level MPI API functions that only invoke an MPI exception) can be
re-enabled with --enable-mpi2-one-sided.
This commit was SVN r3802.
support is included because ROMIO is inherently thread-unsafe.
One possible way to have true asynchronous progress would be to use a
progress thread that wakes up and polls at some frequency when there
are non-blocking IO requests pending. This is pretty icky, though --
it should definitely have an MCA parameter to enable/disable this
functionality, as well as another to control the polling frequency.
This also strengthens the argument that we need a v2 of the io
framework -- one that is not designed to exclusively support ROMIO --
one that does something unimaginably "better" for the parallel MPI-2
IO interface. :-)
This commit was SVN r3786.
included by ompi_config_bottom.h, so it's redundant to include
ompi_config.h in it.
- Add OMPI_DEBUG_ZERO macro for zeroing out memory while debugging so
that valgrind (et al.) don't complain about uninitialized memory
when we know it's safe.
- correct a comment in ompi_config_bottom.h to make it have the
correct filename
This commit was SVN r3662.
that the C compiler may support bool with no help from <stdbool.h>.
So add another configure test and adjust ompi_config_bottom.h as
appropriate. Since the #if logic in ompi_config_bottom.h got a little
complicated w.r.t. bool, I indented to make the conditionals clear.
This commit was SVN r3291.
1. header file and source file protections using #ifdef WIN32
2. new files and directories to support windows functionality
3. appropritate linkage symbols added (OMPI_DECLSPEC) for windows
4. some functions are unimplemented on the windows side. this is mostly
because there might not be need to implement it in windows land. eg., forking
a daemon off
5. Introduced locking mechanisms for windows
This commit was SVN r3286.
alignment. Right now, we only check for char, short, and int. If we
ever run across a platform where one of those three don't work, we'll
need to extend ompi_config_bottom.h. :-)
This commit was SVN r3271.
ompi_config_bottom.h -- it's already in src/mpi/runtime/params.h.
- Add /src/mpi/runtime/params.h to a small number of places.
- Remove some useless run-time checks in MPI fortran functions
This commit was SVN r3177.
c2f MPI_Status translation along the way. This should enable Fortran
MPI apps that use non-blocking communication to start working.
This commit was SVN r2996.
table in my last commit. This commit fixes that, and then re-patches
up mpif.h.in to match.
I'm not sure that we need *all* of the datatypes in there (e.g., do we
really need the C datatypes?), but since George isn't around, I
followed the "when in doubt, it doesn't hurt to add more entries to
the table" rule. Following up with a detailed message to George...
This commit was SVN r2900.
