qemu/tests/tcg/i386/x86.csv
Michael Tokarev bad5cfcd60 i386: spelling fixes
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
2023-09-20 07:54:34 +03:00

681 KiB

1# x86 instruction set description version 0.2x2018-05-08
2# of the fileso a reader can skip past the comments and hand the
3# 5. The validity of the instruction in 32-bit (aka compatibilitylegacy) mode.
4# distinguished only by operand sizelike most arithmetic instructions.
5# The instruction mnemonics are as used in the Intel manualwith a few exceptions.
6# Perhaps most significantlythe argument syntaxes used in the mnemonic indicate
7# exactly how to derive the argument from the instruction encodingor vice versa.
8# The encodings are also as used in the Intel manualwith automated corrections.
9# For examplethe manual lists many instruction forms using REX bytes
10# to use the instruction. If multiple flags are required
11# they are listed separated by plus signsas in PCLMULQDQ+AVX.
12# Insteadit is itself a comma-separated list of tags or hints derived by analysis
13# If two address tags are listedthe instruction can be used with either of those
14# If two operand tags are listedthe instruction can be used with either of those
15# For instructions with different possible data sizes
16# r/m encoding must specify a register or memoryrespectively.
17# Especially in newer instructionsthe modrm constraint may be the only way
18# instructions share the same encodingexcept that the former requires the
19# modrm byte's r/m to indicate a registerwhile the latter requires it to indicate memory.
20# the manual lists an instruction twiceonce with the optional 64-bit mode REX byte.
21# Since most decoders will handle the REX byte separatelythe form with the
22# As an exampleall instructions of SSE4a have such tag.
23# bscale4 and bscale8 have the same meaningbut are used
24# If instruction does not have bscaleX tagit does not support EVEX broadcasting.
The file is too large to be shown. View Raw