Furthermore, the address and data registers and buses are 16 bits and
the high 16-bits are shared ...
On Sun, 14 Jan 2024 14:30:51 -0500, EricP wrote:
Furthermore, the address and data registers and buses are 16 bits and
the high 16-bits are shared ...
No, in the 68000 family the A- and D- registers are 32 bits.
If you compare the earlier members with the 68020 and later, it becomes
clear that the architecture was designed as full 32-bit from the
beginning, and then implemented in a cut-down form for the initial 16-bit products. Going full 32-bit was just a matter of filling in the gaps.
On 16/04/2024 02:35, Lawrence D'Oliveiro wrote:
On Sun, 14 Jan 2024 14:30:51 -0500, EricP wrote:
Furthermore, the address and data registers and buses are 16 bits and
the high 16-bits are shared ...
No, in the 68000 family the A- and D- registers are 32 bits.
If you compare the earlier members with the 68020 and later, it becomes
clear that the architecture was designed as full 32-bit from the
beginning, and then implemented in a cut-down form for the initial 16-bit
products. Going full 32-bit was just a matter of filling in the gaps.
Yes, the 68000 was designed to have full support for 32-bit types and a 32-bit future, but (primarily for cost reasons) used a 16-bit ALU and
16-bit buses internally and externally. Some 68000 compilers had 16-bit int, some had 32-bit int, and some let you choose either, since 16-bit
types could be significantly faster on the 68000 even though the general-purpose registers were 32-bit.
Yes, I was referring to its 16-bit internal bus structure.
This M68000 patent from 1978 shows it in Fig 2:
Patent US4296469 Execution unit for data processor using
segmented bus structure, 1978
https://patents.google.com/patent/US4296469A/en
Sysop: | DaiTengu |
---|---|
Location: | Appleton, WI |
Users: | 914 |
Nodes: | 10 (1 / 9) |
Uptime: | 223:56:39 |
Calls: | 12,156 |
Calls today: | 12 |
Files: | 186,517 |
Messages: | 2,232,450 |