Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!rpi!uupsi!sunic!liuida!prosys!ath
From: ath@prosys.se (Anders Thulin)
Newsgroups: comp.arch
Subject: Re: Large executables: Where's the space going?
Message-ID: <483@helios.prosys.se>
Date: 6 Jun 90 06:33:04 GMT
References: <266B4748.28579@paris.ics.uci.edu>
Organization: Telesoft AB, Teknikringen 2A, S-583 30 Linkoping, Sweden
Lines: 18

In article <266B4748.28579@paris.ics.uci.edu> teami125@ics.uci.edu (klefstad 125b team i) writes:
>
>With all this talk of 1.3Meg 'xclock' executables, etc., has anyone
>done any digging to find exactly what is taking so much space? Obviously,
>it's library code, et. al., but which routines? Why? How much data?

I suspect that there's a mistake somewhere. I've checked the X
binaries on A/UX, Sun3(3.5), Aviion, Ultrix, and HPUX, and only in a
few cases have xclock (or any other binary) been larger than 300k.
None of these, it appears, use dynamic linking.

It seems more likely that the 1.3Meg figure refers to libraries/code
compiled with debug options on, which easily produces executables
larger than a meg.

-- 
Anders Thulin       ath@prosys.se   {uunet,mcsun}!sunic!prosys!ath
Telesoft Europe AB, Teknikringen 2B, S-583 30 Linkoping, Sweden