<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="">
Hi Rolf,
<div class=""><br class="">
</div>
<div class="">This is a (somewhat contrived, arguably) reason for taking another tiny step towards removing the “mpif.h” method of Fortran support and pushing users and implementations towards preferring the Fortran 2008 interface, which is a direction of travel
that I fully support.</div>
<div class=""><br class="">
</div>
<div class="">I think this might be seen as quite a big change for implementers, especially if it were to occur between the RCM and FRM.</div>
<div class=""><br class="">
</div>
<div class="">
<div class="">
<div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
Cheers,</div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
Dan.</div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
—<br class="">
Dr Daniel Holmes PhD<br class="">
Architect (HPC Research)<br class="">
<a href="mailto:d.holmes@epcc.ed.ac.uk" class="">d.holmes@epcc.ed.ac.uk</a><br class="">
Phone: +44 (0) 131 651 3465<br class="">
Mobile: +44 (0) 7940 524 088<br class="">
Address: Room 2.09, Bayes Centre, 47 Potterrow, Central Area, Edinburgh, EH8 9BT</div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
—</div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.</div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
—</div>
</div>
</div>
</div>
</div>
<div><br class="">
<blockquote type="cite" class="">
<div class="">On 10 Jan 2021, at 12:22, Rolf Rabenseifner via mpi-forum <<a href="mailto:mpi-forum@lists.mpi-forum.org" class="">mpi-forum@lists.mpi-forum.org</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">This email was sent to you by someone outside the University.<br class="">
You should only click on links or attachments if you are certain that the email is genuine and the content is safe.<br class="">
<br class="">
Dear MPI-Forum members,<br class="">
<br class="">
MPI-3.1 and MPI-4.0 includes the following rule on top of the 2nd page<br class="">
of the Language Binding chapter:<br class="">
<br class="">
| MPI implementations providing a Fortran interface must provide<br class="">
| one or both of the following:<br class="">
| - The USE mpi_f08 Fortran support method.<br class="">
| - The USE mpi and INCLUDE 'mpif.h' Fortran support methods.<br class="">
<br class="">
The embiggening was included only in the C and mpi_f08 bindings.<br class="">
<br class="">
Most implementors nowadays provide all three MPI Fortran support methods,<br class="">
i.e., the mpi_f08 and the mpi module and mpif.h.<br class="">
<br class="">
For all MPI-3.1 libraries that provide all three MPI Fortran support methods,<br class="">
the most easiest and fastest way to provide MPI-4.0 for C and Fortran is,<br class="">
- to implement the embiggening for C,<br class="">
- and to remove the mpi_f08 module,<br class="">
- and maybe months or years later, to provide mpi_f08 again, now embiggened.<br class="">
<br class="">
This implementation path (by removing mpi_f08 from MPI-3.1 and to name<br class="">
it MPI-4.0 without Fortran embiggening) was of course never intended,<br class="">
when we decided to require the embiggened routines only for mpi_f08.<br class="">
The goal was<br class="">
- to not require additional work from the implementors for the old mpi module<br class="">
- convince the users that it is a good idea to make a transition<br class="">
to mpi_f08.<br class="">
<br class="">
The most simplest way to resolve this problem would be to require<br class="">
mpi_f08 for MPI-4.0, i.e., to change the text to<br class="">
<br class="">
| MPI implementations providing a Fortran interface<br class="">
| - must provide the USE mpi_f08 Fortran support method,<br class="">
| - and additionally may provide both,<br class="">
| the USE mpi and INCLUDE 'mpif.h' Fortran support methods.<br class="">
<br class="">
What is your opinion?<br class="">
<br class="">
I expect that we should discuss this next Wednesday at our MPI Forum telcon.<br class="">
<br class="">
Best regards<br class="">
Rolf<br class="">
<br class="">
--<br class="">
Dr. Rolf Rabenseifner . . . . . . . . . .. <a href="mailto:rabenseifner@hlrs.de" class="">
email rabenseifner@hlrs.de</a> .<br class="">
High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 .<br class="">
University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 .<br class="">
Head of Dpmt Parallel Computing . . . <a href="http://www.hlrs.de/people/rabenseifner" class="">
www.hlrs.de/people/rabenseifner</a> .<br class="">
Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room 1.307) .<br class="">
_______________________________________________<br class="">
mpi-forum mailing list<br class="">
<a href="mailto:mpi-forum@lists.mpi-forum.org" class="">mpi-forum@lists.mpi-forum.org</a><br class="">
https://lists.mpi-forum.org/mailman/listinfo/mpi-forum<br class="">
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</body>
</html>