Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uflorida!ziggy!usfvax2!tscs!tct!chip From: chip@tct.uucp (Chip Salzenberg) Newsgroups: comp.arch Subject: Re: Large executables: Where's the space going? Message-ID: <266D740B.B2C@tct.uucp> Date: 6 Jun 90 21:22:19 GMT References: <266B4748.28579@paris.ics.uci.edu> <483@helios.prosys.se> Organization: ComDev/TCT, Sarasota, FL Lines: 11 According to ath@prosys.se (Anders Thulin): >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. Any window system where a clock program binary is larger than 30K has a problem. No, I take that back. Such a window system *is* a problem. -- Chip Salzenberg at ComDev/TCT ,