Age | Commit message (Collapse) | Author |
|
|
|
|
|
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@
|
|
noticed when going over a macppc clang build error reported by deraadt@
|
|
builds were running out of memory
requested by deraadt@
|
|
|
|
tested by matthieu@ naddy@ and myself
|
|
- handle the NULL timeout pointer case
- avoid negative cases.
Suggested by cheloha@ ok cheloha@, jsg@
|
|
|
|
Grrr, sorry about that.
|
|
When not in c++ or c11 mode:
- check for _Static_assert support in clang with __has_extension
- gcc implements _Static_assert starting with 4.6.0
- as a fallback, use a forward decl instead of ((void)0) so that
static_assert can be used at file scope (scope issue pointed out by
guenther@)
ok jsg@
|
|
Temporary workaround while we find a better solution.
Linking errors in ports reported by cwen@, "Please commit" jsg@
|
|
|
|
distfiles when upstream removed autotools
|
|
|
|
|
|
|
|
|
|
autoconf function tests run without --std and have c11 visibility
timespec_get(3), a c11 function is found this way.
With gcc < 4.6 Mesa will build with --std=gnu99 with clang it will
build with --std=c99 and timespec_get() will no longer be visibile.
Further complicating things gcc 4.2 does not recognise --std=c11.
This was not noticed on linux as they build with _GNU_SOURCE which
among other things gives c11 visibility even with --std=c99.
discussed with millert@
|
|
issetugid(), not just the sloppy uid != euid test. gid != egid cases
can occur also.
Part of 6.6/009_mesaxlock.patch.sig and 6.5/020_mesaxlock.patch.sig
From Qualys, ok
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
From Brian Paul
02c3dad0f3b4d26e0faa5cc51d06bc50d693dcdc in mainline Mesa
"A security advisory (TALOS-2019-0857/CVE-2019-5068) found that
creating shared memory regions with permission mode 0777 could allow
any user to access that memory. Several Mesa drivers use shared-
memory XImages to implement back buffers for improved performance.
This path changes the shmget() calls to use 0600 (user r/w).
Tested with legacy Xlib driver and llvmpipe."
|
|
ok kettenis@ patrick@
|
|
From Anuj Phogat
82f6a746e8b47fb6e3f96d7f5f69973f50eec9ca in mesa master
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|