north@princeton.UUCP (Stephen C. North) (02/28/85)
why do we think the CCI machine is really a VAX? north/honey
guy@rlgvax.UUCP (Guy Harris) (03/02/85)
> why do we think the CCI machine is really a VAX?
What, just because the following code appears in its assembler?
##
## Copyright (c) 1982 Regents of the University of California
## @(#)instrs 4.9 6/30/83
.
.
.
# 270a aoblss AOBLSS S 0x2f 3 R L M L B W
.
.
.
Don't try and depend on the byte order, though (it's big-endian), don't
depend on auto-increment and auto-decrement addressing modes (they only
work on the stack pointer), and don't depend on instructions like MOVC5
(we have NUL-terminated string instructions) or CRC16 (we don't have it).
Besides, the CPU is only 5 boards, not 27 or so...
Guy Harris
{seismo,ihnp4,allegra}!rlgvax!guynorth@down.FUN (Stephen C North) (03/04/85)
You were close, Guy. But it's not just the assembler that's the same, it's the opcodes. For example, see Figure 1. north/honey Figure 1 ---------------------------- mnemonic VAX CCI -------- --- --- bicpsw b9 9b calls fb bf insque 0e e0 ldpctx 06 60 movzbw 9b b9 probew 0d d0 pushr bb bb called storer on CCI aobleq f3 2f tricky aoblss f2 3f ditto