diff options
| author | Jay Kwak <82421531+jkwak-work@users.noreply.github.com> | 2024-12-11 13:28:40 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-12-11 13:28:40 -0800 |
| commit | e50aac13e2c161d672b137a62f6d66820d0f9ff1 (patch) | |
| tree | 89d30f6c2a63db452a6fe15619a6f148de4bbf39 /include | |
| parent | f573c15868234ab6013faf0fc2b93a72fa89f21d (diff) | |
Update SPIRV submodules (#5815)
* Update SPIRV submodules
With the latest SPIR-V submodules, one of tests started failing:
tests/gpu-feature/texture/query/footprint/nv-shader-texture-footprint.slang
[ForceInline] is added to GLSL texture functions in order to inline %true and %false.
Without it, the value was indirectly passed down via a function parameter, which broke the existing test.
Also the test is modified to use -DAG, because the order unpredictably changed for Grad variants due to additional [ForceInline] marks for Gradient functions.
A new validation check in SPIRV-Tools was causing a validation error:
```
error: line 324: [VUID-StandaloneSpirv-OpTypeImage-06924] Cannot store to OpTypeImage, OpTypeSampler, OpTypeSampledImage, or OpTypeAccelerationStructureKHR objects
OpStore %17 %242
```
It appears that this is a bug on SPIRV-Tools.
A proper fix is proposed to Khronos/SPIRV-Tools:
https://github.com/KhronosGroup/SPIRV-Tools/pull/5914
But this commit uses `shader-slang/SPIRV-Tools/fix_for_OpImageSampleFootprintNV` with a custom fix as a temporary solution:
https://github.com/shader-slang/SPIRV-Tools/tree/fix_for_OpImageSampleFootprintNV
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions