4 ms·
Consider that the compiler cannot optimize A != A into false, or A == A into true, because NaN values can occur at run time. While you might not explicitly wri
by kazinator 5y ago
Consider that the compiler cannot optimize A != A into false, or A == A into true, because NaN values can occur at run time.
While you might not explicitly write A == A into your code, it could occur implicitly due to some macro expansion, inline expansion or other code transformation.
I think GCC with -ffast-math gets rid of this NaN rule and does such optimizations anyway. (Your code just has to avoid generating NaNs so that the optimizations are valid.)