NetNews Usenet Archive 1993 #1/NN_1993_1.iso/spool/comp/sys/hp/14652

Text File | 1993-01-08 | 1.5 KB | 31 lines

Newsgroups: comp.sys.hp
Path: sparky!uunet!paladin.american.edu!howland.reston.ans.net!zaphod.mps.ohio-state.edu!usc!cs.utexas.edu!torn!watserv2.uwaterloo.ca!madmax.uwaterloo.ca!gordon
From: [e-mail] (Gordon R. Strachan)
Subject: Re: Huge executables from f77 on 750's
Message-ID: <[e-mail]>
Sender: [e-mail]
Organization: University of Waterloo
References: <[e-mail]>
Date: Fri, 8 Jan 1993 16:12:18 GMT
Lines: 19

In article <[e-mail]> [e-mail] (Franco Trani) writes:
>
>I've a problem with f77 (what /usr/bin/f77: HPUX Fortran/ 9000s700
>09/19/91 B2408 A08.07). Some code I compile on a 9000s433 gives an
>executable of 336 KB. The same code compiled with the same comp-
>iler options results in a 29 MB monster on the 750 (it can be com-
>pressed to a size of ~ 400 KB !). I've another example which is not

This is standard fortran madness with defining large arrays.  It has to do with
how the compiler and linker arange intialized and uninitialized data in memory.
You most likely have defined a couple of large arrays in your program.  The
best thing to do is to all put those arrays into a dummy common block.  It
doesn't matter if any other function access the common block but just make
sure that there is not initialized data (ie a variable defined in a data
statement) in that common block.  That will solve your problem.

Gordon