-
Notifications
You must be signed in to change notification settings - Fork 474
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
VkLogicOp with floating and sRGB color attachments #2426
Comments
@YaaZ I confirmed with some driver developers, yes, this is telling you that the HW will ignore any logical operations, so there is no "undefined behavior" and it is not a spec violation as it is actually very well specified what will not happen With that, I think this is a good thing to add as a warning since I was not even aware of this case and assume others might also not as well |
Ok, I got it. So you actually can use logicOp with sRGB attachments, though it must have no effect. |
Can you tell me what driver/gpu you are seeing this effect on? Also which exact format you see an effect? This seems like a lack of CTS coverage as there should be tests that this is ignored |
No idea about the drivers, something default for Fedora 40, but here are versions from
XOR logicOp worked for me at least with |
created https://gitlab.khronos.org/vulkan/vulkan/-/issues/3981 to track this |
update: was discussed and seems this might just be a driver bug, we are going to create CTS tests and make sure the drivers are doing what the spec says should happen, Thanks again for reporting this btw! |
CTS issue is being tracked here https://gitlab.khronos.org/Tracker/vk-gl-cts/-/issues/5278 For the time being, moved to a Spec issue, if we decide to add a Validation restriction, will bring back to Validation Layer repo, but for now there is nothing actionable from the Validation Layers point of view |
Spec states:
https://registry.khronos.org/vulkan/specs/1.3-extensions/html/vkspec.html#framebuffer-logicop
Although for me they work for much more attachment formats, including SRGB and even SFLOAT.
It's nice that they still work, but this is a spec violation and deserves to be caught by validation layers.
The text was updated successfully, but these errors were encountered: