Extensions
Forms
17 (8 VEX, 9 EVEX)
Data
Intel XED v2026.08.23

VMOVAPS is MOVAPS in VEX and EVEX encodings: a copy of packed singles, bits not interpreted, between vector registers or between a register and aligned memory. The MOVAPS page covers its use for any kind of data and its two register encodings. What changes:

  • Alignment grows with the width. A memory operand must be aligned to 16 bytes for xmm, 32 for ymm and 64 for zmm, or the instruction raises #GP. A write mask does not relax this: Intel’s table of exception class E1 lists the alignment fault without the condition that exempts masked-out elements from other memory faults.
  • Clearing above the width. MOVAPS leaves bits 128 and up of its destination register alone; VEX and EVEX forms clear them above their own width. On Zen 5, vmovaps xmm12, xmm6 left bits 128 to 511 of ZMM12 zero.
  • Masks and more registers. EVEX (AVX512F, or AVX10.1) adds a write mask per single, merging or zeroing on loads, and the registers 16 to 31. VMOVAPD, VMOVDQA32 and VMOVDQA64 mask doubles, doublewords and quadwords instead.

In compiled code

At -O2 with -march=x86-64-v3 or -v4, GCC 14 and Clang 23 copy vector registers of floats with VMOVAPS, and Clang copies integer vectors with it too, where GCC uses VMOVDQA or VMOVDQA64. Both emit it for _mm256_load_ps and _mm256_store_ps, and Clang also for _mm256_load_si256 and the 512-bit _mm512_load_si512. A masked _mm512_maskz_load_ps becomes vmovaps zmm0{k1}{z}, [rdi] in both.

For data whose alignment they cannot see, compilers use VMOVUPS instead, and AMD’s Zen 5 guide says the two perform the same on aligned data (Section 2.6.2): what VMOVAPS adds is the check, which turns a misaligned pointer into a fault rather than a slower access.

Zen 5’s 17 recorded cases cover every form, the masked loads and stores included, all at an aligned address.

In the optimization guide

What the optimization guide says about VMOVAPS, a line per claim. Each links to the claim in the guide, with its sources and where they differ.

Out of order

  • Move elimination: A register-to-register copy can be made at renaming, by pointing the destination at the physical register of the source; the move then has no latency and uses no execution unit.

Forms

Every encoding of VMOVAPS that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VMOVAPS xmm, m128 VMOVAPS_XMMdq_MEMdqVEX.128.NP.0F.WIG 28 /rAVX
VMOVAPS xmm, xmm VMOVAPS_XMMdq_XMMdq_28VEX.128.NP.0F.WIG 28 /rAVX
VMOVAPS m128, xmm VMOVAPS_MEMdq_XMMdqVEX.128.NP.0F.WIG 29 /rAVX
VMOVAPS xmm, xmm VMOVAPS_XMMdq_XMMdq_29VEX.128.NP.0F.WIG 29 /rAVX
VMOVAPS ymm, m256 VMOVAPS_YMMqq_MEMqqVEX.256.NP.0F.WIG 28 /rAVX
VMOVAPS ymm, ymm VMOVAPS_YMMqq_YMMqq_28VEX.256.NP.0F.WIG 28 /rAVX
VMOVAPS m256, ymm VMOVAPS_MEMqq_YMMqqVEX.256.NP.0F.WIG 29 /rAVX
VMOVAPS ymm, ymm VMOVAPS_YMMqq_YMMqq_29VEX.256.NP.0F.WIG 29 /rAVX
VMOVAPS zmm {k}{z}, zmm VMOVAPS_ZMMf32_MASKmskw_ZMMf32_AVX512EVEX.512.NP.0F.W0 28 /r
EVEX.512.NP.0F.W0 29 /r
AVX10.1 or AVX512F
VMOVAPS zmm {k}{z}, m512 VMOVAPS_ZMMf32_MASKmskw_MEMf32_AVX512EVEX.512.NP.0F.W0 28 /rAVX10.1 or AVX512F
VMOVAPS m512 {k}, zmm VMOVAPS_MEMf32_MASKmskw_ZMMf32_AVX512EVEX.512.NP.0F.W0 29 /rAVX10.1 or AVX512F
VMOVAPS xmm {k}{z}, xmm VMOVAPS_XMMf32_MASKmskw_XMMf32_AVX512EVEX.128.NP.0F.W0 28 /r
EVEX.128.NP.0F.W0 29 /r
AVX10.1 or AVX512F + AVX512VL
VMOVAPS xmm {k}{z}, m128 VMOVAPS_XMMf32_MASKmskw_MEMf32_AVX512EVEX.128.NP.0F.W0 28 /rAVX10.1 or AVX512F + AVX512VL
VMOVAPS m128 {k}, xmm VMOVAPS_MEMf32_MASKmskw_XMMf32_AVX512EVEX.128.NP.0F.W0 29 /rAVX10.1 or AVX512F + AVX512VL
VMOVAPS ymm {k}{z}, ymm VMOVAPS_YMMf32_MASKmskw_YMMf32_AVX512EVEX.256.NP.0F.W0 28 /r
EVEX.256.NP.0F.W0 29 /r
AVX10.1 or AVX512F + AVX512VL
VMOVAPS ymm {k}{z}, m256 VMOVAPS_YMMf32_MASKmskw_MEMf32_AVX512EVEX.256.NP.0F.W0 28 /rAVX10.1 or AVX512F + AVX512VL
VMOVAPS m256 {k}, ymm VMOVAPS_MEMf32_MASKmskw_YMMf32_AVX512EVEX.256.NP.0F.W0 29 /rAVX10.1 or AVX512F + AVX512VL

Latency and throughput

What the scheduling models of LLVM 23.1.2 give for each form, not measurements: latency / reciprocal throughput in cycles, the ports under them. A row is a model, or models that agree; a dash, a form that its processors lack. Memory forms: latency from the address, ports without the load and store units. Which processors each model covers.
Modelxmm, m128xmm, xmm
xmm {k}{z}, xmmno mask
ymm {k}{z}, ymmno mask
m128, xmm
m512 {k}, zmm
m128 {k}, xmm
m256 {k}, ymm
ymm, m256ymm, ymmm256, ymmzmm {k}{z}, zmmno maskzmm {k}{z}, zmmwith a mask, zeroingzmm {k}{z}, m512no mask
ymm {k}{z}, m256no mask
zmm {k}{z}, m512with a mask, zeroingxmm {k}{z}, xmmwith a mask, zeroing
ymm {k}{z}, ymmwith a mask, zeroing
xmm {k}{z}, m128no maskxmm {k}{z}, m128with a mask, zeroingymm {k}{z}, m256with a mask, zeroing
Sandy Bridge6 / 0.5p231 / 1p51 / 1p4 p237 / 0.5p231 / 1p51 / 1p4 p23
Haswell6 / 0.5p231 / 1p51 / 1p23477 / 0.5p231 / 1p51 / 1p2347
Broadwell5 / 0.5p231 / 1p51 / 1p23476 / 0.5p231 / 1p51 / 1p2347
Skylake6 / 0.5p231 / 0.33p0151 / 1p23477 / 0.5p231 / 0.33p0151 / 1p2347
Skylake-SP6 / 0.5p231 / 0.33p0151 / 1p23477 / 0.5p231 / 0.33p0151 / 1p23471 / 0.5p051 / 0.5p058 / 0.5p0158 / 0.5p0151 / 0.33p0157 / 0.5p0157 / 0.5p0158 / 0.5p015
Ice Lake6 / 0.5p231 / 0.33p0151 / 0.5p47897 / 0.5p231 / 0.33p0151 / 0.5p47891 / 0.5p051 / 0.5p058 / 0.5p0158 / 0.5p0151 / 0.33p0157 / 0.5p0157 / 0.5p0158 / 0.5p015
Alder Lake7 / 0.33p2 p3 p101 / 012 / 0.5p47898 / 0.33p2 p3 p101 / 012 / 0.5p4789
Sapphire Rapids7 / 0.33p2 p3 p101 / 012 / 0.5p47898 / 0.33p2 p3 p101 / 012 / 0.5p47891 / 01 / 0.5p058 / 0.33p2 p3 p109 / 0.5p051 / 0.33p0157 / 0.33p2 p3 p108 / 0.33p0159 / 0.33p015
Lunar Lake7 / 2p20 p21 p221 / 012 / 0.5p10 p11 p25 p26 p278 / 2.33p20 p21 p221 / 012 / 0.5p10 p11 p25 p26 p27
Piledriver5 / 1.5FPFMA FPU0 FPU11 / 1FPFMA FPU0 FPU11 / 1.5AGLU01 FPSTO FPU2 FPU3 Store5 / 1.5FPFMA FPU0 FPU12 / 1FPFMA FPU0 FPU11 / 18AGLU01 FPSTO FPU2 FPU3 Store
Zen8 / 0.5AGU0 AGU11 / 0.25FPU0 FPU1 FPU2 FPU31 / 0.5AGU0 AGU18 / 0.5AGU0 AGU11 / 0.25FPU0 FPU1 FPU2 FPU31 / 0.5AGU0 AGU1
Zen 28 / 0.33AGU0 AGU1 AGU21 / 0.25FPU0 FPU1 FPU2 FPU31 / 0.33AGU0 AGU1 AGU28 / 0.33AGU0 AGU1 AGU21 / 0.25FPU0 FPU1 FPU2 FPU31 / 0.33AGU0 AGU1 AGU2
Zen 38 / 0.5FP45 LSU Load0 / 0.171 / 1FP45 FPSt LSU Store8 / 0.5FP45 LSU Load0 / 0.171 / 1FP45 FPSt LSU Store
Zen 48 / 0.5FP45 LSU Load0 / 0.171 / 1FP45 FPSt LSU Store8 / 0.5FP45 LSU Load0 / 0.171 / 1FP45 FPSt LSU Store0 / 0.170 / 0.178 / 0.5FP45 LSU Load8 / 0.5FP45 LSU Load0 / 0.178 / 0.5FP45 LSU Load8 / 0.5FP45 LSU Load8 / 0.5FP45 LSU Load
Jaguar5 / 1LAGU1 / 0.5FPA FPM FPU0 FPU11 / 1FPU15 / 2LAGU1 / 1FPA FPM FPU0 FPU11 / 2FPU1

Data flow

Where the elements of the sources go, element 0 on the right; results that depend on a control value are drawn for an example. How to read.

A masked move: each single is copied where its bit of k1 is 1; elsewhere merging keeps the old element, and zeroing writes 0.VMOVAPS xmm, xmm/m128 VMOVAPS ymm, ymm/m256 VMOVAPS xmm {k}{z}, xmm/m128 VMOVAPS ymm {k}{z}, ymm/m256 VMOVAPS zmm {k}{z}, zmm/m512

merging, {k1}

VMOVAPS with merging, {k1}With merging: result singles 3 to 0: a3, unchanged, a1, a0.0123xmm2or m128a1110k1a0a1a3xmm1

zeroing, {k1}{z}

VMOVAPS with zeroing, {k1}{z}With zeroing: result singles 3 to 0: a3, 0, a1, a0.0

Example mask k1 = 0x0B. Every single works alike: 4, 8 and 16 singles in the xmm, ymm and zmm forms.

With merging: result singles 3 to 0: a3, unchanged, a1, a0.

With zeroing: result singles 3 to 0: a3, 0, a1, a0.

A masked store: each single is copied where its bit of k1 is 1; elsewhere the memory is left as it was.VMOVAPS m128, xmm VMOVAPS m256, ymm VMOVAPS m128 {k}, xmm VMOVAPS m256 {k}, ymm VMOVAPS m512 {k}, zmm
VMOVAPS with merging, {k1}Memory singles 3 to 0: a3, unchanged, a1, a0.xmm2am128

Example mask k1 = 0x0B. Every single works alike: 4, 8 and 16 singles in the xmm, ymm and zmm forms.

Memory singles 3 to 0: a3, unchanged, a1, a0.

Operation

What the forms do, in pseudocode that our tests run against results recorded on real processors. How to read.

VMOVAPS xmm, xmm/m128 VMOVAPS ymm, ymm/m256 VMOVAPS xmm {k}{z}, xmm/m128 VMOVAPS ymm {k}{z}, ymm/m256 VMOVAPS zmm {k}{z}, zmm/m512
for i in range(VL // 32):
    if k1[i]:  # 1 without a write mask
        zmm1.d[i] = src2.d[i]
    elif zeroing:
        zmm1.d[i] = 0
    # else: zmm1.d[i] keeps its value
# zmm1 is zeroed from bit VL up

Run on AMD Zen 5 (EPYC 9645): 12 cases.

VMOVAPS m128, xmm VMOVAPS m256, ymm VMOVAPS m128 {k}, xmm VMOVAPS m256 {k}, ymm VMOVAPS m512 {k}, zmm
for i in range(VL // 32):
    if k1[i]:  # 1 without a write mask
        mem.d[i] = zmm2.d[i]
    # else: mem.d[i] is not written

Run on AMD Zen 5 (EPYC 9645): 5 cases.

Operands

What each form reads and writes, as Intel XED records it: the operands of its syntax, in order, and the implicit ones that the syntax does not name. How to read.
OperandKindAction
VMOVAPS xmm, xmm/m128 VMOVAPS ymm, ymm/m256
xmm, ymmexplicitwrite
xmm/m128, ymm/m256explicitread
VMOVAPS xmm/m128, xmm VMOVAPS ymm/m256, ymm
xmm/m128, ymm/m256explicitwrite
xmm, ymmexplicitread
VMOVAPS xmm {k}{z}, xmm/m128 VMOVAPS ymm {k}{z}, ymm/m256 VMOVAPS zmm {k}{z}, zmm/m512
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm/m128, ymm/m256, zmm/m512explicitread
VMOVAPS m128 {k}, xmm VMOVAPS m256 {k}, ymm VMOVAPS m512 {k}, zmm
m128/256/512explicitwrite (masked)
{k}explicitread (write mask)
xmm, ymm, zmmexplicitread

Flags

None: XED records no flag that the forms test or change.

Exceptions

The exception class is XED's name for the set of exception conditions that a form follows. How to read.

VEX forms
avx-type-1
EVEX forms
AVX512-E1

Attributes

What else XED records about the forms. How to read.

Memory forms
aligned memory operand
EVEX forms
write masking
EVEX memory forms
memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VMOVAPS, each with the form it compiles to and the Clang options it needs. The forms come from compiling every intrinsic and decoding the result with Intel XED; all intrinsics A–Z explains the method.

IntrinsicCompiles to
_mm_load_pbh __m128bh _mm_load_pbh(const void *__p)

VMOVAPS xmm, m128 VEX.128 -mavx10.2

_mm_load_ph __m128h _mm_load_ph(const void *__p)

VMOVAPS xmm, m128 VEX.128 -mavx512fp16

_mm_load_ps __m128 _mm_load_ps(const float *__p)

VMOVAPS xmm, m128 VEX.128 -mavxwith AVX enabled

_mm_store_pbh void _mm_store_pbh(void *__P, __m128bh __A)

VMOVAPS m128, xmm VEX.128 -mavx10.2

_mm_store_ph void _mm_store_ph(void *__P, __m128h __A)

VMOVAPS m128, xmm VEX.128 -mavx512fp16

_mm_store_ps void _mm_store_ps(float *__p, __m128 __a)

VMOVAPS m128, xmm VEX.128 -mavxwith AVX enabled

_mm_store_si128 void _mm_store_si128(__m128i *__p, __m128i __b)

VMOVAPS m128, xmm VEX.128 -mavxwith AVX enabled; Clang emits the equivalent VMOVDQA

_mm_mask_blend_ps __m128 _mm_mask_blend_ps(__mmask8 __U, __m128 __A, __m128 __W)

VMOVAPS xmm {k}, xmm EVEX.128 -mavx512vl

_mm_mask_load_ps __m128 _mm_mask_load_ps(__m128 __W, __mmask8 __U, const void *__P)

VMOVAPS xmm {k}, m128 EVEX.128 -mavx512vl

_mm_mask_mov_ps __m128 _mm_mask_mov_ps(__m128 __W, __mmask8 __U, __m128 __A)

VMOVAPS xmm {k}, xmm EVEX.128 -mavx512vl

_mm_mask_store_ps void _mm_mask_store_ps(void *__P, __mmask8 __U, __m128 __A)

VMOVAPS m128 {k}, xmm EVEX.128 -mavx512vl

_mm_maskz_load_ps __m128 _mm_maskz_load_ps(__mmask8 __U, const void *__P)

VMOVAPS xmm {k}{z}, m128 EVEX.128 -mavx512vl

_mm_maskz_mov_ps __m128 _mm_maskz_mov_ps(__mmask8 __U, __m128 __A)

VMOVAPS xmm {k}{z}, xmm EVEX.128 -mavx512vl

_mm256_load_pbh __m256bh _mm256_load_pbh(const void *__p)

VMOVAPS ymm, m256 VEX.256 -mavx10.2

_mm256_load_ph __m256h _mm256_load_ph(const void *__p)

VMOVAPS ymm, m256 VEX.256 -mavx512fp16

_mm256_load_ps __m256 _mm256_load_ps(const float *__p)

VMOVAPS ymm, m256 VEX.256 -mavx

_mm256_store_pbh void _mm256_store_pbh(void *__P, __m256bh __A)

VMOVAPS m256, ymm VEX.256 -mavx10.2

_mm256_store_ph void _mm256_store_ph(void *__P, __m256h __A)

VMOVAPS m256, ymm VEX.256 -mavx512fp16

_mm256_store_ps void _mm256_store_ps(float *__p, __m256 __a)

VMOVAPS m256, ymm VEX.256 -mavx

_mm256_mask_blend_ps __m256 _mm256_mask_blend_ps(__mmask8 __U, __m256 __A, __m256 __W)

VMOVAPS ymm {k}, ymm EVEX.256 -mavx512vl

_mm256_mask_load_ps __m256 _mm256_mask_load_ps(__m256 __W, __mmask8 __U, const void *__P)

VMOVAPS ymm {k}, m256 EVEX.256 -mavx512vl

_mm256_mask_mov_ps __m256 _mm256_mask_mov_ps(__m256 __W, __mmask8 __U, __m256 __A)

VMOVAPS ymm {k}, ymm EVEX.256 -mavx512vl

_mm256_mask_store_ps void _mm256_mask_store_ps(void *__P, __mmask8 __U, __m256 __A)

VMOVAPS m256 {k}, ymm EVEX.256 -mavx512vl

_mm256_maskz_load_ps __m256 _mm256_maskz_load_ps(__mmask8 __U, const void *__P)

VMOVAPS ymm {k}{z}, m256 EVEX.256 -mavx512vl

_mm256_maskz_mov_ps __m256 _mm256_maskz_mov_ps(__mmask8 __U, __m256 __A)

VMOVAPS ymm {k}{z}, ymm EVEX.256 -mavx512vl

_mm512_load_pbh __m512bh _mm512_load_pbh(const void *__p)

VMOVAPS zmm, m512 EVEX.512 -mavx10.2

_mm512_load_ph __m512h _mm512_load_ph(const void *__p)

VMOVAPS zmm, m512 EVEX.512 -mavx512fp16

_mm512_load_ps __m512 _mm512_load_ps(const void *__p)

VMOVAPS zmm, m512 EVEX.512 -mavx512f

_mm512_store_pbh void _mm512_store_pbh(void *__P, __m512bh __A)

VMOVAPS m512, zmm EVEX.512 -mavx10.2

_mm512_store_ph void _mm512_store_ph(void *__P, __m512h __A)

VMOVAPS m512, zmm EVEX.512 -mavx512fp16

_mm512_store_ps void _mm512_store_ps(void *__P, __m512 __A)

VMOVAPS m512, zmm EVEX.512 -mavx512f

_mm512_mask_blend_ps __m512 _mm512_mask_blend_ps(__mmask16 __U, __m512 __A, __m512 __W)

VMOVAPS zmm {k}, zmm EVEX.512 -mavx512f

_mm512_mask_load_ps __m512 _mm512_mask_load_ps(__m512 __W, __mmask16 __U, const void *__P)

VMOVAPS zmm {k}, m512 EVEX.512 -mavx512f

_mm512_mask_mov_ps __m512 _mm512_mask_mov_ps(__m512 __W, __mmask16 __U, __m512 __A)

VMOVAPS zmm {k}, zmm EVEX.512 -mavx512f

_mm512_mask_store_ps void _mm512_mask_store_ps(void *__P, __mmask16 __U, __m512 __A)

VMOVAPS m512 {k}, zmm EVEX.512 -mavx512f

_mm512_maskz_load_ps __m512 _mm512_maskz_load_ps(__mmask16 __U, const void *__P)

VMOVAPS zmm {k}{z}, m512 EVEX.512 -mavx512f

_mm512_maskz_mov_ps __m512 _mm512_maskz_mov_ps(__mmask16 __U, __m512 __A)

VMOVAPS zmm {k}{z}, zmm EVEX.512 -mavx512f

CPUID and processors

Each form belongs to an XED ISA set. A form can be used when the processor reports every CPUID bit of one of its ISA set's alternatives.

CPUID requirements and processors of the XED ISA sets above. Alternatives are separated by “or”; processors follow XED’s chip model, whose AMD processors end with Zen 2, and the CPU data of this site for Zen 3 to Zen 6.
ISA setCPUIDProcessors
AVX

AVX
CPUID.01H:ECX[28] AVX

Sandy Bridge, Ivy Bridge, Haswell, Broadwell, Skylake, Comet Lake, Cannon Lake, Ice Lake (client), Tiger Lake, Alder Lake, Arrow Lake, Panther Lake, Nova Lake, Skylake-SP, Cascade Lake, Cooper Lake, Ice Lake (server), Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Sierra Forest, Clearwater Forest, Knights Landing, Knights Mill, Bulldozer, Piledriver, Zen, Zen+, Zen 2, Zen 3, Zen 4, Zen 5, Zen 6
AVX512F_512

AVX10.1
CPUID.(EAX=07H,ECX=1):EDX[19] AVX10
CPUID.(EAX=24H,ECX=0):EBX[7:0] ≥ 1 AVX10 version

or

AVX512F
CPUID.(EAX=07H,ECX=0):EBX[16] AVX512F

Cannon Lake, Ice Lake (client), Tiger Lake, Nova Lake, Skylake-SP, Cascade Lake, Cooper Lake, Ice Lake (server), Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Knights Landing, Knights Mill, Zen 4, Zen 5, Zen 6
AVX512F_128

AVX10.1
CPUID.(EAX=07H,ECX=1):EDX[19] AVX10
CPUID.(EAX=24H,ECX=0):EBX[7:0] ≥ 1 AVX10 version

or

AVX512F + AVX512VL
CPUID.(EAX=07H,ECX=0):EBX[16] AVX512F
CPUID.(EAX=07H,ECX=0):EBX[31] AVX512VL

Cannon Lake, Ice Lake (client), Tiger Lake, Nova Lake, Skylake-SP, Cascade Lake, Cooper Lake, Ice Lake (server), Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Zen 4, Zen 5, Zen 6
AVX512F_256
Same as AVX512F_128Same as AVX512F_128

More AVX instructions

All 253 AVX instructions

More AVX10.1 instructions

All 686 AVX10.1 instructions

Sources

  1. Intel XED v2026.08.23 (commit 0bcb6237345c): forms, encodings, operands, flags, exception classes, attributes, ISA sets, CPUID bits and chip model.
  2. The CPU data of x86-64.net: Zen 3 to Zen 6, from GCC’s -march feature sets and AMD’s Processor Programming References, which the page of each processor cites.
  3. Clang's x86 intrinsic headers, LLVM 23.1.2 (commit 85ac56026243): the intrinsics, their signatures and doc comments, and the Clang of that release, which compiled each of them.
  4. LLVM 23.1.2's x86 scheduling models (commit 85ac56026243): the latency, reciprocal throughput and ports of each form, as llvm-mca reports them.
  5. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2B, page 4-41 (MOVAPS)
  6. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 1 (253665-093, September 2026)
  7. Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
  8. Software Optimization Guide for the AMD Zen5 Microarchitecture (58455, rev. 1.00, August 2024), Wayback Machine copy of AMD's ZIP

The tables are derived from Intel XED, Copyright Intel Corporation, licensed under the Apache License 2.0; x86-64.net converted and reformatted them. The intrinsics and their signatures come from Clang and the timings from LLVM's scheduling models, both part of the LLVM Project, licensed under the Apache License 2.0 with LLVM Exceptions. The text is our own.