KhronosGroup / KhronosGroup/Khronos-Schemas
VkPhysicalDeviceHostImageCopyPropertiesEXT in profiles schema differs from spec.
- Dominant language
- Ruby
- Stars
- 5
- Forks
- 6
- Avg merge
- 4m
- Merged PRs (30d)
- 4
Description
Vulkan spec's definition of `VkPhysicalDeviceHostImageCopyPropertiesEXT`:
```c
VkStructureType sType;
void* pNext;
uint32_t copySrcLayoutCount;
VkImageLayout* pCopySrcLayouts;
uint32_t copyDstLayoutCount;
VkImageLayout* pCopyDstLayouts;
uint8_t optimalTilingLayoutUUID[VK_UUID_SIZE];
VkBool32 identicalMemoryTypeRequirements;
```
The profiles schema says that this struct should contain only the members `optimalTilingLayoutUUID` and `identicalMemoryTypeRequirements`.
But vulkaninfo and vulkan-caps-viewer print the entire structs. Is this just a bug in the schema generator?
Contributor guide
Research direction
Compare the profiles schema definition for VkPhysicalDeviceHostImageCopyPropertiesEXT with the Vulkan specification, then trace the schema generator that produces it. Check how vulkaninfo and vulkan-caps-viewer consume the result; done means the generated schema consistently represents the complete struct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100