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

VCVTSI2SH converts a signed integer from a general-purpose register or memory, 32 bits or, with EVEX.W1 in 64-bit mode, 64 bits, to a half in the low 16 bits of the destination, copying bits 127:16 from the middle operand and clearing bits 128 and up. It is the conversion of C’s (_Float16) on an int or a long, and the scalar form of VCVTDQ2PH and VCVTQQ2PH. The opcode is 2Ah with the F3 prefix in EVEX map 5, where VCVTSI2SS has F3 2Ah in the 0F map; outside 64-bit mode W is ignored.

Overflow, unlike VCVTSI2SS

A single holds any 64-bit integer’s magnitude, so VCVTSI2SS lists only the precision exception; a half stops at 65504, and Intel’s entry for VCVTSI2SH adds overflow. In round to nearest every integer from 65520 up becomes infinity with OE and PE, toward zero it becomes 65504, and from 2049 up in magnitude an integer may be rounded. The rounding mode is MXCSR.RC or an {er} mode in the instruction, for a register source; there is no write mask.

In our builds

At -O2 with -march=x86-64-v4 -mavx512fp16, return x; from int to _Float16 is vcvtsi2sh xmm0, xmm0, edi in GCC 14 and vcvtsi2sh xmm0, xmm31, edi in Clang 23, which takes the untouched bits from XMM31, a register nothing else in the function writes, as it names XMM15 for the VEX conversions that CVTSI2SD’s page describes; GCC names the destination itself, an input the conversion has to wait for. For a short or signed char argument, GCC sign-extends it with MOVSX first, while Clang relies on the caller having done so; Clang also uses VCVTSI2SH for an unsigned short, which as a 32-bit value is never negative. _mm_cvt_roundi32_sh(a, b, _MM_FROUND_TO_ZERO | _MM_FROUND_NO_EXC) becomes vcvtsi2sh xmm0, xmm0, {rz-sae}, edi. Without AVX512-FP16, GCC converts an int to a double and calls __truncdfhf2, and Clang uses VCVTSI2SS and VCVTPS2PH. AMD’s Zen 5 guide does not list AVX512-FP16, and this site’s recorded cases include none of VCVTSI2SH.

Forms

Every encoding of VCVTSI2SH that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VCVTSI2SH xmm, xmm, r32, {er} VCVTSI2SH_XMMf16_XMMf16_GPR32i32_AVX512EVEX.LIG.F3.MAP5.W0 2A /rAVX10.1 or AVX512_FP16
VCVTSI2SH xmm, xmm, m32 VCVTSI2SH_XMMf16_XMMf16_MEMi32_AVX512EVEX.LIG.F3.MAP5.W0 2A /rAVX10.1 or AVX512_FP16
VCVTSI2SH xmm, xmm, r64, {er} 64-bit mode only VCVTSI2SH_XMMf16_XMMf16_GPR64i64_AVX512EVEX.LIG.F3.MAP5.W1 2A /rAVX10.1 or AVX512_FP16
VCVTSI2SH xmm, xmm, m64 64-bit mode only VCVTSI2SH_XMMf16_XMMf16_MEMi64_AVX512EVEX.LIG.F3.MAP5.W1 2A /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.

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.

Scalar: only the low half is computed; the other halves come from xmm2.
VCVTSI2SH: the low elementResult half 0 is computed from r32; halves 7 to 1 are those of xmm2. Result halves 7 to 0: a7, a6, a5, a4, a3, a2, a1, r0.01234567xmm2ar0a1a2a3a4a5a6a7xmm10r32or r64, m32, m64b

Result half 0 is computed from r32; halves 7 to 1 are those of xmm2. Result halves 7 to 0: a7, a6, a5, a4, a3, a2, a1, r0.

Operation

What the forms do, in pseudocode that our tests run against results recorded on real processors. How to read.

xmm1.f16[0] = to_f16(signed(src3))
for i in range(1, 8):
    xmm1.w[i] = xmm2.w[i]
# {er}: the form's rounding, not MXCSR.RC, and no flags
# xmm1 is zeroed from bit 128 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
VCVTSI2SH xmm, xmm, r/m32, {er} VCVTSI2SH xmm, xmm, r/m64, {er} 64-bit mode only
xmmexplicitwrite
xmmexplicitread
r/m32/64explicitread

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-E3NF

Attributes

What else XED records about the forms. How to read.

All forms
follows MXCSR

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VCVTSI2SH, 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_cvt_roundi32_sh __m128h _mm_cvt_roundi32_sh(__m128h A, int B, const int R)

VCVTSI2SH xmm, xmm, r32, {er} EVEX.LIG -mavx512fp16

_mm_cvt_roundi64_sh __m128h _mm_cvt_roundi64_sh(__m128h A, long long B, const int R)

VCVTSI2SH xmm, xmm, r64, {er} EVEX.LIG -mavx512fp16

_mm_cvti32_sh __m128h _mm_cvti32_sh(__m128h __A, int __B)

VCVTSI2SH xmm, xmm, r32 EVEX.LIG -mavx512fp16

_mm_cvti64_sh __m128h _mm_cvti64_sh(__m128h __A, long long __B)

VCVTSI2SH xmm, xmm, r64 EVEX.LIG -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_SCALAR

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

Nova Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Zen 6

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-96 (VCVTSI2SH)
  7. 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.