4 ms·
VLIW is what the Unison project (the context behind this post) was attacking. https://unison-code.github.io/ https://unison-code.github.io/ My best understandin
by philzook 3y ago
VLIW is what the Unison project (the context behind this post) was attacking. https://unison-code.github.io/ https://unison-code.github.io/ My best understanding is that exposing the details of the CPU to the compiler via a more complex ISA has not worked that well. Possibly because the compilation problem just gets too hard, but maybe also for momeentum and ecosystem reasons. I think another lesson is that it is unwise to make your isa expose microarchitecture because microarchitecture changes quite a bit between generations and inidividual CPUs. Things like delay slots seem like misfeatures now.
- gsnedders 3y agoAnd it's worth noting VLIW survived longer in GPUs—where there isn't any expectation of ISA stability, which avoids that problem.
- remexre 3y agoAnd, perhaps also relevantly, your compute kernel probably fits in iCache, even with VLIW instructions.
- LoganDark 3y agoNot to be confused with the Unison language, I guess. https://www.unison-lang.org https://www.unison-lang.org