Thanks! Good catch.
George
On Nov 16, 2010, at 18:26, Tim Mattox wrote:
> I see a bug in this code fragment:
>
> +#define MEMMOVE(d, s, l) \
> +do { \
> +if( (((d) < (s)) && (((d) + (l)) > (s))) ||
I see a bug in this code fragment:
+#define MEMMOVE(d, s, l) \
+do { \
+if( (((d) < (s)) && (((d) + (l)) > (s))) || \
+(((s) < (d)) && (((s) + (l)) > (s))) ) { \
+memmov
Dear awesome community,
Over the last months, I closely followed the evolution of bug 2043,
entitled 'sm BTL hang with GCC 4.4.x'.
https://svn.open-mpi.org/trac/ompi/ticket/2043
The reason is that I am developping an MPI-based software, and I use
Open-MPI as it is the only implementation I am a
On Tue, Nov 16, 2010 at 1:23 AM, Sylvain Jeaugey
wrote:
> On Mon, 15 Nov 2010, Ralph Castain wrote:
>
> Guess I am a little confused. Every MPI process already has full knowledge
>> of what node all other processes are located on - this has been true for
>> quite a long time.
>>
> Ok, I didn't se
On Mon, 15 Nov 2010, Ralph Castain wrote:
Guess I am a little confused. Every MPI process already has full knowledge
of what node all other processes are located on - this has been true for
quite a long time.
Ok, I didn't see that.
Once my work is complete, mpirun will have full knowledge of
