On Tue Nov 7 14:03:18 2023 +0000, Giovanni Mascellani wrote:
Ok, if you could structure next MRs so that frontend changes are introduced before backend changes I'd be happy to have a look at problems that might appear with the shader runner.
Vulkan asserts if we pass invalid SPIR-V, so to fix the runner we'd probably depend on spirv-tools. The problem with emitting errors in the backend is, after the necessary changes are upstream, we'd be handling errors which can't occur and should be handled with an assertion.