Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84 +MMDF+MULTI+2.11; site kcl-cs.UUCP Path: utzoo!linus!philabs!cmcl2!seismo!mcvax!ukc!kcl-cs!agjenkin From: agjenkin@kcl-cs.UUCP (Alun Jenkins) Newsgroups: net.micro,net.arch Subject: Re: Z800 & Z8000000000 preliminary specs to net.jokes please. Message-ID: <578@west44.kcl-cs.UUCP> Date: Sat, 25-May-85 11:34:27 EDT Article-I.D.: west44.578 Posted: Sat May 25 11:34:27 1985 Date-Received: Sat, 1-Jun-85 14:15:10 EDT References: <627@abnji.UUCP> <413@rtech.UUCP> Reply-To: agjenkin@kcl-cs.UUCP (Alun Jenkins) Organization: Department of Computing, Kings College, University of London. Lines: 40 Xref: linus net.micro:9343 net.arch:1107 Xpath: kcl-cs west44 Ha!! If you had even bothered to read the Zilog spec for the Z80k you would see that the 68000 looks like a mere toy in comparison. Does the 68k have an on chip MMU variable size segments, cache that run at 25MHz , possible contiguous memory of 2^32 bytes. 32032 comes close but cant process as fast. As for instruction sets, so the Z80k has a weird instruction layout but what an instruction set. Basic spec looks something like this...... Features 1. 32 Bit architecture 2. many data types (bit, bit field, logical, signed int ,string ! etc..... 3. Z8000 binary compatible. All internal data paths are full 32 bit implementations. The chip directly supports multiprocessing with memory interlocking. The MMU supports full memory protection. Anyway less of the technical drivel and on to the instruction set. Just a few examples (6502 programmers just drool quietly in the corner). CHK compare destination and source bounds and if out of bound then trap INDEX calculate array index: check scale and accumulate ENTER enter procedure. + EXIT procedure CPSDR compare string decrement & repeat If this chip does not succeed in a big way then the whole business sucks! Send flames to...................................................................... Alun Jenkins ...ukc!kcl-cs!agjenkin