Simon Ser 7265a79e46 Drop "restrict" keyword ... The "restrict" keyword can be used to indicate that no other pointer will be used to access a chunk of memory while the restricted pointer is alive. If that promise is not upheld, undefined behavior is triggered. It may be difficult to ensure this property, and the property may be brittle - becoming invalid as code evolves. Just like "inline", let's just leave optimizations up to the compiler to figure out.		2026-05-25 08:42:35 +00:00
..
atomic.c	output/drm: don't use OUT_FENCE_PTR	2026-03-17 18:14:35 +00:00
backend.c	treewide: make type-check helpers take const pointers	2026-03-06 16:04:21 +08:00
drm.c	output/drm: don't use OUT_FENCE_PTR	2026-03-17 18:14:35 +00:00
fb.c	drm: Make it clear that we tried to import a shm buffer	2026-05-06 19:56:19 -04:00
gen_pnpids.sh	backend/drm: use libdisplay-info to parse EDID	2023-02-28 14:44:02 +00:00
legacy.c	backend/drm: add support for color transforms	2025-06-16 09:06:10 +00:00
libliftoff.c	output/drm: don't use OUT_FENCE_PTR	2026-03-17 18:14:35 +00:00
meson.build	backend/drm: add support for color primaries	2025-06-18 00:07:58 +02:00
monitor.c	backend/drm: drop wl_display argument	2024-01-25 15:05:36 +00:00
properties.c	backend/drm: Add color_range/encoding properties	2026-03-17 16:32:30 +00:00
renderer.c	backend/drm: log when creating multi-GPU renderer	2025-01-30 02:10:58 +00:00
util.c	Drop "restrict" keyword	2026-05-25 08:42:35 +00:00