Xref: utzoo comp.emacs:4629 gnu.emacs:160
Path: utzoo!utgpu!watmath!clyde!att!rutgers!cmcl2!nrl-cmf!ames!sgi!arisia!weikart
From: weikart@arisia.Xerox.COM (Scott Weikart)
Newsgroups: comp.emacs,gnu.emacs
Subject: Possible to do #undef NO_REMAP for V/386?
Keywords: 386,NO_REMAP
Message-ID: <442@arisia.Xerox.COM>
Date: 13 Nov 88 03:19:05 GMT
Organization: Xerox PARC
Lines: 29


I'm using GNU Emacs 18.52 on a 386/AT clone, with MicroPort Unix and Everex's
Enix (both derived from AT&T V/386, System 5 Release 3.0).  Has anyone been
able to successfully dump a GNU Emacs with the read-only data region remapped
into the text region, i.e. with #undef NO_REMAP ?  I got the following comment
on this:

> I do not know the answer.  The problem is that the data space starts
> well away from the text space.  Supposedly ld -N can move them closer,
> but that appears to be broken: it doesn't work for any program I've
> tried, much less GNU emacs.  I suggest posting to gnu.emacs and seeing
> if anyone has found a way.  Let me know if you find one.  Good Luck!
> ---
> James R. Van Artsdalen      james@bigtex.cactus.org      "Live Free or Die"
> Home: 512-346-2444 Work: 338-8789       9505 Arboretum Blvd Austin TX 78759

Does anyone know if ld -N works in Release 3.1 or 3.2 of V/386?

Also, it has been suggested that #undef NO_REMAP isn't as important with
System V release 3, because under Vr3 a new exec shares an existing data
region, and uses copy on write to replace the data region pages that get
changed, so that in general there is only one copy of the Emacs libraries in
memory even if there are multiple Emacses running.  Is this correct?

-scott
-- 
weikart@arisia.xerox.com
pyramid!cdp!scott
(415)322-9069