Instruction
VPINSRB
Inserts a byte from a register or memory into an XMM register at the position an immediate gives.
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
| Instruction | Encoding | Requires |
|---|---|---|
VPINSRB xmm, xmm, m8, imm8
VPINSRB_XMMdq_XMMdq_MEMb_IMMb | VEX.128.66.0F3A.WIG 20 /r ib | AVX |
VPINSRB xmm, xmm, r32, imm8
VPINSRB_XMMdq_XMMdq_GPR32d_IMMb | VEX.128.66.0F3A.WIG 20 /r ib | AVX |
VPINSRB xmm, xmm, r32, imm8
VPINSRB_XMMu8_XMMu8_GPR32u8_IMM8_AVX512 | EVEX.128.66.0F3A.WIG 20 /r ib | AVX10.1 or AVX512BW |
VPINSRB xmm, xmm, m8, imm8
VPINSRB_XMMu8_XMMu8_MEMu8_IMM8_AVX512 | EVEX.128.66.0F3A.WIG 20 /r ib | AVX10.1 or AVX512BW |
Latency and throughput
| Model | xmm, xmm, m8, imm8 | xmm, xmm, r32, imm8 | xmm, xmm, r32, imm8 |
|---|---|---|---|
| Sandy Bridge | 7 / 0.5p15 | 2 / 1p15 | |
| Haswell, Broadwell, Skylake | 6 / 1p5 | 2 / 2p5 | |
| Skylake-SP | 6 / 1p5 | 2 / 2p5 | 2 / 2p5 |
| Ice Lake | 6 / 0.5p15 | 2 / 1p15 | 2 / 1p15 |
| Alder Lake | 8 / 0.5p15 | 4 / 1p15 | |
| Sapphire Rapids | 8 / 0.5p15 | 4 / 1p15 | 4 / 1p15 |
| Lunar Lake | 7 / 2V2 V3 | 5 / 1.33V2 V3 p1 p3 p5 | |
| Piledriver | 6 / 2FPMAL FPU0 FPU1 | 12 / 1.5FPMAL FPU0 FPU1 | |
| Zen | 8 / 0.5FPU0 FPU1 FPU2 FPU3 | 1 / 0.25FPU0 FPU1 FPU2 FPU3 | |
| Zen 2 | 8 / 0.33FPU0 FPU1 FPU2 FPU3 | 1 / 0.25FPU0 FPU1 FPU2 FPU3 | |
| Zen 3 | 8 / 1.5FP45 LSU Load | 2 / 1FP45 | |
| Zen 4 | 8 / 1.5FP45 LSU Load | 2 / 1FP45 | 1 / 1FP45 |
| Jaguar | 4 / 1FPU0 FPU1 VALU0 VALU1 | 7 / 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.
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 upRun on AMD Zen 5 (EPYC 9645): 4 cases.
Operands
| Operand | Kind | Action |
|---|---|---|
VPINSRB xmm, xmm, m8, imm8 | ||
xmm | explicit | write |
xmm | explicit | read |
m8 | explicit | read |
imm8 | explicit | read |
VPINSRB xmm, xmm, r32, imm8 | ||
xmm | explicit | write |
xmm | explicit | read |
r32 | explicit | read |
imm8 | 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-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.
| Intrinsic | Compiles to |
|---|---|
_mm_insert_epi8
__m128i _mm_insert_epi8(__m128i X, int I, const int N) |
|
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.
| ISA set | CPUID | Processors |
|---|---|---|
AVX | 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 |
AVX512BW_128N | AVX10.1 or AVX512BW | 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 |
More AVX instructions
- VPCMPGTB
- VPCMPGTD
- VPCMPGTQ
- VPCMPGTW
- VPCMPISTRI
- VPCMPISTRM
- VPERM2F128
- VPERMILPD
- VPERMILPS
- VPEXTRB
- VPEXTRD
- VPEXTRQ
- VPEXTRW
- VPHADDD
- VPHADDSW
- VPHADDW
- VPHMINPOSUW
- VPHSUBD
- VPHSUBSW
- VPHSUBW
- VPINSRD
- VPINSRQ
- VPINSRW
- VPMADDUBSW
- VPMADDWD
- VPMAXSB
- VPMAXSD
- VPMAXSW
- VPMAXUB
- VPMAXUD
- VPMAXUW
- VPMINSB
- VPMINSD
- VPMINSW
- VPMINUB
- VPMINUD
- VPMINUW
- VPMOVMSKB
- VPMOVSXBD
- VPMOVSXBQ
More AVX10.1 instructions
- VPERMQ
- VPERMT2B
- VPERMT2D
- VPERMT2PD
- VPERMT2PS
- VPERMT2Q
- VPERMT2W
- VPERMW
- VPEXPANDB
- VPEXPANDD
- VPEXPANDQ
- VPEXPANDW
- VPEXTRB
- VPEXTRD
- VPEXTRQ
- VPEXTRW
- VPGATHERDD
- VPGATHERDQ
- VPGATHERQD
- VPGATHERQQ
- VPINSRD
- VPINSRQ
- VPINSRW
- VPLZCNTD
- VPLZCNTQ
- VPMADD52HUQ
- VPMADD52LUQ
- VPMADDUBSW
- VPMADDWD
- VPMAXSB
- VPMAXSD
- VPMAXSQ
- VPMAXSW
- VPMAXUB
- VPMAXUD
- VPMAXUQ
- VPMAXUW
- VPMINSB
- VPMINSD
- VPMINSQ
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-305 (PINSRB/
PINSRD/ PINSRQ) - 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)
- 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.