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

VCVTTPS2DQ converts singles to signed doublewords, rounding toward zero: the VEX and EVEX form of CVTTPS2DQ, whose page explains the truncation, the integer indefinite 80000000h for NaNs and out-of-range values, and how compilers build the unsigned conversion. VEX gives it 128 and 256 bits with AVX; EVEX adds 512 bits, write masks with zeroing, a broadcast single from memory and {sae}, with AVX-512F (now AVX10.1).

MXCSR’s rounding field plays no part

The T in the name fixes the rounding, so MXCSR.RC is ignored, and the assembly syntax of the EVEX form offers only {sae}, not the embedded rounding modes. In a case recorded on Zen 5 with RC set to round up, 0.5 still gave 0 and 1.5 gave 1, and only the precision flag was set.

What {sae} changes

With {sae}, on the register-to-register 512-bit form, the conversion raises no exception and sets no flag: an out-of-range input still gives 80000000h, but nothing records that it happened. Zen 5 converted 2^32, 2^63 and -2^63 to 80000000h under {sae} with the invalid exception unmasked (MXCSR 1E40h), took no #XM, and left MXCSR as it was; -2^31, which fits, gave 80000000h too, and 2,147,483,520 gave 7FFFFF80h. Without {sae}, the same out-of-range input sets IE, or faults when IE is unmasked. Code that needs to know about invalid inputs must therefore check them itself, for example by looking again at the inputs of the elements that came out as 80000000h.

Compilers

For out[i] = (int)in[i] over 1,024 floats, GCC 14 at -O2 with -march=x86-64-v4 converts ZMM registers, while Clang 23 uses YMM registers; with -march=znver5 both use ZMM. _mm512_cvtt_roundps_epi32(x, _MM_FROUND_NO_EXC) gives the {sae} form, and the masked intrinsics the forms with {k}. A loop that converts only the elements selected by a condition becomes, in both compilers, a masked load, an unmasked conversion and a masked store.

Related conversions: VCVTTPS2UDQ to unsigned doublewords, VCVTTPS2QQ to quadwords, and AVX10.2’s VCVTTPS2DQS, which saturates instead of giving the indefinite value. AMD’s Zen 5 guide lists VCVTTPS2DQ as one macro-op with a latency of three cycles at every width.

Forms

Every encoding of VCVTTPS2DQ that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VCVTTPS2DQ xmm, m128 VCVTTPS2DQ_XMMdq_MEMdqVEX.128.F3.0F.WIG 5B /rAVX
VCVTTPS2DQ xmm, xmm VCVTTPS2DQ_XMMdq_XMMdqVEX.128.F3.0F.WIG 5B /rAVX
VCVTTPS2DQ ymm, m256 VCVTTPS2DQ_YMMqq_MEMqqVEX.256.F3.0F.WIG 5B /rAVX
VCVTTPS2DQ ymm, ymm VCVTTPS2DQ_YMMqq_YMMqqVEX.256.F3.0F.WIG 5B /rAVX
VCVTTPS2DQ zmm {k}{z}, zmm, {sae} VCVTTPS2DQ_ZMMi32_MASKmskw_ZMMf32_AVX512EVEX.512.F3.0F.W0 5B /rAVX10.1 or AVX512F
VCVTTPS2DQ zmm {k}{z}, m512/m32bcst VCVTTPS2DQ_ZMMi32_MASKmskw_MEMf32_AVX512EVEX.512.F3.0F.W0 5B /rAVX10.1 or AVX512F
VCVTTPS2DQ xmm {k}{z}, xmm VCVTTPS2DQ_XMMi32_MASKmskw_XMMf32_AVX512EVEX.128.F3.0F.W0 5B /rAVX10.1 or AVX512F + AVX512VL
VCVTTPS2DQ xmm {k}{z}, m128/m32bcst VCVTTPS2DQ_XMMi32_MASKmskw_MEMf32_AVX512EVEX.128.F3.0F.W0 5B /rAVX10.1 or AVX512F + AVX512VL
VCVTTPS2DQ ymm {k}{z}, ymm VCVTTPS2DQ_YMMi32_MASKmskw_YMMf32_AVX512EVEX.256.F3.0F.W0 5B /rAVX10.1 or AVX512F + AVX512VL
VCVTTPS2DQ ymm {k}{z}, m256/m32bcst VCVTTPS2DQ_YMMi32_MASKmskw_MEMf32_AVX512EVEX.256.F3.0F.W0 5B /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/m32bcst
xmm, xmm
xmm {k}{z}, xmm
ymm, m256
ymm {k}{z}, m256/m32bcst
ymm, ymmzmm {k}{z}, zmm, {sae}no maskzmm {k}{z}, zmm, {sae}with a mask, zeroing, with {sae}zmm {k}{z}, m512/m32bcstymm {k}{z}, ymm
Sandy Bridge, Haswell9 / 1p13 / 1p110 / 1p13 / 1p1
Broadwell8 / 1p13 / 1p19 / 1p13 / 1p1
Skylake10 / 0.5p014 / 0.5p0111 / 0.5p014 / 0.5p01
Skylake-SP, Ice Lake10 / 0.5p014 / 0.5p0111 / 0.5p013 / 0.5p014 / 0.5p053 / 0.5p0511 / 0.5p014 / 0.5p01
Alder Lake11 / 0.5p014 / 0.5p0112 / 0.5p014 / 0.5p01
Sapphire Rapids11 / 0.5p014 / 0.5p0112 / 0.5p014 / 0.5p014 / 1p04 / 1p012 / 1p04 / 0.5p01
Lunar Lake10 / 2V0 V14 / 2V0 V111 / 2.33V0 V14 / 2V0 V1
Piledriver9 / 1.5FPCVT FPU04 / 1FPCVT FPSTO FPU09 / 2FPCVT FPU04 / 2FPCVT FPSTO FPU0
Zen12 / 1FPU35 / 1FPU312 / 1FPU35 / 1FPU3
Zen 212 / 1FPU33 / 1FPU1 FPU2 FPU312 / 1FPU35 / 1FPU3
Zen 310 / 0.5FP2 FP33 / 0.5FP2 FP310 / 0.5FP2 FP33 / 0.5FP2 FP3
Zen 410 / 0.5FP2 FP33 / 0.5FP2 FP311 / 0.5FP2 FP34 / 0.51FP2 FP34 / 12FP2 FP34 / 12FP2 FP311 / 1FP2 FP34 / 0.53FP2 FP3
Jaguar8 / 1FPU13 / 1FPU1 STC8 / 2FPU13 / 2FPU1 STC
  1. Zen 4 model: AMD's spreadsheets give latency 3 for Zen 4 and Zen 5 (AMD 57647, row 1066; AMD 58455, row 1076).
  2. Zen 4 model: AMD's spreadsheets give latency 3 for Zen 4 and Zen 5 (AMD 57647, row 1068; AMD 58455, row 109).
  3. Zen 4 model: AMD's spreadsheets give latency 3 for Zen 4 and Zen 5 (AMD 57647, row 1067; AMD 58455, row 109).

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 single of the result comes from the single in the same place in each source.
VCVTTPS2DQ: element by elementResult single i comes from single i of xmm2. Result singles 3 to 0: r3, unchanged (bit 2 of k1 is 0), r1, r0.0123xmm2or m128a1110k1r0r1r3xmm1

Every single works alike: 4, 8 and 16 singles 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 m32bcst, one single from memory stands for every element of the last source.

Result single i comes from single i of xmm2. Result singles 3 to 0: r3, unchanged (bit 2 of k1 is 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 // 32):
    if k1[i]:  # 1 without a write mask
        a = src2.f32[i]
        zmm1.d[i] = cvtt_int(a, 32)
    elif zeroing:
        zmm1.d[i] = 0
    # else: zmm1.d[i] keeps its value
# m32bcst: src2.f32[i] is the m32 for every i
# {sae}: no exception flags
# zmm1 is zeroed from bit VL up

Run on AMD Zen 5 (EPYC 9645): 15 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
VCVTTPS2DQ xmm, xmm/m128 VCVTTPS2DQ ymm, ymm/m256
xmm, ymmexplicitwrite
xmm/m128, ymm/m256explicitread
VCVTTPS2DQ xmm {k}{z}, xmm/m128/m32bcst VCVTTPS2DQ ymm {k}{z}, ymm/m256/m32bcst VCVTTPS2DQ zmm {k}{z}, zmm/m512/m32bcst, {sae}
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm/m128/m32bcst, ymm/m256/m32bcst, zmm/m512/m32bcstexplicitread

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 VCVTTPS2DQ, 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_cvttps_epi32 __m128i _mm_cvttps_epi32(__m128 __a)

VCVTTPS2DQ xmm, xmm VEX.128 -mavxwith AVX enabled

_mm_mask_cvttps_epi32 __m128i _mm_mask_cvttps_epi32(__m128i __W, __mmask8 __U, __m128 __A)

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

_mm_maskz_cvttps_epi32 __m128i _mm_maskz_cvttps_epi32(__mmask8 __U, __m128 __A)

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

_mm256_cvttps_epi32 __m256i _mm256_cvttps_epi32(__m256 __a)

VCVTTPS2DQ ymm, ymm VEX.256 -mavx

_mm256_mask_cvttps_epi32 __m256i _mm256_mask_cvttps_epi32(__m256i __W, __mmask8 __U, __m256 __A)

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

_mm256_maskz_cvttps_epi32 __m256i _mm256_maskz_cvttps_epi32(__mmask8 __U, __m256 __A)

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

_mm512_cvtt_roundps_epi32 __m512i _mm512_cvtt_roundps_epi32(__m512 A, const int R)

VCVTTPS2DQ zmm, zmm, {sae} EVEX.512 -mavx512f

_mm512_cvttps_epi32 __m512i _mm512_cvttps_epi32(__m512 __a)

VCVTTPS2DQ zmm, zmm EVEX.512 -mavx512f

_mm512_mask_cvtt_roundps_epi32 __m512i _mm512_mask_cvtt_roundps_epi32(__m512i W, __mmask16 U, __m512 A, const int R)

VCVTTPS2DQ zmm {k}, zmm, {sae} EVEX.512 -mavx512f

_mm512_mask_cvttps_epi32 __m512i _mm512_mask_cvttps_epi32(__m512i __W, __mmask16 __U, __m512 __A)

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

_mm512_maskz_cvtt_roundps_epi32 __m512i _mm512_maskz_cvtt_roundps_epi32(__mmask16 U, __m512 A, const int R)

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

_mm512_maskz_cvttps_epi32 __m512i _mm512_maskz_cvttps_epi32(__mmask16 __U, __m512 __A)

VCVTTPS2DQ zmm {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-249 (CVTTPS2DQ)
  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.