Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

No, VLIW is even worse than this. Describing it as a compiler problem undersells the issue. VLIW is not tractable for a multitasking / multi tenant system due to cache residency issues. The compiler cannot efficiently schedule instructions without knowing what is in cache. But, it can’t know what’s going to be in cache if it doesn’t know what’s occupying the adjacent task time slices. Add virtualization and it’s a disaster.


It only works for fixed workloads, like accelerators, with no dynamic sharing.


Yeah, VLIW is still used for stuff like DSP and GPUs, but it doesn't make sense for general computing.


GPUs have long since moved away from VLIW as well


They are still mostly statically scheduled which I think it is the point the parent is making.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: