FWIW, here's the v1.3.x bug report we review every week:
https://svn.open-mpi.org/trac/ompi/report/14
I still have one "blocker" bug (coll sm) that seems to creep
asymptotically close to completion but never seems to get all the way
there. :-(
On Sep 28, 2009, at 8:50 AM, Terry Dontje
On Sep 16, 2009, at 9:53 PM, Ralph Castain wrote:
WHAT: change the IPv6 configuration option to enable IPv6 if and
only if specifically requested
WHY: IPv6 support is only marginally maintained, and is currently
broken yet again. The current default setting is causing user
systems to brea
Thanks for your explanation, George. However:
suppose we have leave_pinned = FALSE. Then we go to
mca_mpool_rdma_find. There we try to find suitable registration in the
cache. Suppose we cannot (cache's empty). Then NULL registration is
returned, BTL is skipped and 0 is returned from mca_pml_ob1_rd
On Mon, Sep/28/2009 03:11:46PM, Ethan Mallove wrote:
> On Mon, Sep/28/2009 02:05:14PM, Jeff Squyres wrote:
> > Try a newer compiler than gcc 3.4 -- it's pretty ancient.
>
> I don't get the warning with 4.1.2 either.
To get the warning I needed to enable some developer configure options (e.g.,
mkd
I don't think we need to DECLSPEC it, do we? We don't need (or want)
this symbol to be visible at the link level when user apps link
against libmpi. You might want to put in a comment about why it's not
static so that we don't repeat this conversation again next year. ;-)
I think not hav
The issue isn't why or why not static, Jeff - the issue is that we get
a compiler warning whenever we do a developer build.
On Sep 29, 2009, at 2:32 PM, Jeff Squyres wrote:
I don't think we need to DECLSPEC it, do we? We don't need (or
want) this symbol to be visible at the link level when
On Sep 29, 2009, at 5:30 PM, Ralph Castain wrote:
The issue isn't why or why not static, Jeff - the issue is that we get
a compiler warning whenever we do a developer build.
Right. The initial issue was the static-ness, though -- Ethan removed
the static because some compilers were effecti
