No point in making parityti2 go through 2 calls to get to
paritysi2.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
I think this is correct, but does their performance matter? llvm/IR/RuntimeLibcalls.def does not define them (they cannot be produced by llvm). Targets either emit popcount & 1 or detect the idiom and emit an optimized parity (x86 after PR46954)
Comment Actions
Performance probably doesn't matter. Just one of the things a certain someone wasn't amused by.