[llvm] [ISel] Introduce `llvm.pext` and `llvm.pdep` intrinsics (PR #200570)
Jan Schultke via llvm-commits
llvm-commits at lists.llvm.org
Sun May 31 21:49:24 PDT 2026
eisenwave wrote:
> Is the bit compress/expand name catching on the desirable outcome? Do you think it will make more ISAs adopt these instructions in the future? Will those ISAs use pext/pdep or compress/expand?
Idk, they seem to pick the name by roulette wheel for this instruction.
> If the latter, does naming it llvm.pext/pdep now end up making the name look X86 specific in the future. Will other frontends adopt the bit_compress/expand naming for the their builtins/intrinsics and be confused by the IR intrinsic having a different name? Renaming an intrinsic in the future isn't free so I want to make sure we aren't painting ourselves into a corner.
The PEXT/PDEP or BEXT/BDEP terms are widepsread enough to the point where they'll likely be around for a long time.
In Rust, I don't think anyone uses the "bit compress" terminology; the crates all seem to refer to `pext`, like https://github.com/gnzlbg/bitintr/blob/master/src/pext.rs
And sure, we would be painting ourselves into a corner with an x86-specific name if that became less popular over time, but the same applies to pretty much all of our bit manipulation intrinsics, and I care about consistency here. PEXT is the most widely known name right now, and that's unlikely to change in the next 10-20 years.
https://github.com/llvm/llvm-project/pull/200570
More information about the llvm-commits
mailing list