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

VDIVPS is DIVPS in VEX and EVEX encodings. The DIVPS page covers division by zero against the invalid 0/0, the history of its speed and why compilers replace it; the VEX forms add a separate destination and 256 bits, and the EVEX forms 512 bits, masking, a broadcast single and a rounding mode given in the instruction. On Zen 5, 1 divided by 1.5 times 2^-24 gave 11184811 under MXCSR’s round to nearest and 11184810 under {rz-sae}, which also leaves MXCSR’s flags alone.

Approximations by target

Without -ffast-math, GCC 14 and Clang 23 at -O2 keep a[i] = b[i] / c[i] a division: VDIVPS on ymm registers for -march=x86-64-v3, on zmm for znver5, and with -march=x86-64-v4 on zmm in GCC and ymm in Clang. With -ffast-math both turn it into an estimate of 1/c[i] and a Newton-Raphson step, but in different ways:

  • GCC refines the reciprocal first, as 2r - r * r * c, with VMULPS, VADDPS and VSUBPS, then multiplies by b[i]; it uses no FMA even where the target has it.
  • Clang multiplies the estimate by b[i] first and corrects that quotient with VFMSUB213PS and VFNMADD213PS.

The estimate is VRCPPS on ymm registers, which is why Clang uses it for x86-64-v4 too, and VRCP14PS on zmm registers: GCC for x86-64-v4 and both for znver5. Intel’s manual bounds their relative error by 1.5 times 2^-12 and by 2^-14, so even after the Newton-Raphson step the quotients are approximate and can differ from VDIVPS’s correctly rounded ones in the last bits.

On Zen 5

AMD’s Zen 5 guide lists VDIVPS with a latency of 10 cycles and a throughput of 0.4 per cycle for xmm, ymm and zmm registers alike, so a zmm division delivers four times the quotients of an xmm one in the same time. Its one divide unit also runs every square root (Section 2.11.1), so VSQRTPS competes with VDIVPS for it.

In the optimization guide

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

Haswell and Broadwell

  • AVX2 and FMA: Apart from division, square root, AES and the SSE4.2 string compares, the vector units are 256 bits wide. sources differ

Skylake to Cooper Lake

Forms

Every encoding of VDIVPS that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VDIVPS xmm, xmm, m128 VDIVPS_XMMdq_XMMdq_MEMdqVEX.128.NP.0F.WIG 5E /rAVX
VDIVPS xmm, xmm, xmm VDIVPS_XMMdq_XMMdq_XMMdqVEX.128.NP.0F.WIG 5E /rAVX
VDIVPS ymm, ymm, m256 VDIVPS_YMMqq_YMMqq_MEMqqVEX.256.NP.0F.WIG 5E /rAVX
VDIVPS ymm, ymm, ymm VDIVPS_YMMqq_YMMqq_YMMqqVEX.256.NP.0F.WIG 5E /rAVX
VDIVPS zmm {k}{z}, zmm, zmm, {er} VDIVPS_ZMMf32_MASKmskw_ZMMf32_ZMMf32_AVX512EVEX.512.NP.0F.W0 5E /rAVX10.1 or AVX512F
VDIVPS zmm {k}{z}, zmm, m512/m32bcst VDIVPS_ZMMf32_MASKmskw_ZMMf32_MEMf32_AVX512EVEX.512.NP.0F.W0 5E /rAVX10.1 or AVX512F
VDIVPS xmm {k}{z}, xmm, xmm VDIVPS_XMMf32_MASKmskw_XMMf32_XMMf32_AVX512EVEX.128.NP.0F.W0 5E /rAVX10.1 or AVX512F + AVX512VL
VDIVPS xmm {k}{z}, xmm, m128/m32bcst VDIVPS_XMMf32_MASKmskw_XMMf32_MEMf32_AVX512EVEX.128.NP.0F.W0 5E /rAVX10.1 or AVX512F + AVX512VL
VDIVPS ymm {k}{z}, ymm, ymm VDIVPS_YMMf32_MASKmskw_YMMf32_YMMf32_AVX512EVEX.256.NP.0F.W0 5E /rAVX10.1 or AVX512F + AVX512VL
VDIVPS ymm {k}{z}, ymm, m256/m32bcst VDIVPS_YMMf32_MASKmskw_YMMf32_MEMf32_AVX512EVEX.256.NP.0F.W0 5E /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, xmm
ymm, ymm, m256
ymm {k}{z}, ymm, m256/m32bcst
ymm, ymm, ymm
ymm {k}{z}, ymm, ymm
zmm {k}{z}, zmm, zmm, {er}no maskzmm {k}{z}, zmm, zmm, {er}with a mask, zeroing, with {er}zmm {k}{z}, zmm, m512/m32bcst
Sandy Bridge20 / 14SBFPDivider p014 / 14SBFPDivider p036 / 28SBFPDivider p0 p529 / 28SBFPDivider p0 p5
Haswell19 / 7HWFPDivider p013 / 7HWFPDivider p028 / 14HWFPDivider p0 p1 p521 / 14HWFPDivider p0 p1 p5
Broadwell16 / 5BWFPDivider p011 / 5BWFPDivider p023 / 10BWFPDivider p0 p1 p517 / 10BWFPDivider p0 p1 p5
Skylake17 / 3SKLFPDivider p011 / 3SKLFPDivider p018 / 5SKLFPDivider p011 / 5SKLFPDivider p0
Skylake-SP17 / 3SKXFPDivider p011 / 3SKXFPDivider p018 / 5SKXFPDivider p011 / 5SKXFPDivider p018 / 10SKXFPDivider p0 p518 / 10SKXFPDivider p0 p525 / 10SKXFPDivider p0 p5
Ice Lake17 / 3ICXFPDivider p011 / 3ICXFPDivider p018 / 5ICXFPDivider p011 / 5ICXFPDivider p018 / 10ICXFPDivider p0 p518 / 10ICXFPDivider p0 p525 / 10ICXFPDivider p0 p5
Alder Lake18 / 1p011 / 1p019 / 1p011 / 1p0
Sapphire Rapids18 / 1p011 / 1p019 / 1p011 / 1p017 / 2p0518 / 2p0525 / 2p05
Lunar Lake13 / 3.5V0 V17 / 3.5V0 V114 / 3.5V0 V17 / 3.5V0 V1
Piledriver14 / 4.5FPFMA FPU19 / 4.5FPFMA FPU114 / 9FPFMA FPU19 / 9FPFMA FPU1
Zen17 / 3FPU310 / 3FPU317 / 6FPU310 / 6FPU3
Zen 217 / 5FPU310 / 5FPU317 / 5FPU310 / 5FPU3
Zen 318 / 3FP111 / 3FP118 / 3FP111 / 3FP1
Zen 418 / 3FP111 / 31FP118 / 3FP111 / 32FP111 / 6FP111 / 6FP118 / 6FP1
Jaguar24 / 19FPM FPU119 / 19FPM FPU143 / 38FPM FPU138 / 38FPM FPU1
  1. Zen 4 model: AMD's spreadsheets give latency 10 for Zen 4 and Zen 5 (AMD 57647, row 1110; AMD 58455, row 1080).
  2. Zen 4 model: AMD's spreadsheets give latency 10 for Zen 4 and Zen 5 (AMD 57647, row 1112; AMD 58455, row 1080).

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.
VDIVPS: 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] = div(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
VDIVPS xmm, xmm, xmm/m128 VDIVPS ymm, ymm, ymm/m256
xmm, ymmexplicitwrite
xmm, ymmexplicitread
xmm/m128, ymm/m256explicitread
VDIVPS xmm {k}{z}, xmm, xmm/m128/m32bcst VDIVPS ymm {k}{z}, ymm, ymm/m256/m32bcst VDIVPS 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 VDIVPS, 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_div_ps __m128 _mm_div_ps(__m128 __a, __m128 __b)

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

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

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

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

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

_mm256_div_ps __m256 _mm256_div_ps(__m256 __a, __m256 __b)

VDIVPS ymm, ymm, ymm VEX.256 -mavx

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

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

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

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

_mm512_div_ps __m512 _mm512_div_ps(__m512 __a, __m512 __b)

VDIVPS zmm, zmm, zmm EVEX.512 -mavx512f

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

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

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

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

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

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

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

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

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

VDIVPS 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-270 (DIVPS)
  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.