thingy needs to go on the *declaration*, not the *definition*. Well,
at least this was all done en masse and via an automated mechanism, so
total time wasted was only about 15 minutes...
This commit was SVN r2858.
am sure that some will have to be added back in as functionality is
added (like for comm_spawn.c), but for now might as well compile
faster :)
This commit was SVN r2780.
invoking an errhandler in MPI_INIT when we don't yet have a
communicator to invoke them on. Instead, remove some of the logic
from the ERRHANDLER macros and just invoke the back-end function
directly in MPI_INIT.
This commit was SVN r2692.
such as MPI_DUP_FN: MPI says that they have to be available via that
name in both C and Fortran. However, for implementation reasons, we
have to have them as separate functions. But if a Fortran compiler's
naming convention is ALL_CAPS, this is not possible. Hence, we need
to put in #define's in mpi.h to change the C names something like
this: MPI_DUP_FN -> OMPI_C_MPI_DUP_FN. This was actually done a long
time ago.
However, the source code where those C functions actually live
(src/mpi/c/attr_fn.c) still reflected the old names (e.g.,
MPI_DUP_FN). This is fine, actually -- mpi.h would come in and
#define them to their real names (OMPI_C_MPI_DUP_FN). So it was
functionally correct, but confusing at hell (and it just bit Edgar and
me today). So I'm changing src/mpi/c/attr_fn.c to use the real names
(OMPI_C_MPI_DUP_FN) so that tools like ctags and grep can find them in
the source code when you go looking. Plus, the code is just more
clear that way. I also put in massive comments about this in
src/mpi/c/attr_fn.c and src/mpi/f77/attr_fn_f.c so that we remember
why the heck we did this. :-)
This commit was SVN r2670.
includes the romio component. Only blocking operations are supported
-- non-blocking stuff is pending some changes in the top-level
progression engine, and some threaded issues need to be worked out.
This commit was SVN r2655.
ompi_pointer_array_get_item() function instead of accessing the array
directly. This is because accessing the array directly in
multi-threaded situations is unsafe (someone else may be writing to
the array, the array may get moved out from under you via realloc(),
etc.).
This commit was SVN r2634.
upcoming commit), this is the preferred way to do conditional source
files these days. AM can then infer which files to pick up for
distribution without the need for EXTRA_DIST. Also, for mpi/c/profile
and mpi/f77/profile, don't distribute any source files -- just let the
sym links be made by the user. This makes the tarball just slightly
smaller. ;-)
This commit was SVN r2316.
- the f2c functions should return the corresponding *_NULL functions
and not invoke an MPI exception if an invalid fortran handle is
passed
- the error check should be outside MPI_PARAM_CHECK -- MPI defines the
behavior of when an invalid fortran handle is passed; it is not
dependant upon whether we are checking parameters or not
This commit was SVN r2140.
somewhat tied together and I'd rather have a consistent commit rather
than several smaller commits that individually break the tree:
- first cut of src/file/file.c: MPI_File handling. More to come here.
- tweaked MPI_Info handling a bit: cause MPI_Info_f2c to invoke error
handler if provided index is out of range (vs. returing
MPI_INFO_NULL without invoking an error handler)
- moved general MPI MCA params off into their own .h and .c file (so
that ompi_info can call it and therefore display MPI MCA params)
- first [abbreviated] cut of src/mca/io/base/* -- much more to come
here; stripped down to basics for this commit
- filled in a small number of MPI_File* functions for testing purposes
- updated a bunch of doxygen docs
--> Unresolved questions about MPI_ERRORS_RETURN, MPI_ERRORS_ABORT,
and MPI::ERRORS_THROW_EXCEPTIONS because of vagueness in MPI
standard -- Edgar and I are discussing what to do here
--> Unresolved questions about what to do in a case like this:
MPI_File_open(..., &file);
MPI_File_close(&file);
MPI_File_read(..., &file);
because MPI-2:9.7 says that the default error handler on MPI_File
handles is MPI_ERRORS_RETURN -- we can't even print a warning
here! This certainly violates the Law of Least Astonishment for
MPI users (who certainly expect MPI functions that fail to
complain loudly and to abort by default).
This commit was SVN r2136.
- fix a few bugs
- convert/add doxygen comments for internal info functions in
src/info/info.h (some comments were originally in src/info/info.c)
- make it thread safe
- make MPI_INFO_NULL be a real object (vs ((struct ompi_info_t*) 0))
- add error checking into top-level MPI functions
- add support in MPI_Info for "never freeing MPI handles" as a form of
debugging i.e., check if see if you accidentally use a freed handle)
- add support for "print out a list of un-freed MPI_Info handles
during MPI_FINALIZE"
This commit was SVN r2089.
are in the right order in the process struct
This commit was SVN r2006.
The following SVN revision numbers were found above:
r1965 --> open-mpi/ompi@48c8d55b6d
comm_join and comm_connect to #if 0 out the calls to the ns added in
r1965
This commit was SVN r1994.
The following SVN revision numbers were found above:
r1965 --> open-mpi/ompi@48c8d55b6d
