This was the result of an unfortunate commit. Starting from revision
r20884 the header file ompi_config.h is not included anymore.
Thanks for the report.
george.
On Mar 25, 2009, at 13:29 , Kiril Dichev wrote:
One remark: after installation, I had to remove the '#include
"ompi_config.h"'
Hi All,
George - I really appreciate the quick response.
> Hi,
>
> at least for the specific test program I used, the negative values for
the peer attribute disappeared after George's modifications in 20844.
Same here for my profiling library - tested with openmpi-1.3.2a1r20855.
>
> One remark:
I did a quick check and I think there is no other possibility to get
the peer equal to -1. Well, at least in theory. Please let me know if
you find any other problems with our PERUSE interface.
Meanwhile, I will take a look at the peruse.h header.
Thanks,
george.
On Mar 25, 2009, at 1
Hi,
at least for the specific test program I used, the negative values for
the peer attribute disappeared after George's modifications in 20844.
One remark: after installation, I had to remove the '#include
"ompi_config.h"' line in the "include/peruse.h" header to get PERUSE
applications to comp
You are absolutely right, the peer should never be set to -1 on any of
the PERUSE callbacks. I checked the code this morning and figure out
what was the problem. We report the peer and the tag attached to a
request before setting the right values (some code moved around). I
submitted a patc
Hi Kiril,
Appreciate the quick response.
> Hi Samuel,
>
> On Sat, 21 Mar 2009 18:18:54 -0600 (MDT)
> "Samuel K. Gutierrez" wrote:
>> Hi All,
>>
>> I'm writing a simple profiling library which utilizes
>>PERUSE. My callback
>
> So am I :)
>
>> function counts communication events (see example
Hi Samuel,
On Sat, 21 Mar 2009 18:18:54 -0600 (MDT)
"Samuel K. Gutierrez" wrote:
Hi All,
I'm writing a simple profiling library which utilizes
PERUSE. My callback
So am I :)
function counts communication events (see example code
below). I noticed
that in OMPI v1.3 spec->peer is sometim
Hi All,
I'm writing a simple profiling library which utilizes PERUSE. My callback
function counts communication events (see example code below). I noticed
that in OMPI v1.3 spec->peer is sometimes a negative value (OMPI v1.2.6
did not exhibit this behavior). I added some boundary checks, but it
