Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site ucbvax.ARPA
Path: utzoo!watmath!clyde!cbosgd!ucbvax!info-vax
From: info-vax@ucbvax.ARPA
Newsgroups: fa.info-vax
Subject: Huge object modules from Vax-11 C -- why?
Message-ID: <5522@ucbvax.ARPA>
Date: Fri, 15-Mar-85 20:22:48 EST
Article-I.D.: ucbvax.5522
Posted: Fri Mar 15 20:22:48 1985
Date-Received: Sun, 17-Mar-85 00:01:45 EST
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 17

From: stew%lhasa@harvard.ARPA

I wonder if anyone has seen and can explain this.  I have been working on
a multi-source-file C program (porting C-Kermit to VMS) and some of the
object modules (3 out of maybe a dozen) are huge, maybe 400 blocks from
a 30 block source file.  This is not related to the #include files, since
other modules which #include the same header files are appropriately
sized.  These huge object modules contain linker commands which form
large tables at the beginning of the $CODE segment for the corresponding
file.  The result is about 80K * 3 files = 240K of inexplicable data
in my EXE file.

Ideas anyone?

Stew
rubenstein@harvard.arpa
{ihnp4,seismo,ut-sally}!harvard!rubenstein