Have You Tried Using a Nearest Neighbor Search?

Re:Have You Tried Using a Nearest Neighbor Search? by nkurz on Wednesday April 13, 2016 @01:28PM (#11490264)

There is a bug that significantly reduces performance if certain register combinations are used, but the current generation of compilers have been patched to avoid triggering it. So it's something you should be on the lookout for, but if you are compiling your own code (or working directly in assembly) it's not a reason to avoid POPCNT.

If you are distributing high-performance code that might be compiled with unpatched compilers, you probably should take steps to mitigate. In this case using a snippet of inline assembly where you have control of the registers is probably the best solution, since even if you avoid explicitly using __builtin_popcount() the compiler might "optimize" your algorithm to use it anyway.

[ Parent | on HN ]

Re:Have You Tried Using a Nearest Neighbor Search? by dalke on Wednesday April 13, 2016 @02:20PM (#11490810)

My own code is in assembly. Plus, when that came out I tested the different alternatives, and found that my hardware didn't have the problem. Perhaps it was too old.

I also did extensive comparisons between the POPCNT version and the nibble-based version using PSHUFB, and showed that the POPCNT version was always faster.

[ Parent | on HN ]