KhronosGroup / KhronosGroup/Vulkan-ValidationLayers

Handle detecting which members in the Push Data were accessed

Open
#12,747 0 comments 0 reactions 1 assignee Claimed by @spencer-lunarg View on GitHub
Bug
Dominant language
C++
Stars
1k
Forks
504
Avg merge
11h 35m
Merged PRs (30d)
224

Description

From https://gitlab.khronos.org/Tracker/vk-gl-cts/-/issues/6753

Will hit if you run things like `dEQP-VK.binding_model.descriptor_heap.zero_stride.*heap_with_*` as well

This will require proper detection of accesses... which we already do in the GPU-AV path... likely will want to just move over that logic but will wait until the SDK release as this will want full testing

For now if you go

```glsl
layout(push_constant) uniform PC {
uint a;
uint b;
uint c; // never used
}
```

you will get a false positive that you never called `vkCmdPushDataEXT`

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.