[Bug 17421] Diablo2 fails to run when Wine is compiled with -march=amdfam10

wine-bugs at winehq.org wine-bugs at winehq.org
Wed Feb 18 10:00:57 CST 2009


http://bugs.winehq.org/show_bug.cgi?id=17421





--- Comment #5 from haarp <liquitsnake at gmx.net>  2009-02-18 10:00:57 ---
>git reset --hard 0a2efbb1ccb73da5943baa204aad670ed9b9c9a0
Diablo fails to work
>git revert 0a2efbb1ccb73da5943baa204aad670ed9b9c9a0
works.
This was with CFLAGS="-pipe -fno-ident -fomit-frame-pointer -march=k8-sse3 -O3
-fprefetch-loop-arrays -ftracer"
I know that the last 2 are experimental. Removing them gets rid of this bug for
1.1.7. My own fault then. Sorry for bothering you Rob...

BUT In 1.1.15, it's back! So along the way something else must've broken.
Interestingly, Changing the optimization level down to -O2 also allows Diablo
to work there.
Now here's the dilemma. I doubt that many people use this level, probably only
those with lots of CPU cache. And even then, most will use pre-compiled
packages. On the other hand, -O3 is a fairly common CFLAG that should, in
theory, pose no problems (aside from making an app slower/faster). Should Wine
be required to work properly on this level? I think it should. But others may
have other opinions on this. In the meantime, I'll try to find out what broke
it again between 1.1.7 and 1.1.15.


-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.



More information about the wine-bugs mailing list