- 25 Jul, 2013 22 commits
-
-
The FT functions are now the default (only) way to call the collective helper functions. This is one of a few patches to migrate all uses to no longer use the MPIC_*_ft naming scheme. Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
The FT functions are now the default (only) way to call the collective helper functions. This is one of a few patches to migrate all uses to no longer use the MPIC_*_ft naming scheme. Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
The FT functions are now the default (only) way to call the collective helper functions. This is one of a few patches to migrate all uses to no longer use the MPIC_*_ft naming scheme. Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
The FT functions are now the default (only) way to call the collective helper functions. This is one of a few patches to migrate all uses to no longer use the MPIC_*_ft naming scheme.Rename MPIC_Send_ft to MPIC_Send Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
The FT functions are now the default (only) way to call the collective helper functions. This is one of a few patches to migrate all uses to no longer use the MPIC_*_ft naming scheme.Rename MPIC_Send_ft to MPIC_Send Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
The FT functions are now the default (only) way to call the collective helper functions. This is one of a few patches to migrate all uses to no longer use the MPIC_*_ft naming scheme. Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
The FT functions are now the default (only) way to call the collective helper functions. This is one of a few patches to migrate all uses to no longer use the MPIC_*_ft naming scheme. Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
The FT functions are now the default (only) way to call the collective helper functions. This is one of a few patches to migrate all uses to no longer use the MPIC_*_ft naming scheme. Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
Merge the two functions into one function and remove the non-ft version. Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
Merge the two functions into one function and remove the non-ft version. Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
Merge the two functions into one function and remove the non-ft version. Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
Merge the two functions into one function and remove the non-ft version. Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
Merge the two functions into one function and remove the non-ft version. Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
Merge the two functions into one function and remove the non-ft version. Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
Merge the two function into one function and remove the non-ft version. Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
All usages of the non-ft versions have moved over to use the ft versions to avoid the need to maintain both and to ensure that we provide some ability to provide ft everywhere. There are times where this isn't necessary or useful and in those cases, the value of *errflag can be ignored and just the return value can be checked to see if the function was successful or not. The MPIC_* functions that have an ft mirror (e.g. MPIC_Send -> MPIC_Send_ft) are no longer accessible outside of helper_fns.c. Now the MPIC_*_ft functions should be called directly. Note that this is not going to be a long lived policy. Instead, the MPIC_*_ft functions will be merged with the standard MPIC_* functions and will replace them. Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
The functionality has been replaced by reserving a bit from the tag space to accomplish the same thing without messing up tag matching. Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
All of the *_ft functions now set/check for the error bit in the tag instead of using a completely separate tag to send error notifications. Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
When appropriate, the error bit should not be part of the tag space when matching. This isn't always necessary. For pt2pt messages, the error bit will never be set so the masking isn't necessary. This change has minimal measured effect on matching times. Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
These macros are used to manipulate the error bit that has been added to the tag space to propagate error notification on top of other communication. Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
The highest bit of tag space will now be reserved for failure notification. We are far above the required 32767, so this shouldn't be a problem. Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
- 24 Jul, 2013 1 commit
-
-
Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
- 23 Jul, 2013 2 commits
-
-
Antonio J. Pena authored
Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
Rob Latham authored
This parameter gets allocated and broadcasted but near as I can tell it's never actually used for anything.
-
- 22 Jul, 2013 1 commit
-
-
Ken Raffenetti reported the default GNU patch for FreeBSD is too old to recognise the --no-backup-if-mismatch flag. This fix switches to a manual removal approach. Signed-off-by:
Ken Raffenetti <raffenet@mcs.anl.gov>
-
- 19 Jul, 2013 4 commits
-
-
Cleaned up spaces-tabs mismatch in patch file, and fixed a few parameters for the patch command. Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
In MPIDI_CH3I_Win_allocate_shared, if the size of shared memory segment is 0, we just set window's base to NULL, do not allocate shared memory segment and mutex memory region. In MPIDI_CH3I_SHM_Win_free, we detach the shared memory segment and mutex memory region only when the size of shared memory segment is not 0. Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
MPICH currently has a bug that causes it to abort when all processes provide zero bytes to the window allocation routine. While it can be considered a user error, the MPI-3 standard does not explicitly disallow this case.
-
MPIR_ERRTEST_ARGNULL is used in MPI_Get_accumulate and MPI_Rget_accumulate to verify that the address of a buffer is not NULL. However, a NULL buffer is valid when the count is zero or when a derived datatype of size 0 is used. Signed-off-by:
Jeff Hammond <jhammond@alcf.anl.gov>
-
- 18 Jul, 2013 6 commits
-
-
Pavan Balaji authored
strict builds no longer do gcc-specific things. We test each option to see if the compiler accepts them before using it.
-
Pavan Balaji authored
This program tests to make sure we can do zero-count or zero-size datatype RMA tests without the MPI library throwing errors.
-
Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
Patching libtool.m4 from autogen.sh to add compatibility with the NAG Fortran compiler plus shared libraries. Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
- 17 Jul, 2013 1 commit
-
-
Pavan Balaji authored
This covers a small part of ticket #1835.
-
- 16 Jul, 2013 3 commits
-
-
Rob Latham authored
Since different file systems have different default hints, make a start at being a bit more sophisticated with respect to what we should compare against. If no arguments given, file_info will simply test that hints set can be retrieved. If given the -b (bluegene) or -u (unix file system) flag, file_info will check those default values. todo: add pvfs, lustre, and other file systems of interest. fixes tt #1810
-
-
(ibm) D191388 : MPICOM case with mpich2 hit Assertion failed issue (ibm) AIX71J Signed-off-by:
Charles Archer <archerc@us.ibm.com>
-