On Apr 30, 2012, at 2:04 PM, Leif Lindholm wrote:
> My only question mark was with regards to the lack of out-of-line assembly
> implementations for the older architecture versions (as in "I don't know
> whether people would care about that or not").
>
> It does apply cleanly-ish (non-interacti
My only question mark was with regards to the lack of out-of-line assembly
implementations for the older architecture versions (as in "I don't know
whether people would care about that or not").
It does apply cleanly-ish (non-interactively) on top of 1.5.5, but I don't know
if any further drops
Can you send me a copy of the warnings, or tell me which machine at LANL is
generating them? I'm working on libevent now (found a bug they are helping
with) and can take a look at it.
On Apr 25, 2012, at 11:05 AM, Nathan Hjelm wrote:
> Let me take a look. The code in question is in evutil.c an
I'm good with it as long as you guys are.
Re the "...for now" comment; does this imply that you're going to do more later?
BTW, I assume this is for trunk and the v1.6 branch, right?
On Apr 30, 2012, at 9:47 AM, Leif Lindholm wrote:
> Thanks,
>
> I'm happy for this to go in - Jeff?
>
> /
>
Thanks,
I'm happy for this to go in - Jeff?
/
Leif
> -Original Message-
> From: nave.notn...@gmail.com [mailto:nave.notn...@gmail.com] On Behalf
> Of Evan Clinton
> Sent: 30 April 2012 05:12
> To: Leif Lindholm
> Cc: Open MPI Developers; Jeffrey Squyres
> Subject: Re: [OMPI devel] [P
Thanks again for the comments.
>> Quote the documentation, __kuser_cmpxchg "already includes memory
>> barriers as needed," so the code using it shouldn't need anything
>> extra.
>
> Fair enough - but could you put a comment to this effect into the patch?
Comment added.
> But I'm still not too ha
