4 ms·
The huge disadvantages of Itanium's style of compile-time VLIW, as they were explained to me, were: 1. There is absolutely no flexibility in scheduling. Any EU
by duskwuff 9y ago
The huge disadvantages of Itanium's style of compile-time VLIW, as they were explained to me, were:
1. There is absolutely no flexibility in scheduling. Any EU stalls due to memory access delays, non-constant-time instructions, or the like delays completion of the entire instruction word. This makes cache misses disastrous.
2. If a newer CPU makes improvements to the architecture (say, adding new EUs), programs cannot take advantage of those improvements until compilers are updated to support those improvements, and the programs are rebuilt with the new compiler. This is unlike typical superscalar architectures, where a new EU will be used automatically with no changes needed to the program.
- deepnotderp 9y agoAs an overarching critique of VLIW, this isn't that bad, but it does ignore a few things: 1. It's not strictly true that there is "absolutely no flexibility in scheduling", there are a few techniques that can at least mitigate this issue, such as Itanium's advanced loads and a few others. On the aggregate though, the lack of MLP is absolutely what killed VLIW, especially nowadays. 2. This is true, but IBM's style (which the Mill has adopted) of "specialization" can effectively negate this issue.