For code reviews, there's the Code Review SE. But please read about their posting rules first. — Some programmer dude 40 secs ago

Consider maping a posting on codereview.stackexchange.com where you explain what you want to achieve and how your current solution works. I believe that could give a deeper insight into the matter. — Ulrich Eckhardt 17 secs ago

Code Review is for reviewing code. This is off topic on Stack Overflow. — Cow 41 secs ago

However, even in your results, the difference is less than 200 nanoseconds, which usually isn't a problem since your function is much more expensive in practice. i.e., you don't care about the difference between 10,000 nanoseconds and 10,200 nanoseconds. The only case where this might be a problem is if you are repeatedly calling a cheap function, although in that case it is probably more effective to improve the caller side. If this applies to you, I recommend posting a new question (maybe CodeReview is better in this case). — ken 51 secs ago

@Parminder Singh, you make enjoy Detecting unicorn and dinosaur compilers. — chux - Reinstate Monica 53 secs ago