Age | Commit message (Collapse) | Author |
|
From Jan Beich
46c368907fcf333a19881d28c46e997845d00faf in mainline Mesa
We had a related local patch in 19.2 which wasn't needed when 20.1 was
imported as the above commit was backported to the upstream 20.1 branch.
When Mesa 20.0 was imported after issues with 20.1 on Haswell the
changes to use futexes for simple_mtx.h and u_queue.h were lost.
Noticed by otto@ and kettenis@ when looking for memory leaks.
|
|
From Vinson Lee
ff8daa013621019f1606dc0c188b16f1ce34fea7 in mainline Mesa
fixes clang 11 build
mortimer@ had almost the same diff
|
|
|
|
From Kristian Hoegsberg
e3dfa8f4d694e7d64a6401752af1f973b0852aab in mainline Mesa
reduces clang warnings
|
|
From Kristian Hoegsberg
b40281d8306367e68dde6b723d2114d9cb5fca5a in mainline Mesa
|
|
|
|
|
|
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.
|
|
|
|
haswell hangs still occurred just less frequently with the 1.10 revert of
'intel/eu: Use non-coherent mode (BTI=253) for stateless A64 messages'
The recent kernel change to do wbinvd across all cpus instead of just one
is a better approach and avoids hangs seen with piglit on haswell.
|
|
|
|
intel/eu: Use non-coherent mode (BTI=253) for stateless A64 messages
d23bbc8c28b6a5cd7f4d3d03c74d8319da5d47d5 on 20.1 branch
4985e380dd776ac65c4ae5627138211f9d9f03ce on mainline
thanks to gnezdo@ sthen@ and espie@ for reports and testing
|
|
|
|
|
|
|
|
|
|
problem spotted by Jason Ekstrand reviewing proposed patches upstream
|
|
avoids error: no previous prototype for function '__sync_sub_and_fetch_8_c'
|
|
|
|
Mesa is no longer built on hppa or sh
|
|
|
|
From Oschowa
c310677a7563b1e2d97f8216be1d60cb21204eae in mainline mesa
reduces clang warnings
|
|
From Oschowa
663e8cb4e67f8b85186631c6a3719ed83da32151 in mainline mesa
reduces clang warnings
|
|
From Oschowa
7b1bc460fd6ae9bf5efeca62227bb05e0c50ee15 in mainline mesa
reduces clang warnings
|
|
From Oschowa
536339b0dda33241d21a0e045681419ca46fc812 in mainline mesa
reduces clang warnings
|
|
From Oschowa
c2a778ef0f1720f9fb28afd40a791488648218d0 in mainline mesa
reduces clang warnings
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
On mips64, the compiler does not allow use of non-zero argument with
__builtin_frame_address(). However, the returned frame address is only
used when PIPE_ARCH_X86 is defined. The compile error can be avoided
by making #ifdef PIPE_ARCH_X86 cover the getting of frame address too.
The argument checking of __builtin_frame_address() has been present
as a debug assert in clang 8. In clang 10, there is a proper runtime
check for the argument. This is why the build has not failed before.
OK jsg@
|
|
From Eric Engestrom
7f5ef97a07d4054efb96f0d644344644023af82c in Mesa git
fixes llvmpipe renderer string showing "LLVM 16.0" with LLVM 10
|
|
from Samuel Pitoiset
ee9811a0bb86d3d75fafeece368f6182048807d0 in mainline Mesa
|
|
conver __sync_val_compare_and_swap.
ok jsg@
|
|
instructions. Clang doesn't allow redeclaration (and therefore
redefinition) of the __sync_* builtins. Use #pragma redefine_extname
to work around that restriction. Clang also turns __sync_add_and_fetch
into __sync_fetch_and_add (and __sync_sub_and_fetch into
__sync_fetch_and_sub) in certain cases, so provide these functions as
well.
ok jsg@
|
|
tested by matthieu@ naddy@ and myself
|
|
- handle the NULL timeout pointer case
- avoid negative cases.
Suggested by cheloha@ ok cheloha@, jsg@
|
|
|
|
|
|
distfiles when upstream removed autotools
|
|
|