Re: Compilation failure in wine-1.1.44

> 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
* faster compilation during bisection
* recommended for Valgrind
* my brain makes best optimalization, no need for buggy gcc :-D