3 ms·
We know that Apple was investigating the successor to the 65816 as used in the then current //GS https://mirrors.apple2.org.za/apple2.caltech.edu/miscinfo/65xxx
by spongeb00b 6y ago
We know that Apple was investigating the successor to the 65816 as used in the then current //GS https://mirrors.apple2.org.za/apple2.caltech.edu/miscinfo/65xxx.chronology https://mirrors.apple2.org.za/apple2.caltech.edu/miscinfo/65...
- rbanffy 6y agoI often wonder what a 65832 (or 65864) would look like. For instance, I'd add instructions treating all registers as floating point (fp32 and fp64). And have full 32/64 bits data buses.
- duskwuff 6y agoWonder no more! Here's a preliminary datasheet. http://archive.6502.org/datasheets/wdc_w65c832_preliminary_mar_1991.pdf http://archive.6502.org/datasheets/wdc_w65c832_preliminary_m... The part was never produced, in large part because Apple wasn't interested in continuing the IIgs line.
- ksherlock 6y agoIn this case, it's better to imagine what could have than to see what it would have been. That's basically the 65816 documentation but 16 is find/replaced with 32. Some of time. A, X, and Y are 32-bit but the data bus is still 8-bit, address space is still 24-bit, stack, direct page, and program counter are still 16-bit.
- rbanffy 6y agoOne of the first things I'd throw out is binary compatibility. Making it source-compatible at the assembly level would be enough and would free a lot of possibilities that being attached to old code wouldn't.