3 ms·
Are you talking about Very Long Instruction Words (VLIW)? IIRC, that's the concept of having the scheduling done in the compiler. Instead of the compiler spitti
by djsumdog 10y ago
Are you talking about Very Long Instruction Words (VLIW)? IIRC, that's the concept of having the scheduling done in the compiler. Instead of the compiler spitting out op codes and operands, each part of the instruction space controls specific functional units. So if you stick something in the adder, the documentation might specify the next x instructions need to be nops so it can complete.
The idea being if scheduling is done at compile time, you can update the compiler and update the scheduling/performance. Unfortunately, creating compilers for these systems was incredibly difficult, hence the failure of ix64/EPIC.
- wyldfire 10y agoQualcomm makes a VLIW DSP called "Hexagon" used in their SoCs [1]. It's a pretty popular chip used in lots of phones. [1] https://en.wikipedia.org/wiki/Qualcomm_Hexagon#Code_sample https://en.wikipedia.org/wiki/Qualcomm_Hexagon#Code_sample
- puzzlingcaptcha 10y agoThere also used to be the Transmeta processors which were x86 compatible and did the translation to VLIW in software (CMS - Code Morphing Software). I used to have a hp thin client with a Transmeta Efficeon where I installed Debian and it worked remarkably well for a 2004 processor, handily beating some Atoms and VIA Nanos in real-life workloads. Frankly I don't know what led to its demise.