rovide such support for the mpi_f08 module.
>> This means, they prove that they are not MPI-3.1 compliant :-)
>>
>>
>> Sometimes implementors ignore the goals and the wording of the MPI standard.
>>
>>
>> And there is also no request that users want to
; mpi module definition.
>
> Best regards
> Rolf
>
>
> - Original Message -
>> From: "Main MPI Forum mailing list"
>> To: "Main MPI Forum mailing list"
>> Cc: "Jeff Squyres"
>> Sent: Sunday, January 10, 2021 5:09:55 PM
>&g
"Jeff Squyres"
> Sent: Sunday, January 10, 2021 5:09:55 PM
> Subject: Re: [Mpi-forum] Big Fortran hole in MPI-4.0 Embiggening
> I can't imagine a vendor would:
>
> - support mpi_f08
> - then stop supporting mpi_f08 just so that they can get an "MPI-4.0" rel
I can't imagine a vendor would:
- support mpi_f08
- then stop supporting mpi_f08 just so that they can get an "MPI-4.0" release
out
- then support mpi_f08 again
I think their users would be very unhappy.
On Jan 10, 2021, at 10:55 AM, William Gropp via mpi-forum
I agree with Dan that this is a big change from the RCM. Further, the approach
in MPI has always been to encourage the users to make it clear to the vendors
what is acceptable in implementations, especially implementation schedules.
Nothing in the standard prohibits implementors from
Hi Rolf,
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.
I think this
Dear MPI-Forum members,
MPI-3.1 and MPI-4.0 includes the following rule on top of the 2nd page
of the Language Binding chapter:
| MPI implementations providing a Fortran interface must provide
| one or both of the following:
| - The USE mpi_f08 Fortran support method.
| - The USE mpi and
