Re: [OMPI users] Problems building Open MPI 1.4.1 with Pathscale

2010-02-10 Thread Terry Dontje
Jeff Squyres wrote: Iain did the genius for the new assembly. Iain -- can you respond? Iain is on vacation right now so he probably want be able to respond until next week. --td On Feb 9, 2010, at 5:44 PM, Mostyn Lewis wrote: The old opal_atomic_cmpset_32 worked: static inline int

Re: [OMPI users] Problems building Open MPI 1.4.1 with Pathscale

2010-02-10 Thread Ake Sandgren
On Tue, 2010-02-09 at 14:44 -0800, Mostyn Lewis wrote: > The old opal_atomic_cmpset_32 worked: > > static inline int opal_atomic_cmpset_32( volatile int32_t *addr, > unsigned char ret; > __asm__ __volatile__ ( > SMPLOCK "cmpxchgl %1,%2 \n\t" >

Re: [OMPI users] Problems building Open MPI 1.4.1 with Pathscale

2010-02-10 Thread Jeff Squyres
On Feb 10, 2010, at 7:47 AM, Ake Sandgren wrote: > According to people who knows asm statements fairly well (compiler > developers), it should be > static inline int opal_atomic_cmpset_32( volatile int32_t *addr, > int32_t oldval, int32_t newval) > { >

Re: [OMPI users] Problems building Open MPI 1.4.1 with Pathscale

2010-02-10 Thread Ake Sandgren
On Wed, 2010-02-10 at 08:21 -0500, Jeff Squyres wrote: > On Feb 10, 2010, at 7:47 AM, Ake Sandgren wrote: > > > According to people who knows asm statements fairly well (compiler > > developers), it should be > > > static inline int opal_atomic_cmpset_32( volatile int32_t *addr, > >

Re: [OMPI users] openmpi fails to terminate for errors/signals on some but not all processes

2010-02-10 Thread Douglas Guptill
Hello Lawrence: If I correctly remember your code which created this problem, perhaps you could solve it by using the iostatus parameter: read(unit,*,iostatus=ierror) some_variable if (ierror.ne.0) then c handle error endif Hope that helps, Douglas. On Mon, Feb 08, 2010 at 01:29:38PM

Re: [OMPI users] Problems building Open MPI 1.4.1 with Pathscale

2010-02-10 Thread Barrett, Brian W
Adding the memory and cc will certainly do no harm, and someone tried to remove them as an optimization. I wouldn't change the input and output lines - the differences are mainly syntactic sugar. Brian On Feb 10, 2010, at 7:04 AM, Ake Sandgren wrote: > On Wed, 2010-02-10 at 08:21 -0500, Jeff

Re: [OMPI users] Problems building Open MPI 1.4.1 with Pathscale

2010-02-10 Thread Ake Sandgren
On Wed, 2010-02-10 at 08:42 -0700, Barrett, Brian W wrote: > Adding the memory and cc will certainly do no harm, and someone tried to > remove them as an optimization. I wouldn't change the input and output lines > - the differences are mainly syntactic sugar. Gcc actually didn't like the

[OMPI users] orte-checkpoint hangs

2010-02-10 Thread Addepalli, Srirangam V
I am trying to test orte-checkpoint with a MPI JOB. It how ever hangs for all jobs. This is how i submit the job is started mpirun -np 8 -mca ft-enable cr /apps/nwchem-5.1.1/bin/LINUX64/nwchem siosi6.nw >From another terminal i try the orte-checkpoint ompi-checkpoint -v --term 9338

[OMPI users] parameters for newer IB card on older OpenMPI

2010-02-10 Thread Brock Palen
We added some Qlogic IB to our system that is newer than our MPI that we are running (1.3.2) When we run we get an (expected) warning about tuning options: -- WARNING: No preset parameters were found for the device that

Re: [OMPI users] parameters for newer IB card on older OpenMPI

2010-02-10 Thread Jeff Squyres
On Feb 10, 2010, at 3:14 PM, Brock Palen wrote: > Is there any reason I can not unpack a newer MPI and backport the > config for these newer cards to this version of openMPI? That should be fine. You can probably just copy the .ini file from newer Open MPI to your installation. I don't