KhronosGroup / KhronosGroup/Vulkan-ValidationLayers
Add GPL VUs around various graphics state
- Dominant language
- C++
- Stars
- 1k
- Forks
- 504
- Avg merge
- 11h 35m
- Merged PRs (30d)
- 224
Description
- [ ] VUID-VkGraphicsPipelineCreateInfo-flags-08899
- [ ] VUID-VkGraphicsPipelineCreateInfo-flags-08900
- [ ] VUID-VkGraphicsPipelineCreateInfo-flags-08903
- [ ] VUID-VkGraphicsPipelineCreateInfo-flags-08904
- [ ] VUID-VkGraphicsPipelineCreateInfo-flags-08906
- [ ] VUID-VkGraphicsPipelineCreateInfo-flags-08907
Need to still better understand if these are needed or not
Some related paper trails of me trying to work on these in the past
- https://github.com/KhronosGroup/Vulkan-ValidationLayers/issues/7054
- https://gitlab.freedesktop.org/mesa/mesa/-/issues/10663
- https://gitlab.khronos.org/vulkan/vulkan/-/issues/3801#note_456409
- https://gitlab.khronos.org/vulkan/vulkan/-/issues/3803
- https://gitlab.khronos.org/vulkan/vulkan/-/issues/3804
Contributor guide
Research direction
No files, tests, or entry points are named. Start by reviewing the six listed VUIDs and the linked Vulkan ValidationLayers, Mesa, and Vulkan specification discussions to determine whether each requirement applies. Done means reaching a supported decision for every VUID and adding the corresponding validation coverage where needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100