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

VMOVUPS copies packed singles between vector registers, or between a register and memory at any address. Like MOVUPS, its SSE form, it does not interpret the bits, so compilers move any data with it: at -O2 with -march=x86-64-v3, GCC 14 and Clang 23 load and store the floats of vectorized loops with VMOVUPS, and Clang also uses it for _mm256_loadu_si256 and for a 32-byte memcpy, where GCC emits VMOVDQU. VMOVAPS is the same move for aligned addresses, and AMD’s Zen 5 guide says that on aligned data the two perform the same (Section 2.6.2).

What VEX and EVEX add

  • Clearing above the width. MOVUPS leaves bits 128 and up of its destination register alone; every VEX and EVEX form clears them above its own width. On Zen 5, vmovups xmm8, xmm15 left bits 128 to 511 of ZMM8 zero.
  • Write masks. The EVEX forms (AVX512F, or AVX10.1) select singles with a mask register. A masked load keeps the unselected elements of the destination, or zeroes them with {z}; a masked store writes only the selected ones. Elements left out raise no fault, so a load may reach into an unmapped page past the end of an array.
  • Two register encodings. Opcode 10 writes the register in ModRM.reg and 11 the one in ModRM.rm. GNU as and LLVM’s assembler pick 10, but take 11 where that fits the two-byte VEX prefix: vmovups xmm0, xmm15 becomes C5 78 11 F8.

Loop tails

The masks let a loop finish without a scalar remainder: for a mask of the n low bits made with BZHI, _mm512_maskz_loadu_ps and _mm512_mask_storeu_ps compile to one VMOVUPS each under both compilers with -march=x86-64-v4. For a plain loop over 1,024 floats that target makes GCC 14 use zmm registers, while Clang 23 stays with ymm.

Zen 5’s 17 recorded cases cover every form, among them a masked vmovups zmm14{k6} load that kept the unselected singles of ZMM14 and a masked store that left the unselected memory as it was.

In the optimization guide

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

Memory

  • Cache lines, alignment and splits: In a stream of consecutive accesses that all start at the same misalignment, the share that splits a line grows with the width: one 16-byte access in four, every second 32-byte AVX access and every 64-byte AVX-512 access.

Forms

Every encoding of VMOVUPS that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VMOVUPS xmm, m128 VMOVUPS_XMMdq_MEMdqVEX.128.NP.0F.WIG 10 /rAVX
VMOVUPS xmm, xmm VMOVUPS_XMMdq_XMMdq_10VEX.128.NP.0F.WIG 10 /rAVX
VMOVUPS m128, xmm VMOVUPS_MEMdq_XMMdqVEX.128.NP.0F.WIG 11 /rAVX
VMOVUPS xmm, xmm VMOVUPS_XMMdq_XMMdq_11VEX.128.NP.0F.WIG 11 /rAVX
VMOVUPS ymm, m256 VMOVUPS_YMMqq_MEMqqVEX.256.NP.0F.WIG 10 /rAVX
VMOVUPS ymm, ymm VMOVUPS_YMMqq_YMMqq_10VEX.256.NP.0F.WIG 10 /rAVX
VMOVUPS m256, ymm VMOVUPS_MEMqq_YMMqqVEX.256.NP.0F.WIG 11 /rAVX
VMOVUPS ymm, ymm VMOVUPS_YMMqq_YMMqq_11VEX.256.NP.0F.WIG 11 /rAVX
VMOVUPS zmm {k}{z}, zmm VMOVUPS_ZMMf32_MASKmskw_ZMMf32_AVX512EVEX.512.NP.0F.W0 10 /r
EVEX.512.NP.0F.W0 11 /r
AVX10.1 or AVX512F
VMOVUPS zmm {k}{z}, m512 VMOVUPS_ZMMf32_MASKmskw_MEMf32_AVX512EVEX.512.NP.0F.W0 10 /rAVX10.1 or AVX512F
VMOVUPS m512 {k}, zmm VMOVUPS_MEMf32_MASKmskw_ZMMf32_AVX512EVEX.512.NP.0F.W0 11 /rAVX10.1 or AVX512F
VMOVUPS xmm {k}{z}, xmm VMOVUPS_XMMf32_MASKmskw_XMMf32_AVX512EVEX.128.NP.0F.W0 10 /r
EVEX.128.NP.0F.W0 11 /r
AVX10.1 or AVX512F + AVX512VL
VMOVUPS xmm {k}{z}, m128 VMOVUPS_XMMf32_MASKmskw_MEMf32_AVX512EVEX.128.NP.0F.W0 10 /rAVX10.1 or AVX512F + AVX512VL
VMOVUPS m128 {k}, xmm VMOVUPS_MEMf32_MASKmskw_XMMf32_AVX512EVEX.128.NP.0F.W0 11 /rAVX10.1 or AVX512F + AVX512VL
VMOVUPS ymm {k}{z}, ymm VMOVUPS_YMMf32_MASKmskw_YMMf32_AVX512EVEX.256.NP.0F.W0 10 /r
EVEX.256.NP.0F.W0 11 /r
AVX10.1 or AVX512F + AVX512VL
VMOVUPS ymm {k}{z}, m256 VMOVUPS_YMMf32_MASKmskw_MEMf32_AVX512EVEX.256.NP.0F.W0 10 /rAVX10.1 or AVX512F + AVX512VL
VMOVUPS m256 {k}, ymm VMOVUPS_MEMf32_MASKmskw_YMMf32_AVX512EVEX.256.NP.0F.W0 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 single is copied where its bit of k1 is 1; elsewhere merging keeps the old element, and zeroing writes 0.VMOVUPS xmm, xmm/m128 VMOVUPS ymm, ymm/m256 VMOVUPS xmm {k}{z}, xmm/m128 VMOVUPS ymm {k}{z}, ymm/m256 VMOVUPS zmm {k}{z}, zmm/m512

merging, {k1}

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

zeroing, {k1}{z}

VMOVUPS 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.VMOVUPS m128, xmm VMOVUPS m256, ymm VMOVUPS m128 {k}, xmm VMOVUPS m256 {k}, ymm VMOVUPS m512 {k}, zmm
VMOVUPS 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.

VMOVUPS xmm, xmm/m128 VMOVUPS ymm, ymm/m256 VMOVUPS xmm {k}{z}, xmm/m128 VMOVUPS ymm {k}{z}, ymm/m256 VMOVUPS 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.

VMOVUPS m128, xmm VMOVUPS m256, ymm VMOVUPS m128 {k}, xmm VMOVUPS m256 {k}, ymm VMOVUPS 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
VMOVUPS xmm, xmm/m128 VMOVUPS ymm, ymm/m256
xmm, ymmexplicitwrite
xmm/m128, ymm/m256explicitread
VMOVUPS xmm/m128, xmm VMOVUPS ymm/m256, ymm
xmm/m128, ymm/m256explicitwrite
xmm, ymmexplicitread
VMOVUPS xmm {k}{z}, xmm/m128 VMOVUPS ymm {k}{z}, ymm/m256 VMOVUPS zmm {k}{z}, zmm/m512
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm/m128, ymm/m256, zmm/m512explicitread
VMOVUPS m128 {k}, xmm VMOVUPS m256 {k}, ymm VMOVUPS 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 VMOVUPS, 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_pbh __m128bh _mm_loadu_pbh(const void *__p)

VMOVUPS xmm, m128 VEX.128 -mavx10.2

_mm_loadu_ph __m128h _mm_loadu_ph(const void *__p)

VMOVUPS xmm, m128 VEX.128 -mavx512fp16

_mm_loadu_ps __m128 _mm_loadu_ps(const float *__p)

VMOVUPS xmm, m128 VEX.128 -mavxwith AVX enabled

_mm_storeu_pbh void _mm_storeu_pbh(void *__P, __m128bh __A)

VMOVUPS m128, xmm VEX.128 -mavx10.2

_mm_storeu_ph void _mm_storeu_ph(void *__P, __m128h __A)

VMOVUPS m128, xmm VEX.128 -mavx512fp16

_mm_storeu_ps void _mm_storeu_ps(float *__p, __m128 __a)

VMOVUPS m128, xmm VEX.128 -mavxwith AVX enabled

_mm_storeu_si128 void _mm_storeu_si128(__m128i_u *__p, __m128i __b)

VMOVUPS m128, xmm VEX.128 -mavxwith AVX enabled; Clang emits the equivalent VMOVDQU

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

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

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

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

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

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

_mm256_loadu_pbh __m256bh _mm256_loadu_pbh(const void *__p)

VMOVUPS ymm, m256 VEX.256 -mavx10.2

_mm256_loadu_ph __m256h _mm256_loadu_ph(const void *__p)

VMOVUPS ymm, m256 VEX.256 -mavx512fp16

_mm256_loadu_ps __m256 _mm256_loadu_ps(const float *__p)

VMOVUPS ymm, m256 VEX.256 -mavx

_mm256_storeu_pbh void _mm256_storeu_pbh(void *__P, __m256bh __A)

VMOVUPS m256, ymm VEX.256 -mavx10.2

_mm256_storeu_ph void _mm256_storeu_ph(void *__P, __m256h __A)

VMOVUPS m256, ymm VEX.256 -mavx512fp16

_mm256_storeu_ps void _mm256_storeu_ps(float *__p, __m256 __a)

VMOVUPS m256, ymm VEX.256 -mavx

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

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

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

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

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

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

_mm512_loadu_pbh __m512bh _mm512_loadu_pbh(const void *__p)

VMOVUPS zmm, m512 EVEX.512 -mavx10.2

_mm512_loadu_ph __m512h _mm512_loadu_ph(const void *__p)

VMOVUPS zmm, m512 EVEX.512 -mavx512fp16

_mm512_loadu_ps __m512 _mm512_loadu_ps(const void *__p)

VMOVUPS zmm, m512 EVEX.512 -mavx512f

_mm512_storeu_pbh void _mm512_storeu_pbh(void *__P, __m512bh __A)

VMOVUPS m512, zmm EVEX.512 -mavx10.2

_mm512_storeu_ph void _mm512_storeu_ph(void *__P, __m512h __A)

VMOVUPS m512, zmm EVEX.512 -mavx512fp16

_mm512_storeu_ps void _mm512_storeu_ps(void *__P, __m512 __A)

VMOVUPS m512, zmm EVEX.512 -mavx512f

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

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

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

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

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

VMOVUPS 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-126 (MOVUPS)
  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.