Mateusz Kielan

Depends on #172 so will review after that is merged

I'll not look at the main.cpp at all and let @AnastaZIuk hone his "this is wrong" skills under tutelage of @Erfan-Ahmadi

@keptsecret we usually compile with `-fspv-debug=vulkan-with-source` by default, why doesn't our ray query unit test crash as well? We do have a significant difference that `lib_6_x` target never worked for...

Now we always tend to use Spir-V intrinsics because there's less problem/hassle for us than relying on the HLSL Spir-V codegen for certain "extensions" Here's our custom Godbolt and STL...

@ChristianReinbold, huh `-fspv-debug=vulkan-with-source` segfaults, but `-fspv-debug=source -fspv-debug=tool` works... hmmm

OK, there's another similar issue https://github.com/microsoft/DirectXShaderCompiler/issues/5113 The Non-Semantic Debug info extension was authored by the Renderdoc author, Renderdoc probably doesn't support ray-queries yet and definitely doesn't support RT pipeline shaders....

> [#5113](https://github.com/microsoft/DirectXShaderCompiler/issues/5113) seems to boil down to the same problem, just for another type missing in the switch statement. > > Regarding usage: NSight Graphics also claims to require the...

> Regarding options `source` and `tool`: They behave differently than `vulkan-with-source`, see [HLSLOptions.cpp:1213](https://github.com/microsoft/DirectXShaderCompiler/blob/d39324e0635130e834a68e33b0c603cf5fc9fb4f/lib/DxcSupport/HLSLOptions.cpp#L1213). As far as I see it, the flag that results in entering the broken code-path is `opts.SpirvOptions.debugInfoRich...

very nice, very clean

why do you have random things from sorakrit here instead of your own branch against his or `master` ? I literally can't see whats yours and what's @keptsecret's.