On Sat, 4 Sep 2004 01:32:16 +0200, you wrote:
> > You need to know what the bug is in order to write a proper configure
> > check, so the first thing to do is to figure out why that flag causes
> > trouble.
> >
>
> Know and know, I know at least it was this patch
> http://www.winehq.org/hyperma
On Friday 03 September 2004 17:40, Alexandre Julliard wrote:
> Mike Hearn <[EMAIL PROTECTED]> writes:
>
> > If your disassembly-fu is up to it, be my guest ... that doesn't solve
> > the problem of mysterious crashes for people using/compiling Wine
> > today though. So I'd still vote for a configu
Mike Hearn <[EMAIL PROTECTED]> writes:
> If your disassembly-fu is up to it, be my guest ... that doesn't solve
> the problem of mysterious crashes for people using/compiling Wine
> today though. So I'd still vote for a configure check.
You need to know what the bug is in order to write a proper
Lionel Ulmer wrote:
> Open Source is helping each other and if we just say 'oh well, it's easier
> for us to just remove the optimisation flag' and forget the issue, it's an
> opportunity lost to improve GCC.
We can report this to gcc developers, but, at least on my side, I don't know
enough how GC
> Heh, I always find it hard :)
Well, my example was on code generated for ARM which is unreadable when the
complier saves the frame pointer :-)
> If your disassembly-fu is up to it, be my guest ... that doesn't solve
> the problem of mysterious crashes for people using/compiling Wine today
> t
Well, I always found the resulting assembly of code compiled with
'-fomit-frame-pointer' much easier to read than without :-)
Heh, I always find it hard :)
Why not first try to search for the bug and report it to the GCC people ?
If your disassembly-fu is up to it, be my guest ... that doesn't solv
Lionel Ulmer wrote:
> Why not first try to search for the bug and report it to the GCC people ?
IMHO Wine has so much things to take care of that are more important than a
GCC bug that the better way to handle this for now is to filter off that
flag.
There're also other softwares which filter some
Mike Hearn wrote:
> Using this switch is almost always a bad idea, as it makes getting
> backtraces impossible. OK, without debug symbols, they are of only
> limited usefulness but I've still been able to track down problems
> before using a stripped backtrace.
I build quite everything in Gentoo wi
> -fomit-frame-pointer is one of those "optimizations" that does more harm
> than good in my opinion.
Well, I always found the resulting assembly of code compiled with
'-fomit-frame-pointer' much easier to read than without :-)
> If you are right and this is causing misbuilds, perhaps we should
Seems like I found out which flags causes trouble with the scrollbars and
the mouse's scrollwheel: building wine without -fomit-frame-pointer flag
makes it work right.
Using this switch is almost always a bad idea, as it makes getting
backtraces impossible. OK, without debug symbols, they are of o
Hi,
Seems like I found out which flags causes trouble with the scrollbars and
the mouse's scrollwheel: building wine without -fomit-frame-pointer flag
makes it work right.
This fixes my problem
( http://article.gmane.org/gmane.comp.emulators.wine.devel/23780 ) and
seems to fix (at least for me) th
11 matches
Mail list logo
