Re:“It is never a compiler error”
by ethbro on Tuesday November 14, 2017 @11:39PM
(#15701495)
From what I remember of a deep dive post I read on this once, the ordering type bug / no-bug situations tend to be the result of incorrect optimizations. Changing the ordering will sometimes make the code look just different enough to go down a different (not bugged) optimization path.
If you ever catch them still there with a "no optimizations" flag, then that's a pretty serious bug!
If you ever catch them still there with a "no optimizations" flag, then that's a pretty serious bug!