Re: [OMPI devel] 1.8.4rc2 now available for testing

I’ll raise the point at our Tues telecon and see who among them might have the cycles to address this as I’ll be on the road with limited time over the next week, and then we’ll be hitting the holidays. > On Dec 13, 2014, at 11:12 AM, Eric Chamberland >

[OMPI devel] 1.8.4rc4 now out for testing

Hi folks I’ve rolled up the bug fixes so far, including the thread-multiple performance fix. So please give this one a whirl http://www.open-mpi.org/software/ompi/v1.8/ Ralph

Re: [OMPI devel] 1.8.4rc2 now available for testing

On 12/12/2014 01:12 PM, Ralph Castain wrote: I just checked it with —enable-memchecker —with-valgrind and found that many of these are legitimate leaks. We can take a look at them, though as I said, perhaps may wait for 1.8.5 as I wouldn’t hold up 1.8.4 for it. wait! When end-developpers of

Re: [OMPI devel] autogen broken

FWIW: I'm thinking that this is a bug in Libtool 2.4.3/2.4.4. See https://github.com/open-mpi/ompi/issues/311#issuecomment-66885102 for more details. On Dec 9, 2014, at 11:54 AM, Nick Papior Andersen wrote: > Yes, I know, but it might give a clue as to what goes wrong

Re: [OMPI devel] Patch proposed: opal_set_using_threads(true) in ompi/runtime/ompi_mpi_init.c is called to late

The source of this annoyance is the widely spread usage of OMPI_ENABLE_THREAD_MULTIPLE as an argument for all of the component init calls. This is obviously wrong as OMPI_ENABLE_THREAD_MULTIPLE is not about the requested support of thread support but about the less restrictive thread level