Instruction
MOVLPD
Loads a double from memory into the low half of an XMM register, or stores the low double to memory.
- Extensions
- Forms
- 2 (2 Legacy)
- Data
- Intel XED v2026.08.23
MOVLPD, from SSE2, moves one double between memory and the low half of an XMM register. The load replaces bits 63:0 and keeps bits 127:64, unlike a MOVSD load, which clears them; the store writes eight bytes, as a MOVSD store does. MOVHPD is the high-half twin and explains what the pair is for, and MOVLPS is the same instruction with no 66 prefix. There is no register to register form; MOVSD between registers is the merging move. The memory operand need not be aligned, and the load keeps bits 128 and up of the register (see SSE and AVX).
Zen 5’s recorded cases: movlpd xmm0, qword ptr [mem] replaced the low
double of XMM0 and kept the high one, and movlpd qword ptr [mem], xmm7
wrote the low double of XMM7 and left the next bytes alone.
Where compilers use it
In our builds at -O2, GCC 14 compiles _mm_loadl_pd(a, p), or assigning
*p to element 0 of a __m128d, to movlpd xmm0, QWORD PTR [rdi], and
_mm_storel_pd to the store; Clang 23 uses MOVLPS for both. For a plain
double, both compilers load with MOVSD, which does not depend on the
register’s old contents. Clang also stored a single result with MOVLPD
in the scalar tail of a vectorized loop, where MOVSD would have done the
same.
The merging load has a cost and a remedy on Zen 5. AMD’s guide
recommends whole-register loads over MOVLPD and MOVHPD halves (Section
2.11.2), and lists MOVLPD xmm, [mem] among the instructions whose
merge can skip waiting for the register’s old value when the processor
has tracked its upper bits as cleared to zero (Section 2.11.5).
In the optimization guide
What the optimization guide says about MOVLPD, a line per claim. Each links to the claim in the guide, with its sources and where they differ.
Out of order
- Partial register and flag writes: Scalar SSE instructions that write only the low element of an XMM register keep the rest of it, and so wait for its last writer:
movssandmovsdbetween registers,movlpdandmovhpdfrom memory, and conversions and square roots such ascvtsi2sdandsqrtss.
Forms
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.
MOVLPD xmm, m64Result quadwords 1 to 0: a1, b0.
MOVLPD m64, xmmm64 receives quadword 0 of xmm2: a0.
Operation
What the forms do, in pseudocode that our tests run against results recorded on real processors. How to read.
MOVLPD xmm, m64xmm1.q[0] = mem.q[0] # xmm1.q[1] keeps its value
# bits 128 and up of the register are unchangedRun on AMD Zen 5 (EPYC 9645): 1 case.
MOVLPD m64, xmmmem.q[0] = xmm2.q[0]Run on AMD Zen 5 (EPYC 9645): 1 case.
Operands
| Operand | Kind | Action |
|---|---|---|
MOVLPD xmm, m64 | ||
xmm | explicit | read, write |
m64 | explicit | read |
MOVLPD m64, xmm | ||
m64 | explicit | write |
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.
- All forms
SSE_TYPE_5
Intrinsics
The C intrinsics of Clang 23.1.2 that compile to MOVLPD, 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_loadl_pd
__m128d _mm_loadl_pd(__m128d __a, const double *__dp) |
|
_mm_loadl_pi
__m128 _mm_loadl_pi(__m128 __a, const __m64 *__p) |
|
_mm_storel_pd
void _mm_storel_pd(double *__dp, __m128d __a) |
|
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 |
|---|---|---|
SSE2 | SSE2 | Every x86-64 processor in XED’s model and Zen 3 to Zen 6 |
More SSE2 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. - Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2B, page 4-80 (MOVLPD)
- Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 1 (253665-093, September 2026)
- AMD64 Architecture Programmer's Manual, Volume 4: 128-Bit and 256-Bit Media Instructions (26568, rev. 3.25, November 2021), Wayback Machine copy of AMD's PDF
- 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, part of the LLVM Project, licensed under the Apache License 2.0 with LLVM Exceptions. The text is our own.