[Bug 48693] New: -O2 optimization breaks 32 bit wine 3D on 64 bit system

* [Bug 48693] New: -O2 optimization breaks 32 bit wine 3D on 64 bit system
@ 2012-04-14 17:28 bugzilla-daemon
  2012-04-14 18:38 ` [Bug 48693] " bugzilla-daemon
                   ` (5 more replies)
  0 siblings, 6 replies; 7+ messages in thread
From: bugzilla-daemon @ 2012-04-14 17:28 UTC (permalink / raw)
  To: dri-devel

https://bugs.freedesktop.org/show_bug.cgi?id=48693

             Bug #: 48693
           Summary: -O2 optimization breaks 32 bit wine 3D on 64 bit
                    system
    Classification: Unclassified
           Product: Mesa
           Version: unspecified
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/R600
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: haagch.christoph@googlemail.com

Created attachment 59983
  --> https://bugs.freedesktop.org/attachment.cgi?id=59983
furmark crash in wine, mesa compiled with CFLAGS="-O2"

So I had this bug across some gcc versions and mesa versions (since about the
time llvm 3.0 came out) and I figured I should probably report it since it
didn't go away until now.

I'm on a notebook with Redwood, HD 6550M with current libdrm git, mesa git,
xf86-video-ati git, gcc (GCC) 4.7.0 20120407.

The problem is this:
If I compile mesa with CFLAGS="-O2" I immedately get a crash in all (32 bit) 3D
applications/games I have tested in wine (before even displaying the main
window). An example is furmark, see attachment.

It tries to access an apparently invalid address at 0x7cae670a and at this
position there is r600_dri.so.

If I compile mesa with CFLAGS="-O1" (or "-Os") this does not happen. In fact,
if I install mesa compiled with "-O2" and only replace
/usr/lib32/xorg/modules/dri/r600_dri.so with one from a mesa build compiled
with "-O1" it also works.

Another curiosity is that when I do this:
 ~/.wine/drive_c/FurMark % WINEDEBUG=+all wine FurMark.exe &> /dev/null
then I get the same crash, as expected.
But when I do this:
 ~/.wine/drive_c/FurMark % WINEDEBUG=+all wine FurMark.exe &> furmarkdebug.txt
it starts fine to the main window. Only later, when clicking on benchmark, I
get a very similar crash to the above.

Native 32 bit games work fine with an "-O2" compiled mesa. Internal wine
programs like regedit, explorer or wine internet explorer work also.

If you can tell me how I can obtain more information about this obscure bug I
will gladly do.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 7+ messages in thread