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

VSHUFPS is SHUFPS with a separate destination: the low two singles of each result come from the first source and the high two from the second, each picked by a 2-bit field of the immediate, as SHUFPS’s page explains. The ymm and zmm forms apply the one immediate to every 128-bit lane, and a field picks only within its own lane. Memory needs no alignment, and the destination is zeroed above the vector length. The VEX forms need AVX, ymm included; the EVEX forms (AVX-512F, with AVX512VL below 512 bits, or AVX10.1) add a write mask per single and a second source of one broadcast single. Zen 5’s recorded cases:

  • vshufps ymm7, ymm11, ymm7, 0x88 gave elements 0 and 2 of YMM11, then 0 and 2 of YMM7 in the low lane, and elements 4 and 6 of each in the high lane: the even singles of both sources, lane by lane.
  • vshufps zmm5{k6}, zmm5, dword bcst [mem], 0x42 wrote the single from memory into elements 2, 7 and 14, where the fields pick the second source, singles of ZMM5’s own lanes into elements 5, 8 and 9, and kept the other ten.

Lanes in compiled code

In our builds at -O2, splitting a global array of (x, y) pairs into two arrays shows what the lanes cost. With -march=x86-64-v3, Clang 23 takes the even singles with VSHUFPS 88h and the odd ones with DDh, as SHUFPS does, and then puts the quadwords in order with vpermpd ymm, ymm, 0xd8, since each lane holds results of both sources; GCC 14 uses VPERMD and VBLENDPS instead. With -march=x86-64-v4 both use VPERMT2PS, GCC on zmm registers and Clang on ymm. _mm_set1_ps(x), a SHUFPS for the x86-64 baseline, becomes the register form of VBROADCASTSS at -v3.

AMD’s latency spreadsheet for Zen 5 gives VSHUFPS, in its VEX row and its EVEX row alike, one macro-op with a latency of 1 cycle, four per cycle.

In the optimization guide

What the optimization guide says about VSHUFPS, a line per claim. Each links to the claim in the guide, with its sources and where they differ.

Vectors

  • Shuffles and lane crossing: Intel’s shuffles share one port, so blends and shuffles done by loads relieve it; Ice Lake and Golden Cove add a second, in-lane one.

Forms

Every encoding of VSHUFPS that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VSHUFPS xmm, xmm, m128, imm8 VSHUFPS_XMMdq_XMMdq_MEMdq_IMMbVEX.128.NP.0F.WIG C6 /r ibAVX
VSHUFPS xmm, xmm, xmm, imm8 VSHUFPS_XMMdq_XMMdq_XMMdq_IMMbVEX.128.NP.0F.WIG C6 /r ibAVX
VSHUFPS ymm, ymm, m256, imm8 VSHUFPS_YMMqq_YMMqq_MEMqq_IMMbVEX.256.NP.0F.WIG C6 /r ibAVX
VSHUFPS ymm, ymm, ymm, imm8 VSHUFPS_YMMqq_YMMqq_YMMqq_IMMbVEX.256.NP.0F.WIG C6 /r ibAVX
VSHUFPS zmm {k}{z}, zmm, zmm, imm8 VSHUFPS_ZMMf32_MASKmskw_ZMMf32_ZMMf32_IMM8_AVX512EVEX.512.NP.0F.W0 C6 /r ibAVX10.1 or AVX512F
VSHUFPS zmm {k}{z}, zmm, m512/m32bcst, imm8 VSHUFPS_ZMMf32_MASKmskw_ZMMf32_MEMf32_IMM8_AVX512EVEX.512.NP.0F.W0 C6 /r ibAVX10.1 or AVX512F
VSHUFPS xmm {k}{z}, xmm, xmm, imm8 VSHUFPS_XMMf32_MASKmskw_XMMf32_XMMf32_IMM8_AVX512EVEX.128.NP.0F.W0 C6 /r ibAVX10.1 or AVX512F + AVX512VL
VSHUFPS xmm {k}{z}, xmm, m128/m32bcst, imm8 VSHUFPS_XMMf32_MASKmskw_XMMf32_MEMf32_IMM8_AVX512EVEX.128.NP.0F.W0 C6 /r ibAVX10.1 or AVX512F + AVX512VL
VSHUFPS ymm {k}{z}, ymm, ymm, imm8 VSHUFPS_YMMf32_MASKmskw_YMMf32_YMMf32_IMM8_AVX512EVEX.256.NP.0F.W0 C6 /r ibAVX10.1 or AVX512F + AVX512VL
VSHUFPS ymm {k}{z}, ymm, m256/m32bcst, imm8 VSHUFPS_YMMf32_MASKmskw_YMMf32_MEMf32_IMM8_AVX512EVEX.256.NP.0F.W0 C6 /r ibAVX10.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, xmm, m128, imm8
xmm {k}{z}, xmm, m128/m32bcst, imm8
xmm, xmm, xmm, imm8
xmm {k}{z}, xmm, xmm, imm8
ymm {k}{z}, ymm, ymm, imm8
ymm, ymm, m256, imm8
ymm {k}{z}, ymm, m256/m32bcst, imm8
ymm, ymm, ymm, imm8zmm {k}{z}, zmm, zmm, imm8zmm {k}{z}, zmm, m512/m32bcst, imm8
Sandy Bridge, Haswell, Skylake7 / 1p51 / 1p58 / 1p51 / 1p5
Broadwell6 / 1p51 / 1p57 / 1p51 / 1p5
Skylake-SP7 / 1p51 / 1p58 / 1p51 / 1p51 / 1p58 / 1p5
Ice Lake7 / 0.5p151 / 0.5p158 / 0.5p151 / 0.5p151 / 1p58 / 1p5
Alder Lake8 / 0.5p151 / 0.5p159 / 0.5p151 / 0.5p15
Sapphire Rapids8 / 0.5p151 / 0.5p159 / 0.5p151 / 0.5p151 / 1p59 / 1p5
Lunar Lake7 / 2V2 V31 / 0.5V2 V39 / 0.5V2 V31 / 0.5V2 V3
Piledriver7 / 1.5FPFMA FPU0 FPU12 / 1FPFMA FPU0 FPU17 / 2FPFMA FPU0 FPU12 / 2FPFMA FPU0 FPU1
Zen8 / 0.5FPU1 FPU21 / 0.5FPU1 FPU28 / 1FPU1 FPU21 / 1FPU1 FPU2
Zen 28 / 0.5FPU1 FPU21 / 0.5FPU1 FPU28 / 0.5FPU1 FPU21 / 0.5FPU1 FPU2
Zen 38 / 0.5FP1 FP21 / 0.5FP1 FP28 / 0.5FP1 FP21 / 0.5FP1 FP2
Zen 48 / 0.5FP1 FP21 / 0.5FP1 FP28 / 0.5FP1 FP21 / 0.5FP1 FP21 / 1FP1 FP28 / 1FP1 FP2
Jaguar6 / 1FPA FPM FPU0 FPU11 / 0.5FPA FPM FPU0 FPU16 / 2FPA FPM FPU0 FPU11 / 1FPA FPM FPU0 FPU1

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.

Shuffle by immediate: the low two singles of the result come from xmm2, the high two from xmm3, each picked by two bits of imm8.
VSHUFPS with imm8 = 0x4EWith imm8 = 0x4E, result singles 3 to 0: b1, unchanged (bit 2 of k1 is 0), a3, a2.10110001imm80x4E0123xmm2a1110k1a2a3b1xmm10123xmm3or m128b

Example: imm8 = 0x4E (0100 1110 in binary). The ymm and zmm forms repeat this in each 128-bit lane. 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 xmm3.

With imm8 = 0x4E, result singles 3 to 0: b1, unchanged (bit 2 of k1 is 0), a3, a2.

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):
    k = imm8 >> 2 * (i % 4) & 3
    j = i - i % 4 + k
    if k1[i]:  # 1 without a write mask
        if i % 4 < 2:
            zmm1.d[i] = zmm2.d[j]
        else:
            zmm1.d[i] = src3.d[j]
    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): 10 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
VSHUFPS xmm, xmm, xmm/m128, imm8 VSHUFPS ymm, ymm, ymm/m256, imm8
xmm, ymmexplicitwrite
xmm, ymmexplicitread
xmm/m128, ymm/m256explicitread
imm8explicitread
VSHUFPS xmm {k}{z}, xmm, xmm/m128/m32bcst, imm8 VSHUFPS ymm {k}{z}, ymm, ymm/m256/m32bcst, imm8 VSHUFPS zmm {k}{z}, zmm, zmm/m512/m32bcst, imm8
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm, ymm, zmmexplicitread
xmm/m128/m32bcst, ymm/m256/m32bcst, zmm/m512/m32bcstexplicitread
imm8explicitread

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-4
EVEX forms
AVX512-E4NF

Attributes

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

EVEX forms
write masking
EVEX memory forms
embedded broadcast (tuple Full)

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VSHUFPS, 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_shuffle_ps __m128 _mm_shuffle_ps(__m128 a, __m128 b, const int mask)

VSHUFPS xmm, xmm, xmm, imm8 VEX.128 -mavxwith AVX enabled

_mm_mask_permute_ps __m128 _mm_mask_permute_ps(__m128 W, __mmask8 U, __m128 X, const int C)

VSHUFPS xmm {k}, xmm, xmm, imm8 EVEX.128 -mavx512vl

_mm_mask_shuffle_ps __m128 _mm_mask_shuffle_ps(__m128 W, __mmask8 U, __m128 A, __m128 B, const int M)

VSHUFPS xmm {k}, xmm, xmm, imm8 EVEX.128 -mavx512vl

_mm_maskz_permute_ps __m128 _mm_maskz_permute_ps(__mmask8 U, __m128 X, const int C)

VSHUFPS xmm {k}{z}, xmm, xmm, imm8 EVEX.128 -mavx512vl

_mm_maskz_shuffle_ps __m128 _mm_maskz_shuffle_ps(__mmask8 U, __m128 A, __m128 B, const int M)

VSHUFPS xmm {k}{z}, xmm, xmm, imm8 EVEX.128 -mavx512vl

_mm256_shuffle_ps __m256 _mm256_shuffle_ps(__m256 a, __m256 b, const int mask)

VSHUFPS ymm, ymm, ymm, imm8 VEX.256 -mavx

_mm256_mask_permute_ps __m256 _mm256_mask_permute_ps(__m256 W, __mmask8 U, __m256 X, const int C)

VSHUFPS ymm {k}, ymm, ymm, imm8 EVEX.256 -mavx512vl

_mm256_mask_shuffle_ps __m256 _mm256_mask_shuffle_ps(__m256 W, __mmask8 U, __m256 A, __m256 B, const int M)

VSHUFPS ymm {k}, ymm, ymm, imm8 EVEX.256 -mavx512vl

_mm256_maskz_permute_ps __m256 _mm256_maskz_permute_ps(__mmask8 U, __m256 X, const int C)

VSHUFPS ymm {k}{z}, ymm, ymm, imm8 EVEX.256 -mavx512vl

_mm256_maskz_shuffle_ps __m256 _mm256_maskz_shuffle_ps(__mmask8 U, __m256 A, __m256 B, const int M)

VSHUFPS ymm {k}{z}, ymm, ymm, imm8 EVEX.256 -mavx512vl

_mm512_permute_ps __m512 _mm512_permute_ps(__m512 X, const int C)

VSHUFPS zmm, zmm, zmm, imm8 EVEX.512 -mavx512f

_mm512_shuffle_ps __m512 _mm512_shuffle_ps(__m512 A, __m512 B, const int M)

VSHUFPS zmm, zmm, zmm, imm8 EVEX.512 -mavx512f

_mm512_mask_permute_ps __m512 _mm512_mask_permute_ps(__m512 W, __mmask16 U, __m512 X, const int C)

VSHUFPS zmm {k}, zmm, zmm, imm8 EVEX.512 -mavx512f

_mm512_mask_shuffle_ps __m512 _mm512_mask_shuffle_ps(__m512 W, __mmask16 U, __m512 A, __m512 B, const int M)

VSHUFPS zmm {k}, zmm, zmm, imm8 EVEX.512 -mavx512f

_mm512_maskz_permute_ps __m512 _mm512_maskz_permute_ps(__mmask16 U, __m512 X, const int C)

VSHUFPS zmm {k}{z}, zmm, zmm, imm8 EVEX.512 -mavx512f

_mm512_maskz_shuffle_ps __m512 _mm512_maskz_shuffle_ps(__mmask16 U, __m512 A, __m512 B, const int M)

VSHUFPS zmm {k}{z}, zmm, zmm, imm8 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 2B, page 4-651 (SHUFPS)
  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)
  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.