ru♂SLAVE
ru♂SLAVE
**Environment:** - Mobile Device: Huawei Mate 60 Pro+ - Layer: `VK_LAYER_KHRONOS_validation` **Describe the Issue** I used `VK_HUAWEI_subpass_shading` device extension, but faced with VVL error: ``` ERROR: [3012269921][VUID-VkPipelineShaderStageCreateInfo-pName-00707] : Validation Error:...
Can you add support for [`GL_HUAWEI_subpass_shading`](https://github.com/KhronosGroup/GLSL/blob/main/extensions/huawei/GLSL_HUAWEI_subpass_shading.txt) and corresponding [`SPV_HUAWEI_subpass_shading`](https://htmlpreview.github.io/?https://github.com/KhronosGroup/SPIRV-Registry/blob/main/extensions/HUAWEI/SPV_HUAWEI_subpass_shading.html)? Here we need a translator from *GLSL* to *SPIR-V* that supports [`GL_HUAWEI_subpass_shading`](https://github.com/KhronosGroup/GLSL/blob/main/extensions/huawei/GLSL_HUAWEI_subpass_shading.txt) features.
Want to clarify compute shaders barriers. To do this, I compared the language mappings to SPIR-V: * HLSL: https://github.com/Microsoft/DirectXShaderCompiler/blob/main/docs/SPIR-V.rst#synchronization-intrinsics * GLSL: https://docs.vulkan.org/glsl/latest/chapters/spirvmappings.html#_mapping_of_barriers
This extension is written to support `VK_KHR_relaxed_block_layout` **Vulkan** extension. Currently there is only `VK_EXT_scalar_block_layout` support - `GL_EXT_scalar_block_layout`. To correct this historical injustice, I present this extension. If GLSL Working Group...