<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">We will deprecate for v3.1 (expected out this fall), and may phase it out sometime in 2018 with the release of OMPI 4.0, or maybe as late as 2019. No real schedule has been developed yet. We are just trying to provide folks like you with as much notice as possible. You should plan on at least one year to get ready.<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jul 13, 2017, at 9:03 AM, John DelSignore <<a href="mailto:John.DelSignore@roguewave.com" class="">John.DelSignore@roguewave.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta content="text/html; charset=windows-1252" http-equiv="Content-Type" class="">
<div bgcolor="#FFFFFF" text="#000000" class=""><p class="">Ouch. Have you decided what the deprecation time line looks like
yet? In other words, when do you think that Open MPI will <u class="">stop</u>
supporting MPIR?<br class="">
</p><p class="">Cheers, John D.<br class="">
</p>
<br class="">
<div class="moz-cite-prefix">On 07/13/17 08:00, Jeff Squyres
(jsquyres) wrote:<br class="">
</div>
<blockquote cite="mid:4C44C960-B8E1-4A13-94B6-ABF970F6731C@cisco.com" type="cite" class="">
<pre wrap="" class="">FWIW, we just decided this week in Open MPI to deprecate the MPIR interface in favor of PMIx.
</pre>
<blockquote type="cite" class="">
<pre wrap="" class="">On Jul 12, 2017, at 2:02 PM, Durnov, Dmitry <a class="moz-txt-link-rfc2396E" href="mailto:dmitry.durnov@intel.com"><dmitry.durnov@intel.com></a> wrote:
Sure.
Thanks.
BR,
Dmitry
-----Original Message-----
From: mpiwg-tools [<a class="moz-txt-link-freetext" href="mailto:mpiwg-tools-bounces@lists.mpi-forum.org">mailto:mpiwg-tools-bounces@lists.mpi-forum.org</a>] On Behalf Of John DelSignore
Sent: Wednesday, July 12, 2017 9:52 PM
To: <a class="moz-txt-link-abbreviated" href="mailto:mpiwg-tools@lists.mpi-forum.org">mpiwg-tools@lists.mpi-forum.org</a>
Subject: Re: [mpiwg-tools] Intel MPI Backend Breakpoint
I'd be interested in being included in that discussion. FWIW, I work on the TotalView debugger and wrote-up the MPIR specification.
Cheers, John D.
-----Original Message-----
From: mpiwg-tools [<a class="moz-txt-link-freetext" href="mailto:mpiwg-tools-bounces@lists.mpi-forum.org">mailto:mpiwg-tools-bounces@lists.mpi-forum.org</a>] On Behalf Of Durnov, Dmitry
Sent: Wednesday, July 12, 2017 2:44 PM
To: <a class="moz-txt-link-abbreviated" href="mailto:mpiwg-tools@lists.mpi-forum.org">mpiwg-tools@lists.mpi-forum.org</a>
Subject: Re: [mpiwg-tools] Intel MPI Backend Breakpoint
Hi Alex,
I've started a separate mail thread where we may discuss details.
Thanks.
BR,
Dmitry
-----Original Message-----
From: mpiwg-tools [<a class="moz-txt-link-freetext" href="mailto:mpiwg-tools-bounces@lists.mpi-forum.org">mailto:mpiwg-tools-bounces@lists.mpi-forum.org</a>] On Behalf Of Alexander Zahdeh
Sent: Wednesday, July 12, 2017 7:27 PM
To: <a class="moz-txt-link-abbreviated" href="mailto:mpiwg-tools@lists.mpi-forum.org">mpiwg-tools@lists.mpi-forum.org</a>
Subject: [mpiwg-tools] Intel MPI Backend Breakpoint
Hi,
This is Alex Zahdeh, one of the debugger tools developers at Cray. I had a question about how Intel MPI handles synchronization according to the MPIR debugging standard. The usual procedure for our debugger is to launch tool daemons to attach to the backend application processes while the application launcher is held at MPIR_Breakpoint. At this point the application process must be in some sort of barrier so the debugger tries to return the user to their own code by setting breakpoints at various initialization symbols for different parallel models, continuing, hitting one of the breakpoints, deleting the rest and finishing the current function. This works if the application is held before the breakpoints we set which does not seem to be the case with Intel MPI. Is there a more standard approach to returning the user to their own code or does it vary by programming model and implementor? And specifically with Intel MPI would there be a good breakpoint to set in this scenari
</pre>
</blockquote>
<pre wrap="" class=""> o?
</pre>
<blockquote type="cite" class="">
<pre wrap="" class="">Thanks much,
Alex
--
Alex Zahdeh | PE Debugger Development | Cray Inc.
<a class="moz-txt-link-abbreviated" href="mailto:azahdeh@cray.com">azahdeh@cray.com</a> | Office: 651-967-9628 | Cell: 651-300-2005 _______________________________________________
mpiwg-tools mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mpiwg-tools@lists.mpi-forum.org">mpiwg-tools@lists.mpi-forum.org</a>
<a class="moz-txt-link-freetext" href="https://lists.mpi-forum.org/mailman/listinfo/mpiwg-tools">https://lists.mpi-forum.org/mailman/listinfo/mpiwg-tools</a>
--------------------------------------------------------------------
Joint Stock Company Intel A/O
Registered legal address: Krylatsky Hills Business Park,
17 Krylatskaya Str., Bldg 4, Moscow 121614, Russian Federation
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
_______________________________________________
mpiwg-tools mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mpiwg-tools@lists.mpi-forum.org">mpiwg-tools@lists.mpi-forum.org</a>
<a class="moz-txt-link-freetext" href="https://lists.mpi-forum.org/mailman/listinfo/mpiwg-tools">https://lists.mpi-forum.org/mailman/listinfo/mpiwg-tools</a>
_______________________________________________
mpiwg-tools mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mpiwg-tools@lists.mpi-forum.org">mpiwg-tools@lists.mpi-forum.org</a>
<a class="moz-txt-link-freetext" href="https://lists.mpi-forum.org/mailman/listinfo/mpiwg-tools">https://lists.mpi-forum.org/mailman/listinfo/mpiwg-tools</a>
--------------------------------------------------------------------
Joint Stock Company Intel A/O
Registered legal address: Krylatsky Hills Business Park,
17 Krylatskaya Str., Bldg 4, Moscow 121614,
Russian Federation
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
_______________________________________________
mpiwg-tools mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mpiwg-tools@lists.mpi-forum.org">mpiwg-tools@lists.mpi-forum.org</a>
<a class="moz-txt-link-freetext" href="https://lists.mpi-forum.org/mailman/listinfo/mpiwg-tools">https://lists.mpi-forum.org/mailman/listinfo/mpiwg-tools</a>
</pre>
</blockquote>
<pre wrap="" class="">
</pre>
</blockquote>
<br class="">
</div>
_______________________________________________<br class="">mpiwg-tools mailing list<br class=""><a href="mailto:mpiwg-tools@lists.mpi-forum.org" class="">mpiwg-tools@lists.mpi-forum.org</a><br class="">https://lists.mpi-forum.org/mailman/listinfo/mpiwg-tools</div></blockquote></div><br class=""></div></body></html>