I could use some help from one of you MCA gurus - if you run the test, you'll see that I cannot get the gpr components to be recognized. I'm not sure of the reason - I would appreciate any help you can provide to get the gpr components "registered".
This commit was SVN r2158.
I have to commit this to cleanup a break in my tree. I'm hoping it won't break the compile of the tree, but will fix it as quickly as possible.
Jeff - you are welcome to set an "ignore" on the gpr if you like - I'll let you know when I've got the "kinks" out.
This commit was SVN r2145.
MPI_PARAM_CHECK was previously set to disable MPI API param checking
at compile time (and our hands are tied at run-time) and implict MCA
param assignements
This commit was SVN r2142.
- 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.
structures to make it easier to swap around lists when doing process ->
resource mapping
* Fix spawn interface to take an ompi_list_t* instead of an ompi_list_t
since you can't pass an ompi_list_t by value
* Change allocate_resource to return an ompi_list_t* instead of having
an ompi_list_t** as an argument, since it's a bit cleaner and makes
who should call OBJ_NEW much more clear
* Clean up deallocation in error cases for the llm_base_allocate function
* Update test case for llm to not depend on current environment for
correctness
This commit was SVN r2126.
Major change to the name server system to introduce the OOB interface. Changed the ompi_process_name_t to no longer be an OBJ, but instead just a regular C structure. Include the packing-based oob interface.
This commit was SVN r2114.
removing the warning in comm_split_f pointed out be the 64bit architecture. Actually, I wonder why g77 did not detect that, since this was a real bug and not just a warning :-)
This commit was SVN r2113.
Looks like it works:
SUPPORT: OMPI Test Passed: oob packed recieve then send: (15 tests)
SUPPORT: OMPI Test Passed: oob packed send then recieve: (15 tests)
This commit was SVN r2110.
