6 ms·
Citing a paper from the mid 90s isn't a credible answer in 2016. All VLIW does is move a lot of on-chip logic off-chip into the compiler. This only works for a
by TheOtherHobbes 11y ago
Citing a paper from the mid 90s isn't a credible answer in 2016.
All VLIW does is move a lot of on-chip logic off-chip into the compiler. This only works for a small set of computing tasks - which is why the closest thing we have to VLIW today lives in GPUs. And why Itanium was nicknamed Itanic.
It's a non-starter for general computing because as soon as you start dealing with real-time conditions the compiler can't optimise in advance, the speed advantage turns into a speed penalty.
- deleted 11y ago[deleted]
- graycat 11y agoIIRC the 9:1 worked for the IBM 370 instruction set on general purpose code. Kemal was across the hall from me at Watson and explained it. Yes, the compiler is involved. So what?
- over 11y ago> Citing a paper from the mid 90s isn't a credible answer in 2016. I think it's unfair to generalize from VLIW to everything published 20+ years ago. Plenty of the things discovered back then, or earlier, are still applicable and in production today. Your compiler picked most of its low hanging fruit ages ago. Lots of PhD theses are rehashing old ideas, often unknowingly. Results are results, what matters more is whether there's a relevant context, as you've highlighted.
- graycat 11y ago> It's a non-starter for general computing because as soon as you start dealing with real-time conditions the compiler can't optimise in advance, the speed advantage turns into a speed penalty. "Real time"? What?