Extensions
Forms
6 (6 EVEX)
Data
Intel XED v2026.08.23

VCVTUW2PH converts unsigned words to half precision, 8, 16 or 32 at a time, in a destination as wide as the source. It is the unsigned partner of VCVTW2PH, with the same opcode, 7Dh in EVEX map 5, under F2 instead of F3; VCVTUDQ2PH converts unsigned doublewords. VADDPH covers AVX512-FP16 and the format.

The top of the word range overflows

Signed words always fit a half, so VCVTW2PH lists only the precision exception; unsigned words reach 65535, past the largest finite half, 65504, and Intel’s entry for VCVTUW2PH adds overflow. Above 32768 the halves are 32 apart: in round to nearest, 65519 becomes 65504, while 65520 lies halfway to 65536 and rounds to the even significand, which is past the format, so it and every word above become infinity with OE and PE set. Toward zero or down they become 65504. Intel’s optimization manual points out that full-range unsigned words land at the very top of the half range, where almost any arithmetic overflows, and advises scaling them after the conversion (Section 18.5.7).

In our builds

At -O2 with -march=x86-64-v4 -mavx512fp16, h[i] = u[i] from a uint16_t array to a _Float16 array becomes VCVTUW2PH from memory in GCC 14, on ZMM registers, and Clang 23, on YMM registers. For a single unsigned short, GCC zero-extends it and uses VCVTUSI2SH, while Clang uses the signed VCVTSI2SH, which gives the same half for any value below 2^31. _mm512_cvtepu16_ph and _mm512_cvt_roundepu16_ph are the intrinsics. AMD’s Zen 5 guide does not list AVX512-FP16, and this site’s recorded cases include none of VCVTUW2PH.

Forms

Every encoding of VCVTUW2PH that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VCVTUW2PH xmm {k}{z}, xmm VCVTUW2PH_XMMf16_MASKmskw_XMMu16_AVX512EVEX.128.F2.MAP5.W0 7D /rAVX10.1 or AVX512_FP16 + AVX512VL
VCVTUW2PH xmm {k}{z}, m128/m16bcst VCVTUW2PH_XMMf16_MASKmskw_MEMu16_AVX512EVEX.128.F2.MAP5.W0 7D /rAVX10.1 or AVX512_FP16 + AVX512VL
VCVTUW2PH ymm {k}{z}, ymm VCVTUW2PH_YMMf16_MASKmskw_YMMu16_AVX512EVEX.256.F2.MAP5.W0 7D /rAVX10.1 or AVX512_FP16 + AVX512VL
VCVTUW2PH ymm {k}{z}, m256/m16bcst VCVTUW2PH_YMMf16_MASKmskw_MEMu16_AVX512EVEX.256.F2.MAP5.W0 7D /rAVX10.1 or AVX512_FP16 + AVX512VL
VCVTUW2PH zmm {k}{z}, zmm, {er} VCVTUW2PH_ZMMf16_MASKmskw_ZMMu16_AVX512EVEX.512.F2.MAP5.W0 7D /rAVX10.1 or AVX512_FP16
VCVTUW2PH zmm {k}{z}, m512/m16bcst VCVTUW2PH_ZMMf16_MASKmskw_MEMu16_AVX512EVEX.512.F2.MAP5.W0 7D /rAVX10.1 or AVX512_FP16

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 {k}{z}, xmmno mask
ymm {k}{z}, ymmno mask
xmm {k}{z}, xmmwith a mask, zeroing
ymm {k}{z}, ymmwith a mask, zeroing
xmm {k}{z}, m128/m16bcst
ymm {k}{z}, m256/m16bcst
zmm {k}{z}, zmm, {er}no mask, with {er}zmm {k}{z}, zmm, {er}with a mask, zeroingzmm {k}{z}, m512/m16bcst
Sapphire Rapids5 / 0.5p016 / 0.5p0112 / 0.5p015 / 1p06 / 1p012 / 1p0

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 word of the result comes from the word in the same place in each source.
VCVTUW2PH: element by elementResult word i comes from word i of xmm2. Result words 7 to 0: r7, unchanged (bit 6 of k1 is 0), r5, r4, r3, r2, r1, r0.01234567xmm2or m128a11111110k1r0r1r2r3r4r5r7xmm1

Every word works alike: 8, 16 and 32 words in the xmm, ymm and zmm forms. The forms write under a mask: where its bit is 0, the element keeps its old value, or zeroes it with {z}. With m16bcst, one word from memory stands for every element of the last source.

Result word i comes from word i of xmm2. Result words 7 to 0: r7, unchanged (bit 6 of k1 is 0), r5, r4, r3, r2, 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 // 16):
    if k1[i]:
        zmm1.f16[i] = to_f16(src2.w[i])
    elif zeroing:
        zmm1.f16[i] = 0
    # else: zmm1.f16[i] keeps its value
# m16bcst: src2.w[i] is the m16 for every i
# {er}: the form's rounding, not MXCSR.RC, and no flags
# zmm1 is zeroed from bit VL up

Not run on a processor: none of these processors has AVX512-FP16. The tests check its arithmetic against MPFR.

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
VCVTUW2PH xmm {k}{z}, xmm/m128/m16bcst VCVTUW2PH ymm {k}{z}, ymm/m256/m16bcst VCVTUW2PH zmm {k}{z}, zmm/m512/m16bcst, {er}
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm/m128/m16bcst, ymm/m256/m16bcst, zmm/m512/m16bcstexplicitread

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 VCVTUW2PH, 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_cvtepu16_ph __m128h _mm_cvtepu16_ph(__m128i __A)

VCVTUW2PH xmm, xmm EVEX.128 -mavx512fp16 -mavx512vl

_mm_mask_cvtepu16_ph __m128h _mm_mask_cvtepu16_ph(__m128h __W, __mmask8 __U, __m128i __A)

VCVTUW2PH xmm {k}, xmm EVEX.128 -mavx512fp16 -mavx512vl

_mm_maskz_cvtepu16_ph __m128h _mm_maskz_cvtepu16_ph(__mmask8 __U, __m128i __A)

VCVTUW2PH xmm {k}{z}, xmm EVEX.128 -mavx512fp16 -mavx512vl

_mm256_cvtepu16_ph __m256h _mm256_cvtepu16_ph(__m256i __A)

VCVTUW2PH ymm, ymm EVEX.256 -mavx512fp16 -mavx512vl

_mm256_mask_cvtepu16_ph __m256h _mm256_mask_cvtepu16_ph(__m256h __W, __mmask16 __U, __m256i __A)

VCVTUW2PH ymm {k}, ymm EVEX.256 -mavx512fp16 -mavx512vl

_mm256_maskz_cvtepu16_ph __m256h _mm256_maskz_cvtepu16_ph(__mmask16 __U, __m256i __A)

VCVTUW2PH ymm {k}{z}, ymm EVEX.256 -mavx512fp16 -mavx512vl

_mm512_cvt_roundepu16_ph __m512h _mm512_cvt_roundepu16_ph(__m512i A, const int R)

VCVTUW2PH zmm, zmm, {er} EVEX.512 -mavx512fp16

_mm512_cvtepu16_ph __m512h _mm512_cvtepu16_ph(__m512i __A)

VCVTUW2PH zmm, zmm EVEX.512 -mavx512fp16

_mm512_mask_cvt_roundepu16_ph __m512h _mm512_mask_cvt_roundepu16_ph(__m512h W, __mmask32 U, __m512i A, const int R)

VCVTUW2PH zmm {k}, zmm, {er} EVEX.512 -mavx512fp16

_mm512_mask_cvtepu16_ph __m512h _mm512_mask_cvtepu16_ph(__m512h __W, __mmask32 __U, __m512i __A)

VCVTUW2PH zmm {k}, zmm EVEX.512 -mavx512fp16

_mm512_maskz_cvt_roundepu16_ph __m512h _mm512_maskz_cvt_roundepu16_ph(__mmask32 U, __m512i A, const int R)

VCVTUW2PH zmm {k}{z}, zmm, {er} EVEX.512 -mavx512fp16

_mm512_maskz_cvtepu16_ph __m512h _mm512_maskz_cvtepu16_ph(__mmask32 __U, __m512i __A)

VCVTUW2PH zmm {k}{z}, zmm EVEX.512 -mavx512fp16

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
AVX512_FP16_128

AVX10.1
CPUID.(EAX=07H,ECX=1):EDX[19] AVX10
CPUID.(EAX=24H,ECX=0):EBX[7:0] ≥ 1 AVX10 version

or

AVX512_FP16 + AVX512VL
CPUID.(EAX=07H,ECX=0):EDX[23] AVX512_FP16
CPUID.(EAX=07H,ECX=0):EBX[31] AVX512VL

Nova Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Zen 6
AVX512_FP16_256
Same as AVX512_FP16_128Same as AVX512_FP16_128
AVX512_FP16_512

AVX10.1
CPUID.(EAX=07H,ECX=1):EDX[19] AVX10
CPUID.(EAX=24H,ECX=0):EBX[7:0] ≥ 1 AVX10 version

or

AVX512_FP16
CPUID.(EAX=07H,ECX=0):EDX[23] AVX512_FP16

Same as AVX512_FP16_128

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 Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
  6. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2C, page 5-150 (VCVTUW2PH)
  7. Intel 64 and IA-32 Architectures Optimization Reference Manual, Volume 1 (248966-051, October 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.