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 :-) ).
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 ?
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