mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-01-13 22:50:26 +01:00
STACK_ARRAY() is used in a lot of places. When games are running we see STACK_ARRAY() arrays being used all the time: each queue submission uses 6, WaitSemaphores and syncobj waiting also uses them: they're constantly present in Vulkan runtime. There's no need for STACK_ARRAY()'s stack array to be initialized, callers cannot not depend on it. If the number of elements is greater than STACK_ARRAY_SIZE, then STACK_ARRAY() will just malloc() the array and return it not initialized: anybody depending of zero-initialization is going to break when the array is big. The reason why we're zero-intializing STACK_ARRAY()'s stack array is to silence -Wmaybe-uninitialized warnings: see commit |
||
|---|---|---|
| .. | ||
| gen_enum_to_str.py | ||
| meson.build | ||
| vk_alloc.c | ||
| vk_alloc.h | ||
| vk_cmd_queue_gen.py | ||
| vk_dispatch_table_gen.py | ||
| vk_dispatch_trampolines_gen.py | ||
| vk_entrypoints.py | ||
| vk_entrypoints_gen.py | ||
| vk_extensions.py | ||
| vk_extensions_gen.py | ||
| vk_format.c | ||
| vk_format.h | ||
| vk_icd_gen.py | ||
| vk_physical_device_features_gen.py | ||
| vk_physical_device_properties_gen.py | ||
| vk_struct_type_cast_gen.py | ||
| vk_synchronization_helpers_gen.py | ||
| vk_util.c | ||
| vk_util.h | ||