- 18 May, 2013 9 commits
-
-
Pavan Balaji authored
No reviewer.
-
Pavan Balaji authored
We have been allocating a "large enough" pool of temporary strings and hoping that we don't overflow it for our temporary allocations. This commit provides macros that better check for overflow problems without making the code too clumsy. No reviewer.
-
With MS-MPI 64-bit from HPC Pack 2008 and 2012, MPI_Attr_get returns error code 773 when called from delete_fn on a communicator obtained from MPI_Comm_split. The standard is not explicit that the 'comm' argument of delete_fn must be valid, so this test is only in effect when !USE_STRICT_MPI. Signed-off-by:
Jed Brown <jedbrown@mcs.anl.gov> Signed-off-by:
Satish Balay <balay@mcs.anl.gov>
-
The old method attempts to create a failed compile when the function *is* already declared, by creating an incompatible declaration. That is insufficient with clang-3.2, which only warns in case of incompatible redeclaration of a library function: conftest.c:44:5: warning: incompatible redeclaration of library function 'strncmp' int strncmp(double, int, double, const char *); ^ /usr/include/string.h:143:12: note: 'strncmp' is a builtin with type 'int (const char *, const char *, size_t)' extern int strncmp (const char *__s1, const char *__s2, size_t __n) ^ 1 warning generated. Instead, we take the opposite approach, generating a failed compile when the library function has *not* been declared in the header. void (*fptr)(void) = (void(*)(void))strncmp; Signed-off-by:
Jed Brown <jedbrown@mcs.anl.gov>
-
(ibm) D189371 (ibm) b02a38e0680dbd1471884439214ee6afe13baeb4 (ibm) c8ebe0da80732297de985c3640caa4c5623c55d4 (ibm) 48d1993041c3820a468d2ee6c838ff0a5bc1154a
-
1 - Fixes for command line paramters 2 - Fix for allgather PAMI_IN_PLACE handling in collective selection path (ibm) D189995 (ibm) 7Z8 (ibm) bad205a6147cebce9a40f3b50560df80d3ddb354 Signed-off-by:
Michael Blocksome <blocksom@us.ibm.com>
-
+ build fix (ibm) D189887 (ibm) 556b0b576c22ef4cc8b745d2ebc57bf4cf354818 (ibm) cee6d5876ad57094c8631e6c3faaef1bb213377a Signed-off-by:
Michael Blocksome <blocksom@us.ibm.com>
-
(ibm) D189889 (ibm) 7Z8 (ibm) b987ee6281ea76879793f596a0f6c93c425716d7 Signed-off-by:
Michael Blocksome <blocksom@us.ibm.com>
-
1 - A fix where all (v) algorithms are disabled in collective selection and only (v)_int algorithms are enabled since MPICH only supports (v)_int algorithms. IN the tune case, (v) collectives are skipped even if user selected them. Also a warning message is displayed to stderr if infolevel is >= 1 in collective selection and tuning cases. 2 - Another fix for one task geometries where the fast_query object was not initialized but was still used and may cause core dump. (ibm) D189887 (ibm) 7Z8 (ibm) 0ea3f16a9fd6e2fbc1cfffeb5401cce20a861e96 Signed-off-by:
Michael Blocksome <blocksom@us.ibm.com> This is the 2nd commit message: BGQ build break fix
-
- 17 May, 2013 8 commits
-
-
Pavan Balaji authored
Reviewed by Charles Archer @ IBM.
-
(ibm) D188808 (ibm) 2021904184004ba65cb4f277d01dc88b47d692bc Signed-off-by:
Bob Cernohous <bobc@us.ibm.com> Modified significantly by Pavan Balaji to utilize mpich infrastructure more consistently for all SMP collectives. Reviewed by Charles Archer @ IBM.
-
Pavan Balaji authored
Reviewed by Charles Archer @ IBM.
-
Pavan Balaji authored
Reviewed by Charles Archer @ IBM.
-
Pavan Balaji authored
configure option. Reviewed by Charles Archer @ IBM.
-
Pavan Balaji authored
Reviewed by Charles Archer @ IBM.
-
Pavan Balaji authored
Reviewed by Charles Archer @ IBM.
-
Pavan Balaji authored
All CH3 parameters start with CH3_ now. All nemesis parameters start with NEMESIS_. For netmod specific parameters, we use NEMESIS_<netmod>_. Reviewed by Charles Archer @ IBM.
-
- 16 May, 2013 1 commit
-
-
Pavan Balaji authored
No reviewer.
-
- 15 May, 2013 17 commits
-
-
-
(ibm) D190238 (ibm) 1fe9a013d48ef38d1505dd96977fbe105b2a2b90 Signed-off-by:
Michael Blocksome <blocksom@us.ibm.com> This is the 2nd commit message: BGQ build break fix
-
(ibm) D189842 (ibm) 7Z8 (ibm) b4718cf2b8bf3ddb7d39e2fdf7aee7b87eac8e1f Signed-off-by:
Michael Blocksome <blocksom@us.ibm.com>
-
(ibm) D189842 (ibm) 7Z8 (ibm) 017c9d99634bcfb225c4ede785709e3f3644a193 (ibm) a42fc06e0ed99acd968fc18405199bc98e5b1190 (ibm) 5326308445643a91cdd15ec7b402285aef9095e4 Signed-off-by:
Michael Blocksome <blocksom@us.ibm.com>
-
(ibm) D189968 (ibm) 4260cf9294bc75af0cb175823885f20d1d2b1ee8 Signed-off-by:
Michael Blocksome <blocksom@us.ibm.com>
-
(ibm) D189791 (ibm) 921af973d312be39763878d9478bea10187ad762 Signed-off-by:
Michael Blocksome <blocksom@us.ibm.com>
-
(ibm) D189783 (ibm) 769e26acc31c01fdda183fe86f871df73504064c Signed-off-by:
Michael Blocksome <blocksom@us.ibm.com>
-
* pami_tune's -v flag conflicts with poe's -v flag. * Disable -x flag for checkpoint mode until later (ibm) D189881 (ibm) 749763c4d0c973739c356d59d561df6feb40aad3 Signed-off-by:
Michael Blocksome <blocksom@us.ibm.com>
-
-
(ibm) D189828 (ibm) 51d29ce7faf74d2d2c8a02798cd7880e1a5f3783 Signed-off-by:
Michael Blocksome <blocksom@us.ibm.com>
-
(ibm) D189833 (ibm) 7Z8 (ibm) 9e89a54cd839c58e0c0573b09f39e4adf6e012e3 Signed-off-by:
Michael Blocksome <blocksom@us.ibm.com>
-
(ibm) D189766 (ibm) 623ef12fe24e80752c51b38db46926520e530136 Signed-off-by:
Michael Blocksome <blocksom@us.ibm.com>
-
Rob Latham authored
-
Rob Latham authored
maddeningly we cannot dup MPI_INFO_NULL, so let's check for that case
-
Pavan Balaji authored
Reviewed by Mike Blocksome @ IBM.
-
Pavan Balaji authored
We now provide two types of function pointers: _sched and _req. The _sched functions just add instructions to the schedule, but no request is created. The _req functions return an MPID request. Reviewed by Mike Blocksome @ IBM.
-
The following collectives are updated: MPIX_Ibcast MPIX_Iallgather MPIX_Iallgatherv MPIX_Iallreduce MPIX_Ialltoall MPIX_Ialltoallv MPIX_Ialltoallw MPIX_Iexscan MPIX_Igather MPIX_Igatherv MPIX_Ireduce_scatter_block MPIX_Ireduce_scatter MPIX_Ireduce MPIX_Iscan MPIX_Iscatter MPIX_Iscatterv These collectives are updated similar to how the optimized MPIX_Ibarrier is implemented: | The previous MPIR_Ibarrier_impl() function forced all adi implementations | to create a MPID_Sched_t opaque object which was then passed in to the | specific ibarrier implementation via a function pointer table. | | The MPID_Sched_t object represents a completely new state machine that | must be advanced whenever mpi progress is made. | | The required construction of the MPID_Sched_t object and the required | advance of the schedule state machine would be extremely detrimental to | pamid performance. (ibm) 47b497e15cd87df666c6031a28f5f8a5ae53cece (ibm) aee872eb91f4300066957349e5a3d8103da33f40 Signed-off-by:
Charles Archer <archerc@us.ibm.com>
-
- 14 May, 2013 4 commits
-
-
Pavan Balaji authored
No reviewer.
-
Pavan Balaji authored
This is an important warning flag, but given the number of places we are breaking this in mpich, it is causing us to miss other warnings. This is meant to be a temporary disabling. No reviewer.
-
(ibm) D190161 (ibm) 55566af07e7d69df17005e50c783ff3ae26cc325 Signed-off-by:
Michael Blocksome <blocksom@us.ibm.com>
-
Rob Latham authored
In response to IBM's integration ticket 1822 (but reworked), turn MPIO_CHECK_INFO into a collective macro; exchange result of info inspection with all procs. Now a bogus info on one proc won't cause a process hang.
-
- 13 May, 2013 1 commit
-
-
(ibm) D186334 (ibm) 7Z6 (ibm) 63716b02ccab7cd99116e927a210eca43b03d52e Signed-off-by:
Michael Blocksome <blocksom@us.ibm.com>
-