Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: Re: [OMPI devel] debugger confusion
From: Ralph Castain (rhc_at_[hidden])
Date: 2011-11-08 10:36:08

On Nov 8, 2011, at 8:25 AM, George Bosilca wrote:

> On Nov 8, 2011, at 07:52 , Jeff Squyres wrote:
>> To be clear: that document simply standardizes what MPI implementations are supposed to provide in their MPIR implementation (prior to this, MPI implementations tended to have subtle differences between their MPIR implementations, which were a nightmare for the debugger/tool vendors). This document does *not* fix the scalability and other well-known issues with MPIR -- it just consolidates and standardizes the slightly-different versions of MPIR that were floating around out there.
> 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. What a mess …
> All the time we spent in the MPI Forum talking about the MPIR interface, and look at the result !

Patience, patience - I look at the document as describing where people want to go, not a snapshot of where they already are. What will be interesting to see is how long it takes them to get there, how many of them will bother to do so, etc.

And, of course, how we maintain integration with all of them as the migration progresses!

> george.
> _______________________________________________
> devel mailing list
> devel_at_[hidden]