I'm puzzled by your questions as I don't remember that at any past
moment in the lifetime of Open MPI the convertor or datatype was in
OPAL. So I don't see how your "OLD" code could have included "opal/
datatype/convertor.h". This only ended in the 1.3 series starting from
To your last question the short answer is: the obsolete one is the
ompi_convertor. About two months ago, most of the datatype was moved
from the OMPI layer into the OPAL one. When I say most this means
everything not MPI specific was moved in OPAL, everything else was
kept in OMPI. The convertor is MPI agnostic so it ended in OPAL.
On Nov 9, 2009, at 16:33 , Christian Bendele wrote:
> I was porting a 3rd party btl module that was originally written for
> openmpi 1.0.x to the current release.
> Now, even after some googling, I am a little confused about
> ompi_convertor and opal_convertor.
> The OLD code includes opal/datatype/convertor.h and calls several
> functions starting opal_convertor_...(). That header file didn't
> seem to exist in 1.3.3 though.
> The 1.3.3 btl_tcp code I referenced uses ompi_convertor. Thus I
> understood that at some point in history opal_convertor was
> obsoleted and replaced by ompi_convertor.
> It happened so that I overlooked a single occurence of
> opal_convertor_need_buffers() in my code. Although I thought I
> removed all headers related to opal_convertor the code actually
> compiled, and only failed during the linking stage (no such symbol).
> Now since I thought that rather strange (I thought maybe there was
> some obsolete header still astray or something), I checked with
> There I actually found a few rather current patches (e.g. http://www.open-mpi.org/community/lists/devel/2009/07/6457.php
> ) that seem to suggest that actually ompi_datatype is obsoleted in
> favour of opal_datatype...
> Can anybody give me a small overview what's going on here?
> devel mailing list