> I have come across a scenario where the gcc -O2/-O3 "over-optiimized" the > code and that resulted in a buggy behavior.
That is strange. For O3 the issue is known for a few C and C++ packages, as it it known that some packages do not work with -flto. But O2 should work always, and when there are problems with O3, Nim devs can fix it. But maybe O2 should be the default, O3 can make executables really large, without much speed gain.
