News for hackers. Stuff that matters.

javitron

Well, maybe she should try communicating science while NOT playing a video game. That may be the issue making it hard?
There is no "crisis in science" LOL. Talk about overblowing a few isolated data points trying to make them representative of whole fields.
That makes no sense. Alpha was horrible in terms of power consumption.
It is a great representation of the average article written about Itanium. I think the register made most of its revenue from articles about Itanium, where the authors had no clue about what they were talking about.

Not defending Itanium. But the average article on computer architecture has been garbage for decades now, it's fascinating.

The irony being that Itanium is basically a SPARC64 on steroids; both wide, both used huge register windows, and both were in order. the only difference being that Itanium exposed a lot of the superscalar bits to the programmer. I still have no clue why an HP shop would be using Solaris boxes, alas...
Alpha was on life support by the time Compaq bought DEC. AXP was literally one of the things that basically killed DEC.

By the time HP bought Compaq, AXP was on legacy mode. Plus Itanium was as much of an HP architecture as it was intel's, so it made no sense for HP to develop AXP further.

What killed Alpha and high performance MIPS (And eventually SPARC) was simple economics; their design costs grew faster than the revenue they generated.

I don't think many of the arm chair CPU experts really understand how expensive it is to design a high performance CPU core.

P4 was also, initially, process-driven.

The fab side of Intel had a huge priority in setting early architectural themes. And some of the CMOs flows in lab, in mid 90s, were showing huge speed scaling, but they had very restrictive design rules and cell libraries. But with the payout of extreme GHz scaling.

From that point of view, the P4 made sense; a narrow architecture with very deep pipelines. Where each stage used the tiny datapaths between latches/registers those libraries supported. Netburst makes sense in terms of dealing with extremely deep out of order pipelines.

However, those processes never met the scaling roadmaps. While the power consumption scaled horribly, and things like thermal, leakage and variability started to become first order limiters.

Intel has some of the best architecture and design teams in the industry.

They have had failed products, no doubt.

But I don't think you understand also how insanely good at execution Intel was during the 80s and 90s.

Itanium was being defined around the same time the 1st Alphas came to market. By the time Itanium2 came out, it matched/surpassed the contemporary AXP parts.

FWIW the alpha design teams ended up cannibalized between AMD and Intel. The original Opteron and the first generations of Core i have a ton of AXP DNA in them, from a uarch standpoint. So in a sense, Intel and AMD did continue Alpha... sort of.

However. I feel that Alpha gets over fetishized on the internet sometimes. It was a clean arch, mainly because it was a clean 64bit design from the get go. But as far as uArch, it was pretty generic. Most of the uArch themes the AXP design teams used, which a lot of people think were native inventions to Alpha, came straight from industry/academia research, and plenty of other processors implemented them as well.

The compilers worked just fine. Itanium was not even that particularly VLIWish, as the instruction carrier wasn't that particularly wide (up to 4 instructions)

All that Itanium was, at the end of the day, was an in-order PA-RISC/SPARC hybrid that exposed a lot of the superscalar innards to the programmer (compiler)

VLIW scheduling even back then wasn't as much of a mystery as the usenet and register flamewars implied. It really is pretty straightforward for a compiler to behave like an in-order superscalar scheduler. And since the compiler has a much global information about the instruction stream it can do much more optimizations and static ordering than a normal in-order HW superscalar scheduler alone.

Plus itanium had plenty of dynamic microarchitectural components to complement the static ordering done by the compiler and increase FU utilization.

If anything, things like predication and its adverse effect in power consumption had a much worse impact on itanium than the compilers.

What killed the itanium was just simple economics; its performance was fine (for the time, at least for itanium2). It's performance/price ratio, however, was not.

LOL I am always fascinated by the soap opera scripts some people come up when it comes to stuff like this. Y'all be so let down if you knew how boring and much more pragmatic/economics driven the real stories, behind how these sausages are made, really are.
Re:OpenVMS 9.2 for x86 is finally available for hobbyists on Tuesday April 11, 2023 @03:39PM (#35530354)
The file versioning in OpenVMS is really not that powerful. It also led to it's own set of issues, specially in terms of space waste.

Also VMS had their own issues when it came to it's filesystem(s).

Re:OpenVMS 9.2 for x86 is finally available for hobbyists on Tuesday April 11, 2023 @03:35PM (#35530291)
Yeah, and Unix originally ran on a PDP with 256KB of RAM. Alas...
Re:OpenVMS 9.2 for x86 is finally available for hobbyists on Tuesday April 11, 2023 @03:33PM (#35530251)
I don't think OpenVMS has run on VAX for a very long time.