Re: [OMPI devel] MPI_Mprobe

2012-08-09 Thread Eugene Loh
On 8/7/2012 5:45 AM, Jeff Squyres wrote: So the issue is when (for example) Fortran MPI_Recv says "hey, C ints are the same as Fortran INEGERs, so I don't need a temporary MPI_Status buffer; I'll just use the INTEGER array that I was given, and pass it to the back-end C MPI_Recv() routine."

Re: [OMPI devel] MPI_Mprobe

2012-07-31 Thread Eugene Loh
On 7/31/2012 5:15 AM, Jeff Squyres wrote: On Jul 31, 2012, at 2:58 AM, Eugene Loh wrote: The main issue is this. If I go to ompi/mpi/fortran/mpif-h, I see six files (*recv_f and *probe_f) that take status arguments. Normally, we do some conversion between Fortran and C status arguments.

Re: [OMPI devel] MPI_Mprobe

2012-07-31 Thread Jeff Squyres
On Jul 31, 2012, at 2:58 AM, Eugene Loh wrote: > The main issue is this. If I go to ompi/mpi/fortran/mpif-h, I see six files > (*recv_f and *probe_f) that take status arguments. Normally, we do some > conversion between Fortran and C status arguments. These files test if >

[OMPI devel] MPI_Mprobe

2012-07-31 Thread Eugene Loh
I have some questions originally motivated by some mpif-h/MPI_Mprobe failures we've seen in SPARC MTT runs at 64-bit in both v1.7 and v1.9, but my poking around spread out from there. The main issue is this. If I go to ompi/mpi/fortran/mpif-h, I see six files (*recv_f and *probe_f) that take