BSD Commit Log Search

   unbreak build with llvm-19+ by pulling the following upstream commits

   5a9c052ba78e5d1b0020b8f8320d211d2205a958 amd: Include missing llvm IR header Module.h
   fa9cd89a85b904615ebc11da609445b5b751e68d Update lp_bld_misc.cpp to support llvm-19+.
   a8eed9cca26b1c4b6526be7d042adec6703a30ae gallium: Don't pass avx512er and avx512pf features on LLVM 19

   ok jsg@

   Enable PAC in addition to BTI on arm64 such that JIT code matches the
   default branch protection provided by our base compiler.

   ok jsg@

   Merge Mesa 23.3.6

   Import Mesa 23.3.6

   Tell LLVM to generate code with BTI instructions.

   "looks ok" jsg@, ok deraadt@

   Merge Mesa 23.1.9

   Import Mesa 23.1.9

   Merge Mesa 22.3.4

   Import Mesa 22.3.4

   Merge Mesa 22.1.7

   Import Mesa 22.1.7

   Merge Mesa 21.3.7

   Import Mesa 21.3.7

   backport from Mesa upstream to fix i386 build with llvm 13

   gallivm: fix FTBFS on i386 with LLVM >= 13, StackAlignmentOverride is gone
   3a2d317b996f57647da23de7876142be4b9b71f3

   gallivm: add new wrapper around Module::setOverrideStackAlignment()
   c1b4c64a28d9fc093229eab91a3a7fc4cb4fe29a

   https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11940

   ok sthen@

   Merge Mesa 21.1.5

   Initial revision

   gallium/gallivm: remove unused header include for newer LLVM

   From Jan Zielinski
   52aa730d07618513d6c055618069b2f4680974cc in mainline Mesa

   Encountered by naddy@ when doing a clang 11 build.  This commit
   suggested by patrick@

   Merge Mesa 20.0.8

   With Mesa 20.1 even after the kernel change to do wbinvd on all cpus
   sthen@ reported that hard hangs still occurred on his Haswell system
   with inteldrm.

   Mark Kane also reported seeing hangs on Ivy Bridge on bugs@.

   Some systems/workloads seem to be more prone to triggering this than
   others as I have not seen any hangs on Ivy Bridge and the only hangs
   I saw on Haswell when running piglit went away with the wbinvd change.

   It seems something is wrong with drm memory attributes or coherency in
   the kernel and newer Mesa versions expect behaviour we don't have.

   Import Mesa 20.0.8

   Merge Mesa 20.1.6

   Import Mesa 20.1.6

   Merge Mesa 19.2.8

   Initial revision

   Merge Mesa 19.0.5

   Import Mesa 19.0.5

   Merge Mesa 18.3.2

   Import Mesa 18.3.2

   Merge Mesa 17.3.9

   Mesa 18.x needs an ld with build-id for at least the intel code
   Mesa 18.2 assumes linux only memfd syscalls in intel code

   Tested by matthieu@, kettenis@ and myself on a variety of hardware and
   architectures. ok kettenis@

   Import Mesa 17.3.9

   Revert to Mesa 13.0.6 again.

   Corruption has again been reported on Intel hardware running Xorg with
   the modesetting driver (which uses OpenGL based acceleration instead of
   SNA acceleration the intel driver defaults to).

   Reported in various forms on Sandy Bridge (X220), Ivy Bridge (X230) and
   Haswell (X240).  Confirmed to not occur with the intel driver but the
   xserver was changed to default to the modesetting driver on >= gen4
   hardware (except Ironlake).

   One means of triggering this is to open a large pdf with xpdf on an
   idle machine and highlight a section of the document.

   There have been reports of gpu hangs on gen4 intel hardware
   (T500 with GM45, X61 with 965GM) when starting Xorg as well.