Re: compiler bugs

glen herrmannsfeldt <>
Tue, 5 May 2009 19:00:14 +0000 (UTC)

          From comp.compilers

Related articles
[17 earlier articles]
Re: compiler bugs (Chris F Clark) (2009-04-30)
Re: compiler bugs (2009-05-01)
Re: compiler bugs (Gene) (2009-05-01)
Re: compiler bugs (Christopher Glaeser) (2009-05-04)
Re: compiler bugs (2009-05-05)
Re: compiler bugs (glen herrmannsfeldt) (2009-05-05)
Re: compiler bugs (glen herrmannsfeldt) (2009-05-05)
Re: compiler bugs (Christopher Glaeser) (2009-05-06)
Re: compiler bugs (2009-05-06)
Re: compiler bugs (Chris F Clark) (2009-05-07)
Re: compiler bugs (Barry Kelly) (2009-05-10)
Re: compiler bugs (2009-05-10)
| List of all articles for this month |

From: glen herrmannsfeldt <>
Newsgroups: comp.compilers
Date: Tue, 5 May 2009 19:00:14 +0000 (UTC)
Organization: California Institute of Technology, Pasadena
References: 09-04-072 09-04-086 09-05-010 09-05-022 09-05-029
Keywords: Fortran, history
Posted-Date: 06 May 2009 05:56:26 EDT

glen herrmannsfeldt <> wrote:
> (John wrote)

> [Yup, HX, same program. I gather HX has the same broken optimizations
> that H did. In its defense, Fortran H did have to invent a lot of the
> analysis techniques it used, and run on a 128K (for the young folks, yes,
> that's a K) machine. -John]

If it generates bit compatible output, it would have to have
the same broken optimizations.

I believe, though, that would be 256K, though people I knew
gave it 300K.

IBM uses a binary system similar to roman numerals, where a lower
value to the right is added, and to the left is subtracted.

F is 64K, G is 128K, H is 256K, such that a 192K machine would be
indicated by GF and a 7MB machine by JM. The numbering doesn't work
quite as well for programs, but PL/I (F) was designed to run in 44K on
a 64K machine, leaving 20K for the OS. (That might result in the
symbol table residing on disk. At the end of every run, PL/I (F)
would indicate the smallest region that would keep the symbol table in
main memory.)

As virtual memory became more popular, one common thing to do was to
remove the overlay structure from Fortran H. Load it into the linker
without any OVERLAY control cards, and then write it out again.

-- glen
[Darn those off by one bugs. You're right, it needed a 256K machine
rather than 128K. And like pretty much every other OS program it
ran a lot faster if you had enough storage to undo the origami and
get rid of the overlays. -John]

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.