4 ms·
Denver (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 comp
by gpderetta 7y ago
Denver (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]