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

VMOVUPD copies 16, 32 or 64 bytes between vector registers, or between a register and memory at any address, bits not interpreted. It is MOVUPD in VEX and EVEX encodings and the double-precision twin of VMOVUPS, whose page covers what the two share: the clearing above the vector width, masked loads that do not fault on the elements left out, the two register encodings and loop tails. VMOVAPD is the same move for aligned addresses. What the PD name changes is the mask: one bit per double.

Masks per double

On Zen 5, vmovupd zmm1{k2}, zmmword ptr [mem] with C9H in the low byte of K2 loaded doubles 0, 3, 6 and 7 and kept the other four of ZMM1, and a store under E5H wrote doubles 0, 2, 5, 6 and 7 and left the rest of memory as it was. A 256-bit form reads only the low four mask bits: vmovupd ymm0{k1}{z}, ymm31 with A0H in K1 zeroed the whole register, since bits 3 to 0 were clear. The 17 recorded cases cover every form, all at a 64-byte aligned address.

In compiled code

In our builds at -O2, both GCC 14 and Clang 23 load and store the doubles of a loop such as d[i] = s[i] * 2.0 with VMOVUPD: on ymm registers for -march=x86-64-v3, and for x86-64-v4 on zmm in GCC and ymm in Clang. For a tail of n doubles, a mask made with BZHI and _mm512_maskz_loadu_pd with _mm512_mask_storeu_pd give a zeroing VMOVUPD load and a masked VMOVUPD store under both compilers.

Alignment still counts

The U only removes the fault. AMD’s Zen 5 guide says that a load or store crossing a 64-byte boundary costs at least a cycle and runs at half throughput, and one crossing a 4 KiB page can cost much more (Section 2.6.2; MOVDQU has the details). A zmm access is 64 bytes long, so at any address that is not a multiple of 64 it always spans two cache lines, where a ymm access does so only at some offsets.

Forms

Every encoding of VMOVUPD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VMOVUPD xmm, m128 VMOVUPD_XMMdq_MEMdqVEX.128.66.0F.WIG 10 /rAVX
VMOVUPD xmm, xmm VMOVUPD_XMMdq_XMMdq_10VEX.128.66.0F.WIG 10 /rAVX
VMOVUPD m128, xmm VMOVUPD_MEMdq_XMMdqVEX.128.66.0F.WIG 11 /rAVX
VMOVUPD xmm, xmm VMOVUPD_XMMdq_XMMdq_11VEX.128.66.0F.WIG 11 /rAVX
VMOVUPD ymm, m256 VMOVUPD_YMMqq_MEMqqVEX.256.66.0F.WIG 10 /rAVX
VMOVUPD ymm, ymm VMOVUPD_YMMqq_YMMqq_10VEX.256.66.0F.WIG 10 /rAVX
VMOVUPD m256, ymm VMOVUPD_MEMqq_YMMqqVEX.256.66.0F.WIG 11 /rAVX
VMOVUPD ymm, ymm VMOVUPD_YMMqq_YMMqq_11VEX.256.66.0F.WIG 11 /rAVX
VMOVUPD zmm {k}{z}, zmm VMOVUPD_ZMMf64_MASKmskw_ZMMf64_AVX512EVEX.512.66.0F.W1 10 /r
EVEX.512.66.0F.W1 11 /r
AVX10.1 or AVX512F
VMOVUPD zmm {k}{z}, m512 VMOVUPD_ZMMf64_MASKmskw_MEMf64_AVX512EVEX.512.66.0F.W1 10 /rAVX10.1 or AVX512F
VMOVUPD m512 {k}, zmm VMOVUPD_MEMf64_MASKmskw_ZMMf64_AVX512EVEX.512.66.0F.W1 11 /rAVX10.1 or AVX512F
VMOVUPD xmm {k}{z}, xmm VMOVUPD_XMMf64_MASKmskw_XMMf64_AVX512EVEX.128.66.0F.W1 10 /r
EVEX.128.66.0F.W1 11 /r
AVX10.1 or AVX512F + AVX512VL
VMOVUPD xmm {k}{z}, m128 VMOVUPD_XMMf64_MASKmskw_MEMf64_AVX512EVEX.128.66.0F.W1 10 /rAVX10.1 or AVX512F + AVX512VL
VMOVUPD m128 {k}, xmm VMOVUPD_MEMf64_MASKmskw_XMMf64_AVX512EVEX.128.66.0F.W1 11 /rAVX10.1 or AVX512F + AVX512VL
VMOVUPD ymm {k}{z}, ymm VMOVUPD_YMMf64_MASKmskw_YMMf64_AVX512EVEX.256.66.0F.W1 10 /r
EVEX.256.66.0F.W1 11 /r
AVX10.1 or AVX512F + AVX512VL
VMOVUPD ymm {k}{z}, m256 VMOVUPD_YMMf64_MASKmskw_MEMf64_AVX512EVEX.256.66.0F.W1 10 /rAVX10.1 or AVX512F + AVX512VL
VMOVUPD m256 {k}, ymm VMOVUPD_MEMf64_MASKmskw_YMMf64_AVX512EVEX.256.66.0F.W1 11 /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 / 1FPU1
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 double is copied where its bit of k1 is 1; elsewhere merging keeps the old element, and zeroing writes 0.VMOVUPD xmm, xmm/m128 VMOVUPD ymm, ymm/m256 VMOVUPD xmm {k}{z}, xmm/m128 VMOVUPD ymm {k}{z}, ymm/m256 VMOVUPD zmm {k}{z}, zmm/m512

merging, {k1}

VMOVUPD with merging, {k1}With merging: result doubles 1 to 0: a1, unchanged.01xmm2or m128a10k1a1xmm1

zeroing, {k1}{z}

VMOVUPD with zeroing, {k1}{z}With zeroing: result doubles 1 to 0: a1, 0.0

Example mask k1 = 0x02. Every double works alike: 2, 4 and 8 doubles in the xmm, ymm and zmm forms.

With merging: result doubles 1 to 0: a1, unchanged.

With zeroing: result doubles 1 to 0: a1, 0.

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

Example mask k1 = 0x02. Every double works alike: 2, 4 and 8 doubles in the xmm, ymm and zmm forms.

Memory doubles 1 to 0: a1, unchanged.

Operation

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

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

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

VMOVUPD m128, xmm VMOVUPD m256, ymm VMOVUPD m128 {k}, xmm VMOVUPD m256 {k}, ymm VMOVUPD m512 {k}, zmm
for i in range(VL // 64):
    if k1[i]:  # 1 without a write mask
        mem.q[i] = zmm2.q[i]
    # else: mem.q[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
VMOVUPD xmm, xmm/m128 VMOVUPD ymm, ymm/m256
xmm, ymmexplicitwrite
xmm/m128, ymm/m256explicitread
VMOVUPD xmm/m128, xmm VMOVUPD ymm/m256, ymm
xmm/m128, ymm/m256explicitwrite
xmm, ymmexplicitread
VMOVUPD xmm {k}{z}, xmm/m128 VMOVUPD ymm {k}{z}, ymm/m256 VMOVUPD zmm {k}{z}, zmm/m512
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm/m128, ymm/m256, zmm/m512explicitread
VMOVUPD m128 {k}, xmm VMOVUPD m256 {k}, ymm VMOVUPD 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-4M
EVEX forms
AVX512-E4

Attributes

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

EVEX forms
write masking
EVEX memory forms
memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VMOVUPD, 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_loadu_pd __m128d _mm_loadu_pd(const double *__dp)

VMOVUPD xmm, m128 VEX.128 -mavxwith AVX enabled

_mm_storeu_pd void _mm_storeu_pd(double *__dp, __m128d __a)

VMOVUPD m128, xmm VEX.128 -mavxwith AVX enabled

_mm_mask_loadu_pd __m128d _mm_mask_loadu_pd(__m128d __W, __mmask8 __U, const void *__P)

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

_mm_mask_storeu_pd void _mm_mask_storeu_pd(void *__P, __mmask8 __U, __m128d __A)

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

_mm_maskz_loadu_pd __m128d _mm_maskz_loadu_pd(__mmask8 __U, const void *__P)

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

_mm256_loadu_pd __m256d _mm256_loadu_pd(const double *__p)

VMOVUPD ymm, m256 VEX.256 -mavx

_mm256_storeu_pd void _mm256_storeu_pd(double *__p, __m256d __a)

VMOVUPD m256, ymm VEX.256 -mavx

_mm256_mask_loadu_pd __m256d _mm256_mask_loadu_pd(__m256d __W, __mmask8 __U, const void *__P)

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

_mm256_mask_storeu_pd void _mm256_mask_storeu_pd(void *__P, __mmask8 __U, __m256d __A)

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

_mm256_maskz_loadu_pd __m256d _mm256_maskz_loadu_pd(__mmask8 __U, const void *__P)

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

_mm512_loadu_pd __m512d _mm512_loadu_pd(const void *__p)

VMOVUPD zmm, m512 EVEX.512 -mavx512f

_mm512_storeu_pd void _mm512_storeu_pd(void *__P, __m512d __A)

VMOVUPD m512, zmm EVEX.512 -mavx512f

_mm512_mask_loadu_pd __m512d _mm512_mask_loadu_pd(__m512d __W, __mmask8 __U, const void *__P)

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

_mm512_mask_storeu_pd void _mm512_mask_storeu_pd(void *__P, __mmask8 __U, __m512d __A)

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

_mm512_maskz_loadu_pd __m512d _mm512_maskz_loadu_pd(__mmask8 __U, const void *__P)

VMOVUPD zmm {k}{z}, m512 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-122 (MOVUPD)
  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.