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

VADDPS is ADDPS in VEX and EVEX encodings. The ADDPS page covers the rounding, the tie rule and the invalid sums; this one covers what only the new encodings do, as the cases recorded on Zen 5 show it.

  • The VEX forms write a third register and clear everything above the result: a 128-bit VADDPS left bits 128 to 511 of its destination zero, whatever they held.
  • The EVEX forms write under a mask register, and an element whose mask bit is clear is not computed at all. With the invalid exception unmasked, vaddps zmm9{k2}, zmm9, zmm14 added 1 and 2 in the eight selected elements and left signaling NaNs in the other eight alone, without #XM.

Rounding given in the instruction

Between 512-bit registers, an EVEX VADDPS can carry its own rounding mode, {rn-sae}, {rd-sae}, {ru-sae} or {rz-sae}, which replaces MXCSR.RC for that instruction. Zen 5 added 3 and 0.1 to 3.0999999 under MXCSR’s round to nearest, and to 3.10000014 under {ru-sae} while MXCSR asked to round toward zero. The sae part suppresses every exception: with all of them unmasked (MXCSR 0) and signaling NaNs among the inputs, {rn-sae} returned the NaNs quieted, took no #XM and set no flag.

Compilers

For a[i] = b[i] + c[i] over 1,024 floats, GCC 14 and Clang 23 at -O2 with -march=x86-64-v3 add ymm registers and take one operand straight from memory, which the VEX form allows at any alignment. With -march=x86-64-v4 GCC uses zmm registers and Clang stays with ymm; for -march=znver5 both use zmm, the width that AMD’s Zen 5 guide recommends, as that processor’s data paths are 512 bits wide (Section 2.11.2). The guide lists VADDPS as one macro-op with a latency of 2 cycles at every width.

In the optimization guide

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

Out of order

Forms

Every encoding of VADDPS that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VADDPS xmm, xmm, m128 VADDPS_XMMdq_XMMdq_MEMdqVEX.128.NP.0F.WIG 58 /rAVX
VADDPS xmm, xmm, xmm VADDPS_XMMdq_XMMdq_XMMdqVEX.128.NP.0F.WIG 58 /rAVX
VADDPS ymm, ymm, m256 VADDPS_YMMqq_YMMqq_MEMqqVEX.256.NP.0F.WIG 58 /rAVX
VADDPS ymm, ymm, ymm VADDPS_YMMqq_YMMqq_YMMqqVEX.256.NP.0F.WIG 58 /rAVX
VADDPS zmm {k}{z}, zmm, zmm, {er} VADDPS_ZMMf32_MASKmskw_ZMMf32_ZMMf32_AVX512EVEX.512.NP.0F.W0 58 /rAVX10.1 or AVX512F
VADDPS zmm {k}{z}, zmm, m512/m32bcst VADDPS_ZMMf32_MASKmskw_ZMMf32_MEMf32_AVX512EVEX.512.NP.0F.W0 58 /rAVX10.1 or AVX512F
VADDPS xmm {k}{z}, xmm, xmm VADDPS_XMMf32_MASKmskw_XMMf32_XMMf32_AVX512EVEX.128.NP.0F.W0 58 /rAVX10.1 or AVX512F + AVX512VL
VADDPS xmm {k}{z}, xmm, m128/m32bcst VADDPS_XMMf32_MASKmskw_XMMf32_MEMf32_AVX512EVEX.128.NP.0F.W0 58 /rAVX10.1 or AVX512F + AVX512VL
VADDPS ymm {k}{z}, ymm, ymm VADDPS_YMMf32_MASKmskw_YMMf32_YMMf32_AVX512EVEX.256.NP.0F.W0 58 /rAVX10.1 or AVX512F + AVX512VL
VADDPS ymm {k}{z}, ymm, m256/m32bcst VADDPS_YMMf32_MASKmskw_YMMf32_MEMf32_AVX512EVEX.256.NP.0F.W0 58 /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, xmm, m128
xmm {k}{z}, xmm, m128/m32bcst
xmm, xmm, xmm
xmm {k}{z}, xmm, xmmno mask, with a mask
ymm {k}{z}, ymm, ymmno mask, with a mask
ymm, ymm, m256
ymm {k}{z}, ymm, m256/m32bcst
ymm, ymm, ymmzmm {k}{z}, zmm, zmm, {er}no mask, with {er}zmm {k}{z}, zmm, zmm, {er}with a mask, zeroingzmm {k}{z}, zmm, m512/m32bcstxmm {k}{z}, xmm, xmmzeroing
ymm {k}{z}, ymm, ymmzeroing
Sandy Bridge, Haswell9 / 1p13 / 1p110 / 1p13 / 1p1
Broadwell8 / 1p13 / 1p19 / 1p13 / 1p1
Skylake10 / 0.5p014 / 0.5p0111 / 0.5p014 / 0.5p01
Skylake-SP10 / 0.5p014 / 0.5p0111 / 0.5p014 / 0.5p014 / 0.5p054 / 0.5p0511 / 0.5p054 / 0.5p01
Ice Lake10 / 0.5p014 / 0.5p0111 / 0.5p014 / 0.5p014 / 1p04 / 1p011 / 1p04 / 0.5p01
Alder Lake10 / 0.5p153 / 0.5p1511 / 0.5p153 / 0.5p15
Sapphire Rapids10 / 0.5p153 / 0.5p1511 / 0.5p153 / 0.5p153 / 0.5p054 / 0.5p0511 / 0.5p054 / 0.5p15
Lunar Lake10 / 0.5V2 V33 / 0.5V2 V311 / 0.5V2 V33 / 0.5V2 V3
Piledriver10 / 1.5FPFMA FPU05 / 1FPFMA FPU010 / 1.5FPFMA FPU05 / 1FPFMA FPU0
Zen10 / 0.5FPU2 FPU33 / 0.5FPU2 FPU310 / 1FPU2 FPU33 / 1FPU2 FPU3
Zen 210 / 0.5FPU2 FPU33 / 0.5FPU2 FPU310 / 0.5FPU2 FPU33 / 0.5FPU2 FPU3
Zen 310 / 0.5FP2 FP33 / 0.5FP2 FP310 / 0.5FP2 FP33 / 0.5FP2 FP3
Zen 410 / 0.5FP2 FP33 / 0.5FP2 FP310 / 0.5FP2 FP33 / 0.5FP2 FP33 / 1FP2 FP33 / 1FP2 FP310 / 1FP2 FP33 / 0.5FP2 FP3
Jaguar8 / 1FPA FPU03 / 1FPA FPU08 / 2FPA FPU03 / 2FPA FPU0

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.

Element-wise: each single of the result comes from the single in the same place in each source.
VADDPS: element by elementResult single i comes from single i of xmm2 and xmm3. Result singles 3 to 0: a3+b3, unchanged (bit 2 of k1 is 0), a1+b1, a0+b0.0123xmm2a1110k1a0+b0a1+b1a3+b3xmm10123xmm3or m128b

Every single works alike: 4, 8 and 16 singles in the xmm, ymm and zmm forms. The EVEX forms write under a mask: where its bit is 0, the element keeps its old value, or zeroes it with {z}. With m32bcst, one single from memory stands for every element of the last source.

Result single i comes from single i of xmm2 and xmm3. Result singles 3 to 0: a3+b3, unchanged (bit 2 of k1 is 0), a1+b1, a0+b0.

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
        a = zmm2.f32[i]
        b = src3.f32[i]
        zmm1.f32[i] = add(a, b)
    elif zeroing:
        zmm1.f32[i] = 0
    # else: zmm1.f32[i] keeps its value
# m32bcst: src3.f32[i] is the m32 for every i
# {er}: the form's rounding, not MXCSR.RC, and no flags
# zmm1 is zeroed from bit VL up

Run on AMD Zen 5 (EPYC 9645): 48 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
VADDPS xmm, xmm, xmm/m128 VADDPS ymm, ymm, ymm/m256
xmm, ymmexplicitwrite
xmm, ymmexplicitread
xmm/m128, ymm/m256explicitread
VADDPS xmm {k}{z}, xmm, xmm/m128/m32bcst VADDPS ymm {k}{z}, ymm, ymm/m256/m32bcst VADDPS zmm {k}{z}, zmm, zmm/m512/m32bcst, {er}
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm, ymm, zmmexplicitread
xmm/m128/m32bcst, ymm/m256/m32bcst, zmm/m512/m32bcstexplicitread

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-2
EVEX forms
AVX512-E2

Attributes

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

All forms
follows MXCSR
EVEX forms
write masking
EVEX memory forms
embedded broadcast (tuple Full); memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VADDPS, 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_add_ps __m128 _mm_add_ps(__m128 __a, __m128 __b)

VADDPS xmm, xmm, xmm VEX.128 -mavxwith AVX enabled

_mm_mask_add_ps __m128 _mm_mask_add_ps(__m128 __W, __mmask8 __U, __m128 __A, __m128 __B)

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

_mm_maskz_add_ps __m128 _mm_maskz_add_ps(__mmask8 __U, __m128 __A, __m128 __B)

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

_mm256_add_ps __m256 _mm256_add_ps(__m256 __a, __m256 __b)

VADDPS ymm, ymm, ymm VEX.256 -mavx

_mm256_mask_add_ps __m256 _mm256_mask_add_ps(__m256 __W, __mmask8 __U, __m256 __A, __m256 __B)

VADDPS ymm {k}, ymm, ymm EVEX.256 -mavx512vl

_mm256_maskz_add_ps __m256 _mm256_maskz_add_ps(__mmask8 __U, __m256 __A, __m256 __B)

VADDPS ymm {k}{z}, ymm, ymm EVEX.256 -mavx512vl

_mm512_add_ps __m512 _mm512_add_ps(__m512 __a, __m512 __b)

VADDPS zmm, zmm, zmm EVEX.512 -mavx512f

_mm512_add_round_ps __m512 _mm512_add_round_ps(__m512 A, __m512 B, const int R)

VADDPS zmm, zmm, zmm, {er} EVEX.512 -mavx512f

_mm512_mask_add_ps __m512 _mm512_mask_add_ps(__m512 __W, __mmask16 __U, __m512 __A, __m512 __B)

VADDPS zmm {k}, zmm, zmm EVEX.512 -mavx512f

_mm512_mask_add_round_ps __m512 _mm512_mask_add_round_ps(__m512 W, __mmask16 U, __m512 A, __m512 B, const int R)

VADDPS zmm {k}, zmm, zmm, {er} EVEX.512 -mavx512f

_mm512_maskz_add_ps __m512 _mm512_maskz_add_ps(__mmask16 __U, __m512 __A, __m512 __B)

VADDPS zmm {k}{z}, zmm, zmm EVEX.512 -mavx512f

_mm512_maskz_add_round_ps __m512 _mm512_maskz_add_round_ps(__mmask16 U, __m512 A, __m512 B, const int R)

VADDPS zmm {k}{z}, zmm, zmm, {er} 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
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 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 2A, page 3-19 (ADDPS)
  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. 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.