Extensions
Forms
10 (4 VEX, 6 EVEX)
Data
Intel XED v2026.08.23

VPMOVSXBW is the VEX and EVEX form of SSE4.1’s PMOVSXBW, whose page covers the sign extension of bytes to words. The source is half the width of the result: 8 bytes for an xmm destination (AVX), 16 for ymm (AVX2) and 32 for zmm (AVX512BW; the EVEX xmm and ymm forms also need AVX512VL, or AVX10.1), from memory at any alignment. The bytes stay in order across lanes: on Zen 5, vpmovsxbw ymm12, xmm6 widened bytes 8 to 15 of XMM6, 80h, 7Fh, 80h, 7Fh, 00h, 0Fh, 10h and 08h, into the upper 128-bit lane as FF80h, 007Fh, FF80h, 007Fh, 0000h, 000Fh, 0010h and 0008h, and cleared bits 511:256 of ZMM12, which PMOVSXBW would keep.

Masks

The EVEX forms add a write mask per word. The recorded vpmovsxbw zmm1{k2}, ymm2, with C9h in the low byte of k2, wrote words 0, 3, 6 and 7, FF80h, 0001h, 0001h and FFFFh from bytes 80h, 01h, 01h and FFh, and merged the others: words 1 and 2 kept 887Bh and A295h. vpmovsxbw xmm24{k6}{z}, qword ptr [mem] zeroed instead: with A4h in k6, only words 2, 5 and 7 were written, and every other bit of ZMM24 up to 511 was cleared.

In compiled code

In our builds at -O2 over fixed-size int8_t arrays copied into int16_t ones, or multiplied pairwise into them with VPMULLW, Clang 23 widens 16 bytes at a time straight from memory with -march=x86-64-v3 and with x86-64-v4, on ymm registers either way. GCC 14 loads 32 bytes, widens the low half, moves the high half down with VEXTRACTI128 and widens it too; with -v4 it does the same at twice the width, each ymm half into a zmm register. Into int32_t, Clang uses VPMOVSXBD while GCC goes through words, VPMOVSXBW and then VPMOVSXWD.

AMD’s latency spreadsheet for Zen 5 gives the VEX row and the EVEX xmm and ymm row a latency of 2 cycles and the zmm row 4, one macro-op and two per cycle each. VPMOVZXBW fills with zeros instead.

In the optimization guide

What the optimization guide says about VPMOVSXBW, 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

Every encoding of VPMOVSXBW that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPMOVSXBW xmm, xmm VPMOVSXBW_XMMdq_XMMqVEX.128.66.0F38.WIG 20 /rAVX
VPMOVSXBW xmm, m64 VPMOVSXBW_XMMdq_MEMqVEX.128.66.0F38.WIG 20 /rAVX
VPMOVSXBW ymm, xmm VPMOVSXBW_YMMqq_XMMdqVEX.256.66.0F38.WIG 20 /rAVX2
VPMOVSXBW ymm, m128 VPMOVSXBW_YMMqq_MEMdqVEX.256.66.0F38.WIG 20 /rAVX2
VPMOVSXBW xmm {k}{z}, xmm VPMOVSXBW_XMMi16_MASKmskw_XMMi8_AVX512EVEX.128.66.0F38.WIG 20 /rAVX10.1 or AVX512BW + AVX512VL
VPMOVSXBW xmm {k}{z}, m64 VPMOVSXBW_XMMi16_MASKmskw_MEMi8_AVX512EVEX.128.66.0F38.WIG 20 /rAVX10.1 or AVX512BW + AVX512VL
VPMOVSXBW ymm {k}{z}, xmm VPMOVSXBW_YMMi16_MASKmskw_XMMi8_AVX512EVEX.256.66.0F38.WIG 20 /rAVX10.1 or AVX512BW + AVX512VL
VPMOVSXBW ymm {k}{z}, m128 VPMOVSXBW_YMMi16_MASKmskw_MEMi8_AVX512EVEX.256.66.0F38.WIG 20 /rAVX10.1 or AVX512BW + AVX512VL
VPMOVSXBW zmm {k}{z}, ymm VPMOVSXBW_ZMMi16_MASKmskw_YMMi8_AVX512EVEX.512.66.0F38.WIG 20 /rAVX10.1 or AVX512BW
VPMOVSXBW zmm {k}{z}, m256 VPMOVSXBW_ZMMi16_MASKmskw_MEMi8_AVX512EVEX.512.66.0F38.WIG 20 /rAVX10.1 or AVX512BW

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, xmm
xmm {k}{z}, xmmno mask
xmm, m64ymm, xmm
ymm {k}{z}, xmmno mask
ymm, m128xmm {k}{z}, xmmwith a mask, zeroingxmm {k}{z}, m64no maskxmm {k}{z}, m64with a mask, zeroingymm {k}{z}, xmmwith a mask, zeroingymm {k}{z}, m128no mask
zmm {k}{z}, m256no mask
ymm {k}{z}, m128with a mask, zeroing
zmm {k}{z}, m256with a mask, zeroing
zmm {k}{z}, ymmno maskzmm {k}{z}, ymmwith a mask, zeroing
Sandy Bridge1 / 0.5p157 / 0.5p15
Haswell, Skylake1 / 1p56 / 1p53 / 1p59 / 1p5
Broadwell1 / 1p56 / 1p53 / 1p58 / 1p5
Skylake-SP1 / 1p56 / 1p53 / 1p59 / 1p51 / 1p57 / 1p57 / 1p53 / 1p510 / 1p510 / 1p53 / 1p53 / 1p5
Ice Lake1 / 0.5p157 / 0.5p153 / 1p59 / 1p51 / 0.5p157 / 0.5p157 / 0.5p153 / 1p510 / 1p510 / 1p53 / 1p53 / 1p5
Alder Lake1 / 0.5p158 / 0.5p153 / 1p511 / 1p5
Sapphire Rapids1 / 0.5p158 / 0.5p153 / 1p511 / 1p53 / 0.5p158 / 0.5p1511 / 0.5p155 / 1p511 / 1p513 / 1p53 / 1p55 / 1p5
Lunar Lake1 / 0.5V2 V38 / 0.5V2 V33 / 0.5V2 V310 / 2.33V2 V3
Piledriver2 / 1FPU1 FPXBR7 / 1.5FPU1 FPXBR
Zen1 / 0.5FPU1 FPU28 / 0.5FPU1 FPU21 / 2FPU1 FPU28 / 2FPU1 FPU2
Zen 21 / 0.5FPU1 FPU28 / 0.5FPU1 FPU24 / 0.5FPU1 FPU28 / 0.5FPU1 FPU2
Zen 31 / 0.5FP1 FP28 / 0.5FP1 FP24 / 1.5FP1 FP211 / 1.5FP1 FP2
Zen 42 / 0.5FP1 FP28 / 0.5FP1 FP22 / 0.5FP1 FP211 / 1.5FP1 FP22 / 0.5FP1 FP28 / 0.5FP1 FP28 / 0.5FP1 FP22 / 0.5FP1 FP211 / 1.5FP1 FP211 / 1.5FP1 FP24 / 1FP1 FP24 / 1FP1 FP2
Jaguar1 / 0.5FPU0 FPU1 VALU0 VALU16 / 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.

Widen: each byte becomes a word, sign-extended, in the same order.
VPMOVSXBW: each element widenedResult 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.0123456789101112131415xmm2or m128a1111111111111110k1a0a1a2a3a4a5a6a7a8a9a10a11a12a13a15ymm1

The grey upper half of each word is the extension: copies of the sign bit. 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.sb[i]  # sign-extended
    elif zeroing:
        zmm1.w[i] = 0
    # else: zmm1.w[i] keeps its value
# zmm1 is zeroed from bit VL up

Run on AMD Zen 5 (EPYC 9645): 10 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
VPMOVSXBW xmm, xmm/m64 VPMOVSXBW ymm, xmm/m128
xmm, ymmexplicitwrite
xmm/m64/128explicitread
VPMOVSXBW xmm {k}{z}, xmm/m64 VPMOVSXBW ymm {k}{z}, xmm/m128 VPMOVSXBW zmm {k}{z}, ymm/m256
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm/m64, xmm/m128, ymm/m256explicitread

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 VPMOVSXBW, 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_cvtepi8_epi16 __m128i _mm_cvtepi8_epi16(__m128i __V)

VPMOVSXBW xmm, xmm VEX.128 -mavxwith AVX enabled

_mm_mask_cvtepi8_epi16 __m128i _mm_mask_cvtepi8_epi16(__m128i __W, __mmask8 __U, __m128i __A)

VPMOVSXBW xmm {k}, xmm EVEX.128 -mavx512vl -mavx512bw

_mm_maskz_cvtepi8_epi16 __m128i _mm_maskz_cvtepi8_epi16(__mmask8 __U, __m128i __A)

VPMOVSXBW xmm {k}{z}, xmm EVEX.128 -mavx512vl -mavx512bw

_mm256_cvtepi8_epi16 __m256i _mm256_cvtepi8_epi16(__m128i __V)

VPMOVSXBW ymm, xmm VEX.256 -mavx2

_mm256_mask_cvtepi8_epi16 __m256i _mm256_mask_cvtepi8_epi16(__m256i __W, __mmask16 __U, __m128i __A)

VPMOVSXBW ymm {k}, xmm EVEX.256 -mavx512vl -mavx512bw

_mm256_maskz_cvtepi8_epi16 __m256i _mm256_maskz_cvtepi8_epi16(__mmask16 __U, __m128i __A)

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

_mm512_cvtepi8_epi16 __m512i _mm512_cvtepi8_epi16(__m256i __A)

VPMOVSXBW zmm, ymm EVEX.512 -mavx512bw

_mm512_mask_cvtepi8_epi16 __m512i _mm512_mask_cvtepi8_epi16(__m512i __W, __mmask32 __U, __m256i __A)

VPMOVSXBW zmm {k}, ymm EVEX.512 -mavx512bw

_mm512_maskz_cvtepi8_epi16 __m512i _mm512_maskz_cvtepi8_epi16(__mmask32 __U, __m256i __A)

VPMOVSXBW zmm {k}{z}, ymm EVEX.512 -mavx512bw

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
AVX2

AVX2
CPUID.(EAX=07H,ECX=0):EBX[5] AVX2

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, Zen, Zen+, Zen 2, Zen 3, Zen 4, Zen 5, Zen 6
AVX512BW_128

AVX10.1
CPUID.(EAX=07H,ECX=1):EDX[19] AVX10
CPUID.(EAX=24H,ECX=0):EBX[7:0] ≥ 1 AVX10 version

or

AVX512BW + AVX512VL
CPUID.(EAX=07H,ECX=0):EBX[30] AVX512BW
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
AVX512BW_256
Same as AVX512BW_128Same as AVX512BW_128
AVX512BW_512

AVX10.1
CPUID.(EAX=07H,ECX=1):EDX[19] AVX10
CPUID.(EAX=24H,ECX=0):EBX[7:0] ≥ 1 AVX10 version

or

AVX512BW
CPUID.(EAX=07H,ECX=0):EBX[30] AVX512BW

Same as AVX512BW_128

More AVX instructions

All 253 AVX instructions

More AVX2 instructions

All 138 AVX2 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-352 (PMOVSX)
  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.