But Intel 64, amd64, x86_64, x86, all work because none are ambiguous or misleading. "IA-32e" would be confusing, but at least it refers to a specific Intel marketing term that one can look up. They're specific enough to avoid ambiguity.
(to be fair, "Intel 64" could refer to Itanic, so that's not as unambiguous as it could be, but without context, it's reasonable most would assume it refers to 64 bit x86)
No, it cannot. It refers exactly to AMD64 (not "amd64", it's a GCC's marketing name) and Intel 64 (and their previous revisions) and nothing else. See, I too can omit middle terms in a logical sequence and simply assert the conclusion (You've omitted something like "and if the name can denote two things it may as well denote any number of things with vaguely similar alternative names" which is obviously ridiculous).
> "Intel 64" could refer to Itanic
By your own logic it could not. "Itanium" is a marketing name, the architecture's actual name was "IA-64".
The things have names that people put on them. If people refer to AMD64 as "x64", then "x64" is a name of that thing, literally. Whether it's correct or not is a matter of convention and popularity, and your proposed convention is quite unpopular, I'd say.
I think your reaction is an excellent example of a significant problem with discourse on the Internet.
Correct terms matter. Using incorrect terminology just because it's common is no excuse.
Being pedantic about things isn't helpful, either, but which is worse: a teacher in a specific field using terms incorrectly, and therefore passing along that incorrect usage, or someone pointing that out?
So let's reexamine: is this "one of the most stark examples of bikeshedding", or is this the Internet showing its lack of tolerance for a genuine care for facts and correctness?