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

VPTERNLOGQ computes a bitwise function of three inputs whose truth table is its immediate, exactly as VPTERNLOGD does; that page explains how to read and build the immediate. The two differ only where elements matter: VPTERNLOGQ applies a write mask per quadword and broadcasts a quadword from memory, so it is the one to use with a mask from a 64-bit compare such as VPCMPQ, or with a 64-bit constant in memory. Without either, both give the same bits, and the compilers pick freely: GCC 14 and Clang 23 at -O2 fill a vector of uint64_t with ones using VPTERNLOGD and the immediate FFh.

Three-input steps in 64-bit algorithms

Hash functions built on 64-bit words, such as SHA-512 and SHA-3, are full of three-input logic. With F0h, CCh and AAh standing for the first, second and third operand, the immediate is the expression evaluated on them:

StepExpressionimm8
Keccak chia ^ (~b & c)F0h ^ (33h & AAh) = D2h
SHA-512 Ch(e & f) ^ (~e & g), e as the first operandCAh
SHA-512 Majmajority of a, b, cE8h
Keccak theta, paritya ^ b ^ c96h

On uint64_t vector types with -march=x86-64-v4, Clang 23 compiles a ^ (~b & c) to one VPTERNLOGQ with D2h, and GCC 14 to one with B4h, having put the operands in the order a, c, b. Both find 96h for the three-way XOR and a single instruction for Ch. For the majority, whether written as (a & b) ^ (a & c) ^ (b & c), with ORs, or as (a & b) | (c & (a | b)), both emit two VPTERNLOGQ instead of one with E8h; the intrinsic _mm512_ternarylogic_epi64(a, b, c, 0xE8) gives the single instruction.

Recorded on Zen 5

The cases recorded on Zen 5 include E8h with a broadcast quadword and zeroing: each selected quadword became the majority of its three inputs, and the others zero. Immediate 0Fh, NOT of the first operand, inverted only the quadwords whose mask bits were set.

AMD’s Zen 5 guide lists VPTERNLOGQ as one macro-op with a latency of one cycle and a throughput of four per cycle, at every width.

Forms

Every encoding of VPTERNLOGQ that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPTERNLOGQ zmm {k}{z}, zmm, zmm, imm8 VPTERNLOGQ_ZMMu64_MASKmskw_ZMMu64_ZMMu64_IMM8_AVX512EVEX.512.66.0F3A.W1 25 /r ibAVX10.1 or AVX512F
VPTERNLOGQ zmm {k}{z}, zmm, m512/m64bcst, imm8 VPTERNLOGQ_ZMMu64_MASKmskw_ZMMu64_MEMu64_IMM8_AVX512EVEX.512.66.0F3A.W1 25 /r ibAVX10.1 or AVX512F
VPTERNLOGQ xmm {k}{z}, xmm, xmm, imm8 VPTERNLOGQ_XMMu64_MASKmskw_XMMu64_XMMu64_IMM8_AVX512EVEX.128.66.0F3A.W1 25 /r ibAVX10.1 or AVX512F + AVX512VL
VPTERNLOGQ xmm {k}{z}, xmm, m128/m64bcst, imm8 VPTERNLOGQ_XMMu64_MASKmskw_XMMu64_MEMu64_IMM8_AVX512EVEX.128.66.0F3A.W1 25 /r ibAVX10.1 or AVX512F + AVX512VL
VPTERNLOGQ ymm {k}{z}, ymm, ymm, imm8 VPTERNLOGQ_YMMu64_MASKmskw_YMMu64_YMMu64_IMM8_AVX512EVEX.256.66.0F3A.W1 25 /r ibAVX10.1 or AVX512F + AVX512VL
VPTERNLOGQ ymm {k}{z}, ymm, m256/m64bcst, imm8 VPTERNLOGQ_YMMu64_MASKmskw_YMMu64_MEMu64_IMM8_AVX512EVEX.256.66.0F3A.W1 25 /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.
Modelzmm {k}{z}, zmm, zmm, imm8zmm {k}{z}, zmm, m512/m64bcst, imm8xmm {k}{z}, xmm, xmm, imm8
ymm {k}{z}, ymm, ymm, imm8
xmm {k}{z}, xmm, m128/m64bcst, imm8ymm {k}{z}, ymm, m256/m64bcst, imm8
Skylake-SP, Ice Lake1 / 0.33p0158 / 0.5p0151 / 0.33p0157 / 0.5p0158 / 0.5p015
Sapphire Rapids1 / 0.5p059 / 0.5p051 / 0.33p0158 / 0.33p0159 / 0.33p015
Zen 41 / 0.5FP0 FP1 FP2 FP38 / 0.5FP0 FP1 FP2 FP31 / 0.25FP0 FP1 FP2 FP38 / 0.5FP0 FP1 FP2 FP38 / 0.5FP0 FP1 FP2 FP3

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 quadword of the result comes from the quadword in the same place in each source.
VPTERNLOGQ: element by elementResult quadword i comes from quadword i of xmm1, xmm2 and xmm3. Result quadwords 1 to 0: r1, r0.01xmm1a01xmm2b01xmm3or m128c11k1r0r1xmm1

Every quadword works alike: 2, 4 and 8 quadwords 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 m64bcst, one quadword from memory stands for every element of the last source. The sources are drawn above the result, each element in its own column.

Result quadword i comes from quadword i of xmm1, xmm2 and xmm3. Result quadwords 1 to 0: 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 // 64):
    if k1[i]:
        a = zmm1.q[i]
        b = zmm2.q[i]
        c = src3.q[i]
        zmm1.q[i] = ternlog(imm8, a, b, c)
    elif zeroing:
        zmm1.q[i] = 0
    # else: zmm1.q[i] keeps its value
# m64bcst: src3.q[i] is the m64 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
VPTERNLOGQ xmm {k}{z}, xmm, xmm/m128/m64bcst, imm8 VPTERNLOGQ ymm {k}{z}, ymm, ymm/m256/m64bcst, imm8 VPTERNLOGQ zmm {k}{z}, zmm, zmm/m512/m64bcst, imm8
xmm, ymm, zmmexplicitread, write (masked)
{k}explicitread (write mask)
xmm, ymm, zmmexplicitread
xmm/m128/m64bcst, ymm/m256/m64bcst, zmm/m512/m64bcstexplicitread
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.

All forms
AVX512-E4

Attributes

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

All forms
write masking
Memory forms
embedded broadcast (tuple Full); memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VPTERNLOGQ, 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_ternarylogic_epi64 __m128i _mm_ternarylogic_epi64(__m128i A, __m128i B, __m128i C, const unsigned char imm)

VPTERNLOGQ xmm, xmm, xmm, imm8 EVEX.128 -mavx512vl

_mm_mask_ternarylogic_epi64 __m128i _mm_mask_ternarylogic_epi64(__m128i A, __mmask8 U, __m128i B, __m128i C, const unsigned char imm)

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

_mm_maskz_ternarylogic_epi64 __m128i _mm_maskz_ternarylogic_epi64(__mmask8 U, __m128i A, __m128i B, __m128i C, const unsigned char imm)

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

_mm256_ternarylogic_epi64 __m256i _mm256_ternarylogic_epi64(__m256i A, __m256i B, __m256i C, const unsigned char imm)

VPTERNLOGQ ymm, ymm, ymm, imm8 EVEX.256 -mavx512vl

_mm256_mask_ternarylogic_epi64 __m256i _mm256_mask_ternarylogic_epi64(__m256i A, __mmask8 U, __m256i B, __m256i C, const unsigned char imm)

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

_mm256_maskz_ternarylogic_epi64 __m256i _mm256_maskz_ternarylogic_epi64(__mmask8 U, __m256i A, __m256i B, __m256i C, const unsigned char imm)

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

_mm512_ternarylogic_epi64 __m512i _mm512_ternarylogic_epi64(__m512i A, __m512i B, __m512i C, const unsigned char imm)

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

_mm512_mask_ternarylogic_epi64 __m512i _mm512_mask_ternarylogic_epi64(__m512i A, __mmask8 U, __m512i B, __m512i C, const unsigned char imm)

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

_mm512_maskz_ternarylogic_epi64 __m512i _mm512_maskz_ternarylogic_epi64(__mmask8 U, __m512i A, __m512i B, __m512i C, const unsigned char imm)

VPTERNLOGQ 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
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-651 (VPTERNLOGD/VPTERNLOGQ)
  7. NIST FIPS 180-4: Secure Hash Standard (SHS) (August 2015)
  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.