Instruction
VPMOVZXBW
Zero-extends packed bytes to words.
VPMOVZXBW widens unsigned bytes to words: each byte of the source
becomes a 16-bit element with a zero high byte. Code does this before
arithmetic that would overflow a byte, such as summing pixels or
counting, and compilers emit it for a loop that adds uint8_t values
into uint16_t ones. The result is twice as wide as the source, so the
source is half a register: eight bytes for an XMM result, sixteen for
YMM, thirty-two for ZMM, from a register or from memory at any
alignment.
In order, across the whole register
Before SSE4.1 the same widening took an unpack with a zeroed register:
PUNPCKLBW for the low eight bytes and
PUNPCKHBW for the high ones. In a YMM register the
two differ. VPUNPCKLBW works within each 128-bit
lane and takes bytes 0 to 7 and 16 to 23, while vpmovzxbw ymm, xmm
takes bytes 0 to 15 of an XMM register in order and spreads them over
both lanes. The way back is not symmetric: VPACKUSWB
packs within lanes and needs a VPERMQ to restore the
order, while AVX-512’s VPMOVWB narrows in order, by
truncation.
What GCC 14 and Clang 23 make of a widening loop at -O2:
- With the x86-64 baseline (SSE2 only), unpacks against a zeroed register.
- With SSE4.1 or AVX2, this instruction. GCC loads a full vector, widens its low half, and moves the high half down with PSRLDQ or VEXTRACTI128 to widen it too; Clang widens straight from memory, sixteen bytes at a time for a YMM result.
- For x86-64-v4, GCC uses the ZMM form, while Clang stays with YMM registers.
Both compilers also replace _mm_unpacklo_epi8(x, zero) with PMOVZXBW
once SSE4.1 is enabled, as the two give the same result.
Intel’s optimization guide notes that in the Crestmont microarchitecture the 256-bit form with a memory source takes two micro-ops that depend on each other, while the register form handles its two halves in parallel (Section 4.1.9.3).
The EVEX forms add a mask with one bit per word. PMOVZXBW is the legacy SSE4.1 form; VPMOVSXBW sign-extends, and VPMOVZXBD and VPMOVZXWD widen to other sizes.
In the optimization guide
What the optimization guide says about VPMOVZXBW, a line per claim. Each links to the claim in the guide, with its sources and where they differ.
Crestmont and Gracemont
- Vectors and AVX2: The 256-bit forms that widen or insert data loaded from memory take two dependent micro-ops.
Forms
| Instruction | Encoding | Requires |
|---|---|---|
VPMOVZXBW xmm, xmm
VPMOVZXBW_XMMdq_XMMq | VEX.128.66.0F38.WIG 30 /r | AVX |
VPMOVZXBW xmm, m64
VPMOVZXBW_XMMdq_MEMq | VEX.128.66.0F38.WIG 30 /r | AVX |
VPMOVZXBW ymm, xmm
VPMOVZXBW_YMMqq_XMMdq | VEX.256.66.0F38.WIG 30 /r | AVX2 |
VPMOVZXBW ymm, m128
VPMOVZXBW_YMMqq_MEMdq | VEX.256.66.0F38.WIG 30 /r | AVX2 |
VPMOVZXBW xmm {k}{z}, xmm
VPMOVZXBW_XMMi16_MASKmskw_XMMi8_AVX512 | EVEX.128.66.0F38.WIG 30 /r | AVX10.1 or AVX512BW + AVX512VL |
VPMOVZXBW xmm {k}{z}, m64
VPMOVZXBW_XMMi16_MASKmskw_MEMi8_AVX512 | EVEX.128.66.0F38.WIG 30 /r | AVX10.1 or AVX512BW + AVX512VL |
VPMOVZXBW ymm {k}{z}, xmm
VPMOVZXBW_YMMi16_MASKmskw_XMMi8_AVX512 | EVEX.256.66.0F38.WIG 30 /r | AVX10.1 or AVX512BW + AVX512VL |
VPMOVZXBW ymm {k}{z}, m128
VPMOVZXBW_YMMi16_MASKmskw_MEMi8_AVX512 | EVEX.256.66.0F38.WIG 30 /r | AVX10.1 or AVX512BW + AVX512VL |
VPMOVZXBW zmm {k}{z}, ymm
VPMOVZXBW_ZMMi16_MASKmskw_YMMi8_AVX512 | EVEX.512.66.0F38.WIG 30 /r | AVX10.1 or AVX512BW |
VPMOVZXBW zmm {k}{z}, m256
VPMOVZXBW_ZMMi16_MASKmskw_MEMi8_AVX512 | EVEX.512.66.0F38.WIG 30 /r | AVX10.1 or AVX512BW |
Latency and throughput
| Model | xmm, xmmxmm {k}{z}, xmmno mask | xmm, m64 | ymm, xmmymm {k}{z}, xmmno mask | ymm, m128ymm {k}{z}, m128no maskzmm {k}{z}, m256no mask | xmm {k}{z}, xmmwith a mask, zeroing | xmm {k}{z}, m64no mask | xmm {k}{z}, m64with a mask, zeroing | ymm {k}{z}, xmmwith a mask, zeroing | ymm {k}{z}, m128with a mask, zeroingzmm {k}{z}, m256with a mask, zeroing | zmm {k}{z}, ymmno mask | zmm {k}{z}, ymmwith a mask, zeroing |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Sandy Bridge | 1 / 0.5p15 | 7 / 0.5p15 | |||||||||
| Haswell, Skylake | 1 / 1p5 | 6 / 1p5 | 3 / 1p5 | 10 / 1p5 | |||||||
| Broadwell | 1 / 1p5 | 6 / 1p5 | 3 / 1p5 | 9 / 1p5 | |||||||
| Skylake-SP | 1 / 1p5 | 6 / 1p5 | 3 / 1p5 | 10 / 1p5 | 1 / 1p5 | 7 / 1p5 | 7 / 1p5 | 3 / 1p5 | 10 / 1p5 | 3 / 1p5 | 3 / 1p5 |
| Ice Lake | 1 / 0.5p15 | 7 / 0.5p15 | 3 / 1p5 | 10 / 1p5 | 1 / 0.5p15 | 7 / 0.5p15 | 7 / 0.5p15 | 3 / 1p5 | 10 / 1p5 | 3 / 1p5 | 3 / 1p5 |
| Alder Lake | 1 / 0.5p15 | 8 / 0.5p15 | 3 / 1p5 | 11 / 1p5 | |||||||
| Sapphire Rapids | 1 / 0.5p15 | 8 / 0.5p15 | 3 / 1p5 | 11 / 1p5 | 3 / 0.5p15 | 8 / 0.5p15 | 11 / 0.5p15 | 5 / 1p5 | 13 / 1p5 | 3 / 1p5 | 5 / 1p5 |
| Lunar Lake | 1 / 0.5V2 V3 | 8 / 0.5V2 V3 | 3 / 0.5V2 V3 | 10 / 2.33V2 V3 | |||||||
| Piledriver | 2 / 1FPU1 FPXBR | 7 / 1.5FPU1 FPXBR | |||||||||
| Zen | 1 / 0.5FPU1 FPU2 | 8 / 0.5FPU1 FPU2 | 1 / 2FPU1 FPU2 | 8 / 2FPU1 FPU2 | |||||||
| Zen 2 | 1 / 0.5FPU1 FPU2 | 8 / 0.5FPU1 FPU2 | 4 / 0.5FPU1 FPU2 | 8 / 0.5FPU1 FPU2 | |||||||
| Zen 3 | 1 / 0.5FP1 FP2 | 8 / 0.5FP1 FP2 | 4 / 1.5FP1 FP2 | 11 / 1.5FP1 FP2 | |||||||
| Zen 4 | 2 / 0.5FP1 FP2 | 8 / 0.5FP1 FP2 | 2 / 0.5FP1 FP2 | 11 / 1.5FP1 FP2 | 2 / 0.5FP1 FP2 | 8 / 0.5FP1 FP2 | 8 / 0.5FP1 FP2 | 2 / 0.5FP1 FP2 | 11 / 1.5FP1 FP2 | 4 / 1FP1 FP2 | 4 / 1FP1 FP2 |
| Jaguar | 1 / 0.5FPU0 FPU1 VALU0 VALU1 | 6 / 1FPU0 FPU1 VALU0 VALU1 | |||||||||
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.
The grey upper half of each word is the extension: zeros. Shown for the ymm form; the xmm and zmm forms work the same on 8 and 32 bytes. The EVEX forms write under a mask: where its bit is 0, the element keeps its old value, or zeroes it with {z}.
Result words 15 to 0: a15, unchanged (bit 14 of k1 is 0), a13, a12, a11, a10, a9, a8, a7, a6, 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.
for i in range(VL // 16):
if k1[i]: # 1 without a write mask
zmm1.w[i] = src2.b[i] # zero-extended
elif zeroing:
zmm1.w[i] = 0
# else: zmm1.w[i] keeps its value
# zmm1 is zeroed from bit VL upRun on AMD Zen 5 (EPYC 9645): 10 cases.
Operands
| Operand | Kind | Action |
|---|---|---|
VPMOVZXBW xmm, xmm/m64 VPMOVZXBW ymm, xmm/m128 | ||
xmm, ymm | explicit | write |
xmm/m64/128 | explicit | read |
VPMOVZXBW xmm {k}{z}, xmm/m64 VPMOVZXBW ymm {k}{z}, xmm/m128 VPMOVZXBW zmm {k}{z}, ymm/m256 | ||
xmm, ymm, zmm | explicit | write (masked) |
{k} | explicit | read (write mask) |
xmm/m64, xmm/m128, ymm/m256 | 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 VPMOVZXBW, 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_cvtepu8_epi16
__m128i _mm_cvtepu8_epi16(__m128i __V) |
|
_mm_mask_cvtepu8_epi16
__m128i _mm_mask_cvtepu8_epi16(__m128i __W, __mmask8 __U, __m128i __A) |
|
_mm_maskz_cvtepu8_epi16
__m128i _mm_maskz_cvtepu8_epi16(__mmask8 __U, __m128i __A) |
|
_mm256_cvtepu8_epi16
__m256i _mm256_cvtepu8_epi16(__m128i __V) |
|
_mm256_mask_cvtepu8_epi16
__m256i _mm256_mask_cvtepu8_epi16(__m256i __W, __mmask16 __U, __m128i __A) |
|
_mm256_maskz_cvtepu8_epi16
__m256i _mm256_maskz_cvtepu8_epi16(__mmask16 __U, __m128i __A) |
|
_mm512_cvtepu8_epi16
__m512i _mm512_cvtepu8_epi16(__m256i __A) |
|
_mm512_mask_cvtepu8_epi16
__m512i _mm512_mask_cvtepu8_epi16(__m512i __W, __mmask32 __U, __m256i __A) |
|
_mm512_maskz_cvtepu8_epi16
__m512i _mm512_maskz_cvtepu8_epi16(__mmask32 __U, __m256i __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.
More AVX instructions
- VPMAXSD
- VPMAXSW
- VPMAXUB
- VPMAXUD
- VPMAXUW
- VPMINSB
- VPMINSD
- VPMINSW
- VPMINUB
- VPMINUD
- VPMINUW
- VPMOVMSKB
- VPMOVSXBD
- VPMOVSXBQ
- VPMOVSXBW
- VPMOVSXDQ
- VPMOVSXWD
- VPMOVSXWQ
- VPMOVZXBD
- VPMOVZXBQ
- VPMOVZXDQ
- VPMOVZXWD
- VPMOVZXWQ
- VPMULDQ
- VPMULHRSW
- VPMULHUW
- VPMULHW
- VPMULLD
- VPMULLW
- VPMULUDQ
- VPOR
- VPSADBW
- VPSHUFB
- VPSHUFD
- VPSHUFHW
- VPSHUFLW
- VPSIGNB
- VPSIGND
- VPSIGNW
- VPSLLD
More AVX2 instructions
- VPMAXSD
- VPMAXSW
- VPMAXUB
- VPMAXUD
- VPMAXUW
- VPMINSB
- VPMINSD
- VPMINSW
- VPMINUB
- VPMINUD
- VPMINUW
- VPMOVMSKB
- VPMOVSXBD
- VPMOVSXBQ
- VPMOVSXBW
- VPMOVSXDQ
- VPMOVSXWD
- VPMOVSXWQ
- VPMOVZXBD
- VPMOVZXBQ
- VPMOVZXDQ
- VPMOVZXWD
- VPMOVZXWQ
- VPMULDQ
- VPMULHRSW
- VPMULHUW
- VPMULHW
- VPMULLD
- VPMULLW
- VPMULUDQ
- VPOR
- VPSADBW
- VPSHUFB
- VPSHUFD
- VPSHUFHW
- VPSHUFLW
- VPSIGNB
- VPSIGND
- VPSIGNW
- VPSLLD
More AVX10.1 instructions
- VPMOVSQB
- VPMOVSQD
- VPMOVSQW
- VPMOVSWB
- VPMOVSXBD
- VPMOVSXBQ
- VPMOVSXBW
- VPMOVSXDQ
- VPMOVSXWD
- VPMOVSXWQ
- VPMOVUSDB
- VPMOVUSDW
- VPMOVUSQB
- VPMOVUSQD
- VPMOVUSQW
- VPMOVUSWB
- VPMOVW2M
- VPMOVWB
- VPMOVZXBD
- VPMOVZXBQ
- VPMOVZXDQ
- VPMOVZXWD
- VPMOVZXWQ
- VPMULDQ
- VPMULHRSW
- VPMULHUW
- VPMULHW
- VPMULLD
- VPMULLQ
- VPMULLW
- VPMULTISHIFTQB
- VPMULUDQ
- VPOPCNTB
- VPOPCNTD
- VPOPCNTQ
- VPOPCNTW
- VPORD
- VPORQ
- VPROLD
- VPROLQ
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-362 (PMOVZX)
- 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)
- Intel 64 and IA-32 Architectures Optimization Reference Manual, Volume 1 (248966-051, October 2026)
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.