home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.vms
- Path: sparky!uunet!paladin.american.edu!gatech!darwin.sura.net!haven.umd.edu!decuac!pa.dec.com!nntpd2.cxo.dec.com!adserv.enet.dec.com!winalski
- From: winalski@adserv.enet.dec.com (Paul S. Winalski)
- Subject: Re: ballooning EXE size
- Message-ID: <1992Dec30.222945.25613@nntpd2.cxo.dec.com>
- Lines: 28
- Sender: usenet@nntpd2.cxo.dec.com (USENET News System)
- Reply-To: winalski@adserv.enet.dec.com (Paul S. Winalski)
- Organization: Digital Equipment Corporation, Nashua NH
- References: <01GSUT89O7JK000J0I@XRT.UPENN.EDU> <29DEC199216584048@venus.lerc.nasa.gov>
- Date: Wed, 30 Dec 1992 22:29:45 GMT
-
-
- In article <29DEC199216584048@venus.lerc.nasa.gov>,
- uugblum@venus.lerc.nasa.gov (VMScluster Administrator) writes:
- |>
- |>I assisted one of the users here with this problem about a month ago.
- |>
- |>The problem with a program growing from a small to a large executable size
- |>by making a small change in source code is caused by the linker demand zero
- |>compression not being used when a certain image section count is exceeded.
- |>This can be corrected by specifying a ISD_MAX value of 200 to 300 in a
- |>link options file. See the DSNlink article entitled "Image File Grows Much
- |>Larger After Adding Small Amount of Code".
-
- Raising ISD_MAX creates its own set of problems. You may have to raise
- PROCSECTCNT, for example, which increases the size of process headers and thus
- the amount of physical memory permanently allocated to VMS. Also, having lots
- of process sections can drastically increase image activation time.
-
- A better way to remedy this situation is to examine the link map to determine
- which program sections are initialized versus uninitialized, and to use
- CLUSTER and COLLECT linker options to cause those program sections to be
- consolidated into a single image section. With rare exceptions, a VMS
- executable image need not have more than 10 image sections, not counting those
- associated with shareable images that the executable image references. If
- an image is bumping into the ISD_MAX limit, that is a sign that the programmer
- needs to take a look at how the PSECTs are being laid out in memory.
-
- --PSW
-