X86 Bit manipulation instruction set

Bit manipulation instructions sets (BMI sets) are extensions to the x86 instruction set architecture for microprocessors from Intel and AMD. The purpose of these instruction sets is to improve the speed of bit manipulation. All the instructions in these sets are non-SIMD and operate only on general-purpose registers.

There are two sets published by Intel: BMI (now referred to as BMI1) and BMI2; they were both introduced with the Haswell microarchitecture with BMI1 matching features offered by AMD's ABM instruction set and BMI2 extending them. Another two sets were published by AMD: ABM (Advanced Bit Manipulation, which is also a subset of SSE4a implemented by Intel as part of SSE4.2 and BMI1), and TBM (Trailing Bit Manipulation, an extension introduced with Piledriver-based processors as an extension to BMI1, but dropped again in Zen-based processors).

ABM (Advanced Bit Manipulation)
AMD was the first to introduce the instructions that now form Intel's BMI1 as part of its ABM (Advanced Bit Manipulation) instruction set, then later added support for Intel's new BMI2 instructions. AMD today advertises the availability of these features via Intel's BMI1 and BMI2 cpuflags and instructs programmers to target them accordingly.

While Intel considers  as part of SSE4.2 and   as part of BMI1, both Intel and AMD advertise the presence of these two instructions individually. has a separate CPUID flag of the same name, and Intel and AMD use AMD's  flag to indicate   support (since   combined with BMI1 and BMI2 completes the expanded ABM instruction set).

is related to the Bit Scan Reverse instruction, but sets the ZF (if the result is zero) and CF (if the source is zero) flags rather than setting the ZF (if the source is zero). Also, it produces a defined result (the source operand size in bits) if the source operand is zero. For a non-zero argument, sum of  and   results is argument bit width minus 1 (for example, if 32-bit argument is  , LZCNT gives 12, and BSR gives 19).

The encoding of  is such that if ABM is not supported, then the   instruction is executed instead.

BMI1 (Bit Manipulation Instruction Set 1)
The instructions below are those enabled by the  bit in CPUID. Intel officially considers  as part of BMI, but advertises   support using the   CPUID feature flag. BMI1 is available in AMD's Jaguar, Piledriver and newer processors, and in Intel's Haswell and newer processors.

is almost identical to the Bit Scan Forward instruction, but sets the ZF (if the result is zero) and CF (if the source is zero) flags rather than setting the ZF (if the source is zero). For a non-zero argument, the result of  and   is equal.

As with, the encoding of   is such that if BMI1 is not supported, then the   instruction is executed instead.

BMI2 (Bit Manipulation Instruction Set 2)
Intel introduced BMI2 together with BMI1 in its line of Haswell processors. Only AMD has produced processors supporting BMI1 without BMI2; BMI2 is supported by AMDs Excavator architecture and newer.

Parallel bit deposit and extract
The  and   instructions are new generalized bit-level compress and expand instructions. They take two inputs; one is a source, and the other is a selector. The selector is a bitmap selecting the bits that are to be packed or unpacked. copies selected bits from the source to contiguous low-order bits of the destination; higher-order destination bits are cleared. does the opposite for the selected bits: contiguous low-order bits are copied to selected bits of the destination; other destination bits are cleared. This can be used to extract any bitfield of the input, and even do a lot of bit-level shuffling that previously would have been expensive. While what these instructions do is similar to bit level gather-scatter SIMD instructions,  and   instructions (like the rest of the BMI instruction sets) operate on general-purpose registers.

The instructions are available in 32-bit and 64-bit versions. An example using arbitrary source and selector in 32-bit mode is:

AMD processors before Zen 3 that implement PDEP and PEXT do so in microcode, with a latency of 18 cycles rather than (Zen 3) 3 cycles. As a result it is often faster to use other instructions on these processors.

TBM (Trailing Bit Manipulation)
TBM consists of instructions complementary to the instruction set started by BMI1; their complementary nature means they do not necessarily need to be used directly but can be generated by an optimizing compiler when supported. AMD introduced TBM together with BMI1 in its Piledriver line of processors; later AMD Jaguar and Zen-based processors do not support TBM. No Intel processors (at least through Alder Lake) support TBM.

Supporting CPUs

 * Intel
 * Intel Nehalem processors and newer (like Sandy Bridge, Ivy Bridge) (POPCNT supported)
 * Intel Silvermont processors (POPCNT supported)
 * Intel Haswell processors and newer (like Skylake, Broadwell) (ABM, BMI1 and BMI2 supported)
 * AMD
 * K10-based processors (ABM supported)
 * "Cat" low-power processors
 * Bobcat-based processors (ABM supported)
 * Jaguar-based processors and newer (ABM and BMI1 supported)
 * Puma-based processors and newer (ABM and BMI1 supported)
 * "Heavy Equipment" processors
 * Bulldozer-based processors (ABM supported)
 * Piledriver-based processors (ABM, BMI1 and TBM supported)
 * Steamroller-based processors (ABM, BMI1 and TBM supported)
 * Excavator-based processors and newer (ABM, BMI1, BMI2 and TBM supported; microcoded PEXT and PDEP)
 * Zen-based, Zen+-based, and Zen 2-based processors (ABM, BMI1 and BMI2 supported; microcoded PEXT and PDEP)
 * Zen 3 processors and newer (ABM, BMI1 and BMI2 supported; full hardware implementation)

Note that instruction extension support means the processor is capable of executing the supported instructions for software compatibility purposes. The processor might not perform well doing so. For example, Excavator through Zen 2 processors implement PEXT and PDEP instructions using microcode resulting in the instructions executing significantly slower than the same behaviour recreated using other instructions. (A software method called "zp7" is, in fact, faster on these machines.) For optimum performance it is recommended that compiler developers choose to use individual instructions in the extensions based on architecture specific performance profiles rather than on extension availability.