Could you explain the comment about opal_setenv getting “picky”? You can pass a
flag that tells opal_setenv whether or not to overwrite a pre-existing value,
and it tells you if the value was found (which is exactly what you asked for) -
why isn’t it adequate to just pass a “false” for overwrite
George,
i was able to reproduce the hang with intel compiler 14.0.0
but i am still unable to reproduce it with intel compiler 14.3
i was not able to understand where the issue come from, so
i could not create an appropriate test in configure
at this stage, i can only recommend you update your co
Attaching the test for reproduction.
On Mon, Jan 19, 2015 at 11:48 AM, Alina Sklarevich <
ali...@dev.mellanox.co.il> wrote:
> Dear OMPI community,
>
>
>
> We observe a segmentation fault in our regression testing. Our initial
> investigation shows that It happens for any 1.8.x release and with an
Dear OMPI community,
We observe a segmentation fault in our regression testing. Our initial
investigation shows that It happens for any 1.8.x release and with any
PML/BTL/MTL combo on two processes, when running the MPICH one-sided test,
accumulate-fence test, attached to this report with the fo
Btw,
MPI_Type_hvector(2, 1, 0, MPI_INT, &type);
Is just a weird datatype. Because the stride is 0, this datatype a memory
layout that includes 2 times the same int. I'm not sure this was indeed
intended...
George.
On Mon, Jan 19, 2015 at 12:17 AM, Gilles Gouaillardet <
gilles.gouaill
The extent should not be part of the decision, what matters is the amount
of data to be pushed on the wire, and not it's span in memory.
George.
On Mon, Jan 19, 2015 at 12:17 AM, Gilles Gouaillardet <
gilles.gouaillar...@iferc.org> wrote:
> Adrian,
>
> i just fixed this in the master
> (
> ht
Adrian,
about the
"[n050409][[36216,1],1][btl_openib_xrc.c:58:mca_btl_openib_xrc_check_api] XRC
error: bad XRC API (require XRC from OFED pre 3.12). " message.
this means ompi was built on a system with OFED 3.12 or greater, and you
are running on a system with an earlier OFED release.
please no
Adrian,
i just fixed this in the master
(https://github.com/open-mpi/ompi/commit/d14daf40d041f7a0a8e9d85b3bfd5eb570495fd2)
the root cause is a corner case was not handled correctly :
MPI_Type_hvector(2, 1, 0, MPI_INT, &type);
type has extent = 4 *but* size = 8
ob1 used to test only the
