-
Notifications
You must be signed in to change notification settings - Fork 396
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
layers: Rework shader variable access logic #8058
layers: Rework shader variable access logic #8058
Conversation
CI Vulkan-ValidationLayers build queued with queue ID 191712. |
CI Vulkan-ValidationLayers build # 16686 running. |
CI Vulkan-ValidationLayers build # 16686 failed. |
fd98da5
to
e12eef6
Compare
CI Vulkan-ValidationLayers build queued with queue ID 191738. |
CI Vulkan-ValidationLayers build # 16687 running. |
CI Vulkan-ValidationLayers build # 16687 failed. |
CI Vulkan-ValidationLayers build queued with queue ID 191811. |
CI Vulkan-ValidationLayers build # 16690 running. |
CI Vulkan-ValidationLayers build # 16690 passed. |
CI Vulkan-ValidationLayers build queued with queue ID 191836. |
CI Vulkan-ValidationLayers build # 16691 running. |
CI Vulkan-ValidationLayers build # 16691 passed. |
e12eef6
to
9bc75e9
Compare
CI Vulkan-ValidationLayers build queued with queue ID 191918. |
CI Vulkan-ValidationLayers build # 16692 running. |
CI Vulkan-ValidationLayers build # 16692 passed. |
CI Vulkan-ValidationLayers build queued with queue ID 192312. |
CI Vulkan-ValidationLayers build # 16696 running. |
CI Vulkan-ValidationLayers build # 16696 passed. |
e7713fa
to
ab1257c
Compare
CI Vulkan-ValidationLayers build queued with queue ID 192683. |
CI Vulkan-ValidationLayers build # 16699 running. |
CI Vulkan-ValidationLayers build # 16699 passed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. To be honest don't understand all details but checked general structure and trust the expertise of the author.
the
is_written_to
/is_read_from
was a lie and never workedThis adds proper support to know if the variable is actually accessed. This is important for many upcoming SPIR-V related changes