Return-Path: Delivery-Date: Received: from leopard.cs.byu.edu (no rfc931) by swan.cl.cam.ac.uk with SMTP (PP-6.5) outside ac.uk; Wed, 9 Nov 1994 18:39:35 +0000 Received: by leopard.cs.byu.edu (1.38.193.4/16.2) id AA22727; Wed, 9 Nov 1994 11:14:43 -0700 Sender: info-hol-request@lal.cs.byu.edu Errors-To: info-hol-request@lal.cs.byu.edu Precedence: bulk Received: from tango.rahul.net by leopard.cs.byu.edu with SMTP (1.38.193.4/16.2) id AA22719; Wed, 9 Nov 1994 11:14:41 -0700 Received: from bolero.rahul.net by tango.rahul.net with SMTP id AA13240 (5.67b8/IDA-1.5); Wed, 9 Nov 1994 10:06:14 -0800 Received: by bolero.rahul.net id AA13256 (5.67b8/IDA-1.5); Wed, 9 Nov 1994 10:06:13 -0800 Date: Wed, 9 Nov 1994 10:06:11 -0800 (PST) From: Bill Hogan Subject: Re: Peter Bumbulis: Re: saving a HOL image To: Phil Windley Cc: info-hol@leopard.cs.byu.edu In-Reply-To: <9411091501.AA25730@jaguar.cs.byu.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I have a question about the size of the hol88 2.02 executable. After compiling hol88 2.02. using gcl-1.0, I ran `strip hol', and I got this: -rwxrwxr-x 1 root root 7119876 Nov 3 12:07 hol Later, I decided to make a backup copy, so I ran `zip hol.zip hol' and got this: -rw-r--r-- 1 root root 1974189 Nov 3 17:44 hol.zip I am wondering if anything can be done to get the size of the gcl-compiled HOL executable closer to 1.97MB than to its present 7.12 MB. If so, at least on Linux, it seems to me it would be much easier to keep the entire executable in RAM, rather than being forced on occasion to swap sections of it back and forth between disk and RAM. Bill