4 ms·
The trouble with the CISC vs RISC interpretation is that the x86 was CISC but trashed all other architectures in the 1990s especially RISC architectures includi
by PaulHoule 1y ago
The trouble with the CISC vs RISC interpretation is that the x86 was CISC but trashed all other architectures in the 1990s especially RISC architectures including
https://en.wikipedia.org/wiki/DEC_Alpha https://en.wikipedia.org/wiki/DEC_Alpha
and Intel’s own
https://en.wikipedia.org/wiki/Itanium https://en.wikipedia.org/wiki/Itanium
I think it’s as simple as a mass market architecture that sells more units can justify more investment than anything that sells fewer units. If DEC had been able to steal market share from the 386 with a VAX based product it might have been able to take the 386’s place but from a business perspective they didn’t want to cannabalize sales of higher margin minicomputers. The transition from bipolar to CMOS was also difficult because it did mean a regression in performance, IBM addressed this in the 390 by introducing a clustering solution but it was a bold and risky move.
- fredoralive 1y agox86 isn’t a VAX though, not all CISC architectures are equally complex (or RISC arch’s reduced), and VAX does have a reputation for being a particularly CISCy CISC. We don’t really know fully if the same tricks would have worked as well with it.
- TMWNN 1y agoAnd, in fact, Mashey specifically discusses what you identified, and what Houle wrote (rushing to post a gotcha on HN, obviously without having read Mashey's lengthy writings).
- kjs3 1y agoYeah, always good to read it. He goes into some detail about a hypothetical VAX-based x86 killer, tho some of it is "when I had beers with the guys designing the VAX..." reminiscing. Comp.arch was something really special. Guys like Mash, John McCalpin, Bob Colwell, Eugene Maya, Mitch Alsup, Terje Mathisen...folks who really, really understood computers, what the real tradeoffs are, did actual homework instead of guessing, and were generally able to discuss the issues without being jerks. Good times.
- PaulHoule 1y agoWhat I've read was that DEC had a huge amount of regret over the PDP-11 having too small of an address space. It could be that experience led them to think the answer to their problems was to be early to market in the 64-bit age with the Alpha. They did have VMS for the Alpha and later Win NT but high-powered RISC processors were a crowded space in the 1990s.
- panick21_ 1y agoYou can learn all about the details of how and why Alpha was developed: https://www.computerhistory.org/collections/catalog/102738264/ https://www.computerhistory.org/collections/catalog/10273826... Its in Part 2. If I remember correctly, it was basically 64bit because Alpha was basically a (good) virus inside of DEC. Or maybe like secret society that revolted against the leader of the company. Olson had killed 32 bit PRISM and they already had VAX that was 32 bit and people making processor for it. To get people all over DEC to buy into Alpha (Alpha barley had any budget of it own) it had to be something new, and winning 64 bit did make sense. Olson really killed basically everything that make sense, that DEC survived so long with Olson as CEO is kind of crazy. The amount of horrible decision starting as early as the early 70s is kind of crazy. VAX had also been early, driven by Gordon Bell not Olson, very few of the competitors had 32 bit processors then, and people like Data General and Prime struggled to develop them in response. Funny enough a hardware guy on the VAX team basically proposed RISC-like architecture but it was rejected because they optimized for code size. To bad that they didn't hit on the idea of compressed instructions.
- drewg123 1y agoAlpha died because HP decided that Itanium was the one true processor and killed PA-RISC and Alpha (which it had acquired) in favor of itanic. I'd love to live in a world where Alpha had been free to compete on merit. Who knows, maybe we'd all be running Alpha desktops and laptops. DEC was (slowly) on its way to making alpha mass-market. Around the time of the Compaq acquisition, they started offering the CPU to 3rd parties to design their own boards. One example is the API UP1000, which had an AMD irongate chipset and an EV6 CPU. (I had an early sample that I ported FreeBSD/alpha to). Alpha was the only somewhat popular non-x86 platform that Windows NT ran on. FX!32 made it possible to run x86 apps, like Rosetta on Apple M4. Alpha was the first non-x86 linux port.. I was at the USENIX where John "Maddog" Hall gave Linus an Alpha (I think it was a Multia) Alpha was also the first 64-bit FreeBSD port (which I contributed to), and paved the way for amd64. Alpha had a HUGE amount of momentum when HP summarily executed it. I still hate HP with a passion, and I still won't buy anything from them, 20+ years later.
- chasil 1y agoI have heard that the Alpha architecture maintainers said that their options for improvements were limited, and themselves advocated ending development. What I also know is that DEC chose ARM for low-power applications, because the design of the Alpha was simply not capable of scaling to lower power usage. "According to Allen Baum, the StrongARM traces its history to attempts to make a low-power version of the DEC Alpha, which DEC's engineers quickly concluded was not possible." https://en.m.wikipedia.org/wiki/StrongARM https://en.m.wikipedia.org/wiki/StrongARM Power efficiency was soon to become a chief concern. This alone would have ended the Alpha.
- sillywalk 1y ago> I have heard that the Alpha architecture maintainers said that their options for improvements were limited, and themselves advocated ending development. Interesting. One of the main design principles for the Alpha was for longevity, and to have a thousand-times increase in performance over 25 years.[0] [0] https://danluu.com/dick-sites-alpha-axp-architecture.pdf https://danluu.com/dick-sites-alpha-axp-architecture.pdf
- panick21_ 1y agoI don't think that x86 beat Alpha. Alpha was more expensive because of a bunch of reason, but just in terms of how much performance they got out of the same amount of transistors, Alpha was better. But I think generally speaking you are right, the size of the teams that all the RISC people had compared to the amount of resources Intel had was not really comparable. > The transition from bipolar to CMOS was also difficult because it did mean a regression in performance DEC already had the VAXCluster by 1983 and they were working on a bunch of implementations at the same time. They did a lower performance VAX already when the did a AMD 29000 bit-slice implementation in 1982. So they did know the value lower performance. By 1985 they had matched the 780 in a single chip. Basically by 1988 the CMOS version was already faster then anything else. The transition was really just difficult because some people (who happen to be CEO) didn't want to see the reality.
- p_l 1y agox86 is closer to RISC designs than "respectable CISC" of the era that defined the split between RISC and CISC. It's why huge chunk of instructions on modern x86 can execute in essentially one cycle - the encoding is not all that complex, the instructions are also not all that complex, and majority of "complex addressing" can be pipelined into having an extra stage capable of doing "LEA" instruction on it's own, unlike either VAX or 68k At the point Alpha got killed, it was the fastest option, and then HP had to resurrect it anyway because the supposed Alpha killer (Itanium) was slower in practice. That said, the killing was done by Compaq, not HP - and done fully on politics/vibes not actual thorough thinking. A lot of late Alpha design ended up being "inherited" in ways by later x86 cores - Athlon reused chunks of EV6 architecture which also enabled cheap Alpha motherboards (but made Athlon-MP extra expensive, unfortunately). K8 heavily drank from experience of the team members who worked on EV7 which exhibited the same fabric structure.