6 ms·
> A RISC based implementation of the Apple II 6502 Processor: In mid ’85 I performed an analysis that showed a simple RISC style implementation of a 16‐bit bin
by klodolph 8y ago
> A RISC based implementation of the Apple II 6502 Processor: In mid ’85 I performed an analysis that showed a simple RISC style implementation of a 16‐bit binary compatible superset of the 8‐bit microprocessor used in the Apple II 6502, along with some judicious use of on‐chip caching, could substantially improve performance – to the point of potentially outperforming the 68000 used in the Mac, and given the simplicity of the 6502 the implementation was “doable” by a small team.
This is fascinating, and I wonder if any of the design work has survived.
- ddingus 8y agoSeconded. There is a pretty active Apple 2 community out there who would definitely be interested. My one question, given what we just read is, "What were the plans for the 1mhz system bus?"
- agumonkey 8y agoreminds me of an alleged quote about Michelin: "We can make undestructible tires, but why would we"
- nikanj 8y agoI think it was clear even then that the 68k had an upgrade path ahead of it. Beefing up the 6502 would have been an evolutionary dead end, and left Apple with an even more fragmented market share
- microtherion 8y agoUltimately, the 68k upgrade path was not THAT long. But I agree with the rest of your argument. As the triumph of x86 has shown, in microprocessors, superior shipping volume can drive investment that covers a multitude of architectural sins. And the 68K architecture was quite nice, actually.
- zozbot123 8y agoThe Motorola 68k was just as much of a dead end in practice... and it took the Amiga and Atari ST platforms down with it, plus possibly others (it was used in a LOT of places). It's only very recently that the Apollo core has been reviving it.
- wk_end 8y agoHorrendous mismanagement at both Commodore and Atari respectively took the Amiga and ST down; the writing was on the wall for those platforms long before the 68k architecture was ever starting to plateau. Even Apple's transition to PPC arguably had more to do with everyone (Motorola included) hopping on the RISC hype train than with some kind of fundamental performance limitations inherent to the 68k architecture.
- jandrese 8y agoThe 68k was also used in Sun Workstations at the time. Motorola's failure to improve on it left a lot of companies in the lurch, some of which never recovered. Certainly it started out in no worse a place than the 8086, and Intel was able to improve on that for many years. It seemed like after the 68040 Motorola just kind of gave up on developing chips, and then Intel launched the Pentium and ate their lunch.
- wmf 8y agoAfter the 68040 Motorola was working on PowerPC because they thought it was impossible to improve performance and maintain 68K compatibility.
- ken 8y agoThere was an article here a little while ago about the 1980's at Apple (can't seem to find it right now, sorry) where someone said they didn't go with x86 because someone (Motorola?) convinced them it could only scale up to some pretty unimpressive speeds (sub-100 MHz?). It turns out, if you try hard enough, any CPU architecture can have lots of room to grow. The Intel 8008 wasn't an "evolutionary dead end", so I don't see any reason the 6502 was, except the decision to let it be.
- jacquesm 8y agoI'm not sure about that particular design but there was the 65816. https://en.wikipedia.org/wiki/WDC_65816/65802 https://en.wikipedia.org/wiki/WDC_65816/65802 It wasn't exactly a RISC but it was a vast improvement over the regular 6502, and was also co-developed with Apple.
- pinewurst 8y agoThat's how ARM originated - as a simple, yet fast processor philosophically descended from the 6502. In an alternate universe, ARM could very well have stood for Apple RISC Machine.
- Taniwha 8y agoPete (the guy who's resume this is) may not have been as big a fan of the ARM back then ... he worked on the Newton, built the Hobbit CPU which was canned and replaced by an ARM just after he got working silicon back ....
- JonathonW 8y agoIn a sense, it sort of does-- Apple was involved with ARM fairly early in their lifecycle, collaborating with their design team to build the ARM6 which was ultimately used in the Newton. That's around the same time as Acorn spun out the ARM design team into its own company, and dropped the Acorn out of its name in the process (first became Advanced RISC Machines, Ltd., then just ARM Ltd.).
- ken 8y agoThat level of performance had already been achieved. According to a French article (on www.apple-iigs.info) linked from Wikipedia, the 65C816 (introduced 1983) could 'easily' run at 16 MHz. It was only limited to 2.8 MHz so it wouldn't compete with the 7.8 MHz Macintosh. This is believable, as IIgs accelerator cards above 10 MHz were popular add-ons.
- klodolph 8y agoIs the 65C816 running at 16 MHz competitive with a 68000, though? The 68k has a 16-bit data bus, compared to the 8-bit bus of the 65C816, and the 68k has a bunch of registers on top of that. Although 68000 instruction timings weren't that great.
- rasz 8y ago65C816 is faster than 68K, what good is 16 bit bus when you spend at minimum 4 clocks fiddling your thumbs.
- klodolph 8y agoOk, I see what you mean. Even then, at that point in history it was becoming clear that memory speed would not keep up with processor speed, so I can understand why the 16-bit bus seemed like the way of the future.
- rpiguy 8y agoThe primary factor holding back the 65C816 was the required RAM speed. The 65XX processors required RAM almost twice as fast as the same clocked X86 or 68K. An 8Mhz 65C816 requires 70ns RAM, whereas an 8Mhz 286 or 68K can use 140ns RAM without wait states. 70ns RAM was very expensive until the early 90s, at which point the 65C816 had already missed its window.
- Taniwha 8y agoRemember that "RISC" in 1985 was barely a word, RISC was, in part a response to the changing costs/speed tradeoffs between memory and CPUs - prior to ~'86 memory was slow and expensive - instructions were heavily encoded to reduce instruction fetch bandwidth - RISC instructions are bigger, easier to encode, they essentially assume caches A "RISC 6502" likely wasn't a "reduced instruction set 6502" it was more likely a "non-microcoded single cycle CPU running the 6502 instruction set" (possibly with some address extension past 64k and 16-bit data paths) - remember that even the very first 68ks available in '79 was a 32-bit CPU architecture from day one (even if it had 24-bit addressing and an external 16-bit data bus), while the 8088/8086/80186/80286 were all 16-bit (the 80386 didn't show up until 6 years later)
- zozbot123 8y ago> A "RISC 6502" likely wasn't a "reduced instruction set 6502" it was more likely a "non-microcoded single cycle CPU running the 6502 instruction set" The 6502 was not microcoded. It used simple wired logic (implemented in a PLA) to "decode" and "run" opcodes by driving other parts of the chip. This is why many unimplemented opcodes "work", sometimes with recognizable effects.
- Taniwha 8y agoUsing a PLA vs microcode to sequence a multiple clock instruction execution is sort of a no-op (ie they're pretty much the same thing) when comparing how a CISCy chip works compared with a RISC which has instructions designed to be easily decoded by random logic and executed in one clock
- zozbot123 8y agoThe 6502 and Z80 were both 'CISCy' chips, but they were very different when it came to instruction execution. While formally a PLA may have been used to "sequence a multiple-clock instruction" in both, in a practical sense 6502 instructions took a handful of clock cycles to execute, not very dissimilar from later RISC chips. I think your point is more valid for the Z80 than for the 6502.