Hacker News Reader

I think both are pretty common. E.g. uname -a says x86_64 and GCC/Clang use x86-64 for defining the target while, on the other hand, MSVC (and a lot of Microsoft stuff in general) uses amd64 as do many BSDs.

> MSVC (and a lot of Microsoft stuff in general) uses amd64 as do many BSDs.

That's partly because Microsoft had support for ia32 (x86) and ia64 (Itanium). So amd64 was to differentiate the architecture (and it was unclear Intel would ever extend x86).

Debian-based systems are slightly confused with dpkg architecture returning amd64 and uname returning x86_64.

Compiler explorer (godbolt.org) uses x86-64, as do the man pages for gcc and clang. I suspect there are plenty of other places too.

I remember it a fair bit right after 64 bit became mainstream. In the excitement phase it was generally amd64 then as it became fully established and adopted it was most often referred to as x86-64, at least in the press.

But my filesystem is full of references like /usr/lib/x86_64-linux-gnu

It makes it clearly different from arm64 at least, which may be part of it.