Yes. There’s work going on toward this at the moment. 1103 is actually closed, but I think you can track the progress of this issue with #79. This is on the roadmap for MPICH 3.3 since it requires a fairly large amount of work that wasn’t ready for MPICH 3.2. That’s roughly scheduled for a 2016 release, but there will undoubtedly be alphas and betas before that. If you keep an eye on the ticket, you’ll know when it’s fixed and you can try out some of the nightly builds. Thanks, Wesley On Nov 17, 2014, at 10:40 AM, Roy, Hirak <[email protected]<mailto:[email protected]>> wrote: Hi All, It looks like the issue is still open described in the following two tickets in mpich-3.1.3 http://trac.mpich.org/projects/mpich/ticket/1103 http://trac.mpich.org/projects/mpich/ticket/79 Is there any plan to work on these? The issue is critical and stops us from using nemesis. Thanks, Hirak _______________________________________________ discuss mailing list [email protected]<mailto:[email protected]> To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list [email protected] To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss