Add support for mutable descriptor types

.gitignore

@@ -9,3 +9,5 @@ docs/traces/
 .vs/
 .cache
 .vimspector.json
+subprojects/.wraplock
+subprojects/pml.wrap

docs/env.md

@@ -46,6 +46,8 @@ Environment variables
   and counting the number of warnings errors. On windows, will allocate
   a console window to output to.
   Note that internal logs/asserts are disabled in release builds.
+- `VIL_LOG_FILE` can be set to a file path where vil will output its
+  log messages. By default, will simply output to stdout.
 
 - `VIL_WINDOW_MIN_FRAME_TIME=<time in ms>` when a window was created
   via `VIL_CREATE_WINDOW`, will throttle its framerate (if needed) to make
@@ -56,3 +58,10 @@ Environment variables
 - `VIL_WAIT_SURFACE={0, 1}`, default 0. Wait until the application has created
   a surface object until the window is initialized. Fixes window initialization
   for DXVK. If you have a compute-only application, this needs to be 0.
+
+- `VIL_ALLOW_UNSUPPORTED_EXTS={0, 1}`, default 0. When a vulkan instance/device
+  is created with an unsupported extension, vil will output and return an error
+  if this is not set to 1. If this is set to 1, vil still outputs an error
+  but does not fail device/instance creation.
+  Please note that running vil with unsupported extensions will likely
+  cause crashes and issues.

docs/features.md

@@ -7,194 +7,7 @@ environment variable, it will significantly increase the chance that
 new extensions "just work", with a slight performance hit.
 See [env.md](env.md) for more details.
 
-## Vulkan 1.0
-
-Fully implemented.
-
-## Vulkan 1.1
-
-Implemented:
-- VK_KHR_descriptor_update_template
-  resources tab description is still TODO
-- VK_KHR_bind_memory2
-- vkCmdDispatchBase
-- VK_KHR_maintenance1 (e.g. vkTrimCommandPool)
-- VK_KHR_dedicated_allocation (not indicated in ui yet though)
-- VK_KHR_maintenance3 (nothing to do)
-
-Missing:
-- Anything with device masks is missing; using it will very likely crash.
-- no support for render pass multiview, VK_KHR_multiview
-- external memory, fences, semaphores
-- VK_KHR_maintenance2
-	- using the renderpass/imageView extensions might crash
-- ui: for YCbCr conversion handles not tracked/shown
-- ui: no support for variable pointers buffer
-
-## Vulkan 1.2
-
-Implemented:
-- VK_KHR_draw_indirect_count
-- VK_KHR_create_renderpass2
-- VK_KHR_buffer_device_address (introspection support WIP)
-	- known problem: synchronization problems when using the gui on
-	  commands/buffers using this feature. WIP
-- VK_KHR_imageless_framebuffer
-- VK_EXT_descriptor_indexing
-	- some edge cases with update_unused_while_pending are not properly
-	  tested yet, might need some changes.
-- VK_KHR_timeline_semaphore
-	- has some tricky edge cases (especially when application is really making
-	  use of out-of-order submission chaining), not yet tested a lot.
-
-missing:
-- extensions extending render passes (e.g. VK_KHR_depth_stencil_resolve)
-  using those might lead to crash.
-
-## Vulkan 1.3
-
-Implemented:
-- VK_KHR_copy_commands2
-- VK_EXT_extended_dynamic_state
-- VK_EXT_extended_dynamic_state2 (with extension-exclusive additions as well)
-- VK_KHR_dynamic_rendering (including hook/ui support)
-- VK_KHR_synchronization2
-
-Incomplete/missing:
-- VK_KHR_format_feature_flags2 (enum names)
-- VK_EXT_private_data
-- VK_EXT_subgroup_size_control (NOTE: might need changes to the way we
-  patch shaders, need to correctly forward pNext).
-- VK_EXT_texture_compression_astc_hdr (only enum names)
-- VK_EXT_4444_formats (only enum names)
-- VK_EXT_tooling_info (not sure if we should interact with it)
-
-no-op/shader exts that should be supported out of the box (as long
-as spirv-tools supports them):
-- VK_KHR_maintenance4 (no changes needed afaik)
-- VK_KHR_shader_subgroup_extended_types
-- VK_KHR_shader_non_semantic_info
-- VK_KHR_shader_terminate_invocation
-- VK_EXT_shader_demote_to_helper_invocation
-- VK_KHR_zero_initialize_workgroup_memory
-- VK_EXT_pipeline_creation_feedback
-- VK_EXT_image_robustness
-- VK_EXT_inline_uniform_block
-- VK_EXT_pipeline_creation_cache_control
-- VK_EXT_texel_buffer_alignment
-
-## Vulkan 1.4
-
-Implemented:
-- VK_KHR_map_memory2
-- VK_KHR_line_rasterization
-- VK_KHR_vertex_attribute_divisor
-
-Incomplete:
-- VK_KHR_maintenance5
-  allow to pass shader modules create info directly in pipeCreateInfo.pNext
-  missing UI support for new flags
-- VK_KHR_push_descriptor
-  No UI support, those descriptor won't show up, cannot be inspected
-- VK_EXT_vertex_attribute_divisor
-  need support in pipeline patch creation
-  probably an issue for many extensions that modify pipe creation
-- VK_KHR_maintenance6
-- VK_EXT_host_image_copy
-
-assumed no-op:
-- VK_KHR_shader_expect_assume
-- VK_KHR_shader_float_controls2
-- VK_KHR_shader_subgroup_rotate
-- VK_KHR_load_store_op_none
-
-## Non-core extensions
-
-Extensions promoted to core not explicitly mentioned here, see above.
-Supported extensions:
-
-- VK_KHR_surface, VK_KHR_swapchain
-- VK_EXT_debug_utils
-- VK_KHR_surface (tested overlay platforms: xlib, xcb, win32)
-	- other platforms should work without crash at least
-
-supported but no/incomplete gui interaction/information:
-- VK_KHR_acceleration_structure
-- VK_KHR_ray_tracing_pipeline
-- VK_EXT_extended_dynamic_state
-- VK_EXT_line_rasterization
-- VK_KHR_draw_indirect_count
-- VK_EXT_sample_locations
-- VK_EXT_discard_rectangles
-- VK_EXT_vertex_input_dynamic_state
-- VK_EXT_color_write_enable
-- VK_EXT_multi_draw
-
-Extensions that just add new features or flags shouldn't need any
-support by the layer but may have incomplete introspection. New functions
-on physical device are usually also not a problem.
-For instance:
-- VK_EXT_conservative_rasterization
-- VK_EXT_custom_border_color
-- VK_EXT_depth_clip_enable
-- VK_EXT_depth_range_unrestricted
-- VK_EXT_device_memory_report
-- VK_NV_cooperative_matrix
-
-Extensions that just add SPIR-V features shouldn't be a problem in general
-as long as SPIRV-Tools supports it.
-For instance:
-- VK_KHR_ray_query
-- VK_KHR_workgroup_memory_explicit_layout
-- VK_KHR_zero_initialize_workgroup_memory
-- VK_KHR_shader_clock
-- VK_KHR_vulkan_memory_model
-- VK_EXT_fragment_shader_interlock
-- VK_EXT_post_depth_coverage
-- VK_EXT_shader_atomic_float
-- VK_EXT_shader_demote_to_helper_invocation
-- VK_AMD_shader_fragment_mask
-- VK_AMD_texture_gather_bias_lod
-- VK_INTEL_shader_integer_functions2
-- VK_NV_compute_shader_derivatives
-- VK_NV_fragment_shader_barycentric
-- VK_NV_geometry_shader_passthrough
-- VK_NV_sample_mask_override_coverage
-- VK_NV_shader_image_footprint
-- VK_NV_shader_sm_builtins
-- VK_NV_viewport_array2
-- VK_KHR_16bit_storage
-- VK_KHR_8bit_storage
-- VK_KHR_shader_atomic_int64
-- VK_KHR_shader_float16_int8
-- VK_KHR_shader_subgroup_extended_types
-- VK_KHR_spirv_1_4
-- VK_KHR_storage_buffer_storage_class
-- VK_KHR_variable_pointers
-- VK_EXT_scalar_block_layout
-- VK_EXT_shader_subgroup_ballot
-
-The shader debugger does not work with most spirv extensions yet, though.
-
-## Missing extensions
-
-Using these extensions will likely cause a crash.
-
-- VK_EXT_transform_feedback
-- VK_AMD_buffer_marker
-- VK_NV_device_diagnostic_checkpoints
-- VK_NV_scissor_exclusive
-- VK_NV_mesh_shader
-- VK_INTEL_performance_query
-- VK_NV_shading_rate_image
-- VK_NV_fragment_shading_rate_enums
-- VK_NV_device_generated_commands
-- The old NV raytracing extensions. They also won't be supported in the future,
-  use the KHR extensions instead.
-- VK_EXT_descriptor_buffer
-
-- VK_EXT_extended_dynamic_state3
-- VK_EXT_shader_object (incomplete support)
+For a list of supported/unsupported extensions, see [exts.hpp](../src/exts.hpp).
 
 ## NOTES:
 - vendor-specific extensions are generally not a focus, unless someone
@@ -208,7 +21,6 @@ Using these extensions will likely cause a crash.
   layer itself is using it for the vertex viewer (which would conflict with
   an application-side use of it). It's only supposed to be used by tools/layers
   anyways.
-
 - Extensions that have significant changes to command recording (such as
   new pipeline bind points or new commands) will very likely always lead to
   significant problems. Implementing basic support for them isn't complicated

docs/own/workstack.md

@@ -1,5 +1,15 @@
+- [ ] try to enable bufferDeviceAddress
+- [ ] fix errors with validation tests
+	- [ ] document how to run validation tests
+- [ ] when VIL_SKIP_EXT_CHECK is set (or other env var?) override supported
+      extensions in that function. Investigate how to make this work.
+	  Can be provided in layer manifest or something?
+
+- [ ] implement VK_KHR_dynamic_rendering_local_read for core 1.4
+- [ ] impement VK_KHR_pipeline_executable_properties
 - [ ] fix invalid pipeline barrier with BeginRendering (test e.g. with iro gpuDebugDraw)
 - [ ] fix vulkan samples "Losing open cmd" with trianglevulkan13
+- [ ] copyChain: add functions for proper deep copying
 
 - [ ] Format weird for (RW)ByteAddressBuffers in hlsl/slang
 	- [ ] in that case, allow to explicitly specify the format to be printed.