2 ms·
> I thought this was sarcasm, but the tone continues throughout the article. It was sarcasm, but the tone continued because I think Itanium was an enormous was
by kstrauser 5y ago
> I thought this was sarcasm, but the tone continues throughout the article.
It was sarcasm, but the tone continued because I think Itanium was an enormous waste of time and other resources.
> The ISA was brilliant.
I completely disagree. The ISA depended on enormous leaps in compiler technology in order to make it useful. However pretty it may have been, it couldn't be implemented in a performant way. It'd take ugly-but-practical over pretty-but-impossible any day of the week, especially when I get to use languages that abstract the ugliness away from me.
- SavantIdiot 5y agoI think that statement suffers from hindsight bias: x86 is great now because of enormous leaps in compiler technology to work. Yes, compilers do need to evolve with CPUs, they don't just grow on trees! Put another way: given a choice between stuffing an electric engine in a Ford Fiesta, and a Tesla, Itanium could have been the Tesla in the hands of another company, but the market went after the Fiesta retrofit because it was here-and-now, not coming-soon. EDIT: changed from "you" to "that statement"; added analogy.
- kstrauser 5y agoI don't believe that's historically accurate at all. x86 compiler performance has been good enough for a long, long time. Yes, newer versions are clearly a lot better than ones from the mid 90s, but the performance improvements would be described in terms of percentages, not orders of magnitude. IA-64 required a complete rethinking of compiler design to solve NP-hard problems on a large scale just to get passable performance. Translating C to ASM that keeps execution units busy is radically different on IA-64 than pretty much anything else.
- SavantIdiot 5y ago> x86 compiler performance has been good enough for a long, long time. > NP-hard problems on a large scale just to get passable performance. First, it is hard to refute a claim, or find meaning in it, when you start using terms like "passable" and "good enough". Second, I think this overstates the need for optimal scheduling because Itanium SPEC performance was "passable" out of the gate.