←back to thread

331 points giuliomagnifico | 4 comments | | HN request time: 0s | source
Show context
bombcar ◴[] No.45377061[source]
Youngsters today don't remember it; x86 was fucking dead according to the press; it really wasn't until Athlon 64 came out (which gave a huge bump to Linux as it was one of the first OSes to fully support it - one of the reasons I went to Gentoo early on was to get that sweet 64 bit compilation!) that everyone started to admit the Itanium was a turd.

The key to the whole thing was that it was a great 32 bit processor; the 64 bit stuff was gravy for many, later.

Apple did something similar with its CPU changes - now three - they only swap when the old software runs better on the new chip even if emulated than it did on the old.

AMD64 was also well thought out; it wasn't just a simple "have two more bytes" slapped on 32 bit. Doubling the number of general purpose registers was noticeable - you took a performance hit going to 64 bit early on because all the memory addresses were wider, but the extra registers usually more than made up for it.

This is also where the NX bit entered.

replies(4): >>45377177 #>>45377584 #>>45377642 #>>45377870 #
drob518 ◴[] No.45377177[source]
Itanium wasn’t a turd. It was just not compatible with x86. And that was enough to sink it.
replies(10): >>45377228 #>>45377279 #>>45377290 #>>45377368 #>>45377474 #>>45377560 #>>45377649 #>>45378005 #>>45378555 #>>45379366 #
fooker ◴[] No.45377290[source]
>Itanium wasn’t a turd

It required immense multi-year efforts from compiler teams to get passable performance with Itanium. And passable wasn't good enough.

replies(2): >>45377427 #>>45377504 #
bombcar ◴[] No.45377427[source]
Wasn't the only compiler that produced code worth anything for Itanium the paid one from Intel? I seem to recall complaining about it on the GCC lists.
replies(2): >>45377736 #>>45378374 #
1. hawflakes ◴[] No.45377736[source]
I lost track of it but HP, as co-architects, had its own compiler team working on it. I think SGI also had efforts to target ia64 as well. But the EPIC (Explicitly Parallel Instruction Computing) didn't really catch on. VLIW would need recompilation on each new chip but EPIC promised it would still run.

https://en.wikipedia.org/wiki/Explicitly_parallel_instructio...

replies(2): >>45378119 #>>45380556 #
2. fooker ◴[] No.45378119[source]
In the compiler world, these HP compiler folks are leading compiler teams/orgs at ~all the tech companies now, while almost none of the Intel compiler people seem to be around.
replies(1): >>45384790 #
3. nextos ◴[] No.45380556[source]
Yes, SGI sold quite a lot of high-end IA-64 machines for HPCs, e.g. https://en.wikipedia.org/wiki/SGI_Altix
4. jabl ◴[] No.45384790[source]
Are you sure about that? If my memory serves, a lot of the Intel compiler people were transferred from HP? At least in the Fortran world, the Fortran frontend for the Intel compiler traces it's lineage back to DEC Fortran (for VAX and later Alpha) -> Compaq Visual Fortran (for Windows) -> Intel Fortran.