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

VDIVPD divides doubles, two, four or eight at a time, and is DIVPD in VEX and EVEX encodings. VDIVPS covers what the encodings add and how compilers trade a division of singles for an estimate; doubles are a different story.

No shortcut for doubles

With -ffast-math, GCC 14 and Clang 23 at -O2 replace a division of floats by a reciprocal estimate and a Newton-Raphson step, but for a[i] = b[i] / c[i] over doubles they keep VDIVPD: on ymm registers for -march=x86-64-v3, on zmm for znver5, and for -march=x86-64-v4 on zmm in GCC and ymm in Clang. The estimates that exist for doubles, VRCP14PD among them, have a relative error of up to 2^-14, too far from a double’s 53 bits for one refining step. A division by a constant is another matter: see VMULPD.

Zero, infinity and DAZ

The cases recorded on Zen 5 tell the invalid operation from a division by zero. 0/0 and -0/0 gave the indefinite FFF8000000000000H and set the invalid flag; a finite number over zero gave an infinity of the quotient’s sign and set the divide-by-zero flag; an infinity over zero gave infinity with neither. With DAZ set, a denormal divided by zero counted as 0/0 and gave the indefinite, not an infinity. Under {rd-sae}, the largest denormal divided by -2^-1023 gave its exact quotient, -1.9999999999999996, and no flag changed although MXCSR unmasked the denormal exception.

On Zen 5

AMD’s Zen 5 guide gives VDIVPD a latency of 13 cycles and a throughput of 0.25 per cycle at every width, against 10 cycles and 0.4 for VDIVPS, in the same divide unit on pipe FP1: a zmm VDIVPD delivers at most two quotients per cycle.

In the optimization guide

What the optimization guide says about VDIVPD, 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 VDIVPD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VDIVPD xmm, xmm, m128 VDIVPD_XMMdq_XMMdq_MEMdqVEX.128.66.0F.WIG 5E /rAVX
VDIVPD xmm, xmm, xmm VDIVPD_XMMdq_XMMdq_XMMdqVEX.128.66.0F.WIG 5E /rAVX
VDIVPD ymm, ymm, m256 VDIVPD_YMMqq_YMMqq_MEMqqVEX.256.66.0F.WIG 5E /rAVX
VDIVPD ymm, ymm, ymm VDIVPD_YMMqq_YMMqq_YMMqqVEX.256.66.0F.WIG 5E /rAVX
VDIVPD zmm {k}{z}, zmm, zmm, {er} VDIVPD_ZMMf64_MASKmskw_ZMMf64_ZMMf64_AVX512EVEX.512.66.0F.W1 5E /rAVX10.1 or AVX512F
VDIVPD zmm {k}{z}, zmm, m512/m64bcst VDIVPD_ZMMf64_MASKmskw_ZMMf64_MEMf64_AVX512EVEX.512.66.0F.W1 5E /rAVX10.1 or AVX512F
VDIVPD xmm {k}{z}, xmm, xmm VDIVPD_XMMf64_MASKmskw_XMMf64_XMMf64_AVX512EVEX.128.66.0F.W1 5E /rAVX10.1 or AVX512F + AVX512VL
VDIVPD xmm {k}{z}, xmm, m128/m64bcst VDIVPD_XMMf64_MASKmskw_XMMf64_MEMf64_AVX512EVEX.128.66.0F.W1 5E /rAVX10.1 or AVX512F + AVX512VL
VDIVPD ymm {k}{z}, ymm, ymm VDIVPD_YMMf64_MASKmskw_YMMf64_YMMf64_AVX512EVEX.256.66.0F.W1 5E /rAVX10.1 or AVX512F + AVX512VL
VDIVPD ymm {k}{z}, ymm, m256/m64bcst VDIVPD_YMMf64_MASKmskw_YMMf64_MEMf64_AVX512EVEX.256.66.0F.W1 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/m64bcst
xmm, xmm, xmm
xmm {k}{z}, xmm, xmm
ymm, ymm, m256
ymm {k}{z}, ymm, m256/m64bcst
ymm, ymm, ymm
ymm {k}{z}, ymm, ymm
zmm {k}{z}, zmm, zmm, {er}zmm {k}{z}, zmm, m512/m64bcst
Sandy Bridge28 / 22SBFPDivider p022 / 22SBFPDivider p052 / 44SBFPDivider p0 p545 / 44SBFPDivider p0 p5
Haswell26 / 14HWFPDivider p020 / 14HWFPDivider p042 / 28HWFPDivider p0 p1 p535 / 28HWFPDivider p0 p1 p5
Broadwell19 / 8BWFPDivider p014 / 8BWFPDivider p029 / 16BWFPDivider p0 p1 p523 / 16BWFPDivider p0 p1 p5
Skylake20 / 4SKLFPDivider p014 / 4SKLFPDivider p021 / 8SKLFPDivider p014 / 8SKLFPDivider p0
Skylake-SP20 / 4SKXFPDivider p014 / 4SKXFPDivider p021 / 8SKXFPDivider p014 / 8SKXFPDivider p023 / 16SKXFPDivider p0 p530 / 16SKXFPDivider p0 p5
Ice Lake20 / 4ICXFPDivider p014 / 4ICXFPDivider p021 / 8ICXFPDivider p014 / 8ICXFPDivider p023 / 16ICXFPDivider p0 p530 / 16ICXFPDivider p0 p5
Alder Lake20 / 1p014 / 1p021 / 1p014 / 1p0
Sapphire Rapids20 / 1p014 / 1p021 / 1p014 / 1p023 / 2p0530 / 2p05
Lunar Lake16 / 5V0 V110 / 5V0 V117 / 5V0 V110 / 5V0 V1
Piledriver14 / 4.5FPFMA FPU19 / 4.5FPFMA FPU114 / 9FPFMA FPU19 / 9FPFMA FPU1
Zen20 / 5FPU313 / 5FPU322 / 9FPU315 / 9FPU3
Zen 220 / 6FPU313 / 6FPU320 / 6FPU313 / 6FPU3
Zen 320 / 5FP113 / 5FP120 / 5FP113 / 5FP1
Zen 420 / 5FP113 / 5FP120 / 5FP113 / 5FP113 / 10FP120 / 10FP1
Jaguar24 / 19FPM FPU119 / 19FPM FPU143 / 38FPM FPU138 / 38FPM FPU1

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 double of the result comes from the double in the same place in each source.
VDIVPD: element by elementResult double i comes from double i of xmm2 and xmm3. Result doubles 1 to 0: a1/b1, a0/b0.01xmm2a11k1a0/b0a1/b1xmm101xmm3or m128b

Every double works alike: 2, 4 and 8 doubles 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 m64bcst, one double from memory stands for every element of the last source.

Result double i comes from double i of xmm2 and xmm3. Result doubles 1 to 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 // 64):
    if k1[i]:  # 1 without a write mask
        a = zmm2.f64[i]
        b = src3.f64[i]
        zmm1.f64[i] = div(a, b)
    elif zeroing:
        zmm1.f64[i] = 0
    # else: zmm1.f64[i] keeps its value
# m64bcst: src3.f64[i] is the m64 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): 15 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
VDIVPD xmm, xmm, xmm/m128 VDIVPD ymm, ymm, ymm/m256
xmm, ymmexplicitwrite
xmm, ymmexplicitread
xmm/m128, ymm/m256explicitread
VDIVPD xmm {k}{z}, xmm, xmm/m128/m64bcst VDIVPD ymm {k}{z}, ymm, ymm/m256/m64bcst VDIVPD zmm {k}{z}, zmm, zmm/m512/m64bcst, {er}
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm, ymm, zmmexplicitread
xmm/m128/m64bcst, ymm/m256/m64bcst, zmm/m512/m64bcstexplicitread

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 VDIVPD, 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_pd __m128d _mm_div_pd(__m128d __a, __m128d __b)

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

_mm_mask_div_pd __m128d _mm_mask_div_pd(__m128d __W, __mmask8 __U, __m128d __A, __m128d __B)

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

_mm_maskz_div_pd __m128d _mm_maskz_div_pd(__mmask8 __U, __m128d __A, __m128d __B)

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

_mm256_div_pd __m256d _mm256_div_pd(__m256d __a, __m256d __b)

VDIVPD ymm, ymm, ymm VEX.256 -mavx

_mm256_mask_div_pd __m256d _mm256_mask_div_pd(__m256d __W, __mmask8 __U, __m256d __A, __m256d __B)

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

_mm256_maskz_div_pd __m256d _mm256_maskz_div_pd(__mmask8 __U, __m256d __A, __m256d __B)

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

_mm512_div_pd __m512d _mm512_div_pd(__m512d __a, __m512d __b)

VDIVPD zmm, zmm, zmm EVEX.512 -mavx512f

_mm512_div_round_pd __m512d _mm512_div_round_pd(__m512d A, __m512d B, const int R)

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

_mm512_mask_div_pd __m512d _mm512_mask_div_pd(__m512d __W, __mmask8 __U, __m512d __A, __m512d __B)

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

_mm512_mask_div_round_pd __m512d _mm512_mask_div_round_pd(__m512d W, __mmask8 U, __m512d A, __m512d B, const int R)

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

_mm512_maskz_div_pd __m512d _mm512_maskz_div_pd(__mmask8 __U, __m512d __A, __m512d __B)

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

_mm512_maskz_div_round_pd __m512d _mm512_maskz_div_round_pd(__mmask8 U, __m512d A, __m512d B, const int R)

VDIVPD 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-267 (DIVPD)
  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.