Subject: Re: Compiler timings on varous MVII NetBSDs etc.
To: NetBSD Bob <>
From: Manuel Bouyer <>
List: port-vax
Date: 01/22/2001 23:05:52
On Mon, Jan 22, 2001 at 02:28:53PM -0500, NetBSD Bob wrote:
> Over the weekend I did some simple compiler tests on the NetBSDs
> and other OS's I have up on my MicroVAX II critters.
> The test suite was a very simple program, gkermit.  I chose that
> because it is simple, stupid, and compiles on anything.  Yeah, I know
> that is not a real benchmark killer, but, it points out some of the
> compiler issues that I am struggling with on a less-than-one VUP
> VAXencritter.  The machine was a MVII KA630 13M ram with scsi disks,
> except for the 4.3BSD box which had only 7M ram and esdi drives.
> All I did was boot up on different identical Fuji scsi drives to
> bring up different OS's, then do a make, timing from the <CR>
> until the make finished.
> OS                           Gkermit compile time (m:s)
> --------------------------   --------------------------
> 4.3BSD-Tahoe PCC             3:01                 
> Ultrix 4.2 VAX-C             2.50
> NetBSD-1.2 gcc 2.72          5:05
> NetBSD-1.3 gcc 2.72.1        6:07
> NetBSD-1.4.3 gcc 2.91        7:08
> NetBSD-1.5 gcc 2.91          7:40
> --------------------------   --------------------------

Well, there are a lot of things to take in account here:
- the compiler itself
- the libs against which the compiler is linked
- the include files cpp has to parse
- the make binary (and maybe sh, too).
- the kernel

Especially the last 4 items needs to be evaluated individually between
1.4.3 and 1.5

Manuel Bouyer <>