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

VCVTTPD2DQ converts doubles to signed doublewords, truncating toward zero, into a register half as wide as its source. The legacy CVTTPD2DQ page covers the truncation, the integer indefinite 80000000H, the AT&T suffixes vcvttpd2dqx and vcvttpd2dqy, and how GCC joins two halves, and VCVTTPS2DQ explains {sae}, which this form shares. What the double source adds:

Every doubleword fits from below

A double holds every 32-bit integer and the fractions around them, so the edge of the range is visible here as it is not with singles. In the cases recorded on Zen 5, 2,147,483,647.9999998 truncated to 7FFFFFFFH, the largest doubleword, while 2^31 gave 80000000H, the indefinite value, and -2^31 also 80000000H, this time as a real result. Rounding to nearest, VCVTPD2DQ would have turned the first into the indefinite value too.

Masks and broadcast

Each mask bit selects a result doubleword, eight for a zmm source. With K4 holding CAH, vcvttpd2dq ymm24{k4}, zmm3, {sae} wrote elements 1, 3, 6 and 7 (2^31, 2,147,483,647.9999998, 10^300 and 10^-300 became 80000000H, 7FFFFFFFH, 80000000H and 0) and kept the rest. A broadcast double, {1to2}, {1to4} or {1to8} in AT&T syntax, converts one value into every element. With MXCSR 0, every exception unmasked, {sae} let a signaling NaN through as 80000000H without #XM.

In compiled code

In our builds at -O2, Clang 23 compiles out[i] = (int)in[i] over doubles to one VCVTTPD2DQ per 32 bytes, ymm to xmm, each result stored on its own for -march=x86-64-v3 and x86-64-v4, and zmm to ymm for znver5; GCC 14 joins pairs with VINSERTI128, or VINSERTI32X8 for x86-64-v4. AVX10.2’s VCVTTPD2DQS saturates instead: 7FFFFFFFH for 2^31 rather than the indefinite value.

Forms

Every encoding of VCVTTPD2DQ that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VCVTTPD2DQ xmm, m128 VCVTTPD2DQ_XMMdq_MEMdqVEX.128.66.0F.WIG E6 /rAVX
VCVTTPD2DQ xmm, xmm VCVTTPD2DQ_XMMdq_XMMdqVEX.128.66.0F.WIG E6 /rAVX
VCVTTPD2DQ xmm, m256 VCVTTPD2DQ_XMMdq_MEMqqVEX.256.66.0F.WIG E6 /rAVX
VCVTTPD2DQ xmm, ymm VCVTTPD2DQ_XMMdq_YMMqqVEX.256.66.0F.WIG E6 /rAVX
VCVTTPD2DQ ymm {k}{z}, zmm, {sae} VCVTTPD2DQ_YMMi32_MASKmskw_ZMMf64_AVX512_VL512EVEX.512.66.0F.W1 E6 /rAVX10.1 or AVX512F
VCVTTPD2DQ ymm {k}{z}, m512/m64bcst VCVTTPD2DQ_YMMi32_MASKmskw_MEMf64_AVX512_VL512EVEX.512.66.0F.W1 E6 /rAVX10.1 or AVX512F
VCVTTPD2DQ xmm {k}{z}, xmm VCVTTPD2DQ_XMMi32_MASKmskw_XMMf64_AVX512_VL128EVEX.128.66.0F.W1 E6 /rAVX10.1 or AVX512F + AVX512VL
VCVTTPD2DQ xmm {k}{z}, m128/m64bcst VCVTTPD2DQ_XMMi32_MASKmskw_MEMf64_AVX512_VL128EVEX.128.66.0F.W1 E6 /rAVX10.1 or AVX512F + AVX512VL
VCVTTPD2DQ xmm {k}{z}, ymm VCVTTPD2DQ_XMMi32_MASKmskw_YMMf64_AVX512_VL256EVEX.256.66.0F.W1 E6 /rAVX10.1 or AVX512F + AVX512VL
VCVTTPD2DQ xmm {k}{z}, m256/m64bcst VCVTTPD2DQ_XMMi32_MASKmskw_MEMf64_AVX512_VL256EVEX.256.66.0F.W1 E6 /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/m64bcst
xmm, xmm
xmm {k}{z}, xmm
xmm, m256
xmm {k}{z}, m256/m64bcst
xmm, ymm
xmm {k}{z}, ymm
ymm {k}{z}, zmm, {sae}no maskymm {k}{z}, zmm, {sae}with a mask, zeroing, with {sae}ymm {k}{z}, m512/m64bcst
Sandy Bridge10 / 1p154 / 1p1511 / 1p154 / 1p15
Haswell10 / 1p154 / 1p1512 / 1p156 / 1p15
Broadwell9 / 1p154 / 1p1512 / 1p156 / 1p15
Skylake11 / 1p0155 / 1p01513 / 1p0157 / 1p015
Skylake-SP, Ice Lake8 / 0.5p015 / 1p0158 / 0.5p017 / 1p0157 / 1p053 / 0.5p0514 / 1p015
Alder Lake12 / 1p0155 / 1p01515 / 1p0157 / 1p015
Sapphire Rapids12 / 1p0155 / 1p01515 / 1p0157 / 1p0157 / 1p057 / 1p0515 / 1p05
Lunar Lake12 / 0.5V0 V1 V2 V35 / 0.5V0 V1 V2 V315 / 0.5V0 V1 V2 V37 / 0.5V0 V1 V2 V3
Piledriver13 / 1.5FPCVT FPU08 / 1FPCVT FPSTO FPU013 / 2FPCVT FPFMA FPU08 / 2FPCVT FPFMA FPSTO FPU0
Zen12 / 1FPU1 FPU2 FPU35 / 1FPU1 FPU2 FPU312 / 1FPU1 FPU2 FPU35 / 1FPU1 FPU2 FPU3
Zen 210 / 1FPU1 FPU2 FPU33 / 1FPU1 FPU2 FPU310 / 1FPU1 FPU2 FPU33 / 1FPU1 FPU2 FPU3
Zen 310 / 0.5FP2 FP33 / 0.5FP2 FP313 / 1FP2 FP36 / 1FP2 FP3
Zen 410 / 1FP2 FP33 / 11FP2 FP310 / 1FP2 FP33 / 1FP2 FP33 / 22FP2 FP33 / 22FP2 FP310 / 2FP2 FP3
Jaguar8 / 1FPU13 / 1FPU1 STC11 / 2FPA FPM FPU16 / 2FPA FPM FPU1 STC
  1. Zen 4 model: AMD's spreadsheets give reciprocal throughput 0.5 for Zen 4 and Zen 5 (AMD 57647, row 1050; AMD 58455, row 1074).
  2. Zen 4 model: AMD's spreadsheets give latency 7 for Zen 4 and Zen 5 (AMD 57647, row 1054; AMD 58455, row 103).

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.

Narrow: each double becomes a doubleword, in the same order, at the low end of the result.
VCVTTPD2DQ: each element narrowedResult doublewords 7 to 0: a7, unchanged (bit 6 of k1 is 0), a5, a4, a3, a2, a1, a0.01234567zmm2or m512a11111110k1a0a1a2a3a4a5a7ymm1

Shown for the zmm form; the xmm and ymm forms work the same on 2 and 4 doubles. The EVEX forms write under a mask: where its bit is 0, the element keeps its old value, or zeroes it with {z}.

Result doublewords 7 to 0: a7, unchanged (bit 6 of k1 is 0), a5, a4, a3, a2, a1, a0.

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]:  # 1 without a write mask
        a = src2.f64[i]
        ymm1.d[i] = cvtt_int(a, 32)
    elif zeroing:
        ymm1.d[i] = 0
    # else: ymm1.d[i] keeps its value
for i in range(VL // 64, 4):
    ymm1.d[i] = 0
# m64bcst: src2.f64[i] is the m64 for every i
# {sae}: no exception flags
# ymm1 is zeroed from bit 128 (xmm) or 256 (ymm) up

Run on AMD Zen 5 (EPYC 9645): 45 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
VCVTTPD2DQ xmm, xmm/m128 VCVTTPD2DQ xmm, ymm/m256
xmmexplicitwrite
xmm/m128, ymm/m256explicitread
VCVTTPD2DQ xmm {k}{z}, xmm/m128/m64bcst VCVTTPD2DQ xmm {k}{z}, ymm/m256/m64bcst VCVTTPD2DQ ymm {k}{z}, zmm/m512/m64bcst, {sae}
xmm, ymmexplicitwrite (masked)
{k}explicitread (write mask)
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-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 VCVTTPD2DQ, 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_cvttpd_epi32 __m128i _mm_cvttpd_epi32(__m128d __a)

VCVTTPD2DQ xmm, xmm VEX.128 -mavxwith AVX enabled

_mm_mask_cvttpd_epi32 __m128i _mm_mask_cvttpd_epi32(__m128i __W, __mmask8 __U, __m128d __A)

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

_mm_maskz_cvttpd_epi32 __m128i _mm_maskz_cvttpd_epi32(__mmask8 __U, __m128d __A)

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

_mm256_cvttpd_epi32 __m128i _mm256_cvttpd_epi32(__m256d __a)

VCVTTPD2DQ xmm, ymm VEX.256 -mavx

_mm256_mask_cvttpd_epi32 __m128i _mm256_mask_cvttpd_epi32(__m128i __W, __mmask8 __U, __m256d __A)

VCVTTPD2DQ xmm {k}, ymm EVEX.256 -mavx512vl

_mm256_maskz_cvttpd_epi32 __m128i _mm256_maskz_cvttpd_epi32(__mmask8 __U, __m256d __A)

VCVTTPD2DQ xmm {k}{z}, ymm EVEX.256 -mavx512vl

_mm512_cvtt_roundpd_epi32 __m256i _mm512_cvtt_roundpd_epi32(__m512d A, const int R)

VCVTTPD2DQ ymm, zmm, {sae} EVEX.512 -mavx512f

_mm512_cvttpd_epi32 __m256i _mm512_cvttpd_epi32(__m512d __a)

VCVTTPD2DQ ymm, zmm EVEX.512 -mavx512f

_mm512_mask_cvtt_roundpd_epi32 __m256i _mm512_mask_cvtt_roundpd_epi32(__m256i W, __mmask8 U, __m512d A, const int R)

VCVTTPD2DQ ymm {k}, zmm, {sae} EVEX.512 -mavx512f

_mm512_mask_cvttpd_epi32 __m256i _mm512_mask_cvttpd_epi32(__m256i __W, __mmask8 __U, __m512d __A)

VCVTTPD2DQ ymm {k}, zmm EVEX.512 -mavx512f

_mm512_maskz_cvtt_roundpd_epi32 __m256i _mm512_maskz_cvtt_roundpd_epi32(__mmask8 U, __m512d A, const int R)

VCVTTPD2DQ ymm {k}{z}, zmm, {sae} EVEX.512 -mavx512f

_mm512_maskz_cvttpd_epi32 __m256i _mm512_maskz_cvttpd_epi32(__mmask8 __U, __m512d __A)

VCVTTPD2DQ ymm {k}{z}, zmm 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 2A, page 3-244 (CVTTPD2DQ)
  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)

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.