3 ms·
Itanium is essentially a VLIW architecture and... well, as the bottom of the page mentions, VLIW architectures tend to turn out to be bad ideas in practice. GP
by jcranmer 7y ago
Itanium is essentially a VLIW architecture and... well, as the bottom of the page mentions, VLIW architectures tend to turn out to be bad ideas in practice.
GPUs showed two things: one, you can relegate kernels to accelerators instead of having to maximize performance in the CPU core; and two, you can convince people to rewrite their code, if the gains are sufficiently compelling.
- cpr 7y agoSpecifically, the promise of VLIWs (scalar parallelism) was overhyped--the Multiflow compiler couldn't find enough scalar parallelism in practice to keep all 28 ALUs busy (in the widest model we built), or even all 7 ALUs (in the narrowest). (I ended up running the OS group at Multiflow before bailing right before they hit the wall.)
- zozbot234 7y agoWe need new programming models that make it easier to expose static parallelism to the compiler. Doing it all in plain old C/C++, or even in "managed" VM-based languages, cannot possibly work - and even conventional multi-threading is way too coarse-grained by comparison to what's most likely needed. Something based on a dataflow-oriented description of the code would probably work well, and be possible to integrate well enough with modern functional-like paradigms.
- pdimitar 7y agoI reached the same conclusion. We need a way to be able to explicitly say "this piece of code here is a standalone unit that is independent of everything else until we have to coalesce results of computation", or "this unit manages those other units and coalesces their results". Erlang's OTP captures this pretty okay-ish with their concept of processes (preemptively scheduled green threads that get aggressively multiplexed on all CPU cores) but I feel we can go a little bit further than that and have some sort of shorter markers in the code, say `actor { ... }` or `supervises(a1, a2, a3) { ... }` or something.
- Symmetry 7y agoVISC seems at least potentially promising. https://www.anandtech.com/show/10025/examining-soft-machines-architecture-visc-ipc/2 https://www.anandtech.com/show/10025/examining-soft-machines...
- cpr 7y agoYes, but VLIW's premise was that all that coordination that the VISC architecture is doing at runtime in hardware could be computed at compile-time in software.
- Symmetry 7y agoNot in general, VLIWs work great in DSP architectures like the Hexagon. They tend to fall down in the presence of unpredictable memory accesses, though, and while Itanium had facilities to try to mitigate that they didn't work well enough.
- dfox 7y agoI think that another issue with VLIW as a general purpose ISA is that for it to be worthwhile the compiler has to have deep understanding of the underlying implementation (deep enough to always generate hazard-free code) such that the CPU does not have to contain any scheduling logic. This is the case for most embedded/DSP VLIW architectures. The issue with that is that there cannot reasonably be any kind of backward compatibility on the machine code level.