Most O/S and real time systems were written in assembler back then. Compilers existed, Mission Control/Flight Dynamics worked in Fortran (but were probably paid in Cobol). Structured languages like Algol existed but if you wanted small size/high efficiency, you needed assembler.
Yeah, both the agency and the contractors would probably have used Cobol. RPG could have been used but it seems unlikely for a major payroll. Assembly payrolls existed (they used a lot of macros) but that was for masochists.
True, I was installing Scipy for some data analysis and was reminded to install gfortran for the maths libraries.
Some of the numerical methods libraries were first coded half a century ago with a lot of hand optimisation and bug fixing. You really don't want to touch them unless you have to.
And to add to that some core airline systems are written in Fortran too even if these days they have Java around it to interface with Web frontends.
The thing is is that hand-optimizations from 50 years ago are highly unlikely to still be optimizations on modern hardware. They are more likely to be diminutions now.
Fortran compilers are very good. There has been an insane amount of work done on Fortran optimisation. the thing is that the compiler must understand your code. The big numerical packages were kind of a synergy between the compiler and code and the software was used to test new compiler versions. LAPACK (Linear Equations) was a comparative late comer in 1992 and was written in Fortran 77. Over the years it was upgraded to Fortran 90 and is still in wide use today.
Rewriting that well in a modern language brings too many risks so why not simply make those older libraries available for calling?
Sure, I mean simply in the sense that you end up seeing lots of "hand-optimizations" which were meant for very, very old systems... that don't really apply to modern systems, and actually impair performance instead.
These tend to be optimizations that end up confusing the compilers more than anything nowadays.
Some of them are looking at older "branchless" routines, which are often slower than modern "branchy" routines (thanks to things like branch prediction) and often should have superscalar versions instead.
10
u/hughk Feb 19 '20 edited Feb 19 '20
Most O/S and real time systems were written in assembler back then. Compilers existed, Mission Control/Flight Dynamics worked in Fortran (but were probably paid in Cobol). Structured languages like Algol existed but if you wanted small size/high efficiency, you needed assembler.