Path: utzoo!utgpu!watserv1!watmath!att!tut.cis.ohio-state.edu!purdue!haven!mimsy!jds
From: jds@mimsy.umd.edu (James da Silva)
Newsgroups: comp.os.minix
Subject: Re: Sc 6.8 binary size
Message-ID: <26457@mimsy.umd.edu>
Date: 10 Sep 90 14:18:29 GMT
References: <4338@crash.cts.com>
Reply-To: jds@cs.umd.edu (James da Silva)
Organization: University of Maryland, Department of Computer Science
Lines: 25

In article <4338@crash.cts.com> cwr@pnet01.cts.com (Will Rose) writes:
>155,900 bytes of text, 52,640 bytes of data, 18,768 bytes of bss for a total
>of 227,308 bytes.  The actual file is 210,366 bytes.
> 
>Still won't fit in 64K+64K without unusual cunning; I hope you make it,
>though, because it would be very nice to have.

Remember, these sizes are for 32 bit instruction sets.  Small model 8086
code for the same program is going to be a *lot* smaller.  If the data
space contains many pointers, it's going to shrink quite a bit as well.
While sc is a *bit* large, it's fair game for a try.

>By the way, the current
>size record on the 7300 seems to be Kyoto lisp, with a 1.4 *Megabyte*
>binary.  Not knowing anything about lisp, I can't imagine what they put
>in a file that size - some of the whales they will keep catching perhaps?

That size includes the compiler, interpreter, dynamic loader, and entire
runtime library for a large, rich programming language with lots of library
routines.  The size isn't too bad, considering.  

Jaime
...........................................................................
: domain: jds@cs.umd.edu				     James da Silva
: path:   uunet!mimsy!jds	 	    Systems Design & Analysis Group