<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>BIND(FORTRAN, name="MPI_Test_f08") seems like a great idea. Unfortunately I can't find it in the Fortran standard :-(</div></div><div><br></div><div>Perhaps J3 would be amenable to adding FORTRAN to language-binding-spec. </div><br><div apple-content-edited="true">
<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; "><div>Craig Rasmussen</div><div>CAS Scientific Programmer</div><div><a href="mailto:rasmus@cas.uoregon.edu">rasmus@cas.uoregon.edu</a></div><div><br></div></div></span></span>
</div>
<br><div><div>On Mar 21, 2013, at 10:11 AM, Hubert Ritzdorf wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><blockquote type="cite">I believe the NEC Fortran MPI API may do similar things.<br></blockquote><br>This is right.<br>The tool guys are mainly looking for a well-defined name.<br>I think that it is a bad idea to kill backward compatibility, Fortran profiling interface<br>and optimization possibilities of MPI implementers in order to get this well-defined name.<br><br>It would be possibly simpler to add a specific BIND(Fortran, name="MPI_Test_f08") to Fortran<br>which sets the linker name instead of using BIND(C, name="MPI_Test_f08") and we could<br>avoid all the interoperability problems which were found till now (and in future).<br><br>MPI_Test is a relatively simple function. We have much more complex functions which<br>might increase scalability problems (for example additional memory<br>allocation for MPI_Alltoallw in order to transform datatypes, possibly counts, displacements)<br>for this requested approach. <br><br>The upper routines/functions might become complex or<br>cpu-time relevant (example: implementation of MPI_SUBARRAYS_SUPPORTED).<br>In this case, the usage of performance (or debugging) tools which ignore the work in<br>this upper functions (since these tools see only the C MPI functions) might<br>become problematic.<br><br>Hubert<br>________________________________________<br>From: <a href="mailto:mpi3-fortran-bounces@lists.mpi-forum.org">mpi3-fortran-bounces@lists.mpi-forum.org</a> [<a href="mailto:mpi3-fortran-bounces@lists.mpi-forum.org">mpi3-fortran-bounces@lists.mpi-forum.org</a>] on behalf of Jeff Squyres (jsquyres) [<a href="mailto:jsquyres@cisco.com">jsquyres@cisco.com</a>]<br>Sent: Thursday, March 21, 2013 4:38 PM<br>To: MPI-3 Fortran working group<br>Cc: Martin Schulz<br>Subject: Re: [MPI3 Fortran] [Mpi-comments] MPI 3.0: Fortran 2008 interface - issue with the LOGICAL kind<br><br>On Mar 21, 2013, at 8:26 AM, Craig Rasmussen <<a href="mailto:rasmus@cas.uoregon.edu">rasmus@cas.uoregon.edu</a>> wrote:<br><br><blockquote type="cite">I talked with Martin yesterday and he would be happy to have the requirement in the standard that the Fortran wrappers MUST call the MPI C interface. This would much simplify things for the tools community. (I had earlier thought he would object to this solution.)<br></blockquote><br>No! This is NOT a good idea to mandate.<br><br>Open MPI currently has a bunch of Fortran functions that do NOT call the corresponding MPI_<foo> C function. Instead, they call some other back-end, internal function.<br><br>I believe the NEC Fortran MPI API may do similar things.<br><br>--<br>Jeff Squyres<br><a href="mailto:jsquyres@cisco.com">jsquyres@cisco.com</a><br>For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/<br><br><br>_______________________________________________<br>mpi3-fortran mailing list<br>mpi3-fortran@lists.mpi-forum.org<br>http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-fortran<br><br><br> Click https://www.mailcontrol.com/sr/Geaaq1rkMOPGX2PQPOmvUpJBCTqJzJUeYtFmk42MgAlOvSHOzXVuO4Ep5Wd3HnToAzNTk47hsmGOdoKZwoXR0w== to report this email as spam.<br><br>_______________________________________________<br>mpi3-fortran mailing list<br>mpi3-fortran@lists.mpi-forum.org<br>http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-fortran<br></div></blockquote></div><br></body></html>