Extensions
Forms
6 (6 EVEX)
Data
Intel XED v2026.08.23

VPMOVUSQW narrows unsigned quadwords to words, clamping each to 65535: 8 quadwords of a ZMM register become 8 words in an XMM register or in memory, 4 come from a YMM register and 2 from an XMM one. The source is unsigned, so a negative int64_t becomes FFFFh rather than 0, as VPMOVUSDB’s page explains. It is the saturating form of VPMOVQW, which keeps the low word, and the quadword form of VPMOVUSDW; VPMOVSQW clamps signed values. It is part of AVX-512F.

Recorded on Zen 5

  • Unsigned limits. {evex} vpmovusqw qword ptr [mem], ymm7 turned 7FFFFFFFFFFFFFFFh into FFFFh and kept 0055h, 0000h and 0001h.
  • Above the signed range. vpmovusqw xmm17{k6}, zmm30, with A4h in the low byte of K6, wrote words 2, 5 and 7: 8001h stayed 8001h, where a signed clamp gives 7FFFh, and FFFFh and 8000000000000000h gave FFFFh. The other words kept XMM17’s old values, and the register was cleared from bit 128 up.
  • Masked store. vpmovusqw xmmword ptr [mem]{k3}, zmm17, with EBh in the low byte of K3, wrote six words, FFFFh for 7FFFFFFFFFFFFFFFh and 8000h and 8001h unchanged among them, and left words 2 and 4 of memory as they were.

In compiled code

For d[i] = x > 65535 ? 65535 : x over uint64_t and uint16_t arrays, Clang 23 at -O2 with -march=x86-64-v4 stores each 4 results with vpmovusqw qword ptr [rdx + 2*rax], ymm0. GCC 14 clamps with VPMINUQ against 65535 and joins the low words of four ZMM registers with VPERMT2D and VPERMT2W. Both compile _mm512_cvtusepi64_epi16 to vpmovusqw xmm0, zmm0.

AMD’s Zen 5 latency spreadsheet gives the register forms one macro-op on pipe FP1 or FP2, with 2, 4 and 5 cycles from XMM, YMM and ZMM sources, and the memory forms two macro-ops, with 3, 5 and 6.

Forms

Every encoding of VPMOVUSQW that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPMOVUSQW xmm {k}{z}, zmm VPMOVUSQW_XMMu16_MASKmskw_ZMMu64_AVX512EVEX.512.F3.0F38.W0 14 /rAVX10.1 or AVX512F
VPMOVUSQW m128 {k}, zmm VPMOVUSQW_MEMu16_MASKmskw_ZMMu64_AVX512EVEX.512.F3.0F38.W0 14 /rAVX10.1 or AVX512F
VPMOVUSQW xmm {k}{z}, xmm VPMOVUSQW_XMMu16_MASKmskw_XMMu64_AVX512EVEX.128.F3.0F38.W0 14 /rAVX10.1 or AVX512F + AVX512VL
VPMOVUSQW m32 {k}, xmm VPMOVUSQW_MEMu16_MASKmskw_XMMu64_AVX512EVEX.128.F3.0F38.W0 14 /rAVX10.1 or AVX512F + AVX512VL
VPMOVUSQW xmm {k}{z}, ymm VPMOVUSQW_XMMu16_MASKmskw_YMMu64_AVX512EVEX.256.F3.0F38.W0 14 /rAVX10.1 or AVX512F + AVX512VL
VPMOVUSQW m64 {k}, ymm VPMOVUSQW_MEMu16_MASKmskw_YMMu64_AVX512EVEX.256.F3.0F38.W0 14 /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 {k}{z}, zmmno maskxmm {k}{z}, zmmwith a mask, zeroingm128 {k}, zmmno maskm128 {k}, zmmwith a maskxmm {k}{z}, xmmno maskxmm {k}{z}, xmmwith a mask, zeroing
xmm {k}{z}, ymmno mask
m32 {k}, xmmno mask
m64 {k}, ymmno mask
m32 {k}, xmmwith a maskxmm {k}{z}, ymmwith a mask, zeroingm64 {k}, ymmwith a mask
Skylake-SP, Ice Lake3 / 1p53 / 1p55 / 2p55 / 2p53 / 1p53 / 1p55 / 2p55 / 2p53 / 1p55 / 2p5
Sapphire Rapids4 / 2p56 / 2p512 / 2p515 / 2p52 / 1p154 / 1p1512 / 1p1513 / 1p156 / 1p1515 / 1p15
Zen 45 / 1FP1 FP25 / 1FP1 FP211 / 1.5FP1 FP211 / 1.5FP1 FP22 / 0.5FP1 FP22 / 0.5FP1 FP211 / 1.5FP1 FP211 / 1.5FP1 FP22 / 0.5FP1 FP211 / 1.5FP1 FP2

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.

Narrow: each quadword becomes a word, in the same order, at the low end of the result.Register forms
VPMOVUSQW: each element narrowedResult words 7 to 0: a7, unchanged (bit 6 of k1 is 0), a5, a4, a3, a2, a1, a0.01234567zmm2a11111110k1a0a1a2a3a4a5a7xmm1

Shown for the zmm form; the xmm and ymm forms work the same on 2 and 4 quadwords. The forms write under a mask: where its bit is 0, the element keeps its old value, or zeroes it with {z}.

Result words 7 to 0: a7, unchanged (bit 6 of k1 is 0), a5, a4, a3, a2, a1, a0.

Narrow: each quadword becomes a word, in the same order, at the low end of the result.Memory forms
VPMOVUSQW: each element narrowedResult words 7 to 0: a7, unchanged (bit 6 of k1 is 0), a5, a4, a3, a2, a1, a0.m128

A memory destination receives the words alone. Shown for the zmm form; the xmm and ymm forms work the same on 2 and 4 quadwords. The forms write under a mask: where its bit is 0, the element keeps its old value.

Result words 7 to 0: a7, unchanged (bit 6 of k1 is 0), a5, a4, a3, a2, a1, a0.

Operation

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

Register forms
for i in range(VL // 64):
    if k1[i]:
        xmm1.w[i] = usat(zmm2.q[i], 16)
    elif zeroing:
        xmm1.w[i] = 0
    # else: xmm1.w[i] keeps its value
for i in range(VL // 64, 8):
    xmm1.w[i] = 0
# xmm1 is zeroed from bit 128 up

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

Memory forms
for i in range(VL // 64):
    if k1[i]:
        mem.w[i] = usat(zmm2.q[i], 16)
    # else: mem.w[i] is not written

Run on AMD Zen 5 (EPYC 9645): 3 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
VPMOVUSQW xmm/m128 {k}{z}, zmm VPMOVUSQW xmm/m32 {k}{z}, xmm VPMOVUSQW xmm/m64 {k}{z}, ymm
xmm/m32/64/128explicitwrite (masked)
{k}explicitread (write mask)
zmm, xmm, ymmexplicitread

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.

Register forms
AVX512-E6NF
Memory forms
AVX512-E6

Attributes

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

All forms
write masking
Memory forms
memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VPMOVUSQW, 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_cvtusepi64_epi16 __m128i _mm_cvtusepi64_epi16(__m128i __A)

VPMOVUSQW xmm, xmm EVEX.128 -mavx512vl

_mm_mask_cvtusepi64_epi16 __m128i _mm_mask_cvtusepi64_epi16(__m128i __O, __mmask8 __M, __m128i __A)

VPMOVUSQW xmm {k}, xmm EVEX.128 -mavx512vl

_mm_mask_cvtusepi64_storeu_epi16 void _mm_mask_cvtusepi64_storeu_epi16(void *__P, __mmask8 __M, __m128i __A)

VPMOVUSQW m32 {k}, xmm EVEX.128 -mavx512vl

_mm_maskz_cvtusepi64_epi16 __m128i _mm_maskz_cvtusepi64_epi16(__mmask8 __M, __m128i __A)

VPMOVUSQW xmm {k}{z}, xmm EVEX.128 -mavx512vl

_mm256_cvtusepi64_epi16 __m128i _mm256_cvtusepi64_epi16(__m256i __A)

VPMOVUSQW xmm, ymm EVEX.256 -mavx512vl

_mm256_mask_cvtusepi64_epi16 __m128i _mm256_mask_cvtusepi64_epi16(__m128i __O, __mmask8 __M, __m256i __A)

VPMOVUSQW xmm {k}, ymm EVEX.256 -mavx512vl

_mm256_mask_cvtusepi64_storeu_epi16 void _mm256_mask_cvtusepi64_storeu_epi16(void *__P, __mmask8 __M, __m256i __A)

VPMOVUSQW m64 {k}, ymm EVEX.256 -mavx512vl

_mm256_maskz_cvtusepi64_epi16 __m128i _mm256_maskz_cvtusepi64_epi16(__mmask8 __M, __m256i __A)

VPMOVUSQW xmm {k}{z}, ymm EVEX.256 -mavx512vl

_mm512_cvtusepi64_epi16 __m128i _mm512_cvtusepi64_epi16(__m512i __A)

VPMOVUSQW xmm, zmm EVEX.512 -mavx512f

_mm512_mask_cvtusepi64_epi16 __m128i _mm512_mask_cvtusepi64_epi16(__m128i __O, __mmask8 __M, __m512i __A)

VPMOVUSQW xmm {k}, zmm EVEX.512 -mavx512f

_mm512_mask_cvtusepi64_storeu_epi16 void _mm512_mask_cvtusepi64_storeu_epi16(void *__P, __mmask8 __M, __m512i __A)

VPMOVUSQW m128 {k}, zmm EVEX.512 -mavx512f

_mm512_maskz_cvtusepi64_epi16 __m128i _mm512_maskz_cvtusepi64_epi16(__mmask8 __M, __m512i __A)

VPMOVUSQW xmm {k}{z}, zmm 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
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 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 Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
  6. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2C, page 5-596 (VPMOVQW/VPMOVSQW/VPMOVUSQW)
  7. 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.