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

VCVTPS2DQ converts singles to signed doublewords, rounding as MXCSR.RC says, in VEX forms of 128 and 256 bits and EVEX forms up to 512. CVTPS2DQ explains the rounding, the integer indefinite 80000000H for NaNs and out-of-range values, and the difference from the truncating VCVTTPS2DQ, whose page also covers {sae}. What this form adds is the rounding mode in the instruction.

Floor and ceiling in one instruction

The 512-bit register form takes {rn-sae}, {rd-sae}, {ru-sae} or {rz-sae}, so it converts with a fixed direction whatever MXCSR says: {rd-sae} is (int)floorf(x) for every element in range and {ru-sae} is the ceiling. In the cases recorded on Zen 5:

  • {ru-sae} turned 1.5, 2.5 and -2.5 into 2, 3 and -2, and 10^-30 into 1;
  • {rd-sae} turned -1 into -1 and the smallest normal single into 0, and, with DAZ set, the denormal -2^-127 into 0 rather than -1;
  • {rn-sae} turned 2.5 into 2 and -2.5 into -2, ties to even.

These rounding operands also report nothing: with every exception unmasked (MXCSR 0 or 6000H), -2,147,483,904, the largest single and a signaling NaN each gave 80000000H, with no #XM and MXCSR unchanged. Without them, a signaling NaN raised #XM when invalid was unmasked.

What compilers emit

The embedded rounding is there for intrinsics: _mm512_cvt_roundps_epi32(x, _MM_FROUND_TO_NEG_INF | _MM_FROUND_NO_EXC) becomes vcvtps2dq zmm0, zmm0, {rd-sae} in our builds. Loops do not use it. At -O2 with -fno-math-errno, a loop of (int)floorf(a[i]) in Clang 23 rounds with VROUNDPS, immediate 9, and truncates with VCVTTPS2DQ (on zmm with VRNDSCALEPS for znver5); GCC 14 keeps it scalar. For (int)rintf(a[i]), Clang uses VCVTPS2DQ itself on ymm registers for -march=x86-64-v3 and x86-64-v4, and zmm for znver5, while GCC rounds with VROUNDPS (VRNDSCALEPS for x86-64-v4) and truncates. With x86-64-v4, Clang turns lrintf loops into VCVTPS2QQ, where GCC converts one element at a time.

Forms

Every encoding of VCVTPS2DQ that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VCVTPS2DQ xmm, m128 VCVTPS2DQ_XMMdq_MEMdqVEX.128.66.0F.WIG 5B /rAVX
VCVTPS2DQ xmm, xmm VCVTPS2DQ_XMMdq_XMMdqVEX.128.66.0F.WIG 5B /rAVX
VCVTPS2DQ ymm, m256 VCVTPS2DQ_YMMqq_MEMqqVEX.256.66.0F.WIG 5B /rAVX
VCVTPS2DQ ymm, ymm VCVTPS2DQ_YMMqq_YMMqqVEX.256.66.0F.WIG 5B /rAVX
VCVTPS2DQ zmm {k}{z}, zmm, {er} VCVTPS2DQ_ZMMi32_MASKmskw_ZMMf32_AVX512EVEX.512.66.0F.W0 5B /rAVX10.1 or AVX512F
VCVTPS2DQ zmm {k}{z}, m512/m32bcst VCVTPS2DQ_ZMMi32_MASKmskw_MEMf32_AVX512EVEX.512.66.0F.W0 5B /rAVX10.1 or AVX512F
VCVTPS2DQ xmm {k}{z}, xmm VCVTPS2DQ_XMMi32_MASKmskw_XMMf32_AVX512EVEX.128.66.0F.W0 5B /rAVX10.1 or AVX512F + AVX512VL
VCVTPS2DQ xmm {k}{z}, m128/m32bcst VCVTPS2DQ_XMMi32_MASKmskw_MEMf32_AVX512EVEX.128.66.0F.W0 5B /rAVX10.1 or AVX512F + AVX512VL
VCVTPS2DQ ymm {k}{z}, ymm VCVTPS2DQ_YMMi32_MASKmskw_YMMf32_AVX512EVEX.256.66.0F.W0 5B /rAVX10.1 or AVX512F + AVX512VL
VCVTPS2DQ ymm {k}{z}, m256/m32bcst VCVTPS2DQ_YMMi32_MASKmskw_MEMf32_AVX512EVEX.256.66.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, ymm
ymm {k}{z}, ymm
zmm {k}{z}, zmm, {er}no maskzmm {k}{z}, zmm, {er}with a mask, zeroing, with {er}zmm {k}{z}, m512/m32bcst
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.5p014 / 0.5p014 / 0.5p053 / 0.5p0511 / 0.5p01
Alder Lake11 / 0.5p014 / 0.5p0112 / 0.5p014 / 0.5p01
Sapphire Rapids11 / 0.5p014 / 0.5p0112 / 0.5p014 / 0.5p014 / 1p04 / 1p012 / 1p0
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 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 1009; AMD 58455, row 1055).
  2. Zen 4 model: AMD's spreadsheets give latency 3 for Zen 4 and Zen 5 (AMD 57647, row 1011; AMD 58455, row 61).

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.
VCVTPS2DQ: 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
        zmm1.d[i] = cvt_int(src2.f32[i], 32)
    elif zeroing:
        zmm1.d[i] = 0
    # else: zmm1.d[i] keeps its value
# m32bcst: src2.f32[i] is the m32 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): 48 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
VCVTPS2DQ xmm, xmm/m128 VCVTPS2DQ ymm, ymm/m256
xmm, ymmexplicitwrite
xmm/m128, ymm/m256explicitread
VCVTPS2DQ xmm {k}{z}, xmm/m128/m32bcst VCVTPS2DQ ymm {k}{z}, ymm/m256/m32bcst VCVTPS2DQ zmm {k}{z}, zmm/m512/m32bcst, {er}
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 VCVTPS2DQ, 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_cvtps_epi32 __m128i _mm_cvtps_epi32(__m128 __a)

VCVTPS2DQ xmm, xmm VEX.128 -mavxwith AVX enabled

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

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

_mm_maskz_cvtps_epi32 __m128i _mm_maskz_cvtps_epi32(__mmask8 __U, __m128 __A)

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

_mm256_cvtps_epi32 __m256i _mm256_cvtps_epi32(__m256 __a)

VCVTPS2DQ ymm, ymm VEX.256 -mavx

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

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

_mm256_maskz_cvtps_epi32 __m256i _mm256_maskz_cvtps_epi32(__mmask8 __U, __m256 __A)

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

_mm512_cvt_roundps_epi32 __m512i _mm512_cvt_roundps_epi32(__m512 A, const int R)

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

_mm512_cvtps_epi32 __m512i _mm512_cvtps_epi32(__m512 __A)

VCVTPS2DQ zmm, zmm EVEX.512 -mavx512f

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

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

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

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

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

VCVTPS2DQ zmm {k}{z}, zmm, {er} EVEX.512 -mavx512f

_mm512_maskz_cvtps_epi32 __m512i _mm512_maskz_cvtps_epi32(__mmask16 __U, __m512 __A)

VCVTPS2DQ 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-225 (CVTPS2DQ)
  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.