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
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_SIZEOF_FORTRA
On Jul 30, 2012, at 15:29 , Ralph Castain wrote:
>
> On Jul 30, 2012, at 2:37 AM, George Bosilca wrote:
>
>> I think that as long as there is a single home area per cluster the
>> difference between the different approaches might seem irrelevant to most of
>> the people.
>
> Yeah, I agree -
I haven't used SGE or Oracle Grid Engine in ages, but apparently it is now
called Open Grid Engine
http://gridscheduler.sourceforge.net/
-Original Message-
From: devel-boun...@open-mpi.org [mailto:devel-boun...@open-mpi.org] On
Behalf Of Rayson Ho
Sent: Friday, July 27, 2012 8:25 AM
To: O
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. The
There's a compile error in the ud oob right now. I tried a few different ways
to fix it, but I'm still consistently getting segv's.
-
[svbu-mpi046:02934] wc status = 2
[svbu-mpi046:02934] *** Process received signal ***
[svbu-mpi046:02934] Signal: Segmentation fault (11)
[svbu-mpi046:02934
