4 ms·
1) The article says "thread level parallelism" when they mean "instruction level parallelism" 2) There is way more ILP available at run-time than compile time,
by aidenn0 16y ago
1) The article says "thread level parallelism" when they mean "instruction level parallelism"
2) There is way more ILP available at run-time than compile time, and what ILP is available in both is much more tractable at run-time. An out-of-order CPU is constantly filling a buffer with instructions (or microcode), and hardware is determining the dependencies dynamically to issue them to the ALU. This is a much more tractable problem than trying to guess the control flow at compile time. A large enough prefetch buffer can overcome a really dumb compiler.
3) Requiring software to be aware of details of your hardware implementation is a really tempting idea, but it has been historically much worse than the opposite. Consider a modern x86 that is nothing like an 80386, but runs the same software, often at higher IPCs than an original 386. Now compare to MIPS which has its delay-slot for branches which often just gets filled with a NOP. Furthermore on modern MIPS cores, which have longer pipelines and branch-prediction, that slot is more-or-less useless!
4) Assuming IA64 doesn't die out, by the time compiler writers figure out how to make code that runs fast on an Itanium of today, Intel will be performing hardware gymnastics to make that code run fast on the hardware of tomorrow.
- cx01 16y agoRegarding point 2, I wonder how much of a benefit Itanium would see from JIT-compiled languages, because the JIT could then dynamically arrange instructions to maximize ILP.
- sb 16y agoWhile I certainly think this would make for interesting research, I think the runtime-complexity of VLIW algorithms (such as Monica Lam's "Software Pipelining") would definitely interfere with the upper-bounds for compilation time of JIT compilers. (But, then again you could always use a background optimization thread...)
- sb 16y agoRegarding point 2: Last time I checked (IIRC 2006-ish), there seemed to be common resentiment among scientists working in the area of programming language implementation that there is just too little ILP for successful wide-spread VLIW adoption (modulo some special use cases.) AFAI(K|R), Hennesy and Patterson's cannonical text (CA-AQA [1]) reflects this: going from 3rd to 4th edition, we find a new chapter "Limits on ILP", VLIW/EPIC elements have been moved from the main contents to the CD-ROM, too (which probably is not a good indicator, though: the 3rd edition was just too heavy to carry it around a lot ;) [1]: http://www.amazon.com/Computer-Architecture-Quantitative-Approach-4th/dp/0123704901 http://www.amazon.com/Computer-Architecture-Quantitative-App...
- DarkShikari 16y agoThere is plenty of ILP for VLIW in many real-world cases -- but the most common case is that where all the instructions in the VLIW are identical. This of course reduces to SIMD, which makes the VLIW unnecessary.
- edge17 16y agoA large enough prefetch buffer can overcome a really dumb compiler. haha words for life