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

VINSERTF32X8 copies a ZMM source to the destination with its low or high 256 bits, chosen by bit 0 of the immediate, replaced by a YMM register or 32 bytes of memory, and writes the result under a mask of singles. It is VINSERTI32X8 under a floating-point name, with the same bits moved and the same AVX512DQ requirement, and that page sets it against VINSERTI64X4, which gives the same result unmasked. Nothing is converted or quieted, and no SIMD exception can arise.

Recorded on Zen 5

  • Source and destination in one register. In vinsertf32x8 zmm7{k4}, zmm12, ymm7, 0xe9, only bit 0 of E9h counted and put YMM7 in the high half: the selected singles 8, 10, 11, 13 and 14 received the old singles 0, 2, 3, 5 and 6 of ZMM7, so the YMM source was read before any element was written. In the low half the selected singles came from ZMM12 and the others kept ZMM7’s old values.
  • Memory into the low half. With immediate 08h, bit 0 clear, vinsertf32x8 zmm24{k3}, zmm3, [mem], 0x8 put memory singles 0, 1, 3, 5, 6 and 7 where AAEBh, the low 16 bits of K3, selected them, and ZMM3’s singles 9, 11, 13 and 15 in the high half.

In compiled code

GCC 14 and Clang 23 at -O2 with -march=x86-64-v4 compile the masked _mm512_mask_insertf32x8 and _mm512_maskz_insertf32x8 to VINSERTF32X8. Unmasked, GCC keeps VINSERTF32X8 for _mm512_insertf32x8(x, y, 1), also when it joins two __m256 halves, while Clang emits VINSERTF64X4. Inserting a vector loaded from memory into a copy of itself becomes a load and VINSERTF32X8 in GCC and one VBROADCASTF64X4 in Clang.

AMD’s Zen 5 latency spreadsheet gives VINSERTF32X8 one cycle and two per cycle on pipes FP1 and FP2, the same as VINSERTI32X8.

Forms

Every encoding of VINSERTF32X8 that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VINSERTF32X8 zmm {k}{z}, zmm, ymm, imm8 VINSERTF32X8_ZMMf32_MASKmskw_ZMMf32_YMMf32_IMM8_AVX512EVEX.512.66.0F3A.W0 1A /r ibAVX10.1 or AVX512DQ
VINSERTF32X8 zmm {k}{z}, zmm, m256, imm8 VINSERTF32X8_ZMMf32_MASKmskw_ZMMf32_MEMf32_IMM8_AVX512EVEX.512.66.0F3A.W0 1A /r ibAVX10.1 or AVX512DQ

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.
Modelzmm {k}{z}, zmm, ymm, imm8zmm {k}{z}, zmm, m256, imm8
Skylake-SP, Ice Lake3 / 1p58 / 0.5p015
Sapphire Rapids3 / 1p59 / 0.5p05
Zen 42 / 11FP19 / 1FP1
  1. Zen 4 model: AMD's spreadsheets give latency 1 for Zen 4 and Zen 5 (AMD 57647, row 1527; AMD 58455, row 559).

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: ymm3 replaces the 256-bit block of zmm2 that imm8 numbers; the rest of the result comes from zmm2.
VINSERTF32X8 with imm8 = 0x01With imm8 = 0x01, result singles 15 to 0: b7, unchanged (bit 14 of k1 is 0), b5, b4, b3, b2, b1, b0, a7, a6, a5, a4, a3, a2, a1, a0.0123456789101112131415zmm2a1111111111111110k1a0a1a2a3a4a5a6a7b0b1b2b3b4b5b7zmm101234567ymm3or m256b

Example: imm8 = 0x01. The forms write under a mask: where its bit is 0, the element keeps its old value, or zeroes it with {z}.

With imm8 = 0x01, result singles 15 to 0: b7, unchanged (bit 14 of k1 is 0), b5, b4, b3, b2, b1, b0, 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.

x = imm8 & 1  # the 256-bit block replaced
for i in range(16):
    if k1[i]:
        if i // 8 == x:
            zmm1.d[i] = src3.d[i % 8]
        else:
            zmm1.d[i] = zmm2.d[i]
    elif zeroing:
        zmm1.d[i] = 0
    # else: zmm1.d[i] keeps its value

Run on AMD Zen 5 (EPYC 9645): 2 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
VINSERTF32X8 zmm {k}{z}, zmm, ymm/m256, imm8
zmmexplicitwrite (masked)
{k}explicitread (write mask)
zmmexplicitread
ymm/m256explicitread
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.

All forms
AVX512-E6NF

Attributes

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

All forms
write masking

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VINSERTF32X8, 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
_mm512_broadcast_f32x8 __m512 _mm512_broadcast_f32x8(__m256 __A)

VINSERTF32X8 zmm, zmm, ymm, imm8 EVEX.512 -mavx512dqClang emits the equivalent VINSERTF64X4

_mm512_insertf32x8 __m512 _mm512_insertf32x8(__m512 A, __m256 B, const int imm)

VINSERTF32X8 zmm, zmm, ymm, imm8 EVEX.512 -mavx512dqClang emits the equivalent VINSERTF64X4

_mm512_mask_broadcast_f32x8 __m512 _mm512_mask_broadcast_f32x8(__m512 __O, __mmask16 __M, __m256 __A)

VINSERTF32X8 zmm {k}, zmm, ymm, imm8 EVEX.512 -mavx512dq

_mm512_mask_insertf32x8 __m512 _mm512_mask_insertf32x8(__m512 W, __mmask16 U, __m512 A, __m256 B, const int imm)

VINSERTF32X8 zmm {k}, zmm, ymm, imm8 EVEX.512 -mavx512dq

_mm512_maskz_broadcast_f32x8 __m512 _mm512_maskz_broadcast_f32x8(__mmask16 __M, __m256 __A)

VINSERTF32X8 zmm {k}{z}, zmm, ymm, imm8 EVEX.512 -mavx512dq

_mm512_maskz_insertf32x8 __m512 _mm512_maskz_insertf32x8(__mmask16 U, __m512 A, __m256 B, const int imm)

VINSERTF32X8 zmm {k}{z}, zmm, ymm, imm8 EVEX.512 -mavx512dq

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
AVX512DQ_512

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

or

AVX512DQ
CPUID.(EAX=07H,ECX=0):EBX[17] AVX512DQ

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 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-406 (VINSERTF128/VINSERTF32x4/VINSERTF64x2/VINSERTF32x8/VINSERTF64x4)
  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.