What is the compatible subset of Intel's and AMD's x86-64 implementations?
Asked Answered
C

1

8

While learning x86-64 assembly, I came across my first incompatibility between Intel 64 and AMD64 implementations of "x86-64": Why does syscall compile in NASM 32 bit output while popa does not compile in 64 bit? syscall is valid in the compatibility mode of one but not the other.

Is there a better way of finding out those incompatibilities besides carefully reading both manuals and comparing them, which is error prone and duplicates my manual reading effort when aiming for portability?

For example, it would be much easier if there was either:

  • a standard subset which both Intel and AMD claim to follow
  • comments on the Intel manual about AMD compatibility since AMD was the one to invent x86-64. But of course, this would be hard for Intel to maintain, and the Intel manuals don't contain the word AMD.
  • some general official or non-official guideline which assures compatibility of certain parts. For example, something like: compatibility mode may be incompatible, but 64-bit mode not.
  • some well maintained list of incompatibilities by Intel, AMD or some third party
Cognomen answered 23/4, 2015 at 20:43 Comment(2)
As always, Wikipedia is a good place to start!Parmenides
@Parmenides you are right, and I feel silly :-)Cognomen
P
9

History note: Intel implemented their 64-bit ISA, which they called IA-64 which was a complete replacement of the 32-bit x86 ISA, in their Itanium line of processors. IA-64 wasn't backward compatible with x86 and never really became popular outside the high-end server market.

AMD created the AMD64 ISA as an incremental evolution over the x86 ISA. AMD64 gained popularity and acceptance quickly and Intel adopted it as well, but called it IA-32e, EM64T and Intel64 at various times. Intel64 and AMD64 are nearly identical with a few differences.

Wikipedia lists these differences:

  • Intel 64's BSF and BSR instructions act differently than AMD64's when the source is zero and the operand size is 32 bits. The processor sets the zero flag and leaves the upper 32 bits of the destination undefined.

  • AMD64 requires a different microcode update format and control MSRs (model-specific registers) while Intel 64 implements microcode update unchanged from their 32-bit only processors.

  • Intel 64 lacks some MSRs that are considered architectural in AMD64. These include SYSCFG, TOP_MEM, and TOP_MEM2.

  • Intel 64 allows SYSCALL/SYSRET only in 64-bit mode (not in compatibility mode), and allows SYSENTER/SYSEXIT in both modes. AMD64 lacks SYSENTER/SYSEXIT in both sub-modes of long mode.

  • In 64-bit mode, near branches with the 66H (operand size override) prefix behave differently. Intel 64 ignores this prefix: the instruction has 32-bit sign extended offset, and instruction pointer is not truncated. AMD64 uses 16-bit offset field in the instruction, and clears the top 48 bits of instruction pointer.

  • AMD processors raise a floating point Invalid Exception when performing an FLD or FSTP of an 80-bit signalling NaN, while Intel processors do not.

  • Intel 64 lacks the ability to save and restore a reduced (and thus faster) version of the floating-point state (involving the FXSAVE and FXRSTOR instructions).

  • Recent AMD64 processors have reintroduced limited support for segmentation, via the Long Mode Segment Limit Enable (LMSLE) bit, to ease virtualization of 64-bit guests.

  • When returning to a non-canonical address using SYSRET, AMD64 processors execute the general protection fault handler in privilege level 3, while on Intel 64 processors it is executed in privilege level 0.

Parmenides answered 23/4, 2015 at 21:10 Comment(3)
You got your history backwards: IA64/Itanium (which is totally different from IA32/x86) predates AMD64. (Intel originally didn't intend x86 CPUs eating into their high-end highly-priced 64 bits server line).L
In practice Intel CPUs run bsf and bsr the same way AMD documents: by leaving the entire destination unmodified when the input=0. (Both document how ZF is set according to the input.) I think the author of that Wikipedia article misread the docs and didn't actually test on real CPUs. IIRC there's a discussion in comments somewhere on SO about that being an error in wikipedia.Dictatorial
I don't know why Intel doesn't document the destination register being unchanged; perhaps some ancient Intel CPUs really are different.Dictatorial

© 2022 - 2024 — McMap. All rights reserved.