[carry_bit]

Optimization fuel[1] is a neat solution: have the compiler perform only the first n optimization operations, then use binary search to find which operation was bad. You can then break execution at that point to see what is going wrong.

[1] http://blog.ezyang.com/2011/06/debugging-compilers-with-opti...