The static should just be optimized out since its address doesn't leak and the value is never used before storing to it.
-
-
I assume it happens to work in practice, but if so it's a bug (shortcoming) in the optimizer, not a real constraint.
-
of course it's not a real constraint

-
the actual implementation doesn't do it that way, just the comment
-
I think olde x87 GCC would care about that named var though. AKA when you know your semantics jumped the shark.
-
Modern gcc in standards-conforming mode (as opposed to -ffast-math or something) will always do it in the right order
-
But excess-precision issues and double rounding due to them still could mess you up.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.