Re:Debunking the Java Performance Myth
by DannyBee on Sunday October 22, 2017 @12:18PM
(#15527477)
Yes, because if the loop is not always-executing, it may be cheaper to not initialize the complex object, even if it is safe to so.
[ Parent
| on HN ]
I've also (recently) had poor performance on MSVC when "outside the loop" meant "a function argument", for a type that was essentially a struct wrapping a single primitive. It ended up being ABI weirdness that was confusing MSVC (and forceinline ended up fixing it).