It seems the implementation of OpAbortKHR doesn't use an explicit layout and it then fails to be parsed correctly in Mesa. VVL support is also missing but I reported it here KhronosGroup/Vulkan-ValidationLayers#12298.
This has been found with the KHR_shader_abort VKCTS tests here https://gerrit.khronos.org/c/vk-gl-cts/+/16088.
I think it should emit the ArrayStride decoration to match what the SPIR-V spec is saying: "Message Type is the type of the data to be written. Message Type must be a concrete type. If the Shader capability is declared, Message Type must have an explicit layout."
It seems the implementation of OpAbortKHR doesn't use an explicit layout and it then fails to be parsed correctly in Mesa. VVL support is also missing but I reported it here KhronosGroup/Vulkan-ValidationLayers#12298.
This has been found with the KHR_shader_abort VKCTS tests here https://gerrit.khronos.org/c/vk-gl-cts/+/16088.
I think it should emit the ArrayStride decoration to match what the SPIR-V spec is saying: "Message Type is the type of the data to be written. Message Type must be a concrete type. If the Shader capability is declared, Message Type must have an explicit layout."