Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!dali.cs.montana.edu!milton!news
From: dwatola@nextasy2 (David Watola)
Newsgroups: comp.sys.next
Subject: f2c and LARGE object files
Keywords: blech!
Message-ID: <1991May1.173124.17624@milton.u.washington.edu>
Date: 1 May 91 17:31:24 GMT
Sender: news@milton.u.washington.edu (News)
Organization: University of Washington
Lines: 23


has anyone noticed this problem with f2c:

typically, f2c seems to produce c source that is twice the size of the original
fortran.  for some reason, i noticed extremely long compile times for these
sources (~40k of source), on the order of several minutes on a 16M cube.  since
my use of infernal fortran is rare, i was not too concerned.  but finally i got
fed up and decided to build a library.  that's when i discovered the reason for
the long compile times.  if i compile source code generated by f2c with 'cc -c'
the resulting object file for my 40k source is a whopping 37 megs!!!  without
the '-c' flag (and with a main() routine to link edit) this 37 meg file is
still generated, but somehow gets trimmed down around 70k after link editing.
this seems ever-so-slightly excessive to me, especially since 37 spare mb on
disk is a fairly rare circumstance around here (had to trim my account back).
the resulting executable works as expected... [UNLIKE ABSOFT FORTRAN, WHICH
DIES HORRIBLY]

so, anyone else experience this?  porting f2c was very painless...  also, these
huge files do not get generated by f2c/gcc or f2c/cc on our hp9000 systems.

-------------------------------------------------------------------------------
dwatola @ nextasy2.eecs.wsu.edu or @ yoda.eecs.wsu.edu
'the world is my toaster oven'