Instruction
VBROADCASTI32X4
Copies a group of four doublewords (128 bits) from memory to every 128-bit block of a vector.
- Extensions
- Forms
- 2 (2 EVEX)
- Data
- Intel XED v2026.08.23
VBROADCASTI32X4 loads 16 bytes from memory and repeats them in every 128-bit block of a YMM or ZMM register, writing the result under a mask of doublewords. Like VBROADCASTI128, whose page covers tables for byte shuffles, it has no register source. It needs AVX512F; VBROADCASTI64X2 is the same with a quadword mask and needs AVX512DQ.
On Zen 5, vbroadcasti32x4 zmm9{k5}, [mem] with D5E1h in the low 16
bits of K5 wrote the four doublewords of memory into doublewords 0, 5
to 8, 10, 12, 14 and 15 of ZMM9, each in its place within its block,
and kept the other seven.
Uses
- Round keys. VAES works on four AES blocks in a zmm register, so each round key must be in all four lanes; the VAESENC and VAESDEC pages show compilers loading each key with VBROADCASTI32X4.
- Tables. GCC 14 and Clang 23 at -O2 with
-march=x86-64-v4load a 16-byte table for a 512-bit VPSHUFB lookup with VBROADCASTI32X4, from one 16-byte copy of the table. - Rows into lanes. A mask that selects one block turns it into an insert from memory. Intel’s optimization manual transposes BF16 matrices this way: one unmasked VBROADCASTI32X4 and three masked with 0F0h, 0F00h and 0F000h place four 16-byte rows in the four blocks of a register (Section 20.16.1, Example 20-26).
The masked intrinsics _mm512_mask_broadcast_i32x4 and
_mm512_maskz_broadcast_i32x4 compile to VBROADCASTI32X4 in both
compilers, as does the plain one of a loaded value; of a value in a
register, which the instruction cannot take, GCC makes a
VSHUFI32X4. The 256-bit
_mm256_broadcast_i32x4 is VBROADCASTI32X4 in GCC and VBROADCASTI128
in Clang.
AMD’s Zen 5 latency spreadsheet gives VBROADCASTI32X4 one cycle on pipe FP1 or FP2 and two per cycle, where the VEX VBROADCASTI128 row names no pipe. Zen 5’s 2 recorded cases cover both widths.
Forms
| Instruction | Encoding | Requires |
|---|---|---|
VBROADCASTI32X4 zmm {k}{z}, m128
VBROADCASTI32X4_ZMMu32_MASKmskw_MEMu32_AVX512 | EVEX.512.66.0F38.W0 5A /r | AVX10.1 or AVX512F |
VBROADCASTI32X4 ymm {k}{z}, m128
VBROADCASTI32X4_YMMu32_MASKmskw_MEMu32_AVX512 | EVEX.256.66.0F38.W0 5A /r | AVX10.1 or AVX512F + AVX512VL |
Latency and throughput
| Model | zmm {k}{z}, m128no maskymm {k}{z}, m128no mask | zmm {k}{z}, m128with a mask, zeroing | ymm {k}{z}, m128with a mask, zeroing |
|---|---|---|---|
| Skylake-SP, Ice Lake | 8 / 0.5p015 | 8 / 0.5p015 | 8 / 0.5p015 |
| Sapphire Rapids | 8 / 0.33p2 p3 p10 | 9 / 0.5p05 | 9 / 0.33p015 |
| Zen 4 | 8 / 0.5FP1 FP2 | 8 / 0.5FP1 FP2 | 8 / 0.5FP1 FP2 |
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.
Shown for the zmm form; the ymm form works the same on 8 doublewords. The forms write under a mask: where its bit is 0, the element keeps its old value, or zeroes it with {z}.
Result doublewords 15 to 0: a3, unchanged (bit 14 of k1 is 0), a1, a0, a3, a2, a1, a0, a3, a2, a1, a0, 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 // 32):
if k1[i]:
zmm1.d[i] = mem.d[i % 4]
elif zeroing:
zmm1.d[i] = 0
# else: zmm1.d[i] keeps its value
# zmm1 is zeroed from bit VL upRun on AMD Zen 5 (EPYC 9645): 2 cases.
Operands
| Operand | Kind | Action |
|---|---|---|
VBROADCASTI32X4 ymm {k}{z}, m128 VBROADCASTI32X4 zmm {k}{z}, m128 | ||
ymm, zmm | explicit | write (masked) |
{k} | explicit | read (write mask) |
m128 | 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.
- All forms
AVX512-E6
Attributes
What else XED records about the forms. How to read.
- All forms
- write masking; memory fault suppression
Intrinsics
The C intrinsics of Clang 23.1.2 that compile to VBROADCASTI32X4, 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 |
|---|---|
_mm256_mask_broadcast_i32x4
__m256i _mm256_mask_broadcast_i32x4(__m256i __O, __mmask8 __M, __m128i __A) |
|
_mm256_maskz_broadcast_i32x4
__m256i _mm256_maskz_broadcast_i32x4(__mmask8 __M, __m128i __A) |
|
_mm512_broadcast_i32x4
__m512i _mm512_broadcast_i32x4(__m128i __A) |
|
_mm512_mask_broadcast_i32x4
__m512i _mm512_mask_broadcast_i32x4(__m512i __O, __mmask16 __M, __m128i __A) |
|
_mm512_maskz_broadcast_i32x4
__m512i _mm512_maskz_broadcast_i32x4(__mmask16 __M, __m128i __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.
| ISA set | CPUID | Processors |
|---|---|---|
AVX512F_512 | AVX10.1 or AVX512F | 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, Knights Landing, Knights Mill, Zen 4, Zen 5, Zen 6 |
AVX512F_256 | AVX10.1 or AVX512F + 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 |
More AVX10.1 instructions
- VADDSH
- VADDSS
- VAESDEC
- VAESDECLAST
- VAESENC
- VAESENCLAST
- VALIGND
- VALIGNQ
- VANDNPD
- VANDNPS
- VANDPD
- VANDPS
- VBLENDMPD
- VBLENDMPS
- VBROADCASTF32X2
- VBROADCASTF32X4
- VBROADCASTF32X8
- VBROADCASTF64X2
- VBROADCASTF64X4
- VBROADCASTI32X2
- VBROADCASTI32X8
- VBROADCASTI64X2
- VBROADCASTI64X4
- VBROADCASTSD
- VBROADCASTSS
- VCMPPD
- VCMPPH
- VCMPPS
- VCMPSD
- VCMPSH
- VCMPSS
- VCOMISD
- VCOMISH
- VCOMISS
- VCOMPRESSPD
- VCOMPRESSPS
- VCVTDQ2PD
- VCVTDQ2PH
- VCVTDQ2PS
- VCVTNE2PS2BF16
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 Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
- Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2C, page 5-442 (VPBROADCAST)
- Intel 64 and IA-32 Architectures Optimization Reference Manual, Volume 1 (248966-051, October 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.