Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Development mailing list

Subject: Re: [OMPI devel] possible bugs and unexpected values in returned errors classes
From: Lisandro Dalcin (dalcinl_at_[hidden])
Date: 2009-12-09 10:59:40

It seems that this issue got lost.

On Thu, Feb 12, 2009 at 9:02 PM, Jeff Squyres <jsquyres_at_[hidden]> wrote:
> On Feb 11, 2009, at 8:24 AM, Lisandro Dalcin wrote:
>> Below a list of stuff that I've got by running mpi4py testsuite.
>> 4)  When passing MPI_WIN_NULL, MPI_Win_get_errhandler() and
>> MPI_Win_set_errhandler()  DO NOT fail.
> I was a little more dubious here; the param checking code was specifically
> checking for MPI_WIN_NULL and not classifying it as an error.  Digging to
> find out why we did that, the best that I can come up with is that it is
> *not* an error to call MPI_File_set|get_errhandler on MPI_FILE_NULL (to set
> behavior for what happens when FILE_OPEN fails); I'm *guessing* that we
> simply copied the _File_ code to the _Win_ code and forgot to remove that
> extra check.
> I can't find anything in MPI-2.1 that says it is legal to call set|get
> errhandler on MPI_WIN_NULL.  I checked LAM as well; LAM errors in this case.
>  So I made this now be an error in OMPI as well.
> Do you need these in the 1.3 series?  Or are you ok waiting for 1.4
> (assuming 1.4 takes significantly less time to release than 1.3 :-) ).

In short:

When passing MPI_WIN_NULL, MPI_Win_get_errhandler() and
MPI_Win_set_errhandler() DO NOT fail.

Jeff, you promised this for 1.4 ;-). Any chance for 1.4.1 ?

Lisandro Dalcín
Centro Internacional de Métodos Computacionales en Ingeniería (CIMEC)
Instituto de Desarrollo Tecnológico para la Industria Química (INTEC)
Consejo Nacional de Investigaciones Científicas y Técnicas (CONICET)
PTLC - Güemes 3450, (3000) Santa Fe, Argentina
Tel/Fax: +54-(0)342-451.1594