Spencer Fricke
Spencer Fricke
Inside https://github.com/KhronosGroup/glslang/blob/main/SPIRV/GlslangToSpv.h there is ```c++ struct SpvOptions { bool generateDebugInfo {false}; bool stripDebugInfo {false}; bool disableOptimizer {true}; bool optimizeSize {false}; bool disassemble {false}; bool validate {false}; bool emitNonSemanticShaderDebugInfo {false}; bool...
for https://github.com/compiler-explorer/compiler-explorer/pull/6883 confirmed locally this grabs the rolling release and creates a `glslang-trunk` going `./bin/ce_install glsl`
adds some more details to the technical parts of `VK_KHR_buffer_device_address` (mostly from the SPIR-V side, but didn't quite fit in the SPIRV-Guide scope)
> The macOS 12 runner image will be removed by December 3rd, 2024. > ... > Jobs using the macos-12 YAML workflow label should be updated to macos-15, macos-14, macos-13,...
closes https://github.com/KhronosGroup/SPIRV-Guide/issues/24
`OpCopyObject`/`OpCopyLogical`/`OpCopyMemory` How are they used, can they be used anywhere, etc
Go over the various [Image Instructions](https://registry.khronos.org/SPIR-V/specs/unified1/SPIRV.html#_image_instructions) Things like - `OpSampledImage` vs `OpTypeSampledImage` - `OpImageFetch` - `OpImageTexelPointer` - `OpImageSparseTexelsResident`
Things like `OpLine`, `OpSource`, `NonSemantic.Shader.DebugInfo.100`, etc are designed to allow SPIR-V generators to add this information into the SPIR-V and then allow tooling to retrieve this information to help map...
Similar to the LLVM `undef` (and later `Poison`) What is `OpUndef`, when is it used, when can it be valid (or invalid)
It is very common you will find an `OpImage` or `OpStore` and need to get back to the `OpVariable`, the issue is how does one properly write a loop to...