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.
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.
- 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.
- Mark those who are still not yet implemented:
- return an error
- have a grep-able string indicating that they are not yet
implemented
- ensure every function checks for init/finalize
- add more error checking to a bunch of functions
- unify the error checking -- it reflected about 3 different
[previous] error checking styles and MPI exception invocation styles
This commit was SVN r1817.
