[Home]History of Motorola 68000

HomePage | Recent Changes | Preferences

Revision 13 . . October 23, 2001 9:34 am by Ray G. Van De Walker [Rewrote the orthogonality discussion from NPOV]
Revision 12 . . October 23, 2001 9:26 am by Ray G. Van De Walker [Rewrote the code size parts as NPOV]
Revision 11 . . (edit) October 19, 2001 7:25 pm by (logged).37.81.xxx [Added links to later family members.]
  

Difference (from prior major revision) (author diff)

Changed: 27c27
The assembly language was orthogonal. That is, instructions were divided into operations and address modes. Almost all address modes were available for almost all instructions. (Not really true. Exactly which combinations worked was remarkably irregular and difficult to remember.)
The designers attempted to make the assembly language was orthogonal. That is, instructions were divided into operations and address modes. Almost all address modes were available for almost all instructions. Many programmers disliked the "near" orthogonality, while others were grateful for the attempt.

Changed: 29c29
This was a remarkable convenience. However, at the bit level, the person writing the assembler would clearly see that these "instructions" could become any of several different op-codes. It was quite a good compromise because it gave almost the same convenience as a truly orthogonal machine, and yet also gave the CPU designers freedom to fill in the op-code table.
At the bit level, the person writing the assembler would clearly see that these "instructions" could become any of several different op-codes. It was quite a good compromise because it gave almost the same convenience as a truly orthogonal machine, and yet also gave the CPU designers freedom to fill in the op-code table.

HomePage | Recent Changes | Preferences
Search: