3 ms·
What's intriguing to me is that Itanic was the "fetch" that Intel tried to make happen not once, not twice, but three times: once as iAPX 432, once as i860, and
by bitwize 3y ago
What's intriguing to me is that Itanic was the "fetch" that Intel tried to make happen not once, not twice, but three times: once as iAPX 432, once as i860, and once as Itanium. The whole idea of "pack multiple (often variable bit-length) instructions into a word and rely on compiler writers to determine optimal instruction packings" to make implementation simpler and therefore hopefully faster, but woe betide thee if thy compiler dost not find such optimal instruction packings; for then thy CPU will actually run code more slowly than a conventional design like x86! Someone very high up at Intel must've been very in love with this idea, as it was tried and flopped thrice throughout Intel's entire history as a major microprocessor vendor.
I didn't think AMD64 was a good idea at the time because it was more of the same. But good on Dave for helping eliminate the cruft that pretty much killed the RISC revolution.
- tedunangst 3y agoFunny in contrast to all the "I want the cpu to do what I tell it and nothing else" comments in every thread about speculative execution.
- philjohn 3y agoThinking about instruction packing and if this is something a JIT could have helped with, if we'd had state-of-the-art JIT's at the time.
- astrange 3y agoUnfortunately it can't work well because memory latency is so high and variable. It has been used in GPUs though.