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

VPMADD52HUQ is the other half of VPMADD52LUQ: it multiplies the low 52 bits of each quadword of its two sources and adds bits 103 to 52 of the 104-bit product, where VPMADD52LUQ adds bits 51 to 0, to the quadword in the destination. That page explains the radix-2^52 arithmetic the pair serves, the AVX512_IFMA and AVX-IFMA forms and the build-flag trap of the VEX encoding; on Zen 5 the VEX forms of VPMADD52HUQ raised #UD as well.

The high half in recorded cases

  • One factor all ones. In vpmadd52huq ymm7{k2}{z}, ymm12, ymm7 element 0 of YMM7 was both accumulator and factor, D05154C465A0A03Ch, and YMM12’s was FFFFFFFFFFFFFFFFh, whose low 52 bits are 2^52 - 1. The high half of the product was the other factor’s low 52 bits, 154C465A0A03Ch, less one, and the element became D052A988CB414077h.
  • Small products add nothing. With a broadcast factor of 80h, vpmadd52huq zmm17{k3}, zmm30, qword bcst [mem] left an accumulator unchanged where the other factor was 1, and also where it was 8000000000000000h, whose low 52 bits are zero.
  • The sum wraps. In the same case, factors of all ones added 7Fh: FFFFFFFFFFFFFFFFh became 7Eh and 7FFFFFFFFFFFFFFFh became 800000000000007Eh, with no saturation and no flag.

In compiled code

GCC 14 and Clang 23 at -O2 with -march=znver5 do not find the instruction in a[i] += ((unsigned __int128)(b[i] & M) * (c[i] & M)) >> 52 over uint64_t arrays, with M = 2^52 - 1. GCC keeps the loop scalar with MULX and SHRD; Clang vectorizes the masking and the addition but moves every element to a general register for its MULX and SHRD and back. The intrinsics _mm512_madd52hi_epu64 and kin give VPMADD52HUQ, and a function that applies both halves to the same factors gets one VPMADD52LUQ and one VPMADD52HUQ from either compiler.

AMD’s Zen 5 latency spreadsheet gives VPMADD52HUQ what it gives VPMADD52LUQ: 4 cycles and two per cycle on pipes FP0 and FP1. Zen 5’s 10 recorded cases cover the VEX forms, which all faulted, and the EVEX register, memory and broadcast forms at all three widths.

In the optimization guide

What the optimization guide says about VPMADD52HUQ, a line per claim. Each links to the claim in the guide, with its sources and where they differ.

Crestmont and Gracemont

  • Vectors and AVX2: Crestmont runs the 52-bit integer multiply-adds of AVX-IFMA in its floating-point multipliers.

Ice Lake to Rocket Lake

  • Vectors and AVX-512: VPMADD52LUQ and VPMADD52HUQ multiply eight pairs of 52-bit numbers and add the low or the high 52 bits of each product to a 64-bit accumulator, for the big-number arithmetic of RSA.

Forms

Every encoding of VPMADD52HUQ that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPMADD52HUQ xmm, xmm, xmm VPMADD52HUQ_XMMu64_XMMu64_XMMu64VEX.128.66.0F38.W1 B5 /rAVX_IFMA
VPMADD52HUQ xmm, xmm, m128 VPMADD52HUQ_XMMu64_XMMu64_MEMu64VEX.128.66.0F38.W1 B5 /rAVX_IFMA
VPMADD52HUQ ymm, ymm, ymm VPMADD52HUQ_YMMu64_YMMu64_YMMu64VEX.256.66.0F38.W1 B5 /rAVX_IFMA
VPMADD52HUQ ymm, ymm, m256 VPMADD52HUQ_YMMu64_YMMu64_MEMu64VEX.256.66.0F38.W1 B5 /rAVX_IFMA
VPMADD52HUQ xmm {k}{z}, xmm, xmm VPMADD52HUQ_XMMu64_MASKmskw_XMMu64_XMMu64_AVX512EVEX.128.66.0F38.W1 B5 /rAVX10.1 or AVX512IFMA + AVX512VL
VPMADD52HUQ xmm {k}{z}, xmm, m128/m64bcst VPMADD52HUQ_XMMu64_MASKmskw_XMMu64_MEMu64_AVX512EVEX.128.66.0F38.W1 B5 /rAVX10.1 or AVX512IFMA + AVX512VL
VPMADD52HUQ ymm {k}{z}, ymm, ymm VPMADD52HUQ_YMMu64_MASKmskw_YMMu64_YMMu64_AVX512EVEX.256.66.0F38.W1 B5 /rAVX10.1 or AVX512IFMA + AVX512VL
VPMADD52HUQ ymm {k}{z}, ymm, m256/m64bcst VPMADD52HUQ_YMMu64_MASKmskw_YMMu64_MEMu64_AVX512EVEX.256.66.0F38.W1 B5 /rAVX10.1 or AVX512IFMA + AVX512VL
VPMADD52HUQ zmm {k}{z}, zmm, zmm VPMADD52HUQ_ZMMu64_MASKmskw_ZMMu64_ZMMu64_AVX512EVEX.512.66.0F38.W1 B5 /rAVX10.1 or AVX512IFMA
VPMADD52HUQ zmm {k}{z}, zmm, m512/m64bcst VPMADD52HUQ_ZMMu64_MASKmskw_ZMMu64_MEMu64_AVX512EVEX.512.66.0F38.W1 B5 /rAVX10.1 or AVX512IFMA

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, xmm
ymm, ymm, ymm
xmm, xmm, m128
ymm, ymm, m256
xmm {k}{z}, xmm, xmm
ymm {k}{z}, ymm, ymm
xmm {k}{z}, xmm, m128/m64bcstymm {k}{z}, ymm, m256/m64bcstzmm {k}{z}, zmm, zmmzmm {k}{z}, zmm, m512/m64bcst
Ice Lake5 / 0.5p0111 / 0.5p0112 / 0.5p015 / 0.5p0512 / 0.5p05
Sapphire Rapids4 / 0.5p0111 / 0.5p0112 / 0.5p014 / 1p012 / 1p0
Lunar Lake4 / 2V0 V14 / 2V0 V1
Zen 44 / 21FP0 FP110 / 0.5FP0 FP310 / 0.5FP0 FP34 / 2FP0 FP110 / 1FP0 FP3
  1. Zen 4 model: AMD's spreadsheets give reciprocal throughput 0.5 for Zen 4 and Zen 5 (AMD 57647, row 2409; AMD 58455, row 915).

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 quadword of the result comes from the quadword in the same place in each source.
VPMADD52HUQ: element by elementResult quadword i comes from quadword i of xmm1, xmm2 and xmm3. Result quadwords 1 to 0: r1, r0.01xmm1a01xmm2b01xmm3or m128c11k1r0r1xmm1

Every quadword works alike: 2, 4 and 8 quadwords 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 quadword from memory stands for every element of the last source. The sources are drawn above the result, each element in its own column.

Result quadword i comes from quadword i of xmm1, xmm2 and xmm3. Result quadwords 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.

VEX forms
if not cpuid_leaf(7, 1)[0] >> 23 & 1:
    fault(UD)  # CPUID: no AVX-IFMA
for i in range(VL // 64):
    a = ymm1.q[i]
    b = ymm2.q[i]
    c = src3.q[i]
    x = low(b, 52) * low(c, 52)
    ymm1.q[i] = a + (x >> 52)
# ymm1 is zeroed from bit VL up

Run on AMD Zen 5 (EPYC 9645): 4 cases. Its cases ran where CPUID reported no AVX-IFMA, and every one raised an exception.

EVEX forms
for i in range(VL // 64):
    if k1[i]:
        a = zmm1.q[i]
        b = zmm2.q[i]
        c = src3.q[i]
        x = low(b, 52) * low(c, 52)
        zmm1.q[i] = a + (x >> 52)
    elif zeroing:
        zmm1.q[i] = 0
    # else: zmm1.q[i] keeps its value
# m64bcst: src3.q[i] is the m64 for every i
# zmm1 is zeroed from bit VL 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
VPMADD52HUQ xmm, xmm, xmm/m128 VPMADD52HUQ ymm, ymm, ymm/m256
xmm, ymmexplicitread, write
xmm, ymmexplicitread
xmm/m128, ymm/m256explicitread
VPMADD52HUQ xmm {k}{z}, xmm, xmm/m128/m64bcst VPMADD52HUQ ymm {k}{z}, ymm, ymm/m256/m64bcst VPMADD52HUQ zmm {k}{z}, zmm, zmm/m512/m64bcst
xmm, ymm, zmmexplicitread, write (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-4
EVEX forms
AVX512-E4

Attributes

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

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 VPMADD52HUQ, 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_madd52hi_avx_epu64 __m128i _mm_madd52hi_avx_epu64(__m128i __X, __m128i __Y, __m128i __Z)

VPMADD52HUQ xmm, xmm, xmm VEX.128 -mavxifma

_mm_madd52hi_epu64 __m128i _mm_madd52hi_epu64(__m128i X, __m128i Y, __m128i Z)

VPMADD52HUQ xmm, xmm, xmm EVEX.128 -mavx512ifma -mavx512vl

_mm_mask_madd52hi_epu64 __m128i _mm_mask_madd52hi_epu64(__m128i __W, __mmask8 __M, __m128i __X, __m128i __Y)

VPMADD52HUQ xmm {k}, xmm, xmm EVEX.128 -mavx512ifma -mavx512vl

_mm_maskz_madd52hi_epu64 __m128i _mm_maskz_madd52hi_epu64(__mmask8 __M, __m128i __X, __m128i __Y, __m128i __Z)

VPMADD52HUQ xmm {k}{z}, xmm, xmm EVEX.128 -mavx512ifma -mavx512vl

_mm256_madd52hi_avx_epu64 __m256i _mm256_madd52hi_avx_epu64(__m256i __X, __m256i __Y, __m256i __Z)

VPMADD52HUQ ymm, ymm, ymm VEX.256 -mavxifma

_mm256_madd52hi_epu64 __m256i _mm256_madd52hi_epu64(__m256i X, __m256i Y, __m256i Z)

VPMADD52HUQ ymm, ymm, ymm EVEX.256 -mavx512ifma -mavx512vl

_mm256_mask_madd52hi_epu64 __m256i _mm256_mask_madd52hi_epu64(__m256i __W, __mmask8 __M, __m256i __X, __m256i __Y)

VPMADD52HUQ ymm {k}, ymm, ymm EVEX.256 -mavx512ifma -mavx512vl

_mm256_maskz_madd52hi_epu64 __m256i _mm256_maskz_madd52hi_epu64(__mmask8 __M, __m256i __X, __m256i __Y, __m256i __Z)

VPMADD52HUQ ymm {k}{z}, ymm, ymm EVEX.256 -mavx512ifma -mavx512vl

_mm512_madd52hi_epu64 __m512i _mm512_madd52hi_epu64(__m512i __X, __m512i __Y, __m512i __Z)

VPMADD52HUQ zmm, zmm, zmm EVEX.512 -mavx512ifma

_mm512_mask_madd52hi_epu64 __m512i _mm512_mask_madd52hi_epu64(__m512i __W, __mmask8 __M, __m512i __X, __m512i __Y)

VPMADD52HUQ zmm {k}, zmm, zmm EVEX.512 -mavx512ifma

_mm512_maskz_madd52hi_epu64 __m512i _mm512_maskz_madd52hi_epu64(__mmask8 __M, __m512i __X, __m512i __Y, __m512i __Z)

VPMADD52HUQ zmm {k}{z}, zmm, zmm EVEX.512 -mavx512ifma

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_IFMA

AVX_IFMA
CPUID.(EAX=07H,ECX=1):EAX[23] AVX_IFMA

Arrow Lake, Panther Lake, Nova Lake, Diamond Rapids, Sierra Forest, Clearwater Forest, Zen 6
AVX512_IFMA_128

AVX10.1
CPUID.(EAX=07H,ECX=1):EDX[19] AVX10
CPUID.(EAX=24H,ECX=0):EBX[7:0] ≥ 1 AVX10 version

or

AVX512IFMA + AVX512VL
CPUID.(EAX=07H,ECX=0):EBX[21] AVX512IFMA
CPUID.(EAX=07H,ECX=0):EBX[31] AVX512VL

Cannon Lake, Ice Lake (client), Tiger Lake, Nova Lake, Ice Lake (server), Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Zen 4, Zen 5, Zen 6
AVX512_IFMA_256
Same as AVX512_IFMA_128Same as AVX512_IFMA_128
AVX512_IFMA_512

AVX10.1
CPUID.(EAX=07H,ECX=1):EDX[19] AVX10
CPUID.(EAX=24H,ECX=0):EBX[7:0] ≥ 1 AVX10 version

or

AVX512IFMA
CPUID.(EAX=07H,ECX=0):EBX[21] AVX512IFMA

Same as AVX512_IFMA_128

More AVX-IFMA 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 2C, page 5-565 (VPMADD52HUQ)
  6. Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
  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.