Path: utzoo!attcan!uunet!peregrine!elroy!ames!joyce!cslb!porthos!aida From: aida@porthos.csl.sri.com (Hitoshi Aida) Newsgroups: comp.unix.wizards Subject: Re: Problem with xstr Message-ID: <6646@cslb.CSL.SRI.COM> Date: 22 Sep 88 20:06:48 GMT References: <4252@thorin.cs.unc.edu> <145@taux02.UUCP> Sender: usenet@cslb.CSL.SRI.COM Reply-To: aida@csl.sri.com (Hitoshi AIDA) Organization: Computer Science Lab, SRI International Lines: 15 In article <145@taux02.UUCP> amos@taux02.UUCP (Amos Shapir) writes: >Unless you use a pdp11 with separate I/D space, the solution is to just >throw out all the xstr stuff from your makefiles, and compile normally >instead. >Xstr is a hack for putting strings, which are supposed to be read-only, >into the executable's text (code) space. This makes more room for data >on machines with limited address space. On 32-bit machines, this >approach is obsolete and causes more trouble than benefit. No! You can't put strings into code segment on separate I/D machines! The reason why xstr makes more room is because same strings will be shared within a program, not because they will go to code segment. -------- Hitoshi AIDA (aida@csl.sri.com) Computer Science Lab, SRI International