3 ms·
Nah I think the Itanic concept is dead in the water VLIW works (especially in the way it was done in Itanium - IIRC) when either your workload is too predictab
by raverbashing 6y ago
Nah I think the Itanic concept is dead in the water
VLIW works (especially in the way it was done in Itanium - IIRC) when either your workload is too predictable or maybe if your compiler manages to be one order of magnitude smarter than it is today (even with llvm, etc)
It seems even M1 prefers to reorder scalar operations than work with SIMD ops in some cases (this is one of its processors)
- mhh__ 6y agoItanium is dead but VLIW as a concept is still interesting to me. If you look at uops executed per port benchmarks you can see that CPUs are far from all seeing eyes.
- hajile 6y agoAMD and Nvidia both used VLIW in the past and both moved away because they couldn't get it to run efficiently. If embarrassingly parallel problems can't execute efficiently on VLIW architectures, I somehow doubt that CPUs will either. The final versions of Itanic started adopting all the branch predictors and trappings from more traditional chips. The problem is that loops theoretically cannot be completely predicted at compile time (the halting problem). Modern OoO CPUs are basically hardware JITs that change execution paths and patterns on the fly based on previous behavior. This (at least at present) seems to get much better data resulting in much better real-world performance compared to what the compiler sees.
- garethrowlands 6y agoMill is claimed to run general purpose code well, unlike Itanic and VLIW in general. Are you claiming Mill would be like Itanium?