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

VSQRTPS is SQRTPS in VEX and EVEX encodings. The SQRTPS page covers the special inputs, C’s errno and the history of its speed; the VEX forms add a separate destination and 256 bits, the EVEX forms 512 bits, masking, a broadcast single and a rounding mode given in the instruction. On Zen 5, {ru-sae} took the root of 2 to 1.41421366, the single just above the true value, where rounding to nearest gives 1.41421354, and set no flag although the result was inexact.

What compilers emit

The loop a[i] = sqrtf(b[i]) stays scalar at -O2 in GCC 14 and Clang 23 unless errno is out of the way. With -fno-math-errno it becomes VSQRTPS on ymm registers for -march=x86-64-v3, on zmm for -march=znver5, and for -march=x86-64-v4 on zmm in GCC and ymm in Clang. A reciprocal root, 1.0f / sqrtf(b[i]), becomes VSQRTPS and VDIVPS for each of these targets.

-ffast-math lets them use an estimate instead, and here the compilers part ways:

  • For -march=x86-64-v3, both compute the root as x times VRSQRTPS’s estimate of 1/sqrt(x), refined by one Newton-Raphson step with an FMA, and add a compare and a VANDPS so that 0 still gives 0 rather than 0 times infinity, a NaN.
  • For -march=x86-64-v4 and znver5, GCC does the same with VRSQRT14PS on zmm registers, while Clang keeps VSQRTPS.

Intel’s manual bounds the relative error of the two estimates by 1.5 times 2^-12 and by 2^-14, and the refined results are close but not correctly rounded, so a -ffast-math build can give different last bits from one without it, and GCC’s from Clang’s.

On Zen 5

AMD’s Zen 5 guide lists VSQRTPS with a latency of 14 cycles and a throughput of 0.222 per cycle at every width, in the same divide unit as VDIVPS (Section 2.11.1).

In the optimization guide

What the optimization guide says about VSQRTPS, 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 VSQRTPS that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VSQRTPS xmm, m128 VSQRTPS_XMMdq_MEMdqVEX.128.NP.0F.WIG 51 /rAVX
VSQRTPS xmm, xmm VSQRTPS_XMMdq_XMMdqVEX.128.NP.0F.WIG 51 /rAVX
VSQRTPS ymm, m256 VSQRTPS_YMMqq_MEMqqVEX.256.NP.0F.WIG 51 /rAVX
VSQRTPS ymm, ymm VSQRTPS_YMMqq_YMMqqVEX.256.NP.0F.WIG 51 /rAVX
VSQRTPS zmm {k}{z}, zmm, {er} VSQRTPS_ZMMf32_MASKmskw_ZMMf32_AVX512EVEX.512.NP.0F.W0 51 /rAVX10.1 or AVX512F
VSQRTPS zmm {k}{z}, m512/m32bcst VSQRTPS_ZMMf32_MASKmskw_MEMf32_AVX512EVEX.512.NP.0F.W0 51 /rAVX10.1 or AVX512F
VSQRTPS xmm {k}{z}, xmm VSQRTPS_XMMf32_MASKmskw_XMMf32_AVX512EVEX.128.NP.0F.W0 51 /rAVX10.1 or AVX512F + AVX512VL
VSQRTPS xmm {k}{z}, m128/m32bcst VSQRTPS_XMMf32_MASKmskw_MEMf32_AVX512EVEX.128.NP.0F.W0 51 /rAVX10.1 or AVX512F + AVX512VL
VSQRTPS ymm {k}{z}, ymm VSQRTPS_YMMf32_MASKmskw_YMMf32_AVX512EVEX.256.NP.0F.W0 51 /rAVX10.1 or AVX512F + AVX512VL
VSQRTPS ymm {k}{z}, m256/m32bcst VSQRTPS_YMMf32_MASKmskw_MEMf32_AVX512EVEX.256.NP.0F.W0 51 /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, m128
xmm {k}{z}, m128/m32bcst
xmm, xmm
xmm {k}{z}, xmm
ymm, m256
ymm {k}{z}, m256/m32bcst
ymm, ymm
ymm {k}{z}, ymm
zmm {k}{z}, zmm, {er}no maskzmm {k}{z}, zmm, {er}with a mask, zeroing, with {er}zmm {k}{z}, m512/m32bcst
Sandy Bridge20 / 14SBFPDivider p014 / 14SBFPDivider p036 / 28SBFPDivider p0 p529 / 28SBFPDivider p0 p5
Haswell17 / 7HWFPDivider p011 / 7HWFPDivider p028 / 14HWFPDivider p0 p1 p521 / 14HWFPDivider p0 p1 p5
Broadwell16 / 7BWFPDivider p011 / 7BWFPDivider p027 / 14BWFPDivider p0 p1 p521 / 14BWFPDivider p0 p1 p5
Skylake18 / 3SKLFPDivider p012 / 3SKLFPDivider p019 / 6SKLFPDivider p012 / 6SKLFPDivider p0
Skylake-SP18 / 3SKXFPDivider p012 / 3SKXFPDivider p019 / 6SKXFPDivider p012 / 6SKXFPDivider p020 / 12SKXFPDivider p0 p520 / 12SKXFPDivider p0 p527 / 12SKXFPDivider p0 p5
Ice Lake18 / 3ICXFPDivider p012 / 3ICXFPDivider p019 / 6ICXFPDivider p012 / 6ICXFPDivider p020 / 12ICXFPDivider p0 p520 / 12ICXFPDivider p0 p527 / 12ICXFPDivider p0 p5
Alder Lake19 / 1p012 / 1p020 / 1p012 / 1p0
Sapphire Rapids19 / 1p012 / 1p020 / 1p012 / 1p019 / 2p0520 / 2p0527 / 2p05
Lunar Lake16 / 5V0 V110 / 5V0 V117 / 5V0 V110 / 5V0 V1
Piledriver14 / 4.5FPFMA FPU19 / 4.5FPFMA FPU114 / 9FPFMA FPU19 / 9FPFMA FPU1
Zen21 / 5FPU314 / 5FPU321 / 10FPU314 / 10FPU3
Zen 221 / 7FPU314 / 7FPU321 / 7FPU314 / 7FPU3
Zen 322 / 5FP115 / 5FP122 / 5FP115 / 5FP1
Zen 422 / 5FP115 / 5FP122 / 5FP115 / 5FP115 / 10FP115 / 10FP122 / 10FP1
Jaguar26 / 21FPM FPU121 / 21FPM FPU147 / 42FPM FPU142 / 42FPM 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 single of the result comes from the single in the same place in each source.
VSQRTPS: element by elementResult single i comes from single i of xmm2. Result singles 3 to 0: r3, unchanged (bit 2 of k1 is 0), r1, r0.0123xmm2or m128a1110k1r0r1r3xmm1

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. Result singles 3 to 0: r3, unchanged (bit 2 of k1 is 0), r1, r0.

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.f32[i] = sqrt(src2.f32[i])
    elif zeroing:
        zmm1.f32[i] = 0
    # else: zmm1.f32[i] keeps its value
# m32bcst: src2.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): 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
VSQRTPS xmm, xmm/m128 VSQRTPS ymm, ymm/m256
xmm, ymmexplicitwrite
xmm/m128, ymm/m256explicitread
VSQRTPS xmm {k}{z}, xmm/m128/m32bcst VSQRTPS ymm {k}{z}, ymm/m256/m32bcst VSQRTPS zmm {k}{z}, zmm/m512/m32bcst, {er}
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
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 VSQRTPS, 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_sqrt_ps __m128 _mm_sqrt_ps(__m128 __a)

VSQRTPS xmm, xmm VEX.128 -mavxwith AVX enabled

_mm_mask_sqrt_ps __m128 _mm_mask_sqrt_ps(__m128 __W, __mmask8 __U, __m128 __A)

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

_mm_maskz_sqrt_ps __m128 _mm_maskz_sqrt_ps(__mmask8 __U, __m128 __A)

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

_mm256_sqrt_ps __m256 _mm256_sqrt_ps(__m256 __a)

VSQRTPS ymm, ymm VEX.256 -mavx

_mm256_mask_sqrt_ps __m256 _mm256_mask_sqrt_ps(__m256 __W, __mmask8 __U, __m256 __A)

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

_mm256_maskz_sqrt_ps __m256 _mm256_maskz_sqrt_ps(__mmask8 __U, __m256 __A)

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

_mm512_sqrt_ps __m512 _mm512_sqrt_ps(__m512 __A)

VSQRTPS zmm, zmm EVEX.512 -mavx512f

_mm512_sqrt_round_ps __m512 _mm512_sqrt_round_ps(__m512 A, const int R)

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

_mm512_mask_sqrt_ps __m512 _mm512_mask_sqrt_ps(__m512 __W, __mmask16 __U, __m512 __A)

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

_mm512_mask_sqrt_round_ps __m512 _mm512_mask_sqrt_round_ps(__m512 W, __mmask16 U, __m512 A, const int R)

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

_mm512_maskz_sqrt_ps __m512 _mm512_maskz_sqrt_ps(__mmask16 __U, __m512 __A)

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

_mm512_maskz_sqrt_round_ps __m512 _mm512_maskz_sqrt_round_ps(__mmask16 U, __m512 A, const int R)

VSQRTPS zmm {k}{z}, 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 2B, page 4-664 (SQRTPS)
  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.