> I still have to add workarounds to prevent compiler over-optimizing the code Yet remembering how to measure time with nanosecond precision is the burden? >

> I still have to add workarounds to prevent compiler over-optimizing the code Yet remembering how to measure time with nanosecond precision is the burden? > By the way, the fastest way was branchless linear scan up to 32-64 elements, as far as I remember. The analysis presented in the article is far more interesting, qualified, and useful that what you've produced here.