Instruction
VMOVSD
Moves the low double between XMM registers or to and from memory; a load zeroes the rest of the register.
VMOVSD is the VEX and EVEX form of MOVSD, whose page covers the scalar double move and the string instruction that shares its name. The load of eight bytes now clears the register up to bit 511, and the store is unchanged. The register form takes a second source: the low double comes from the last operand and the high double from the first source rather than from the destination, and bits 128 and up are cleared. VMOVSS covers what the two encodings share: two opcodes for the register form, no ymm form, vvvv at 1111b for the memory forms, AVX for VEX and AVX-512F or AVX10.1 for EVEX, whose write mask covers the one double. Zen 5’s recorded cases:
{store} vmovsd xmm0, xmm13, xmm9, the 11h encoding, put the low double of XMM9 under the high double of XMM13 and cleared bits 511:128 of ZMM0.vmovsd xmm17{k1}{z}, qword ptr [mem], with bit 0 of K1 clear, left all of ZMM17 zero: the masked double is zeroed, and the load clears the rest in any case.vmovsd qword ptr [mem]{k6}, xmm7, with bit 0 of K6 clear, left the eight bytes alone.
In compiled code
In our builds at -O2 with -march=x86-64-v3 and x86-64-v4, GCC 14
and Clang 23 load and store double values with VMOVSD, except that
GCC loads _mm_load_sd(p) with VMOVQ. _mm_set_sd(x) is
vmovq xmm0, xmm0 in both, the zeroing register move that the scalar
moves lack (VMOVQ). _mm_move_sd(a, b) is
vmovsd xmm0, xmm0, xmm1 in GCC and vblendps xmm0, xmm0, xmm1, 3 in
Clang. At -v4 Clang selects between two doubles with the write mask,
vcmpltsd k1, xmm0, xmm1 and then vmovsd xmm3{k1}, xmm3, xmm2 for
x < y ? a : b, as VMOVSS’s page shows for floats; GCC uses
VCMPNLTSD and VBLENDVPD.
AMD’s latency spreadsheet for Zen 5 gives VMOVSD the cells of VMOVSS: one macro-op on pipes FP0 to FP3, a latency of 1 cycle, four per cycle in the VEX row and the EVEX register and store row, two per cycle in the EVEX load row.
Forms
| Instruction | Encoding | Requires |
|---|---|---|
VMOVSD xmm, m64
VMOVSD_XMMdq_MEMq | VEX.LIG.F2.0F.WIG 10 /r | AVX |
VMOVSD m64, xmm
VMOVSD_MEMq_XMMq | VEX.LIG.F2.0F.WIG 11 /r | AVX |
VMOVSD xmm, xmm, xmm
VMOVSD_XMMdq_XMMdq_XMMq_10 | VEX.LIG.F2.0F.WIG 10 /r | AVX |
VMOVSD xmm, xmm, xmm
VMOVSD_XMMdq_XMMdq_XMMq_11 | VEX.LIG.F2.0F.WIG 11 /r | AVX |
VMOVSD xmm {k}{z}, m64
VMOVSD_XMMf64_MASKmskw_MEMf64_AVX512 | EVEX.LIG.F2.0F.W1 10 /r | AVX10.1 or AVX512F |
VMOVSD m64 {k}, xmm
VMOVSD_MEMf64_MASKmskw_XMMf64_AVX512 | EVEX.LIG.F2.0F.W1 11 /r | AVX10.1 or AVX512F |
VMOVSD xmm {k}{z}, xmm, xmm
VMOVSD_XMMf64_MASKmskw_XMMf64_XMMf64_AVX512 | EVEX.LIG.F2.0F.W1 10 /rEVEX.LIG.F2.0F.W1 11 /r | AVX10.1 or AVX512F |
Latency and throughput
| Model | xmm, m64 | m64, xmmm64 {k}, xmm | xmm, xmm, xmmxmm {k}{z}, xmm, xmm | xmm {k}{z}, m64no mask | xmm {k}{z}, m64with a mask, zeroing |
|---|---|---|---|---|---|
| Sandy Bridge | 6 / 0.5p23 | 1 / 1p4 p23 | 1 / 1p5 | ||
| Haswell, Broadwell, Skylake | 5 / 0.5p23 | 1 / 1p2347 | 1 / 1p5 | ||
| Skylake-SP | 5 / 0.5p23 | 1 / 1p2347 | 1 / 1p5 | 7 / 1p5 | 7 / 1p5 |
| Ice Lake | 5 / 0.5p23 | 1 / 0.5p4789 | 1 / 0.33p015 | 7 / 1p5 | 7 / 1p5 |
| Alder Lake | 7 / 0.33p2 p3 p10 | 12 / 0.5p4789 | 1 / 0.33p015 | ||
| Sapphire Rapids | 7 / 0.33p2 p3 p10 | 12 / 0.5p4789 | 1 / 0.33p015 | 7 / 0.33p2 p3 p10 | 8 / 0.33p015 |
| Lunar Lake | 7 / 0.33p20 p21 p22 | 12 / 0.5p10 p11 p25 p26 p27 | 1 / 0.25V0 V1 V2 V3 | ||
| Piledriver | 5 / 1.5FPFMA FPU0 FPU1 | 2 / 1.5AGLU01 FPSTO FPU2 FPU3 Store | 2 / 1FPFMA FPU0 FPU1 | ||
| Zen | 8 / 0.5AGU0 AGU1 | 1 / 0.5AGU0 AGU1 | 1 / 0.5FPU1 FPU2 | ||
| Zen 2 | 8 / 0.33AGU0 AGU1 AGU2 | 1 / 0.33AGU0 AGU1 AGU2 | 1 / 0.5FPU1 FPU2 | ||
| Zen 3 | 8 / 0.5FP45 LSU Load | 1 / 1FP45 FPSt LSU Store | 1 / 0.5FP1 FP2 | ||
| Zen 4 | 8 / 0.5FP45 LSU Load | 1 / 1FP45 FPSt LSU Store | 1 / 0.5FP1 FP2 | 8 / 0.5FP45 LSU Load | 8 / 0.5FP45 LSU Load |
| Jaguar | 5 / 1FPA FPM FPU0 FPU1 | 2 / 1FPU1 | 1 / 0.5FPA FPM FPU0 FPU1 | ||
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.
VMOVSD xmm, m64 VMOVSD xmm {k}{z}, m64The write mask k1 applies to the low double only: with bit 0 clear, it keeps its old value, or is zeroed with {z}.
Result doubles 1 to 0: 0, a0.
VMOVSD m64, xmm VMOVSD m64 {k}, xmmThe write mask k1 applies to the low double only: with bit 0 clear, it keeps its old value.
m64 receives double 0 of xmm2: a0.
The write mask k1 applies to the low double only: with bit 0 clear, it keeps its old value, or is zeroed with {z}.
Result doubles 1 to 0: b1, a0.
Operation
What the forms do, in pseudocode that our tests run against results recorded on real processors. How to read.
VMOVSD xmm, m64 VMOVSD xmm {k}{z}, m64if k1[0]: # 1 without a write mask
xmm1.q[0] = mem.q[0]
elif zeroing:
xmm1.q[0] = 0
# else: xmm1.q[0] keeps its value
for i in range(1, 2):
xmm1.q[i] = 0
# xmm1 is zeroed from bit 128 upRun on AMD Zen 5 (EPYC 9645): 2 cases.
VMOVSD m64, xmm VMOVSD m64 {k}, xmmif k1[0]: # 1 without a write mask
mem.q[0] = xmm2.q[0]
# else: mem.q[0] is not writtenRun on AMD Zen 5 (EPYC 9645): 2 cases.
if k1[0]: # 1 without a write mask
xmm1.q[0] = xmm3.q[0]
elif zeroing:
xmm1.q[0] = 0
# else: xmm1.q[0] keeps its value
for i in range(1, 2):
xmm1.q[i] = xmm2.q[i]
# xmm1 is zeroed from bit 128 upRun on AMD Zen 5 (EPYC 9645): 3 cases.
Operands
| Operand | Kind | Action |
|---|---|---|
VMOVSD xmm, m64 | ||
xmm | explicit | write |
m64 | explicit | read |
VMOVSD m64, xmm | ||
m64 | explicit | write |
xmm | explicit | read |
VMOVSD xmm, xmm, xmm | ||
xmm | explicit | write |
xmm | explicit | read |
xmm | explicit | read |
VMOVSD xmm {k}{z}, m64 | ||
xmm | explicit | write (masked) |
{k} | explicit | read (write mask) |
m64 | explicit | read |
VMOVSD m64 {k}, xmm | ||
m64 | explicit | write (masked) |
{k} | explicit | read (write mask) |
xmm | explicit | read |
VMOVSD xmm {k}{z}, xmm, xmm | ||
xmm | explicit | write (masked) |
{k} | explicit | read (write mask) |
xmm | explicit | read |
xmm | explicit | read |
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-5- EVEX forms
AVX512-E5
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 VMOVSD, 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.
| Intrinsic | Compiles to |
|---|---|
_mm_load_sd
__m128d _mm_load_sd(const double *__dp) |
|
_mm_store_sd
void _mm_store_sd(double *__dp, __m128d __a) |
|
_mm_mask_load_sd
__m128d _mm_mask_load_sd(__m128d __W, __mmask8 __U, const double *__A) |
|
_mm_mask_move_sd
__m128d _mm_mask_move_sd(__m128d __W, __mmask8 __U, __m128d __A, __m128d __B) |
|
_mm_mask_store_sd
void _mm_mask_store_sd(double *__W, __mmask8 __U, __m128d __A) |
|
_mm_maskz_load_sd
__m128d _mm_maskz_load_sd(__mmask8 __U, const double *__A) |
|
_mm_maskz_move_sd
__m128d _mm_maskz_move_sd(__mmask8 __U, __m128d __A, __m128d __B) |
|
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.
| ISA set | CPUID | Processors |
|---|---|---|
AVX | 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_SCALAR | AVX10.1 or 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 |
More AVX instructions
- VMINSS
- VMOVAPD
- VMOVAPS
- VMOVD
- VMOVDDUP
- VMOVDQA
- VMOVDQU
- VMOVHLPS
- VMOVHPD
- VMOVHPS
- VMOVLHPS
- VMOVLPD
- VMOVLPS
- VMOVMSKPD
- VMOVMSKPS
- VMOVNTDQ
- VMOVNTDQA
- VMOVNTPD
- VMOVNTPS
- VMOVQ
- VMOVSHDUP
- VMOVSLDUP
- VMOVSS
- VMOVUPD
- VMOVUPS
- VMPSADBW
- VMULPD
- VMULPS
- VMULSD
- VMULSS
- VORPD
- VORPS
- VPABSB
- VPABSD
- VPABSW
- VPACKSSDW
- VPACKSSWB
- VPACKUSDW
- VPACKUSWB
- VPADDB
More AVX10.1 instructions
Sources
- Intel XED v2026.08.23 (commit
0bcb6237345c): forms, encodings, operands, flags, exception classes, attributes, ISA sets, CPUID bits and chip model. - The CPU data of x86-64.net: Zen 3 to Zen 6, from GCC’s
-marchfeature sets and AMD’s Processor Programming References, which the page of each processor cites. - 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. - LLVM 23.1.2's x86 scheduling models (commit
85ac56026243): the latency, reciprocal throughput and ports of each form, as llvm-mca reports them. - Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2B, page 4-108 (MOVSD)
- Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 1 (253665-093, September 2026)
- Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
- AMD64 Architecture Programmer's Manual, Volume 4: 128-Bit, 256-Bit, and 512-Bit Media Instructions (26568, rev. 3.27, July 2026)
- 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.