Instruction
VDIVPS
Divides packed singles.
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
- Vectors on all parts: Division and square root are pipelined, and 256-bit forms have the latency of 128-bit ones: LLVM’s models give DIVPS 11 cycles, SQRTPS 12, DIVPD 14 and SQRTPD 18.
Forms
| Instruction | Encoding | Requires |
|---|---|---|
VDIVPS xmm, xmm, m128
VDIVPS_XMMdq_XMMdq_MEMdq | VEX.128.NP.0F.WIG 5E /r | AVX |
VDIVPS xmm, xmm, xmm
VDIVPS_XMMdq_XMMdq_XMMdq | VEX.128.NP.0F.WIG 5E /r | AVX |
VDIVPS ymm, ymm, m256
VDIVPS_YMMqq_YMMqq_MEMqq | VEX.256.NP.0F.WIG 5E /r | AVX |
VDIVPS ymm, ymm, ymm
VDIVPS_YMMqq_YMMqq_YMMqq | VEX.256.NP.0F.WIG 5E /r | AVX |
VDIVPS zmm {k}{z}, zmm, zmm, {er}
VDIVPS_ZMMf32_MASKmskw_ZMMf32_ZMMf32_AVX512 | EVEX.512.NP.0F.W0 5E /r | AVX10.1 or AVX512F |
VDIVPS zmm {k}{z}, zmm, m512/m32bcst
VDIVPS_ZMMf32_MASKmskw_ZMMf32_MEMf32_AVX512 | EVEX.512.NP.0F.W0 5E /r | AVX10.1 or AVX512F |
VDIVPS xmm {k}{z}, xmm, xmm
VDIVPS_XMMf32_MASKmskw_XMMf32_XMMf32_AVX512 | EVEX.128.NP.0F.W0 5E /r | AVX10.1 or AVX512F + AVX512VL |
VDIVPS xmm {k}{z}, xmm, m128/m32bcst
VDIVPS_XMMf32_MASKmskw_XMMf32_MEMf32_AVX512 | EVEX.128.NP.0F.W0 5E /r | AVX10.1 or AVX512F + AVX512VL |
VDIVPS ymm {k}{z}, ymm, ymm
VDIVPS_YMMf32_MASKmskw_YMMf32_YMMf32_AVX512 | EVEX.256.NP.0F.W0 5E /r | AVX10.1 or AVX512F + AVX512VL |
VDIVPS ymm {k}{z}, ymm, m256/m32bcst
VDIVPS_YMMf32_MASKmskw_YMMf32_MEMf32_AVX512 | EVEX.256.NP.0F.W0 5E /r | AVX10.1 or AVX512F + AVX512VL |
Latency and throughput
| Model | xmm, xmm, m128xmm {k}{z}, xmm, m128/m32bcst | xmm, xmm, xmmxmm {k}{z}, xmm, xmm | ymm, ymm, m256ymm {k}{z}, ymm, m256/m32bcst | ymm, ymm, ymmymm {k}{z}, ymm, ymm | zmm {k}{z}, zmm, zmm, {er}no mask | zmm {k}{z}, zmm, zmm, {er}with a mask, zeroing, with {er} | zmm {k}{z}, zmm, m512/m32bcst |
|---|---|---|---|---|---|---|---|
| Sandy Bridge | 20 / 14SBFPDivider p0 | 14 / 14SBFPDivider p0 | 36 / 28SBFPDivider p0 p5 | 29 / 28SBFPDivider p0 p5 | |||
| Haswell | 19 / 7HWFPDivider p0 | 13 / 7HWFPDivider p0 | 28 / 14HWFPDivider p0 p1 p5 | 21 / 14HWFPDivider p0 p1 p5 | |||
| Broadwell | 16 / 5BWFPDivider p0 | 11 / 5BWFPDivider p0 | 23 / 10BWFPDivider p0 p1 p5 | 17 / 10BWFPDivider p0 p1 p5 | |||
| Skylake | 17 / 3SKLFPDivider p0 | 11 / 3SKLFPDivider p0 | 18 / 5SKLFPDivider p0 | 11 / 5SKLFPDivider p0 | |||
| Skylake-SP | 17 / 3SKXFPDivider p0 | 11 / 3SKXFPDivider p0 | 18 / 5SKXFPDivider p0 | 11 / 5SKXFPDivider p0 | 18 / 10SKXFPDivider p0 p5 | 18 / 10SKXFPDivider p0 p5 | 25 / 10SKXFPDivider p0 p5 |
| Ice Lake | 17 / 3ICXFPDivider p0 | 11 / 3ICXFPDivider p0 | 18 / 5ICXFPDivider p0 | 11 / 5ICXFPDivider p0 | 18 / 10ICXFPDivider p0 p5 | 18 / 10ICXFPDivider p0 p5 | 25 / 10ICXFPDivider p0 p5 |
| Alder Lake | 18 / 1p0 | 11 / 1p0 | 19 / 1p0 | 11 / 1p0 | |||
| Sapphire Rapids | 18 / 1p0 | 11 / 1p0 | 19 / 1p0 | 11 / 1p0 | 17 / 2p05 | 18 / 2p05 | 25 / 2p05 |
| Lunar Lake | 13 / 3.5V0 V1 | 7 / 3.5V0 V1 | 14 / 3.5V0 V1 | 7 / 3.5V0 V1 | |||
| Piledriver | 14 / 4.5FPFMA FPU1 | 9 / 4.5FPFMA FPU1 | 14 / 9FPFMA FPU1 | 9 / 9FPFMA FPU1 | |||
| Zen | 17 / 3FPU3 | 10 / 3FPU3 | 17 / 6FPU3 | 10 / 6FPU3 | |||
| Zen 2 | 17 / 5FPU3 | 10 / 5FPU3 | 17 / 5FPU3 | 10 / 5FPU3 | |||
| Zen 3 | 18 / 3FP1 | 11 / 3FP1 | 18 / 3FP1 | 11 / 3FP1 | |||
| Zen 4 | 18 / 3FP1 | 11 / 31FP1 | 18 / 3FP1 | 11 / 32FP1 | 11 / 6FP1 | 11 / 6FP1 | 18 / 6FP1 |
| Jaguar | 24 / 19FPM FPU1 | 19 / 19FPM FPU1 | 43 / 38FPM FPU1 | 38 / 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.
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 upRun on AMD Zen 5 (EPYC 9645): 48 cases.
Operands
| Operand | Kind | Action |
|---|---|---|
VDIVPS xmm, xmm, xmm/m128 VDIVPS ymm, ymm, ymm/m256 | ||
xmm, ymm | explicit | write |
xmm, ymm | explicit | read |
xmm/m128, ymm/m256 | explicit | read |
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, zmm | explicit | write (masked) |
{k} | explicit | read (write mask) |
xmm, ymm, zmm | explicit | read |
xmm/m128/m32bcst, ymm/m256/m32bcst, zmm/m512/m32bcst | explicit | read |
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.
| Intrinsic | Compiles to |
|---|---|
_mm_div_ps
__m128 _mm_div_ps(__m128 __a, __m128 __b) |
|
_mm_mask_div_ps
__m128 _mm_mask_div_ps(__m128 __W, __mmask8 __U, __m128 __A, __m128 __B) |
|
_mm_maskz_div_ps
__m128 _mm_maskz_div_ps(__mmask8 __U, __m128 __A, __m128 __B) |
|
_mm256_div_ps
__m256 _mm256_div_ps(__m256 __a, __m256 __b) |
|
_mm256_mask_div_ps
__m256 _mm256_mask_div_ps(__m256 __W, __mmask8 __U, __m256 __A, __m256 __B) |
|
_mm256_maskz_div_ps
__m256 _mm256_maskz_div_ps(__mmask8 __U, __m256 __A, __m256 __B) |
|
_mm512_div_ps
__m512 _mm512_div_ps(__m512 __a, __m512 __b) |
|
_mm512_div_round_ps
__m512 _mm512_div_round_ps(__m512 A, __m512 B, const int R) |
|
_mm512_mask_div_ps
__m512 _mm512_mask_div_ps(__m512 __W, __mmask16 __U, __m512 __A, __m512 __B) |
|
_mm512_mask_div_round_ps
__m512 _mm512_mask_div_round_ps(__m512 W, __mmask16 U, __m512 A, __m512 B, const int R) |
|
_mm512_maskz_div_ps
__m512 _mm512_maskz_div_ps(__mmask16 __U, __m512 __A, __m512 __B) |
|
_mm512_maskz_div_round_ps
__m512 _mm512_maskz_div_round_ps(__mmask16 U, __m512 A, __m512 B, const int R) |
|
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.
More AVX instructions
- VCMPSS
- VCOMISD
- VCOMISS
- VCVTDQ2PD
- VCVTDQ2PS
- VCVTPD2DQ
- VCVTPD2PS
- VCVTPS2DQ
- VCVTPS2PD
- VCVTSD2SI
- VCVTSD2SS
- VCVTSI2SD
- VCVTSI2SS
- VCVTSS2SD
- VCVTSS2SI
- VCVTTPD2DQ
- VCVTTPS2DQ
- VCVTTSD2SI
- VCVTTSS2SI
- VDIVPD
- VDIVSD
- VDIVSS
- VDPPD
- VDPPS
- VEXTRACTF128
- VEXTRACTPS
- VHADDPD
- VHADDPS
- VHSUBPD
- VHSUBPS
- VINSERTF128
- VINSERTPS
- VLDDQU
- VLDMXCSR
- VMASKMOVDQU
- VMASKMOVPD
- VMASKMOVPS
- VMAXPD
- VMAXPS
- VMAXSD
More AVX10.1 instructions
- VCVTTSD2SI
- VCVTTSD2USI
- VCVTTSH2SI
- VCVTTSH2USI
- VCVTTSS2SI
- VCVTTSS2USI
- VCVTUDQ2PD
- VCVTUDQ2PH
- VCVTUDQ2PS
- VCVTUQQ2PD
- VCVTUQQ2PH
- VCVTUQQ2PS
- VCVTUSI2SD
- VCVTUSI2SH
- VCVTUSI2SS
- VCVTUW2PH
- VCVTW2PH
- VDBPSADBW
- VDIVPD
- VDIVPH
- VDIVSD
- VDIVSH
- VDIVSS
- VDPBF16PS
- VEXPANDPD
- VEXPANDPS
- VEXTRACTF32X4
- VEXTRACTF32X8
- VEXTRACTF64X2
- VEXTRACTF64X4
- VEXTRACTI32X4
- VEXTRACTI32X8
- VEXTRACTI64X2
- VEXTRACTI64X4
- VEXTRACTPS
- VFCMADDCPH
- VFCMADDCSH
- VFCMULCPH
- VFCMULCSH
- VFIXUPIMMPD
Sources
- Intel XED v2026.08.23 (commit
0bcb6237345c): forms, encodings, operands, flags, exception classes, attributes, ISA sets, CPUID bits and chip model. - The CPU data of x86-64.net: Zen 3 to Zen 6, from GCC’s
-marchfeature sets and AMD’s Processor Programming References, which the page of each processor cites. - 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. - LLVM 23.1.2's x86 scheduling models (commit
85ac56026243): the latency, reciprocal throughput and ports of each form, as llvm-mca reports them. - Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2A, page 3-270 (DIVPS)
- Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 1 (253665-093, September 2026)
- Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
- 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.