4 ms·
Without going through various repos, I'm struggling to recall ever even seeing "x86-64" - It's always amd64 that I look for - so the rebrand wasn't that success
by ghshephard 3y ago
Without going through various repos, I'm struggling to recall ever even seeing "x86-64" - It's always amd64 that I look for - so the rebrand wasn't that successful.
- milsorgen 3y agoI 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.
- zamadatix 3y agoI 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.
- 908B64B197 3y ago> 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).
- viraptor 3y agoDebian-based systems are slightly confused with dpkg architecture returning amd64 and uname returning x86_64.
- usefulcat 3y agoCompiler explorer (godbolt.org) uses x86-64, as do the man pages for gcc and clang. I suspect there are plenty of other places too.
- m463 3y agoBut my filesystem is full of references like /usr/lib/x86_64-linux-gnu
- bombcar 3y agoIt makes it clearly different from arm64 at least, which may be part of it.