On Sat, 8 May 2010, wy...@volny.cz wrote:
[...]
> > * Not testing the code under Release conditions.
>
> I guess, that running Word2007 under linux/wine also does not meet release
> conditions by Microsoft ;-) Anyway, i hope that if i run Win program
> calculating PI on 4 decimal place, both -O0 a
Ben Klein:
> Any cases where -O0 and -O2 give different results for backtraces are
> > bugs in the gcc optimisation code, not in Wine.
And this was excatly one of the reasons, why use -O0. I do not want to
report gcc bugs in wine's bugzilla.
> Speed of code execution is an issue primarily with la
On 9 May 2010 06:21, wrote:
> Hi Marcus,
>
>> > * better backtraces for bug reports
>>
>> -O2 works like a charm there too, at least for me.
>
> I think i read that somewhere and if i understood that correctly, my
> conclusion at that time was, that -02 optimizes the code, so it can
> "omit some"
Le 08/05/2010 22:37, Nikolay Sivov a écrit :
On 5/9/2010 00:21, wy...@volny.cz wrote:
Hi Marcus,
* better backtraces for bug reports
-O2 works like a charm there too, at least for me.
I think i read that somewhere and if i understood that correctly, my
conclusion at that time was, that -02
On 5/9/2010 00:21, wy...@volny.cz wrote:
Hi Marcus,
* better backtraces for bug reports
-O2 works like a charm there too, at least for me.
I think i read that somewhere and if i understood that correctly, my
conclusion at that time was, that -02 optimizes the code, so it can
Hi Marcus,
> > * better backtraces for bug reports
>
> -O2 works like a charm there too, at least for me.
I think i read that somewhere and if i understood that correctly, my
conclusion at that time was, that -02 optimizes the code, so it can
"omit some" part of code and replace them by faster al
On Sat, May 08, 2010 at 03:02:48PM +0200, wy...@volny.cz 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
> 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
Yeah the -O0 bug was reported on #winehackers yesterday and will
likely be fixed soon. Compiling using -O2 (which is what you should
use by default anyway unless you have very good reasons not to) should
work fine.
Roderick
On Sat, May 8, 2010 at 2:33 PM, wrote:
>
> Hi guys, i can't compile win
Hi guys, i can't compile wine-1.1.44 (1.1.43 is OK here like all the
ones before)... As i guess you would not release a wine, which can't
be compiled, than i suspect there could be a trouble in my system (Debian
Lenny 32bit). For this reason, i did not bother to fill a bug ;) as
it would be marked
10 matches
Mail list logo
