From xemacs-m  Tue Apr 15 19:13:44 1997
Received: from jagor.srce.hr (hniksic@jagor.srce.hr [161.53.2.130])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id TAA04540
	for <xemacs-beta@xemacs.org>; Tue, 15 Apr 1997 19:13:43 -0500 (CDT)
Received: (from hniksic@localhost)
          by jagor.srce.hr (8.8.5/8.8.4)
	  id CAA21802; Wed, 16 Apr 1997 02:13:40 +0200 (MET DST)
To: Zlatko.Calusic@CARNet.hr
Cc: xemacs-beta@xemacs.org
Subject: Re: [comp.emacs.xemacs] Re: multi-threaded XEmacs lisp interpreter
References: <m2wwq3svck.fsf@altair.xemacs.org> <87k9m3zvth.fsf@atlas.infra.CARNet.hr>
X-URL: ftp://gnjilux.cc.fer.hr/pub/unix/util/wget/
X-Attribution: Hrv
X-Face: &}4JQk=L;e.~x+|eo]#DGk@x3~ed!.~lZ}YQcYb7f[WL9L'Z*+OyA\nA
        EL1M(".[qvI#a2E6WYI5>>e7'@_)3Ol9p|Nn2wNa/;~06jL*B%tTcn/X
        vhAu7qeES0\|MF%$;sI#yn1+y"
From: Hrvoje Niksic <hniksic@srce.hr>
Date: 16 Apr 1997 02:13:40 +0200
In-Reply-To: Zlatko Calusic's message of 16 Apr 1997 01:53:58 +0200
Message-ID: <kig3esr964r.fsf@jagor.srce.hr>
Lines: 43
X-Mailer: Gnus v5.4.45/XEmacs 19.15

Zlatko Calusic <Zlatko.Calusic@CARNet.hr> writes:

> {Solaris 2.5.1 - UltraSparc} [~]% size =xemacs
> text    data    bss     dec     hex     filename
> 1122728 2038937 0       3161665 303e41  /usr/local/bin/xemacs
> 
> {Digital Unix 4.0 - Alpha} [~]% size =xemacs
> text    data    bss     dec     hex
> 2031616 3391488 0       5423104 52c000
>

Thanks.  Here are the results for XEmacs 20.1-b15, its temacs and GNU
Emacs 19.34 on Digital Unix 4.0:

{bjesomar}[~/work/xemacs-20.1-b15]$ size ./src/temacs 
text    data    bss     dec     hex
2531328 1523712 255968  4311008 41c7e0

{bjesomar}[~/work/xemacs-20.1-b15]$ size ./src/xemacs    
text    data    bss     dec     hex
2531328 3825664 0       6356992 610000

{bjesomar}[~/work/xemacs-20.1-b15]$ size =emacs
text    data    bss     dec     hex
1146880 2179072 0       3325952 32c000

> For long time I wanted to know what's the real purpose of unexec.

The practical purpose of unexec is for you not to wait half-hour upon
each XEmacs startup. :-)  The whole XEmacs state, including all the
Lisp code loaded into temacs is dumped into the xemacs binary.

The temacs results are very important: as far as I see it, all the
Lisp code (some 2M) adds to the data segment, which explains why it's
so large for XEmacs.

The question is: should the preloaded Lisp code found in the data
segment be shared?  *Can* it be shared -- it is not read-only.

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
The end of the world is coming...  SAVE YOUR BUFFERS!

