Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!sdd.hp.com!apollo!apollo.hp.com!kumorek
From: kumorek@apollo.HP.COM (James Kumorek)
Newsgroups: comp.sys.apollo
Subject: Re: Problems with Fortran-Compiler
Message-ID: <5010ae58.20b6d@apollo.HP.COM>
Date: 27 Feb 91 13:59:00 GMT
References: <250@mailgzrz.tu-berlin.de>
Sender: root@apollo.HP.COM
Reply-To: kumorek@apollo.HP.COM (James Kumorek)
Organization: Hewlett-Packard Apollo Division - Chelmsford, MA
Lines: 44

In article <250@mailgzrz.tu-berlin.de>,
jaenicke@w414zrz.zrz.tu-berlin.de (Lutz Jaenicke) writes:
|> Two weeks ago, we upgraded our DN10000 to SR10.3.
|> During the installation-process, we had to re-install our
|> fortran- and c-compilers. Since this day we have got a
|> disk-space consuming problem with our fortran-software.
|> 
|> We are doing FEM-calculations which require the use of large
|> arrays. The arrays are of static size and declared in the
|> program header. The compiler is running well and .o-Files of 
|> normal size are generated. When the program is linked, it seems 
|> that all the arrays are allocated, filled with nothing 
|> and then are written into the executable file, so that a large 
|> amount of diskspace is wasted. Under SR10.2p the executables 
|> where of normal size (which means some 100k), now they take MEGABYTES.  
|> 
|> We are using the Fortan-Compiler v10.7p. Since we haven't got
|> much UNIX experience yet, there is a good chance we made some
|> installation mistake.
|> 
|> Does anybody know, how this problem can be solved?
|> 
|> Thanks,
|> Lutz Jaenicke, TU-Berlin, Institut fuer Elektrische Maschinen
|> jaenicke@w414zrz.ee.tu-berlin.de

If your FEM calculation program contains modules written in C, then
you may need to add the option '-W0,-compress' to your C compile commands.
This will instruct the C compile to comress the object files, which
I beleive it does not do by default.  The Fortran compiler does compress
it's object files by default, but if your Fortran modules are linked
with uncompressed C modules, the linker will uncompress the fortran modules
and the resulting executable will be uncompressed.

This should have been the same at SR10.2;  I can't explain why switching
to SR10.3 would have changed this.

I hope this helps!

                 - Jim

Jim Kumorek
Apollo Computer, Inc. - A subsidiary of Hewlett Packard
kumorek@apollo.hp.com