Shirley. :-)
On Jun 7, 2013, at 1:07 PM, Thomas Naughton wrote:
> Hi,
>
> It looks like an auto-generated 'install-sh' was accidentally added to SVN
> under libevent in OPAL:
>
>ompi-trunk/opal/mca/event/libevent2021/libevent/install-sh
>
> Ok, to remove it?
> --tjn
>
> ___
Hi,
It looks like an auto-generated 'install-sh' was accidentally added to SVN
under libevent in OPAL:
ompi-trunk/opal/mca/event/libevent2021/libevent/install-sh
Ok, to remove it?
--tjn
_
Thomas Naughton
Perhaps I was wrong -- I thought we had no static initializer because there was
no static initializer for mutexes in windows.
On Jun 7, 2013, at 9:28 AM, George Bosilca wrote:
> Im curious to know why Windows support is to be blamed for the lack of such
> functionality?
>
> George.
>
> O
Im curious to know why Windows support is to be blamed for the lack of such
functionality?
George.
On Jun 7, 2013, at 18:08 , Jeff Squyres (jsquyres) wrote:
> Nathan forgot to mention that we didn't have this before because of Windows.
> But now we don't have Windows support, so...
>
>
>
Nathan forgot to mention that we didn't have this before because of Windows.
But now we don't have Windows support, so...
On Jun 7, 2013, at 9:01 AM, "Hjelm, Nathan T" wrote:
> What: Add a static initializer for opal_mutex_t for both posix and solaris
> threads.
>
> Why: Enables the use of
What: Add a static initializer for opal_mutex_t for both posix and solaris
threads.
Why: Enables the use of opal locks that don't have to be OBJ_CONSTRUCT'ed.
When: This is a trivial addition but I would like some review/testing of the
code (I don't have solaris). Setting timeout to Tuesday, Ju
Yes - thanks!
One note about the threading changes. We will need to sequence those a bit.
IIRC, the current OOB isn't happy when you turn on opal thread support and can
"wedge" itself. I also suspect we'll want the MPI_Waitall fix before we enable
thread multiple by default.
On Jun 7, 2013, a
I updated the notes -- better now?
On Jun 6, 2013, at 10:09 AM, Ralph Castain wrote:
> Hmmmthere seem to be some typos in this posting. For example, you say
> that both I and Aure will do the orte classes for the single-vs-multi thread
> APIs. Could you take a glance thru it and clean up a