Re: [OMPI users] MPI_IN_PLACE with GATHERV, AGATHERV, and SCATERV

2013-10-22 Thread Gerlach, Charles A.
The IN_PLACE alterations to my code encompassed GATHERV as well, but as I continued to debug, it appeared more and more as though SCATTERV was the only problem case. So, I do not forsee any GATHER reproducers, but I'll certainly send 'em if I find 'em. I followed the link to the bug-diff, and

Re: [OMPI users] MPI_IN_PLACE with GATHERV, AGATHERV, and SCATERV

2013-10-22 Thread Nathan Hjelm
Ok, I think we have this resolved in trunk and the fix will go into 1.7.4. The check for MPI_IN_PLACE was wrong in the mpif-h bindings. The fix was tested with your reproducer. Both MPI_SCATTER and MPI_SCATTERV had this bug. The bug does not exist in 1.6.x though so I don't know why it was failing

[OMPI users] MPI_THREAD_SINGLE vs. MPI_THREAD_FUNNELED

2013-10-22 Thread Jai Dayal
Hi All, I, for the life of me, can't understand the difference between these two init_thread modes. MPI_THREAD_SINGLE states that "only one thread will execute", but MPI_THREAD_FUNNELED states "The process may be multi-threaded, but only the main thread will make MPI calls (all MPI calls are funn

Re: [OMPI users] MPI_IN_PLACE with GATHERV, AGATHERV, and SCATERV

2013-10-22 Thread Gerlach, Charles A.
My reproducer is below (SCATTERV only). It needs to be compiled with 64-bit default reals, and I'm running on four cores of a single linux86-64 box running SLED 12.3 (except where noted). Using Open-MPI with different compilers: With g95: The non-root procs print the correct values, but the ro