Issues: KhronosGroup/SPIRV-Headers
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
CI headers check should ensure non-capability enums are guarded by capability, not by extension
help wanted
#278
opened Apr 20, 2022 by
dneto0
As per SPV_KHR_ray_tracing spec minimum version SPIRV should be 1.4
#275
opened Apr 19, 2022 by
pmistryNV
[Request] Updates for Machine-readable content and the documentation.
#267
opened Feb 23, 2022 by
DanielBaumert
A few extended functions for GLSL do not clarify what should happen if given a scalar operand
#254
opened Nov 21, 2021 by
expenses
Header versioning for compatibility with other components (as opposed to SPIR-V versioning)
Fixing Inside Khronos
#167
opened Aug 11, 2020 by
kloczek
Migrate extension headers from SPIRV-Tools to SPIRV-Headers
Functionality Enhancement
help wanted
#137
opened Jan 13, 2020 by
ben-clayton
spirv.core.grammar.json doesn't match PDF description for OpSpecConstantOp
Specification Enhancement
#124
opened Jul 20, 2019 by
gleblebedev
OpAccessChain should allow OpConstantNull for structures
Specification Enhancement
#50
opened Oct 10, 2017 by
ianromanick
control flow path branching and block mangling
Fixing Inside Khronos
question
#22
opened Sep 17, 2016 by
sylware
OpGroupIAdd shouldn't be forced to have the same return type as argument type
Extension
#9
opened May 22, 2016 by
allanmac
ProTip!
Type g p on any issue or pull request to go back to the pull request listing page.