<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">My feeling on this is (a) there have already been too many oversights because of the tremendous scope of the changes and (b) the mpif.h interface, in practice, should and will be used mostly for legacy applications - thus either defining it as similar to the original "basic" support, with any new constants, will satisfy the users without the risk of finding another MPI_SIZEOF issue. At this point I have no confidence that there isn't something else lurking in the wings, and that argues for as conservative an approach as possible.<div><br></div><div>Bill</div><div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div style="font-size: 12px; ">William Gropp</div><div style="font-size: 12px; ">Director, Parallel Computing Institute</div></div></div></span><span class="Apple-style-span" style="font-size: 12px; ">Thomas M. Siebel Chair in Computer Science</span><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div style="font-size: 12px; ">University of Illinois Urbana-Champaign</div></div><div><br></div></div></span><br class="Apple-interchange-newline"></div></span><br class="Apple-interchange-newline"></span><br class="Apple-interchange-newline">
</div>
<br><div><div>On Jun 14, 2014, at 12:49 PM, Rolf Rabenseifner wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Yes, the "Extended Support" listed of about 5 additional routines,<br>but as far as I understand, MPI_SIZEOF is the only one<br>that needs an INTERFACE description in mpif.h.<br><br>All other routines are without any implementation-problems.<br><br>Therefore, it would be enough to allow in the special case<br>that MODULE (and INTERFACE) are not supported by the target compiler, <br>that <br> - the Fortran Support requires only mpif.h (same as in MPI-2.0), <br> and<br> - MPI_SIZEOF is not provided.<br><br>Additionally, we can restrict the MPI_SIZEOF support only 23 dimensions <br> - in mpif.h<br> - or generally if TS29113 or other non-Standard methods<br> are not available,<br>supposed that "DOUBLE PRECISION" is the longest<br>Fortran type Name:<br><br>123456789012345678901234567890123456789012345678901234567890123456789012<br> SUBROUTINE MPI_SIZEOF(x,n)<br> DOUBLE PRECISION x(1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,*)<br>! 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3<br>What did mpich and OpenMPI in the past with MPI_SIZEOF? <br><br>Rolf<br><br>----- Original Message -----<br><blockquote type="cite">From: "William Gropp" <<a href="mailto:wgropp@illinois.edu">wgropp@illinois.edu</a>><br></blockquote><blockquote type="cite">To: "MPI-WG Fortran working group" <<a href="mailto:mpiwg-fortran@lists.mpi-forum.org">mpiwg-fortran@lists.mpi-forum.org</a>><br></blockquote><blockquote type="cite">Sent: Saturday, June 14, 2014 6:36:35 AM<br></blockquote><blockquote type="cite">Subject: Re: [MPIWG Fortran] MPI_SIZEOF: Errata<span class="Apple-tab-span" style="white-space:pre"> </span>required<span class="Apple-tab-span" style="white-space:pre"> </span>(was:<span class="Apple-tab-span" style="white-space:pre"> </span>Another<span class="Apple-tab-span" style="white-space:pre"> </span>MPI_SIZEOF question)<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Not quite true. See my email, which gives specific locations in the<br></blockquote><blockquote type="cite">standard for the relevant text. Note also that MPI_SIZEOF is *not*<br></blockquote><blockquote type="cite">the only function that is not included in the "basic" Fortran<br></blockquote><blockquote type="cite">support - the routines to create a type based on precision and range<br></blockquote><blockquote type="cite">are also not required for basic support. <br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">I think there are two options for the so-called Fortran 77 support.<br></blockquote><blockquote type="cite"> Continue to support the "basic" support, as defined in MPI-2, or<br></blockquote><blockquote type="cite">delete it entirely. Anything else is likely to leave errors and<br></blockquote><blockquote type="cite">mistakes. And while I agree with Jeff that its not good practice to<br></blockquote><blockquote type="cite">remove something like F77 support at a point release, I believe that<br></blockquote><blockquote type="cite">the language in the standard removed Fortran 77 with 3.0. We're<br></blockquote><blockquote type="cite">just now recognizing that.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Bill<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">William Gropp<br></blockquote><blockquote type="cite">Director, Parallel Computing Institute Thomas M. Siebel Chair in<br></blockquote><blockquote type="cite">Computer Science<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">University of Illinois Urbana-Champaign<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On Jun 13, 2014, at 10:32 AM, Rolf Rabenseifner wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">2) The requirement of having this function in mpif.h was changed:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> MPI-2.0 through 2.2 requiered MPI_SIZEOF in mpif.h<br></blockquote><blockquote type="cite"> "unless the target compiler does not support modules<br></blockquote><blockquote type="cite"> or KIND-parametrized types."<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> This restriction was removed.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite">mpiwg-fortran mailing list<br></blockquote><blockquote type="cite"><a href="mailto:mpiwg-fortran@lists.mpi-forum.org">mpiwg-fortran@lists.mpi-forum.org</a><br></blockquote><blockquote type="cite"><a href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran">http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran</a><br></blockquote><br>-- <br>Dr. Rolf Rabenseifner . . . . . . . . . .. email <a href="mailto:rabenseifner@hlrs.de">rabenseifner@hlrs.de</a><br>High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530<br>University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832<br>Head of Dpmt Parallel Computing . . . <a href="http://www.hlrs.de/people/rabenseifner">www.hlrs.de/people/rabenseifner</a><br>Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room 1.307)<br>_______________________________________________<br>mpiwg-fortran mailing list<br><a href="mailto:mpiwg-fortran@lists.mpi-forum.org">mpiwg-fortran@lists.mpi-forum.org</a><br>http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran</div></blockquote></div><br></div></body></html>