News for hackers. Stuff that matters.
Re:RISC vs. CISC by John R. Mashey (1995) by Symmetry on Sunday May 19, 2024 @09:37AM (#40406881)
The end result seems to be that the two entries from that old post that have seen the most success, x86 and ARM, are essentially the RISCiest of the CISCs and the CISCiest of the RISCs. A happy medium.
Re:RISC vs. CISC by John R. Mashey (1995) by hmry on Sunday May 19, 2024 @11:57AM (#40407740)
Intel's new x86 extension (APX) is adding 16 more registers and three-register instructions. RISCification is still in progress.
Re:RISC vs. CISC by John R. Mashey (1995) by sapiogram on Sunday May 19, 2024 @03:08PM (#40409049)
What's RISC about adding more registers?
Re:RISC vs. CISC by John R. Mashey (1995) by ajross on Sunday May 19, 2024 @03:26PM (#40409165)
The simple answer is that a big symmetric register set has always been a hallmark of RISC ISAs, because having lots of symmetric registers increases throughput by reducing compiler-generated spill/fill overhead and permits more permissive ABIs for leaf functions that need the extra space.

The complicated answer is that, no, it's not especially "reduced" and you could implement all those other RISCy ideas in a much smaller set of GPRs without otherwise effecting the "RISCiness" of the design. But that answer is a little specious, since it's true of all the other RISCy traits too. Most of them stand alone, which is why the whole debate tends to be a little silly.

Re:RISC vs. CISC by John R. Mashey (1995) by Symmetry on Monday May 20, 2024 @06:29AM (#40414020)
The name "RISC" is something we gave to a particular design philosophy, but not everything in that philosophy is summed up in the name. Classic RISC designs have 32 registers to make up for the lack of instructions that operate directly on memory addresses and to make things easier for the compiler and achieve good performance without load-op-store instructions.
Re:RISC vs. CISC by John R. Mashey (1995) by fanf2 on Sunday May 19, 2024 @09:38AM (#40406891)
The runner-up CISC, IBM z / 370, is also fairly RISCy.
Re:RISC vs. CISC by John R. Mashey (1995) by pclmulqdq on Sunday May 19, 2024 @06:25PM (#40410205)
The runner-up RISC, IBM's POWER, is arguably more CISC-y than ARM.
Re:RISC vs. CISC by John R. Mashey (1995) by brucehoult on Sunday May 19, 2024 @09:36PM (#40411228)
I can't agree with that -- POWER has slightly simpler addressing modes, in that `lwu` etc are always and only pre-increment/decrement, and doesn't have load/store multiple (the most CISCy thing in arm32) at all. And also, obviously, not predication, either per-instruction or with anything like `IT*`.
Re:RISC vs. CISC by John R. Mashey (1995) by pclmulqdq on Sunday May 19, 2024 @09:53PM (#40411350)
ARM64 gets a lot closer to CISC than ARM32, honestly (aside from the "everything predicated" and "double word stores"), with a larger suite of weirder instructions. Predication is also a distinct feature of ARM instructions, not a generic CISC thing.

POWER has instructions like RLIMI, DOZ, and STHBRX on the "complex" side.

The RISC/CISC distinction is not just about addressing and accessing memory (register-register vs register-memory operations). The headline operations for x86 actually were more about the compute side rather than the memory side - things like the "AAD" instruction did a lot of computing work in one bite. There were also RISC register-memory machines at the time the distinction was meaningful.

Re:RISC vs. CISC by John R. Mashey (1995) by brucehoult on Monday May 20, 2024 @07:29AM (#40414340)
> ARM64 gets a lot closer to CISC than ARM32

No way. Quite the opposite. ARM64 is quite similar to e.g. RISC-V in most respects other than the use of condition codes.

> POWER has instructions like RLIMI, DOZ, and STHBRX on the "complex" side.

There is nothing complex or "un-RISC" about any of those.

RLIMI is similar to Arm32 BFI or Arm64 UBFM.

DOZ is just subtract with the output zeroed if the MSB is 1. It is easily implemented with just a handful of straight-line instructions in any ISA with min/max or slt or for that matter asr i.e. in hardware with a simple combinatorial add-on to standard subtraction.

STHBRX is just a little-endian store (on big-endian POWER). Plenty of other RISC ISAs (whether big-endian or little-endian) have that.

> things like the "AAD" instruction did a lot of computing work in one bite

Less than other ISAs with a one-shot decimal add instruction (or mode e.g. 6502). Once again, it's a very simple combinatorial circuit -- no CISCy microcode or control flow needed.

> There were also RISC register-memory machines at the time the distinction was meaningful.

Name one.

Re:RISC vs. CISC by John R. Mashey (1995) by RetroTechie on Monday May 20, 2024 @12:39PM (#40417285)
As the article explains:

"General comment: this may sound weird, but in the long term, it might be easier to deal with a really complicated bunch of instruction formats, than with a complex set of addressing modes, because at least the former is more amenable to pre-decoding into a cache of decoded instructions that can be pipelined reasonably, whereas the pipeline on the latter can get very tricky (examples to follow)."

So the distinction is more about how 'easy' an ISA lends itself to pipelining (critical paths, dependencies between instructions/operands & so on), than about how rich the instruction set is or how much work 1 instruction may do.

Re:RISC vs. CISC by John R. Mashey (1995) by snvzz on Sunday May 19, 2024 @07:49PM (#40410635)
>the RISCiest of the CISCs and the CISCiest of the RISCs. A happy medium.

Until RISC-V enters the conversation.

Re:RISC vs. CISC by John R. Mashey (1995) by thechao on Monday May 20, 2024 @08:26AM (#40414714)
If you actually dig into the details of RISC-V — especially the variable width extensions, it scratches all of my CISC-y itches just fine. Is it as CISC-y as ARM or x86? Not yet; not yet.