[Bug 47835] New: `-funroll-loops` breaks wine, "wine: Unhandled page fault on write access to 0x00000000 at address ..."

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=47835

            Bug ID: 47835
           Summary: `-funroll-loops` breaks wine, "wine: Unhandled page
                    fault on write access to 0x00000000 at address ..."
           Product: Wine
           Version: unspecified
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: minor
          Priority: P2
         Component: -unknown
          Assignee: wine-bugs at winehq.org
          Reporter: zegentzy at protonmail.com
      Distribution: ---

As the name implies, compiling with `-funroll-loops` breaks wine. Every part of
it, from winedbg, to wine, to wineboot. Tested against both the latest wine on
git, wine 4.15, and wine 4.15. GCC 9.1.0. Arch Linux.

This is `winedbg`, for example:
```
wine: created the configuration directory '/home/gentz/.wine'
000b:fixme:thread:create_user_shared_data_thread Creating user shared data
update thread.
000b:fixme:winediag:start_process Wine Staging 4.16 is a testing version
containing experimental patches.
000b:fixme:winediag:start_process Please mention your exact version when filing
bug reports on winehq.org.
000d:fixme:thread:create_user_shared_data_thread Creating user shared data
update thread.
0010:fixme:thread:create_user_shared_data_thread Creating user shared data
update thread.
0012:fixme:thread:create_user_shared_data_thread Creating user shared data
update thread.
0014:fixme:thread:create_user_shared_data_thread Creating user shared data
update thread.
wine: Unhandled page fault on write access to 0x00000000 at address
00006BB2783C2DB9 (thread 0014), starting debugger...
0014:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 19 80" (2)
Read the Wine Developers Guide on how to set up winedbg or another debugger
wine: Unhandled page fault on write access to 0x00000000 at address
0000634EEE5AADB9 (thread 0012), starting debugger...
0012:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 17 88" (2)
Read the Wine Developers Guide on how to set up winedbg or another debugger
wine: Unhandled page fault on write access to 0x00000000 at address
000062C321ACADB9 (thread 0010), starting debugger...
0010:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 15 84" (2)
Read the Wine Developers Guide on how to set up winedbg or another debugger
^C0009:err:seh:raise_exception Unhandled exception code c000013a flags 0 addr
0xea872929
```

Here is `winecfg`: 
```
winecfg       
wine: created the configuration directory '/home/gentz/.wine'
000b:fixme:thread:create_user_shared_data_thread Creating user shared data
update thread.
000b:fixme:winediag:start_process Wine Staging 4.16 is a testing version
containing experimental patches.
000b:fixme:winediag:start_process Please mention your exact version when filing
bug reports on winehq.org.
000d:fixme:thread:create_user_shared_data_thread Creating user shared data
update thread.
0010:fixme:thread:create_user_shared_data_thread Creating user shared data
update thread.
0012:fixme:thread:create_user_shared_data_thread Creating user shared data
update thread.
0014:fixme:thread:create_user_shared_data_thread Creating user shared data
update thread.
wine: Unhandled page fault on write access to 0x00000000 at address
000060CC8A44ADB9 (thread 0012), starting debugger...
0012:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 17 80" (2)
Read the Wine Developers Guide on how to set up winedbg or another debugger
wine: Unhandled page fault on write access to 0x00000000 at address
00006628B5FD2DB9 (thread 0014), starting debugger...
0014:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 19 88" (2)
Read the Wine Developers Guide on how to set up winedbg or another debugger
^C0009:err:seh:raise_exception Unhandled exception code c000013a flags 0 addr
0xe16b1929
```

I'm marking this as minor, as the workaround is trivial: just don't build with
`funroll-loops`, but hopefully someone looks into it. I did some searching, and
couldn't find this already reported, but feel free to close if it's a dupe,
sorry!

-- 
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.