Instruction
VCVTUDQ2PH
Converts packed unsigned doublewords to half precision.
- Extensions
- Forms
- 6 (6 EVEX)
- Data
- Intel XED v2026.08.23
VCVTUDQ2PH converts unsigned doublewords to half precision, the vector
form of C’s conversion from unsigned int to _Float16. It is the
unsigned partner of VCVTDQ2PH, whose page covers the
widths, the rounding and where a half runs out: 16 doublewords of a ZMM
register become 16 halves in a YMM register, and so on down to 4 halves
in the low 64 bits of an XMM register. The opcode is 7Ah with the F2
prefix in EVEX map 5, the byte of VCVTUDQ2PS in the
0F map.
Where signed and unsigned part
The two conversions agree up to 7FFFFFFFh, and that range already ends
far past a half’s largest finite value, 65504: in round to nearest every
input from 65520 up becomes infinity, toward zero it becomes 65504, and
Intel’s entry lists overflow and precision for both. From 80000000h on,
VCVTDQ2PH reads a negative number and gives minus infinity or -65504,
where VCVTUDQ2PH gives plus infinity or 65504. Like the other
AVX512-FP16 conversions it takes a write mask with merging or zeroing, a
doubleword broadcast from memory, and {er} on the 512-bit register
form.
In our builds
At -O2 with -march=x86-64-v4 -mavx512fp16, h[i] = u[i] from a
uint32_t array to a _Float16 array becomes VCVTUDQ2PH from memory in
GCC 14 and Clang 23, with the same arrangement as VCVTDQ2PH: two ZMM
loads joined into one ZMM store in GCC, YMM loads to XMM results in
Clang. A single value is converted with VCVTUSI2SH.
At -march=x86-64-v3, without AVX512-FP16, Clang builds a single from
the two 16-bit halves of each element with VPBLENDW,
VSUBPS and VADDPS, as on the VCVTUDQ2PS page, and narrows it with
VCVTPS2PH; GCC zero-extends each element to 64 bits,
converts it to a double and calls __truncdfhf2. AMD’s Zen 5 guide does
not list AVX512-FP16, and this site’s recorded cases include none of
VCVTUDQ2PH.
Forms
| Instruction | Encoding | Requires |
|---|---|---|
VCVTUDQ2PH xmm {k}{z}, xmm
VCVTUDQ2PH_XMMf16_MASKmskw_XMMu32_AVX512 | EVEX.128.F2.MAP5.W0 7A /r | AVX10.1 or AVX512_FP16 + AVX512VL |
VCVTUDQ2PH xmm {k}{z}, m128/m32bcst
VCVTUDQ2PH_XMMf16_MASKmskw_MEMu32_AVX512_VL128 | EVEX.128.F2.MAP5.W0 7A /r | AVX10.1 or AVX512_FP16 + AVX512VL |
VCVTUDQ2PH xmm {k}{z}, ymm
VCVTUDQ2PH_XMMf16_MASKmskw_YMMu32_AVX512 | EVEX.256.F2.MAP5.W0 7A /r | AVX10.1 or AVX512_FP16 + AVX512VL |
VCVTUDQ2PH xmm {k}{z}, m256/m32bcst
VCVTUDQ2PH_XMMf16_MASKmskw_MEMu32_AVX512_VL256 | EVEX.256.F2.MAP5.W0 7A /r | AVX10.1 or AVX512_FP16 + AVX512VL |
VCVTUDQ2PH ymm {k}{z}, zmm, {er}
VCVTUDQ2PH_YMMf16_MASKmskw_ZMMu32_AVX512 | EVEX.512.F2.MAP5.W0 7A /r | AVX10.1 or AVX512_FP16 |
VCVTUDQ2PH ymm {k}{z}, m512/m32bcst
VCVTUDQ2PH_YMMf16_MASKmskw_MEMu32_AVX512 | EVEX.512.F2.MAP5.W0 7A /r | AVX10.1 or AVX512_FP16 |
Latency and throughput
| Model | xmm {k}{z}, xmmno mask | xmm {k}{z}, xmmwith a mask, zeroing | xmm {k}{z}, m128/m32bcstno mask, broadcast | xmm {k}{z}, m128/m32bcstwith a mask, zeroing | xmm {k}{z}, ymmno mask | xmm {k}{z}, ymmwith a mask, zeroing | xmm {k}{z}, m256/m32bcstno mask, broadcast | xmm {k}{z}, m256/m32bcstwith a mask, zeroing | ymm {k}{z}, zmm, {er}no mask, with {er} | ymm {k}{z}, zmm, {er}with a mask, zeroing | ymm {k}{z}, m512/m32bcstno mask, broadcast | ymm {k}{z}, m512/m32bcstwith a mask, zeroing |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Sapphire Rapids | 7 / 1p015 | 12 / 1p015 | 15 / 1p015 | 19 / 1p015 | 9 / 1p015 | 14 / 1p015 | 17 / 1p015 | 21 / 1p015 | 9 / 2p05 | 14 / 2p05 | 17 / 2p05 | 21 / 2p05 |
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.
Shown for the zmm form; the xmm and ymm forms work the same on 4 and 8 doublewords. The forms write under a mask: where its bit is 0, the element keeps its old value, or zeroes it with {z}.
Result halves 15 to 0: a15, unchanged (bit 14 of k1 is 0), a13, a12, a11, a10, a9, a8, a7, a6, 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 // 32):
if k1[i]:
ymm1.f16[i] = to_f16(src2.d[i])
elif zeroing:
ymm1.f16[i] = 0
# else: ymm1.f16[i] keeps its value
for i in range(VL // 32, 8):
ymm1.w[i] = 0
# m32bcst: src2.d[i] is the m32 for every i
# {er}: the form's rounding, not MXCSR.RC, and no flags
# ymm1 is zeroed from bit 128 (xmm) or 256 (ymm) upNot run on a processor: none of these processors has AVX512-FP16. The tests check its arithmetic against MPFR.
Operands
| Operand | Kind | Action |
|---|---|---|
VCVTUDQ2PH xmm {k}{z}, xmm/m128/m32bcst VCVTUDQ2PH xmm {k}{z}, ymm/m256/m32bcst VCVTUDQ2PH ymm {k}{z}, zmm/m512/m32bcst, {er} | ||
xmm, ymm | explicit | write (masked) |
{k} | explicit | read (write mask) |
xmm/m128/m32bcst, ymm/m256/m32bcst, zmm/m512/m32bcst | explicit | read |
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.
- All forms
AVX512-E2
Attributes
What else XED records about the forms. How to read.
- All forms
- write masking; follows MXCSR
- Memory forms
- embedded broadcast (tuple Full); memory fault suppression
Intrinsics
The C intrinsics of Clang 23.1.2 that compile to VCVTUDQ2PH, 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.
| Intrinsic | Compiles to |
|---|---|
_mm_cvtepu32_ph
__m128h _mm_cvtepu32_ph(__m128i __A) |
|
_mm_mask_cvtepu32_ph
__m128h _mm_mask_cvtepu32_ph(__m128h __W, __mmask8 __U, __m128i __A) |
|
_mm_maskz_cvtepu32_ph
__m128h _mm_maskz_cvtepu32_ph(__mmask8 __U, __m128i __A) |
|
_mm256_cvtepu32_ph
__m128h _mm256_cvtepu32_ph(__m256i __A) |
|
_mm256_mask_cvtepu32_ph
__m128h _mm256_mask_cvtepu32_ph(__m128h __W, __mmask8 __U, __m256i __A) |
|
_mm256_maskz_cvtepu32_ph
__m128h _mm256_maskz_cvtepu32_ph(__mmask8 __U, __m256i __A) |
|
_mm512_cvt_roundepu32_ph
__m256h _mm512_cvt_roundepu32_ph(__m512i A, const int R) |
|
_mm512_cvtepu32_ph
__m256h _mm512_cvtepu32_ph(__m512i __A) |
|
_mm512_mask_cvt_roundepu32_ph
__m256h _mm512_mask_cvt_roundepu32_ph(__m256h W, __mmask16 U, __m512i A, const int R) |
|
_mm512_mask_cvtepu32_ph
__m256h _mm512_mask_cvtepu32_ph(__m256h __W, __mmask16 __U, __m512i __A) |
|
_mm512_maskz_cvt_roundepu32_ph
__m256h _mm512_maskz_cvt_roundepu32_ph(__mmask16 U, __m512i A, const int R) |
|
_mm512_maskz_cvtepu32_ph
__m256h _mm512_maskz_cvtepu32_ph(__mmask16 __U, __m512i __A) |
|
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.
| ISA set | CPUID | Processors |
|---|---|---|
AVX512_FP16_128 | AVX10.1 or AVX512_FP16 + AVX512VL | Nova Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Zen 6 |
AVX512_FP16_256 | Same as AVX512_FP16_128 | Same as AVX512_FP16_128 |
AVX512_FP16_512 | AVX10.1 or AVX512_FP16 | Same as AVX512_FP16_128 |
More AVX10.1 instructions
- VCVTTPD2QQ
- VCVTTPD2UDQ
- VCVTTPD2UQQ
- VCVTTPH2DQ
- VCVTTPH2QQ
- VCVTTPH2UDQ
- VCVTTPH2UQQ
- VCVTTPH2UW
- VCVTTPH2W
- VCVTTPS2DQ
- VCVTTPS2QQ
- VCVTTPS2UDQ
- VCVTTPS2UQQ
- VCVTTSD2SI
- VCVTTSD2USI
- VCVTTSH2SI
- VCVTTSH2USI
- VCVTTSS2SI
- VCVTTSS2USI
- VCVTUDQ2PD
- VCVTUDQ2PS
- VCVTUQQ2PD
- VCVTUQQ2PH
- VCVTUQQ2PS
- VCVTUSI2SD
- VCVTUSI2SH
- VCVTUSI2SS
- VCVTUW2PH
- VCVTW2PH
- VDBPSADBW
- VDIVPD
- VDIVPH
- VDIVPS
- VDIVSD
- VDIVSH
- VDIVSS
- VDPBF16PS
- VEXPANDPD
- VEXPANDPS
- VEXTRACTF32X4
Sources
- Intel XED v2026.08.23 (commit
0bcb6237345c): forms, encodings, operands, flags, exception classes, attributes, ISA sets, CPUID bits and chip model. - The CPU data of x86-64.net: Zen 3 to Zen 6, from GCC’s
-marchfeature sets and AMD’s Processor Programming References, which the page of each processor cites. - 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. - LLVM 23.1.2's x86 scheduling models (commit
85ac56026243): the latency, reciprocal throughput and ports of each form, as llvm-mca reports them. - Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
- Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2C, page 5-133 (VCVTUDQ2PH)
- 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.