Thanks for the stackoverflow link, that’s an interesting discussion.
I’m still in the camp though that it’s the programmer’s fault if a legitimate optimization breaks your code. Being able to choose between no optimization and full optimization should give you enough tools to find the mistake you made, there is no need on CodinGame for -O2, -O1 or even more fine-grained option control.