On Nov 8, 2011, at 10:25 AM, George Bosilca wrote: > However, based on what we have in the trunk today, Open MPI doesn't follow > that document. As Ralph pinpointed it, the current version work with several > tools (tv, stat, padb) as is, so that means the tools do not really follow > that document either.
This is not quite accurate. What the tools did over the past decade was make it so that they work with the 5-6 MPIR variants that are out there. So yes, they work with OMPI, but they work with the others who aren't quite "right," either. Because before this, there was no central definition of "right." The intent of the document was to make that central definition of "right" and gradually have everyone move to it. AFAIK, all the tools have been updated to work with the "right" definition of MPIR. Keep in mind that this is pretty much the same rationale as to why MPI still supports functions like MPI_ATTR_SET: even though it's deprecated, there's apps out there that still use it and will take a long time to adapt. Hence, the tools will keep supporting the "old" / "not-quite-right" definitions of MPIR for a long time. -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
