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

VSQRTSD is SQRTSD in VEX and EVEX encodings: the root of the low double of its last operand, with the high double copied from the operand before it and the bits above 127 cleared. VSQRTSS covers what the encodings add, from the named source of the upper element to masking and a rounding mode on xmm registers; the SQRTSD page covers C’s sqrt and its errno test.

Which register gives the high double

In Zen 5’s recorded vsqrtsd xmm8, xmm15, xmm0, under MXCSR 3FC0H (round down, DAZ set), XMM0 held -1 below and 2 above. The result was the indefinite FFF8000000000000H, with IE set, below and the high double of XMM15 above: the source of the root gives only its low element.

That operand order is the one of the intrinsic. _mm_sqrt_sd(a, b) returns the root of the low double of b with the high double of a, and Clang 23 compiles it to a single vsqrtsd xmm0, xmm0, xmm1 with -march=x86-64-v3 or x86-64-v4, while GCC 14 still copies the low double over with VMOVSD first and then takes the root in place, as it does for SQRTSD. For sqrt(x) both emit vsqrtsd xmm0, xmm0, xmm0 after the test for a negative x.

Suppressed exceptions

Zen 5’s EVEX cases:

  • vsqrtsd xmm7{k7}, xmm12, xmm7, {rz-sae}, with bit 0 of K7 set, took the root of -1 while MXCSR (6600H) left the invalid exception unmasked. The result was the indefinite, with no #XM and no flag set: {sae} suppresses both.
  • Without it, vsqrtsd xmm0{k4}{z}, xmm31, qword ptr [mem] took the root of -infinity under FFC0H and gave the indefinite with IE set, the high double coming from XMM31, a register only EVEX can name.

AMD’s latency spreadsheet for Zen 5 lists it at 20 cycles and 0.133 per cycle on pipe FP1, against 14 cycles for VSQRTSS.

Forms

Every encoding of VSQRTSD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VSQRTSD xmm, xmm, m64 VSQRTSD_XMMdq_XMMdq_MEMqVEX.LIG.F2.0F.WIG 51 /rAVX
VSQRTSD xmm, xmm, xmm VSQRTSD_XMMdq_XMMdq_XMMqVEX.LIG.F2.0F.WIG 51 /rAVX
VSQRTSD xmm {k}{z}, xmm, xmm, {er} VSQRTSD_XMMf64_MASKmskw_XMMf64_XMMf64_AVX512EVEX.LIG.F2.0F.W1 51 /rAVX10.1 or AVX512F
VSQRTSD xmm {k}{z}, xmm, m64 VSQRTSD_XMMf64_MASKmskw_XMMf64_MEMf64_AVX512EVEX.LIG.F2.0F.W1 51 /rAVX10.1 or AVX512F

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, m64
xmm {k}{z}, xmm, m64no mask
xmm, xmm, xmm
xmm {k}{z}, xmm, xmm, {er}
xmm {k}{z}, xmm, m64with a mask, zeroing
Sandy Bridge27 / 21SBFPDivider p021 / 21SBFPDivider p0
Haswell21 / 14HWFPDivider p016 / 14HWFPDivider p0
Broadwell21 / 14BWFPDivider p016 / 8BWFPDivider p0
Skylake23 / 6SKLFPDivider p018 / 6SKLFPDivider p0
Skylake-SP23 / 6SKXFPDivider p018 / 6SKXFPDivider p023 / 6SKXFPDivider p0
Ice Lake23 / 6ICXFPDivider p018 / 6ICXFPDivider p023 / 6ICXFPDivider p0
Alder Lake24 / 1p018 / 1p0
Sapphire Rapids24 / 1p018 / 1p020 / 1p0
Lunar Lake24 / 1p015 / 7.5V0 V1
Piledriver14 / 4.5FPFMA FPU19 / 4.5FPFMA FPU1
Zen27 / 8FPU320 / 8FPU3
Zen 227 / 10FPU320 / 10FPU3
Zen 328 / 9FP121 / 9FP1
Zen 428 / 9FP121 / 9FP128 / 9FP1
Jaguar32 / 27FPM FPU127 / 27FPM 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.

Scalar: only the low double is computed; the other double comes from xmm2.
VSQRTSD: the low elementResult double 0 is computed from double 0 of xmm3; double 1 is that of xmm2. Result doubles 1 to 0: a1, r0.01xmm2a1k1r0a1xmm101xmm3or m64b

The write mask k1 applies to the low double: with bit 0 clear it keeps its old value, or is zeroed with {z}.

Result double 0 is computed from double 0 of xmm3; double 1 is that of xmm2. Result doubles 1 to 0: a1, r0.

Operation

What the forms do, in pseudocode that our tests run against results recorded on real processors. How to read.

if k1[0]:  # 1 without a write mask
    xmm1.f64[0] = sqrt(src3.f64[0])
elif zeroing:
    xmm1.f64[0] = 0
# else: xmm1.f64[0] keeps its value
xmm1.q[1] = xmm2.q[1]
# {er}: the form's rounding, not MXCSR.RC, and no flags
# xmm1 is zeroed from bit 128 up

Run on AMD Zen 5 (EPYC 9645): 6 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
VSQRTSD xmm, xmm, xmm/m64
xmmexplicitwrite
xmmexplicitread
xmm/m64explicitread
VSQRTSD xmm {k}{z}, xmm, xmm/m64, {er}
xmmexplicitwrite (masked)
{k}explicitread (write mask)
xmmexplicitread
xmm/m64explicitread

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-3
EVEX forms
AVX512-E3

Attributes

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

All forms
follows MXCSR
EVEX forms
write masking
EVEX memory forms
memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VSQRTSD, 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_round_sd __m128d _mm_sqrt_round_sd(__m128d A, __m128d B, const int R)

VSQRTSD xmm, xmm, xmm, {er} EVEX.LIG -mavx512f

_mm_sqrt_sd __m128d _mm_sqrt_sd(__m128d __a, __m128d __b)

VSQRTSD xmm, xmm, xmm VEX.LIG -mavxwith AVX enabled

_mm_mask_sqrt_round_sd __m128d _mm_mask_sqrt_round_sd(__m128d W, __mmask8 U, __m128d A, __m128d B, const int R)

VSQRTSD xmm {k}, xmm, xmm, {er} EVEX.LIG -mavx512f

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

VSQRTSD xmm {k}, xmm, xmm EVEX.LIG -mavx512f

_mm_maskz_sqrt_round_sd __m128d _mm_maskz_sqrt_round_sd(__mmask8 U, __m128d A, __m128d B, const int R)

VSQRTSD xmm {k}{z}, xmm, xmm, {er} EVEX.LIG -mavx512f

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

VSQRTSD xmm {k}{z}, xmm, xmm EVEX.LIG -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.

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-667 (SQRTSD)
  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.