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

VPINSRB is the VEX and EVEX form of PINSRB, whose page covers the immediate, building vectors of bytes and an index known only at run time. The other fifteen bytes come from a separate source register instead of the destination, and bits 128 and up are zeroed, so the result no longer waits for the destination’s old value. Only a 128-bit form exists: VEX.L = 1 or EVEX.L’L other than 0 raises #UD, and in 64-bit mode Intel’s table ignores VEX.W, as it ignores REX.W for PINSRB. The VEX form needs AVX; the EVEX form needs AVX512BW or AVX10.1, and adds only XMM16 to XMM31, with no mask.

On Zen 5, vpinsrb xmm8, xmm15, eax, 0xaf put FDh, the low byte of RAX, into byte 15 and took the other bytes from XMM15, and {evex} vpinsrb xmm0, xmm31, byte ptr [mem], 0x25 put the byte C5h from memory into byte 5 of a copy of XMM31; both cleared bits 511:128.

In compiled code

In our builds at -O2 with -march=x86-64-v3 and x86-64-v4, GCC 14 and Clang 23 compile v[5] = c on 16 unsigned chars to one VPINSRB, from a register or from memory. A byte in the upper half of a ymm register, v[20] = c, is extracted, inserted and put back with VEXTRACTI128, VPINSRB and VINSERTI128 in both compilers (GCC writes the 32X4 forms at -v4).

For _mm_setr_epi8 over 16 bytes loaded from scattered addresses, the two styles of PINSRB’s page carry over at -v3: Clang’s chain of 15 VPINSRBs after a MOVZX and VMOVD, and GCC’s eight pairs joined by unpacks. At -v4 Clang drops the chain: two masked VMOVDQU8 loads pick the bytes out of two 32-byte windows, and VPSHUFB and VPOR put them in order.

AMD’s latency spreadsheet for Zen 5 gives the register form two macro-ops on pipes FP1 or FP2, a latency of 2 cycles and one per cycle, and the memory form one macro-op, two per cycle, in its VEX and EVEX rows alike.

Forms

Every encoding of VPINSRB that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPINSRB xmm, xmm, m8, imm8 VPINSRB_XMMdq_XMMdq_MEMb_IMMbVEX.128.66.0F3A.WIG 20 /r ibAVX
VPINSRB xmm, xmm, r32, imm8 VPINSRB_XMMdq_XMMdq_GPR32d_IMMbVEX.128.66.0F3A.WIG 20 /r ibAVX
VPINSRB xmm, xmm, r32, imm8 VPINSRB_XMMu8_XMMu8_GPR32u8_IMM8_AVX512EVEX.128.66.0F3A.WIG 20 /r ibAVX10.1 or AVX512BW
VPINSRB xmm, xmm, m8, imm8 VPINSRB_XMMu8_XMMu8_MEMu8_IMM8_AVX512EVEX.128.66.0F3A.WIG 20 /r ibAVX10.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, m8, imm8xmm, xmm, r32, imm8xmm, xmm, r32, imm8
Sandy Bridge7 / 0.5p152 / 1p15
Haswell, Broadwell, Skylake6 / 1p52 / 2p5
Skylake-SP6 / 1p52 / 2p52 / 2p5
Ice Lake6 / 0.5p152 / 1p152 / 1p15
Alder Lake8 / 0.5p154 / 1p15
Sapphire Rapids8 / 0.5p154 / 1p154 / 1p15
Lunar Lake7 / 2V2 V35 / 1.33V2 V3 p1 p3 p5
Piledriver6 / 2FPMAL FPU0 FPU112 / 1.5FPMAL FPU0 FPU1
Zen8 / 0.5FPU0 FPU1 FPU2 FPU31 / 0.25FPU0 FPU1 FPU2 FPU3
Zen 28 / 0.33FPU0 FPU1 FPU2 FPU31 / 0.25FPU0 FPU1 FPU2 FPU3
Zen 38 / 1.5FP45 LSU Load2 / 1FP45
Zen 48 / 1.5FP45 LSU Load2 / 1FP451 / 1FP45
Jaguar4 / 1FPU0 FPU1 VALU0 VALU17 / 0.5FPU0 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.

Insert: the byte from r32 replaces byte imm8 of xmm2; the rest of the result comes from xmm2.
VPINSRB with imm8 = 0x05With imm8 = 0x05, result bytes 15 to 0: a15, a14, a13, a12, a11, a10, a9, a8, a7, a6, b0, a4, a3, a2, a1, a0.0123467891011121314155xmm2aa0a1a2a3a4a6a7a8a9a10a11a12a13a14a15b0xmm10r32or m8b

Example: imm8 = 0x05.

With imm8 = 0x05, result bytes 15 to 0: a15, a14, a13, a12, a11, a10, a9, a8, a7, a6, b0, 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.

xmm1.write(xmm2.read())
xmm1.b[imm8 & 15] = src3.b[0]
# xmm1 is zeroed from bit 128 up

Run on AMD Zen 5 (EPYC 9645): 4 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
VPINSRB xmm, xmm, m8, imm8
xmmexplicitwrite
xmmexplicitread
m8explicitread
imm8explicitread
VPINSRB xmm, xmm, r32, imm8
xmmexplicitwrite
xmmexplicitread
r32explicitread
imm8explicitread

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-E9NF

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VPINSRB, 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_insert_epi8 __m128i _mm_insert_epi8(__m128i X, int I, const int N)

VPINSRB xmm, xmm, r32, imm8 VEX.128 -mavxwith AVX enabled

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.

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-305 (PINSRB/PINSRD/PINSRQ)
  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.