On Sat, May 08, 2010 at 03:02:48PM +0200, [email protected] wrote: > > > Roderick: > > Yeah the -O0 bug was reported on #winehackers yesterday > > and will likely be fixed soon. > > Ah, ok :) I know you already test nearly everythink, but what about adding > another test -O{0,1,2,s,...} > a] before official release or > b] evening wine git update > > > Compiling using -O2 (which is what you should use by default anyway > > > unless you have very good reasons not to) should work fine. > > I quickly thing of these reasons why -O0 > * better backtraces for bug reports
-O2 works like a charm there too, at least for me. > * faster compilation during bisection > * recommended for Valgrind -O2 works like a charm there too. > * my brain makes best optimalization, no need for buggy gcc :-D Also: * Not testing the code under Release conditions. * Slow code. Ciao, Marcus
