- 31 Oct, 2013 1 commit
-
-
Also includes random fixes to `-Wshorten-64-to-32` warnings which might need to be teased out. Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
- 29 Oct, 2013 19 commits
-
-
Pavan Balaji authored
No reviewer.
-
Pavan Balaji authored
No reviewer.
-
Pavan Balaji authored
We were downgrading void * content to int and then upgrading it back to an MPIR_Pint, losing bits in the process. This worked fine when Fint was just 4 bytes, but not when Fint was 8 bytes. Signed-off-by:
William Gropp <wgropp@illinois.edu>
-
Pavan Balaji authored
When freeing arrays, we were not checking for the case where the array might be set to MPI_WEIGHTS_EMPTY. Signed-off-by:
William Gropp <wgropp@illinois.edu>
-
Pavan Balaji authored
When MPI_Count was added to the status field, a bunch of bogus checks got added into configure and MPI_Init. This patch cleans up these checks. Signed-off-by:
William Gropp <wgropp@illinois.edu>
-
Pavan Balaji authored
An initial version of this patch was provided by Intel. Signed-off-by:
William Gropp <wgropp@illinois.edu>
-
Pavan Balaji authored
Based on an Intel contributed patch. The idea is to use the bits from the cancelled field to extend the count, rather than increasing the count datatype itself. Signed-off-by:
Ken Raffenetti <raffenet@mcs.anl.gov> Fixes to the bit manipulation based on feedback from Artem Yalozo @ Intel. Fixes to the naming convention based on feedback from Bill Gropp. Signed-off-by:
William Gropp <wgropp@illinois.edu>
-
Pavan Balaji authored
This reverts commit 81ad170b . Signed-off-by:
William Gropp <wgropp@illinois.edu>
-
This selects the buildiface option that specifies a specific ordering of the routines in mpicxx.h(.in) in order to provide ABI consistency. Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
For MPICH builds, eliminate the C++ distgraphcomm test. In other cases test for presense of MPI::Distgraphcomm and only include the test if available. Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
Enhanced cxx/buildiface to output support for Distgraphcomm only if requested through the feature interface. Distgraphcomm was added only in MPI 2.2 and for historical reasons is not part of the MPICH ABI. Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
Improve buildiface for C++ to detect an unknown feature request with the -feature= option and abort. Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
In support of the standard ABI, this change allows us to provide the Distgraphcomm support defined in MPI 2.2, as well as support the ABI, which only supports MPI 2.1. This change is not complete in itself; another commit is needed to select the ABI level in configure. Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
Add a way to output the order of function output in mpicxx.h.in file and a way to read in a file specifying the order. This is used to meet ABI needs. Also fixed some old MPI_xxx vs MPI::xxx cases, and the almost duplicated Create_struct call. All in a single commit because the test was against the proposed ABI mpicxx.h.in file Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
Since in mpich_cvars.h, we used a type MPIR_T_cvar_range_value_t, which is defined in mpitimpl.h. Fix #1953 Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
Junchao Zhang authored
The new init. priority order of MPICH cvars is MPICH_* < MPIR_PARAM_* < MPIR_CVAR_* Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
The old code used (void*)(intptr_t)i to pass the thread id i. However intptr_t is C99, so I changed it to (void*)(long)i. Direct usage of (void*)i will issue a compilation warning saying it is dangerous to convert integer to pointer. Fixes #1956 Signed-off-by:
Ken Raffenetti <raffenet@mcs.anl.gov>
-
- 27 Oct, 2013 3 commits
-
-
Pavan Balaji authored
Signed-off-by:
Ken Raffenetti <raffenet@mcs.anl.gov>
-
Pavan Balaji authored
We are calling the next release 3.1rc1. The ABI string has already been updated. No reviewer.
-
Pavan Balaji authored
No reviewer.
-
- 26 Oct, 2013 17 commits
-
-
Pavan Balaji authored
Some content was being printed even when not in verbose mode causing the test to incorrectly fail. Signed-off-by:
Junchao Zhang <jczhang@mcs.anl.gov>
-
Also change src/util/param/params.yml to src/util/cvar/cvars.yml, maint/genparams to maint/gencvars Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
To adapt to naming for control variables in MPI_T. Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
The case is adapted from test/mpi/mpi_t/mpit_vars.c Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
This bug was fixed with the new MPI_T implementation. Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
Now we can control printing using env var MPITEST_VERBOSE. The old code used a local variable 'verbose'. It shades the global variable 'verbose'. So we renamed the local one to 'verb' instead. Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
Since initthread.c is used for MPI_Init_thread(), we'd better use mpit_initthread.c for MPI_T_init_thread(). Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
The old name doesn't confrom to naming convention of other files under mpi_t Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
These two files are renamed to mpich_params.{c, h} since the old ones are not uniform. Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
Signed-off-by:
Pavan Balaji <balaji@mcs.anl.gov>
-
This makes parameters (cvars) conform to MPI_T standard. However, probably the info is too conservative. Need further tuning the info. 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>
-
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>
-