home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.hp
- Path: sparky!uunet!elroy.jpl.nasa.gov!jato!vsnyder
- From: vsnyder@jato.jpl.nasa.gov (Van Snyder)
- Subject: Re: executable sizes in fortran
- Message-ID: <1992Sep8.201454.17374@jato.jpl.nasa.gov>
- Organization: Jet Propulsion Laboratory
- References: <lee.715546990@ceg.uiuc.edu> <Bu2BvF.8Aw@atl.hp.com>
- Date: Tue, 8 Sep 1992 20:14:54 GMT
- Lines: 33
-
- In article <Bu2BvF.8Aw@atl.hp.com> aaa@hpuerca.atl.hp.com (Simon Fowler) writes:
- >In article <lee.715546990@ceg.uiuc.edu>, lee@ceg.uiuc.edu (Chris Lee) writes:
- >> One of our users has a question:
- >>
- >> Why are the fortran executables SOOOOOO BIIIIIIIIIIG?
- >> It seems that "all" of the data is being allocated at
- >> compile/link time, and he would like to know if there is a
- >> way to force the compiler/linker to allocate it at runtime.
- >>
- >> We are running HPUX 8.07 on 9000/700s.
- >
- >Typically this is caused by large (should say LARGE) arrays that are statically allocated.
- >I usually see this when code is ported from another machine and then compiled with the -K
- >option to force all data to static storage (instead of being put on the stack). If this is
- >the case, you can declare the array as being in COMMON, e.g.
- >
- >change
- >
- > DIMENSION BIG(1000000)
- >to
- >
- > DIMENSION BIG(1000000)
- > COMMON /BIGCOM/BIG
- >
- >and don't compile with -K. You'll have to figure out which modules you can use this on.
-
- It's simpler to say SAVE BIG (or SAVE LITTLE if LITTLE is really the
- variable that needs to stick around from one invocation to the next).
-
- --
- vsnyder@jato.Jpl.Nasa.Gov vsnyder@math.Jpl.Nasa.Gov <-- preferred
- ames!elroy!jato!vsnyder ames!elroy!math!vsnyder
- vsnyder@jato.uucp
-