3 ms·
> The reason they werent successful is because if a load misses the cache, you wait. Instead of superscalars which would have found other instructions to execut
by ajross 7y ago
> The reason they werent successful is because if a load misses the cache, you wait. Instead of superscalars which would have found other instructions to execute.
I'm not sure I quite buy that. In practice, what would happen is that a suitably large, optimized VLIW core would start fetching more than one wide instruction in a cycle and issuing the resulting ops in parallel with interlocks for dependencies, etc... Effectively, that is, VLIW would drop the explicit promise of the instruction set and turn into a speculative RISC core internally. And the cost for that translation would have been very comparable with what we see in all the existing very successful x86 CPUs.
But this never happened, because we never got that far. VLIW failed for other reasons. This particular problem had an obvious safety safety valve.
- gpderetta 7y agoDenver (and Crusoe before it) implements OoO behaviour on top of a VLIW core via dynamic translation. It performed fairly competitively, but in the end the complexity moved from one place to the other and was hardly worth it.
- CalChris 7y agoThe Denver team came from Transmeta but they didn't bring VLIW with them. Denver is a very wide (7+ wide) in-order superscalar pipeline. https://en.wikichip.org/wiki/nvidia/microarchitectures/denver https://en.wikichip.org/wiki/nvidia/microarchitectures/denve... I can't even understand how OOO VLIW would work.
- gpderetta 7y agoThe rumour I have heard is that Denver is indeed an VLIW machine (in order superscalar does not exclude that). It might be wrong of course. Regarding the OoO part, the dynamic scheduling is supposedly done by a JIT layer in firmware.
- CalChris 7y agoEverything I've read/heard is that it's superscalar. They've gone from 7 wide to 10 wide with Carmel. That's a lot of width to schedule and/or waste. The other big difference is that Denver uses a HW ARM decoder vs Transmeta's SW decoder. That was smart since they could license the IP from ARM whereas Intel would fight them every step of the way.
- gpderetta 7y agoIt seems that we had the same discussion 2 years ago on HN :). I can't find any authoritative source so I'll concede. The guys at RWT are pretty sure it is an VLIW though.
- deleted 7y ago[deleted]
- temac 7y ago> I'm not sure I quite buy that. In practice, what would happen is that a suitably large, optimized VLIW core would start fetching more than one wide instruction in a cycle and issuing the resulting ops in parallel with interlocks for dependencies, etc... Effectively, that is, VLIW would drop the explicit promise of the instruction set and turn into a speculative RISC core internally. Well at this point this would be quite insane to stay VLIW except for backward compat; but I suspect that the backward compat in question would have way more cost than e.g. the x86 tax. For example x86 is dense which is actually an advantage, but quite hard to decode (which is the main drawback of x86, but even then that's a quite relative drawback, because modern processes let us have complex decoders). What would VLIW have left for itself if internally turned into a classical modern speculative core? Maybe even load-time software translation would perform better...