Re: ancient PL/I, was fledgling assembler programmer

gah4 <gah4@u.washington.edu>
Fri, 24 Mar 2023 22:44:49 -0700 (PDT)

          From comp.compilers

Related articles
fledgling assembler programmer Alan.Beck@darkrealms.ca (2023-03-21)
Re: fledgling assembler programmer gah4@u.washington.edu (gah4) (2023-03-21)
Re: fledgling assembler programmer tkoenig@netcologne.de (Thomas Koenig) (2023-03-22)
Re: fledgling assembler programmer gah4@u.washington.edu (gah4) (2023-03-22)
Re: fledgling assembler programmer tkoenig@netcologne.de (Thomas Koenig) (2023-03-23)
Re: fledgling assembler programmer gah4@u.washington.edu (gah4) (2023-03-24)
Re: ancient PL/I, was fledgling assembler programmer drb@ihatespam.msu.edu (2023-03-24)
Re: ancient PL/I, was fledgling assembler programmer gah4@u.washington.edu (gah4) (2023-03-24)
Re: ancient PL/I, was fledgling assembler programmer gah4@u.washington.edu (gah4) (2023-03-25)
| List of all articles for this month |

From: gah4 <gah4@u.washington.edu>
Newsgroups: comp.compilers
Date: Fri, 24 Mar 2023 22:44:49 -0700 (PDT)
Organization: Compilers Central
References: 23-03-001 23-03-002 23-03-003 23-03-007 23-03-008 23-03-012 23-03-013
Injection-Info: gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="72169"; mail-complaints-to="abuse@iecc.com"
Keywords: storage, comment
Posted-Date: 25 Mar 2023 03:09:26 EDT
In-Reply-To: 23-03-013

On Friday, March 24, 2023 at 9:13:05 PM UTC-7, Dennis Boone wrote:


(after I wrote)
> > OK, the IBM PL/I (F) compiler, for what many consider a bloated
> > language, is designed to run (maybe not well) in 64K.
> > At the end of every compilation it tells how much memory was
> > used, how much available, and how much to keep the symbol table
> > in memory.


> It's... 30-some passes, iirc?


> [Well, phases or overlays but yes, IBM was really good at slicing compilers
> into pieces they could overlay. -John]


It is what IBM calls, I believe, dynamic overlay. Each module specifically
requests others to be loaded into memory. If there is enough memory,
they can stay, otherwise they are removed.


And there are a few disk files to be used, when it is actually
a separate pass. The only one I actually know, is if the preprocessor
is used, it writes a disk file with the preprocessor output.


And as noted, if it is really short on memory, the symbol table
goes out to disk.


Fortran H, on the other hand, uses the overlay system generated
by the linkage editor. When running on virtual storage system, it is
usual to run the compiler through the linkage editor to remove
the overlay structure. (One of the few linkers that knows how
to read its own output.) Normally it is about 300K, without
overlay closer to 450K.
[Never heard of dynamic overlays on S/360. -John]


Post a followup to this message

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