<div dir="ltr"><div>I disagree. There is still F77 code around that has not been ported to a more recent standard. I have some of that code myself and need to stay in its present form (no updating).</div><div><br></div><div>Jeff</div><div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jan 27, 2021 at 1:53 PM Håkon Strandenes via discuss <<a href="mailto:discuss@mpich.org">discuss@mpich.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">You must differentiate between Fortran 77 and fixed-form Fortran source <br>
code.<br>
<br>
I doubt there are any true Fortran 77 code around today.<br>
<br>
I am myself maintaining a large codebase written in Fixed Form Fortran. <br>
The code was probably Fortran 77 at some point 30-40 years ago, but not <br>
any more. Yet we still maintain parts in Fixed Form, though. This code <br>
is Fortran 2003 at minimum.<br>
<br>
I do not have the Fortran 2018 standard document around, but at least <br>
Fortran 2008 include fixed-form as an allowed source form (although <br>
marked as deprecated). For those interested, this is chapter 3.3 "Source <br>
form" in ISO/IEC 1539-1:2010.<br>
<br>
F77 can only be fixed form, but that does not make any fixed-form <br>
Fortran program F77. Fixed-form Fortran can be F2008 as well.<br>
<br>
This must be understood correctly for this discussion to be fruitful.<br>
<br>
Best regards,<br>
Håkon<br>
<br>
Den 2021-01-27 04:08, skrev Gus Correa via discuss:<br>
> IS IT OKAY TO REMOVE F77 SUPPORT?<br>
> <br>
> No, NO, NO!!!! NO!<br>
> <br>
> Removing the support to Fortran 77 from MPI is a disastrous idea!<br>
> Sorry to say, but it is really stupid to suppose that only because<br>
> compilers support F90<br>
> that you can remove F77 support from MPI.<br>
> A lot of people, academic institutions, and probably industry,<br>
> continue to use,<br>
> and develop new code in F77.<br>
> <br>
> What matters is if the CODE is written in Fortran 90 or in Fortran 77,<br>
> and whether it uses the Fortran 77 MPI API or the Fortran 90 MPI API,<br>
> not whether the compiler supports Fortran 90 (and yes, if not all,<br>
> do).<br>
> <br>
> There is an enormous Fortran 77 code base, written using MPI, and that<br>
> is not likely to change for the foreseeable future.<br>
> That is true in the Atmospheric/Climate/Ocean sciences, where I work,<br>
> <br>
> <br>
> but would guess this is true in other areas of science as well.<br>
> Just one example: The MITgcm, which has an huge community of users,<br>
> <br>
> is the backbone for many research projects, supports many PhD thesis,<br>
> is 100% written in Fortran-77 and will not be changed anytime soon,<br>
> as there is no financial support to do that.<br>
> <br>
> Also, this type of inquiry to the MPICH community is way too narrow.<br>
> I don't think you should be using emails on a mailing list to base<br>
> such a consequential decision.<br>
> Argonne should know better which community it supports, which codes<br>
> out there use MPI.<br>
> <br>
> Thank you,<br>
> <br>
> Gus Correa<br>
> Lamont-Doherty Earth Observatory of Columbia University.<br>
> <br>
> On Tue, Jan 26, 2021 at 6:12 PM Zhou, Hui via discuss<br>
> <<a href="mailto:discuss@mpich.org" target="_blank">discuss@mpich.org</a>> wrote:<br>
> <br>
>> Dear MPICH community,<br>
>> <br>
>> Can we assume at this point of time, that every Fortran compiler out<br>
>> there supports Fortran 90 at least?<br>
>> <br>
>> --<br>
>> Hui Zhou<br>
>> <br>
>> _______________________________________________<br>
>> discuss mailing list <a href="mailto:discuss@mpich.org" target="_blank">discuss@mpich.org</a><br>
>> To manage subscription options or unsubscribe:<br>
>> <a href="https://lists.mpich.org/mailman/listinfo/discuss" rel="noreferrer" target="_blank">https://lists.mpich.org/mailman/listinfo/discuss</a><br>
> _______________________________________________<br>
> discuss mailing list <a href="mailto:discuss@mpich.org" target="_blank">discuss@mpich.org</a><br>
> To manage subscription options or unsubscribe:<br>
> <a href="https://lists.mpich.org/mailman/listinfo/discuss" rel="noreferrer" target="_blank">https://lists.mpich.org/mailman/listinfo/discuss</a><br>
_______________________________________________<br>
discuss mailing list <a href="mailto:discuss@mpich.org" target="_blank">discuss@mpich.org</a><br>
To manage subscription options or unsubscribe:<br>
<a href="https://lists.mpich.org/mailman/listinfo/discuss" rel="noreferrer" target="_blank">https://lists.mpich.org/mailman/listinfo/discuss</a><br>
</blockquote></div></div><div id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br>
<table style="border-top:1px solid #d3d4de">
<tr>
<td style="width:55px;padding-top:13px"><a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon" target="_blank"><img src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif" alt="" width="46" height="29" style="width: 46px; height: 29px;"></a></td>
<td style="width:470px;padding-top:12px;color:#41424e;font-size:13px;font-family:Arial,Helvetica,sans-serif;line-height:18px">Virus-free. <a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link" target="_blank" style="color:#4453ea">www.avast.com</a>
</td>
</tr>
</table><a href="#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1"></a></div>