Antonio J. Pena authored Jul 03, 2014 and Kenneth Raffenetti committed Jul 07, 2014

Moved the weak,alias attribute declarations from header files to the
implementation. Complies with the requirement that alias targets are
defined in the same compilation unit.

Fixes #2002

Signed-off-by: Ken Raffenetti <raffenet@mcs.anl.gov>

Move error checking from critical paths. Fixes #1978

Signed-off-by: Antonio J. Pena <apenya@mcs.anl.gov>

Fixes #1969

Signed-off-by: Antonio J. Pena <apenya@mcs.anl.gov>

Junchao Zhang authored Sep 03, 2013 and Pavan Balaji committed Oct 26, 2013

Implemented the framework for MPI_T enums, categories, performance variables.
and control variables specified in MPI3. Fix #1898, #1930.

The code should make MPICH MPI_T compliant, though not all MPICH pvars/cvars
are currently exposed through MPI_T.

The code supports multithreading up to MPI_THREAD_MULTIPLE.

Signed-off-by: Pavan Balaji <balaji@mcs.anl.gov>

Junchao Zhang authored Aug 16, 2013 and Pavan Balaji committed Sep 21, 2013

Some MPI_T functions return MPI_SUCCESS even when they are not implemented.
Now return MPI_ERR_INTERN instead. Of course it is a temp fix.

Signed-off-by: Pavan Balaji <balaji@mcs.anl.gov>

notation to match the MPI-3 standard: mpi_t.

Reviewed by dinan.

moved some error messages which should have been mpix to mpi.

Reviewed by dinan.

MPI_.

A slightly older version of this patch was reviewed by goodell.

In several places, after checking for a parameter (e.g., comm) we were
directly using it assuming that the parameter is valid.  Since the
previous ERRTEST macros did not jump to fn_fail on an error, this
could result in undefined behavior if the parameter was invalid.  Now,
since we jump on errors within the macros themselves, once the check
is done, we know that the parameter values are valid.

Reviewed by buntinas.

Most of the problems associated with this implementation have to do with
initialization bootstrapping/teardown issues.  Using the new interface
to profile MPI_Init/MPI_Finalize certainly has at least a few bugs right
now.  Use entirely within an MPI_Init/MPI_Finalize region should
basically work fine.

Two performance variables are exposed right now, the expected and
unexpected queue lengths.  All environment variables from the parameter
interface are exposed via the new "control variable" API.

No reviewer.