News for hackers. Stuff that matters.
Re:Microsoft ports Windows 10, Linux to homegrown “E2” CPU d... by gmueckl on Tuesday June 19, 2018 @04:20PM (#17349990)
Compiler hints for data dependencies between groups of instructions sounds very much like the mistake that sank the Itanium. What is different this time around?
Re:Microsoft ports Windows 10, Linux to homegrown “E2” CPU d... by wmf on Tuesday June 19, 2018 @04:41PM (#17350150)
In VLIW like Itanium, the compiler had to determine not only instruction dependencies but it had to fully schedule when each instruction would execute, even though critical information like cache access time cannot be known by the compiler. In EDGE architectures the processor still does dynamic "out of order" instruction scheduling which gives much better performance.
Re:Microsoft ports Windows 10, Linux to homegrown “E2” CPU d... by dogma1138 on Tuesday June 19, 2018 @04:57PM (#17350240)
The iceberg that sunk the Itanic was the HP-Oracle-Intel deal.

HP was the only one who could sell them and Oracle put restrictions on how they could be used.

Wheb you have an ultra niche product that also happens to require a lot of ground work which is utterly incompatible with everything else on the market you aren’t likely to succeed.

If anything given the handicap that Itanium was playing with it can be considered an astonishing success.

Re:Microsoft ports Windows 10, Linux to homegrown “E2” CPU d... by slrz on Wednesday June 20, 2018 @01:18PM (#17357373)
Huh? Itaniums weren't available just from HP. At some point, basically everyone sold them, although HP is probably the only one left still selling systems based on it (Integrity/Superdome).
Re:Microsoft ports Windows 10, Linux to homegrown “E2” CPU d... by dogma1138 on Wednesday June 20, 2018 @03:06PM (#17358629)
Outside of “super-computers” all the other OEMs were limited to a low cpu/core count which made their offerings essentially mute.
Re:Microsoft ports Windows 10, Linux to homegrown “E2” CPU d... by PeCaN on Tuesday June 19, 2018 @04:34PM (#17350101)
That wasn't a mistake, and Itanium did just fine. Circa 2008 the fastest database servers in the world ran on Itanium.
Re:Microsoft ports Windows 10, Linux to homegrown “E2” CPU d... by pjmlp on Tuesday June 19, 2018 @05:16PM (#17350351)
Intel was just unlucky that AMD exists and came out with AMD64.

I believe if that wasn't the case, we would be using Itanium laptops nowadays.

Re:Microsoft ports Windows 10, Linux to homegrown “E2” CPU d... by scruffyherder on Tuesday June 19, 2018 @09:44PM (#17351800)
I don't think they would have ever made Itanium mobile, instead we'd be stuck with that PAE nonsense, and living in 32bit world, because 'general users don't need 64bits' ...
Re:Microsoft ports Windows 10, Linux to homegrown “E2” CPU d... by wmf on Tuesday June 19, 2018 @10:01PM (#17351928)
I think Intel wanted to eventually phase out x86 and push Itanium all the way down the stack, not for technical reasons but because it was a proprietary architecture that would never have competing implementations.
Re:Microsoft ports Windows 10, Linux to homegrown “E2” CPU d... by FullyFunctional on Thursday June 21, 2018 @02:59PM (#17368257)
You are think of Intel as having a single mind. The reality, and the reality of most large organizations, is that the ant hill is beaming with divergent and competing opinions. In particular, there were two powerful, competing camps: x86 and Itanium. The combined effect of Itanium performance not living up to promises [1] and AMD introducing a 64-bit x86 extension shifted the power balance, but it wasn't an inevitable outcome.

[1] The first iteration (I have one in the garage) was ~ 486 level fast and, sure, the final iterations were fast, but that took an AWFUL lot of silicon. The perf/transistor is terrible, even worse than x86 (which is bad).

Re:Microsoft ports Windows 10, Linux to homegrown “E2” CPU d... by protomyth on Tuesday June 19, 2018 @10:23PM (#17352060)
Maybe, but the Itanium came out during a time when the laptops were really becoming important and there was never an Itanium laptop. I look at the Itanium like I look at the G5 (970). It doomed itself by having no laptop possibilities.
Re:Microsoft ports Windows 10, Linux to homegrown “E2” CPU d... by beagle3 on Wednesday June 20, 2018 @02:08AM (#17352970)
It mostly doomed itself by being a backward incompatible mess. You couldn't run your existing software on it, it was expensive, and slow; being in a laptop would not have mitigated any of these.
Re:Microsoft ports Windows 10, Linux to homegrown “E2” CPU d... by slrz on Wednesday June 20, 2018 @01:32PM (#17357543)
Sure, you couldn't run your i386 machine code on it or at least not at competitive speed. But that is true for basically everything that isn't an x86.

That you can't run object code for one ISA on a totally different architecture is kind of the default state and you solve it by recompiling your code. It's why we have portable programming languages. No need to re-write your software except for some assembly routines in the OS and support libraries.

The Wintel dominance really fucked up the industry, badly.

Re:Microsoft ports Windows 10, Linux to homegrown “E2” CPU d... by protomyth on Wednesday June 20, 2018 @03:50PM (#17359083)
Some of its a self inflicted wound by chip makers. Skipping the Alpha because it was doomed by HP, it doesn't seem a lot of chip makers know how to put out a motherboard that can be bought by developers. MIPS theoretically had the Magnum boards, but even they were not generally available. Even today, getting a PC board for POWER or ARM is an adventure for your wallet.
Re:Microsoft ports Windows 10, Linux to homegrown “E2” CPU d... by protomyth on Wednesday June 20, 2018 @09:41AM (#17355220)
Remembering the history, they had pretty much everyone signed up (including Sun for some reason) to convert their software. They were expensive, and like most manufactures they didn't have a good on ramp for hobbyists and early developers. I think if they had noticed the trend to laptops, the rest would have followed.
Re:Microsoft ports Windows 10, Linux to homegrown “E2” CPU d... by beagle3 on Wednesday June 20, 2018 @10:31AM (#17355732)
Sun was in their blunder years at the time, also releasing x86 solaris and open sourcing it, so it's not surprising they signed up (I trust you when you say they did, I don't remember). HP signed up as part of the deal of killing their own processor division. Digital Alpha was somewhere between dying and dead/purchased by Intel. MIPS wasn't fairing very well already, especially with SGI committing slow long winded suicide by moving to Intel.

Obviously everyone is entitled to their opinion, but I don't find your argument convincing. ARM had a much better story even with early portables/laptops with Windows CE, and were a dismal failure -- just like the later Surface RT.

ARM had a power/battery-life advantage for laptops and support from Microsoft, and that didn't help; Switching to Itanium would not even have that. If Itanium found any general market success, it would have only been because of Intel's dominance. Luckily for us, that didn't happen.

Re:Microsoft ports Windows 10, Linux to homegrown “E2” CPU d... by protomyth on Wednesday June 20, 2018 @11:23AM (#17356250)
Sun: https://www.linuxtoday.com/developer/1999090200706PS

ARM has just as crappy a story except from the opposite way but not the performance or PC. They had power consumption but didn't duplicate their early PC support in the US. Palm and Windows CE handhelds did ok but go clobbered by the iPhone. ARM never had a big launch with multiple PC OS vendors. ARM also didn't have motherboards available in PC configuration for a lot of its lifetime. That's what made the Raspberry Pi so special since it was an actual motherboard available to people and not some dev / eval board. Now, we see ARM showing up in the server and PC market because the performance is there, smart phones have paid for the research, and ARM is customizable / multi-vendor.

If we had been lucky, IBM would have chosen the 68000.

Re:Microsoft ports Windows 10, Linux to homegrown “E2” CPU d... by beagle3 on Wednesday June 20, 2018 @03:42PM (#17359007)
> Palm and Windows CE handhelds did ok but go clobbered by the iPhone.

Palm and Windows CE were there since 1998, maybe even before. the iPhone came out in 2007. There were multiple ARM PDAs at the time (Compaq's iPaq, HP's Jornada, Palm's Pilot, many windows CE devices).

> If we had been lucky, IBM would have chosen the 68000.

Totally agree. The 68000 ISA is so elegant compared to the mess that is x86.

Re:Microsoft ports Windows 10, Linux to homegrown “E2” CPU d... by protomyth on Wednesday June 20, 2018 @04:00PM (#17359174)
The original Palms were Dragonball machines (68000) and CE actually ran pretty well on MIPS.

Palm and CE are 1996. Like I said, they did ok, but never sold in the volume that the iPhone and later Android achieved.

I dearly miss the 68000 and seriously sometimes wish the whole PowerPC thing didn't happen in favor of continued 68000. If the x86 proved anything its CISC / RISC wasn't exactly clear cut. The 88000 wasn't that bad except for a price that makes me think they were doing a bit of hallucinogens. I never got to play with ColdFire.

Re:Microsoft ports Windows 10, Linux to homegrown “E2” CPU d... by beagle3 on Thursday June 21, 2018 @02:24AM (#17362603)
Forgot about the Dragonball times ... Thanks.
Re:Microsoft ports Windows 10, Linux to homegrown “E2” CPU d... by _ph_ on Tuesday June 19, 2018 @05:00PM (#17350260)
Indeed, and it would be interesting to see how the most recent Itanium would perform if it would be ported to the current 14nm process instead of 32nm. While it once was considered to be a monster chip in transistor count , it no longer is.
Re:Microsoft ports Windows 10, Linux to homegrown “E2” CPU d... by cptskippy on Tuesday June 19, 2018 @07:50PM (#17351243)
Didn't Itanium suffer from the same issues as the Netburst architecture?
Re:Microsoft ports Windows 10, Linux to homegrown “E2” CPU d... by wmf on Tuesday June 19, 2018 @10:02PM (#17351934)
No, the issues were completely different. Itanium was pretty low-frequency.
Re:Microsoft ports Windows 10, Linux to homegrown “E2” CPU d... by Symmetry on Tuesday June 19, 2018 @06:56PM (#17350945)
Static scheduling plays badly with variable memory latencies and Itanium's speculative memory features just didn't work well enough. But it's instruction encoding was very inefficient and hurt a lot on workloads sensitive to i-cache pressure. If I understand EDGE correctly they don't try to statically schedule with respect to loads so this isn't a problem, they're just explicit about where the parallelism is.
Re:Microsoft ports Windows 10, Linux to homegrown “E2” CPU d... by usrusr on Tuesday June 19, 2018 @05:02PM (#17350270)
One thing that has changed: we routinely see hardware outliving software these days (e.g. Android phones that would still be perfectly adequate if software updates were available), this was hardly imaginable in the days of the "Itanic". Back then new hardware was typically bought to run old software faster.

Also, jit runtimes, once you have a hardware specific build of your browser (or of your server stack) you are 90% there.

Re:Microsoft ports Windows 10, Linux to homegrown “E2” CPU d... by twoodfin on Tuesday June 19, 2018 @04:42PM (#17350154)
I haven’t read the relevant papers, but I imagine they were targeting something that presented more like a fine-grained MIMD and less like VLIW. That is, many tiny cores with independent execution pipelines, not a few large cores with very wide paths of functional units.
Re:Microsoft ports Windows 10, Linux to homegrown “E2” CPU d... by SolarNet on Wednesday June 20, 2018 @03:22PM (#17358803)
It's right there in the announcement, all the compiler support is already there this time around.