The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] tool (that wnj wrote?) that reduced the data segment size?
Date: Fri, 27 Nov 2015 16:03:56 -0800	[thread overview]
Message-ID: <20151128000356.GC21698@mcvoy.com> (raw)
In-Reply-To: <alpine.BSF.2.11.1511281038260.60532@aneurin.horsfall.org>

On Sat, Nov 28, 2015 at 10:44:58AM +1100, Dave Horsfall wrote:
> On Fri, 27 Nov 2015, Larry McVoy wrote:
> 
> > I've gotten sucked into an embedded system project and they are running 
> > out of memory.  I have a vague memory of some sort of tool that I think 
> > Bill Joy wrote (or maybe he told me about it) that would do some magic 
> > processing of all the string constants and somehow it de-dupped the 
> > space.
> > 
> > Though now that I'm typing this that doesn't seem possible.  Does this 
> > ring a bell with anyone?  I'm sure it was for the PDP 11 port.
> 
> I think you're referring to an abomination called "xstrings" (or "xstr"?).

Yup, that's it.  Cool, thanks.

> It was described by a colleague of mine as "about as subtle as a car 
> crash"; it worked by comparing strings at compilation time, even unto the 
> tails of said strings.
> 
> Woe betide the user if any string was changed at run time...

I get it.  I also get that I have 32KB of RAM and I'm down to my last 1.2KB.

--lm



  reply	other threads:[~2015-11-28  0:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-27 22:26 Larry McVoy
2015-11-27 23:44 ` Dave Horsfall
2015-11-28  0:03   ` Larry McVoy [this message]
2015-11-30  2:45     ` Erik E. Fair
2015-11-28 14:58 Doug McIlroy
2015-11-28 23:30 Norman Wilson
2015-11-28 23:38 ` Charles Anthony
2015-11-30  3:07   ` John Cowan
2015-11-30  5:38     ` Nick Downing

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151128000356.GC21698@mcvoy.com \
    --to=lm@mcvoy.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).