Re: [OMPI users] OpenMPI with bounds checking

2008-06-24 Thread Jeff Squyres
On Jun 24, 2008, at 4:44 AM, Gabriele Fatigati wrote: sorry for the delay. When i have little time, i'll check OMPI trunck with bound checking. When is the deliver date of 1.3 version? "Soon". With so many different organizations working together, it's difficult to predict the exact date.

Re: [OMPI users] OpenMPI with bounds checking

2008-06-24 Thread Gabriele Fatigati
Hi Jeff, sorry for the delay. When i have little time, i'll check OMPI trunck with bound checking. When is the deliver date of 1.3 version? 2008/6/20 Jeff Squyres : > On Jun 19, 2008, at 11:47 AM, Gabriele Fatigati wrote: > > i didn't compile OpenMPI with bounds checking, but only my application

Re: [OMPI users] OpenMPI with bounds checking

2008-06-20 Thread Jeff Squyres
On Jun 19, 2008, at 11:51 AM, Gabriele Fatigati wrote: >does the gcc bounds checking stuff give you the possibility of saying "this memory is ok"? I think yes. How does one do so? It may be worthwhile to expand our support for gcc bounds checking (i.e., beyond just valgrind). The valgri

Re: [OMPI users] OpenMPI with bounds checking

2008-06-20 Thread Jeff Squyres
On Jun 19, 2008, at 11:47 AM, Gabriele Fatigati wrote: i didn't compile OpenMPI with bounds checking, but only my application. Problems with OMPI compiled with bound checking remains. Were you checking only with the OMPI 1.2 series? If so, is there a chance you could test with the OMPI tru

Re: [OMPI users] OpenMPI with bounds checking

2008-06-19 Thread Gabriele Fatigati
>does the gcc bounds checking stuff give you the possibility of saying "this memory is ok"? I think yes. 2008/6/19 Gabriele Fatigati : > Just a moment: > > i didn't compile OpenMPI with bounds checking, but only my application. > Problems with OMPI compiled with bound checking remains. > > > 20

Re: [OMPI users] OpenMPI with bounds checking

2008-06-19 Thread Gabriele Fatigati
Just a moment: i didn't compile OpenMPI with bounds checking, but only my application. Problems with OMPI compiled with bound checking remains. 2008/6/19 Jeff Squyres : > On Jun 19, 2008, at 11:25 AM, Gabriele Fatigati wrote: > > Hi Jeff, >> i solved using Gigabit net and eth1 interface! >> >>

Re: [OMPI users] OpenMPI with bounds checking

2008-06-19 Thread Jeff Squyres
On Jun 19, 2008, at 11:25 AM, Gabriele Fatigati wrote: Hi Jeff, i solved using Gigabit net and eth1 interface! So, there are problems beetween Infiniband and gcc with bound checking. This is probably not too surprising -- the IB driver gives back memory to the process that didn't come fro

Re: [OMPI users] OpenMPI with bounds checking

2008-06-19 Thread Gabriele Fatigati
Hi Jeff, i solved using Gigabit net and eth1 interface! So, there are problems beetween Infiniband and gcc with bound checking. 2008/6/17 Jeff Squyres : > I'm afraid that we've never tested OMPI under these conditions; I don't > know exactly what xgcc is testing for, so I don't know why it would

Re: [OMPI users] OpenMPI with bounds checking

2008-06-17 Thread Gabriele Fatigati
Hi Jeff, i compiled OpenMPi using xgcc 4.0.2. I noted that the program stops before to do process spawn. Very strange. 2008/6/17 Jeff Squyres : > I'm afraid that we've never tested OMPI under these conditions; I don't > know exactly what xgcc is testing for, so I don't know why it would fail. >

Re: [OMPI users] OpenMPI with bounds checking

2008-06-17 Thread Jeff Squyres
I'm afraid that we've never tested OMPI under these conditions; I don't know exactly what xgcc is testing for, so I don't know why it would fail. There could be weird interactions between the OFED stack and xgcc...? (i.e., memory "appears" from the kernel via ibv_* function calls, etc.)

[OMPI users] OpenMPI with bounds checking

2008-06-14 Thread Gabriele Fatigati
Hi Open MPI developers, I compiled OpenMPI 1.2.6 with xgcc, a gcc version with bounds-checking support. But i have a problem with a simply MPI application compiled with -fbounds-checking flags. The job doesn't works and it is locked to MPI_Init(), doing nothing. It is a very strange behaviour. I