3 ms·
"there hasn't emerged a "parallel-by-default C++" kind of language + hardware system to exploit it" That's roughly what Intel tried with Itanium. I don't know
by tyingq 9y ago
"there hasn't emerged a "parallel-by-default C++" kind of language + hardware system to exploit it"
That's roughly what Intel tried with Itanium. I don't know if whatever barriers they hit are still barriers today.
- pjc50 9y agoNot really - Itanium tried to move the instruction-level parallelism and the burden of re-ordering execution to the compiler. You could only execute the maximum six instructions per cycle if there were no data dependencies. So it only really works for certain kinds of algorithmic data-heavy execution; that's why VLIW is only found in DSP architectures today. Good SE answer here: https://softwareengineering.stackexchange.com/questions/279334/why-was-the-itanium-processor-difficult-to-write-a-compiler-for https://softwareengineering.stackexchange.com/questions/2793... especially the ones focusing on cache misses.
- tyingq 9y ago"Itanium tried to move the instruction-level parallelism and the burden of re-ordering execution to the compiler" That sounds a lot like "parallel-by-default C++" kind of language + hardware system to exploit it" Just swapping "compiler" for language. They didn't succeed, but they did try Edit: helping me understand where I'm off might be more helpful than a downvote. Does swapping "compiler" for "language" not respresent what Intel was trying to do?