Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!apple!oliveb!sun!limes
From: limes@sun.com (Greg Limes)
Newsgroups: comp.arch
Subject: Re: System size (was Re: Criteria for comparing RISC processors)
Message-ID: <LIMES.89Apr27231833@ouroborous.wseng.sun.com>
Date: 28 Apr 89 06:18:33 GMT
References: <18120@winchester.mips.COM>
Sender: news@sun.Eng.Sun.COM
Organization: Sun Microsystems, Inc.
Lines: 39
In-reply-to: schow@bnr-public.uucp's message of 27 Apr 89 03:04:47 GMT

In article <18120@winchester.mips.COM>mash@mips.COM (John Mashey) writes:
>Hmmm.  here's an interesting question for the net: how about offering examples
>of LARGE programs, either in:
>	# of files
>	# of lines of source
>	# of bytes of code generated
>
>	what machine & OS & language does this run on?
>	what does it do?

In article <441@bnr-fos.UUCP>schow@bnr-public.uucp (Stanley Chow) writes:
[Bell Northern Research's system including SOS written in PROTEL,
 see his article for details]
>    Files:          3  * 10**4
>    lines of code:  1  * 10**7
>    binary size:    5  * 10**6  up to 4 * 10**7 bytes
>    Workers:        4  * 10**3  known to system
>		     2  * 10**3  actually changing code 

The SunOS 4.0.3 kernel comes out to:
     ~700 files,
  ~200000 lines,
       ~1Mb binary for each archetecture.

The entire SunOS distribution is, of course much larger; if you want
to call it a "large program" -- stretching things a bit, but it all
interacts tightly and all gets maintained together -- the numbers
would look something like:

    ~6000 files
~14000000 lines
      ~50Mb of binaries for each archetecture

This is only for the machines built and supported by Workstation
division, i.e. Sun-2, Sun-3, Sun-3x, and Sun-4. The source trees for
the Sun-386i and the Sun-4c (SPARCstation 1) are entirely separate,
although probably quite similar in size and layout.

-- Greg Limes [limes@sun.com]