home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!paladin.american.edu!darwin.sura.net!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!news.cs.indiana.edu!arizona.edu!telcom.arizona.edu!leonard
- Newsgroups: comp.os.vms
- Subject: Re: ballooning EXE size
- Message-ID: <1992Dec29.120220.4182@arizona.edu>
- From: leonard@telcom.arizona.edu (Aaron Leonard)
- Date: 29 Dec 92 12:02:19 MST
- Reply-To: Leonard@Arizona.EDU
- References: <01GSUT89O7JK000J0I@XRT.UPENN.EDU>
- Distribution: world,local
- Organization: University of Arizona Telecommunications
- Nntp-Posting-Host: penny.telcom.arizona.edu
- Lines: 23
-
- In article <01GSUT89O7JK000J0I@XRT.UPENN.EDU>, BUHLE@XRT.UPENN.EDU ("E. Loren Buhle, Jr.
- [-662-3084]", 215 writes:
-
- |
- | I have a problem with the size of an executable going from ~1,000 blocks to
- | something on the order of 75,000 blocks.
- |
- | What am I doing? I am charged with writing a small interface to some existing
- | FORTRAN code. I have no control over the existing FORTRAN code and can only say
- | that it makes extensive use of VAX-FORTRAN Structure/record/map statements. I
- | don't own the large body of FORTRAN code and really don't relish the thought of
- | rewriting it...
- |
- | When the FORTRAN interface stub subroutines (e.g. subroutines that print a "not
- | implemented" message and return) are replaced with my code, the resulting
- | executable goes from ~1,000blocks to ~75,000 blocks.
- |
- | Yes, I use some scratch arrays (scratch arrays defined as local to the
- | subroutine), so I replaced these with LIB$GET_VM and LIB$FREE_VM and the
- | executable size when back to ~1,100 blocks. I presume the difference is due to
- | my code size. Ok so far, but I can't get away with this for long....
-
- Does your FORTRAN program declare its arrays initialized to some value?
-