-
-
Hello,
I have been wondering if there is an option is to run the validator on the generated module as I can't find any. The only integration of SPIRV-Tools I'm aware of is the disassemble option an…
-
Simple reproducer:
```c++
#version 460
layout (location = 0) out vec4 fragColor;
layout(binding = 0, std430) readonly buffer A { vec4 a[]; };
layout(binding = 0, std430) readonly buffer B { u…
-
If a sampler is in a struct and relaxed rules (-R) are used when generating SPIR-V code, it can have incorrect output.
Here's an example GLSL shader:
```glsl
#version 450 core
in vec2 VarVerte…
-
**Is your feature request related to a problem? Please describe.**
WGSL doesn't have syntax to specify input attachments for Vulkan subpasses.
This is limiting when using naga as a shader compiler f…
-
```
DEBUG_REPORT: [ UNASSIGNED-CoreValidation-Shader-InconsistentSpirv ] Object: VK_NULL_HANDLE (Type = 0) | SPIR-V module not valid: Structure id 27 decorated as Block must follow standard uniform …
-
We can elide the leading dialect prefix when dealing with nested SPIR-V types, e.g.: `!spirv.ptr>` ==> `!spirv.ptr`.
The abbreviated format should support arbitrary nesting of SPIR-V types.
kuhar updated
6 months ago
-
We have to upstream SPIR-V buit-ins declarations (enabled by https://github.com/intel/llvm/pull/1384 ) to llorg. Otherwise we can't compile any SYCL sample using our SYCL headers and llorg clang:
`…
-
**Describe the bug**
With some SyCL-CTS tests I'm seeing SPIR-V declaring `OpTypeBool` as Kernel function parameters, e.g. `test_spec_constants`. It might not be the best test to dig into this proble…
-
The `lib/CIR/CodeGen/TargetInfo.cpp` collectively includes the implementations of `TargetInfo` and `ABIInfo` for the both targets we currently support: `x86_64` and `AArch64`. Soon I may try merging t…