[flagged]
For example, what their training manual calls "third-order conflicts" are called WAR (write-after-read) hazards today. "first-order conflicts" mean either a functional unit is busy or a RAW hazard.
I hope people in the future will not default to assuming everything is AI generated, and instead do due diligence by looking at the sources and what's written. I took a lot of care to understand the original docs and reframe it in modern terms, even though it's an April Fools joke.
But if no one cares maybe I should try using AI to generate stuff sometime.
If describing how an architecture works is "brochure voice" then I guess pretty much any technical deep dive is. Not sure how to avoid that.
Serious question now, would a company's brochure call out that their functional units are not pipelined? Because none of their original documentation did.