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

MULX multiplies RDX, or EDX for 32 bits, by its source, unsigned, and writes the double-width product to two registers of its choice without touching the flags. In Intel syntax the register for the high half comes first: mulx r9, r8, rsi puts the upper 64 bits of RDX * RSI in R9 and the lower 64 bits in R8. MUL instead takes its other factor from RAX, always writes RDX:RAX and sets CF and OF.

Why no flags

Multiplying integers of several words adds partial products in carry chains, and the flags MUL writes would break a chain of ADC between two steps. MULX leaves CF and OF alone, so its products can be interleaved with ADC, or with ADCX and ADOX, which carry through CF and OF only and so run two chains at once. Intel’s optimization manual shows such a carry chain and says that MULX can speed up computations on large integers, such as RSA’s, significantly (Section 14.5.1.1). The free choice of destinations also saves the moves that MUL’s fixed registers need.

One register for both halves

If both destinations name the same register, it ends up holding the high half, as the page’s pseudocode writes it last; Zen 5 did so in every recorded case. Clang 23 uses this: with -march=x86-64-v3 at -O2 it compiles the high half of a 64-bit product, (unsigned __int128)a * b >> 64, to mulx rax, rax, rdi, and does the same for the multiplication by a reciprocal that replaces x / 10. GCC 14 keeps MUL for both, and uses MULX for the full 128-bit product. The intrinsic _mulx_u64(a, b, &hi) returns the low half and stores the high one; both compilers emit MULX and a store.

Speed

The instruction table of AMD’s Zen 5 guide lists MULX as two macro-ops with a latency of four cycles, on the multiplier that three of Zen 5’s integer ALUs have (Section 2.10.2). Intel’s optimization manual places it, with MUL and IMUL, on the single “slow integer” unit of Golden Cove (Table 2-4).

MULX belongs to BMI2, part of x86-64-v3; APX adds an EVEX form that reaches its new registers.

Forms

Every encoding of MULX that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
MULX r32, r32, r32 MULX_GPR32d_GPR32d_GPR32dVEX.LZ.F2.0F38.W0 F6 /rBMI2
MULX r32, r32, m32 MULX_GPR32d_GPR32d_MEMdVEX.LZ.F2.0F38.W0 F6 /rBMI2
MULX r64, r64, r64 64-bit mode only MULX_GPR64q_GPR64q_GPR64qVEX.LZ.F2.0F38.W1 F6 /rBMI2
MULX r64, r64, m64 64-bit mode only MULX_GPR64q_GPR64q_MEMqVEX.LZ.F2.0F38.W1 F6 /rBMI2
MULX r32, r32, r32 MULX_GPR32i32_GPR32i32_GPR32i32_APXEVEX.LLZ.F2.0F38.W0 F6 /rAPX_F + BMI2
MULX r32, r32, m32 MULX_GPR32i32_GPR32i32_MEMi32_APXEVEX.LLZ.F2.0F38.W0 F6 /rAPX_F + BMI2
MULX r64, r64, r64 MULX_GPR64i64_GPR64i64_GPR64i64_APXEVEX.LLZ.F2.0F38.W1 F6 /rAPX_F + BMI2
MULX r64, r64, m64 MULX_GPR64i64_GPR64i64_MEMi64_APXEVEX.LLZ.F2.0F38.W1 F6 /rAPX_F + BMI2

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.
Modelr32, r32, r32r32, r32, m32r64, r64, r64r64, r64, m64
Haswell4 / 1p01569 / 1p01564 / 1p169 / 1p16
Broadwell, Skylake, Skylake-SP, Ice Lake4 / 1p01569 / 1p01564 / 1p159 / 1p15
Alder Lake, Sapphire Rapids4 / 1p0 p1 p5 p6 p119 / 1p0 p1 p5 p6 p114 / 1p159 / 1p15
Lunar Lake4 / 0.67p0123458 / 0.67p0123454 / 0.67p1358 / 0.67p135
Zen3 / 2ALU1 Mul8 / 2ALU1 Mul3 / 2ALU1 Mul8 / 2ALU1 Mul
Zen 23 / 2ALU1 Mul7 / 2ALU1 Mul3 / 2ALU1 Mul7 / 2ALU1 Mul
Zen 3, Zen 44 / 1ALU18 / 1ALU14 / 1ALU18 / 1ALU1

Operation

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

p = rDX * src                    # EDX or RDX times the source, unsigned: a
                                 # product of 2 * OSIZE bits
lo.write(p)                      # the low half, then the high half: when
hi.write(p >> OSIZE)             # hi and lo are one register, the high
                                 # half is what stays
# no flag changes

Run on AMD Zen 5 (EPYC 9645): 56 cases. The APX forms were not run: none of these processors has APX.

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
MULX r32, r32, r/m32 MULX r64, r64, r/m64 64-bit mode only
r32/64explicitwrite
r32/64explicitwrite
r/m32/64explicitread
rDXimplicitread

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
none in XED
EVEX forms
APX-EVEX-BMI

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to MULX, 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
_mulx_u64 unsigned long long _mulx_u64(unsigned long long __X, unsigned long long __Y, unsigned long long *__P)

MULX r64, r64, r64 VEX.LZ -mbmi2

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 BMI2 instructions

More APX instructions

All 88 APX 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-152 (MULX)
  6. Intel Advanced Performance Extensions (Intel APX) Architecture Specification, revision 9.0 (355828-009, August 2026)
  7. AMD64 Architecture Programmer's Manual, Volume 3: General-Purpose and System Instructions (24594, rev. 3.39, October 2026)
  8. Intel 64 and IA-32 Architectures Optimization Reference Manual, Volume 1 (248966-051, October 2026)
  9. 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.