Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!samsung!munnari.oz.au!sirius.ucs.adelaide.edu.au!sirius!jeremy From: jeremy@cs.ua.oz.au (Jeremy Webber) Newsgroups: comp.arch Subject: Re: Smart Linking Message-ID: Date: 8 Jun 90 00:08:13 GMT References: <9557@pt.cs.cmu.edu> Sender: news@ucs.adelaide.edu.au Organization: Digital Arts Film and Television Lines: 18 In-reply-to: lindsay@MATHOM.GANDALF.CS.CMU.EDU's message of 7 Jun 90 15:54:48 GMT In article <9557@pt.cs.cmu.edu> lindsay@MATHOM.GANDALF.CS.CMU.EDU (Donald Lindsay) writes: In article Rick.Rashid@CS.CMU.EDU writes: >The runtime size of a lot of X programs (e.g. xterm, xclock, X, etc.) >varies strongly with the page size of the machine being used. [ observations about page sizes and smart linking ] Of course, if the X libraries have been made sharable (which they should on a machine which supports shared libraries) it becomes harder to allocate more than one module to a page. It's still worth persuing though on machines with large page sizes though. Does anyone's linker handle this situation neatly? -- -- Jeremy Webber ACSnet: jeremy@chook.ua.oz Digital Arts Film and Television, Internet: jeremy@chook.ua.oz.au 60 Hutt St, Adelaide 5001, Voicenet: +61 8 223 2430 Australia Papernet: +61 8 272 2774 (FAX)