Instruction
VPORQ
Computes the bitwise OR of two vectors, masked at quadword granularity.
- Extensions
- Forms
- 6 (6 EVEX)
- Data
- Intel XED v2026.08.23
VPORQ is the EVEX form of VPOR with a write mask that
selects quadwords: the bitwise OR of two 128-, 256- or 512-bit values,
whose memory operand may be one quadword repeated to every element
({1to8} at 512 bits). VPORD is the same with
doublewords; unmasked, the two give the same bits.
VPANDD shows what the EVEX forms add and how GCC 14
and Clang 23 choose among such names.
On Zen 5, vporq zmm0{k1}, zmm31, qword bcst [mem] with 1 in memory
and A0h in the low byte of K1 set bit 0 of quadwords 5 and 7 of ZMM31
into ZMM0 and left the other six of ZMM0 alone. With a merging mask
the destination keeps what the mask leaves out, so OR under a mask can
set bits in only some elements of a vector.
In compiled code
GCC 14 at -O2 with -march=x86-64-v4 uses VPORQ for long long
data and also where the element size does not matter:
- Setting bits.
q[i] |= 1ULL << 63becomes a VPBROADCASTQ of the constant before the loop and one VPORQ per eight elements. - Bytes.
s[i] = t[i] | 0x20overchararrays, which turns ASCII letters to lower case, is a VPBROADCASTB and VPORQ on zmm registers, since an OR without a mask has no element size. With-mavx512falone GCC drops to VEX VPOR on ymm registers for that loop, and Clang 23 uses VPORQ on zmm registers. - Testing a whole array. Whether any
long longis nonzero is an OR of everything, done in the loop by VPTERNLOGQ on two vectors at a time; GCC folds the result with VEXTRACTI64X4 and VEXTRACTI64X2, each followed by VPORQ.
Clang 23 with -march=x86-64-v4 uses VORPS and, for
_mm512_mask_or_epi64, a masked VORPD instead, which
selects the same quadwords; with -mavx512f it emits VPORQ for both.
For a byte constant such as _mm512_set1_epi8(0x20) it builds one
quadword and ORs with a {1to8} operand.
AMD’s Zen 5 latency spreadsheet gives the EVEX row of VPORQ one cycle and four per cycle on any of the four vector pipes. Zen 5’s 6 recorded cases cover the register and memory forms, broadcast included, at all three widths.
Forms
| Instruction | Encoding | Requires |
|---|---|---|
VPORQ zmm {k}{z}, zmm, zmm
VPORQ_ZMMu64_MASKmskw_ZMMu64_ZMMu64_AVX512 | EVEX.512.66.0F.W1 EB /r | AVX10.1 or AVX512F |
VPORQ zmm {k}{z}, zmm, m512/m64bcst
VPORQ_ZMMu64_MASKmskw_ZMMu64_MEMu64_AVX512 | EVEX.512.66.0F.W1 EB /r | AVX10.1 or AVX512F |
VPORQ xmm {k}{z}, xmm, xmm
VPORQ_XMMu64_MASKmskw_XMMu64_XMMu64_AVX512 | EVEX.128.66.0F.W1 EB /r | AVX10.1 or AVX512F + AVX512VL |
VPORQ xmm {k}{z}, xmm, m128/m64bcst
VPORQ_XMMu64_MASKmskw_XMMu64_MEMu64_AVX512 | EVEX.128.66.0F.W1 EB /r | AVX10.1 or AVX512F + AVX512VL |
VPORQ ymm {k}{z}, ymm, ymm
VPORQ_YMMu64_MASKmskw_YMMu64_YMMu64_AVX512 | EVEX.256.66.0F.W1 EB /r | AVX10.1 or AVX512F + AVX512VL |
VPORQ ymm {k}{z}, ymm, m256/m64bcst
VPORQ_YMMu64_MASKmskw_YMMu64_MEMu64_AVX512 | EVEX.256.66.0F.W1 EB /r | AVX10.1 or AVX512F + AVX512VL |
Latency and throughput
| Model | zmm {k}{z}, zmm, zmm | zmm {k}{z}, zmm, m512/m64bcst | xmm {k}{z}, xmm, xmmymm {k}{z}, ymm, ymm | xmm {k}{z}, xmm, m128/m64bcst | ymm {k}{z}, ymm, m256/m64bcst |
|---|---|---|---|---|---|
| Skylake-SP, Ice Lake | 1 / 0.5p05 | 8 / 0.5p05 | 1 / 0.33p015 | 7 / 0.5p015 | 8 / 0.5p015 |
| Sapphire Rapids | 1 / 0.5p05 | 9 / 0.5p05 | 1 / 0.33p015 | 8 / 0.33p015 | 9 / 0.33p015 |
| Zen 4 | 1 / 0.5FP0 FP1 FP2 FP3 | 8 / 0.5FP0 FP1 FP2 FP3 | 1 / 0.25FP0 FP1 FP2 FP3 | 8 / 0.5FP0 FP1 FP2 FP3 | 8 / 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.
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.
Result quadword i comes from quadword i of xmm2 and xmm3. Result quadwords 1 to 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 // 64):
if k1[i]:
zmm1.q[i] = zmm2.q[i] | src3.q[i]
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 upRun on AMD Zen 5 (EPYC 9645): 6 cases.
Operands
| Operand | Kind | Action |
|---|---|---|
VPORQ xmm {k}{z}, xmm, xmm/m128/m64bcst VPORQ ymm {k}{z}, ymm, ymm/m256/m64bcst VPORQ zmm {k}{z}, zmm, zmm/m512/m64bcst | ||
xmm, ymm, zmm | explicit | write (masked) |
{k} | explicit | read (write mask) |
xmm, ymm, zmm | explicit | read |
xmm/m128/m64bcst, ymm/m256/m64bcst, zmm/m512/m64bcst | 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.
- 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 VPORQ, 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_mask_or_epi64
__m128i _mm_mask_or_epi64(__m128i __W, __mmask8 __U, __m128i __A, __m128i __B) |
|
_mm_mask_or_pd
__m128d _mm_mask_or_pd(__m128d __W, __mmask8 __U, __m128d __A, __m128d __B) |
|
_mm_maskz_or_epi64
__m128i _mm_maskz_or_epi64(__mmask8 __U, __m128i __A, __m128i __B) |
|
_mm_maskz_or_pd
__m128d _mm_maskz_or_pd(__mmask8 __U, __m128d __A, __m128d __B) |
|
_mm256_mask_or_epi64
__m256i _mm256_mask_or_epi64(__m256i __W, __mmask8 __U, __m256i __A, __m256i __B) |
|
_mm256_mask_or_pd
__m256d _mm256_mask_or_pd(__m256d __W, __mmask8 __U, __m256d __A, __m256d __B) |
|
_mm256_maskz_or_epi64
__m256i _mm256_maskz_or_epi64(__mmask8 __U, __m256i __A, __m256i __B) |
|
_mm256_maskz_or_pd
__m256d _mm256_maskz_or_pd(__mmask8 __U, __m256d __A, __m256d __B) |
|
_mm512_or_epi64
__m512i _mm512_or_epi64(__m512i __a, __m512i __b) |
|
_mm512_or_pd
__m512d _mm512_or_pd(__m512d __A, __m512d __B) |
|
_mm512_or_si512
__m512i _mm512_or_si512(__m512i __a, __m512i __b) |
|
_mm512_mask_or_epi64
__m512i _mm512_mask_or_epi64(__m512i __src, __mmask8 __k, __m512i __a, __m512i __b) |
|
_mm512_mask_or_pd
__m512d _mm512_mask_or_pd(__m512d __W, __mmask8 __U, __m512d __A, __m512d __B) |
|
_mm512_maskz_or_epi64
__m512i _mm512_maskz_or_epi64(__mmask8 __k, __m512i __a, __m512i __b) |
|
_mm512_maskz_or_pd
__m512d _mm512_maskz_or_pd(__mmask8 __U, __m512d __A, __m512d __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.
| ISA set | CPUID | Processors |
|---|---|---|
AVX512F_512 | AVX10.1 or 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 or AVX512F + 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_128 | Same as AVX512F_128 |
More AVX10.1 instructions
- VPMOVZXBD
- VPMOVZXBQ
- VPMOVZXBW
- VPMOVZXDQ
- VPMOVZXWD
- VPMOVZXWQ
- VPMULDQ
- VPMULHRSW
- VPMULHUW
- VPMULHW
- VPMULLD
- VPMULLQ
- VPMULLW
- VPMULTISHIFTQB
- VPMULUDQ
- VPOPCNTB
- VPOPCNTD
- VPOPCNTQ
- VPOPCNTW
- VPORD
- VPROLD
- VPROLQ
- VPROLVD
- VPROLVQ
- VPRORD
- VPRORQ
- VPRORVD
- VPRORVQ
- VPSADBW
- VPSCATTERDD
- VPSCATTERDQ
- VPSCATTERQD
- VPSCATTERQQ
- VPSHLDD
- VPSHLDQ
- VPSHLDVD
- VPSHLDVQ
- VPSHLDVW
- VPSHLDW
- VPSHRDD
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 Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
- Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2B, page 4-411 (POR)
- 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.