[OMPI devel] [2.0.0rc] memory:patcher fragility

2016-05-06 Thread Paul Hargrove
I noticed that opal/mca/memory/patcher/memory_patcher_component.c includes without ever checking (not even in the .m4 fragment) that this header exists. At the moment, AIX is the only O/S I've encountered that doesn't have a sys/syscall.h. However, I think the possibility of others needs to be co

[OMPI devel] [2.0.0rc2] opal/mca/timer/aix?

2016-05-06 Thread Paul Hargrove
I see opal/mca/timer/aix is still around in 2.0.0rc2. Does that mean Open MPI is expected to run on AIX, or is this directory an orphan? I have access to AIX-7.1.3 on Power7 h/w, and found that 2.0.0rc does NOT build there out of the box. Does anybody care? -Paul -- Paul H. Hargrove

Re: [OMPI devel] [PATCH] Fix for xlc-13.1.0 ICE (hwloc)

2016-05-06 Thread Brice Goglin
Thanks I think I would be fine with that fix. Unfortunately I won't have a good internet access until sunday night. I won't be able to test anything properly earlier :/ Le 06/05/2016 00:29, Paul Hargrove a écrit : > I have some good news: I have a fix!! > > FWIW: I too can build w/ xlc 12.1 (al

[OMPI devel] [v2.x] printf format warnings w/ -m32

2016-05-06 Thread Paul Hargrove
The 96 printf format warnings in the attachment come from an Linux/x86-64 system w/ Clang and "-m32". Some of the warnings are "size_t" vs "unigned long", which is harmless since both are 32-bits. However, there are several cases in sharedfp/sm where a 64-bit (long long) format has a 32-bit (long

[OMPI devel] [v2.x] Harmless type conversion warnings from Clang

2016-05-06 Thread Paul Hargrove
I don't think any of the warnings below indicate errors. However, each could probably be suppressed with an appropriate cast. -Paul /scratch/phargrov/OMPI/openmpi-v2.x-dev-1410-g81e0924-linux-x86_64-clang/openmpi-gitclone/opal/mca/memory/patcher/memory_patcher_component.c:370:34: warning: passing

Re: [OMPI devel] [v2.x] more "patcher" issues

2016-05-06 Thread Paul Hargrove
BIG-endian PPC64 w/ xlc V13.1 experiences a nearly identical failure. However, this time gdb appears to have been able to resolve frame #0 to a PLT slot (instead of "??"). -Paul #0 0x0fff8904ef88 in 0010.plt_call.opal_mem_hooks_release_hook+0 () from /gpfs-biou/phh1/OMPI/openmpi-v2.x-

Re: [OMPI devel] [v2.x] more "patcher" issues

2016-05-06 Thread George Bosilca
We are getting extremely frequent C++ application deadlocks with the new patcher. We are still investigating. George. On Fri, May 6, 2016 at 12:14 PM, Paul Hargrove wrote: > I am testing a tarball built from v2.x-dev-1410-g81e0924 > This includes pull request #1128 in which Nathan addressed

[OMPI devel] [v2.x] more "patcher" issues

2016-05-06 Thread Paul Hargrove
I am testing a tarball built from v2.x-dev-1410-g81e0924 This includes pull request #1128 in which Nathan addressed multiple "patcher" issues. However, I see the crash below in dlopen_test on a LITTLE-ENDIAN Power8 system. This is happening when built with "V13.1.2 (5725-C73, 5765-J08)", but not w

Re: [OMPI devel] [2.0.0rc2] xlc-13.1.0 ICE (hwloc)

2016-05-06 Thread Josh Hursey
Brice: Can you take a look at Paul's patch here: https://www.open-mpi.org/community/lists/devel/2016/05/18918.php Thanks, Josh On Thu, May 5, 2016 at 4:28 PM, Jeff Squyres (jsquyres) wrote: > On May 5, 2016, at 5:27 PM, Josh Hursey wrote: > > > > Since this also happens with hwloc 1.11.3 s

Re: [OMPI devel] [2.0.0rc2] build failures on OpenBSD-5.7 (romio)

2016-05-06 Thread Paul Hargrove
Gilles, I am testing and will follow-up in the PR. -Paul On Thu, May 5, 2016 at 11:02 PM, Gilles Gouaillardet wrote: > Paul, > > > can you please give a try to > https://patch-diff.githubusercontent.com/raw/open-mpi/ompi/pull/1643.patch > ? > > > Cheers, > > > Gilles > > On 5/3/2016 2:21 PM, P

Re: [OMPI devel] [2.0.0rc2] build failures on OpenBSD-5.7 (romio)

2016-05-06 Thread Gilles Gouaillardet
Paul, can you please give a try to https://patch-diff.githubusercontent.com/raw/open-mpi/ompi/pull/1643.patch ? Cheers, Gilles On 5/3/2016 2:21 PM, Paul Hargrove wrote: This is NOT a new issue, but I wanted to mention it explicitly once again since no progress has been made since I firs

Re: [OMPI devel] Question about 'progress function'

2016-05-06 Thread Nathan Hjelm
The return code of your progress function should be related to the activity (send, recv, put, get, etc completion) on your network. The return is not really used right now but may be meaningful in the future. Your BTL signals progress through two mechanisms: 1) Send completion is indicated by e

[OMPI devel] [2.0.0rc2] Solaris Studio 12.5-beta build failure (libtool, w/ patch)

2016-05-06 Thread Paul Hargrove
Disclamer first: Yes, I am testing a *beta* compiler but this is NOT about a compiler bug. I leave it to the judgment of others whether my findings warrant any action. I am testing the 2.0.0rc2 tarball with the Oracle Solaris Studio 12.5-beta for Linux. With Studio 12.4 all is fine on the same s

Re: [OMPI devel] Question about 'progress function'

2016-05-06 Thread dpchoudh .
George Thanks for your help. But what should the progress function return, so that the event is signalled? Right now I am returning a 1 when data has been transmitted and 0 otherwise, but that does not seem to work. Also, please keep in mind that the transport I am working on supports unreliable d