Announcement

Collapse
No announcement yet.

Wine-Staging 1.7.47 Adds Better GPU Detection, Multi-Threading VCOMP

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Wine-Staging 1.7.47 Adds Better GPU Detection, Multi-Threading VCOMP

    Phoronix: Wine-Staging 1.7.47 Adds Better GPU Detection, Multi-Threading VCOMP

    Building on top of Friday's release of Wine 1.7.47 is a new Wine-Staging release that tacks on a couple extra features...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    For those affected by https://bugs.winehq.org/show_bug.cgi?id=38653, GCC has been working on fixing the issues (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66782, https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66838)

    My Copr builds are currently broken due to GCC issues and I'm waiting for either one of Fedora's Wine maintainers to update the GCC 5 workaround or a new GCC snapshot in Fedora to fix the optimization issues, whichever happens first.

    Comment


    • #3
      Thanks for these links, I've had some wine issues for a few weeks and didn't look much into it.
      That was probably why, so now I know.
      Thanks!

      Comment


      • #4
        Well, the good news is that the recent error that was causing 64bit builds to fail appears to have been fixed in Wine. I suspect that it was only visible with -O0, which has to be enabled with GCC 5 since optimizations break 64bit.

        Hopefully GCC fixes all of the 64bit optimizations issues with Wine soon and Fedora updates to a newer GCC snapshot once it does so that the GCC 5 patch can be dropped, enabling optimizations again.

        Comment


        • #5
          so it sounds like this is a bug in gcc not in wine? if a wine "fix" simply disables optimizations.... so is this actually fixed in gcc yet?

          Comment


          • #6
            Originally posted by quaz0r View Post
            so it sounds like this is a bug in gcc not in wine? if a wine "fix" simply disables optimizations.... so is this actually fixed in gcc yet?
            Correct. The temporary workaround for distributions with GCC 5 is to disable optimizations until the bugs are fixed upstream. See post #2 for the bug reports.

            Comment

            Working...
            X