Sujet : Re: xkcd: CrowdStrike
De : lynnmcguire5 (at) *nospam* gmail.com (Lynn McGuire)
Groupes : rec.arts.sf.written rec.arts.comics.stripsDate : 25. Jul 2024, 22:27:36
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <v7ug09$2f1u3$1@dont-email.me>
References : 1 2 3 4 5
User-Agent : Mozilla Thunderbird
On 7/25/2024 2:52 PM, Scott Dorsey wrote:
Lynn McGuire <lynnmcguire5@gmail.com> wrote:
>
The real problem is that Fortran changed significantly from F66 / F77 to
F90 and beyond. I have written my own program to do most of the
upgrades for me but I am subject to the old 80 / 20 rule. It is easy to
automate 80% of the work but the last 20% is dadgum hard to automate. I
am also cleaning up some old code from the 1970s that is problematic.
Have you considered gnu fortran? It doesn't produce as fast executables
as the Intel compiler sometimes, but it's pretty good and it has an f77
mode.
f90 brings some very cool stuff for matrix operations, which makes
autoparallelization a lot easier, but on the other hand I don't think
engineers should be allowed to use pointers.
And hollerith fields have to go.
I started off porting my F66 / F77 code to C++ using a very modified
version of F2C. Due to the complexity of input and output between the
two languages (Fortran is record oriented, C is byte oriented), I have
split the project into two parts as my customers need a x64 version of
my software.
The original g77 was just f2c in front of gcc and... it was pretty awful
really, and never did work all that well. Modern gfortran is much better.
--scott
Is there a decent IDE for gnu fortran with gcc ? I tried Simply Fortran and the debugger support is very minimal. I need to be able to stop on the Xth call to a subroutine and Simply Fortran does not support that. I have 5,000 subroutines (800k lines of F77), 300 common blocks, and 500K lines of C++ in over 10,000 files in my calculation engine. Managing that without an IDE is challenging.
https://simplyfortran.com/My Hollerith is gone. My structures and unions are reduced. The code actually converts to C++ fairly well until you get to the formats.
Thanks,
Lynn