2 ms·
The VLIW article sounds like VLIW is great. If so, the problem was not with VLIW, but with the fact that switching over to a complete new architecture is hard,
by cubefox 4y ago
The VLIW article sounds like VLIW is great. If so, the problem was not with VLIW, but
with the fact that switching over to a complete new architecture is hard, and basically impossible when AMD at the same time creates pressure on the legacy front.
- zozbot234 4y agoVLIW has some annoying issues. The Mill proposed architecture is basically a tweak on VLIW, adding a number of features to make it easier to write software for and a variant of runtime scheduling that's quite simplified compared to OOO.
- Qem 4y agoAny links to this Mill proposal?
- zozbot234 4y agoJust google around. The basic idea dates as far back as Charles Babbage's work in the 19th century.
- znpy 4y agoMill computing? Did they ever ship anything? They pop up from time to time, i haven't heard their company name in a while, i wonder what they're up to as of today.
- flohofwoe 4y agoThe problem with VLIW was that it isn't a good fit for "general software" which has trouble to fill that many execution lanes with meaningful work. You can't just take existing source code like MS Word or Excel, compile it to a VLIW CPU, and expect it to do better than a traditional CISC or RISC design. It only works well for code written to solve specific "massively parallel" problems.