Instruction
VMOVSS
Moves the low single between XMM registers or to and from memory; a load zeroes the rest of the register.
VMOVSS is the VEX and EVEX form of MOVSS, whose page
covers the single-precision move and its uses in C. A load of four
bytes now clears the register up to bit 511; the store is unchanged.
The register form names two sources: the low single comes from the
last, singles 1 to 3 from the first, and bits 128 and up are cleared,
so vmovss xmm0, xmm2, xmm1 merges into a third register. As for
MOVSD, opcodes 10h and 11h both encode it. There is no
ymm form, and the load and store need vvvv at 1111b. The VEX form needs
AVX; the EVEX form, AVX-512F or AVX10.1, adds a write mask on the
single: a masked store with bit 0 clear writes nothing, and a masked
load clears bits 32 and up whatever the mask says.
On Zen 5, vmovss xmm12, xmm6, xmm6 and its {store} twin, opcode
11h, both gave the low 128 bits of XMM6 and cleared bits 511:128 of
ZMM12. vmovss xmm0{k4}{z}, dword ptr [mem], with bit 0 of K4 set,
loaded the single and zeroed the rest of ZMM0, and
vmovss dword ptr [mem]{k1}, xmm5, with bit 0 of K1 clear, left the
four bytes as they were.
Merging and selecting
In our builds at -O2 with -march=x86-64-v3 and x86-64-v4, GCC 14
and Clang 23 load and store float values with VMOVSS. For
_mm_move_ss(a, b) GCC emits vmovss xmm0, xmm0, xmm1 and Clang
vblendps xmm0, xmm0, xmm1, 1. The write mask appears at -v4, in
Clang: c ? a : b on floats becomes SETE, KMOVD and
vmovss xmm0{k1}, xmm0, xmm1, and x < y ? a : b becomes VCMPLTSS
into K1 and a masked VMOVSS. GCC keeps a branch for the first and
blends with VBLENDVPS for the second, as Clang
does at -v3.
AMD’s latency spreadsheet for Zen 5 gives VMOVSS one macro-op on pipes FP0 to FP3 with a latency of 1 cycle: four per cycle in its VEX row and its EVEX row for registers and stores, two in its EVEX load row.
Forms
| Instruction | Encoding | Requires |
|---|---|---|
VMOVSS xmm, m32
VMOVSS_XMMdq_MEMd | VEX.LIG.F3.0F.WIG 10 /r | AVX |
VMOVSS m32, xmm
VMOVSS_MEMd_XMMd | VEX.LIG.F3.0F.WIG 11 /r | AVX |
VMOVSS xmm, xmm, xmm
VMOVSS_XMMdq_XMMdq_XMMd_10 | VEX.LIG.F3.0F.WIG 10 /r | AVX |
VMOVSS xmm, xmm, xmm
VMOVSS_XMMdq_XMMdq_XMMd_11 | VEX.LIG.F3.0F.WIG 11 /r | AVX |
VMOVSS xmm {k}{z}, m32
VMOVSS_XMMf32_MASKmskw_MEMf32_AVX512 | EVEX.LIG.F3.0F.W0 10 /r | AVX10.1 or AVX512F |
VMOVSS m32 {k}, xmm
VMOVSS_MEMf32_MASKmskw_XMMf32_AVX512 | EVEX.LIG.F3.0F.W0 11 /r | AVX10.1 or AVX512F |
VMOVSS xmm {k}{z}, xmm, xmm
VMOVSS_XMMf32_MASKmskw_XMMf32_XMMf32_AVX512 | EVEX.LIG.F3.0F.W0 10 /rEVEX.LIG.F3.0F.W0 11 /r | AVX10.1 or AVX512F |
Latency and throughput
| Model | xmm, m32 | m32, xmmm32 {k}, xmm | xmm, xmm, xmmxmm {k}{z}, xmm, xmm | xmm {k}{z}, m32no mask | xmm {k}{z}, m32with 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.
VMOVSS xmm, m32 VMOVSS xmm {k}{z}, m32The write mask k1 applies to the low single only: with bit 0 clear, it keeps its old value, or is zeroed with {z}.
Result singles 3 to 0: 0, 0, 0, a0.
VMOVSS m32, xmm VMOVSS m32 {k}, xmmThe write mask k1 applies to the low single only: with bit 0 clear, it keeps its old value.
m32 receives single 0 of xmm2: a0.
The write mask k1 applies to the low single only: with bit 0 clear, it keeps its old value, or is zeroed with {z}.
Result singles 3 to 0: b3, b2, b1, a0.
Operation
What the forms do, in pseudocode that our tests run against results recorded on real processors. How to read.
VMOVSS xmm, m32 VMOVSS xmm {k}{z}, m32if k1[0]: # 1 without a write mask
xmm1.d[0] = mem.d[0]
elif zeroing:
xmm1.d[0] = 0
# else: xmm1.d[0] keeps its value
for i in range(1, 4):
xmm1.d[i] = 0
# xmm1 is zeroed from bit 128 upRun on AMD Zen 5 (EPYC 9645): 2 cases.
VMOVSS m32, xmm VMOVSS m32 {k}, xmmif k1[0]: # 1 without a write mask
mem.d[0] = xmm2.d[0]
# else: mem.d[0] is not writtenRun on AMD Zen 5 (EPYC 9645): 2 cases.
if k1[0]: # 1 without a write mask
xmm1.d[0] = xmm3.d[0]
elif zeroing:
xmm1.d[0] = 0
# else: xmm1.d[0] keeps its value
for i in range(1, 4):
xmm1.d[i] = xmm2.d[i]
# xmm1 is zeroed from bit 128 upRun on AMD Zen 5 (EPYC 9645): 3 cases.
Operands
| Operand | Kind | Action |
|---|---|---|
VMOVSS xmm, m32 | ||
xmm | explicit | write |
m32 | explicit | read |
VMOVSS m32, xmm | ||
m32 | explicit | write |
xmm | explicit | read |
VMOVSS xmm, xmm, xmm | ||
xmm | explicit | write |
xmm | explicit | read |
xmm | explicit | read |
VMOVSS xmm {k}{z}, m32 | ||
xmm | explicit | write (masked) |
{k} | explicit | read (write mask) |
m32 | explicit | read |
VMOVSS m32 {k}, xmm | ||
m32 | explicit | write (masked) |
{k} | explicit | read (write mask) |
xmm | explicit | read |
VMOVSS 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 VMOVSS, 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_ss
__m128 _mm_load_ss(const float *__p) |
|
_mm_store_ss
void _mm_store_ss(float *__p, __m128 __a) |
|
_mm_mask_load_ss
__m128 _mm_mask_load_ss(__m128 __W, __mmask8 __U, const float *__A) |
|
_mm_mask_move_ss
__m128 _mm_mask_move_ss(__m128 __W, __mmask8 __U, __m128 __A, __m128 __B) |
|
_mm_mask_store_ss
void _mm_mask_store_ss(float *__W, __mmask8 __U, __m128 __A) |
|
_mm_maskz_load_ss
__m128 _mm_maskz_load_ss(__mmask8 __U, const float *__A) |
|
_mm_maskz_move_ss
__m128 _mm_maskz_move_ss(__mmask8 __U, __m128 __A, __m128 __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
- VMOVD
- VMOVDDUP
- VMOVDQA
- VMOVDQU
- VMOVHLPS
- VMOVHPD
- VMOVHPS
- VMOVLHPS
- VMOVLPD
- VMOVLPS
- VMOVMSKPD
- VMOVMSKPS
- VMOVNTDQ
- VMOVNTDQA
- VMOVNTPD
- VMOVNTPS
- VMOVQ
- VMOVSD
- VMOVSHDUP
- VMOVSLDUP
- VMOVUPD
- VMOVUPS
- VMPSADBW
- VMULPD
- VMULPS
- VMULSD
- VMULSS
- VORPD
- VORPS
- VPABSB
- VPABSD
- VPABSW
- VPACKSSDW
- VPACKSSWB
- VPACKUSDW
- VPACKUSWB
- VPADDB
- VPADDD
- VPADDQ
- VPADDSB
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-117 (MOVSS)
- 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.