Skip to content

Treat uvec2 as a potential BDA type#3019

Open
mikes-lunarg wants to merge 1 commit into
LunarG:devfrom
mikes-lunarg:detect-uvec2-bdas
Open

Treat uvec2 as a potential BDA type#3019
mikes-lunarg wants to merge 1 commit into
LunarG:devfrom
mikes-lunarg:detect-uvec2-bdas

Conversation

@mikes-lunarg

Copy link
Copy Markdown
Contributor

vkd3d can pass 64-bit buffer device addresses as a 2-component vectors of unsigned 32-bit integers (uvec2). This is apparently a common lowering and explicitly allowed by the GL_EXT_buffer_reference_uvec2 GLSL extension. Therefore, treat uvec2 values (and arrays) as potential BDAs in the forward SPIRV-reflect pass of
SpirVParsingUtil::ParseBufferReferences.

Add a test case to the SpirVParsingUtil for both uvec2 and uvec2[] paths.

vkd3d can pass 64-bit buffer device addresses as a 2-component vectors of
unsigned 32-bit integers (uvec2). This is apparently a common lowering and
explicitly allowed by the GL_EXT_buffer_reference_uvec2 GLSL
extension. Therefore, treat uvec2 values (and arrays) as potential BDAs
in the forward SPIRV-reflect pass of
SpirVParsingUtil::ParseBufferReferences.

Add a test case to the SpirVParsingUtil for both uvec2 and uvec2[]
paths.
@mikes-lunarg mikes-lunarg requested a review from a team as a code owner June 12, 2026 07:22
@mikes-lunarg mikes-lunarg added the approved-to-run-ci Can run CI check on internal LunarG machines label Jun 12, 2026
@CLAassistant

CLAassistant commented Jun 12, 2026

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved-to-run-ci Can run CI check on internal LunarG machines

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants