2 ms·
That's not the scalability the article is talking about. It's about instructions per cycle, and the fact that this gets pretty firmly capped by the bandwidth a
by ajross 7y ago
That's not the scalability the article is talking about. It's about instructions per cycle, and the fact that this gets pretty firmly capped by the bandwidth and latencies of the cache hierarchy, so even with ~6 parallel execution units it's pretty rare to be able to fill more than 2 of them in a cycle. And this is true, but it has absolutely nothing to do with instruction architecture.
The rest of the article is talking about how VLIW "solves" this problem, which is does not. Given an existing parallelizable problem, a VLIW architecture can encode the operations a little more efficiently, and the decode hardware required to interpret the instructions can be a lot simpler. But that's as far as it goes. If you have a classic CPU which can decode 4 instructions in a cycle, then it can decode 4 instructions in a cycle and VLIW isn't going to improve that except by reducing die area.
VLIW also forces compilers to make a choice between crazy specificity to specific hardware architectures, or an insanely complicated ISA with a batching scheme a-la Itanium. This is largely why it failed, not that "compilers weren't smart enough".
There's nothing wrong with RISC. Or classic CISC. Even VLIW isn't bad, really. The sad truth is that ISAs just don't matter. They're a tiny bit of die area and a few pipeline stages in much larger machines, and instruction decode is largely a solved problem.
Programmers just like to yell about ISA because that's what software touches, and we understand that part.
- gpderetta 7y agoAmen.