1. 15 Apr, 2021 1 commit
  2. 14 Apr, 2021 1 commit
    • Michel Dänzer's avatar
      ci: Move docker images from Debian buster to bullseye · af0fde95
      Michel Dänzer authored
      Among other things, this gets us GCC 10 (was 6).
      Requires some changes to third party components we use:
      * Install apitrace (& waffle) from Debian; was hitting issues with the
        local build, and it's the same version 9.0 anyway.
      * Update Fossilize to a newer commit which builds with GCC 10.
      * apt.llvm.org repositories are no longer needed.
      * Use an SPIRV-LLVM-Translator commit which builds with LLVM 11.0.1.
      * Install XCB packages from Debian, 1.13 fails to build with Python 3.9.
      * Install wayland-protocols from Debian, 1.12 is too old for
        libgtk-3-dev in bullseye.
      LLVM 7/8 packages are no longer available.
      Also adapt expected test results to Xvfb now exposing multi-samle
      * Install clang instead of clang-11.
      Closes: mesa/mesa#3124
      Reviewed-by: Eric Anholt <eric@anholt.net> # v1
      Part-of: <mesa/mesa!9833>
  3. 13 Apr, 2021 1 commit
    • Adam Jackson's avatar
      glx: Lift sending the MakeCurrent request to top-level code · 80b67a3b
      Adam Jackson authored
      Somewhat terrifyingly, we never sent this for direct contexts, which
      means the server never knew the context/drawable bindings. To handle
      this sanely, pull the request code up out of the indirect backend, and
      rewrite the context switch path to call it as appropriate.  This
      attempts to preserve the existing behavior of not calling unbind() on
      the context if its refcount would not drop to zero.
      Of course, you can't just do this indiscriminately, because this is GLX
      and extant X servers have bugs and everything is terrible. To wit:
      - For 1.20.x prior to 1.20.6, you can bind a direct context once, but
      the second time you try to modify the context's binding you will get
      GLXBadContextTag. This includes unbinding the context. And "deleting"
      the context will leak memory, because it will still appear to be
      - For 1.19 and earlier, glXMakeCurrent(dpy, None, ctx) should be legal
      for GL 3.0+ contexts, but the server will throw BadMatch.
      To guard against this, we only send the request for indirect contexts
      unless the server is known good, and only mention one context at a time
      in such a request; if switching between contexts, we first unbind the
      old, and then bind the new. Note that the second VendorRelease() version
      is to catch XFree86 4.x and Xorg [67].x, which almost certainly have the
      above bugs. Other servers might report different version numbers here,
      but we can't do direct rendering against them, so this should be safe.
      Fixes: mesa/mesa#4418
      Acked-By: Mike Blumenkrantz's avatarMike Blumenkrantz <michael.blumenkrantz@gmail.com>
      Part-of: <mesa/mesa!9992>
  4. 02 Apr, 2021 1 commit
  5. 29 Mar, 2021 1 commit
  6. 28 Feb, 2021 1 commit
  7. 24 Feb, 2021 2 commits
  8. 23 Feb, 2021 1 commit
  9. 22 Feb, 2021 1 commit
  10. 17 Feb, 2021 1 commit
  11. 11 Feb, 2021 1 commit
  12. 09 Feb, 2021 1 commit
  13. 19 Jan, 2021 1 commit
  14. 22 Dec, 2020 2 commits
  15. 07 Oct, 2020 1 commit
  16. 01 Oct, 2020 1 commit
    • Matt Turner's avatar
      Revert F16C series (MR 6774) · 1aac47db
      Matt Turner authored
      This reverts commit 4fb2eddf.
      This reverts commit 7a1deb16.
      This reverts commit 2b6a1723.
      This reverts commit 5af81393.
      This reverts commit 87900afe.
      A couple of problems were discovered after this series was merged that
      cause breakage in different configurations:
         (1) It seems that using -mf16c also enables AVX, leading to SIGILL on
         platforms that do not support AVX.
         (2) Since clang only warns about unknown flags, and as I understand
         it Meson's handling in cc.has_argument() is broken, the F16C code is
         wrongly enabled when clang is used, even for example on ARM, leading
         to a compilation error.
      Closes: mesa/mesa#3583
      Reviewed-by: Emma Anholt's avatarEric Anholt <eric@anholt.net>
      Reviewed-by: Rob Clark's avatarRob Clark <robdclark@chromium.org>
      Part-of: <mesa/mesa!6969>
  17. 30 Sep, 2020 1 commit
  18. 08 Sep, 2020 1 commit
  19. 17 Aug, 2020 1 commit
  20. 23 Jul, 2020 2 commits
  21. 20 Jul, 2020 1 commit
  22. 16 Jul, 2020 1 commit
  23. 15 Jul, 2020 1 commit
  24. 07 Jul, 2020 2 commits
  25. 06 Jul, 2020 2 commits
  26. 03 Jul, 2020 1 commit
    • Dave Airlie's avatar
      draw/clip: fix viewport index for geometry shaders · 29ce8060
      Dave Airlie authored
      The old code updated the viewport index on the first vertex in
      a primitive, however it was picking the first vertex wrong
      when used with geometry shaders.
      This code has access to the prim info with the primitive lengths
      so instead keep track of when a new primitive starts by tracking
      the lengths and updating the viewport index then. The prim info
      is only valid after a GS or prim assembly, so enable prim assembly
      if a vertex shader ever uses viewport index.
      This fixes:
      piglit arb_viewport_array-render-viewport-2
      Reviewed-by: default avatarRoland Scheidegger <sroland@vmware.com>
      Part-of: <mesa/mesa!5489>
  27. 02 Jul, 2020 2 commits
  28. 11 Jun, 2020 1 commit
  29. 10 Jun, 2020 1 commit
  30. 03 Jun, 2020 1 commit
  31. 02 Jun, 2020 1 commit
  32. 28 May, 2020 1 commit
  33. 19 May, 2020 1 commit
  34. 06 May, 2020 1 commit