Extensions
Forms
6 (6 EVEX)
Data
Intel XED v2026.08.23

VSCALEFPD multiplies each double of the first source by 2 to the power of the matching double of the second, rounded down to an integer first: a times 2^floor(b), with a single rounding of the result. VSCALEFPS describes the operation for singles: the floor, the infinite scales that follow the limits, the quiet NaN scaled by an infinity, and its use with VGETEXP and VREDUCE for exponentials. With doubles the scale reaches further: a result can run from the smallest denormal, 2^-1074, to the largest finite double near 2^1024 before it underflows to zero or overflows to infinity.

Recorded on Zen 5

The cases recorded on Zen 5 show the floor on both sides of zero:

  • 1.0 scaled by -2.5 gave 0.125, and -3.0 scaled by -0.5 gave -1.5, since the floor of -0.5 is -1; 3.0 scaled by 0.5 stayed 3.0.
  • With a broadcast scale of -infinity, 1.0 became +0.0 and -0.0 stayed -0.0, while a signaling NaN in the first source came back quiet, 7FF8000000012345h, and set MXCSR’s IE flag.
  • +infinity and -infinity scaled by -infinity gave the default NaN FFF8000000000000h with IE, while +infinity scaled by +infinity stayed +infinity.
  • Under {rn-sae}, a quiet NaN scale was passed through and a signaling NaN source quieted, without a flag.

In compiled code

GCC 14 and Clang 23 at -O2 with -march=x86-64-v4 -ffast-math compile ldexp(a, e) to the scalar VSCALEFSD after converting e to a double, and a loop of ldexp over arrays stays scalar, one VSCALEFSD per element. GCC also compiles scalbn that way, where Clang calls the library. VSCALEFPD itself comes from _mm512_scalef_pd and its kin.

AMD’s latency spreadsheet for Zen 5 lists VSCALEFPD as VSCALEFPS: two macro-ops on FP2 and FP3.

Forms

Every encoding of VSCALEFPD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VSCALEFPD zmm {k}{z}, zmm, zmm, {er} VSCALEFPD_ZMMf64_MASKmskw_ZMMf64_ZMMf64_AVX512EVEX.512.66.0F38.W1 2C /rAVX10.1 or AVX512F
VSCALEFPD zmm {k}{z}, zmm, m512/m64bcst VSCALEFPD_ZMMf64_MASKmskw_ZMMf64_MEMf64_AVX512EVEX.512.66.0F38.W1 2C /rAVX10.1 or AVX512F
VSCALEFPD xmm {k}{z}, xmm, xmm VSCALEFPD_XMMf64_MASKmskw_XMMf64_XMMf64_AVX512EVEX.128.66.0F38.W1 2C /rAVX10.1 or AVX512F + AVX512VL
VSCALEFPD xmm {k}{z}, xmm, m128/m64bcst VSCALEFPD_XMMf64_MASKmskw_XMMf64_MEMf64_AVX512EVEX.128.66.0F38.W1 2C /rAVX10.1 or AVX512F + AVX512VL
VSCALEFPD ymm {k}{z}, ymm, ymm VSCALEFPD_YMMf64_MASKmskw_YMMf64_YMMf64_AVX512EVEX.256.66.0F38.W1 2C /rAVX10.1 or AVX512F + AVX512VL
VSCALEFPD ymm {k}{z}, ymm, m256/m64bcst VSCALEFPD_YMMf64_MASKmskw_YMMf64_MEMf64_AVX512EVEX.256.66.0F38.W1 2C /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.
Modelzmm {k}{z}, zmm, zmm, {er}zmm {k}{z}, zmm, m512/m64bcstxmm {k}{z}, xmm, xmm
ymm {k}{z}, ymm, ymm
xmm {k}{z}, xmm, m128/m64bcstymm {k}{z}, ymm, m256/m64bcst
Skylake-SP4 / 0.5p0511 / 0.5p054 / 0.5p0110 / 0.5p0111 / 0.5p01
Ice Lake4 / 1p011 / 1p04 / 0.5p0110 / 0.5p0111 / 0.5p01
Sapphire Rapids4 / 1p012 / 1p04 / 0.5p0111 / 0.5p0112 / 0.5p01
Zen 43 / 1FP2 FP310 / 1FP2 FP33 / 0.51FP2 FP310 / 0.5FP2 FP310 / 0.5FP2 FP3
  1. Zen 4 model: AMD's spreadsheets give reciprocal throughput 1 for Zen 4 and Zen 5 (AMD 57647, row 3247; AMD 58455, row 898).

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.
VSCALEFPD: element by elementResult double i comes from double i of xmm2 and xmm3. Result doubles 1 to 0: r1, r0.01xmm2a11k1r0r1xmm101xmm3or m128b

Every double works alike: 2, 4 and 8 doubles in the xmm, ymm and zmm forms. The 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: 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 // 64):
    if k1[i]:
        a = zmm2.f64[i]
        b = src3.f64[i]
        zmm1.f64[i] = scalef(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): 9 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
VSCALEFPD xmm {k}{z}, xmm, xmm/m128/m64bcst VSCALEFPD ymm {k}{z}, ymm, ymm/m256/m64bcst VSCALEFPD 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.

All forms
AVX512-E2

Attributes

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

All forms
write masking; follows MXCSR
Memory forms
embedded broadcast (tuple Full); memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VSCALEFPD, 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_scalef_pd __m128d _mm_scalef_pd(__m128d __A, __m128d __B)

VSCALEFPD xmm, xmm, xmm EVEX.128 -mavx512vl

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

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

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

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

_mm256_scalef_pd __m256d _mm256_scalef_pd(__m256d __A, __m256d __B)

VSCALEFPD ymm, ymm, ymm EVEX.256 -mavx512vl

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

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

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

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

_mm512_scalef_pd __m512d _mm512_scalef_pd(__m512d __A, __m512d __B)

VSCALEFPD zmm, zmm, zmm EVEX.512 -mavx512f

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

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

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

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

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

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

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

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

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

VSCALEFPD 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
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 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 Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
  6. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2C, page 5-725 (VSCALEFPD)
  7. 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.