[OMPI devel] Check AUTHORS file update

All OMPI organizations -- I just updated the trunk AUTHORS file with names and affiliations on all SVN ID's that have had commits on the trunk. Please check the spellings of all names and the affiliations for those who have moved between multiple organizations. For those with multiple

[OMPI devel] MPI F90

Preliminary off-list investigations with Brian Harker (from the users list) seem to indicate that we do not have a problem with our F90 bindings. It's not conclusive yet, but don't let this hold up 1.2.8. -- Jeff Squyres Cisco Systems

Re: [OMPI devel] proper way to shut down orted

Rlaph, Thanks for the reply. I should be able to build my own. Tim Ralph Castain wrote: Hmmm...well, there -used- to be a tool that was distributed with the 1.2 series for doing just that, but I don't see it in the 1.2.7 release. Not sure when or how that got dropped - probably fell through

[OMPI devel] #1506

Hi George, It seems like some data corruption in Reduce_scatter function I discovered it when added -DCHECK to IMB benchmark, and it seemed to be there for ages. it runs with voltaire MPI, but failes with OMPI. you will get a seqv with IMB3.1 and error with IMB3.0 host#VER=TRUNK ;

Re: [OMPI devel] [OMPI svn] svn:open-mpi r19600

Let me make the point that adding a data structure is much less destabilization to the tree than the routine day-to-day changes that go on in the tree. Rich On 9/23/08 6:24 AM, "Terry D. Dontje" wrote: > Jeff Squyres wrote: >> > I think the point is that as a group, we

Re: [OMPI devel] [OMPI svn] svn:open-mpi r19600

Jeff Squyres wrote: I think the point is that as a group, we consciously, deliberately, and painfully decided not to support multi-cluster. And as a result, we ripped out a lot of supporting code. Starting down this path again will likely result in a) re-opening all the discussions, b)