Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!seismo!rochester!ritcv!tropix!rcm
From: rcm@tropix.UUCP (Robert C. Moore)
Newsgroups: net.micro.68k,net.micro.16k
Subject: 68020 vs 16k
Message-ID: <179@tropix.UUCP>
Date: Fri, 27-Jan-84 22:56:48 EST
Article-I.D.: tropix.179
Posted: Fri Jan 27 22:56:48 1984
Date-Received: Sun, 29-Jan-84 22:20:57 EST
Lines: 29

Some further thoughts on the 68020 vs 16k:

	The 68020 will contain a cache for text refrerences, with
		only 2 clock cycles per instruction running from the
		cache.  The 16k doesnt have a cache.

	The 68020 provides indexed addressing modes (as does the vax
		and the 16k) and memory resident pointer addressing modes.

	The 68020 fpu, due out 3 months after the 020, provides full
		80 bit precision and a host of transcendentals.  The
		16k uses 32 and 64 bit presision, and no transcendentals.
		The fp instructions work into 8 80bit registers, making
		floating point register variables quite practical.  The
		16k provides 8 32bit (paired as 4 64bit) fp registers.
		Whetstones should look pretty good on the 020.

	The 68020 will be provided with clocks from 12 to 25 Mhz.  The
		design center is around 20 Mhz.  The 16k is hard to get
		above 6 Mhz.  They are hopeing for 10 Mhz eventually.

	The 68020 paged mmu will allow variable page size and number of
		levels.  This is fixed in the 16k's mmu.

	
	These and other considerations make the 68020 worth waiting for.

						bob moore
						inhp4|tropix|rcm