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

VBROADCASTSS copies one single to every element of a vector. Which sources it takes depends on the extension:

  • AVX: memory only, a 4-byte value at any alignment, into an XMM or YMM register. Only those four bytes are read.
  • AVX2: also the low element of an XMM register.
  • AVX-512F (EVEX): ZMM destinations and masking, so that only the elements a mask selects receive the value.

The register form

_mm256_set1_ps(x), with x in a register, shows what the AVX2 form added. Compiling for AVX alone, GCC 14 and Clang 23 at -O2 need two instructions, VSHUFPS to fill the low 128 bits and VINSERTF128 to copy them to the high half; with -mavx2 both emit vbroadcastss ymm0, xmm0. The same holds for a loop that multiplies an array by a scalar, which broadcasts the scalar once before the loop. A value in memory needs no AVX2: both compile _mm256_set1_ps(*p) to vbroadcastss ymm0, dword ptr [rdi].

The two sources may differ in cost. Intel’s optimization guide says that in the Crestmont microarchitecture the 256-bit memory form takes one ALU micro-op besides the load, and the register form two (Section 4.1.9.2).

Constants

A constant repeated in every element can come from a 4-byte literal. GCC 14 loads a vector of eight 1.5s with VBROADCASTSS from such a literal even for AVX; Clang 23 does so with AVX2 but, with AVX alone, loads a 32-byte constant. With AVX-512 the broadcast can move into the instruction that uses the value: for x86-64-v4, Clang 23 compiles -x on a __m256 to one VXORPS whose memory operand, marked {1to8}, repeats a 4-byte sign mask, while GCC 14 loads the mask with VBROADCASTSS first (see VPBROADCASTD for the integer side).

VBROADCASTSD does the same for doubles, with YMM and ZMM destinations only, and VBROADCASTF128 repeats 16 bytes; VBROADCASTF32X2 and its kin repeat larger groups of singles.

In the optimization guide

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

Crestmont and Gracemont

  • Vectors and AVX2: A 256-bit broadcast is cheapest from memory: one operation, a cycle on top of the load.

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 VBROADCASTSS that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VBROADCASTSS xmm, m32 VBROADCASTSS_XMMdq_MEMdVEX.128.66.0F38.W0 18 /rAVX
VBROADCASTSS ymm, m32 VBROADCASTSS_YMMqq_MEMdVEX.256.66.0F38.W0 18 /rAVX
VBROADCASTSS xmm, xmm VBROADCASTSS_XMMdq_XMMdqVEX.128.66.0F38.W0 18 /rAVX2
VBROADCASTSS ymm, xmm VBROADCASTSS_YMMqq_XMMdqVEX.256.66.0F38.W0 18 /rAVX2
VBROADCASTSS zmm {k}{z}, m32 VBROADCASTSS_ZMMf32_MASKmskw_MEMf32_AVX512EVEX.512.66.0F38.W0 18 /rAVX10.1 or AVX512F
VBROADCASTSS zmm {k}{z}, xmm VBROADCASTSS_ZMMf32_MASKmskw_XMMf32_AVX512EVEX.512.66.0F38.W0 18 /rAVX10.1 or AVX512F
VBROADCASTSS xmm {k}{z}, m32 VBROADCASTSS_XMMf32_MASKmskw_MEMf32_AVX512EVEX.128.66.0F38.W0 18 /rAVX10.1 or AVX512F + AVX512VL
VBROADCASTSS xmm {k}{z}, xmm VBROADCASTSS_XMMf32_MASKmskw_XMMf32_AVX512EVEX.128.66.0F38.W0 18 /rAVX10.1 or AVX512F + AVX512VL
VBROADCASTSS ymm {k}{z}, m32 VBROADCASTSS_YMMf32_MASKmskw_MEMf32_AVX512EVEX.256.66.0F38.W0 18 /rAVX10.1 or AVX512F + AVX512VL
VBROADCASTSS ymm {k}{z}, xmm VBROADCASTSS_YMMf32_MASKmskw_XMMf32_AVX512EVEX.256.66.0F38.W0 18 /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, m32ymm, m32xmm, xmmymm, xmm
zmm {k}{z}, xmm
ymm {k}{z}, xmm
zmm {k}{z}, m32no mask
ymm {k}{z}, m32no mask
zmm {k}{z}, m32with a mask, zeroingxmm {k}{z}, m32no maskxmm {k}{z}, m32with a mask, zeroingxmm {k}{z}, xmmymm {k}{z}, m32with a mask, zeroing
Sandy Bridge6 / 0.5p237 / 1p5
Haswell, Skylake6 / 0.5p237 / 0.5p231 / 1p53 / 1p5
Broadwell5 / 0.5p236 / 0.5p231 / 1p53 / 1p5
Skylake-SP6 / 0.5p237 / 0.5p231 / 1p53 / 1p58 / 0.5p0158 / 0.5p0157 / 0.5p0157 / 0.5p0153 / 1p58 / 0.5p015
Ice Lake6 / 0.5p237 / 0.5p231 / 0.5p153 / 1p58 / 0.5p0158 / 0.5p0157 / 0.5p0157 / 0.5p0153 / 1p58 / 0.5p015
Alder Lake7 / 0.33p2 p3 p108 / 0.33p2 p3 p101 / 1p53 / 1p5
Sapphire Rapids7 / 0.33p2 p3 p108 / 0.33p2 p3 p101 / 1p53 / 1p58 / 0.33p2 p3 p109 / 0.5p057 / 0.33p2 p3 p108 / 0.33p0151 / 1p59 / 0.33p015
Lunar Lake6 / 2p20 p21 p227 / 2.33p20 p21 p221 / 0.5V2 V33 / 0.5V2 V3
Piledriver7 / 1.5FPFMA FPU0 FPU16 / 2FPFMA FPU0 FPU1
Zen8 / 0.5FPU1 FPU28 / 0.5FPU1 FPU21 / 0.5FPU1 FPU22 / 1FPU1 FPU2
Zen 28 / 0.5FPU1 FPU28 / 0.5FPU1 FPU21 / 0.5FPU1 FPU22 / 0.5FPU1 FPU2
Zen 38 / 0.5FP1 FP28 / 0.5FP1 FP21 / 0.5FP1 FP22 / 1FP1
Zen 48 / 0.5FP1 FP28 / 0.5FP1 FP21 / 0.5FP1 FP22 / 11FP19 / 1FP19 / 1FP19 / 1FP19 / 1FP12 / 12FP19 / 1FP1
Jaguar6 / 1FPA FPM FPU0 FPU16 / 2FPA FPM FPU0 FPU1
  1. Zen 4 model: AMD's spreadsheets give latency 1 for Zen 4 and Zen 5 (AMD 57647, row 931; AMD 58455, row 1301).
  2. Zen 4 model: AMD's spreadsheets give latency 1 for Zen 4 and Zen 5 (AMD 57647, row 929; AMD 58455, row 515).

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 single goes to every single of the result.
VBROADCASTSS: one single everywhereResult singles 15 to 0: a0, unchanged (bit 14 of k1 is 0), a0, a0, a0, a0, a0, a0, a0, a0, a0, a0, a0, a0, a0, a0.0123xmm2or m32a1111111111111110k1a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0zmm1

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

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

Run on AMD Zen 5 (EPYC 9645): 10 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
VBROADCASTSS xmm, xmm/m32 VBROADCASTSS ymm, xmm/m32
xmm, ymmexplicitwrite
xmm/m32explicitread
VBROADCASTSS xmm {k}{z}, xmm/m32 VBROADCASTSS ymm {k}{z}, xmm/m32 VBROADCASTSS zmm {k}{z}, xmm/m32
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm/m32explicitread

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
EVEX 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 VBROADCASTSS, 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_ss __m128 _mm_broadcast_ss(const float *__a)

VBROADCASTSS xmm, m32 VEX.128 -mavx

_mm_broadcastss_ps __m128 _mm_broadcastss_ps(__m128 __X)

VBROADCASTSS xmm, xmm VEX.128 -mavx2

_mm_load_ps1 __m128 _mm_load_ps1(const float *p)

VBROADCASTSS xmm, m32 VEX.128 -mavxwith AVX enabled

_mm_set1_pch __m128h _mm_set1_pch(_Complex _Float16 h)

VBROADCASTSS xmm, xmm VEX.128 -mavx512fp16 -mavx512vl

_mm_mask_broadcastss_ps __m128 _mm_mask_broadcastss_ps(__m128 __O, __mmask8 __M, __m128 __A)

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

_mm_maskz_broadcastss_ps __m128 _mm_maskz_broadcastss_ps(__mmask8 __M, __m128 __A)

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

_mm256_broadcast_ss __m256 _mm256_broadcast_ss(const float *__a)

VBROADCASTSS ymm, m32 VEX.256 -mavx

_mm256_broadcastss_ps __m256 _mm256_broadcastss_ps(__m128 __X)

VBROADCASTSS ymm, xmm VEX.256 -mavx2

_mm256_set1_pch __m256h _mm256_set1_pch(_Complex _Float16 h)

VBROADCASTSS ymm, xmm VEX.256 -mavx512fp16 -mavx512vl

_mm256_mask_broadcastss_ps __m256 _mm256_mask_broadcastss_ps(__m256 __O, __mmask8 __M, __m128 __A)

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

_mm256_maskz_broadcastss_ps __m256 _mm256_maskz_broadcastss_ps(__mmask8 __M, __m128 __A)

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

_mm512_broadcastss_ps __m512 _mm512_broadcastss_ps(__m128 __A)

VBROADCASTSS zmm, xmm EVEX.512 -mavx512f

_mm512_set1_pch __m512h _mm512_set1_pch(_Complex _Float16 __h)

VBROADCASTSS zmm, xmm EVEX.512 -mavx512fp16

_mm512_set1_ps __m512 _mm512_set1_ps(float __w)

VBROADCASTSS zmm, xmm EVEX.512 -mavx512f

_mm512_mask_broadcastss_ps __m512 _mm512_mask_broadcastss_ps(__m512 __O, __mmask16 __M, __m128 __A)

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

_mm512_maskz_broadcastss_ps __m512 _mm512_maskz_broadcastss_ps(__mmask16 __M, __m128 __A)

VBROADCASTSS zmm {k}{z}, xmm 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
AVX

AVX
CPUID.01H:ECX[28] 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
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 AVX instructions

All 253 AVX instructions

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-12 (VBROADCAST)
  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. Intel 64 and IA-32 Architectures Optimization Reference Manual, Volume 1 (248966-051, October 2026)

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.