News for hackers. Stuff that matters.
Re:What do RISC and CISC mean in 2020? by fanf2 on Friday November 20, 2020 @01:22PM (#25163253)
I am also a fan of John Mashey’s analysis that you linked to! The key thing is that he counts things like instruction formats, addressing modes, memory ops per instruction, registers, and so on. There is a clear separation in the numbers between the RISCs and the CISCs.

What stuck out to me when I first read it 25 years ago is that the ARM is the least RISCy RISC, and x86 is the least CISCy CISC. At that time the Pentium was killing the 68060 and many of the RISCs, and it seemed clear that x86 had a big advantage in the relatively small number of memory ops per instruction.

Re:What do RISC and CISC mean in 2020? by microtherion on Friday November 20, 2020 @06:40PM (#25166486)
I'm not so convinced that x86 really had an architectural advantage. What Intel had was an enormous volume advantage, which allowed them to throw more resources at their designs than the competition.

In fact, Intel had such an advantage that they managed to bet on a completely failed architecture (Itanium) for more than a decade and not only maintain market position but knock out most RISC architectures during the time.

Re:What do RISC and CISC mean in 2020? by jcranmer on Friday November 20, 2020 @09:13PM (#25167365)
Linus has apparently argued that x86 really did have an architectural advantage: https://yarchive.net/comp/linux/x86.html. The argument here is that the CISC nature of x86 forced Intel to innovate microarchitecturally, and those microarchitectural innovations were more important for performance than the RISCy bits that x86 didn't adapt.

I'm not sure I completely buy into the reasoning, but I do believe that Intel (accidentally!) ended up with an architecture that compromised well between RISC and CISC ideas. When they tried to build a shiny RISC architecture, what we got was Itanium, which turned out to be a disaster in no small part because the sufficiently-smart-compiler ideas underlying RISC definitely didn't work out.

Re:What do RISC and CISC mean in 2020? by microtherion on Friday November 20, 2020 @10:25PM (#25167661)
Linus' own career illustrates my point, I think: Transmeta had advantages in low power design at one point, then Intel simply threw more resources at the problem.

> When [Intel] tried to build a shiny RISC architecture, what we got was Itanium, which turned out to be a disaster

That was a shiny VLIW architecture, more or less. The shiny RISC disaster was the 860. And they also had the 432, a fancy CISC disaster, to their name.

Re:What do RISC and CISC mean in 2020? by gpderetta on Friday November 20, 2020 @08:31PM (#25167160)
x86 doesn't have indirect references. Apparently in ~1995 it was to hard to build an OoO engine that could deal with those. Intel just about manged to bolt OoO on x86 while VAX and 680x0 died. AMD also managed to do it in 1996, so it was not just about resources.
Re:What do RISC and CISC mean in 2020? by microtherion on Friday November 20, 2020 @09:10PM (#25167352)
Can you explain what exactly you mean with "indirect references" here?

Edit: To clarify my question — to the best of my knowledge, while the VAX had a higher level of indirection of indirection in instructions than the x86, the 68K has exactly the same level of indirection.

Re:What do RISC and CISC mean in 2020? by jcranmer on Friday November 20, 2020 @09:14PM (#25167372)
Some architectures have instructions such as LDI imm that load MEM[MEM[imm]]--indirect memory references.
Re:What do RISC and CISC mean in 2020? by gpderetta on Saturday November 21, 2020 @09:43AM (#25169974)
I have little knowledge of 68k, but I understand that memory indirect addressing will deference its operand twice [1].

[1] https://en.wikibooks.org/wiki/68000_Assembly#Indirect_addres...

Re:What do RISC and CISC mean in 2020? by microtherion on Saturday November 21, 2020 @01:11PM (#25171449)
Ah yes, you & grandparent are right, I had forgotten about the existence of these modes.