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

VPBROADCASTQ fills every quadword of a vector with one 64-bit value: the low quadword of an XMM register, eight bytes of memory, or, in the EVEX forms, a 64-bit general-purpose register. VPBROADCASTD describes the family and how the sources differ by encoding. With a write mask, only the selected elements get the value: on Zen 5, vpbroadcastq zmm14{k4}, rdx wrote RDX into quadwords 0, 2, 5, 6 and 7, the set bits of the low byte of K4 (E5h), and kept the other three, while vpbroadcastq ymm7{k3}{z}, r14 zeroed the elements its mask left out.

In compiled code

GCC 14 and Clang 23 at -O2 compile _mm256_set1_epi64x(x), and a loop adding a 64-bit k to every element of an array, to VMOVQ and VPBROADCASTQ with -march=x86-64-v3, and to VPBROADCASTQ straight from the register with -march=x86-64-v4. For 128 bits under AVX2, _mm_set1_epi64x(x) is VMOVQ and VPBROADCASTQ in Clang, while GCC unpacks the register with itself by VPUNPCKLQDQ.

From memory, GCC uses VPBROADCASTQ and Clang prints VBROADCASTSD, which copies the same 64 bits. A 64-bit constant, as in _mm256_add_epi64(a, _mm256_set1_epi64x(0x0123456789abcdef)), shows the two styles of the family: GCC builds it with MOVABS and broadcasts it from the register, and Clang broadcasts eight bytes from memory with VPBROADCASTQ, or, with AVX-512, folds them into the VPADDQ as an embedded {1to4} operand. A constant whose halves are equal, such as 00FF00FF00FF00FFh, needs only a doubleword: GCC broadcasts it with VPBROADCASTD.

A double in a register, _mm256_set1_pd(x), is spread by VBROADCASTSD from the XMM register in both compilers, the register form that AVX2 added beside VPBROADCASTQ.

AMD’s latency spreadsheet for Zen 5 lists the 128-bit VEX form with a register or memory source as one macro-op with a latency of one cycle on all four vector pipes, the 256-bit VEX form and the EVEX forms on two of them, and the forms with a general-purpose source as two macro-ops. VPBROADCASTMB2Q copies a mask register into every quadword instead.

In the optimization guide

What the optimization guide says about VPBROADCASTQ, a line per claim. Each links to the claim in the guide, with its sources and where they differ.

Skylake to Cooper Lake

  • AVX-512 and frequency on the servers: A broadcast of a 32-bit or 64-bit element from memory runs on the load ports, sparing port 5; a 16-bit one still goes through port 5, so it gains nothing from the memory form.

Forms

Every encoding of VPBROADCASTQ that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPBROADCASTQ xmm, m64 VPBROADCASTQ_XMMdq_MEMqVEX.128.66.0F38.W0 59 /rAVX2
VPBROADCASTQ xmm, xmm VPBROADCASTQ_XMMdq_XMMqVEX.128.66.0F38.W0 59 /rAVX2
VPBROADCASTQ ymm, m64 VPBROADCASTQ_YMMqq_MEMqVEX.256.66.0F38.W0 59 /rAVX2
VPBROADCASTQ ymm, xmm VPBROADCASTQ_YMMqq_XMMqVEX.256.66.0F38.W0 59 /rAVX2
VPBROADCASTQ zmm {k}{z}, m64 VPBROADCASTQ_ZMMu64_MASKmskw_MEMu64_AVX512EVEX.512.66.0F38.W1 59 /rAVX10.1 or AVX512F
VPBROADCASTQ zmm {k}{z}, xmm VPBROADCASTQ_ZMMu64_MASKmskw_XMMu64_AVX512EVEX.512.66.0F38.W1 59 /rAVX10.1 or AVX512F
VPBROADCASTQ zmm {k}{z}, r64 64-bit mode only VPBROADCASTQ_ZMMu64_MASKmskw_GPR64u64_AVX512EVEX.512.66.0F38.W1 7C /rAVX10.1 or AVX512F
VPBROADCASTQ xmm {k}{z}, m64 VPBROADCASTQ_XMMu64_MASKmskw_MEMu64_AVX512EVEX.128.66.0F38.W1 59 /rAVX10.1 or AVX512F + AVX512VL
VPBROADCASTQ xmm {k}{z}, xmm VPBROADCASTQ_XMMu64_MASKmskw_XMMu64_AVX512EVEX.128.66.0F38.W1 59 /rAVX10.1 or AVX512F + AVX512VL
VPBROADCASTQ xmm {k}{z}, r64 64-bit mode only VPBROADCASTQ_XMMu64_MASKmskw_GPR64u64_AVX512EVEX.128.66.0F38.W1 7C /rAVX10.1 or AVX512F + AVX512VL
VPBROADCASTQ ymm {k}{z}, m64 VPBROADCASTQ_YMMu64_MASKmskw_MEMu64_AVX512EVEX.256.66.0F38.W1 59 /rAVX10.1 or AVX512F + AVX512VL
VPBROADCASTQ ymm {k}{z}, xmm VPBROADCASTQ_YMMu64_MASKmskw_XMMu64_AVX512EVEX.256.66.0F38.W1 59 /rAVX10.1 or AVX512F + AVX512VL
VPBROADCASTQ ymm {k}{z}, r64 64-bit mode only VPBROADCASTQ_YMMu64_MASKmskw_GPR64u64_AVX512EVEX.256.66.0F38.W1 7C /rAVX10.1 or AVX512F + AVX512VL

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, m64xmm, xmm
xmm {k}{z}, xmm
ymm, m64ymm, xmm
zmm {k}{z}, xmm
ymm {k}{z}, xmm
zmm {k}{z}, m64no mask
ymm {k}{z}, m64no mask
zmm {k}{z}, m64with a mask, zeroingzmm {k}{z}, r64
ymm {k}{z}, r64
xmm {k}{z}, m64no maskxmm {k}{z}, m64with a mask, zeroingxmm {k}{z}, r64ymm {k}{z}, m64with a mask, zeroing
Haswell, Skylake6 / 0.5p231 / 1p57 / 0.5p233 / 1p5
Broadwell5 / 0.5p231 / 1p56 / 0.5p233 / 1p5
Skylake-SP, Ice Lake6 / 0.5p231 / 1p57 / 0.5p233 / 1p58 / 0.5p0158 / 0.5p0153 / 1p57 / 0.5p0157 / 0.5p0151 / 1p58 / 0.5p015
Alder Lake7 / 0.33p2 p3 p101 / 1p58 / 0.33p2 p3 p103 / 1p5
Sapphire Rapids7 / 0.33p2 p3 p101 / 1p58 / 0.33p2 p3 p103 / 1p58 / 0.33p2 p3 p109 / 0.5p055 / 1p57 / 0.33p2 p3 p108 / 0.33p0155 / 1p59 / 0.33p015
Lunar Lake6 / 2p20 p21 p221 / 0.33p1357 / 2.33p20 p21 p223 / 0.5V2 V3
Zen8 / 0.5FPU1 FPU21 / 0.5FPU1 FPU28 / 0.5FPU1 FPU22 / 1FPU1 FPU2
Zen 28 / 0.5FPU1 FPU21 / 0.5FPU1 FPU28 / 0.5FPU1 FPU22 / 0.5FPU1 FPU2
Zen 38 / 0.5FP1 FP21 / 0.5FP1 FP28 / 0.5FP1 FP22 / 1FP1
Zen 48 / 0.5FP1 FP21 / 0.5FP1 FP28 / 0.5FP1 FP21 / 11FP18 / 1FP18 / 1FP11 / 1FP18 / 0.5FP1 FP28 / 0.5FP1 FP21 / 0.52FP1 FP28 / 1FP1
  1. Zen 4 model, ymm form: AMD's spreadsheets give reciprocal throughput 0.5 for Zen 4 and Zen 5 (AMD 57647, row 2031; AMD 58455, row 1296).
  2. Zen 4 model: AMD's spreadsheets give reciprocal throughput 1 for Zen 4 and Zen 5 (AMD 57647, row 2025; AMD 58455, row 511).

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.

Broadcast: the low quadword goes to every quadword of the result.
VPBROADCASTQ: one quadword everywhereResult quadwords 7 to 0: a0, unchanged (bit 6 of k1 is 0), a0, a0, a0, a0, a0, a0.01xmm2or r64, m64a11111110k1a0a0a0a0a0a0a0zmm1

Shown for the zmm form; the xmm and ymm forms work the same on 2 and 4 quadwords. The EVEX forms write under a mask: where its bit is 0, the element keeps its old value, or zeroes it with {z}.

Result quadwords 7 to 0: a0, unchanged (bit 6 of k1 is 0), a0, a0, a0, a0, a0, 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 // 64):
    if k1[i]:  # 1 without a write mask
        zmm1.q[i] = src2.q[0]
    elif zeroing:
        zmm1.q[i] = 0
    # else: zmm1.q[i] keeps its value
# zmm1 is zeroed from bit VL up

Run on AMD Zen 5 (EPYC 9645): 13 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
VPBROADCASTQ xmm, xmm/m64 VPBROADCASTQ ymm, xmm/m64
xmm, ymmexplicitwrite
xmm/m64explicitread
VPBROADCASTQ xmm {k}{z}, xmm/m64 VPBROADCASTQ ymm {k}{z}, xmm/m64 VPBROADCASTQ zmm {k}{z}, xmm/m64
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm/m64explicitread
VPBROADCASTQ xmm {k}{z}, r64 64-bit mode only VPBROADCASTQ ymm {k}{z}, r64 64-bit mode only VPBROADCASTQ zmm {k}{z}, r64 64-bit mode only
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
r64explicitread

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-6
Forms only in 64-bit mode
AVX512-E7NM
Other forms
AVX512-E6

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 VPBROADCASTQ, 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_broadcast_i32x2 __m128i _mm_broadcast_i32x2(__m128i __A)

VPBROADCASTQ xmm, xmm VEX.128 -mavx512vl -mavx512dq

_mm_broadcastmb_epi64 __m128i _mm_broadcastmb_epi64(__mmask8 __A)

VPBROADCASTQ xmm, r64 EVEX.128 -mavx512vl -mavx512cd

_mm_broadcastq_epi64 __m128i _mm_broadcastq_epi64(__m128i __X)

VPBROADCASTQ xmm, xmm VEX.128 -mavx2

_mm_mask_broadcastq_epi64 __m128i _mm_mask_broadcastq_epi64(__m128i __O, __mmask8 __M, __m128i __A)

VPBROADCASTQ xmm {k}, xmm EVEX.128 -mavx512vl

_mm_mask_set1_epi64 __m128i _mm_mask_set1_epi64(__m128i __O, __mmask8 __M, long long __A)

VPBROADCASTQ xmm {k}, r64 EVEX.128 -mavx512vl

_mm_maskz_broadcastq_epi64 __m128i _mm_maskz_broadcastq_epi64(__mmask8 __M, __m128i __A)

VPBROADCASTQ xmm {k}{z}, xmm EVEX.128 -mavx512vl

_mm_maskz_set1_epi64 __m128i _mm_maskz_set1_epi64(__mmask8 __M, long long __A)

VPBROADCASTQ xmm {k}{z}, r64 EVEX.128 -mavx512vl

_mm256_broadcast_i32x2 __m256i _mm256_broadcast_i32x2(__m128i __A)

VPBROADCASTQ ymm, xmm VEX.256 -mavx512vl -mavx512dq

_mm256_broadcastmb_epi64 __m256i _mm256_broadcastmb_epi64(__mmask8 __A)

VPBROADCASTQ ymm, r64 EVEX.256 -mavx512vl -mavx512cd

_mm256_broadcastq_epi64 __m256i _mm256_broadcastq_epi64(__m128i __X)

VPBROADCASTQ ymm, xmm VEX.256 -mavx2

_mm256_mask_broadcastq_epi64 __m256i _mm256_mask_broadcastq_epi64(__m256i __O, __mmask8 __M, __m128i __A)

VPBROADCASTQ ymm {k}, xmm EVEX.256 -mavx512vl

_mm256_mask_set1_epi64 __m256i _mm256_mask_set1_epi64(__m256i __O, __mmask8 __M, long long __A)

VPBROADCASTQ ymm {k}, r64 EVEX.256 -mavx512vl

_mm256_maskz_broadcastq_epi64 __m256i _mm256_maskz_broadcastq_epi64(__mmask8 __M, __m128i __A)

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

_mm256_maskz_set1_epi64 __m256i _mm256_maskz_set1_epi64(__mmask8 __M, long long __A)

VPBROADCASTQ ymm {k}{z}, r64 EVEX.256 -mavx512vl

_mm512_broadcastmb_epi64 __m512i _mm512_broadcastmb_epi64(__mmask8 __A)

VPBROADCASTQ zmm, r64 EVEX.512 -mavx512cd

_mm512_broadcastq_epi64 __m512i _mm512_broadcastq_epi64(__m128i __A)

VPBROADCASTQ zmm, xmm EVEX.512 -mavx512f

_mm512_set1_epi64 __m512i _mm512_set1_epi64(long long __d)

VPBROADCASTQ zmm, r64 EVEX.512 -mavx512f

_mm512_mask_broadcastq_epi64 __m512i _mm512_mask_broadcastq_epi64(__m512i __O, __mmask8 __M, __m128i __A)

VPBROADCASTQ zmm {k}, xmm EVEX.512 -mavx512f

_mm512_mask_set1_epi64 __m512i _mm512_mask_set1_epi64(__m512i __O, __mmask8 __M, long long __A)

VPBROADCASTQ zmm {k}, r64 EVEX.512 -mavx512f

_mm512_maskz_broadcastq_epi64 __m512i _mm512_maskz_broadcastq_epi64(__mmask8 __M, __m128i __A)

VPBROADCASTQ zmm {k}{z}, xmm EVEX.512 -mavx512f

_mm512_maskz_set1_epi64 __m512i _mm512_maskz_set1_epi64(__mmask8 __M, long long __A)

VPBROADCASTQ zmm {k}{z}, r64 EVEX.512 -mavx512f

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

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

or

AVX512F
CPUID.(EAX=07H,ECX=0):EBX[16] 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_128

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

or

AVX512F + AVX512VL
CPUID.(EAX=07H,ECX=0):EBX[16] AVX512F
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
AVX512F_256
Same as AVX512F_128Same as AVX512F_128

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 2C, page 5-442 (VPBROADCAST); Volume 2C, page 5-451 (VPBROADCASTB/W/D/Q)
  6. Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
  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.