"Quadibloc" <
jsa...@ecn.ab.ca> wrote:
>There's always the option of porting Linux - that is, just
>a) retarget gcc for the target architecture, [...]
A sort-of similar solution was used at Oak Ridge National Labs (aka "X-10")
when it installed a 360/75 (running an early version of OS/360).
The /75 replaced a CDC 1604, on which the FORTRAN compiler was considered to
be critically deficient by the researchers, in response to which Jerry
Sullivan wrote a very good, efficient, and feature-rich. Over time the
compiler was rewritten in its own language (much like FORTRAN H).
Porting Jerry's compiler to the /75 was relatively straight-forward: the
1604 compiler was modified to emit S/360 object decks, and was then fed its
own source. The output was the compiler for OS/360 which used the native
FORTRAN library. (There may have been a couple of specialized assembly
language programs that had to be recoded from scratch.)
The ported compiler remained the language translator of choice for a long
time, well after FORT-H became available. I don't know if it was still in
use when the optimizing FORTRAN compiler program product showed up.
If anyone here has ever worked with a FORTRAN program that came from ORNL
and it refers to FORTRAN unit numbers starting at 50, it's likely that the
program was originally intended for use with Jerry's FORTRAN compiler.
Joe