Instruction
VANDPS
Computes the bitwise AND of packed singles.
VANDPS computes the bitwise AND of two vectors of singles. It looks at them only as 32-bit patterns: nothing is rounded, MXCSR plays no part, no exception is possible and NaNs pass through as bits. What makes it a floating-point instruction is its use, with constants and compare results as masks, alongside VANDNPS (which inverts its first source), VORPS and VXORPS, the VEX forms of the legacy ANDPS family.
Masks for floats
- Absolute value. Clearing bit 31 of each element is
fabsf. Fora[i] = fabsf(b[i]), GCC 14 and Clang 23 at -O2 with-march=x86-64-v3broadcast 7FFFFFFFh with VBROADCASTSS and apply it with one VANDPS per vector, taking the data straight from memory. - Copying a sign.
copysignf(b[i], c[i])takes bit 31 from c and the rest from b: VANDNPS, VANDPS and VORPS for-march=x86-64-v3in both compilers, and a single VPTERNLOGD for-march=x86-64-v4. - Selecting. A compare such as VCMPPS gives all ones or all zeros per element, so VANDPS with it zeroes the elements that failed. Code that computes a square root from VRSQRTPS’s estimate uses this to make 0 give 0 (see VSQRTPS).
EVEX needs AVX512DQ
The EVEX forms, with masking, broadcast and registers 16 to 31, came
with AVX512DQ, not AVX512F; AVX512F alone has only the integer
VPANDD and VPANDQ. With -march=x86-64-v4, which
includes DQ, GCC uses VANDPS on zmm registers for fabsf; with only
-mavx512f -mavx512vl and 512-bit vectors preferred, both compilers use
VPANDD instead. The result is the same bits either way.
AMD’s Zen 5 guide lists VANDPS and VPAND alike, one cycle on all four vector pipes, and still recommends keeping to the data type of the values, using VANDPS and VMAXPS on the results of VMULPS (Section 2.11.2).
Forms
| Instruction | Encoding | Requires |
|---|---|---|
VANDPS xmm, xmm, m128
VANDPS_XMMdq_XMMdq_MEMdq | VEX.128.NP.0F.WIG 54 /r | AVX |
VANDPS xmm, xmm, xmm
VANDPS_XMMdq_XMMdq_XMMdq | VEX.128.NP.0F.WIG 54 /r | AVX |
VANDPS ymm, ymm, m256
VANDPS_YMMqq_YMMqq_MEMqq | VEX.256.NP.0F.WIG 54 /r | AVX |
VANDPS ymm, ymm, ymm
VANDPS_YMMqq_YMMqq_YMMqq | VEX.256.NP.0F.WIG 54 /r | AVX |
VANDPS xmm {k}{z}, xmm, xmm
VANDPS_XMMu32_MASKmskw_XMMu32_XMMu32_AVX512 | EVEX.128.NP.0F.W0 54 /r | AVX10.1 or AVX512DQ + AVX512VL |
VANDPS xmm {k}{z}, xmm, m128/m32bcst
VANDPS_XMMu32_MASKmskw_XMMu32_MEMu32_AVX512 | EVEX.128.NP.0F.W0 54 /r | AVX10.1 or AVX512DQ + AVX512VL |
VANDPS ymm {k}{z}, ymm, ymm
VANDPS_YMMu32_MASKmskw_YMMu32_YMMu32_AVX512 | EVEX.256.NP.0F.W0 54 /r | AVX10.1 or AVX512DQ + AVX512VL |
VANDPS ymm {k}{z}, ymm, m256/m32bcst
VANDPS_YMMu32_MASKmskw_YMMu32_MEMu32_AVX512 | EVEX.256.NP.0F.W0 54 /r | AVX10.1 or AVX512DQ + AVX512VL |
VANDPS zmm {k}{z}, zmm, zmm
VANDPS_ZMMu32_MASKmskw_ZMMu32_ZMMu32_AVX512 | EVEX.512.NP.0F.W0 54 /r | AVX10.1 or AVX512DQ |
VANDPS zmm {k}{z}, zmm, m512/m32bcst
VANDPS_ZMMu32_MASKmskw_ZMMu32_MEMu32_AVX512 | EVEX.512.NP.0F.W0 54 /r | AVX10.1 or AVX512DQ |
Latency and throughput
| Model | xmm, xmm, m128xmm {k}{z}, xmm, m128/m32bcst | xmm, xmm, xmmxmm {k}{z}, xmm, xmmymm {k}{z}, ymm, ymm | ymm, ymm, m256ymm {k}{z}, ymm, m256/m32bcst | ymm, ymm, ymm | zmm {k}{z}, zmm, zmm | zmm {k}{z}, zmm, m512/m32bcst |
|---|---|---|---|---|---|---|
| Sandy Bridge, Haswell | 7 / 1p5 | 1 / 1p5 | 8 / 1p5 | 1 / 1p5 | ||
| Broadwell | 6 / 1p5 | 1 / 1p5 | 7 / 1p5 | 1 / 1p5 | ||
| Skylake | 7 / 0.5p015 | 1 / 0.33p015 | 8 / 0.5p015 | 1 / 0.33p015 | ||
| Skylake-SP, Ice Lake | 7 / 0.5p015 | 1 / 0.33p015 | 8 / 0.5p015 | 1 / 0.33p015 | 1 / 0.5p05 | 8 / 0.5p05 |
| Alder Lake | 8 / 0.33p015 | 1 / 0.33p015 | 9 / 0.33p015 | 1 / 0.33p015 | ||
| Sapphire Rapids | 8 / 0.33p015 | 1 / 0.33p015 | 9 / 0.33p015 | 1 / 0.33p015 | 1 / 0.5p05 | 9 / 0.5p05 |
| Lunar Lake | 7 / 2V0 V1 V2 V3 | 1 / 0.25V0 V1 V2 V3 | 8 / 2.33V0 V1 V2 V3 | 1 / 0.25V0 V1 V2 V3 | ||
| Piledriver | 7 / 1.5FPMAL | 2 / 0.5FPMAL FPU2 FPU3 | 7 / 1.5FPMAL | 2 / 1FPMAL FPU2 FPU3 | ||
| Zen | 8 / 0.5FPU0 FPU1 FPU2 FPU3 | 1 / 0.25FPU0 FPU1 FPU2 FPU3 | 8 / 0.5FPU0 FPU1 FPU2 FPU3 | 1 / 0.5FPU0 FPU1 FPU2 FPU3 | ||
| Zen 2 | 8 / 0.33FPU0 FPU1 FPU2 FPU3 | 1 / 0.25FPU0 FPU1 FPU2 FPU3 | 8 / 0.33FPU0 FPU1 FPU2 FPU3 | 1 / 0.25FPU0 FPU1 FPU2 FPU3 | ||
| Zen 3 | 8 / 0.5FP0 FP1 FP2 FP3 | 1 / 0.25FP0 FP1 FP2 FP3 | 8 / 0.5FP0 FP1 FP2 FP3 | 1 / 0.25FP0 FP1 FP2 FP3 | ||
| Zen 4 | 8 / 0.5FP0 FP1 FP2 FP3 | 1 / 0.25FP0 FP1 FP2 FP3 | 8 / 0.5FP0 FP1 FP2 FP3 | 1 / 0.25FP0 FP1 FP2 FP3 | 1 / 0.5FP0 FP1 FP2 FP3 | 8 / 0.5FP0 FP1 FP2 FP3 |
| Jaguar | 6 / 1FPA FPM FPU0 FPU1 | 1 / 0.5FPA FPM FPU0 FPU1 | 6 / 2FPA FPM FPU0 FPU1 | 1 / 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.
Every doubleword works alike: 4, 8 and 16 doublewords in the xmm, ymm and zmm forms. 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 doubleword from memory stands for every element of the last source.
Result doubleword i comes from doubleword i of xmm2 and xmm3. Result doublewords 3 to 0: a3&b3, unchanged (bit 2 of k1 is 0), a1&b1, a0&b0.
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]: # 1 without a write mask
zmm1.d[i] = zmm2.d[i] & src3.d[i]
elif zeroing:
zmm1.d[i] = 0
# else: zmm1.d[i] keeps its value
# m32bcst: src3.d[i] is the m32 for every i
# zmm1 is zeroed from bit VL upRun on AMD Zen 5 (EPYC 9645): 10 cases.
Operands
| Operand | Kind | Action |
|---|---|---|
VANDPS xmm, xmm, xmm/m128 VANDPS ymm, ymm, ymm/m256 | ||
xmm, ymm | explicit | write |
xmm, ymm | explicit | read |
xmm/m128, ymm/m256 | explicit | read |
VANDPS xmm {k}{z}, xmm, xmm/m128/m32bcst VANDPS ymm {k}{z}, ymm, ymm/m256/m32bcst VANDPS zmm {k}{z}, zmm, zmm/m512/m32bcst | ||
xmm, ymm, zmm | explicit | write (masked) |
{k} | explicit | read (write mask) |
xmm, ymm, zmm | explicit | read |
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.
- VEX forms
avx-type-4- EVEX forms
AVX512-E4
Attributes
What else XED records about the forms. How to read.
- EVEX forms
- write masking
- EVEX memory forms
- embedded broadcast (tuple Full); memory fault suppression
Intrinsics
The C intrinsics of Clang 23.1.2 that compile to VANDPS, 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_and_ps
__m128 _mm_and_ps(__m128 __a, __m128 __b) |
|
_mm256_and_ps
__m256 _mm256_and_ps(__m256 __a, __m256 __b) |
|
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.
More AVX instructions
- VADDPD
- VADDPS
- VADDSD
- VADDSS
- VADDSUBPD
- VADDSUBPS
- VANDNPD
- VANDNPS
- VANDPD
- VBLENDPD
- VBLENDPS
- VBLENDVPD
- VBLENDVPS
- VBROADCASTF128
- VBROADCASTSD
- VBROADCASTSS
- VCMPPD
- VCMPPS
- VCMPSD
- VCMPSS
- VCOMISD
- VCOMISS
- VCVTDQ2PD
- VCVTDQ2PS
- VCVTPD2DQ
- VCVTPD2PS
- VCVTPS2DQ
- VCVTPS2PD
- VCVTSD2SI
- VCVTSD2SS
- VCVTSI2SD
- VCVTSI2SS
- VCVTSS2SD
- VCVTSS2SI
- VCVTTPD2DQ
- VCVTTPS2DQ
- VCVTTSD2SI
- VCVTTSS2SI
- VDIVPD
- VDIVPS
More AVX10.1 instructions
- KXNORW
- KXORB
- KXORD
- KXORQ
- KXORW
- VADDPD
- VADDPH
- VADDPS
- VADDSD
- VADDSH
- VADDSS
- VAESDEC
- VAESDECLAST
- VAESENC
- VAESENCLAST
- VALIGND
- VALIGNQ
- VANDNPD
- VANDNPS
- VANDPD
- VBLENDMPD
- VBLENDMPS
- VBROADCASTF32X2
- VBROADCASTF32X4
- VBROADCASTF32X8
- VBROADCASTF64X2
- VBROADCASTF64X4
- VBROADCASTI32X2
- VBROADCASTI32X4
- VBROADCASTI32X8
- VBROADCASTI64X2
- VBROADCASTI64X4
- VBROADCASTSD
- VBROADCASTSS
- VCMPPD
- VCMPPH
- VCMPPS
- VCMPSD
- VCMPSH
- VCMPSS
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 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2A, page 3-72 (ANDPS)
- Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 1 (253665-093, September 2026)
- Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
- 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.