Skip to content

Conversation

@spencer-lunarg
Copy link
Contributor

closes #6323 and #6071

New messages now look like

[VUID-StandaloneSpirv-None-10684] Invalid explicit layout decorations on type for operand '5[%_ptr_Private__struct_2]', the Private storage class has a explicit layout from the Offset decoration.

and

[VUID-StandaloneSpirv-None-10684] Invalid explicit layout decorations on type for operand '6[%_ptr_Workgroup__arr_uint_uint_4]', the Workgroup storage class has a explicit layout from the ArrayStride decoration.


Providing both the storage class and the decoration that makes it explicit layout should be enough, the whole details around which version make it valid or not-valid I think is overkill, the main thing is showing a SPIR-V generator what to look for

@spencer-lunarg
Copy link
Contributor Author

@alan-baker friendly ping, mainly because I want to sneak this into the next SDK release and we are freezing the spirv commit friday

@alan-baker
Copy link
Contributor

I think the shaderc smoketest is unrelated to your change.

@spencer-lunarg
Copy link
Contributor Author

@alan-baker I can rebase incase and try again

@spencer-lunarg spencer-lunarg force-pushed the spencer-lunarg-better-explicit-layout-msg branch from 0c545e5 to 85d3885 Compare September 24, 2025 21:05
@alan-baker alan-baker merged commit 19042c8 into KhronosGroup:main Sep 24, 2025
22 checks passed
@spencer-lunarg spencer-lunarg deleted the spencer-lunarg-better-explicit-layout-msg branch September 26, 2025 05:38
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

Successfully merging this pull request may close these issues.

VUID-StandaloneSpirv-None-10684 still too vague

2 participants