I keep seeing this when I run ompi_info --all:
**
*** DEVELOPER WARNING: A field in ompi_info output is too long and
*** will appear poorly in the prettyprint output.
***
*** Value: "MCA (disabled) pml monitoring"
***
+1 from IBM on removing the v3.x branch sooner rather than later.
I've switched our MTT and Jenkins setups - so we should be in good shape.
On Wed, May 31, 2017 at 9:57 AM, Barrett, Brian via devel <
devel@lists.open-mpi.org> wrote:
>
> > On May 31, 2017, at 7:52 AM, r...@open-mpi.org wrote:
> >
out of curiosity, why would you want to do that ?
- Original Message -
Is it easy to update ompi_datatype_is_valid to judge invalid
datatypes, such as -1?
Dahai
On Fri, Jun 2, 2017 at 9:00 AM, Gilles Gouaillardet wrote:
MPI_Datatype is a opaque handler, and -1 i
As George pointed out earlier, there is no construct in C able to tell
you if a random number is a valid C pointer, i.e., is a valid memory
address. -1, once casted to a pointer, would correspond to the adress
0x...f .
It would probably be better to ajust the initial code in order to use
Is it easy to update *ompi_datatype_is_valid* to judge invalid datatypes,
such as -1?
Dahai
On Fri, Jun 2, 2017 at 9:00 AM, Gilles Gouaillardet <
gilles.gouaillar...@gmail.com> wrote:
> MPI_Datatype is a opaque handler, and -1 is a (signed) integer, so
> what you are trying is very likely to hav
MPI_Datatype is a opaque handler, and -1 is a (signed) integer, so
what you are trying is very likely to have an undefined behavior per
the standard.
if this seems to work with MPICH, this is not portable anyway, and
will very likely cause a crash with OpenMPI
Cheers,
Gilles
On Fri, Jun 2, 201
so you are saying that a user should NOT define send/recv data type as -1,
in openmpi?
Dahai
On Thu, Jun 1, 2017 at 6:59 PM, Gilles Gouaillardet
wrote:
> +1
>
>
> MPI_Datatype is an opaque handler, and in Open MPI, this is an
> ompi_datatype_t *
>
> so we can only test for NULL pointers or MPI_
