[SPIR-V] Hitting max ID bound #6636
Comments
maj-tom
added
bug
s-perron
added a commit
to s-perron/DirectXShaderCompiler
that referenced
this issue
May 27, 2024
Vulkan implementation can have different limits on the maximum value used as an id in a SPIR-V binary. SPIRV-Tools generall assumes this limit is 0x3FFFFF because all implementations must support at least that value for an id. Since many implementations can support larger values, the tools allows an option that will set a different limit. This commit add an option to DXC to do the same. Fixes microsoft#6636
s-perron
added a commit
to s-perron/DirectXShaderCompiler
that referenced
this issue
May 27, 2024
Vulkan implementation can have different limits on the maximum value used as an id in a SPIR-V binary. SPIRV-Tools generall assumes this limit is 0x3FFFFF because all implementations must support at least that value for an id. Since many implementations can support larger values, the tools allows an option that will set a different limit. This commit add an option to DXC to do the same. Fixes microsoft#6636
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In my application I often exceed kDefaultMaxIdBound, how to best deal with this? My understanding is that this is just the minimum bound required by the specification, so how to override it? As a quick test if I put a higher value in this constant it avoids my problem, but since the value is given by the spec, this seems not the correct solution
The text was updated successfully, but these errors were encountered: