- 30 May, 2015 6 commits
-
-
Note that here we move the definition of streaming unit size to mpidimpl.h in CH3, so that Nemesis can see it and do assert check on it. Signed-off-by:
Pavan Balaji <balaji@anl.gov>
-
Signed-off-by:
Pavan Balaji <balaji@anl.gov>
-
The original mtest routine only generated tests for noncontiguous derived datatypes. This patch added two tests for every derived datatype: (1) contiguous ddt (stride=block length) without lower-bound; (2) contiguous ddt with lower-bound. Signed-off-by:
Pavan Balaji <balaji@anl.gov>
-
The original mtest routine only generated datatype tests with zero lower-bound. This patch added a test for every derived datatype that checks datatype structure with non-zero lower-bound. Signed-off-by:
Pavan Balaji <balaji@anl.gov>
-
The original mtest routine used extent as the space required by derived datatypes (i.e., to calculate the offset per datatype in a data buffer). However, it is incorrect if the lower-bound is not zero. The space must be lower-bound + extent. This patch fixed it. Signed-off-by:
Pavan Balaji <balaji@anl.gov>
-
Kenneth Raffenetti authored
No reviewer.
-
- 29 May, 2015 1 commit
-
-
Kenneth Raffenetti authored
Ensures this test runs only when ROMIO is enabled. Signed-off-by:
Rob Latham <robl@mcs.anl.gov>
-
- 28 May, 2015 3 commits
-
-
Huiwei Lu authored
Removes unnecessary thread yielding in threaded nonblocking context id allocation algorithm. The error was introduced by "copy-pasting" from the blocking context id allocation algorithm (MPIR_Get_contextid_sparse_group) when implementing the nonblocking algorithm. Note the subtle difference on thread handling between the two. In the blocking algorithm, yield is needed to allow another thread to make progress. In nonblocking algorithm, there is no need to yield to another thread because this thread will not block the progress. On the contrary, unnecessary yield will allow other threads to execute and insert wrong order of entries to the nonblocking schedule and cause errors. Fixes #2183 Signed-off-by:
Junchao Zhang <jczhang@mcs.anl.gov>
-
Kenneth Raffenetti authored
Refs #2088 Signed-off-by:
Rob Latham <robl@mcs.anl.gov>
-
Kenneth Raffenetti authored
Use PAC macro to AC_SUBST and export WRAPPER_XXX variables. Ensures that they are available to the testsuite configure script. Closes #2190 Signed-off-by:
Pavan Balaji <balaji@anl.gov>
-
- 27 May, 2015 2 commits
-
-
Kenneth Raffenetti authored
Two tag bits are reserved for error propagation. We need to make sure they are ignored by the network matching capabilities. Refs #2260 No reviewer.
-
If the destination of a LMT nonblocking send, which follows a rendez-vous protocol, receives the RTS packet to the unexpected queue followed by a cancelation request, the request in the unexpected queue never gets freed. To solve the issue, we forcefully free the rendez-vous request by adding an additional request release operation. Refs #287 Signed-off-by:
Ken Raffenetti <raffenet@mcs.anl.gov>
-
- 26 May, 2015 2 commits
-
-
Kenneth Raffenetti authored
Frees memory allocated to track large sends when those sends are successfully cancelled. No reviewer.
-
The configure test was dropped long time ago in MPICH, and to keep ABI compatible, we don't want to restore it. Refs #1877 Signed-off-by:
Ken Raffenetti <raffenet@mcs.anl.gov>
-
- 22 May, 2015 3 commits
-
-
Junchao Zhang authored
Refs #1877 Signed-off-by:
Ken Raffenetti <raffenet@mcs.anl.gov>
-
Junchao Zhang authored
Change the bindings to make it as if MPI_BOTTOM in Fortran is at address zero as it in C. See discussion on p.652 of MPI-3.0 Fixes #1877 Signed-off-by:
Ken Raffenetti <raffenet@mcs.anl.gov>
-
Antonio J. Pena authored
According to the standard, collectives using the same communicator must implement thread safety in the application level. So, if using MPI_Comm_spawn in THREAD_MULTIPLE safety level, it must use different communicators. I've modified the test to use different communicators per thread so that we can still test its thread safety. Fixes #2256
-
- 21 May, 2015 1 commit
-
-
Antonio J. Pena authored
It was created but never destroyed.
-
- 20 May, 2015 3 commits
-
-
Kenneth Raffenetti authored
Signed-off-by:
Antonio J. Pena <apenya@mcs.anl.gov>
-
Kenneth Raffenetti authored
Signed-off-by:
Antonio J. Pena <apenya@mcs.anl.gov>
-
Kenneth Raffenetti authored
Simplifies request completion logic and ensures operations are properly accounted for in the cancel send case. Removes pt2pt send tracking in the VC, as requests are enough to guarantee completion. Signed-off-by:
Antonio J. Pena <apenya@mcs.anl.gov>
-
- 19 May, 2015 3 commits
-
-
Sangmin Seo authored
This is currently a workaround to avoid weird errors, e.g., stack fault, occurred in the NBC I/O implementation on Linux. When the host OS is Linux and aio-lite is not used, a blocking ADIO function is used in the NBC I/O implementation. Fixes #2201 Signed-off-by:
Rob Latham <robl@mcs.anl.gov>
-
Sangmin Seo authored
configure defines ROMIO_RUN_ON_LINUX as 1 when the host OS is Linux. Signed-off-by:
Rob Latham <robl@mcs.anl.gov>
-
Kenneth Raffenetti authored
Defines usleep when needed. This build error was discovered via the random config tests in jenkins. Signed-off-by:
Rob Latham <robl@mcs.anl.gov>
-
- 13 May, 2015 2 commits
-
-
Signed-off-by:
Ken Raffenetti <raffenet@mcs.anl.gov>
-
Signed-off-by:
Ken Raffenetti <raffenet@mcs.anl.gov>
-
- 11 May, 2015 2 commits
-
-
Rob Latham authored
we were not correctly handling the case where the error handler MPI_ERRORS_ARE_FATAL was called. credit Lisandro Dalcin with finidng the issue. Signed-off-by:
Junchao Zhang <jczhang@mcs.anl.gov>
-
Rob Latham authored
Lisandro Dalcin found we returned the wrong value from MPI_File_call_errhandler. it should return MPI_SUCCESS unless something goes wrong with MPI_File_call_errhandler itself. Closes #2259 Signed-off-by:
Junchao Zhang <jczhang@mcs.anl.gov>
-
- 10 May, 2015 2 commits
-
-
Jithin Jose authored
Signed-off-by:
Jithin Jose <jithin.jose@intel.com> Signed-off-by:
Charles J Archer <charles.j.archer@intel.com>
-
Jithin Jose authored
Signed-off-by:
Jithin Jose <jithin.jose@intel.com> Signed-off-by:
Charles J Archer <charles.j.archer@intel.com>
-
- 05 May, 2015 2 commits
-
-
Kenneth Raffenetti authored
For tests that call pthread routines, add an explicit dependency. This was not an issue previously, because either the compile wrappers always added -lpthread, or the linker discovered the pthread symbols via an interlibrary dependency on libmpi. However on FreeBSD 10, the interlibrary dependency resolution appears more strict. Applications must specify any libraries directly used, thus this fix. Signed-off-by:
Halim Amer <aamer@anl.gov>
-
Kenneth Raffenetti authored
This reverts commit 7c0f2967 . Signed-off-by:
Halim Amer <aamer@anl.gov>
-
- 30 Apr, 2015 2 commits
-
-
Jeff Hammond authored
Signed-off-by:
Junchao Zhang <jczhang@mcs.anl.gov>
-
Jeff Hammond authored
Signed-off-by:
Junchao Zhang <jczhang@mcs.anl.gov>
-
- 29 Apr, 2015 5 commits
-
-
Rob Latham authored
No reviewer
-
Rob Latham authored
see #1767 Signed-off-by:
Ken Raffenetti <raffenet@mcs.anl.gov>
-
Pavan Balaji authored
If the user passes the -static flag, we disable interlibrary dependencies, since the linker would pick the static versions of the libraries in that case. We are still making an assumption that the default mode of the linker is shared, and the user can specify static library builds with -static. However, this is not always true. On BG/Q, for example, the default is static. Fixes #2190. Signed-off-by:
Ken Raffenetti <raffenet@mcs.anl.gov>
-
Pavan Balaji authored
This includes several changes: 1. Merged WRAPPER and EXTERNAL LIBS. There is no reason to maintain two names for these flags. These are eventually appended and added to the compiler wrappers anyway. 2. Updated mpicc and friend to add the necessary flags directly instead of trying to merge these flags in configure. Signed-off-by:
Ken Raffenetti <raffenet@mcs.anl.gov>
-
Pavan Balaji authored
It does not make sense for the user to specify LDFLAGS/LIBS that would only be used to build the MPICH library, but not the user application. Doing do will create a false dependency of the MPICH library on these external libraries resulting in weird interactions with the user application in cases where interlibrary dependencies are not supported. We were anyway silently modifying the WRAPPER LDFLAGS/LIBS to include these anyway, so the flags themselves were weirdly screwed up. This patch simply removes them instead of pretending to allow them, but not really allowing them. Signed-off-by:
Ken Raffenetti <raffenet@mcs.anl.gov>
-
- 28 Apr, 2015 1 commit
-
-
The random configuration tests revealed that MPI name publishing features could be disabled at configure time, but the test suite would still run tests for them. Signed-off-by:
Sangmin Seo <sseo@anl.gov>
-