<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">The ABI compatibility initiative applies within the same implementation as well. So all MPICH versions back to MPICH 3.1 are binary compatible with each other.<div class=""><br class=""></div><div class=""><a href="https://www.mpich.org/abi/" class="">https://www.mpich.org/abi/</a></div><div class=""><br class=""></div><div class="">It’s possible that MPICH 3.0 is also compatible, but I don’t think there were any guarantees or tests. You might just get lucky if that’s the version you want.</div><div class=""><br class=""></div><div class=""><div class="">Thanks,</div><div class="">Wes</div><div><br class=""><blockquote type="cite" class=""><div class="">On Mar 17, 2020, at 7:40 AM, Saurabh T via discuss <<a href="mailto:discuss@mpich.org" class="">discuss@mpich.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">What is the guarantee for binary (ABI) compatibility between MPICH versions? I am not referring to the ABI compatibility initiative with other MPI implementations, but between different versions of MPICH. For example, is MPICH 3.3 ABI compatible with MPICH 3.0? Thank you.<br class=""><br class="">saurabh<br class="">_______________________________________________<br class="">discuss mailing list <a href="mailto:discuss@mpich.org" class="">discuss@mpich.org</a><br class="">To manage subscription options or unsubscribe:<br class=""><a href="https://lists.mpich.org/mailman/listinfo/discuss" class="">https://lists.mpich.org/mailman/listinfo/discuss</a><br class=""></div></div></blockquote></div><br class=""></div></body></html>