Skip to content
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

Format reinterpretation of r10x6g10x6b10x6a10x6 and similar #505

Open
jenatali opened this issue Jan 2, 2025 · 0 comments
Open

Format reinterpretation of r10x6g10x6b10x6a10x6 and similar #505

jenatali opened this issue Jan 2, 2025 · 0 comments

Comments

@jenatali
Copy link
Contributor

jenatali commented Jan 2, 2025

The Vulkan spec lists R10x6G10x6B10x6A10x6 in its own format compatibility class, the "64-bit R10G10B10A10" class (see https://docs.vulkan.org/spec/latest/chapters/formats.html#formats-compatibility-classes). There are test cases that reinterpret this format to R16G16B16A16 and R32G32 formats. These test cases would seem to violate VUID-VkImageViewCreateInfo-image-01761:

If image was created with the VK_IMAGE_CREATE_MUTABLE_FORMAT_BIT flag, but without the VK_IMAGE_CREATE_BLOCK_TEXEL_VIEW_COMPATIBLE_BIT flag, and if the format of the image is not a multi-planar format, format must be compatible with the format used to create image, as defined in Format Compatibility Classes

This would appear to be either a spec bug, where these 64-bit non-planar non-block formats should be added to the normal 64-bit non-planar non-block compatibility class, or else this is a test bug where this conversion shouldn't be tested.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant