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

VPERMI2PS picks singles from a table of two registers, with the indices in the destination, which the results then overwrite. It works as VPERMI2D does for doublewords, and that page explains the index bits, the I and T forms and how compilers choose between them; VPERMT2PS is the T form for singles. The elements are moved as 32-bit patterns: nothing is rounded or quieted, and the manual lists no floating-point exception for it, so MXCSR plays no part. Intel’s optimization manual introduces the two-source permutes with a drawing of this instruction (Section 17.8, Figure 17-10).

Indices in a float register

The index vector is read as integers, even though the instruction otherwise works on singles, and only its low bits count: five for a ZMM table of 32 singles, four to pick the element and one the register, and one fewer per halving of the width. In the cases recorded on Zen 5, which used whatever bits the registers held:

  • in vpermi2ps ymm9{k2}{z}, ymm9, ymm14, element 0 of YMM9 held C0B3A699h, about -5.614 as a single; its low four bits, 1001b, picked element 1 of YMM14, and other elements picked from YMM9 itself, the register serving as indices and first table at once;
  • against a broadcast single, 8 of the 10 elements of ZMM24 that K4 selected had bit 4 set in their index and took the broadcast value, the other two came from ZMM3, and the 6 unselected elements kept their indices.

In compiled code

For _mm512_permutex2var_ps(a, idx, b), GCC 14 and Clang 23 at -O2 with -march=x86-64-v4 emit VPERMT2PS when a may be overwritten and VPERMI2PS when only the index register is free, and _mm512_mask2_permutex2var_ps, whose unselected elements keep the index, is always VPERMI2PS. For a fixed shuffle of two float vectors with __builtin_shufflevector, such as the interleave 0, 8, 1, 9 …, GCC loads the indices into the destination and uses VPERMI2PS, while Clang uses VPERMT2PS. Splitting complex floats into real and imaginary arrays depends on the count in GCC 14.2: with a constant count it is VPERMT2PS on zmm registers, and with a count known only at run time the loop stays scalar at -O2. Clang 23.1 uses VPERMT2PS on ymm registers in both cases.

AMD’s latency spreadsheet for Zen 5 lists it as one macro-op on pipes FP1 and FP2, with a latency of 3, 4 and 5 cycles for XMM, YMM and ZMM.

Forms

Every encoding of VPERMI2PS that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPERMI2PS zmm {k}{z}, zmm, zmm VPERMI2PS_ZMMf32_MASKmskw_ZMMf32_ZMMf32_AVX512EVEX.512.66.0F38.W0 77 /rAVX10.1 or AVX512F
VPERMI2PS zmm {k}{z}, zmm, m512/m32bcst VPERMI2PS_ZMMf32_MASKmskw_ZMMf32_MEMf32_AVX512EVEX.512.66.0F38.W0 77 /rAVX10.1 or AVX512F
VPERMI2PS xmm {k}{z}, xmm, xmm VPERMI2PS_XMMf32_MASKmskw_XMMf32_XMMf32_AVX512EVEX.128.66.0F38.W0 77 /rAVX10.1 or AVX512F + AVX512VL
VPERMI2PS xmm {k}{z}, xmm, m128/m32bcst VPERMI2PS_XMMf32_MASKmskw_XMMf32_MEMf32_AVX512EVEX.128.66.0F38.W0 77 /rAVX10.1 or AVX512F + AVX512VL
VPERMI2PS ymm {k}{z}, ymm, ymm VPERMI2PS_YMMf32_MASKmskw_YMMf32_YMMf32_AVX512EVEX.256.66.0F38.W0 77 /rAVX10.1 or AVX512F + AVX512VL
VPERMI2PS ymm {k}{z}, ymm, m256/m32bcst VPERMI2PS_YMMf32_MASKmskw_YMMf32_MEMf32_AVX512EVEX.256.66.0F38.W0 77 /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.
Modelzmm {k}{z}, zmm, zmmzmm {k}{z}, zmm, m512/m32bcst
ymm {k}{z}, ymm, m256/m32bcst
xmm {k}{z}, xmm, xmmxmm {k}{z}, xmm, m128/m32bcstymm {k}{z}, ymm, ymm
Skylake-SP, Ice Lake3 / 1p510 / 1p53 / 1p59 / 1p53 / 1p5
Sapphire Rapids3 / 1p511 / 1p53 / 1p510 / 1p53 / 1p5
Zen 45 / 1FP1 FP214 / 1FP13 / 11FP1 FP214 / 1FP14 / 12FP1 FP2
  1. Zen 4 model: AMD's spreadsheets give reciprocal throughput 0.5 for Zen 4 and Zen 5 (AMD 57647, row 2238; AMD 58455, row 591).
  2. Zen 4 model: AMD's spreadsheets give reciprocal throughput 0.5 for Zen 4 and Zen 5 (AMD 57647, row 2239; AMD 58455, row 592).

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.

Permute from two tables: each single of the result is the single that the index in the same place of zmm1 numbers in zmm2 or, with the index's next bit set, in zmm3.
VPERMI2PS with an example index vectorWith the example indices, result singles 15 to 0: b8, unchanged (bit 14 of k1 is 0), b7, a10, a1, b5, b12, a5, a15, b2, a9, b6, b14, a0, b1, a3.317030229181552821110231324zmm1index0135910131524678111214zmm2a1111111111111110k1a3a0a9a15a5a1a10b1b14b6b2b12b5b7b8zmm10349101113151256781214zmm3or m512b

Example index vector in zmm1 (element 0 on the right); only its low 5 bits count. Shown for the zmm form; the xmm and ymm forms work the same on 4 and 8 singles. Under the mask, a masked-off element keeps the old value of zmm1, the index.

With the example indices, result singles 15 to 0: b8, unchanged (bit 14 of k1 is 0), b7, a10, a1, b5, b12, a5, a15, b2, a9, b6, b14, a0, b1, a3.

Operation

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

n = VL // 32           # 4 in xmm, 8 in ymm, 16 in zmm
for i in range(n):
    if k1[i]:
        x = zmm1.d[i]  # the index, in zmm1
        if x & n:
            zmm1.d[i] = src3.d[x % n]
        else:
            zmm1.d[i] = zmm2.d[x % n]
    elif zeroing:
        zmm1.d[i] = 0
    # else: zmm1.d[i] keeps its value
# m32bcst: src3.f32[i] is the m32 for every i
# zmm1 is zeroed from bit VL up

Run on AMD Zen 5 (EPYC 9645): 6 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
VPERMI2PS xmm {k}{z}, xmm, xmm/m128/m32bcst VPERMI2PS ymm {k}{z}, ymm, ymm/m256/m32bcst VPERMI2PS zmm {k}{z}, zmm, zmm/m512/m32bcst
xmm, ymm, zmmexplicitread, write (masked)
{k}explicitread (write mask)
xmm, ymm, zmmexplicitread
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.

All forms
AVX512-E4NF

Attributes

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

All forms
write masking
Memory forms
embedded broadcast (tuple Full)

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VPERMI2PS, 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_permutex2var_ps __m128 _mm_permutex2var_ps(__m128 __A, __m128i __I, __m128 __B)

VPERMI2PS xmm, xmm, xmm EVEX.128 -mavx512vlwhen __A comes from memory

_mm_mask2_permutex2var_ps __m128 _mm_mask2_permutex2var_ps(__m128 __A, __m128i __I, __mmask8 __U, __m128 __B)

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

_mm_maskz_permutex2var_ps __m128 _mm_maskz_permutex2var_ps(__mmask8 __U, __m128 __A, __m128i __I, __m128 __B)

VPERMI2PS xmm {k}{z}, xmm, xmm EVEX.128 -mavx512vlwhen __A comes from memory

_mm256_permutex2var_ps __m256 _mm256_permutex2var_ps(__m256 __A, __m256i __I, __m256 __B)

VPERMI2PS ymm, ymm, ymm EVEX.256 -mavx512vlwhen __A comes from memory

_mm256_mask2_permutex2var_ps __m256 _mm256_mask2_permutex2var_ps(__m256 __A, __m256i __I, __mmask8 __U, __m256 __B)

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

_mm256_maskz_permutex2var_ps __m256 _mm256_maskz_permutex2var_ps(__mmask8 __U, __m256 __A, __m256i __I, __m256 __B)

VPERMI2PS ymm {k}{z}, ymm, ymm EVEX.256 -mavx512vlwhen __A comes from memory

_mm512_permutex2var_ps __m512 _mm512_permutex2var_ps(__m512 __A, __m512i __I, __m512 __B)

VPERMI2PS zmm, zmm, zmm EVEX.512 -mavx512fwhen __A comes from memory

_mm512_mask2_permutex2var_ps __m512 _mm512_mask2_permutex2var_ps(__m512 __A, __m512i __I, __mmask16 __U, __m512 __B)

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

_mm512_maskz_permutex2var_ps __m512 _mm512_maskz_permutex2var_ps(__mmask16 __U, __m512 __A, __m512i __I, __m512 __B)

VPERMI2PS zmm {k}{z}, zmm, zmm EVEX.512 -mavx512fwhen __A comes from memory

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
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 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-505 (VPERMI2W/D/Q/PS/PD)
  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.